FAQ KB0399995
Email
Why is the Confirmation_Out message sent from external system not updated in Ariba Supplier Lifecycle and Performance (SLP)?
Question

Why is the Confirmation_Out message sent from external system not updated in Ariba Supplier Lifecycle and Performance (SLP)?

Answer

It is mandatory for the Confirmation_Out message sent from external system to have required  <InternalID> & <ReceiverInternalID> tag under <Supplier> </Suppler> tag in <BusinessPartner></BusinessPartner> section of the payload file inbound to SLP.

A sample Confirmation_Out message is provided in Additional Information section.

Additional Information

Based on the Request_In message received from SLP, external system should be able to create Business Partner and ERP vendor.

Sample  Confirmation_Out message with <InternalID> & <ReceiverInternalID> tag under <Supplier> </Suppler> tag in <BusinessPartner></BusinessPartner> section

<MessageHeader>

...

<SenderBusinessSystemId>XXX></SenderBusinessSystemId>  // SAP Ariba business systemID maintained in SM Admin > ERP integration > Integration Type

<ReceipientBusinessSystemId>XXX</ReceipientBusinessSystemId> // ERP business systemID mainatined in SM Admin > ERP integration > Integration Type 

</MessageHeader>

<BusinessPartner>
<UUID></UUID>
<InternalID>**SMvendorID**</InternalID>
<ReceiverUUID></ReceiverUUID>
<ReceiverInternalID>**BusinessPartnerID**</ReceiverInternalID>
<Supplier>
<InternalID>**SMvendorID**</InternalID>
<ReceiverInternalID>**ERPVendorID**</ReceiverInternalID>
</Supplier>
</BusinessPartner>

(OR)

The supplier id coming in ReceiverInternalID section might be already mapped to different supplier in SLP and it's already in integrated status.

Why is the Confirmation_Out message sent from external system not updated in Ariba Supplier Lifecycle and Performance (SLP)?.png347.15 KB

Attached File
Why is the Confirmation_Out message sent from external system not updated in Ariba Supplier Lifecycle and Performance (SLP).png346.68 KB

Applies To

Supplier Lifecycle & Performance

Terms of Use  |  Copyright  |  Security Disclosure  |  Privacy