Search Results top_item_description

Overview

XNC_ORG_ITEM_BOM_V is a reporting view belonging to the XNC - Sales for Communications product family, a module that is obsolete in Oracle EBS 12.1.1 and 12.2.2. The view presents the bill of materials (BOM) or package structure associated with a given organization and inventory item. In practice, it exposes a denormalized, flattened result set in which each row pairs a parent assembly (the "top item") with one of its components, together with descriptive attributes for both sides of that relationship. This makes the view suited to reporting and integration scenarios where a consumer needs to enumerate the components, packages, or kits available for a particular organization/item combination without navigating the normalized BOM schema directly.

The defining characteristic of the view is its exposure of the parent assembly as TOP_ITEM_ID. The column name TOP_ITEM_ID is an alias applied to BOM_BILL_OF_MATERIALS_V.ASSEMBLY_ITEM_ID, so a search on "top_item_id" resolves to the assembled parent item rather than to any component. Because XNC is obsolete, the view should be regarded as legacy metadata; the ETRM documentation records that it is not implemented in the reference database, meaning it may not exist in every environment.

Underlying Base Objects

The ETRM metadata lists no referenced base objects directly, but the view text demonstrates that it is defined as a join across four underlying sources:

• BOM_BILL_OF_MATERIALS_V (aliased A) — supplies ORGANIZATION_ID, ASSEMBLY_ITEM_ID (aliased TOP_ITEM_ID), the bill DESCRIPTION, ALTERNATE_BOM_DESIGNATOR, and BILL_SEQUENCE_ID.
• BOM_INVENTORY_COMPONENTS_V (aliased B) — supplies COMPONENT_ITEM_ID, the component DESCRIPTION, and the BILL_SEQUENCE_ID used to relate components to their parent bill.
• MTL_SYSTEM_ITEMS_KFV (aliased C) — supplies PADDED_CONCATENATED_SEGMENTS as TOP_ITEM_NAME, keyed on ORGANIZATION_ID and INVENTORY_ITEM_ID matching the assembly.
• MTL_SYSTEM_ITEMS_KFV (aliased D, a second instance) — supplies PADDED_CONCATENATED_SEGMENTS as COMPONENT_ITEM_NAME, keyed on ORGANIZATION_ID and the component inventory item.

The join logic links A to B on BILL_SEQUENCE_ID, then resolves item names through two independent references to the key flexfield view. Because both parent and component item names derive from MTL_SYSTEM_ITEMS_KFV, the displayed names respect the organization-specific key flexfield concatenation. Organizations are constrained consistently across the assembly and component lookups through the shared ORGANIZATION_ID predicate.

Key Columns

• ORGANIZATION_ID — the inventory organization context for both the assembly and its components.
• TOP_ITEM_ID — the assembly inventory item identifier (aliased from ASSEMBLY_ITEM_ID); the parent item whose BOM is being reported.
• TOP_ITEM_NAME — the padded concatenated flexfield segments for the parent item.
• TOP_ITEM_DESCRIPTION — the description of the parent bill or assembly.
• ALTERNATE_BOM_DESIGNATOR — identifies an alternate BOM when multiple bills exist for the same assembly.
• BILL_SEQUENCE_ID — the internal key linking each parent bill to its component rows.
• COMPONENT_ITEM_ID — the inventory item identifier of the component.
• COMPONENT_ITEM_NAME — the padded concatenated segments for the component item.
• COMPONENT_ITEM_DESCRIPTION — the component description.

Common Use Cases and Queries

Typical scenarios include exploding a package into its constituent items, validating which components ship with a configured offering, and feeding downstream pricing or order-capture logic with BOM detail. A representative query retrieves all components for a parent item:

• SELECT TOP_ITEM_ID, TOP_ITEM_NAME, COMPONENT_ITEM_ID, COMPONENT_ITEM_NAME FROM XNC_ORG_ITEM_BOM_V WHERE ORGANIZATION_ID = :org_id AND TOP_ITEM_ID = :item_id;
• Add AND ALTERNATE_BOM_DESIGNATOR = :alt TO isolate a specific alternate bill where multiple BOMs exist.
• Join TOP_ITEM_ID back to MTL_SYSTEM_ITEMS or order lines to reconcile configured packages against ordered inventory.

Because the object is obsolete and documented as not implemented in the reference database, consumers should confirm its presence in the target instance and consider supported BOM views as replacements.