Exporting Associative BOM Report
You can export the equivalence status between eBOM and mBOM to an Excel report using the Export Associative BOM Report action. This report provides information about part equivalence, occurrence equivalence, and usage equivalence status for the selected node and its child nodes. To export an associative BOM report for all the parts in the upstream view, perform the following steps.
1. In the upstream view, select Export Associative BOM Report from the Tools menu. The Export Associative BOM Report window opens.
2. Select a report from the list and click OK.
The selected type of report is generated. The report provides the following information:
◦ Identity and line number of each part along with the equivalence status.
◦ Quantity of each part in part equivalence report and usage equivalence report.
◦ Reference designator of each part in the occurrence equivalence report.
Similarly, you can export an associative BOM report for all the parts in the downstream view by clicking > in the downstream view.
The report shows multiple rows for parts that have multiple occurrences.
The values shown in the Equivalence Status column of part equivalence report indicate the following:
◦ Equivalent: Equivalent link exists.
◦ None: Equivalent link does not exist.
◦ Unknown: Equivalence status is unknown.
◦ Self-equivalent: Equivalent part is reused from the upstream to downstream assembly.
◦ Out of date: Equivalent link does not point to the latest iteration of the downstream equivalent part.
◦ Implied equivalence: Equivalence is implied to exist as the upstream equivalent part is reused in the downstream assembly.
The values shown in the Occurrence Status column of occurrence equivalence report indicate the following:
◦ Consumed: Equivalent occurrence exists.
◦ Not consumed: Equivalent occurrence does not exist.
◦ Self-consumed: Equivalent occurrence is reused from the upstream to downstream assembly.
◦ Unresolved: Equivalent occurrence exists but the link is unresolved.
◦ Unknown: Equivalent occurrence status is unknown.
◦ Implied consumption: Equivalent occurrence is implied to exist between child parts as the upstream parent part is reused in the downstream assembly.
The values shown in the Usage Consumption Status column of usage equivalence report indicate the following:
◦ Consumed: Equivalent usage exists.
◦ Not consumed: Equivalent usage does not exist.
◦ Self-consumed: Equivalent usage is reused from the upstream assembly to the downstream assembly.
◦ Unresolved: Equivalent usage exists but the link is unresolved.
◦ Consumed in different context: Equivalent usage is consumed in a different context.
You can export custom reports or show custom columns in reports using delegates. For more information, see
Configuring Export Report Delegates.
Tools > in the downstream view.