I am not seeing the Purchase Order (PO) number in the audit logs page in Ariba Sourcing after the Request for Quotation (RFQ) was awarded and the PO was created in SAP ERP.

The entire scenario for the RFQ initiated in ERP is as below:

1. An RFQ is created in ERP transaction ME41.
2. At this point, the document type QuoteRequest is sent from ERP to SAP Integration Suite, managed gateway for spend management and SAP Business Network. After document transformation, the same is sent to Ariba Sourcing.
3. After awarding is done in Ariba Sourcing, a QuoteMessageOrder (for PO) or QuoteMessageContract (for contract) document type is sent back from Ariba to SAP Integration Suite, managed gateway for spend management and SAP Business Network and after document transformation, it is sent to SAP ERP.
4. A Purchase Order is created and the interface for the contract response sends a ContractStatusUpdateRequest to SAP Integration Suite, managed gateway for spend management and SAP Business Network that is routed to Ariba. This payload contains the event update that is sent to Sourcing.

The Purchase Order (PO) number is not visible in the Sourcing event's audit logs because the confirmation message, ContractStatusUpdateRequest, is not being successfully sent from SAP ERP back to Ariba Sourcing after the PO is created. This failure can be due to several reasons:

• The interface for the response message is not published in SAP ERP.
• There are technical errors (e.g., authorization issues) preventing the message from being sent, which can be checked in transactions SRT_MONI or SLG1.
• The message is sent, but it is missing the Sourcing event ID, which is necessary to link the update to the correct event.
• Ariba Sourcing is not configured to accept and process the confirmation message from an external system.

If you are facing issues with this scenario, please refer to the below points:

If the ContractStatusUpdateRequest is not being triggered after ERP receives the QuoteMessageOrder:

1. Make sure that the response interface is published. Go to transaction SPRO > SAP Reference IMG.
2. Click Integration with Other SAP Components > SAP Integration Suite, managed gateway for spend management and SAP Business Network > SAP Ariba Strategic Sourcing Suite Integration > General Settings > Setup the Interface > Configure Connections to send messages.
3. On the Outbound messages section, make sure Ariba Contract Response was checked and published.
4. If the interface was published, make sure you are not having errors in the SRT_MONI transaction that are preventing the response from being sent to SAP Integration Suite, managed gateway for spend management and SAP Business Network (for example, 401 unauthorized errors).
5. If you are not having errors in transaction SRT_MONI, check for errors in transaction SLG1 as well.

If the ContractStatusUpdateRequest is being triggered (from ERP to Ariba) after QuoteMessageOrder / QuoteMessageContract was sent to ERP:

1. SAP Integration Suite, managed gateway for spend management and SAP Business Network > Transaction Tracker and search for the ConctractStatusUpdateRequest message.
2. Download the after-mapping payload and check if the Sourcing event ID is populated in the payload.
3. If this is not populated and if you are using a SP version older than SP5, check the below SAP Notes:
   • 2676629 - An error “No Contract Workspace found with the contract ID AXXXX.” occurred on SAP Ariba Sourcing when the SAP ERP sent the ContractStatusUpdateRequest message after creation of the purchase order on the SAP ERP system.
   • 2849390 - Contract ID was not getting updated in SAP ERP

If the ContractStatusUpdateRequest is triggered and you are still not seeing the event in Sourcing:

1. Check with the Sourcing team if the parameter is enabled: Confirmation Message from External System. Refer to Why is the confirmation message for a Quote message not updating the Sourcing project?
2. Check if the queue is registered on the ERP side. See article: 1915747 - PurchasingContractSRMReplicationConfirmation_Out or PurchasingContractERPConfirmation_Out is not triggered.

• This document flow is described with pictures in the SAP Integration Suite, managed gateway for spend management and SAP Business Network Overview guide in section 4.6.2 SAP Ariba Sourcing - request for Quotation.
• 2676629 - An error “No Contract Workspace found with the contract ID AXXXX.” occurred on SAP Ariba Sourcing when the SAP ERP sent the ContractStatusUpdateRequest message after creation of the purchase order on the SAP ERP system.
• 2849390 - Contract ID was not getting updated in SAP ERP
• Why is the confirmation message for a Quote message not updating the Sourcing project?
• 1915747 - PurchasingContractSRMReplicationConfirmation_Out or PurchasingContractERPConfirmation_Out is not triggered.

SAP Integration Suite Managed Gateway > Managed Gateway for Sourcing Integration