SAP MEINT message retry mechanism

[Former Member]

Hi Experts,

I am stuck up with a MEINT message retry behavior in a client's production system.

If my understanding is right, messages in MEINT integration queue are retried only for connectivity failures during processing and not the data errors. Data errors have to be retried manually. Correct me if i am wrong.

If the above understanding is right, please help me on the following issues.

Prod system details

1. MEINT is on 12.2.3 Build(182)
2. Production order Messages to MEINT integration queue are posted directly from a custom MII application and not from ECC.
3. retry limit is configured for each message.

Behaviour :

What i observed is that whenever the messages are queued into the integration queue, the attempts/retry limit column is displayed as 0/1 (this is OK) and then followed by 1/1 and sometimes even 2/1. When the processing is not complete and the status is queued how this can show 1/1 or 2/1?

At the end of message processing the result sometimes displayed as 2/1. this means the message is attempted twice right. or this has a different meaning?

Typically on every refresh of queue monitor for a production order message, we observed the following for some orders

Order in

Attempts/Retry limit                      Status

0/1                                              queued

1/1                                              queued

2/1                                              queued

2/1                                              success or failed

2/1                                              success if its failed previously

Is this behaviour right. and this is happening only for few orders typically in a particular timeframe where we also noticed that scheduler is in the running state for a long time. This behaviour is not consistent as well and happening randomly.

Also we noticed that the outbound messages like yield confirmations are automatically retried even for data related error and sometimes not and we have to retry it manually. can anyone throw light on the above two issues.

Thanks

Mahalakshmi Syamsunder.

[Former Member · Accepted solution]

To address why it retries sometimes and at other times requires manual retry, in the workflow there is a ResponseXSLT step.  You will need to create a custom XSLT to handle the errors you get back from ECC or the corresponding system.  If the error code is classified as a SYS_ERROR it will retry, if it classified as an APP_ERROR it will not.  The standard Response XSLT has an example for error code 469 or when the connection to ECC fails.  Any other error will result in SYS_ERROR thus no retry.

You can see the error code in the response XSLT in the Document Trace Response.

Does your code which inserts the transaction into SAPMEINT utilize the standard Enqueuer logic or is it custom?  If you do, you may have the retry limit hard coded rather than looking at the workflow to identify it as the standard Enqueuer does.  We had a similar issue utilizing a web service.

We also see the 2/1 sometimes if there is more than one dispatcher running or if there is still one running in the background which you can not see.  For example, if you stop the dispatcher mid-job it will continue running in the background until all of the records are processed and because there is no indicator in the MEINT database to identify whether a record is currently being processed if you restart the dispatcher it wil process the record again since the previous job has not updated it yet.

[Former Member · Accepted solution]

Hi,

Thanks for all your replies. I will suggest for a patch upgrade.

Thanks

S.Mahalakshmi