2012 Oct 16 1:44 PM
Hi Experts,
Inbound Order response Idocs are posted for a single PO. Say for example 1000 idocs are posted @ 1 shot. I have scheduled a background job to process the Inbound idocs for every 5 mins. Now the issue is in the second run of the Job we are getting PO lock issue as the first run is updating the same PO. What are the possible ways to overcome this? We introduced serialization concept and the middleware posts an unique serial number in the idocs. Is there any way to schedule the job in such a way that the second run should be initiated only when the first run of job is completed ? Do you think this will solve the issue ?
Please suggest.
Hi Experts,
Inbound Order response Idocs are posted for a single PO. Say for example 1000 idocs are posted @ 1 shot. I have scheduled a background job to process the Inbound idocs for every 5 mins. Now the issue is in the second run of the Job we are getting PO lock issue as the first run is updating the same PO. What are the possible ways to overcome this? We introduced serialization concept and the middleware posts an unique serial number in the idocs. Is there any way to schedule the job in such a way that the second run should be initiated only when the first run of job is completed ? Do you think this will solve the issue ?
Please suggest.
2012 Oct 17 7:45 AM
Hi Hemavathi,
In WE42 (process codes for inbound Idocs), double click on the process code, system takes you to detailed screen in which identification module(FM or task etc..) is mentioned. click on ALE table button next to Identification input screen. On the screen appeared, change 'Maximum Number of Repeats' value to 5 or 10.
Regards,
SG.