exception or error reprocessing in soap to rfc synchronous scenario

[former_member228109]

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

[azharshaikh · Accepted solution]

Hi Nikhil,

AFAIK - you can't restart Sync message in PI, it has to be resent from Sender.

You can suggest to resent after few hrs / days based on the frequency at which you create the Customer in your system

Regards,
Azhar

[former_member228109 · Accepted solution]

Hi Azhar ,

Thanks for your reply. But cant we do something using exceptions?

Regards ,

Nikhil Save

[iaki_vila · Accepted solution]

Hi Nikhil,

But cant we do something using exceptions?

For the exceptions inside the RFC you can do another RFC to wrap this with the Exception tab filled. Then in the RFC wrapper you can deal with this exception logically.

Other exceptions like timeout, the ECC is down and so on, as far as i know can't be controlled if you don't use a BPM.

Regards.

[RaghuVamseedhar]

I think it is not possible using middle-ware. Source system has to resend "failed messages/creations".

[sntamilselvan]

Hi Nikhil,

if you want to hold the response messages for particular time and then process to send them. means you can achieve by UDF mapping to the target node..Please see below thread,

Hope it helps!

[iaki_vila]

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.

[former_member228109]

Hello Inaki ,

Thanks. but i have read some where that we can reprocess error messages using BPM . Is it true ?

If yes , then how is it possible ?  If i will reprocess using bpm , then where would response go?

Regards ,

Nikhil save