Show TOC

Example documentationExample: Message Flow for Shipment Collaboration

 

This section shows an example of the message flow if the customer uses the standard shipment collaboration with SAP Supply Network Collaboration (SAP SNC) and an SAP ERP back-end system. SAP delivers IDoc to XML mappings for the integration with these back-end variants.

Process

The process runs as follows:

  1. Publish advanced shipping notification (supplier’s ERP system)

    When the material is ready for delivery, the supplier can publish an advanced shipping notification (ASN) 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.

    Note Note

    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.

  2. Receive ASN, or create ASN on the Web UI (SAP SNC)

    Depending on the replenishment requirements, the supplier creates advanced shipping notifications (ASNs). If suppliers do not use an ERP system to send advanced shipping notifications, they can create them on the Web user interface (Web UI) of SAP SNC. The SAP SNC system sends an XML message of type DespatchedDeliveryNotification (DDN) to the SAP NetWeaver system. SAP NetWeaver converts the message to a DESADV.DELVRY05 IDoc before it routes the IDoc to the customer’s SAP ERP system.

  3. Inbound delivery is created (customer's SAP ERP system)

    After the receipt of the DESADV.DELVRY05 IDoc, the customer's SAP ERP system automatically creates an inbound delivery for the expected goods.

  4. Supplier publishes shipment (SAP SNC)

    Depending on the transportation requirements, the supplier creates shipments by grouping one or more ASNs. The supplier can put the shipment in Draft status while the shipment is still being worked on. The supplier publishes the shipment when it is finalized. After the publication, SAP SNC generates an XML message of type FreightOrderExecutionRequest and sends it to SAP NetWeaver. SAP NetWeaver converts the XML message to an SHPMNT.SHPMNT05 IDoc before it routes the IDoc to SAP ERP.

    Note Note

    The supplier can also cancel the shipment again. In this case, SAP SNC generates an XML message of type FreightOrderExecutionCancelRequest. SAP NetWeaver converts the XML message to an SHPCPR.TPSSHT01 IDoc before it routes the IDoc to SAP ERP.

    End of the note.

  5. Shipment document is created (customer's SAP ERP system)

    The customer's SAP ERP system receives the SHPMNT.SHPMNT05 IDoc along with all relevant ASN information, including the expected delivery date/time. The SAP ERP system then automatically creates a shipment document.

  6. Post goods receipt against inbound delivery (customer's SAP ERP system)

    After the physical shipment has arrived at the customer location, the customer posts the goods receipt of the goods against the inbound delivery. When the customer posts the goods receipt, the customer’s ERP system sends an STPPOD.DELVRY03 IDoc to the SAP NetWeaver system. The SAP NetWeaver system converts the IDoc to an XML message of type ReceivedDeliveryNotification (RDN), and transfers it to SAP SNC.

  7. ASN updated with goods receipt status (SAP SNC)

    SAP SNC updates the ASN with the new goods receipt status.

  8. Shipment updated with goods receipt status (SAP SNC)

    After the update of the ASN status, SAP SNC also updates the shipment with the new goods receipt status.