cancel
Showing results for 
Search instead for 
Did you mean: 

How to reprocess failed messages in Production?

Former Member
0 Kudos

Hi Guys,

We have 2 interfaces in production and they handle the real bank transactions.

1. Synchronus interface

2. Asynchronus - with BPM

If a transaction fails in XI for some reason , customer cannot resend the transaction and how can we reprocess the failed message from XI in production environment.

any help or suggestions would be appreciated.

Thanks,

Raj

Accepted Solutions (1)

Accepted Solutions (1)

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

1. synchronous always in the same way - from the calling application do it once more - this is how sync messages are always designed

if ont designed in this way ask the developer

2. async - it depends - maybe there was a key mapping and

you filled the mapping so you can restart it from SXI_MONITOR/RWB

maybe you need to cancel the message in XI and just resend it from the calling application

anyway I'd suggest asking the developer - what was his/her idea to restart them

Regards,

Michal Krawczyk

Former Member
0 Kudos

Hi Michal,

Thanks for the reply.

Raj

naseemallika14
Participant
0 Kudos

Hi Michal Krawczyk,

Could you please let me know , how to reprocess the locked payloads in SRT_MONI with the below screenshot marked in green.

is there any standard report to reprocess the payloads in the background.

Thanks.

Answers (3)

Answers (3)

dharamveer_gaur2
Active Contributor
0 Kudos

Hi

You can automatically resend failed message

/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

prateek
Active Contributor
0 Kudos

For the sync messages, as Michal said, it should be sent from the sender again as it is the production environment.

For second case, if your message gets failed in sxmb_moni, then you may restart it from there. If it is successful there, then check in RWB -> Message monitoring and resend the message from there.

Regards,

Prateek

SudhirT
Active Contributor
0 Kudos

For bpm scenario, can check in SWPR and restart the workflow after correcting the error if any.