Exception Messages by Planner (cprao1120m000)

Field Information

Planner ID

The employee code of the planner whose exception message overview is shown.

If this field is empty, the exception messages displayed are those which are not directed at a specific planner.

Scenario

The scenario for which LN displays the exception messages.

Number of Exception Messages

The total number of item exception messages that was stored for the specified planner.

Note: Only non-accepted exception messages are taken into account.

Plan Item

The plan item for which LN generated the exception messages.

Number of Signals

The number of exception messages that LN generated for the plan item.

Note: Only non-accepted exception messages are taken into account.

Highest Priority

The highest priority of any exception message related to this item. The highest priority is represented by the exception message type with the lowest value in the Priority field in the Exception Messages by Planner and Item (cprao1125m000) session.

Note: Only non-accepted exception messages are taken into account.

Earliest Reference Date

The earliest of the reference dates belonging to each of the exception messages that LN generated for the item on this line.

If this field is empty, there is at least one exception message that has no reference date.

Note: Only non-accepted exception messages are taken into account.

All Accepted

If this check box is selected, all exception messages for the selected item are accepted.

Specification

Specification

If this check box is selected, a specification is present.

Effectivity Unit

unit effectivity

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.

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.

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:

• 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.

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:

• 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.

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

Note: 

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.