|
Confirming End Point setup in Sourcing/AN for Contracts integration using the cXML method.
SAP Business Network (AN):
As an example scenario, we're creating two End Points in the SAP Business Network.
EndPointExampleA (AN to ERP)
EndPointExampleB (AN to Ariba Sourcing/Contracts)
Document Routing:
Contract Request: EndPointExampleA
Contract Status Update Request: EndPointExampleB
SAP Ariba Sourcing:
Create EndPoint as "External System" in Master Data Manager.
Set up EndPointExampleB in the SAP Ariba realm:
End Points were configured incorrectly, or not at all.
This article is useful as a troubleshooting step if you need a breakdown of end-to-end Contracts Integration set up in the SAP Business Network and/or Ariba Sourcing (Contracts) using the cXML Method. Additionally, this is a necessary troubleshooting step if you're attempting to send the Contract Line Item Document (CLID) to an External System and you're receiving an error message.
Check the History tab of the Contract Workspace if you do receive an error. Some error messages will point out missing data that can easily be resolved by amending the Contract Workspace and adding the required information.
Example of a common integration error that this article may help resolve:
There was an error while sending the contract to the external system. Please contact the administrator.
Core Procurement > Core Administration > Application Integration (between Buying & Sourcing)
SAP Business Network for Procurement & Supply Chain
Strategic Sourcing > Strategic Sourcing - Application Integration (BUY & SRC)