A place for storing goods. For each warehouse, you can enter address data and data relating to its type.
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:
Note
On the appropriate menu, you can choose:
Warehouse A place for storing goods. For each warehouse, you can enter address data and data relating to its type. Buy-from BP The business partner from whom you order goods or services; this usually represents a supplier's sales department. The definition includes the default price and discount agreements, purchase-order defaults, delivery terms, and the related ship-from and invoice-from business partner. 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 The business partner that ships the ordered goods to your organization. This usually represents a supplier's distribution center or warehouse. The definition includes the default warehouse at which you want to receive the goods and if you want to inspect the goods, the carrier that takes care of the transport, and the related buy-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 The raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, and sold. An item can also represent a set of items handled as one kit, or which exist in multiple product variants. You can also define nonphysical items, which are not retained in inventory but can be used to post costs or to invoice services to customers. The examples of nonphysical items:
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.
| |||