Inbound Proxy debugging

[Former Member]

Dear All,

I am working on File -> PI -> ECC 6.0 (ABAP Inbound Proxy). We wrote a program in ECC side which includes calling the class and its method of the interface.I am able to successfully process the message in SAP PI and ECC as well i.e. I can see successfully processed message in PI and ECC. Now the problem is that we found that its not updating the table.

To debug the inbound proxy, I went to Tx SPROXY and went to the particular interface, Menu -> Test -> Pop up Select the option -> Generate Request Template and then uploaded the correct payload.

1. After executing and performing Execute Committing , I am not able to see any PI messages in the ECC integration engine (Tx SXMB_MONI).

2. We have called the interface class and its method (Export parameter ) in the report itself not in Tx SE24 ( not inside this method ).
   I tried to put the break point at Class in the report and while executing the test payload from Tx SPROXY , its not being called.
   Do help in this issue.

Regards

[Former Member · Accepted solution]

Hi Rebecca,

1. After executing and performing Execute Committing , I am not able to see any PI messages in the ECC integration engine (Tx SXMB_MONI).

You should to enable the message monitoring in your ECC endpoint. Check Michal Krawczyk's blog http://scn.sap.com/community/pi-and-soa-middleware/blog/2005/05/10/xi-i-cannot-see-some-of-my-messag...

Another way to debug it's to persist the inbound data. You can create Z tables which store the data and in this way to check if the incoming data is correct. Later you can test the proxy code followin Raj's suggestion.

Regards.