Results for “okl_asset_components_b”

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

Overview

The OKL_ASSET_COMPONENTS_B table resides in the OKL schema and belongs to the Oracle Leasing and Finance Management (OKL) module. It stores the component-level breakdown of assets that are assembled within a leasing quotation. Asset components are sourced from inventory items and are always created within the context of a Quoted Asset, meaning that every row in this table is anchored to an asset line held under a quote. This design allows lessors to represent a single leased asset as a structured collection of purchased or inventoried parts, each with its own cost, quantity, and supplier attributes.

From a modeling perspective, the metadata's heuristic Data Vault classification identifies this object as standalone. This suggests that OKL_ASSET_COMPONENTS_B functions as a self-contained entity whose lifecycle is governed by its parent asset rather than by a dense network of foreign key dependencies. It is best treated as a hub-like or standalone entity, with its operational context supplied by the asset and inventory masters it references.

Key Information Stored

The table contains 32 documented columns. The most consequential for functional and reporting purposes are:

• ID — the surrogate primary key, enforced by constraint OKL_ASO_PK and also the sole business-key candidate via the unique index OKL_ASSET_COMPONENTS_B_U1.
• ASSET_ID — links the component to its parent quoted asset.
• INV_ITEM_ID — identifies the inventory item from which the component was sourced.
• SUPPLIER_ID — the vendor supplying the component.
• PRIMARY_COMPONENT — flag indicating whether the component is the principal element of the asset.
• UNIT_COST and NUMBER_OF_UNITS — pricing and quantity attributes used in valuation and roll-up calculations.
• MANUFACTURER_NAME, YEAR_MANUFACTURED, and MODEL_NUMBER — descriptive equipment details.
• OBJECT_VERSION_NUMBER — the optimistic locking token used by the Oracle Applications Framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS flexfield extension columns for client-specific data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on asset valuation, component roll-up, and supplier analysis for quoted leases. A representative query totals component cost for each asset:

• SELECT asset_id, SUM(unit_cost * number_of_units) total_cost FROM okl_asset_components_b GROUP BY asset_id;
• Listing components of a single asset: SELECT inv_item_id, unit_cost, number_of_units FROM okl_asset_components_b WHERE asset_id = :asset_id;
• Identifying the primary component: ... WHERE asset_id = :asset_id AND primary_component = 'Y';
• Supplier concentration reporting grouped by supplier_id.

Reporting use cases include lease quotation detail extracts, asset build-of-materials reports, and cost reconciliation between quoted assets and inventory receipts.

Related Objects

The metadata classifies this table as structurally standalone, so documented foreign keys are limited. The primary relationships extend through the columns present:

• OKL_ASSET_COMPONENTS_B joins to its parent asset via ASSET_ID.
• INV_ITEM_ID references inventory item master data used to source the component.
• SUPPLIER_ID references the supplier master.
• The ID / OBJECT_VERSION_NUMBER pair supports OAF-based maintenance pages.

Because no explicit FK constraints are documented, referential integrity for these columns is enforced within the OKL application logic rather than at the database layer.