Update DOP Header Supply Configuration
Explanation
This activity, preferably run as a background job, is used to modify
the configuration of a DOP header when an alarm exists for a configuration mismatch
between the DOP header and its pegged customer order line or mismatch between the DOP header and top DOP order. This activity performs
a complete rebuild of the DOP structure according to the modifications made
in the requested configuration from the customer order line or the configuration change affected to the standalone DOP Header.
The configuration alarm of type Configuration with source
Customer Order Demand or
DOP Header cannot be ignored or acknowledged, it
must be solved. Configuration alarm of type Configuration and
source Demand Site Customer Order can only be acknowledged
as it is an information DOP alarm for the supply site
to inform the user that a DOP alarm with source Customer Order Demand is expected
to be created later in the business flow. Therefore, it can be acknowledged
if necessary
before the new DOP alarm is created. If the DOP alarm with source Demand
Site Customer Order exists when the DOP alarm with source Customer
Order Demand is created, the Demand Site Customer
Order DOP alarm will be replaced.
As long as a DOP alarm of type Configuration exists, all
shop orders, purchase requisitions, and purchase orders will be locked and cannot
be processed until the alarm is solved or acknowledged.
To perform the activity, click Update Supply Configuration on
the DOP Alarms page, the Alarms tab
on the DOP Header page or the Alarms tab
on the DOP Order page.
Prerequisites
- The DOP order and structure must have been created.
- Peggings must not exist on a shop order in the Started status.
- Peggings must not exist on a DOP order promoted to a status that is
not allowed to perform changes according to the update settings on the Details tab
on the DOP Order page.
- No reserved items are allowed for the customer order line for configuration alarm with source Customer Order Demand.
- The DOP header must have been connected to only one customer order line for configuration alarm with source
Customer Order Demand.
- An alarm must exist due to a configuration mismatch between the DOP header and its pegged customer order line or a mismatch between the DOP
header and the top DOP order.
In addition to the above prerequisites only for the customer order supply DOP orders, if the flag Allow Configuration
Changes for Started Supplies is enabled on the
Site/Manufacturing page in the
Configuration Change Management Settings section:
- Peggings can exist on a shop order in the Started status
if the affected started supply order has not been received to the parent DOP
order or is reserved on the Temp Inventory tab.
- If affected orders connected to the configuration change request are
started, the latest connected Configuration Change Request
status must be Approved, Completed, or
Cancelled.
System Effects
- Any existing alarms for a configuration mismatch between the DOP header and its pegged customer order line will be resolved for configuration alarm with source
Customer Order Demand.
- The configuration will be updated in the DOP Header.
- Any existing alarms for a configuration mismatch between the DOP header and its top DOP order line will be resolved for configuration alarm with the source
DOP Header.
- The configuration will be updated in the top DOP order.
- The changed configuration is promoted to the DOP header from the customer
order line. In standalone DOP orders, the configuration is promoted to the top DOP order from the DOP
header.
The DOP structure is completely rebuilt, taking into consideration the modifications made. Any manual modifications made to the DOP structure will be removed.
- If the configuration change is done only for informational
characteristics, solving the configuration alarm will not remove the
manual modifications. The reason for this is that changing only an
informational characteristic does not affect the physical product or the
configuration ID.
- The Structure Changed will be displayed on the Details
tab on the DOP Header
page for the parent DOP order.
- The whole DOP structure will be recreated, and new DOP orders and
their supplies
will be recreated with the new configuration ID for each level in the DOP
structure with new BOM unless the status is started or closed.
- Started and closed DOP orders affected by the configuration
change will be recreated with a new DOP ID and existing pegged orders will
be re-pegged to the new DOP order.
- Started DOP orders and supplies that are not affected by the configuration
change are ignored. DOP ID and Supply ID remain unchanged.
- Closed supplies that are not affected by the configuration change
remain as they are in the DOP structure.
- DOP orders might not be recreated as they are not needed in
the new configuration. These DOP orders will be disconnected from the current
sub DOP level and reconnected to the top DOP order. This is done since
the product/DOP order is not needed in the structure, and the user must first manually
unpeg the supply Shop Order and then close the DOP order to remove it completely.
- DOP log related to configuration changes will be cleared.
Additionally, if the flag Allow Configuration Changes for Started Supplies
is enabled on the Site/Manufacturing
page in the Configuration Change Management Settings
section and only for the configuration alarm with source Customer Order Demand;
- Configuration ID will be updated on the DOP order and the supply order
if the supply order is started on this level and is affected by the
configuration change.
Note:
- Changed supply
material and operations will not be updated automatically, an update of
a
bill of material must be done manually.
- Suppose a new
supply order is created in Planned status with the new configuration ID
and no receipt on any previously started supply orders has been done. In
that case, the user needs to decide whether to continue with the existing
started supply or to use the newly created supply order. The supply
order which is not required should be unpegged.
- Configuration ID on closed supply shop order will not be updated.
- Material, operations, work guidelines and tools are created based on the new configuration ID for
any newly created supply orders.
- The propagate quantity upstream command should be performed for the
DOP orders that have started supplies and are affected by the
configuration change to have the correct quantities in component DOP
orders. The supplies should be handled manually to solve the quantity
alarms generated.
- When there is a reservation for a component (configurable
part) with the old configuration in the temp inventory, the user
must first unreserve the part from the temp inventory before
resolving the DOP alarm. This action is necessary as the
configuration ID will be updated on the connected supply order.
- When there's a reservation for a component (configurable
part) with the old configuration on the parent part, the user
must unpeg the parent DOP parts supply order before resolving
the DOP alarm, as the configurable component with the old
configuration ID is part of the parent DOP order.
- The due dates and start dates are set for each DOP order in the
structure. For
information on how this is done, see
Plan DOP Orders.
- If the site has Schedule and Create Load for DOP Order
Operations enabled, machine and labor load of source Scheduled DOP are created for
the DOP order operations based on the quantity remaining to supply
on the DOP orders, plus the planned supply scrap for that quantity. This
applies to DOP orders with manufactured parts that have the status
Unreleased or Netted and Create Pegged set to
Pegged Orders.