Results for “okl_itm_cat_rv_prcs_v”

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

Overview

OKL_ITM_CAT_RV_PRCS_V is a wrapper view owned by the APPS schema in Oracle Lease and Finance Management (OKL), a module within Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the residual value processing data associated with catalog items used in lease contracts. The view is documented as VALID in the ETRM metadata for release 12.2.2 and is intended as a presentation-layer object that abstracts direct access to its underlying table. Because it is a wrapper view, it contains no independent logic, filters, or joins beyond simple column projection; its primary role is to provide a stable, read-oriented interface for reporting, concurrent programs, and integration components that require residual value processing information without directly referencing the base table.

Underlying Base Objects

The view is defined exclusively over OKL_ITM_CAT_RV_PRCS, a table in the OKL module referenced in the metadata through a synonym. Every column in the view maps directly to a column of the same name in the base table, with the single exception of the ROWID pseudocolumn, which is aliased as ROW_ID. The view text also introduces several null placeholders that have no corresponding base-table source: CAT_ID1, CAT_ID2, TERM_IN_MONTHS, and RESIDUAL_VALUE_PERCENT are defined with TO_NUMBER(NULL) or NULL. These are structural placeholders rather than functional data columns. All record identifiers, status codes, version numbers, date ranges, audit columns, and descriptive flexfield attributes (ATTRIBUTE1 through ATTRIBUTE15) are taken directly from the base table.

Key Columns

The following columns are of principal interest to developers and report authors:

• ROW_ID — the physical ROWID of the base-table row, available for row-level addressing and deduplication.
• ID — the primary identifier of the residual processing record.
• OBJECT_VERSION_NUMBER — the optimistic locking version, used by the framework to detect concurrent updates.
• ITEM_RESIDUAL_ID — the identifier linking the record to the item residual definition.
• STS_CODE — the status code governing whether the processing record is active, inactive, or otherwise constrained by lifecycle rules.
• VERSION_NUMBER — the business version of the residual processing record.
• START_DATE and END_DATE — the effective date range during which the record applies.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments for customer-specific extensions.
• CAT_ID1, CAT_ID2, TERM_IN_MONTHS, RESIDUAL_VALUE_PERCENT — placeholder columns always returned as NULL in the current definition.

Common Use Cases and Queries

The view is typically consumed by operational reports that list residual value processing records for catalog items, by data-extraction programs feeding downstream systems, and by diagnostic queries during implementations or upgrades. A basic query follows:

• SELECT id, item_residual_id, sts_code, version_number, start_date, end_date FROM okl_itm_cat_rv_prcs_v WHERE sts_code = 'ACTIVE' ORDER BY start_date;
• SELECT id, item_residual_id, object_version_number FROM okl_itm_cat_rv_prcs_v WHERE end_date >= SYSDATE;
• SELECT id, attribute_category, attribute1, attribute2 FROM okl_itm_cat_rv_prcs_v;

Because the view exposes the ROWID and the optimistic locking column, it can also be used in conjunction with the base table for controlled updates, although write operations are normally performed against OKL_ITM_CAT_RV_PRCS directly. Report authors should treat the NULL placeholder columns as reserved and avoid depending on them for business logic.