Delay processing of inbound IDoc

[Former Member]

We're having an issue while processing an inbound ORDRSP IDoc. Contracts are used to created purchase orders. The IDocs arrive in the R/3 system so fast, that the error "User XXXX already processing Contract XXXX" is displayed almost all of the time.

We already tried scheduling the report RBDAPP01 to sequentially process the IDocs, but the error still remains: each time the first IDoc in the row goes OK, and the rest results in error.

Does anyone has an idea on how to be able to process all these IDocs succesfully?

[Former Member]

Hi Iddo,

Iam having the same category of the Issue stated by you.Will you pl share how you have solved it?

Regards

KRISHNAN

[Former Member]

I solved it with an Integration Process, a transport acknowledgement and a refresh job. Look at thread https://forums.sdn.sap.com/click.jspa?searchID=-1&messageID=5914148 for more details.

Edited by: Iddo Rijsdijk on Oct 21, 2008 12:42 PM

wrong URL

[Former Member]

Hi iddo

You Can try processing the idoc in using transaction BD87. you would be able to figure out where the error is.

We can increse the no of work processes in transaction RZ04.

To see the number of work processes assigned and the status of each and every WP in transaction SM50.

Regards

Abhishek

[Former Member]

The error occurs only when multiple IDocs are received at once that use the same contract number, so debugging the IDoc processing didn't result in a solution.

The number of workprocesses isn't the issue as well, because of the sequential processing. The error message would have been different in that case.

[Former Member]

I now found a way to delay the IDocs sent to R/3 by waiting on a transport acknowledgement (BPM).

One thing still bothers me, and that is the long timeout that occurs sometimes before a transport acknowledgement is received and the next IDoc can be sent. This timeout can sometimes be more than 8 minutes, and sometimes it's just a matter of seconds. How can I improve the performance?