Code for Analyzing the PO Update Notification

Edit online

About this task

Typically, the following steps are performed to analyze a PO Update Notification:

Procedure

  1. Translate PO Update Notification into the application format of the ERP system.
    Note: The ERP system mentioned here is an external system that interfaces with the Sterling B2B Integrator usually at the customer end.
  2. Pass translated PO Update Notification to the ERP system.
  3. Transform response of ERP system into RosettaNet document(s).
  4. Pass the translated response document(s) back to private PIP 3A7.
  5. Write the logic to read POChangeRequest or POCancellationRequest from the file system. If you do not want to read the messages from the file system, you can change it. You must be sure your code matches the interface defined above.
  6. Send POChangeRequest or POCancellationRequest to public PIP 3A7.
  7. Consume the FinalPIPStatus from the public 3A7 Seller process. If the value is true, an Acknowledgment for the POChangeRequest or POCancellationRequest has been received and the PIP3A7 process finishes with a success status. If the value is false, it might be necessary to roll back the transaction in step 8.
  8. If you have opened a transaction in step 4, you need to insert the code to close the transaction for PIP3A7 or roll back the transaction. Instead of an automated rollback, sending an e-mail notification to the responsible administrator is an alternative “manual” approach.
  9. If pending items exist, private process 3A7 is started and the POUpdateNotification service content is passed through the process data.