Cross-docking and project pegging
If project pegging is implemented, a cross-dock order is based on a project peg line of an outbound order line. A cross-dock order can be created for each project peg line present for an outbound order line. Outbound project peg lines are maintained in the Outbound Order Line Peg Distribution (whinh2690m000) session.
Cross-dock order lines are based on inbound project peg lines. Inbound project peg lines are maintained in theInbound Order Line Peg Distribution (whinh2680m000) session.
If automatic creation of cross-dock orders is implemented, a cross-dock order is generated when a project peg line is added to an outbound order line in case of inventory shortage. A cross-dock order is manually created by selecting a project peg line in the Cross-dock Orders (whinh6100m000) session.
When a cross-dock order is created, the project, element and activity of the outbound project peg line are used as matching criteria to find the inbound peg lines that are to fulfill the cross-dock order. The project pegs of the inbound and the outbound order lines must be identical.
The project, element and activity of an inbound project peg line are used as matching criteria to find the outbound peg line related to the cross-dock order to be fulfilled. Similar to unpegged order lines, an inbound order peg line can fulfill multiple cross-dock orders. The project pegs of the inbound and the outbound order lines must be identical.
Example
Sales order SO1
Peg line 1, project PRJ1, activity ACT1, quantity 5 pieces
Peg line 2, project PRJ1, activity ACT2, quantity 3 pieces
Expected purchase order PO1
Peg line 1, project PRJ1, activity ACT2, quantity 3 pieces
Peg line 2, project PRJ1, activity ACT1, quantity 1 piece
Peg line 3, project PRJ1, activity ACT1, quantity 4 pieces
These cross-dock orders are created:
| Cross-dock order | Originating order | Outbound peg line | Activity | Status | Requested |
|---|---|---|---|---|---|
| CD1 | SO1 | 1 | ACT1 | Open | 5.00 pcs |
| CD2 | SO1 | 2 | ACT2 | Open | 3.00 pcs |
Cross-dock order CD1 is fulfilled by these cross-dock order lines:
| Cross-dock order line | Originating order | Inbound peg line | Activity | Status | Planned |
|---|---|---|---|---|---|
| 10 | PO1 | 2 | ACT1 | Open | 1.00 pcs |
| 20 | PO1 | 3 | ACT1 | Open | 4.00 pcs |
Cross-dock order CD2 is fulfilled by these cross-dock order lines:
| Cross-dock order line | Originating order | Inbound peg line | Activity | Status | Planned |
|---|---|---|---|---|---|
| 10 | PO1 | 1 | ACT2 | Open | 3.00 pcs |
Creating project pegged cross-dock orders
The options, batch sessions, and manual processes used to create cross-dock orders with project peg lines are identical to those used to create cross-dock orders without project peg lines.
The difference is, that for a project pegged outbound order line, the cross-dock order is based on a project peg line instead of the outbound order line. Likewise, for a project pegged inbound order line, the cross-dock order line is based on a project peg line instead of the inbound order line.
In the Cross-dock Orders (whinh6100m000) and the Cross-dock Order Lines (whinh6110m000) sessions, you can select the project peg lines for which to manually create cross-dock orders or cross-dock order lines. In the Generate Cross-dock Orders (whinh6200m000) session, you can select ranges of project peg lines for which to create cross-dock orders or cross-dock order lines in batch.
When cross-dock orders are created for outbound project peg lines, the quantities to be cross-docked are calculated in this way:
To be cross docked quantity = ordered quantity – canceled quantity – advised quantity – cross-dock requested quantity + rejected quantity + expected not shipped quantity + not shipped quantity.