Hello Experts ,
I have a requirement in which third party will send data to sap using soap to rfc synchronous scenario. They will be going to send data for customer creation. So if costumer is created in sap , then we are sending message as 'customer created' and if not then 'customer not created'. In both the cases it is in successful state in PI.
Now what they are asking is , if response is 'customer not created' then it should stuck in error state in PI and it should be again reprocessed manually next day. How it can be achieved? Is it possible to keep it in error state and reprocess? Can we use exceptions and fault messages?
Thanks and regards ,
Nikhil Save
Hi Nikhil,
As Azhar said the synchronous messages can't be restarted, and this is logical, think you are using your browser and you call any URL and this fails, it has no sense that X days later the URL give you a response to your browser.
When I use RFC's in the receiver side, i usually use an export variable type BAPIRETURN or BAPIRET2 that it contains the success of the call. Personally, i'd rather having a tag in the WSDL of the response in which is pointed out this result.
Hope this helps.
Regards.
I think it is not possible using middle-ware. Source system has to resend "failed messages/creations".
Add a comment