| Signal Overview - Planner (cprao1120m000) |  |
| Use this session to get an overview of the total amount of signals per plan item, for a specific combination of planner and scenario. For the selected combination, the total number of signals 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 ERP LN displays detailed signal 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 ERP LN gives detailed information and advise about the item and order to which a specific signal 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 signals for the highlighted item. Show/Hide Accepted Signals: to show or hide the signals that you accepted in the Planner/Item Signals (cprao1125m000) session. View Tree Structure: ERP LN presents the signals for the specified item/ scenario combination in the Planner/Item Signals (cprao1125m000) session in a tree structure. On one branch, the tree lists the signals that are not directed to a planner, on the other branches, it contains the signals that are directed to the different planners. Note The range of signals taken into account is constrained by the selection you make by using the Find command. Related topics Planning signals in Enterprise Planning To use an overview session To maintain records in an overview session
Fields | Description
Planner ID | The employee code of the planner whose signal overview is shown. If this field is empty, the signals displayed are those which are not directed to a specific planner.
Scenario | The scenario for which ERP LN displays the signals.
Number of Signals | The total number of item signals that have been stored for the specified planner. Note Only non-accepted signals are taken into account.
Plan Item | The plan item for which ERP LN generated the signals.
Number of Signals | The number of signals that ERP LN generated for the plan item. Note Only non-accepted signals are taken into account.
Highest Priority | The highest priority of any signal related to this item. The highest priority is represented by the signal type with the lowest value in the Priority field in the Planner/Item Signals (cprao1125m000) session. Note Only non-accepted signals are taken into account.
Earliest Reference Date | The earliest of the reference dates belonging to each of the signals that ERP LN generated for the item on this line. If this field is empty, this means that there is at least one signal that has no reference date. Note Only non-accepted signals are taken into account.
Accepted | If this check box is selected, all signals for the selected item are accepted. Note Use the Show/Hide Accepted Signals command on the appropriate menu to display or hide the plan items for which you accepted all the signals 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 Allocation and hard 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 signal involves a supply, this field indicates the sold-to business partner to which this supply was allocated or hard pegged. If this signal 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 LN uses this characteristic to match supply and demand. Related topics Allocation and hard pegging overview
Allocated to Business Object Type | If this signal 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 signal 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 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 Allocation and hard pegging overview
Allocated to Business Object | If this signal 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 signal 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 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 Allocation and hard pegging overview
Allocated-to Reference | If this signal involves a supply, this field indicates the reference code to which the inventory was allocated or the supply object was hard pegged. If this signal 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 LN uses this characteristic to find a matching supply for this demand. ERP 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 Allocation and hard 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 Allocation and hard pegging overview
Commands | Description
Specification | Displays the signal's specification.