WM - Opportunistic Cross Docking - Split quantities to 1 each in TO

[mihailo_sundic]

Hello all.
Maybe the title isn't the most descriptive you have seen but the issue I'm having is a bit
complex to be put simply in a sentence. The best thing to do is to show it on an example.

Let's say I have inbound delivery with material A in qty of 10 pcs,
I also have outbound delivery for the same material for 10 pcs too.
These 10 pcs should be cross docked from IB to OB delivery, and it works
fine except for one detail...

When I create decisions in LXDCK and then go to TO creation I get the result:
TO created with 10 items of which:
Item 1: Material A - 1 pc.
Item 2: Material A - 1 pc.
...
Item 10: Material A - 1 pc.

I want it to be 1 item only (or more based on palletization data) with all 10 pcs on it.
It seems to split items for 1 pc at a time, that means if I have 500pcs of one item I
need to confirm 500 times no matter what palletization data I have defined (we use RF devices
so it's out of the question to confirm entire TO on PC by few clicks).

Why in the earth would I need to confirm the item 10 times if I can simply confirm all 10 pcs at once?

My palletization data for material A is 25 pcs on one pallet and logically the system should have created
only one item for 10 pcs in my Cross-Dck TO...

I've been looking around the Cross-docking customizing but no place to indicate this but I found one
very fishy piece of active code in C/D Add-Ins...

I'm not sure this is it but it might be so If anyone has experience with this problem feel free to help.
Why would I reset my palletization data to 1 if it exists?!

I could understand if not defined set as 1 but this makes no sense to me...

Anyway looking forward to your answers and thoughts, thanks in advance!

Regards,
Mihailo

[mihailo_sundic · Accepted solution]

Well once again I had to figure out the solution on my own.

I guess no-one ever faced this issue?! Or didn't get to solve it...

So, here's the solution if anyone has this issue in future.

* First thing, the code in the add-in shown below IS wrong (at least for my requirements).
Might be an over-sight in coding since this resets the palletizing data to 1.

If they have used IS INITIAL (without NOT) it would be OK and would make sense to me.

So alter this code: remove NOT or comment-out line 3 to disable its execution.

* Then, the other thing to do is in the inbound delivery - on item level, on tab "Batch split",

but this doesn't need to be entered for all the materials, check if you only need it for CWM+Batch
or only Batch managed etc.

Worked fine for me, no more problems with splitting of items to 1 each.

P.S. I'm not sure if this ABAP mod thing has to be done in all SAP versions but make sure
you check it on your system... and if it shows you the code I see then you need to change it.

P.P.S. It really seems lame to mark my own comment as correct but whatever...

Regards,
Mihailo

[mihailo_sundic]

OK, commenting the code in the fore-mentioned method didn't help.
As a matter of fact, it doesn't even get called in LTxx t-codes at all
(I've set a breakpoint in the active code).

So are there any cross-docking experts here that have experience in
LE-WM-CD? Anyone recalls a similar problem?

There's no common sense in the way cd TO creation behaves now,
if I have 1000 PCS there's no way it has to be confirmed 1 by 1.
I figure that there must be a standard way to set cross-docking to
make use of the palletization data...

Anyone with idea or solution?

Regards,
Mihailo