| | Planned Order Distribution (cprrp1105m000)Use this session to view the distribution of
planned orders over different effectivity units. 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 LN. Scenario If the scenario is the actual scenario, this field indicates that fact. 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 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. Ordered Quantity The quantity of the order that belongs to a particular
effectivity unit. Line The number used to identify the position of the order line on
the planned order. Planning Group A planning group is used for segregation in planning for
project specific demand and supply. Commingling rules and cost transfer rules
can be defined at planning group level to control supply planning behavior of
project pegged items within the planning group as well as with other planning
groups. Note A project can only be assigned to one planning
group. Project A collection of manufacturing and purchasing actions that are
performed for a particular customer order. A project is initiated to plan and
coordinate the production of the to be manufactured items. For a standard-to-order production, the project is only
used to link the item with the customer order. A project can also include
these: - Customized item data (BOMs and routings)
- Project planning (activity planning)
Element The element code used for project code pegging
purposes. Activity The activity code used for project pegging purposes. Project Peg Origin The origin of the project peg for the planned order. Multiple Required Dates If this check box is selected, the production order has several planned requirement dates on which demand must be met. Specification Business Object Type The type of order to which the planned order was hard pegged, such as, Sales Order,
or Service Order. Note - LN uses this characteristic to match supply and demand.
The following fields are always used in combination;
together, they identify the relevant order or order line: - Business Object Type
- Business Object
- Business Object Reference
Business Object The order, or order line, to which the planned order was hard pegged. Note - LN uses this characteristic to match supply and demand.
The following fields are always used in combination;
together, they identify the relevant order or order line: - Business Object Type
- Business Object
- Business Object Reference
Reference A reference code to which the planned order was hard pegged. - LN uses this characteristic to find a matching supply for this
demand.
- LN uses the 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.
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. | |