Recently we had a situation where a RFC call message call looked successful in PI but the document on ERP wasn’t side wasn’t getting created. We expected process messages to be created on ERP side but when we checked documents in CO54, we couldn’t see any document.
Message monitor on ERP for process messages.
There is a difference of 10 hrs between my timezone ( AEST ) and system time. Hence PI logs indicate time as 18:38 and system time to check for messages is between 08:00 and 09:00.
As the messages were EO ( exactly once ), there is no response captured in BAPI return messages causing PI messages to be successful even though there are errors on ERP side. RFC adapter is able to invoke the BAPI successfully on ERP side and hence PI logs indicate message successfully processed.
Some function modules have logging enabled so that in case of errors, application log can be reviewed. However, in this case there is no application log being written.
We then tried to change the quality of service to BE so that the response can be captured.
This was somewhat fruitful as now we can see there are errors on the BAPI call.
However, the message is still not very useful as all we get from is the message is that an error has happened, looking at the message id / message number.
So we were looking for a way to debug RFC adapter calls.
In past ,we had to use transaction SRDEBUG to activate debugging for another user.
Now it’s much easier as it can be done directly in the ABAP editor.
1. Find the user in the RFC communication channel.
2. Go to the function module on ERP side.
3. From SAPGUI Menu, chose Utilities – Settings ->Debugging . Give the user in the RFC comm channel used for RFC call.
The user needs to be a dialog user when this step is done.
Once the break-point is set, we can put back the user type to system user type.
Now, the message can be sent.
Reference : Note 1766428 Remote ABAP debugging: changed behavior