Results for “bom_odi_ws_components_v”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BOM_ODI_WS_COMPONENTS_V is an APPS-owned view in the Bills of Material (BOM) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It is part of the Oracle Data Integrator (ODI) web services layer that exposes Bill of Materials explosion data for external integration and bulk reporting. The view flattens the output of the BOM explosion engine, joining components to item master descriptions, revision data, and the session parameters supplied by the caller, so that downstream systems receive a single, denormalized result set of component lines for a given assembly and session.
The name and the presence of SESSION_ID indicate that the view is designed to be consumed in the context of a BOM explosion session registered in BOM_ODI_WS_ENTITIES. Rather than requiring the caller to iterate the BOM_EXPLOSIONS_ALL hierarchy directly, the view resolves the effectivity logic (date-based and revision-based) inline and returns the components that are valid for the session's explosion date and item revision code.
Underlying Base Objects
The view is defined over the following documented base objects:
- BOM_EXPLOSIONS_ALL (synonym) — supplies the exploded bill structure, including assembly, component, and operation sequence information.
- BOM_INVENTORY_COMPONENTS (view) — provides the component-level bill attributes used to construct the output rows.
- BOM_ODI_WS_ENTITIES (synonym) — the session/parameter source that yields
PARAMS.SESSION_ID,PARAMS.EXPLOSION_DATE, andPARAMS.ITEM_REV_CODE. - BOM_ODI_WS_REVISIONS (synonym) — supplies revision high dates used in the fixed-revision effectivity branch.
- MTL_ITEM_REVISIONS_B (synonym) — the base revision table (the object the user searched for), used in the revision effectivity subqueries to compare the explosion's revision code against the component or end-item revision.
- MTL_SYSTEM_ITEMS_KFV (synonym) — the concatenated-segments key flexfield view that produces
COMPONENT_ITEM_NAMEand the SEGMENT1–SEGMENT20 columns. - MTL_SYSTEM_ITEMS_TL (synonym) — the translation table providing
DESCRIPTIONandLANGUAGE.
The critical linkage to MTL_ITEM_REVISIONS_B occurs in the effectivity case expression, where the view compares PARAMS.ITEM_REV_CODE against the revision string returned for the end item, its organization, and its revision ID. This is what allows revision-controlled explosions to return only components effective at the requested revision.
Key Columns
- SESSION_ID — identifies the BOM explosion session; the primary filter for retrieval.
- ASSEMBLY_ITEM_ID, ORGANIZATION_ID — the parent assembly and its inventory organization.
- COMMON_BILL_SEQUENCE_ID, COMMON_COMPONENT_SEQUENCE_ID, COMPONENT_SEQUENCE_ID — bill and component sequence identifiers used to trace the row back to the bill definition.
- COMPONENT_ITEM_ID, COMPONENT_ITEM_NAME, ITEM_SEQUENCE_NUMBER — the component item key, its concatenated flexfield display name, and its sequence number on the bill.
- SEGMENT1–SEGMENT20 — individual key flexfield segments for the component item.
- DESCRIPTION, LANGUAGE — translated component description and language code.
- PRIMARY_UOM_CODE, PRIMARY_UNIT_OF_MEASURE, BASIS_TYPE, COMPONENT_QUANTITY — the usage quantity and its unit of measure basis.
- OPERATION_SEQ_NUM, AUTO_REQUEST_MATERIAL — routing operation reference and material auto-request flag.
- NEW_COMPONENT_CODE, COMPONENT_CODE — component classification codes returned by the explosion.
The inline CASE expression governs whether a row is returned under date effectivity (EFFECTIVITY_CONTROL = 1) or revision effectivity (EFFECTIVITY_CONTROL = 4), using TRIMMED_EFFECTIVITY_DATE, TRIMMED_DISABLE_DATE, and the revision comparisons against MTL_ITEM_REVISIONS_B.
Common Use Cases and Queries
Typical uses include extracting exploded BOMs for an integration payload, validating that revision-controlled structures resolve correctly after an item revision change, and auditing component usage across organizations. A representative query is:
SELECT component_item_name, component_quantity, primary_uom_code, operation_seq_num FROM apps.bom_odi_ws_components_v WHERE session_id = :p_session_id ORDER BY item_sequence_number;SELECT assembly_item_id, component_item_id, description FROM apps.bom_odi_ws_components_v WHERE organization_id = :p_org AND component_item_id = :p_item;
Because effectivity is resolved within the view, callers should pass the correct session and explosion parameters through BOM_ODI_WS_ENTITIES rather than attempting to re-implement the revision logic against MTL_ITEM_REVISIONS_B directly.
-
APPS.BOM_ODI_WS_COMPONENTS_V·↳ BOM_EXPLOSIONS_ALL·↳ BOM_INVENTORY_COMPONENTS·↳ BOM_ODI_WS_ENTITIES·Explore BOM module →
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.