View engineering assembly document attachments

You can view assembly documents related to manufacturing that are attached to an engineering bill of materials (EBOM) as "reflective" attachments for EBOM line items assigned to a manufacturing bill of materials (MBOM) and a bill of process (BOP). A variety of preferences let you reflect datasets from an MBOM install assembly item level.

Procedure

1. To enable engineering assembly document attachments, use the preference MEDatasetsToBeReflectedOnBOP to set dataset-relation pairs to Dataset_internal_name:relation_internal_name (one per line).

This preference defines the dataset type and relation pairs that should be reflected from EBOM to MBOM and BOP lines. If there is a root relation between the EBOM and BOP with METarget, document attachments are reflected from the EBOM root to the BOP root. Example PDF:Iman_Specification PDF:IMAN_reference

2. Open a collaboration context (CC) Teamcenter object that contains an EBOM and an MBOM, as well as a BOP that contains line items with engineering assembly document attachments consumed from the EBOM or MBOM.

In this example, line item 39 is consumed from the EBOM to the MBOM and from the MBOM to the BOP.

Note Line item 37 in the EBOM is directly assigned to process 43 in the BOP, skipping the MBOM. Assembly document attachments are reflected in the BOP whether they are assigned from EBOM to MBOM to BOP, or from EBOM to BOP.

Attachments to a parent in the EBOM are reflected to be displayed one level up in the BOP hierarchy. For example, an attachment to EBOM line item 36, A_ref_pdf_e1..., shown in the EBOM Attachments tab below left, is reflected as the attachment A_ref_pdf_e1DocAss... to new line item 43 in the BOP Attachments tab, below right, because 37 is one level lower than line item 43.

Note

If a relation between the EBOM root and BOP root was created using the Link/Associate command, the attachment is displayed at the same level of each structure's root.

If the revision number of an EBOM assembly line changes, attachments reflect the new revision name in the EBOM, MBOM (if applicable), and BOP.

3. To reflect datasets for specific parent item types, use the preference MEAssemblyItemTypesForDatasets.

   The value format Item_type_internal_name (one internal item type per line) defines the preferred types of installable assemblies for a parent type. Instead of picking the documents from the immediate parent assembly, Teamcenter retrieves them from the closest parent whose type matches the preferred type, or a subtype of the preferred type. To further filter this preference, define the additional preference MEParentAssemblyItemTypesForDatasets. For the datasets to be retrieved, the closest parent and "grandparent" types must match the combination defined in both preference MEParentAssemblyItemTypesForDatasets and prefererence MEAssemblyItemTypesForDatasets. Note The MBOM assembly is traversed only one level below to find the EBOM line.

In this example, the grandparent value is Company. Under parent assembly 38, the MEAssemblyItemTypesForDatasets value Company shows document EBOP datasets for the grandparent company on line item 35. MEAssemblyItemTypesForDatasets goes to the closest parent of the immediate parent that matches the preference.