Delivery Patterns by Warehouse / BP / Item (tdipu0124m000)
Use this session to store delivery patterns by warehouse, buy-from business partner/ ship-from business partner, and item.
You can store delivery patterns on three levels:
- By warehouse
- By warehouse, buy-from business partner and ship-from business partner
- By warehouse, buy-from business partner, ship-from business partner and item
Note:
- LN always uses the delivery pattern that is stored on the most detailed available level.
- If the purchase schedule is Shipment Based, which you can define in the Shipment or Receipt Based field of the Purchase Contract Line Logistic Data (tdpur3102m000) session and/or the Items - Purchase Business Partner (tdipu0110m000) session, you cannot use delivery patterns that are stored by warehouse only.
On the appropriate menu, you can choose:
- Generate Planned Delivery Moments (tdipu0225m000) session, in which you can generate planned delivery moments for both shipment based schedules and receipt based schedules. , to start the
- Planned Delivery Moments (Shipment Based) (tdipu0125m000) session, in which you can view planned delivery moments for shipment based schedules. , to start the
- Planned Delivery Moments (Receipt Based) (tdipu0126m000) session, in which you can view planned delivery moments for receipt based schedules. , to start the
- Delete Not-Used Planned Delivery Moments (tdipu0226m000) session, in which you can delete planned delivery moments that are no longer used by Enterprise Planning. , to start the
Field Information
- Warehouse
- Buy-from BP
-
Note: If the Ship-from Business Partner field is filled, it is mandatory to enter a buy-from business partner in the current field.
- Ship-from Business Partner
-
Note: If the Buy-from BP field is filled, it is mandatory to enter a ship-from business partner in the current field.
- Item
- Delivery Pattern
-
The pattern used to determine the moment of delivery.
Note: You can define delivery patterns in the Patterns (tcccp0690m000) session. - Horizon End Date (Receipt Based)
-
The date until which planned receipt moments (receipt based) are generated/updated in the Generate Planned Delivery Moments (tdipu0225m000) session.
Note: Because, in the Planned Delivery Moments (Receipt Based) (tdipu0126m000) session, planned delivery moments (receipt based) are stored by warehouse and delivery pattern, records in the current session with different ship-from business partner(s), buy-from business partner(s) and item(s) can be stored under the same entry in the Planned Delivery Moments (Receipt Based) (tdipu0126m000) session. For this reason, it is also possible that for new combinations entered in the current session, the Horizon End Date (Receipt Based) field is automatically filled, although no delivery moments are generated yet for the combination in the Generate Planned Delivery Moments (tdipu0225m000) session. - Horizon End Date (Shipment Based)
-
The date until which planned shipment moments (shipment based) are generated/updated in the Generate Planned Delivery Moments (tdipu0225m000) session.
Note: Because, in the Planned Delivery Moments (Shipment Based) (tdipu0125m000) session, planned delivery moments (shipment based) are stored by warehouse, ship-from business partner, and delivery pattern, records in the current session with different buy-from business partner(s) and item(s) can be stored under the same entry in the Planned Delivery Moments (Shipment Based) (tdipu0125m000) session. For this reason, it is also possible that for new combinations entered in the current session, the Horizon End Date (Shipment Based) field is automatically filled, although no delivery moments are generated yet for the combination in the Generate Planned Delivery Moments (tdipu0225m000) session.