Carrying forward in-context attachments

If you work with source and target structures, when you assign structures from the MBOM to the EBOM, you can carry forward attachments that are associated in-context in the EBOM. The same information is available in the bill of processes (BOP), when MBOM occurrences with in-context information are assigned to the BOP.

Three preferences manage in-context attachments. One preference manages how in-context attachments from the MBOM are made available in the BOP. Your Teamcenter administrator sets the preference values. It is helpful to know how these preference values control the behavior of in-context attachments in your environment.

Caution

If preference values are not set, attachments are not carried over when you perform an assign operation.

• MEAssignAttachmentAndRelationToUseInCopyRule – indicates which datasets are carried forward as in-context attachments, and whether the datasets are treated as a reference or a copy. For example, set the value to DirectModel:IMAN_Rendering:Reference to carry forward flexible (deformable) parts as in-context attachments referenced in the MBOM.

• MEAssignAttachmentContext – sets the context for the in-context attachment of an assigned occurrence from the EBOM to the MBOM, as either set the top line of the MBOM or a direct parent of the occurrence assigned from the EBOM to the MBOM.

• MEAssignPropertiesInContext – carries forward the in-context overridden value of a property on an occurrence or its child in an EBOM when assigning that occurrence from the EBOM to the MBOM. This feature is supported for the absolute transform matrix (bl_plmxml_abs_xform) only.

• MEAssign_support_incontext_below_consumed – makes in-context datasets available as attachments and transforms overrides for child lines of consumed lines from the MBOM to the BOP.

Related Topics

• Reasons for creating an MBOM

• EBOM-MBOM preferences