![]() Step 2: Go to Transaction code SXMB_MONI. If we observe the screen below, we are not able to see the payload for Receiver Interface.įollow up the below steps which helped me to analyse the Proxy communication. After all this analysis, I got to know that the ABAP proxy is not triggered from XI.įollowing screen shows SXMB_MONI of XI serverĪfter double clicking the above message following screen appears. Now this gets me mind boggling and get to debug my ABAP code which has update query to update DB table in R/3. Let me explain a scenario where my status in XI Monitor is a chequered flag but when I check my custom table the data is still not updated. Inspite of chequered flag in XI, proxy need not be triggered and with respect to this case we cannot see any log in the SXMB_MONI of XI Server, therefore it is very difficult to check the status of the Interface based on the processed XML messages in the XI server. The idea behind this blog is to monitor the processed XML messages for receiver ABAP proxy. Here design and configuration part is been ignored. ![]() Flat file from Legacy system is sent to XI via File Adapter and Mapping is executed according to the business rules and sent to R/3 system via ABAP proxy which in turn updates the custom table. The purpose of this interface to update some custom tables in R/3 system based on data provided in Legacy system in flat file format. A use case for Legacy System->XI->R/3 System.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |