How to capture the Network logs during a PunchOut session to view the data sent by the Supplier.

[Niraj_Panchal]

Reading time: 2 min

Issue Description :

At times when a user does a punchout session and exports the cart to our SAP Ariba Buying solution we often see below error msg.

This is because the supplier might be sending a Non-standard UOM(or commodity) which is not defined in the customer’s system.

In such cases, we would want to know what data the Supplier is sending so we can map its value to our Internal UOM defined in our system.

However, there is no direct method to get the payload and look at the data sent from the Supplier’s system (External System).

---------------------------------------------------------------------------------------------------------------------------------------------

In this Blog I will explain you how to retrieve the PunchOutOrderMessage (don’t worry just a technical term to describe the shopping cart) and look for the data sent.

Resolution :

Start as usual by punching in into the Supplier’s web shop and once you are ready with your cart, before sending it back to the Ariba site start the inspect element.

Right click -> Click on Inspect. The Inspect window opens up.

Click on the “Network tab” and enter method: POST. (HTTPS uses the POST method to send the data to Ariba to create the PR.Our aim is to get hold of this)

Remember to check the preserve log checkbox (very imp otherwise you may lose the request as the logs build up)

Once this setup is ready you can send the cart to Ariba. As you do the check out the inspect tool will keep on logging the entries.

The one that we are looking for is “punchout?client=”. The PunchOutOrderMessage is present in this request and has the payload(cXML) sent from supplier webshop. Click to open.

Check under Payload-> Form data. Here is our data.

Sometimes you might see a base64 encoded version of the payload like below. In that case you can use any decoder tool to decode the xml.

Below is one such Encoder/Decoder tool available online.

To improve readability you can further copy paste the decoded text and do a pretty printer in notepad++ (often not required).

Here the supplier is sending UOM as RL which is not a std UOM in the customer’s system.

So we have to map this to our internal UOM using the UnitOfMeasureMap.csv file.

Upload the file using the below import task.

Delete the existing cart and Redo the punch out. The error should be gone now..!

That's it, in this blog you have learnt how to retrive the newtwork logs and resolve a common issue.

-----------------------------------------------------------------------------------------------------------------------------------------------

All efforts has been made to keep the content as simple as possible so the newbies can understand as well.

Please feel free to drop your valuable feedback, any improvements, suggestions or corrections which would help the community.

Thank you so much!