| # Signal Overview - by Planner (cprao1120m000) Use this session to get an overview of the total amount of exception messages per plan item, for a specific combination of planner and scenario. For the selected combination, the total number of exception messages is shown, as well as overview information for each plan item. Double-click on a record to go to the Planner/Item Signals (cprao1125m000) session, in which LN displays detailed exception message information for the involved plan item. On the appropriate menu you can select the following options: Signals by Item or Planner: to go to the Planner/Item Signals (cprao1125m000) sessions, in which LN gives detailed information and advise about the item and order to which a specific exception message relates. Item Master Plan: to go to the item master plan of the item that you highlighted or marked. Item Order Plan: to go to the Item Order Plan (cprrp0520m000) session. Update Signals: to go the Update Signals (cprao1210m000) session, in which you can update the exception messages for the highlighted item. Show/Hide Accepted Signals: to show or hide the exception messages that you accepted in the Planner/Item Signals (cprao1125m000) session. View Tree Structure: LN presents the exception messages for the specified item/ scenario combination in the Planner/Item Signals (cprao1125m000) session in a tree structure. On one branch, the tree lists the exception messages that are not directed to a planner, on the other branches, it contains the exception messages that are directed to the different planners. Note The range of exception messages taken into account is constrained by the selection you make by using the Find command. Related topics Exception Messages in Enterprise Planning 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 to 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 have been stored for the specified planner. Note Only non-accepted signals 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 Planner/Item Signals (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, this means that there is at least one exception message that has no reference date. Note Only non-accepted exception messages are taken into account. Accepted If this check box is selected, all exception messages for the selected item are accepted. Note Use the Show/Hide Accepted Exception Messages command on the appropriate menu to display or hide the plan items for which you accepted all the exception messages in the Planner/Item Signals (cprao1125m000) session. 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 Allocated to BP 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. Related topics Demand pegging overview 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 Related topics Demand pegging overview 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 Related topics Demand pegging overview 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. 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 Specification Displays the exception message 's specification. |