Example: Message Flow for Contract Manufacturing Procurement - SAP Documentation

Page 1 of 5

Example: Message Flow for Contract Manufacturing Procurement

This section provides an overview of the message flow between systems for the Contract Manufacturing Procurement business scenario, which covers the following processes: Purchase order collaboration with contract manufacturing Purchase order collaboration with approval

Note
The graphics only give a basic overview. We do not recommend that you use them as a basis for configuration. Instead, use the integration scenarios and mappings that are part of the XI content for SAP Supply Network Collaboration (SAP SNC). This allows you to generate message flows and routings automatically.

Purchase Order Collaboration with Contract Manufacturing

The process runs as follows: 1. Create subcontract order (SAP ERP 6.0 with or without DIMP) The customer sends IDoc PORDCR1.PORDCR102 to SAP NetWeaver. SAP NetWeaver maps the IDoc to an XML

http://help.sap.com/saphelp_SNC700_ehp02/helpdata/en/49/d2ad03085742f1e10000000a4... 05-Jun-13

Example: Message Flow for Contract Manufacturing Procurement - SAP Documentation

Page 2 of 5

message of type ReplenishmentOrderNotification (RON), which is sent to SAP SNC. 2. Display subcontract order (SAP SNC) 3. Change subcontract order (SAP ERP 6.0 with or without DIMP) The customer sends IDoc PORDCR1.PORDCR102 to SAP NetWeaver, which maps the IDoc to an XML message of type ReplenishmentOrderNotification (RON). 4. Display updated subcontract order (SAP SNC) SAP SNC can now display the updated subcontract order.

Purchase Order Collaboration with Approval

http://help.sap.com/saphelp_SNC700_ehp02/helpdata/en/49/d2ad03085742f1e10000000a4... 05-Jun-13

Example: Message Flow for Contract Manufacturing Procurement - SAP Documentation

Page 3 of 5

The process runs as follows:

http://help.sap.com/saphelp_SNC700_ehp02/helpdata/en/49/d2ad03085742f1e10000000a4... 05-Jun-13

Example: Message Flow for Contract Manufacturing Procurement - SAP Documentation

Page 4 of 5

1. Confirm sales order, update components (contract manufacturer's (CM) ERP system) The ERP system sends a message of type ReplenishmentOrderConfirmation (ROC) to a SAP NetWeaver system at the customer site.

Note
Mappings for the message flow between the supplier's system and SAP SNC are not part of the standard delivery for SAP SNC because the mappings needed depend on the supplier system used. If necessary, you must create the mappings as part of a project-specific solution. 2. Receive ROC or confirm on Web UI and update components (SAP SNC) SAP SNC receives the XML message from SAP NetWeaver. If the OED keeps track of the components, the OED must update the components manually. SAP SNC sends an XML message of type ROC to SAP NetWeaver, which maps the XML message to the IDoc ORDRSP.ORDERS05. 3. Create confirmation in purchase order (customer's SAP ERP system with or without DIMP) 4. Approve confirmation and component consumption (SAP SNC) 5. Change schedule lines or components (SAP SNC) SAP SNC sends a message of type ReplenishmentOrderNotification (RON) to SAP NetWeaver, which maps the XML message to IDoc PORDCH.PORCH02. 6. Change purchase order (customer's SAP ERP system with or without DIMP) The customer's SAP ERP system sends IDoc PORDCR1.PORDCR102 to SAP NetWeaver, which maps the IDoc to an XML message of type RON. 7. Update sales order (CM's ERP system) 8. Update components (SAP SNC) 9. Create delivery (CM's ERP system) The CM's ERP system sends an XML message of type DespatchedDeliveryNotification (DDN) to the customer's SAP NetWeaver system, which in turn sends the message to SAP SNC. 10. Receive ASN or create on Web UI (SAP SNC) SAP SNC sends a message of type DDN to SAP NetWeaver, which maps the message to IDoc DESADV.DELVRY03.

Note
To convert the XML message DespatchedDeliveryNotification (DDN) to the IDoc DESADV.DELVRY03, you can use mapping DespatchedDeliveryNotification_DesadvDelvry03_01 for ERP systems without industry extension DIMP and mapping DespatchedDeliveryNotification_DesadvDelvry03_02 for ERP systems with industry extension DIMP. 11. Receive ASN (customer's SAP ERP system with or without DIMP) 12. Receive delivery and post goods receipt (customer's SAP ERP system with or without DIMP) SAP ERP sends IDoc STPPOD.DELVRY03 to SAP NetWeaver, which maps the IDoc to an XML message of type ReceivedDeliveryNotification (RDN). 13. Update ASN (SAP SNC)

Scope and Limitations

The scope of the Contract Manufacturing Procurement business scenario outlined in this documentation only concerns the customer side (OED). This business scenario does not cover how an ERP system on the supplier's

http://help.sap.com/saphelp_SNC700_ehp02/helpdata/en/49/d2ad03085742f1e10000000a4... 05-Jun-13

Example: Message Flow for Contract Manufacturing Procurement - SAP Documentation

Page 5 of 5

side (that is, the contract manufacturer's side) receives messages sent by the customer, and how it deals with the additional information (for example, components) submitted with these messages. Mappings are only provided for A2A communication (between the OED's ERP system and SAP SNC) from IDoc to XML and vice versa. This business scenario does not cover the tracking of the manufacturing process (production phases) that takes place at the contract manufacturer's site - it does not take into account the current production phase at the contract manufacturer' site. Consequently, the OED planner cannot predict the supply situation of finished goods. The Contract Manufacturing Procurementbusiness scenario has the following limitations: Once a schedule line in the ERP purchase order is changed, the date and quantity data originally requested are lost. Even if the information is stored in SAP SNC, it is not possible to send this information to the CM. The Contract Manufacturing Procurement business scenario is based on functions introduced in SAP ERP 6.0. For lower releases, you need to develop a customer modification. No data import control functions are provided for messages sent from the CM to SAP SNC. The bill of material (BOM) is not available in SAP SNC. New purchase order items cannot be created in SAP SNC. Product substitution is not supported. Scheduling agreements for the subcontracted material are not allowed. A supplier should be able to update the component consumption in SAP SNC until a good receipt has been posted in the customer ERP back-end system. However, the PORDCR102 Idoc does not contain the goods receipt quantity of a PO schedule line. Therefore, you would need to implement the transfer of the goods receipt quantity as part of a customer project to use this function. As of SAP SNC 7.0 and enhancement package 4 for SAP ERP 6.0, you can use the PurchaseOrderERPReplenishmentOrderCollaborationNotification Xml message instead of the IDOC. This XML message transfers the goods receipt quantity. The subcontracting scenario of the RosettaNet Work Order Management Program as described in the PIPs 7B5 (Notify of Manufacturing Work Order), 7B6 (Notify of Manufacturing Work Order Reply), and 7B1 (Work In Process Notification) is not included in the scope of SAP SCM.

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 PORDCH.PORCH02 IDoc when sending purchase orders to SAP ERP, and instead of the PORDCR1.PORDCR102 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 Supply Network Collaboration ERP . Purchase Order Collaboration http://help.sap.com SAP Integration of Purchase Order Collaboration with SAP

http://help.sap.com/saphelp_SNC700_ehp02/helpdata/en/49/d2ad03085742f1e10000000a4... 05-Jun-13