DOP Alarms
A DOP alarm is displayed whenever a DOP order will not be able to
be delivered at the
right time, or with the right quantity. A DOP alarm
is also generated if a configuration is used to create the DOP structure and if
it does not match the configuration of a customer order line to which the DOP header is pegged.
DOP alarms can be viewed either on the DOP order itself, or as component
alarms on the parent order, if there is any. The component alarms concern the
fact that the necessary components for the DOP order are not available on time,
and/or in the right quantity. If an alarm exists, it is displayed in the Alarm
Exists check box in the DOP header, and/or the DOP order window(s). In addition,
the alarms are displayed in the
Alarms tabs in the
DOP Header,
DOP Order and the
DOP Order Alarms
windows.
The alarms are created in the Not Acknowledged
status. When the alarm has been noticed, the status can be changed to Acknowledged
using the right mouse button menu.
To solve a Time alarm, you can right-click and
then click Adjust Date in the
DOP Header/Alarms,
DOP Order/Alarms,
DOP Order/Component Alarms tabs or
the DOP Order Alarms window.
To solve a Quantity alarm, you can right-click
and then click Adjust Quantity in the
DOP
Header/Alarms,
DOP Order/Alarms,
DOP Order/Component Alarms
tabs or the DOP Order Alarms window. Note that you cannot solve the alarm by updating the quantity
directly on the pegged supply order.
The Configuration alarm only appears on the parent
order and happens when a mismatch has occurred between the configuration defined
from the customer order line and the configuration from which the DOP structure
was created. To solve a Configuration alarm, you can right-click and then click
Update Supply Configuration or Unpeg Customer Order Line in the
DOP Header/Alarms tab. Note that it is not possible to acknowledge a
Configuration alarm; it must be solved before processing the DOP header and
connected DOP orders.
DOP Alarm Types
Five types of alarms exist for a DOP order;
- Time alarm - A DOP order supply is late, i.e., the delivery date of a
pegged order or the delivery date for an excess part on another DOP order is
later than required in order to meet the demand date. This means that the
date required is earlier than the delivery date or today's date. DOP
lead-time uses a Manufacturing calendar, where as Purchasing module uses the
Distribution calendar. In a situation where both these calendars differ,
incorrect alarms could be created.
- Quantity alarm - A DOP order supply is not enough to meet the demand of
the DOP order. This can occur due to extensive scrapping on a shop order,
the inability of a supplier to deliver the quantity ordered on a purchase
order, erroneous inventory balance corrected on counting, or that a
sufficient supply has not been ordered. All this means that the supplied
quantity (the quantity reserved in inventory or on pegged orders) is less
than the quantity required.
- Structure Revision alarm - The due date for a DOP order is not within
the effective date range of its structure. This can occur if due date for a
DOP is updated.
- Routing Revision alarm - The due date for a DOP order is not within the
effective date range of its routing. A change to the due date for a DOP
order might cause this alarm to be generated.
- Configuration alarm - A mismatch has occurred
between the configuration defined for a customer order line and the
configuration of the supplying DOP header. This can occur if the planned
delivery date of the customer order line was changed in a way that the
configuration must be reconfigured on the base of another part configuration revision
than the original. If such reconfiguration is required, a mismatch occurs
between the configuration defined for the customer order line and the DOP
header configuration. Therefore, it is not possible to supply the customer
order line with what is actually requested and the supply will deviate.
Automatic Alarm Generation
Alarms are automatically generated when date, quantity, configuration
mismatches exist between demand orders and supply orders with a DOP structure,
or if no valid structure- and/or routing revision exists for a part to be
processed on an order in the DOP structure. The demand and supply relationships
within a DOP structure are:
Demand |
Supply |
CO Line |
DOP Header |
DOP Header |
DOP Order |
DOP Order |
Pegged Order (Shop Order, Purchase
Requisition/ Order); Inventory Reservation; DOP Order; DOP Order Excess |
Note: The Quantity and
Configuration alarms are generated with alarm source related to the Demand.
Time, structure- and/or routing revision alarms are generated with alarm source related to the Supply.
Date Alarms
An alarm is generated when:
- There is a mismatch between the planned shipping date
of a customer order line and the due date of a DOP header. The alarm
indicates the number of days the due date is earlier or later than the
planned ship date. When a DOP header is connected to multiple customer order
lines, the alarm is generated for the customer order line with the earliest
planned shipping date. When a customer order line is connected to multiple DOP headers, an alarm is generated for each date mismatch that exists
between the customer order line and a DOP header.
- There is a mismatch between the due date of a DOP
header and the revised due date of its top DOP order.
- There is a date mismatch between a DOP order and
its supply orders. This may occur when the due date is changed on the DOP
order, a supply order or when propagating date changes downstream or
upstream.
- There is a date mismatch between a DOP order and
another DOP order which supplies it due to netting.
- There is a date mismatch between a DOP order and another DOP. One DOP
order could be in sync with its supply but out of sync with a demanding DOP
Order up in the structure.
Quantity Alarms
An alarm is generated when:
- There is a quantity mismatch between a DOP header
and its top DOP order.
- There is a quantity mismatch between a DOP order
and its supply orders. This may occur when the quantity is changed on
the DOP order, a supply order or when propagating quantity increases or
decreases.
- A return is recorded for a purchase order
connected to a DOP order.
- Scrap is recorded for a purchase order connected
to a DOP order.
- A substitute part is received for a shop order
connected to a DOP order.
- Scrap is reported for a shop order connected to a DOP order.
- There is a quantity mismatch between a DOP order
and its netted quantity.
- There is a quantity mismatch between a DOP order
and another DOP order which supplies it due to netting.
- A supply order is unpegged from a DOP order.
- There is a quantity mismatch between a DOP order and another DOP. A DOP
order could be in sync with its supply but out of sync with a demanding DOP
Order up in the structure.
Note: If multiple DOP headers are connected to the customer order line, the DOP header with the lowest status gets the alarm.
When a purchase order or shop order is connected to DOP
orders, the alarm is generated for the DOP order with the latest
due date. If the DOP orders have the same due date, the alarm is generated
for the DOP order with the highest DOP ID.
The quantity alarms are automatically removed when a
reversal action for scrap, returns, or substitute receipts is done for the
supply order.
Configuration Alarms
A configuration alarm is generated when there is a
mismatch between the configuration defined for a customer order line and the
configuration for the supplying DOP header. A change in the planned delivery
date of the customer order line might cause this alarm to be generated since
that could require a reconfiguration.
Structure or Routing Revision Alarms
A structure or routing revision alarm is generated when
the due date for a DOP order is not within the effective date range of either
its structure or routing revision. A change to the due date for a DOP
order might cause this alarm to be generated.