| Signal Types - by Planner (cprao1110m000) |  |
| Use this session to define and maintain planner-specific signal settings that determine: Which types of signals are generated for the planner involved. Under which circumstances these signals must be generated. Specify the signal types required for the planner involved, and define the settings for each signal type. For one signal type, you can define different settings for various cost-price ranges. For example, you can use different tolerance levels for high-cost orders versus low-cost orders. In the Minimum Cost Price field, you can specify a minimum cost price for each signal. By leaving the Planner ID field empty, you can define a general set of signal types. This general set is used for those signals that are not directed to a specific planner. Note If you want to generate signals for a specific planner, you must first define a set of signal types for this planner. If you do not, ERP LN does not generate the signals for this planner. Related topics Planning signals in Enterprise Planning Types of planning signals To use an overview session To maintain records in an overview session
Fields | Description
Planner ID | The employee number of the planner whose set of signal types is shown. Note As a rule, a signal is directed to a specific planner if the signal refers to an item for which an employee code has been entered in the Planner field in the Items - Planning (cprpd1100m000) If this field is empty, a general set of signal types is displayed, which is used for all signals that are not directed to a specific planner.
Minimum Cost Price Currency for Signals | The currency that ERP 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, ERP LN converts this currency to the curency for the minimum cost price.
Signal Type | Specify the type of signal that ERP LN can generate during planning. Signal types inform the planner about the current planning process.
Minimum Cost Price | The minimum cost price to which the signal type on this line applies. If the Minimum Cost Price field for a signal type is blank, you can specify a value. If you do so, Common only generates the corresponding signal type, if the Cost Price of the ordered item lies above the minimum cost price.
Signal Priority | The default priority of the signal type. You can use this priority, for example, to display the signals in order of importance. Allowed values Enter a number from one (highest priority) to 100 (lowest priority).
Horizon | The signal horizon of the signal type on this line. Note For some signal types, the horizon has a fixed value. The scope of the horizon is so large that in actuality, the generation of signals of these types is never constrained by the horizon. The signal types involved are the following: Fatal Error No Supplying Relationship No Supplying Business Partner Item Error No Items for Plan Unit Planning Failed Note For pegging signals, 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 signals and Pegging: No Planned Material Stock signals can be generated.
Tolerance (Prc) | The tolerance percentage applies to signals 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 signal type, ERP LN will ignore minor deviations from the norm value when it generates signals of this type. Example The signal type is Inventory > Maximum, the maximum inventory is 50, and the tolerance percentage is ten. In this case, a signal is generated only when the projected inventory is higher than 55. The signal type is Order Quantity < Minimum, the minimum order quantity is 20, and the tolerance percentage is 15. In this case, a signal is generated only when the order quantity is lower than 17. The tolerance percentage applies to the following signals types: Inventory < Safety/Plan Inventory > Maximum Forecast <> Actual Demand Inventory > Inventory Plan Order Quantity < Minimum Order Quantity > Maximum Overloaded Resource For all other signal types, the tolerance percentage is disabled. This includes the signal types Workload < Norm and Workload > Norm. For these two signal types, however, you can define a tolerance percentage in the Resource (cprpd2100m000) session (in the Workload Tolerance field). Note In the case of the signal 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 signals that involve a comparison of dates, and that indicate that a certain date is earlier or later than a certain norm date. The tolerance in days is expressed in working days. If you define a tolerance in days for a signal type, ERP LN will ignore minor deviations from the norm date when it generates signals of this type. Example The signal type is Finish Date > Requirement Date, the requirement date is Monday, April 10, and the tolerance in days is two. In this case, a signal is generated only when the order's end date is later than April 12. The signal type is Reschedule Out, the requirement date is Friday, August 25, and the tolerance in days is three. In this case, a signal is generated only when the order's end date is earlier than August 22. The tolerance in days applies to the following signal 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 signal types, the tolerance in days is disabled. Note For the Transfer Late signal type, the tolerance in days is actually used as a special kind of time fence, to indicate when the order should be transferred. Note Order signals
Maximum Number | The maximum number of signals of this type that ERP LN generates for a specific item/planner combination. For example, if you set the maximum number of a specific signal type to ten, only the first ten signals of this type are stored for one item (and for a specific planner). Note For some signal types, the maximum number of signals is a fixed value. The extent of this value is so large that in actuality, the generation of signals of these types is never constrained by the maximum number. The signal types involved are the following: 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 signals of the type specified are generated. Note Essentially, disabling a signal type has the same effect as deleting the record for that signal type. However, disabling the signal type has the advantage that you can easily re-enable it.
Auto Process | If this check box is selected, ERP LN can process the corresponding signal automatically in the Process - Signals (cprao1220m000) session. You can only select this check box for the following signal types: Cancel Order Reschedule In Reschedule Out ERP LN only generates the signal types mentioned above when you carry out order-based planning. After you carried out order-based planning, and ERP LN generated cancellation and/or rescheduling signals, you can see these signals in the Planner/Item Signals (cprao1125m000) session with the corresponding Auto Process check box selected.
Commands | Description
Print Signal Types | Starts the Print Signal Types (cprao1410m000) session.