Locking errors in WM (TX LT06)

[Susan R Keohan]

First off, thanks Karen and Raf,
 
There were some config changes required on the WM side, which eliminated the
need to use temporary storage locations and transaction LT06, but we still
encountered locking errors using transaction LT01, when the material was moved
to a real, physical location.
 
We were able to solve this locking problem by enabling the event queue to manage
the start of the conflicting workflows.  Hooray for the Event Queue!
 
Thanks
Sue
Quoting "Bormans, Raf" <raf.bormans at thevisionweb.be>:
 
> Hi Susan,
>
> If I interpreted your problem correctly, it seems that you use a WM storage
> type, with only one generic "dummy" bin.
>
> In that case, you would not like to have SAP do any locking at all on the
> storage bin.
>
> Note that standard SAP does not lock a bin when the storage type
> configuration complies ALL of these conditions (check T331, or through
> customising):
> - Put away strategy: Manual stock placement (blank) OR Open storage (C) OR
> Dynamic coordinate quant number (Q)
> - Indicator: mixed storage: Mixed storage without limitations (X)
> - Capacity Check Method: not used
> - Set blocking indicator at time of placement into storage: NOT set
>
> You might adapt your configuration to comply to this (without suggesting to
> hack the system, the related code to this you will find in ABAP report
> LL03AF9H).
>
> If this approach is not applicable, the temporary lock approach from Karen
> should solve the problem, but will of course generate delays in your
> processing, so in meantime WM stock will not be available).
>
> Regards,
>
> Raf Bormans
>
> The Vision Web Belgium NV
> E-mail: raf.bormans at thevisionweb.be
> URL:    http://www.thevisionweb.be
>
>
> -----Original Message-----
>> From: Susan R Keohan [mailto:skeohan at mit.edu]
> Sent: Tuesday, 18 March 2003 15:12
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Locking errors in WM (TX LT06)
>
>
> Hi Workflow-ers,
>
> We are on 4.6c, Basis Support Package 39 for 4.6C.
>
> I have written a workflow which does a goods movement (via BAPI) and
> performs a
> BDC for the subsequent creation of a transfer order, via LT06.  This
> workflow
> completes successfully when called once or twice, or multiple times in
> sequence.
>
> The problem arises when multiple instances (say 10 or 20) of this workflow
> are
> kicked off simultaneously.  Then we encounter error L3 145 (storage location
> is
> locked).  (Business note: All these goods movements and transfer orders use
> the
> same storage location) OSS refers to a correction for this error, but we are
> past that support pack.  I have opened a message with SAP on the locking
> error,
> but...
>
> To me this is ridiculous, because we really don't do 'Warehouse Management'
> here, and I am sure that there are lots of real 'Warehouse Management'
> implementations out there that do the real stuff.
>
> Is there a better way to get around this error ?  We have tried trapping for
> the
> specific error number, and then re-trying the BDC, but to no avail.
>
> Thanks in advance,
> Sue
>