| Exception Messages by Planner and Item (cprao1125m000)Use this session to review the all signals that LN generated for one
specific item. Priority The priority of the exception message. You can use this priority, for example, to display the
exception messages in order of importance. Exception Message The exception message in question. In the Message field, LN provides additional,
situation-specific information, for example, a relevant date, or an error
specification. Note Each exception
message is a token of a certain exception message type. Some exception
message types always appear in the same form. Other exception message types can
appear in various forms. As a rule, however,
it is not hard to recognize to which exception message type a particular
exception message belongs. Order Type The order type of the order involved. LN does not only generate exception messages for planned orders, but also for actual orders. If this field is empty, the exception message relates to
other item related data than orders, such as, for example the safety stock or the planning horizon. Position Number The specific order line to which this exception message refers. Note 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 a
problem or a situation occurs. Note The reference date depends on they type of planning during
which the corresponding exception message was generated: - If LN generated the
exception message for a specific planned order, 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, the
reference date usually indicates the start date of the plan period to which the
exception message refers.
For exception messages of the 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 (zero), which means that
the item error always applies. 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 exception message refers. Accepted If this check box is selected, you indicate that you took notice the exception message and do not want to analyze it any further. If this check box is cleared, you indicate that you want to reexamine the exception
message at a later time. Clearing this check box may be done at any
time. Note You can hide accepted exception messages by selecting Hide Accepted Exception Messages on the appropriate menu. Auto Process If this check box is selected, you can let LN process the
corresponding exception message automatically in the Process Exception Messages (cprao1220m000) session. Note This check box will be selected by LN if an order-planning run is
done while the Auto Process in the Exception Message Types by Planner (cprao1110m000) is selected for the specific
exception message. If this check box is cleared, you can process the exception messages manually
by clicking Process Exception Messages in the appropriate menu. You can only select the Auto Process check box for the following exception
message types: - Cancel
- Reschedule In
- Reschedule Out
Item Exception Message Text You can create a text if you highlight a specific exception message, and click Edit Text on the toolbar. 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 If this check box is selected, a specification is present. 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 If this exception message involves a supply, this field indicates the sold-to business partner to which this
supply was allocated or demand pegged. If this exception message involves a
demand, this field indicates the sold-to business partner to which the supply
that can fill this demand must have been allocated or demand pegged. Note LN uses this characteristic to match supply and demand. 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. Note LN uses this characteristic to match supply and demand. The following fields are always used in combination;
together, they identify the relevant order or order line: - Business Object Type
- Business Object
- Business Object Reference
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. Note LN uses this characteristic to match supply and demand. The following fields are always used in combination;
together, they identify the relevant order or order line: - Business Object Type
- Business Object
- Business Object Reference
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. Note 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
only allocated inventory to fill the demand. | |