| # Planned Order Distribution (cprrp1105m000) Use this session to view the distribution of planned orders over different effectivity units. Related topics Overview of unit effectivity Scenario The identification of an overall planning solution. Each scenario represents one overall planning solution, and involves particular settings for the planning of items and resources. You can use scenarios to analyze and compare various planning options and to find the best planning solution. For example, you can vary demand forecasts or sourcing strategies. One of the scenarios is the actual scenario, which corresponds with the actual planning situation. You can only transfer planned orders and production plans from the actual scenario to the execution level of ERP LN. Scenario If the scenario is the actual scenario, this field indicates that fact. Order Type The type of order ( Planned Production Order, Planned Purchase Order, or Planned Distribution Order). Planned Order A supply order in Enterprise Planning that is created for planning purposes, but which is not an actual order yet. Enterprise Planning works with planned orders of the following types: Planned production order Planned purchase order Planned distribution order Planned orders are generated in the context of a particular scenario. The planned orders of the actual scenario can be transferred to the execution level, where they become actual supply orders. Position Number The number used to identify the position of the order line on the planned order. Unit Effectivity Number A reference number on a sales order line or a sales quotation line that is used to model deviations for a unit effective item. Order Quantity The quantity of the order that belongs to a particular effectivity unit. Specification Allocated to BP The sold-to business partner to which the planned order was hard pegged. ERP LN uses this characteristic to match supply and demand. Related topics Allocation and hard pegging overview Allocated to Business Object Type The type of order to which the planned order was hard pegged, such as, Sales Order, or Service Order. ERP LN uses this characteristic to match supply and demand. Note The following fields are always used in combination; together, they identify the relevant order or order line: Allocated to Business Object Type Allocated to Business Object Allocated to Business Object Reference Related topics Allocation and hard pegging overview Allocated to Business Object The order, or order line, to which the planned order was hard pegged. ERP LN uses this characteristic to match supply and demand. Note The following fields are always used in combination; together, they identify the relevant order or order line: Allocated to Business Object Type Allocated to Business Object Allocated to Business Object Reference Related topics Allocation and hard pegging overview Allocated-to Reference A reference code to which the planned order was hard pegged. ERP LN uses this characteristic to find a matching supply for this demand. ERP LN uses the Allocated-to Reference field to record an internal reference. You can use a reference code to keep a collection of parts linked together, even if they follow different routings, for example, if some of the parts are transported to a subcontractor to be returned later. Related topics Allocation and hard pegging overview Use Unallocated Inventory If this check box is selected, Enterprise Planning can use unallocated inventory to supply the demand. Enterprise Planning uses allocated inventory first. If there is not enough allocated inventory, Enterprise Planning also uses unallocated inventory. If this check box is cleared, Enterprise Planning can use only allocated inventory to fill the demand. Related topics Allocation and hard pegging overview Specification Displays the selected record's specification. |