About BOM Markups

Markups are required to implement changes for assemblies that are not in the Preliminary state. Two kinds of markups can be created in the Bill of Materials page Plant Preferences View: EBOM markups, which always require a CO to implement, or Plant BOM markups, which can be implemented using an MECO.

• If an MECO is used to implement only plant-specific changes, then the assembly item is added to the MECO as an affected item. In this case the value for the Requested Change attribute would be “For Update.”

  In this case, no new revision is created and changes are applied to the same released revision.

• If a CO is used to implement EBOM changes, then the assembly item is added to the CO as an affected item. In this case the value for the Requested Change attribute would be “For Revise.”

  In this case, a new revision is created and both the markups are applied to the new revision.

  Note: When there are both EBOM and plant changes in the Plant Preferences view, then both MECO and CO selection are required.

Both MECO and CO can be selected only when there are both EBOM and plant-specific changes. An EBOM markup is created for EBOM changes. A Plant BOM markup is created for plant-specific changes. The EBOM markup is attached to the CO. The Plant BOM markup is attached to the MECO. In this case, the MECO is released before the CO.

All “For Update” change orders must be released before any “For Revise” change orders.

The Affected Items page shows a "Prerequisite" column, which shows any "For Update" change orders that exist for a "For Revise" change object.

Once the change object releases, the Plant BOM markup is applied to the existing released revision, and the MBOM is updated using the same Plant BOM markup.

When there are both EBOM and plant-specific changes in the Plant Preferences view, then you must select a CO. If you select only an MECO, the following message is displayed:

EBOM changes exist. Please select CO.

All plant-specific changes under the Plant Preferences view are applied to the MBOM for the same plant.

Consider there are three plants assigned to the assembly, and plant changes are made as follows:

Plant-1 common changes

• For plant 1 S type is changed from unassigned to Push.
• CHILD-0000001 plant-specific attribute S type is changed for plant-1. After releasing the respective change order, the plant-1 MBOM will be updated as shown below. Child-000001 will be effected out by MCO-Out as shown below.

Plant-2 common changes

• In this case, Start Date and End Date for plant 2 are modified as shown below.
• After releasing the above changes using a change order, the corresponding MBOM will be updated as shown below.
• Child-000002 will be effected out by MCO-Out as shown below.

Plant-3 MBOM

• There will be no changes to the plant 3 MBOM since no EBOM or plant-specific changes are done.

Adding/Removing Alternates/Substitutes

• Adding or removing alternates and substitutes are not specific to the plants. These changes will be applied to the MBOM for all the plants. Depending on the Auth Status and Pref Rank values, these items will be selected for the particular plant in the MBOM.
• Plant-specific attribute changes to substitute/alternates are specific to the plants. These changes are applied to the MBOM for the particular plant.

This section details MBOM behavior with manufacturing responsibility changes.

New manufacturing responsibility assignment

The assembly can be associated to one or more manufacturing responsibilities at any state. An MECO or CO can be used to associate the manufacturing responsibility at any state and releasing the same generates the MBOM for the assembly. The assembly must be in the Release state to implement these change orders.

Remove manufacturing responsibility

Pending manufacturing responsibilities can be disconnected from the assembly. A manufacturing responsibility in the current state or for which an MBOM has already been generated cannot be removed from the assembly.

Bypass/inactivate/reactivate manufacturing responsibility

The main purpose of this feature is to allow plants to ramp up gradually when a major design change has taken place. Some plants can continue to build the old way, whereas other plants will build the new way. When the plants are ready they can reactivate the part to build it the new way.

• Bypass -- On the Create MCO and MCO Edit Details pages, you can select one or more plants to bypass a MCO implementation. When the related CA is completed, changes released by the CO for all the affected parts will be copied and marked as passive changes in all assigned plants that were marked as bypassed. In the case of plant bypass, the next MCO that affects the plant and is not bypassed includes the delta changes of the MCOs that bypassed this plant.
  Note: No change object is generated for bypass plants while releasing the changes order.

• Inactivate/Reactivate manufacturing responsibility -- Inactivating a part in a plant bypasses/suspends all changes to the plant until the part is reactivated. The next MCO that is sent to the plant on the reactivated part will include all delta changes since it was inactivated (the summary of the passive changes that occurred).

  Plants can be inactivated from the part’s Manufacturing Responsibility page.

  The below actions take place once the respective change orders are released:

  • An MCO is generated for each inactivated plant with parent as an affected item.
  • The latest sequence MBOM is effected out with the new nMCO that was created in the above step.