Use Case 9: Generate a Downstream Structure by Skipping a Part Based on Two Attributes

Prestaciones adicionales > Manufacturing Process Management > Transforming an eBOM into an mBOM > Creating an mBOM > Overview of Generate Downstream Structure Action > Use Cases: Generate Downstream Structure > Use Case 9: Generate a Downstream Structure by Skipping a Part Based on Two Attributes

Consider that the following structure is present in the BOM Transformer:

• An equivalent link exists between the Upstream Parent Part (Design) and Downstream Parent Part (Manufacturing).

• Part C1 (Design), Part C4 (Design), Part C5 (Design), Part C6 (Design), and Part C7 (Design) have the part usage attribute Attribute1 set to true.

Attribute1 is an attribute of type Boolean. In Windchill, the values for this attribute are Yes and No. true and false are synonymous to Yes and No, respectively.

• All the parts in the structure have the part type as wt.part.WTPart.

1. Access the associativity.properties.xconf file located in Windchill/codebase/com/ptc/core/foundation/associativity.

2. Add the following restructuring rules in the Windchill/codebase/com/ptc/core/foundation/associativity file:

After you initiate the

action on the selected part in the upstream, the Windchill system traverses the structure below the selected part. This configuration ensures that:

If the Windchill system detects a part in the upstream with the part attribute Attribute1 set to true, then it is transformed in the downstream under the part whose attribute CustomAttribute1 is set to String1. It is transformed as a new part

If the Windchill system detects a part in the upstream with the part attribute Attribute2 set as true and attribute Source set as Buy, then the part is skipped and is not added in the downstream. However, the structure below the detected part is traversed.

3. Select the Upstream Parent Part (Design and click

in the middle pane tool bar.

4. The following structure appears in the BOM Transformer:

• Part C2 (Design) is skipped as it satisfies the criteria set in the following properties.

◦ <AddToProperty name="com.ptc.windchill.associativity.reconciliation.addusage.wt.part.WTPart" value="skipAttribute.Source=Buy"/>

◦ <AddToProperty name="com.ptc.windchill.associativity.reconciliation.addusage.wt.part.WTPart" value="skipAttribute.Attribute2=true"/>

◦ <AddToProperty name="com.ptc.windchill.associativity.reconciliation.addusage.wt.part.WTPart" value="doAndValidationForAttr=true"/>

However, the system traverses the structure below it.

• Part C1 (Design), Part C4 (Design), Part C5 (Design), Part C3 (Design), Part C6 (Design), and Part C7 (Design) have the part attribute Attribute1 set to true. Hence, they are added as a new part under Part T1 (Manufacturing). Part T1 (Manufacturing) has part attribute CustomAttribute1 set to String1.

• No part is added under Part T2 (Manufacturing). This is because, its part attribute CustomAttribute1 is set toString2 .