Show TOC

Example documentationExample: Message Flow for Purchase Order Processing

 

This section shows an example of the message flow if the customer uses the standard purchase order collaboration with SAP Supply Network Collaboration (SAP SNC) and an SAP back-end system. SAP delivers standard XSLT mapping for the integration with these back-end variants. The example does not use subcontracting or an approval process.

Recommendation Recommendation

The figures are intended to provide a general overview. SAP recommends using the integration scenarios, which are part of the XI content for SAP SNC. This allows you to generate message flows and routings automatically.

End of the recommendation.

The process runs as follows:

  1. Create purchase order (customer's ERP system, SAP R/3 4.6C or higher, with or without DIMP)

    The customer creates a purchase order in the ERP system. The ERP system transfers the ORDERS.ORDERS05 IDoc to the customer's SAP NetWeaver system. The SAP NetWeaver system converts the IDoc into an XML message of type ReplenishmentOrderNotification (RON), and transfers it to SAP SNC.

  2. Display purchase order (SAP SNC)

  3. Create or change purchase order (customer's ERP system)

    The customer creates another purchase order in the ERP system, or changes an existing purchase order. The ERP system transfers the ORDCHG.ORDERS05 IDoc to the customer's SAP NetWeaver system. The SAP NetWeaver system converts the IDoc into an XML message of type ReplenishmentOrderNotification (RON), and transfers it to SAP SNC.

    Note the following special points when creating or changing purchase orders:

    • The customer can specify purchase order quantities in the order unit in his or her ERP system. In inbound message processing, SAP SNC automatically converts the order unit into the base unit of measure. If, in SAP SNC purchase order collaboration, the supplier creates confirmed quantities in the base unit of measure, SAP SNC converts the purchase order quantity back into the order unit in outbound message processing when the purchase order is published.

    • The customer always transfers the entire changed purchase order: For more information, see SAP Note 888599.

    • The customer can delete individual purchase order items in his or her ERP system but cannot delete all the items in a purchase order.

  4. Display updated purchase order (SAP SNC)

  5. Create sales order (supplier's ERP system)

  6. Update sales order (supplier's ERP system)

  7. Confirm or change sales order (supplier's ERP system)

    The supplier's ERP system transfers an XML message of type ReplenishmentOrderConfirmation (ROC) to the SAP NetWeaver system, which forwards the message to the SAP SNC system.

    Note Note

    Note that the IDocs, XML messages, and mappings depend on which ERP system and releases are being used. Mappings are sometimes required for the message flow between the supplier's system and SAP SNC, depending on the supplier's system. Since the mappings are dependent on the supplier's system, they cannot be predefined in the SAP SNC standard delivery. You must create the mappings as part of a project solution.

    End of the note.

  8. Receive purchase order, or confirm or change purchase order in the Web UI (SAP SNC)

    The SAP SNC system transfers an XML message of type ReplenishmentOrderNotification (RON) to the SAP NetWeaver system, which converts the message into the IDoc ORDRSP.ORDERS05 and transfers it to the customer's ERP system.

  9. Receive updated purchase order

  10. Publish advanced shipping notification (supplier's ERP system)

    When the material is ready for delivery, the supplier can publish an advanced shipping notification in his or her ERP system. The ERP system transfers an XML message of type DespatchedDeliveryNotification (DDN) to the customer's SAP NetWeaver system, which forwards the message to SAP SNC.

  11. Receive advanced shipping notification or create it in the Web UI, and update the purchase order (SAP SNC)

    If suppliers do not use an ERP system to send advanced shipping notifications, they can create them in the Web UI. The SAP SNC system transfers an XML message of type DespatchedDeliveryNotification (DDN) to the SAP NetWeaver system, which converts the message into the IDoc DESADV.DELVRY03 and transfers it to the customer's ERP system.

    If you use an ERP system without the DIMP industry extension, you use the mapping DespatchedDeliveryNotification_DesadvDelvry03_01. For SAP ERP 6.0 with DIMP, you use the mapping DespatchedDeliveryNotification_DesadvDelvry03_02.

  12. Receive advanced shipping notification (customer's ERP system)

  13. Receive advanced shipping notification and post goods receipt (customer's ERP system)

    When the customer posts the goods receipt (using transaction VL32N in SAP ERP), the customer's ERP system sends the STPPOD.DELVRY03 IDoc to the SAP NetWeaver system. The SAP NetWeaver system converts the IDoc into an XML message of type ReceivedDeliveryNotification (RDN), and transfers it to SAP SNC.

  14. Display goods receipt information (SAP SNC)

Implementation Considerations

If you are using an SAP ERP back-end system as of release enhancement package 4 for SAP ERP 6.0 , you can use XML services instead of the ORDERS05 IDoc when sending purchase orders from SAP ERP. For more information about the integration of purchase order collaboration with SAP ERP, see SAP Help Portal at Start of the navigation path http://help.sap.comInformation published on SAP site Next navigation step SAP Supply Network Collaboration Next navigation step Purchase Order Collaboration Next navigation step Integration of Purchase Order Collaboration with SAP ERP End of the navigation path.