| | Exception Messages by Planner and Item (cprao1125m000)Use this session to review the all signals that LN generated for one
specific item. Planner ID If you did not
define planner-specific exception message parameters in the Signal Types - by Planner (cprao1110m000) session, LN takes into account the
planner that you specified in the Planner field in
the Items - Planning (cprpd1100m000) session. If you leave this
field empty, LN displays
the exception messages for which you did not define planner-specific exception message parameters in the Signal Types - by Planner (cprao1110m000) session, and for items for which you did not
define a planner in the Items - Planning (cprpd1100m000) session. Note In the Generate Master Planning (cprmp1202m000) session and in the Generate Order Planning (cprrp1210m000) session you can specify the planner to whom LN must direct the exception messages in the Planning Signals to Planner field. Planner ID (Name) The employee that you selected in the Planner ID field. Priority The exception message priority is expressed as a number between one (highest priority)
and 100 (lowest priority). You can enter the
default priority for a exception message type in the Signal Types - by Planner (cprao1110m000) session. Exception Message The signal in question. In the Message field, LN provides additional,
situation-specific information, for example, a relevant date, or an error
specification. Order Type The order type of the order involved. Position Number The value of this
field is zero, if the exception message does not refer to an order. Reference Date The reference date for the exception message involved. The reference date expresses the date and time on
which a problem or a situation occurs. The reference date depends on whether LN generated the
corresponding signal during order planning or during master
planning: - If LN generated the exception message for a specific planned order, that is,
there is an order number in the Order field, the reference date usually indicates the
finish date of the corresponding order line. The only exception is the exception message of type Transfer Late, for which LN indicates the start
date of the corresponding order line.
- If LN generated the exception message on the basis of master-plan data, that is,
the Order field is empty, the reference date usually
indicates the start date of the plan period to which the exception message refers.
For exception messages of type Item Error, LN fills
the finish date of the order if the Item Error exception message is generated for a specific planned order. In all other cases, LN fills the Reference Date field with 0, which means that the
item error applies from date 0 (always). Message This field contains additional, exception message-specific information. The information that LN provides can be useful
to modify the planning aspect to which the signal refers. Accept Select this check box to indicate that you took notice of the exception message and do not want to analyze it any further. Clear the check box
again, if you accepted a exception message, but want to re-examine it. Auto Process If this check box is selected, you can let LN process the
corresponding exception message automatically in the Process - Signals (cprao1220m000) session. To do so, select the exception message, and click Process - Signals on the appropriate menu. LN selects this check box when you carry out an order-planning run, and also
selected the Auto Process check box for the exception message in the Signal Types - by Planner (cprao1110m000) session. You can only select the Auto Process check box for the following exception message types: - Cancel Order
- Reschedule In
- Reschedule Out
Processed If this check box is selected, LN processed the corresponding exception message in the Process - Signals (cprao1220m000) session. Text If this check box is selected, a text is present. You can create a
text if you highlight a specific exception message, and click Edit Text on the toolbar. Effectivity Unit If you specified an effectivity unit for this
item in the Effectivity Unit (tcuef0102m000) session, LN displays the
corresponding number in this field. Quantity The inventory quantity, demand quantity, or order quantity to
which this exception message applies. Depending on the exception message type involved, this number can indicate: - The negative
inventory (or negative ATP) level referred to in the exception message.
- The amount of
inventory that is below a minimum norm level.
- The amount of
inventory that is above a maximum norm level.
- The difference
between demand forecast and actual demand (positive when the actual demand is
higher, negative when it is lower).
- The production plan
quantity that does not conform to the lot size rules.
- The order quantity
that is too late or too early.
- The order quantity
that should be rescheduled.
- The order quantity
or supply plan quantity that must be canceled.
Specification Specification To display the specification, in the appropriate menu, click Specification. Unit Effectivity Number 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
Allocated to BP LN uses this characteristic to match supply and demand. Allocated to Business Object Type If this exception message involves a supply, this field indicates the type of order to
which the inventory was allocated or the supply object was demand pegged, such as, Sales Order,
or Service Order. If this exception message involves a demand, this field indicates the type of order to
which the supply that can fill this demand must have been allocated or demand
pegged. LN uses this characteristic to match supply and demand. Note 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 If this exception message involves a supply, this field indicates the order, or order line, to which the inventory was allocated or the supply object was demand pegged, such as, Sales Order,
or Service Order. If this exception message involves a demand, this field indicates the order, or order line, to which the supply that can fill
this demand must have been allocated or demand pegged. LN uses this characteristic to match supply and demand. Note 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 If this exception message involves a supply, this field indicates the reference code to
which the inventory was allocated or the supply object was demand pegged. If this exception message involves a demand, this field indicates the reference code to
which the supply that can fill this demand must have been allocated or demand
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. | |