Results for “okl_aging_bucket_lines_uv”

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

Overview

The view OKL_AGING_BUCKET_LINES_UV is an APPS-owned database view within the Oracle Lease and Finance Management (OKL) module. It is a user-facing (the "_UV" suffix denotes "User View") projection that consolidates aging bucket configuration data drawn from the Oracle Receivables aging engine with OKL-specific bucket attributes. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a read-only reporting and integration interface, allowing lease and finance applications to resolve bucket definitions, day ranges, and loss rates without directly querying the underlying transactional or setup tables.

Although the user query referenced ar_aging_bucket_lines, the OKL view does not simply expose that Receivables table. Instead, it joins AR aging bucket lines to the OKL bucket master, making it the preferred vehicle for aging-related analysis within Lease and Finance Management. The view's status is VALID, confirming that the metadata is active and current in the ETRM 12.2.2 data model.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms:

• AR_AGING_BUCKET_LINES (SYNONYM) — the Oracle Receivables table holding each aging bucket line, including its parent bucket ID, sequence number, and the number of days from and to which the bucket applies.
• OKL_BUCKETS (SYNONYM) — the OKL table that stores lease-specific bucket attributes such as version, effective dates, comments, and loss rate.

These two are joined with an outer join on AR.AGING_BUCKET_LINE_ID = BKTB.IBC_ID(+). This construction means every AR aging bucket line is returned even when no corresponding OKL bucket record exists; OKL columns become null in that case. This is significant for reconciliation, because aging structures originating in Receivables are surfaced regardless of whether an OKL bucket has been configured for them.

Key Columns

The view exposes the full column set from both source objects. Notable columns include:

• ROW_ID — the ROWID of the OKL_BUCKETS row, used for reliable row identification.
• ID / IBC_ID — identifiers for the OKL bucket and its link to the AR aging bucket line.
• VERSION, START_DATE, END_DATE — date-effective versioning that governs which bucket definition was active in a given period.
• LOSS_RATE — the OKL loss rate associated with the bucket, used in credit and exposure analysis.
• AGING_BUCKET_ID, AGING_BUCKET_LINE_ID, BUCKET_SEQUENCE_NUM — the Receivables aging bucket identity and its ordered position.
• DAYS_START, DAYS_TO — the day-range boundaries defining the bucket interval (for example, 1–30, 31–60, 61–90).
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, REQUEST_ID, and related traceability fields.

Common Use Cases and Queries

Typical uses include aging bucket setup validation, exposure and loss-rate reporting, and integration feeds that must map AR bucket lines to OKL bucket definitions. A simple listing query follows:

• SELECT aging_bucket_line_id, bucket_sequence_num, days_start, days_to, loss_rate FROM okl_aging_bucket_lines_uv ORDER BY aging_bucket_id, bucket_sequence_num;
• SELECT ibc_id, id, days_start, days_to FROM okl_aging_bucket_lines_uv WHERE start_date <= SYSDATE AND NVL(end_date, SYSDATE) >= SYSDATE; — returns currently effective bucket ranges.
• SELECT AR.aging_bucket_id, AR.days_start, AR.days_to, BKTB.loss_rate FROM okl_aging_bucket_lines_uv AR, okl_buckets BKTB WHERE ...; — used where callers must join back to OKL_BUCKETS explicitly.

Because the view carries no application logic beyond the join, it should be treated strictly as a query surface; direct DML is not supported and must be performed against the base tables.