Do you know what DAC SOShipLineSplit is for and what triggers its population (UOM issue)

Question

Do you know what DAC SOShipLineSplit is for and what triggers its population (UOM issue)?

I am trying to understand the difference between shipline and shiplinesplit.

As an example:

Product XX has a base unit of EA and Sales Unit of BOX (5 EA in a BOX). Units are marked as divisible. PO is EA (so we can’t change the base unit)
We raise a SO for XX: Quantity: 1 BOX
Shipping transaction shows XX. Quantity 1 BOX ,the sales unit.
On the Picklist form (report) the UOM is set as “=IsNull([SOShipLineSplit.UOM],[SOShipLine.UOM])”. [I think this is standard]

The picklist shows XX with Qty 5 EA to pick (not 1 BOX)

(as Shipline.UOM = BOX but ShipLineSplit.UOM = EA)

While this is the correct number of base units, we want the picker to send out an unopened box, not 5 individual products and we get mistakes when a shipper (manual picking) sends out 5 Boxes!

Questions

We did not and don’t expect to ship less than a box (so never 3 EA) so why is ShipLineSplit populated?
Can I safely update the report to show just ShipLine.UOM? In what scenarios would this be wrong?

Ed Goodman · Accepted Answer

​@simonForrestThe SOShipLineSplit DAC stores split quantities of a shipment line when a particular item is picked from multiple locations.The DAC is populated during picking when a picker changes the location and picks items from different locations.Hope this helps.Ed

bwhite49 · Answer

Also, the split table would display the lot/serial numbers associated with the shipment if there is more than one. The split table is ultimately where the picking/packing info is storedand the SOShipLine summarizes that info.

Sign up

Social Login

Login to the community

Social Login