How to debug A2A inbound service call from SAP TM in SAP S4
It is choice to utilize outer SAP Brim Solutions Transportation Management (SAP TM) and to incorporate with two different SAP S4 frameworks with the concentration at Logistics, Controlling, Finance.
SAP TM has an assistance situated design. Most of interchanges between TM with different frameworks happen through XML messages.
Expecting, all BASIS activities are completed and the association is laid out, we can test and examine the connection point.
Choosing a situation
For instance, we will audit the A2A Inbound assistance TransportationOrderSUITEInvoicingPreparationRequest_In Receive make or change demands for provider solicitations in SAP ERP which addresses Freight Settlement
This cycle comprises of a few stages:
Send Freight Settlement Request to make Supplier Invoice: ext. SAP TM demands the production of accumulations ( formation of a help buy request and administration section sheets) in SAP S4. It implies the ). SAP S4 sends an update to ext. SAP TM when the comparing provider receipt has been made.
Get Freight Settlement Confirmation: ext. SAP TM gets the affirmation from SAP S4 and updates the comparing cargo settlement archive.
In our model, SAP S4 is the framework holding up the assistance call from SAP TM side, when a call is executed, a message ought to be noticeable with the exchange SRT_MONI - WS Message Monitor (~ two applications discuss straightforwardly with each other without the utilization of a PI server ).
The handling status Transfered_to_Ext_App prompts that the first solicitation couldn't be handled effectively and the reaction about the blunder was moved back to ext. SAP TM.
Then again, on the off chance that the XML message causes a short dump, open the short dump with the exchange ST22 and quest for a variable named ID_XI_GUID. This variable will hold the MESSAGE ID for the XML message.
The point will be to comprehend which information from the solicitation and with which steps are handled, which BADI and improvement focuses are accessible to satisfy client prerequisites.
Finding a web-administration to rehash the solicitation
Utilizing the information from the solicitation
Beneficiary connection point namespace: http://sap.com/xi/APPL/Global2
Collector interface activity: TransportationOrderSUITEInvoicingPreparationRequest_In
Comments
Post a Comment