topic Re: User Lock issue when processing IDOCS in Application Development and Automation Discussions

User Lock issue when processing IDOCS

kiran_k8 — Wed, 19 May 2010 18:14:14 GMT

Hi Folks,

We are pushing the data into SAP using IDOCS.During this process some IDOCS are getting failed due to User Lock on shipment header.Anyone here can share their experience in dealing with User Lock issues.

Thanks,

Kiran.

Re: User Lock issue when processing IDOCS

JL23 — Wed, 19 May 2010 19:33:38 GMT

only one can process a shipment at a time.

if you are in change mode in a shipment, then this shipment is locked for a second user to change anything.

Re: User Lock issue when processing IDOCS

kiran_k8 — Wed, 19 May 2010 19:43:08 GMT

Jurgen,

Ok.How can we avoid this user lock conflct when Processing IDOCS.

Thanks,

Kiran.

Re: User Lock issue when processing IDOCS

JL23 — Wed, 19 May 2010 19:56:11 GMT

process the IDOCs in the night.....

exchange info with the user.

ask the user what he does when he is locking the shipment (often users just use the change transaction instead of the display transaction and do not know what problems they cause with this approach)

explain Whatyour IDOC does and find a good timing together with your users

Re: User Lock issue when processing IDOCS

kiran_k8 — Wed, 19 May 2010 20:14:00 GMT

Thanks.So,will there be no solution programtically ? Did you came across any SAP Notes for such issues.

Kiran.

Re: User Lock issue when processing IDOCS

JL23 — Wed, 19 May 2010 20:24:19 GMT

no, there is nothing you can do with a program. There are OSS notes about this but nothing that would really help you (for material master updates there is an option for late locks)

Re: User Lock issue when processing IDOCS

kiran_k8 — Wed, 19 May 2010 20:26:39 GMT

Can you please share the OSS notes details so that I can take a look at the options.

Thanks,

Kiran.

Re: User Lock issue when processing IDOCS

Former Member — Thu, 20 May 2010 05:45:39 GMT

Kiran,

Only one can edit the document, it's standard fucntion. I think No note can resolve this. I can suggest you to run a back ground job very frequently ,which picks these status 51 IDOCs and reprocess. Report is :RBDMANi2

We can use Message class & error message number on selection screen, so that we can make sure that only those idocs which were failed due to Lock problem are taken by the job.

Reddy