Search Results comp_primary_uom

Overview

APPS.BOM_STRUCTURE_SYNC_V is a denormalized reporting and integration view owned by the APPS schema within the Oracle Bills of Material (BOM) product. Its documented purpose is to support structure synchronization operations with external systems; the ETRM metadata indicates it is currently used for Complex Product Sync with Siebel for the Genesis Project. The view flattens the exploded bill of material hierarchy into a row-per-component structure, then decorates each row with item-level descriptive and planning attributes for both the assembly and the component, together with operating unit and inventory organization context. In Oracle EBS 12.1.1 and 12.2.2, such a view serves as a stable interface surface, shielding downstream consumers from the multiplicity of joins required across BOM_EXPLOSIONS, item master views, and HR organization tables. It is not a transactional table and holds no data of its own; it is a query-only object typically granted to integration and reporting responsibilities.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

• BOM_EXPLOSIONS — the driving source of the structure; supplies assembly, component, bill sequence, sort order, plan level, and effectivity information.
• MTL_SYSTEM_ITEMS_VL — a view over the item master, joined twice (aliased I1 for the assembly and I2 for the component) to supply segment concatenations, descriptions, and item-level flags such as CUSTOMER_ORDER_FLAG and CUSTOMER_ORDER_ENABLED_FLAG.
• HR_ALL_ORGANIZATION_UNITS_TL — provides the operating unit name translated for the current session language.
• HR_ORGANIZATION_INFORMATION — supplies the classification and organization relationships that tie inventory organizations to operating units.
• MTL_PARAMETERS — provides the inventory organization code and organization context.

Joins are keyed on inventory item ID and organization ID, with the NVL expression on ASSEMBLY_ITEM_ID and COMPONENT_ITEM_ID ensuring assembly and component rows resolve to the correct item master record.

Key Columns

Structural columns include ASSEMBLY_ITEM_ID, ORGANIZATION_ID, SORT_ORDER, PARENT_SORT_ORDER, PLAN_LEVEL, EXPLODE_GROUP_ID, TOP_ITEM_ID, TOP_BILL_SEQUENCE_ID, BILL_SEQUENCE_ID, COMPONENT_ITEM_ID, COMPONENT_SEQUENCE_ID, COMPONENT_QUANTITY, EFFECTIVITY_DATE, DISABLE_DATE, and COMP_BILL_SEQ_ID. Assembly attributes are exposed as ASSEMBLY_ITEM_NAME, ASSEMBLY_ITEM_DESCRIPTION, ASSEM_CUSTORDERENABLED_FLAG, ASSEM_CUSTORDER_FLAG, ASSEM_EFFECTIVITY_CONTROL, ASSEMBLY_BOM_ITEM_TYPE, and ASSEM_PRIMARY_UOM. The corresponding component attributes are COMPONENT_ITEM_NAME, COMPONENT_ITEM_DESCRIPTION, COMP_CUSTORDERENABLED_FLAG, COMP_CUSORDER_FLAG, COMP_EFFECTIVITY_CONTROL, COMP_BOM_ITEM_TYPE, and COMP_PRIMARY_UOM. Context columns are OPERATING_UNIT_NAME, OPERATING_UNIT_ID, ORGANIZATION_CODE, and ORGANIZATION_NAME. The user-searched token comp_cusorder_flag corresponds to COMP_CUSORDER_FLAG, the component-level CUSTOMER_ORDER_FLAG sourced from MTL_SYSTEM_ITEMS_VL; it indicates whether the component item may be placed on a customer order. The adjacent COMP_CUSTORDERENABLED_FLAG indicates whether the customer order attribute is enabled at the item level.

Common Use Cases and Queries

Typical uses include feeding external product configurators, validating structure data before publishing to Siebel or another master, and producing assembly-to-component reports with full item descriptions. A representative query filtering on the customer order flag is:

• SELECT assembly_item_name, component_item_name, component_quantity, comp_cusorder_flag, effectivity_date, disable_date FROM apps.bom_structure_sync_v WHERE organization_id = :org_id AND comp_cusorder_flag = 'Y';
• Filtering by operating unit: SELECT assembly_item_name, component_item_name FROM apps.bom_structure_sync_v WHERE operating_unit_id = :ou_id;
• Extracting a single exploded structure: SELECT top_item_id, plan_level, sort_order, component_item_name FROM apps.bom_structure_sync_v WHERE top_bill_sequence_id = :bill_seq_id ORDER BY sort_order;

Because the view relies on BOM_EXPLOSIONS, results reflect the explosion parameters and effectivity at query time, and performance is best when queries are constrained by ORGANIZATION_ID or TOP_BILL_SEQUENCE_ID.