LSC goods issue and picking

Purpose

This page describes LSC logic for goods issue, warehouse picking, package selection, and shipping-relevant checks.

Process flow

1. Create shipment document.
2. Create warehouse pick.
3. Build shipping packaging structure.
4. Create and register package activities.
5. Post final shipment.

graph LR;

%% Nodes
A["Take over<br/>customer order"]
B["Create warehouse<br/>pick"]
C["Generate FIFO/FEFO<br/>proposal"]
D{"Manual adjustment<br/>needed?"}
E["Adjust pick<br/>lines"]
F["Remove packages<br/>from warehouse"]
G["Packages<br/>picked"]
H["Build shipping<br/>packaging structure"]
I{"Customer checks<br/>required?"}
J["Check labels,<br/>RFID/barcode, weight"]
K["Post shipment"]
L["Hand over to<br/>carrier"]

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==> D
D ==>|Yes| E
D ==>|No| F
E ==> F
F ==> G
G ==> H
H ==> I
I ==>|Yes| J
I ==>|No| K
J ==> K
K ==> L

%% Classes
class A btProcessTitle
class B,C,D,E,F,G,H,I,J,K,L btProcessActive

FIFO/FEFO and tolerance control

Proposal logic prioritizes package units based on setup.

Important:

• date logic must be maintained in master-data process,
• exchange tolerance must be used in controlled way,
• manual swap actions require clear business reason.

Manual assignment in quantity gaps

If available package quantity does not fully cover demand:

1. review open activities,
2. adjust Assigned Packaging Quantity deliberately,
3. recreate activities,
4. validate shipping structure again.

Customer and label checks

Depending on customer process, additional checks are required before posting, for example VDA label check or RFLT-ID validation.

Business rule:

• Open mandatory check blocks goods-issue posting.

Checkpoints before posting

• final shipping structure is complete,
• no conflicting activity status,
• mandatory checks are complete,
• physical state matches system state.