Results for “component_quantity”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKX_INV_COMPONENTS_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite environment. It belongs to the OKX product family, which is the Contracts Integration module, and is documented as a VALID object in ETRM 12.2.2 (matching the same behavior in 12.1.1). The view is described as exposing "Bill of material components," meaning it presents the component-level detail of bills of material (BOMs) in a flattened, read-only form suitable for downstream consumption by contract, order, and pricing integration flows. Because it is implemented as a view rather than a table, it stores no data of its own; it is a query transformation layer over the underlying BOM structures. This makes it particularly useful when integration programs or reports need to resolve a manufactured or configured item into its constituent components — for example, to build a contract line, validate a configuration, or price a kit. When a user searches for component_item_id, this view is the relevant object because it explicitly projects that column alongside the parent BOM identifiers.

Underlying Base Objects

According to the ETRM metadata, OKX_INV_COMPONENTS_V is defined over a single referenced base object: BOM_INVENTORY_COMPONENTS, which is itself documented as a view in the APPS schema. The view text is a straightforward projection:

SELECT IC.COMPONENT_SEQUENCE_ID, IC.BILL_SEQUENCE_ID,
       IC.COMPONENT_QUANTITY, IC.COMPONENT_ITEM_ID,
       IC.EFFECTIVITY_DATE, IC.DISABLE_DATE
FROM   BOM_INVENTORY_COMPONENTS IC

No joins, filters, aggregations, or calculations are applied. Consequently, the OKX view provides a stable, integration-friendly interface over the BOM component view without exposing additional logic. This simple pass-through design is intentional: it isolates the OKX integration layer from direct dependency on the BOM schema objects, allowing Oracle to refactor the underlying BOM view while preserving the OKX contract that consuming programs rely upon.

Key Columns

• COMPONENT_SEQUENCE_ID — The unique identifier (surrogate key) for each component row within a bill of material. It is the primary handle for a specific component occurrence and is commonly used in joins to component-level attributes.
• BILL_SEQUENCE_ID — The identifier of the parent bill of material to which the component belongs. It links each component back to its BOM header, enabling grouping of all components for a given assembly.
• COMPONENT_QUANTITY — The quantity of the component required per unit of the parent assembly. This value drives kit explosion, cost rollup, and configuration validation.
• COMPONENT_ITEM_ID — The inventory item identifier of the component itself (the child item). This is the column of primary interest when resolving which items make up a bill; it joins to the item master (MTL_SYSTEM_ITEMS_B) for descriptive and planning attributes.
• EFFECTIVITY_DATE — The date from which the component becomes effective in the BOM structure.
• DISABLE_DATE — The date on which the component is disabled (or NULL if still active), enabling date-effective reporting of BOM composition.

Common Use Cases and Queries

This view is typically used to explode a bill of material for integration, reporting, or validation. A frequent requirement is to retrieve all components for a given BOM sequence:

SELECT component_item_id, component_quantity,
       effectivity_date, disable_date
FROM   okx_inv_components_v
WHERE  bill_sequence_id = :p_bill_sequence_id;

To identify the current, active components as of a specific date, a date-bounded predicate is applied:

SELECT component_item_id, component_quantity
FROM   okx_inv_components_v
WHERE  bill_sequence_id = :p_bill_sequence_id
AND    effectivity_date <= SYSDATE
AND   (disable_date IS NULL OR disable_date > SYSDATE);

Integration developers also join the view to the item master to obtain component descriptions and UOMs, or to pricing and order tables during contract line generation. Because the view is a thin projection over BOM_INVENTORY_COMPONENTS, it inherits that view's performance characteristics and access controls; querying it directly avoids hard-coding the BOM base object name into OKX integration code, which is the principal architectural benefit this view provides.