Results for “okl_asset_pools_v”

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

Overview

OKL_ASSET_POOLS_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module. Its documented purpose is to expose the asset pool definition data stored in the base table OKL_ASSET_POOLS_B, enriched with the translatable descriptive columns (name and description) held in OKL_ASSET_POOLS_TL. In release 12.1.1 and 12.2.2, asset pools are the grouping construct used to organize leased assets for depreciation, tax, and accounting treatment and to drive residual and end-of-term processing.

The view presents a denormalized, join-complete record of each asset pool, including its effective-dating pair (DATE_EFFECTIVE and DATE_INEFFECTIVE) and lease-specific indicators such as SFWT_FLAG and TAX_PERIOD_DAYS. As a view, it provides a read-only, reporting-friendly projection of the underlying tables, shielding consumers from having to perform the base/detail-language join manually and ensuring that description columns are returned in the session's language. Because it is a non-key-preserved or key-preserved reporting view rather than an application form block, its typical role is as a query target for custom reports, Oracle Discoverer, BI Publisher data models, and integration extracts.

Underlying Base Objects

The view is defined over two documented base objects:

• OKL_ASSET_POOLS_B — the primary (base) table holding the operational asset pool definition. The view alias APLB supplies all non-translatable columns and the row identifier.
• OKL_ASSET_POOLS_TL — the translation table for asset pool descriptive text, alias APLT. It is joined on matching ID and restricted to the session language via APLT.LANGUAGE = USERENV('LANG').

The join condition APLB.ID = APLT.ID links each base pool row to its language-specific name and description. Because the language predicate is applied inside the view, every query returns exactly one name/description row per pool for the current user language environment. Repository metadata for ETRM 12.2.2 lists the referenced base objects as "none documented" for the derived view, meaning the join lineage above is the authoritative structural definition rather than a separately registered dependency. The B/TL pairing follows Oracle's standard MLS (Multi-Lingual Support) table pattern.

Key Columns

Key columns exposed by the view are listed below. The user's search term, date_ineffective, corresponds to the DATE_INEFFECTIVE column, which is central to effective-dated querying of asset pools.

• ROW_ID — the physical ROWID of the base row, useful for DML by other views or for de-duplication.
• ID — the primary key of the asset pool.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency version number.
• NAME and DESCRIPTION — translated text sourced from OKL_ASSET_POOLS_TL.
• SFWT_FLAG — a lease-module indicator (short first work term / related flag) carried on the asset pool.
• TAX_PERIOD_DAYS — the number of days used to define the tax period for the pool.
• DATE_EFFECTIVE and DATE_INEFFECTIVE — the effective-dating range. DATE_EFFECTIVE marks when the pool record becomes active; DATE_INEFFECTIVE marks when it ceases to be active. A NULL DATE_INEFFECTIVE conventionally indicates the currently effective record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS flexible descriptive attribute columns for user-defined extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns.

Common Use Cases and Queries

Typical uses include listing all currently active asset pools for a given date, extracting pool configuration for reconciliation with depreciation and tax calculations, and generating translated pool listings for localization reporting. Because DATE_INEFFECTIVE is the effective-dating end marker, most queries filter on it to isolate active records.

Example: retrieve all currently effective asset pools.

• SELECT id, name, description, tax_period_days, date_effective, date_ineffective FROM okl_asset_pools_v WHERE date_ineffective IS NULL ORDER BY name;

Example: query asset pools effective as of a specific date.

• SELECT id, name, date_effective, date_ineffective FROM okl_asset_pools_v WHERE date_effective <= :as_of_date AND (date_ineffective IS NULL OR date_ineffective > :as_of_date);

Example: extract pool name and a flexible attribute for integration.

• SELECT id, name, attribute1, last_update_date FROM okl_asset_pools_v WHERE sfwt_flag = 'Y';

Because the view filters OKL_ASSET_POOLS_TL by the session language, callers benefit from translated names automatically; there is no need to add a LANGUAGE predicate. Standard EBS access and security rules apply to the underlying OKL tables.