cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Inbound Proxy debugging

Former Member
0 Likes
7,558

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

View Entire Topic
r_s_kulkarni11
Participant
0 Likes

Hi Rebecca,

After executing the proxy, you can use the commit work option which will update the required tables.

I think you are not supposed to get the messages in SXMB_MONI as execution of inbound proxy will directly process through the program, you get the message displayed in MONI of ECC when you actually receive the data into ECC from PI system.

Also you can use the testing style as debugging >> debugg method after selecting the proxy test button.

For commiting the work you can go to Extras>>commit work.