| Planner/Item Exception Messages for specific itemLN not only generates exception messages for planned or actual orders of the specified item, but also
for all kinds of possible data that relates to the specified plan item
throughout LN, such as
inventory levels, safety stock, or horizons. On the View menu, you can select
the sort order in which LN displays the data in this
session. Select the Accept check box to
accept a exception message. Once you accepted exception messages, you can select Show/Hide Accepted Signals on the appropriate menu to hide or
display the accepted exception messages, so that the user can focus on the remaining exception messages. Other options on the appropriate menu to respond
to the exception messages are: - Planned Order: to go to the Planned Orders (cprrp1100m000) details session in which you can see the details for
the planned order that you selected. The Order field must be
filled to zoom to the corresponding planned order. If the Order field is not
filled, the Planned Order option on the appropriate menu is
disabled.
- Auto Process: to go to the Process - Signals (cprao1220m000) session in which you can automatically process the exception messages that LN generated during order-based planning, and for which you selected the Auto Process check box in the Signal Types - by Planner (cprao1110m000) session. You can still select or clear the Auto Process check box in the Planner/Item Signals (cprao1125m000) session.
- Update: to go to the Update Signals (cprao1210m000) session to update the exception messages when you made adjustments to the data on which the exception messages are based. If you do so, the accepted exception messages will be retained, so that you will not lose the information
that the exception messages in question are accepted.
- Item Master Plan: to zoom to the item master plan of the
specified plan item.
- Item Order Plan: to zoom to the item order plan of the plan item.
- View Tree Structure: LN presents the exception messages for the specified item/scenario combination in a tree
structure. On one branch, the tree lists the exception messages that are not directed to a planner, on the other branch, it
contains the exception messages that are directed to the specified
planner.
| |