| | Scenarios (cprpd4100m000)Note If you have started
this session by zooming, you can only find and select a record. 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. If the Scenario Status field has the value Closed,
you can no longer modify any data in this scenario. General Scenario Start/Finish Date The period a scenario. If you change the
start or finish date, it does not immediately take effect. The changes are
effected when the master plan is updated by means of the Initialize, Roll, and Update Scenario (cprpd4200m000) session. The value of the Scenario Start Date field also determines the availability of historic demand data for the
generation of a demand forecast. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Scenario start and finish date. Scenario Status An indication of whether the data in a scenario can still be
changed. The plan status can be Open or Closed. When a scenario has the Closed plan status, you can no longer modify it. Update Pegging Relations during Order Planning This field determines whether LN must update the pegging relations if you execute an order-based planning run. Allowed values Always Each time you execute an order-based planning run, LN also updates the
pegging relations. Never If you execute an order-based planning run, LN does not update the pegging relations. User Specified If you execute an order-based planning run, LN updates the planning
relations only if you select the Update Pegging Relations check box in the Generate Order Planning (cprrp1210m000) session or the Generate Order Planning (Item) (cprrp1220m000) session.
Alternative Materials Horizon The time period for which LN tries to find an alternative material if a standard material is not
available. The alternative materials horizon is expressed as a number
of working days from the date you carry out the order-planning process. LN rounds the horizon to
the end of a plan period. Important! The value of this field must not exceed the value of the CTP Horizon field in the Items - Planning (cprpd1100m000) session for any plan item used as alternative
material. Otherwise, LN erroneously assumes that the alternative material is infinitely available to
cover for shortages of the standard material. Days The date on which LN sets the alternative materials horizon. To find the correct date, LN starts from the
current date, and counts forward the number of workdays that you entered in the Alternative Materials Horizon field. LN then rounds the date
up to the end of that plan period. Rolling Data Rolling Scenario If this check box is selected, the scenario is a rolling plan. Reference Date A date that determines when a rolling scenario is shifted
forward in time. Example | Reference date | January 5 | | Rolling frequency | 14 days |
On or after January 19, the scenario is shifted forward 14
days. The new reference date will be January 19. Rolling Frequency The number of days after which a rolling scenario is shifted
forward in time. The number of days by which a plan is shifted forward equals
the value of the scenario's rolling frequency. Note that the rolling frequency is defined in calendar days. Example If the rolling frequency is seven days, the scenario will be
shifted forward seven days, every seventh day. Central Multi Site Planning If this check box is selected, the scenario is a multisite scenario. You can use multisite scenarios to
coordinate a number of local scenarios. If this check box is cleared, the scenario
applies to a single logistic company. Scenario Text If this check box is selected, a text is present. Actual Scenario The scenario that contains the operational master plan or order
plan, as opposed to scenarios used only for simulation, that is, what-if
analysis. The actual scenario is the only scenario from which you can
transfer planned orders to the execution level. Forecast Minimum Days for Forecast The minimum number of days that must be available for a plan
item in the demand history to calculate a demand forecast with the Generate Demand and Inventory Plan (cpdsp1210m000) session. Forecast Period Length The period length that is used in the generation of the demand forecast in the Generate Demand and Inventory Plan (cpdsp1210m000) session. Backward Forecast Consumption The number of calendar days preceding the delivery date of
customer orders during which the demand forecast can be
consumed by those orders (including dependent demand). If an item has an item master plan, the demand forecast for the plan period in which the planned or actual delivery dates
of a customer order fall is always consumed, regardless of the value entered in
this field. If an item does not have an item master plan, the demand forecast for the day in which the planned or actual delivery dates of a
customer order fall is always consumed, regardless of the value entered in this
field. Note If an item has an item master plan and the limit for forecast consumption
is halfway a plan period, LN uses the entire period for forecast
consumption. Forward Forecast Consumption Indicates the number of calendar days following the delivery
date of customer orders that the demand forecast may be
consumed by those orders (including dependent demand). If an item has an item master plan, the demand forecast for the plan period in which the planned or actual delivery dates
of a customer order fall is always consumed, regardless of the value entered in
this field. If an item does not have an item master plan, the demand forecast for the day in which the planned or actual delivery dates of a
customer order fall is always consumed, regardless of the value entered in this
field. Note If the limit for
forecast consumption is halfway a plan period, LN uses the entire period
for forecast consumption. | |