Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Idoc error

Former Member
0 Likes
501

Hi

For each delivery two return Idocs are generated from middleware u2013 One for Picking and another for PGI. Picking Idoc successfully does the picking in delivery but PGI Idoc fails and hence PGI is not done in delivery.

On analysis I notice that for two deliveries having same material when two PGI Idocs- one for each delivery are generated within a span of one second then both PGI Idocs fall in error. This is because of the reason that at a time only one Idoc can activate a material. I think this is standard SAP.

Is there a way to make the second PGI Idoc to wait till first Idoc finishes its job of PGI?

Please suggest

1 REPLY 1
Read only

Former Member
0 Likes
359

Chari,

Record locking is very common in iDoc processing, especially with Materials. Generally one would schedule a frequent job to reprocess such iDocs, via RBDMANI2. We have such a job running every 2 minutes.

The only other option I can think of, if you prefer not to do that, is to sett he WE20 Inbound Partner Profile to 'Trigger by background program' for the Message Type, then schedule RBDAPP01 to run with a pack. size of 1. I'm not even sure if that would work, and I doubt it would give you much in the way of benefits over the RBDMANI2 option I mentioned above.

Cheers, Paul.