Failed GI IDOCS due to locked plant data

[Former Member]

Dear experts,

we are implementing SAP 6.0 at my client. We have implemented an IDOC environment with a warehouse managemenet system of a logistics service provider. We processed a 1000 Goods Issue IDOCS (SHPCON_PGI) for exactly the same deliveries and about half of them fail with the following error msg: 'The plant data of the material 10066200 is locked by the user USER'. We have tried switching the IDOC processing from parallel to sequential but this did not yield any success...

Does anyone have experience with this and how to resolve this?

YOur input is much appreciated!

Kind regards, M

[Shiva_Ram · Accepted solution]

Can you check OSS Note 192423 - Delivery Processing Performance: Consulting of any help to resolve the issue you are facing?

Regards,

[Former Member · Accepted solution]

Thanks you Ram,

we have monitored system performance and there did not seem to ba nay problem with performance during our stress test (and when reading the OSS note, it seems this is pointing to improving the processing time of deliveries).

Is the issue described above a common problem and how can such a problem be solved?

Thank you, M

[Former Member]

Hi,

We have a similar environment with a similar error message that "Material is being blocked by user XXX". We have over come this error by placing a wait time of 15seconds between each delivery document.

We have a volume of 200-400documents a day and the program runs in the early hours as a background job. Hence we have no issues with the wait time which takes approximately 100minutes for a volume of 400docs.

Please try this and let me know if it works for you. We have recently gone line with this 45days back. Havent received any issues so far.

Regards,

Rohan Gudavalli

[Former Member]

Hi Rohan,

sounds reasonable, but our clients processes over 13000 orders each day... which makes your solution too slow I'm afraid

[Former Member]

Hi,

Since these transactions are instantenious, it usually takes only micro seconds to complete one transaction. Perhaps you can try with a wait time of 1 sec. Even this will take 3hrs and 45mins for 13000orders.

If you think this can be run in the mid-night, then it can be tried with 1 second or 2seconds.

Regards,

Rohan Gudavalli

[Lakshmipathi]

Apart from the suggested note, please also ensure that the material is not users by any other users in change mode (MM02) in which case also, system will give this error.  This you can check in SM12.

G. Lakshmipathi

[Former Member]

thanks, but that's clear and not causing the issues

Does anyone else have experience with this scenario?

Thanks, Mark

[Lakshmipathi]

Can you update here what is the error message number for this issue ?

G. Lakshmipathi

[Former Member]

Message no. M3897

[Lakshmipathi]

Check whether the following notes helps you to identify the root cause of the issue

1. Note 1231372 - Conversion of planned orders in APO leads to SYSFAIL queue
2. Note 1428411 - SYSFAIL queue for manual reservation with blocked material

G. Lakshmipathi