XML Messages for Purchase Order Collaboration
This section describes the XML messages used in purchase order collaboration in SAP Supply Network Collaboration (SAP SNC).
ReplenishmentOrderNotification
This XML message is used to receive a purchase order that the customer has created or changed in his or her back-end system.
If the supplier changes and publishes a purchase order in SAP SNC. SAP SNC uses this XML message to send the changed purchase order to the customer back-end system via SAP NetWeaver. The customer back-end system uses this message to update a purchase order. This XML message requires mapping to IDocs when used with an SAP customer back-end system.
PurchaseOrderERPReplenishmentOrderCollaborationNotification
You use this XML message to receive a purchase order that the customer has created or changed in his or her back-end system. You can use this XML message without mapping to IDocs when integrating with a customer back-end system as of enhancement package 4 for SAP ERP 6.0.
PurchaseOrderERPRequest_V1
This XML message is relevant for contract manufacturing (subcontract orders) or purchase order collaboration with approval process. When the supplier changes and publishes a purchase order in SAP SNC, SAP SNC sends the updated purchase order to the customer back-end system using this message type. You can use this XML message without mapping to IDocs when integrating with a customer back-end system as of enhancement package 4 for SAP ERP 6.0.
The ReplenishmentOrderConfirmation
XML message is used when the supplier confirms a purchase order in SAP SNC. SAP SNC sends the confirmation to the customer back-end system. This XML message requires mapping
to IDocs when used with an SAP customer back-end system. A supplier can also use this message type to send a confirmation from his or her back-end system to SAP SNC.
If you, as a customer, use an ERP back-end system as of SAP R/3 4.6C, you can integrate the back-end system with the purchase order collaboration of SAP SNC using XML messages and IDocs, as follows:
Up to enhancement package 3 for SAP ERP 6.0, the ERP system sends and receives data via IDocs. We deliver mappings to XML messages that are compatible with the IDocs. The table below outlines the mappings for these IDocs and XML messages
Process |
Mapping of IDoc to XML |
||
|---|---|---|---|
Direction |
IDoc |
XML Message |
|
Send purchase order from SAP ERP to SAP SNC |
IDoc to XML |
Available as of SAP R/3 4.6C |
|
Send purchase order confirmation from SAP SNC to SAP ERP |
XML to IDoc |
Available as of SAP R/3 4.6C |
|
Send changed purchase order from SAP SNC to SAP ERP as part of approval process |
XML to IDoc |
Available as of SAP ERP 6.0 |
|
Send changed purchase order from SAP ERP to SAP SNC as part of approval process |
IDoc to XML |
Available as of SAP ERP 6.0 |
|
Send new or changed purchase order from SAP ERP to SAP SNC as part of Service Parts Management |
IDoc to XML |
Available as of SAP ERP 6.0 |
|
As of enhancement package 4 for SAP ERP 6.0, the ERP system can also send and receive data directly with the XML messages. In this case no IDocs are used and no mappings are needed. The following table outlines the XML messages that can be used:
Process |
XML Message |
|---|---|
Send purchase order from SAP ERP to SAP SNC |
|
Send purchase order confirmation from SAP SNC to SAP ERP |
Use IDoc/XML Mappings |
Send changed purchase order from SAP SNC to SAP ERP as part of approval process |
|
Send changed purchase order from SAP ERP to SAP SNC as part of approval process |
|
Send new or changed purchase order from SAP ERP to SAP SNC as part of Service Parts Management |
Use IDoc/XML Mappings |
Note
An SAP ERP system of enhancement package 4 for SAP ERP 6.0 can use either the IDocs that were available in lower releases or the XML messages that do not require mapping. We recommend that you use the new services for standard purchase order collaboration and contract manufacturing procurement.
You must specify which XML messages SAP SNC wants to send and receive. You use the PO_PURORDERPREQ_SEND
validation check to specify whether SAP SNC uses the outboundPurchaseOrderERPRequest_V1
XML message or the outbound ReplenishmentOrderNotification
XML
message. If the validation check is inactive, SAP SNC sends the IDoc-compatible ReplenishmentOrderNotification
XML messages. The validation check is inactive in the standard delivery.
You specify default process types for inbound XML messages in Customizing for Supply Network Collaboration
, under . In this activity, you set the Supplier Collaboration
process type for the following inbound XML message types:
ReplenishmentOrderNotification
This is also valid if you use the PurchaseOrderERPReplenishmentOrderCollaborationNotification
message type.
ReplenishmentOrderConfirmation
You only set the ReplenishmentOrderConfirmation
message type, if you want to receive purchase order confirmations directly from a supplier back-end system. For more information,
see Sending Confirmations from the Supplier System to SAP SNC.
You specify default process types for outbound XML messages in Customizing for Supply Network Collaboration
, under . In this activity, you set the Supplier Collaboration
process type for the following outbound XML message types:
ReplenishmentOrderNotification
This is also valid if you use the PurchaseOrderERPRequest_V1
message type.
ReplenishmentOrderConfirmation
If data is missing from a message received in SAP SNC, the system can fill this data based on various master data that is available. For more information about making settings for the completion of missing data, see Customizing for Supply Network Collaboration
,
under .