Delayed Delivery Update (LX47)

[Former Member]

Hi

Need some help understanding an issue that I am having with txn LX47.

We are using STO's and OBD's to move stock between storage locations at the same plant. We are using WM under the main storage location and IM at the others. Reservations are created against the IM Slocs with the WM Sloc as the source. An Sloc to Sloc STO is then created and an associated OBD. We then, via VL06O, create TO's for mixed deliveries and have configured the delayed delivery update within the shipping control to "3 Delayed update at each confirmation of a TO item". We are using staging areas within the warehouse and are set for 2 step confirmation.

Process

1. Create reservations
2. Create STO
3. Create OBD
4. Create Group TO (Mixed Deliveries)
5. Pick TO items (Step 1)
6. Confirm TO into Staging Area (Step 2)
7. Create Shipment
8. Process Shipment (PGI from WM Sloc and GR into IM Sloc)
9. GI from IM Sloc against reservation.

All works well except for line 6 (Step 2 TO Confirmation) and only then, when the final TO line item is confirmed. On a 3 lined TO, there is no problem when I confirm lines 1 & 2 but as soon as I confirm the final line, the TO fails to update the OBD and the TO sits in LX47 waiting to be cleared.

I have tried adjusting the late exclusive block waiting time (OMJI) up to the max 999 and tried the other delayed update options 1 & 2, but still this keeps happening.

Anyone got any ideas as to why it only 'locks' when confirming the last TO item and what I can do the resolve ?

Thanks in advance

Cheers

[former_member245890 · Accepted solution]

Did you check the OSS note :

664316 - Tips for the delayed delivery update for TO confirmation

http://service.sap.com/sap/support/notes/664316

I faced the same issue on my previous project, could not find the reason.

Then we scheduled a background job for (RLLX4700) LX47 according to SAP's suggestion on this note.

Hope this helps.

Alper

[Former Member · Accepted solution]

Thanks Alper

Had thought of this but due to the Business process, it would need to run every 10secs to make it operationally viable .

It would be quicker for the operative to action LX47 manually rather than wait for the background program to run. Having said that, it might just be the only option.

What I'm trying to understand though, is why it only 'locks' when confirming the final line item

Cheers

[former_member245890 · Accepted solution]

Hi

Try to debug function module  L_TO_PASS_DN and  L_TO_PASS_DN_INT which are called in include LL03TF59. They are called when transfer order item is confirmed. The FMs update outbound deliveries. Maybe you can see why it is not updated.

Alper

[Former Member · Accepted solution]

Hi

Will give it a go and let you know.

Thanks

[Former Member · Accepted solution]

Update

Problem lies in custom RF program used so have set up as a background job as an interim solution.

Thanks for your help

Cheers