Show TOC

Background documentationIntegration of Purchase Order Collaboration with SAP ERP

 

You can integrate purchase order collaboration in SAP Supply Network Collaboration (SAP SNC) with an SAP customer back-end system as of SAP R/3 4.6C.

Features

XML Messages

Depending on the SAP back-end system that you are using, you can use XML messages or XML messages mapped to IDocs to send purchase orders and confirmations between SAP ERP and SAP SNC. For more information, see XML Messages for Purchase Order Collaboration.

Changed Purchase Order Items

When a customer changes a purchase order in his or her back-end system, the system sends an updated purchase order to SAP SNC. An SAP customer back-end system does not send an changed purchase order to SAP SNC in the following instances:

  • If a goods receipt is posted in the back-end system (enhancement package 3 for SAP ERP 6.0 or lower)

  • If the customer has manually set the delivery completed indicator for an item in the purchase order (enhancement package 3 for SAP ERP 6.0 or lower)

  • If the components of a subcontract order were changed in the back-end system

Goods Receipt Data in Purchase Orders Schedule Lines

For an SAP customer back-end system of enhancement package 3 for SAP ERP 6.0 or lower, the back-end system updates the goods receipt quantity in the request schedule line in the purchase order at a goods receipt. However, the customer back-end system does not send a corresponding updated purchase order to SAP SNC at goods receipt. The goods receipt information is only sent to SAP SNC (together with other changes to the purchase order) if, for example, the customer manually changes the purchase order in the back-end system after a goods receipt, in a way that triggers the sending of a message. As of enhancement package 4 for SAP ERP 6.0, the goods receipt triggers the sending of the PurchaseOrderERPReplenishmentOrderCollaborationNotification XML message to SAP SNC.

Goods Receipt Data in Purchase Order Items

For an SAP customer back-end system of enhancement package 3 for SAP ERP 6.0 or lower, the ORDERS05 IDoc cannot transfer the delivery completed indicator. The back-end system therefore does not generate a message if the customer manually sets the delivery completed indicator in the back-end system for the purchase order item.

As of enhancement package 4 for SAP ERP 6.0, the PurchaseOrderERPReplenishmentOrderCollaborationNotification XML message can transfer this indicator. The SAP ERP back-end system also generates the XML message when the customer manually sets the delivery completed indicator. The PORDCR102 IDoc also carries this indicator, but does not transfer the goods receipt quantity.

In a standard purchase order in SAP ERP, a customer can enter a supplier in the Vendor field of the Delivery Address tab for a purchase order item. This supplier can differ from the supplier that has been entered as vendor for the purchase order header. However, the supplier entered on the Delivery Address tab is not transferred to SAP SNC as the goods recipient if you use the ORDERS.ORDERS05 IDoc. For information about example code that enables you to transfer this supplier as the goods recipient to SAP SNC, see SAP Note 888599Information published on SAP site. If you use the PurchaseOrderERPReplenishmentOrderCollaborationNotification XML message available with enhancement package 4 for SAP ERP 6.0, this goods recipient is transferred.

Deleting Confirmation Schedule Lines

An SAP ERP back-end system cannot delete confirmation schedule lines, it can only replace them. To avoid temporary inconsistencies between the SAP back-end system and SAP SNC, we recommend the following: After SAP SNC has deleted the confirmation schedule lines for an item, the supplier should create new confirmation schedule lines for the item. Only then is the supplier allowed to publish the purchase order.

Example Example

Example of an Inconsistency

The customer has made confirmation-relevant changes in the customer back-end system to two purchase order items having three confirmation schedule lines each, and has sent the purchase order to SAP SNC. SAP SNC has deleted the confirmation schedule lines for the two items. The supplier creates a confirmation schedule line for one of the items but not for the other item. The supplier then publishes the purchase order, and SAP SNC sends the purchase order to the customer back-end system. In the customer back-end system, the three confirmation schedule lines for the one item are automatically replaced by the single new confirmation schedule line. The other item retains the original three confirmation schedule lines.

End of the example.
Approval Process

In purchase order collaboration, the customer can put confirmations created by the supplier through an approval process. The customer can transfer approved confirmation data into the purchase order manually or automatically as request data and also transfer the changed purchase order to the customer back-end system. We support message integration with an SAP back-end system as of SAP ERP 6.0. Special IDocs are required for receiving and sending purchase orders (PORDCH.PORDCH02 and PORDCR1.PORDCR102) in an SAP ERP system of enhancement package 3 for SAP ERP 6.0 or lower. As of enhancement package 4 for SAP ERP 6.0, the XML messages PurchaseOrderERPReplenishmentOrderCollaborationNotification and PurchaseOrderERPRequest_V1 are available. For more information, see Example: Message Flow for Contract Manufacturing Procurement and SAP Note 888599Information published on SAP site. If the PO integration is realized using the PORDCR102 Idoc or the PORDCH02 Idoc, you must activate the implementation of the ME_BAPI_PO_CUST Business Add-In that is suggested in SAP Note 888599Information published on SAP site.

Confirmation Control

Confirmation control is not integrated with confirmation control in an SAP back-end system of enhancement package 3 for SAP 6.0 or lower. As of enhancement package 4 for SAP ERP 6.0, if you are using the PurchaseOrderERPReplenishmentOrderCollaborationNotification XML message to transfer purchase orders to SAP SNC, whether a supplier can confirm a purchase order or not on the SAP SNC Web UI is determined by the confirmation control settings made for the purchase order in SAP ERP.

Notes

Notes are integrated in the XML messages for purchase orders. However, an SAP customer back-end system cannot receive and process the notes.

Transferring Delivery Tolerances

The transfer of delivery tolerances from an SAP back-end system up to and including enhancement package 3 for SAP ERP 6.0 is only possible with the following IDocs:

  • PORDCR1.PORDCR102

  • ORDNTF.ORDINT01

    The ORDNTF.ORDINT01 IDoc is only relevant for the SAP customer back-end system in the service parts management scenarios (SAP ERP with active Service Parts Management). The IDoc transfers no overdelivery indicator and only transfers the underdelivery and overdelivery tolerance at item level (but not at header level).

As of enhancement package 4 for SAP ERP 6.0, you can transfer delivery tolerances using the PurchaseOrderERPReplenishmentOrderCollaborationNotification XML message. This XML message also transfers the overdelivery indicator.

If you, the customer, use the Core Interface (CIF) to transfer contracts and purchasing info records from an SAP back-end system to the SAP SNC system, you must use the CIFMAT01 customer exit in the SAP back-end system to allow CIF to transfer the delivery tolerances in the product master.

Price Confirmation

When a supplier confirms a price that differs from the requested price, and sends a purchase order confirmation to a back-end SAP ERP system, the price in the purchase order in SAP ERP can be updated with the confirmed price (For more information, see SAP Library for SAP ERP Central Component at http://help.sap.comInformation published on SAP site under Start of the navigation path Logistics Next navigation step Materials Management (MM) Next navigation step Purchasing (MM-PUR) Next navigation step Vendor Confirmations Next navigation step Procurement Using Vendor Confirmations Next navigation step Confirmations from the Purchasing Viewpoint Next navigation step Receiving Vendor Confirmations via EDI End of the navigation path in the Price Check section). A subsequent update of the purchase order sent back to SAP SNC then contains a new requested price, which is equal to the price that the supplier had confirmed. SAP SNC does not update the original price based on this new requested price. If, however, the customer explicitly changes the price in the SAP ERP system, SAP SNC would update the original price in the purchase order upon receipt of a purchase order update because it differs from the confirmed price.

Note Note

If you adopt price changes in SAP ERP, we recommend you use the original price for deviation analysis in SAP SNC.

End of the note.
Batches and Product Configuration

For information about integrating batches and product configuration with an SAP back-end system, see Integration of Batches and Product Configuration with SAP ERP.

Manufacturer Part Number and AMPL

For information about integrating manufacturer part number data and the approved manufacturer parts list with an SAP back-end system, see Use of MPNs with an SAP ERP Back-End System and Integration of Approved Manufacturer Parts List with CIF.