There's a Purchase Requisition (PR) that generates a Purchase Order (PO) after fully approved which become stuck in "Ordering" status after a change adding items which is sent by PurchaseOrderChangeAsyncResponsePullRequest document failing with CIG-PLT-04641 error in the Managed Gateway for Spend&Network portal.

This issue can also be found by looking into the Validator.dat file, which in this scenario contains: The content of element 'urn:item' is not complete. One of '{"urn:Ariba:Buyer:vsap":NumberInCollection, "urn:Ariba:Buyer:vsap":ServiceMapKey, "urn:Ariba:Buyer:vsap":custom}' is expected.

Since the ERP and P2P have different representations for the items in a particular PO, we need to correctly correlate that whenever we do a change, this is why the PurchaseOrderChangeAsyncresponsePullRequest is created. Managed Gateway for Spend&Network transaction tracker have a built-in syntax validator which checks for each item if they are accordingly filled up. In this case, the error CIG-PLT-04641 is triggered because the ERP code fails to add the <AribaItemID> field accordingly.

In order to solve this issue for new documents, you need to apply SAP Note 3050686 - SAP ERP or SAP S/4HANA was creating duplicate line items when a new line item in change purchase orders (POs) was retriggered from SAP Integration Suite, managed gateway for spend management and SAP Business Network.

In order to correct the older ones, you can cancel the affected orders, creating new ones in replacement after applying the SAP Note, or you can follow the steps below for the affected documents individually:

1. Opening the reference table:

1. Go into Managed Gateway for Spend&Network > Transaction Tracker and search for the affected document.
2. Into the Transaction Number column click on the PurchaseOrderChangeAsyncResponsePullRequest document link.
3. Go into the Activity tab and download the payload with the Document Stage "PreProcess".
4. Access the ERP system and go into transaction SE16.
5. Into Table Name field paste ARBCIG_POHISTORY and execute it.
6. Into the EBELN field paste the <SAPDocumentId> value from the PreProcess payload you downloaded and execute it

Now you are facing the ARBCIG_POHISTORY table for the affected PO.

2. Correcting the payload:

1. Open the payload in any text/code editor.
2. For each <Item> make sure that the <SAPItemId> correlates with the <AribaItemID> presented in the table by adding the value of the table as a new line in the payload below the <SAPItemId>: <AribaItemID>XXX</AribaItemID>. See the example below:

3. After correcting and keep sure that each item have its fields correctly correlated, save this manually edited document as a ".xml" file.

3. Posting the corrected payload to CIG:

1. Open a new ERP window into transaction SPROXY.
2. Click into the Open icon () and then click into External Key.
3. In the field Name paste ERPToAribaBuyerResponse_Async_Out and click into the search button in the end of this field () and click into the Continue button, or press ENTER.
4. Do the same for the new window, and now you will notice that the Namespace field is also filled up.
5. Click in Display and then click into Test () or just press F8 and Execute.
6. Now, in this new window click into Load File () or press F5 and locate the edited .xml you created manually and Execute.
7. Go into Extras > Trigger COMMIT WORK.

Now you had successfully sent an edited Payload through Managed Gateway for Spend&Network. You can see it in the Transaction Tracker, and if everything was done correctly, now the transaction is completed.

Into the SE16 transaction, for the ARBCIG_POHISTORY table, the information there stands for:

The EBELN field represents the number of the Purchase Order in the ERP.
The EBELP field represents the item number in the ERP.
The ITEMONREQ field represents the AribaItemId is the item number in P2P.
The REQ_ID field represents the PR which this document is originated from.
The ERPORDERID field represents the Document ID number in Managed Gateway for Spend&Network transaction tracker.

SAP Integration Suite Managed Gateway > Managed Gateway for Business Network SCC > Managed Gateway for Buyer Business Network SCC