Define update actions for parts with custom release status in a Usage BOM

After a Usage BOM and design structure are aligned with each other, some updates can be made to the design structure. In such a case, the aligned Usage BOM must also be updated. By default, certain BMIDE conditions are set to define how the Usage BOM must be updated. These conditions are defined for the default part maturity status.

If you have defined a custom release status for parts, you can update the appropriate BMIDE condition to include this custom release status. The condition that you need to update depends on the maturity level of the release status. For example, the default release status, TCM Released, represents the highest level of part maturity.

When a Usage BOM is updated, the BMIDE conditions are applied in a certain sequence (as shown in the table) in order to determine the update action to be taken on a part. Study this table to decide which condition you must update to meet your business requirement.

Design revised?	Part required?	Part aligned?	Part maturity	Assembly indicator	Condition	LOV	Update actions
No	This is the grandparent design and its skipped child is revised.	Yes	Yes	TCM Released	NA	StructureChangeOnSkipChild && (Pma0EnableRevisePartActionDesign || Pma0EnablePartChangeActionsOnDesign)	Pma0ReviseAndReusePartActionLOV
No	Yes	No	NA	NA	None	Pma0NewPartActionLOV	New
Yes	Yes	No	TCM Released	Configurable Assembly or Generic Part	Pma0EnablePartChangeActionsOnDesign	Pma0ReviseAndReusePartActionLOV	Revise
Yes	Yes	No	Not released	NA	Pma0EnableReusePartActionOnDesign	Pma0ReusePartActionsLOV	Reuse

For highest part maturity levels, you update the Pma0EnablePartChangeActionsOnDesign condition. For intermediate part maturity levels, you update the Pma0EnableRevisePartActionDesign condition. For lower part maturity levels, you update the Pma0EnableReusePartActionOnDesign condition. It is recommended not to update the default LOVs to get the desired results.

Example 1

Consider that you have defined a custom release status named Approved for parts. This release status is at the same maturity level as TCM Released. Therefore, you will update the Pma0EnablePartChangeActionsOnDesign condition to include the custom release status.

Function::INLIST("TCM Released", o.pma0AlignedPrtReleaseStatus, "name") OR Function::INLIST("Approved",o.pma0AlignedPrtReleaseStatus, "name")

During automated or guided update, if the following criteria is met, the part with Approved release status is revised. This is because the default update action is set as Revise.

Design revised?	Part required?	Part aligned?	Part maturity	Assembly indicator	Update actions
Yes	Yes	No	Approved	Configurable Assembly or Generic Part	Revise

Example 2

Consider that you have defined a custom release status named In Progress for parts. This release status is at the same maturity level as that of a part that is not yet released, which is the lowest maturity level. Therefore, you will update the Pma0EnableReusePartActionOnDesign condition to include the custom release status.

Function::INLIST("In Progress", o.pma0AlignedPrtReleaseStatus, "name")

During automated and guided update, if the following criteria is met, the part with In Progress release status is reused.

Design revised?	Part required?	Part aligned?	Part maturity	Assembly indicator	Update actions
Yes	Yes	No	In Progress	NA	Reuse