| | 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. Order 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. Project A collection of manufacturing and purchasing actions that are
performed especially for a particular customer order. A project is initiated by
a customer order for items having a To Order order policy. The purpose of a project is to plan and coordinate the production
of these items. For a standard-to-order production, the project is only
used to link the item with the customer order. Otherwise, a project can
include: - Customized item data (BOMs and routings)
- Project planning (activity planning)
A budget is a special type of project. A budget is used to
plan and estimate, not to carry out production. 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 Allocated to 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: - Allocated to Business Object Type
- Allocated to Business Object
- Allocated to Business Object Reference
Allocated to 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: - Allocated to Business Object Type
- Allocated to Business Object
- Allocated to Business Object Reference
Allocated to 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 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.
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. | |