Search Results assem_primary_uom

Overview

APPS.BOM_STRUCTURE_SYNC_V is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes flattened bill-of-material (BOM) explosion data joined to descriptive item attributes for both the assembly and the component. It is defined over BOM_EXPLOSIONS, the multilingual item view MTL_SYSTEM_ITEMS_VL (aliased twice, i1 for the assembly and i2 for the component), HR_ALL_ORGANIZATION_UNITS_TL, HR_ORGANIZATION_INFORMATION, and MTL_PARAMETERS. The view is primarily consumed by external planning systems, shop-floor integration, and custom reports that must synchronize a BOM structure together with the item-level flags that govern whether an item may be placed on a customer order.

The name suffix "_SYNC" reflects its intended role as a synchronization interface: consumers receive assembly, component, quantity, effectivity, and organizational context in a single flat result set rather than traversing multiple EBS entities. This is directly relevant to the user's search for "customer_order_flag", since the view surfaces both CUSTOMER_ORDER_FLAG and CUSTOMER_ORDER_ENABLED_FLAG for the assembly and the component, aliased as ASSEM_CUSTORDER_FLAG/ASSEM_CUSTORDERENABLED_FLAG and COMP_CUSORDER_FLAG/COMP_CUSTORDERENABLED_FLAG respectively.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects, all resolved through APPS synonyms except the item view:

• BOM_EXPLOSIONS (SYNONYM) — supplies the core structural rows: assembly_item_id, component_item_id, organization_id, plan_level, sort orders, top_item_id, bill_sequence_id, component_quantity, and effectivity/disable dates.
• MTL_SYSTEM_ITEMS_VL (VIEW) — joined twice to derive concatenated_segments, description, CUSTOMER_ORDER_FLAG, CUSTOMER_ORDER_ENABLED_FLAG, effectivity_control, bom_item_type, and primary_uom_code for the assembly and component.
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — provides the operating unit name and identified operating unit.
• HR_ORGANIZATION_INFORMATION (SYNONYM) — supplies organization classification used to constrain the operating unit context.
• MTL_PARAMETERS (SYNONYM) — provides the organization_code exposed as both ORGANIZATION_CODE and ORGANIZATION_NAME.

The joins are keyed on organization_id and inventory_item_id, with the operating unit context established through HR_ALL_ORGANIZATION_UNITS_TL and HR_ORGANIZATION_INFORMATION.

Key Columns

• ASSEMBLY_ITEM_ID / COMPONENT_ITEM_ID — the item identifiers for the parent and child.
• BILL_SEQUENCE_ID / COMPONENT_SEQUENCE_ID / COMP_BILL_SEQ_ID — bill and component sequence identifiers used to trace structure.
• COMPONENT_QUANTITY — usage quantity per assembly.
• EFFECTIVITY_DATE / DISABLE_DATE — the effective window; the view filters on these conditions.
• PLAN_LEVEL / SORT_ORDER / PARENT_SORT_ORDER / EXPLODE_GROUP_ID / TOP_ITEM_ID / TOP_BILL_SEQUENCE_ID — explosion and sequencing context.
• ASSEM_CUSTORDER_FLAG / ASSEM_CUSTORDERENABLED_FLAG — customer-order eligibility for the assembly item (user's search term).
• COMP_CUSORDER_FLAG / COMP_CUSTORDERENABLED_FLAG — customer-order eligibility for the component item.
• ASSEMBLY_ITEM_NAME / COMPONENT_ITEM_NAME / descriptions — descriptive attributes from MTL_SYSTEM_ITEMS_VL.
• OPERATING_UNIT_NAME / OPERATING_UNIT_ID / ORGANIZATION_CODE — organizational context.

Common Use Cases and Queries

Typical uses include synchronizing BOM structures into external planning systems, validating that components on a bill are permitted on customer orders, and reporting organizational BOM content with item descriptions. A representative query isolating items flagged for customer orders is:

• SELECT ASSEMBLY_ITEM_NAME, COMPONENT_ITEM_NAME, COMPONENT_QUANTITY, COMP_CUSORDER_FLAG FROM APPS.BOM_STRUCTURE_SYNC_V WHERE ORGANIZATION_CODE = :org AND COMP_CUSORDER_FLAG = 'Y';
• Filter on organization_id and plan_level to restrict to a specific explosion level.
• Join back to per-assembly records using BILL_SEQUENCE_ID or COMPONENT_SEQUENCE_ID.

Because the view is not itself a table, consumers should apply predicates on organization_id and effectivity to keep result sets bounded and performant.