Signal Types - by Planner (cprao1110m000)

Use this session to define and maintain planner-specific exception message settings that determine:

  • Which types of exception messages are generated for the planner involved.
  • Under which circumstances these exception messages must be generated.

Specify the exception message types required for the planner involved, and define the settings for each exception message type.

Per exception message type / planner combination, a minimum cost price and exception message horizon can be defined that regulate the generation of the exception message.

In the Minimum Cost Price field, you can specify a minimum cost price for each exception message.

By leaving the Planner ID field empty, you can define a general set of exception message types. This general set is used for those exception messages that are not directed to a specific planner.

Note

If you want to generate exception messages for a specific planner, you must first define a set of exception message types for this planner.

If you do not, LN does not generate the exception messages for this planner.

 

Planner ID
The employee number of the planner whose set of exception message types is shown.
Note

If this field is empty, a general set of exception message types is displayed, which is used for all exception messages that are not directed to a specific planner.

Commonly an exception message is directed to a specific planner if the exception message refers to an item for which an employee code has been entered in the Planner field in the Items - Planning (cprpd1100m000)

Minimum Cost Price Currency for Exception Messages
The currency that LN uses to express the minimum cost price, which you can define in the EP Parameters (cprpd0100m000) session.

If you defined a different currency for the item in the Items - Costing (ticpr0107m000) session, LN converts this currency to the currency for the minimum cost price.

Exception Message Type
Specify the type of exception message that LN can generate during planning.

Exception message types inform the planner about the current planning process.

Minimum Cost Price
The minimum cost price to which the exception message type on this line applies.

If the Minimum Cost Price field for a exception message type is blank, you can specify a value. If you do so, LN only generates the corresponding exception message type, if the Cost Price of the ordered item lies above the minimum cost price.

Exception Message Priority
The default priority of the exception message type. You can use this priority, for example, to display the exception messages in order of importance.

Allowed values

Enter a number from one (highest priority) to 100 (lowest priority).

Horizon
The exception message horizon of the exception message type on this line.
Note

For some exception message types, the horizon has a fixed value. The scope of the horizon is so large that in actuality, the generation of exception messages of these types is never constrained by the horizon. The exception message types involved are:

  • Fatal Error
  • No Supplying Relationship
  • No Supplying Business Partner
  • Item Error
  • No Items for Plan Unit
  • Planning Failed

For pegging exception messages, enter a value that is lower than the value of the Pegging Horizon field in the EP Parameters (cprpd0100m000) session. Otherwise, false Pegging: No Planned Stock exception messages and Pegging: No Planned Material Stock exception messages may be generated.

Tolerance (%)
The tolerance percentage applies to exception messages that involve a comparison of quantities or percentages, and that indicate that a certain actual value is higher or lower than a certain norm value.

The tolerance percentage involved is a percentage of the norm value. If you define a tolerance percentage for a exception message type, LN will ignore minor deviations from the norm value when it generates exception messages of this type.

Example

  • The exception message type is Inventory > Maximum, the maximum inventory is 50, and the tolerance percentage is ten. In this case, a exception message is generated only when the projected inventory is higher than 55.
  • The exception message type is Order Quantity < Minimum, the minimum order quantity is 20, and the tolerance percentage is 15. In this case, a exception message is generated only when the order quantity is lower than 17.

The tolerance percentage applies to the following exception messages types:

  • Inventory < Safety/Plan
  • Inventory > Maximum
  • Forecast <> Actual Demand
  • Inventory > Inventory Plan
  • Order Quantity < Minimum
  • Order Quantity > Maximum
  • Overloaded Resource
Note

For all other exception message types, the tolerance percentage is disabled. This includes the exception message types Workload < Norm and Workload > Norm. For these two exception message types, you may define a tolerance percentage in the Workload Tolerance field of the Resource (cprpd2100m000) session.

In the case of the exception message type Forecast <> Actual Demand, the demand forecast is used as the norm value, and the tolerance percentage applies in both directions (below and above the demand forecast).

Tolerance (Days)
The tolerance in days applies to exception messages that involve a comparison of dates, and that indicate that a certain date is earlier or later than a certain norm date.
Note

The tolerance in days is expressed in working days. If you define a tolerance in days for a exception message type, LN will ignore minor deviations from the norm date when it generates exception messages of this type.

For the Transfer Late exception message type, the tolerance in days may be used as a special kind of time fence when using order planning, to indicate when the order should be transferred.

Example

  • The exception message type is Finish Date > Requirement Date, the requirement date is Monday, April 10, and the tolerance in days is two. In this case, a exception message is generated only when the order's end date is later than April 12.
  • The exception message type is Reschedule Out, the requirement date is Friday, August 25, and the tolerance in days is three. In this case, a exception message is generated only when the order's end date is earlier than August 22.

The tolerance in days applies to the following exception message types:

  • Transfer Late
  • Reschedule In
  • Reschedule Out
  • Order within Safety Time
  • Order in Order Interval
  • Order in Extra Lead Time
  • Finish Date > Requirement Date

For all other exception message types, the tolerance in days is disabled.

Related topics

Maximum Number
The maximum number of exception message of this type that LN generates for a specific item/planner combination.

For example, if you set the maximum number of a specific exception message type to ten, only the first ten exception messages of this type are stored for one item (and for a specific planner).

Note

The generation of some exception messages is not constrained by the maximum number. The exception message types involved are:

  • Fatal Error
  • No Supplying Relationship
  • No Supplying Business Partner
  • Item Error
  • No Items for Plan Unit
  • Planning Failed
Disable
If this check box is selected, no exception messages of the type specified are generated.
Auto Process
If this check box is selected, LN can process the corresponding exception message automatically in the Process Exception Messages (cprao1220m000) session.
Note

You can only select this check box for the following exception message types:

  • Cancel Order
  • Reschedule In
  • Reschedule Out

The above exception message types only apply to order-based planning.

If the Auto Process check box is selected in the Planner/Item Signals (cprao1125m000) session as well, you can view the cancellation and/or rescheduling exception messages generated during order-based planning there.

 

Print Exception Message Types