Results for “okl_asset_pools_b”

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

Overview

OKL_ASSET_POOLS_B is the base table that defines asset pools within the Oracle Lease and Finance Management (OKL) module. An asset pool is a grouping construct used to aggregate leased or financed assets so that they can be managed, valued, and reported on collectively — for example, for pool-level accounting, residual or depreciation treatment, and investor or funding reporting. In Oracle EBS 12.1.1 and 12.2.2 this object belongs to the OKL product family and, like many OKL base tables, follows the _B naming convention denoting the base entity that typically has a companion _TL translation table for descriptive/name attributes.

The ETRM metadata records the primary key as OKL_ASSET_POOLS_B_PK, defined on the ID column. The metadata classifies this object as hub-leaning using a Data Vault heuristic derived from its foreign-key structure. In practical modeling terms, this suggests treating OKL_ASSET_POOLS_B as a hub: a stable, business-independent key holder (ID) around which link and satellite structures — such as the relationship to pooled assets — can be organized. This is a modeling suggestion rather than a physical Data Vault implementation, but it reflects the table's role as a central anchor for pooled asset associations.

Key Information Stored

The ETRM metadata documents the primary key and foreign-key relationships; it does not enumerate every descriptive column. The most significant attributes, as documented or implied by the structure, include:

• ID — the surrogate primary key, defined by constraint OKL_ASSET_POOLS_B_PK. This is the unique identifier for each asset pool row and the anchor used by dependent tables.
• Business-key candidates — in OKL base tables, a pool is typically further identified by a pool name/number stored in a companion translation table (e.g., OKL_ASSET_POOLS_TL or a name column), while the _B table holds the operational key. Only the surrogate key is confirmed by the supplied metadata.
• Pool definition/attributes — the base table carries the attribute columns that define the pool's characteristics (pool type, status, effective dates, accounting/valuation references). These are referenced indirectly through the table's role as parent of pooled assets.
• Relationship key — the ID column is the value referenced by OKL_POOLED_ASSETS.APL_ID, linking each pool to its member pooled assets.

The documented foreign-key relationship shows OKL_ASSET_POOLS_B as the parent (referenced) table and OKL_POOLED_ASSETS as the child, with OKL_POOLED_ASSETS.APL_ID pointing to the pool's primary key. This confirms the hub role described above.

Common Use Cases and Queries

Typical usage centers on retrieving pool headers and their member assets. A parent-child join is the most common pattern:

• Listing pooled assets for a given pool: SELECT p.ID, a.APL_ID, a.* FROM OKL_ASSET_POOLS_B p JOIN OKL_POOLED_ASSETS a ON a.APL_ID = p.ID WHERE p.ID = :pool_id;
• Pool-level reporting, such as aggregating asset counts or values per pool for accounting and investor reporting, driven from the pool header and joined to pooled asset detail.
• Resolving a pool for a given pooled asset (reverse lookup) using OKL_POOLED_ASSETS.APL_ID back to OKL_ASSET_POOLS_B.ID.
• Integration or reconciliation queries where pool IDs are exchanged with upstream transaction systems and validated against the base table.

Because the metadata notes "Not implemented in this database," availability of this table depends on whether the OKL Asset Pool feature is licensed and installed in the specific environment.

Related Objects

The most significant related object documented is the child table; others are inferred from OKL conventions and should be verified in the data dictionary.

• OKL_POOLED_ASSETS — primary dependent table; joins via OKL_POOLED_ASSETS.APL_ID = OKL_ASSET_POOLS_B.ID.
• OKL_ASSET_POOLS_TL — translation/descriptive companion (inferred), keyed on the same ID.
• OKL_ASSET_POOLS_B_PK — the primary-key constraint that enforces uniqueness of ID.
• OKL Lease/Finance Management APIs — public OKL APIs and concurrent programs that create and maintain asset pools and pooled asset assignments.
• Account/valuation and reporting views in OKL that consume pool and pooled-asset data for financial reporting.

The documented FK structure establishes OKL_ASSET_POOLS_B squarely as the hub referenced by OKL_POOLED_ASSETS, anchoring pool-to-asset associations within the OKL data model.