Show TOC

Example documentationExample: PO Collaboration in Service Parts Management

 

SAP Supply Network Collaboration (SAP SNC) supports third-party order processing (TPOP) in the business scenarios of Service Parts Management. In third-party order processing, your customer (a dealer) orders a product from you. You do not deliver to the customer yourself; rather, you order the product from a supplier who delivers the product directly to the customer. In the TPOP scenario, SAP Customer Relationship Management (SAP CRM) receives the customer's purchase order. To ensure that the purchase order is visible for the supplier, SAP CRM triggers the creation of a TPOP purchase order in the SAP ERP system (SAP ERP 6.0 with active Service Parts Management). The SAP ERP system sends the TPOP purchase order to SAP SNC and to the supplier.

You and the supplier use purchase order collaboration in SAP SNC to display the TPOP purchase orders and the processing progress of the TPOP purchase orders. A supplier who does not use EDI also creates confirmations and advanced shipping notifications (ASNs) in SAP SNC. A supplier, who is working with EDI, creates the confirmations and ASNs in his or her back-end system and sends them to the SAP ERP system. The SAP ERP system forwards the purchase order and the ASNs to SAP SNC. Note that confirmations that are sent to SAP SNC overwrite confirmations that the supplier has created manually in SAP SNC.

This example is only relevant for an SCM server installation.

Note Note

We do not recommend using the new purchase order collaboration XML messages available as of SAP ERP 6.0 Enhancement Pack 4 for purchase order collaboration with service parts management.

End of the note.

Prerequisites

  • The master data needed for purchase order collaboration (product, location, and business partner) is available in SAP SNC. For more information, see the configuration guide for the business scenarios of Service Parts Management.

  • You have defined descriptions for the cancelation reasons in Customizing for Supply Network Collaboration under Start of the navigation path Purchase Order Next navigation step Reason Codes Next navigation step Define Descriptions for Cancellation Reason Codes End of the navigation path. Cancellation reason codes are relevant if a customer cancels a sales order in SAP CRM. SAP SNC displays the cancellation reason code.

  • You have defined which priority SAP SNC displays for a purchase order item in Customizing for Advanced Planning and Optimization under Start of the navigation path Supply Chain Planning Next navigation step Service Parts Planning Next navigation step Basic Settings Next navigation step Attributes and Priorities of Sales Documents End of the navigation path. SAP SNC determines the priority depending on the sales document type and the item category from the CRM sales order. The SAP ERP system sends this data to SAP SNC with the TPOP purchase order.

Process

Purchase Order Collaboration with a Supplier Who Does Not Use EDI

  1. The SAP ERP system sends a new or modified TPOP purchase order to SAP SNC and to the supplier, as follows:

    • The transfer to SAP SNC occurs as follows: The SAP ERP system sends the IDoc ORDNTF.ORDINT01 (message variant RPL) to SAP NetWeaver. SAP NetWeaver maps the IDoc to an XML message of the type ReplenishmentOrderNotification and sends this XML message to SAP SNC.

    • You send the purchase order to the supplier, for example, by fax.

  2. The supplier displays the purchase order in SAP SNC, for example, in purchase order collaboration or in the due list for purchasing documents. The due list for purchasing documents displays uncovered purchase orders, in other words, purchase orders for which the ASN quantities do not suffice.

  3. If the supplier wants to confirm the delivery before the delivery and the ASN are sent, the supplier manually creates confirmation schedule lines in the purchase order in SAP SNC.

  4. If the supplier sends the delivery, he or she creates an ASN for the purchase order in SAP SNC. SAP SNC and the SAP ERP system process the ASN and the purchase order as follows:

    1. SAP SNC sends the ASN to the SAP ERP system.

    2. The SAP ERP system posts a statistical goods receipt and the ASN items receive the status Completely Processed in the SAP ERP system.

    3. The SAP ERP system sends the updated ASN back to SAP SNC.

    4. If the supplier has delivered the purchase order in full, the ASN items in SAP SNC acquire the Complete Goods Receipt status and (as long as the open quantity does not breach the absolute underdelivery tolerance) the purchase order items acquire the status Delivery Completedstatus (see Update of GR Data in the Purchase Order).

    For more information, see the business scenario for Service Parts Management and ASN Processing.

Purchase Order Collaboration with a Supplier Who Uses EDI

  1. The SAP ERP system sends the new or modified TPOP purchase order not only to SAP SNC. It also sends it to the supplier back-end system at the same time by means of EDI.

    • The transfer to SAP SNC works as follows: The SAP ERP system sends the IDoc ORDNTF.ORDINT01 (message variant RPL) to SAP NetWeaver. SAP NetWeaver maps the IDoc to an XML message of the type ReplenishmentOrderNotification and sends this XML message to SAP SNC.

    • The SAP ERP system uses the IDoc ORDERS.ORDERS05 to send the TPOP purchase order to the supplier. EDI inbound processing maps the IDoc to the EDI message type 850.

  2. If the supplier wants to confirm the delivery before the delivery and the ASN are sent, the supplier creates a confirmation in his or her back-end system and sends it to the SAP ERP system.

    To send the confirmation, the supplier uses the EDI message type 870. EDI outbound processing maps the message to the IDoc ORDRSP.ORDERS05.

  3. The SAP ERP system updates the purchase order and sends the updated purchase order with the confirmation schedule lines to SAP SNC.

    The transfer to SAP SNC works as follows: The SAP ERP system sends the IDoc ORDNTF.ORDINT01 to SAP NetWeaver. SAP NetWeaver maps the IDoc to an XML message of the type ReplenishmentOrderNotification and sends this XML message to SAP SNC.

  4. The supplier creates an ASN in his or her back-end system and sends the ASN to the SAP ERP system by means of EDI.

    The EDI outbound processing maps the EDI message to the IDoc DESADV.DELVRY05.

  5. The SAP ERP system posts a statistical goods receipt and the ASN items receive the status Completely Processed in the SAP ERP system.

  6. The SAP ERP system sends the updated ASN to SAP SNC.

    The transfer to SAP SNC works as follows: The SAP ERP system sends the IDoc DELINF.DELVRY05 to SAP NetWeaver. SAP NetWeaver maps the IDoc to an XML message of the type DeliveryInformation and sends this XML message to SAP SNC.

  7. If the supplier has delivered the purchase order in full, the ASN items in SAP SNC acquire the Complete Goods Receipt status and the purchase order items acquire the status Delivery Completed status.

    Note Note

    The supplier can also manually create confirmation schedule lines and ASNs in SAP SNC, if required (see above).

    End of the note.