A planning concept in which planning data is handled in the form of orders. In order planning, supply is planned in the form of planned orders. LN takes into account the start and finish dates of individual planned orders. For production planning, this method considers all material and capacity requirements, as recorded in an item's BOM and routing. These planned orders can be firmed, confirmed and transferred into execution level orders (purchase, production and warehouse transfers). Transferring the planned order means: execution order gets created and planned order gets deleted. Identifier of planned order and execution order do not match, they are separate entities. Provides information that pertains to the entire Transfer. Provides the line level detail of the items ordered by the Transfer and the associated detail. The Component Subline represents any additional information concerning the product on the Line. The Subline can be used to describe a specific configuration of the ordered item. The schema type for Transfer. The base abstract type, Order, is shared with PurchaseOrder and SalesOrder. Transfer is essentially an extension of PurchaseOrder, but in order to use the local-global design pattern, each of Transfer, PO and SO needs to instantiate its own Header and Line elements.To do this, we factored out the PO content models, instantiated both PO and SO from Order. Indicates the DistributionCenter that the Seller will ship the items from. Indicates the purchase order in the distribution center that is associated with the goods allocated to this transfer. Is the Transfer Line type that provides the structure of the transfer Line. The scheduled delivery date provided by the supplier. Is the actual delivery date and time of the line item. Inidicates the shipping date and time of the line item. Inidicates the shipping date and time of the line item. Indicates the distribution center the line item will be shipped from.