Skip to Content

PI to Handle Exception thrown by Inbound RFC in a File to RFC async scenario

Hello Experts,

I am working on PO 7.5. Scenario is a File to RFC asynchronous scenario where in a certain case(Shipment in edit mode) RFC will be throwing custom exception. as 'Shipment Locked'. So in such cases PI messages show a HOLD status and Retries to call the RFC at Retry Interval of 10 min and no. of Retries is configured to be 5.As soon as the user gets out of edit mode, the RFC retry processes the message successfully.

But now we are getting an issue that in ECC transaction ST22 we have dumps with this exception and it seems they are due to the exception thrown isn't caught.

For this I tried to create an Inbound Service Interface with Request message from RFC and The Exception as Fault.

Then Operation mapping is done between the inbound and outbound service interface just normally without any impact of Fault.

But this has not shown any impact .and the exception is still thowing this dump in ECC.

Could anyone please guide me how should we be avoilding this Dump. Any suggestions to catch this exception or to better handle the same.

Add a comment
10|10000 characters needed characters exceeded

Related questions

0 Answers

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.