| # Exception Messages by Planner and Item (cprao1125m000) Use this session to review the all signals that ERP Enterprise generated for one specific item. Related topics Exception Messages in Enterprise Planning To use an overview session To maintain records in an overview session Planner ID The planner to whom ERP Enterprise directs the displayed exception messages. If you did not define planner-specific exception message parameters in the Exception Message Types by Planner (cprao1110m000) session, ERP Enterprise takes into account the planner that you specified in the Planner field in the Items - Planning (cprpd1100m000) session. If you leave this field empty, ERP Enterprise displays the exception messages for which you did not define planner-specific exception message parameters in the Exception Message 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 ERP Enterprise must direct the exception messages in the Save Messages for Planner field. Planner ID (Name) The employee that you selected in the Planner ID field. Scenario The scenario for which ERP Enterprise displays the exception messages. Plan Item The plan item for which the ERP Enterprise displays the exception messages. Priority The priority of the exception message. You can use this priority, for example, to display the exception messages in order of importance. 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 Exception Message Types by Planner (cprao1110m000) session. Exception Message The signal in question. In the Message field, ERP Enterprise 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. Related topics Types of exception messages Inventory and demand signals Order signals Error signals Order Type The order type of the order involved. ERP Enterprise 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. Order No. The order number of the order to which this exception message refers. This field is empty if: The exception message refers to order planning, but is not linked to a specific order number. The exception message refers to master planning. Position Number The specific order line to which this exception message refers. 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 ERP Enterprise generated the corresponding signal during order planning or during master planning: If ERP Enterprise generated the exception message for a specific planned order, that is, there is an order number in the Order No. 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 ERP Enterprise indicates the start date of the corresponding order line. If ERP Enterprise generated the exception message on the basis of master-plan data, that is, the Order No. 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, ERP Enterprise fills the finish date of the order if the Item Error exception message is generated for a specific planned order. In all other cases, ERP Enterprise 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 ERP Enterprise provides can be useful to modify the planning aspect to which the signal refers. Accepted 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. Note You can choose the Show/Hide Accepted Exception Messages on the appropriate menu to display or hide accepted exception messages, so that you can focus on the remaining exception messages. Exception Message Date The date on which ERP Enterprise generated the exception message. Auto Process If this check box is selected, you can let ERP Enterprise process the corresponding exception message automatically in the Process Exception Messages (cprao1220m000) session. To do so, select the exception message, and click Process Exception Messages on the appropriate menu. ERP Enterprise 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 Exception Message Types by Planner (cprao1110m000) session. You can only select the Auto Process check box for the following exception message types: Cancel Reschedule In Reschedule Out Processed If this check box is selected, ERP Enterprise processed the corresponding exception message in the Process Exception Messages (cprao1220m000) session. Item Exception Message 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. Related topics To use texts Order Status The status of the planned order involved. Unit Number If you specified an effectivity unit for this item in the Effectivity Unit (tcuef0102m000) session, ERP Enterprise displays the corresponding number in this field. Related topics Unit effectivity in Enterprise Planning 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. To display the specification, in the appropriate menu, click Specification. Related topics Demand pegging overview 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 Related topics Unit effectivity in Enterprise Planning Demand Pegged to BP If this exception message involves a supply, this field indicates the sold-to business partner to which this supply was allocated or hard 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 hard pegged. ERP Enterprise uses this characteristic to match supply and demand. Related topics Demand pegging overview Demand Pegged 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 hard 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 hard pegged. ERP Enterprise 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: Demand Pegged to Business Object Type Demand Pegged to Business Object Demand Pegged to Business Object Reference Related topics Demand pegging overview Demand Pegged 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 hard 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 hard pegged. ERP Enterprise 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: Demand Pegged to Business Object Type Demand Pegged to Business Object Demand Pegged to Business Object Reference Related topics Demand pegging overview Demand Pegged 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 hard 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 hard pegged. ERP Enterprise uses this characteristic to find a matching supply for this demand. ERP Enterprise uses the Demand Pegged 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. Related topics Demand pegging overview 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. Related topics Demand pegging overview Update Starts the Update Exception Messages (cprao1210m000) session. Show/Hide Accepted Exception Messages Click this option to show or hide the exception messages that you accepted, which enables you to focus on the remaining exception message. Planned Order Starts the Planned Orders (cprrp1100m000) session. Item Master Plan Starts the Item Master Plan (cprmp2101m000) session. Item Order Plan Starts the Item Order Plan (cprrp0520m000) session. View Tree Structure Displays a exception message overview in a tree format. Print Exception Messages by Planner and Item Starts the Print Exception Messages by Planner and Item (cprao1425m000) session. Process Exception Messages Starts the Process Exception Messages (cprao1220m000) session. Specification Displays the exception message 's specification. |