Special Demand by Item (cpdsp2100m000)

Use this session to maintain special demand for the specified plan item.

Master plan

Special demand is forecast demand for which it is important to administer a reason. LN considers and treats special demand as forecast demand.

You can view the special demand volumes by plan period in the Item Master Plan (cprmp2101m000) session.

LN automatically updates the special demand in the item master plan.

No master plan

If an item has no item master plan, you can use special demand as a demand forecast for order planning.

Note

If you update a scenario with the Initialize, Roll, and Update Scenario (cprpd4200m000) session, LN deletes the special demand that lies before the start date of the scenario.

You cannot create special demand for channeled plan items.

Copying special demand

To copy a special demand line for a plan item and scenario:

  1. Select a special demand record.
  2. From the Edit menu, choose Duplicate.

To copy special demand to another plan item or scenario, from the Group menu, choose Duplicate and follow the instructions in the status bar.

 

Scenario

The scenario for which special demand is created.

Plan Item

The plan item for which you want to specify special demand.

Forecast Time Fence

The date to which the forecast time fence extends.

LN ignores the special demand that falls on or before the forecast time fence.

In master planning, LN ignores the special demand up to the end of the plan period in which the time fence falls.

In order-based planning, LN ignores the special demand up to the end of the day in which the time fence falls. The special demand is taken into account starting 0:00 hours (midnight) of the next day.

Note

You can specify the plan item's forecast time fence in the Items - Planning (cprpd1100m000) session.

Demand Date

The date on which you expect the special demand.

In master planning, LN ignores the special demand that falls on or before the forecast time fence.

Sequence Number

The number that identifies a data record or a step in a sequence of activities. Sequence numbers are used in many contexts. Usually LN generates the sequence number for the next item or step. Depending on the context, you can overwrite this number. You can sometimes influence the numbering by setting the corresponding parameters.

Note

LN assigns the sequence numbers per special demand date. So, with every new special demand date, LN starts again by assigning the first sequence number.

Forecast Quantity

The special demand quantity, expressed in the number of plan items.

NonconsumedForecast Quantity

The part of the forecast demand that has not yet been consumed by actual demand.

As a rule, the demand forecast, extra demand, and special demand are gradually filled by actual orders. This process is referred to as consumption of forecast demand by actual demand.

LN applies forecast consumption automatically during an order simulation. In the current session, you can also consume the forecast manually by choosing Consume Forecast on the appropriate menu.

Reasons for Demand

In this field you can specify a reason for the special demand.

Besides the possibility to label special demand as, for example, a promotion, you can also use this field to label the demand of one specific customer to keep track of it.

Specification
Effectivity Unit

A means to control the validity of variations by effectivity units.

Unit effectivity enables you to model changes for the following entities:

  • Engineering bill of material
  • Production bill of material
  • Routing
  • Routing operations
  • Supplier selection
  • Sourcing strategies
Business Partner

The supply that fills this demand must have been allocated or hard pegged to the sold-to business partner displayed in this field.

LN uses this characteristic to find a matching supply for this demand.

Reference

The supply that fills this demand must have been allocated or hard pegged to the reference code displayed in this field.

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 allocated inventory only.

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.

 

Consume Forecast

Carries out forecast consumption. See also Forecast Consumption without an Item Master Plan.