Search Results aging_type




Overview
Explore in AI Chat

Overview

APPS.OKL_AGING_BUCKETS_UV is a filtered database view in Oracle E-Business Suite 12.1.1 and 12.2.2, defined in the APPS schema. It exposes a restricted subset of aging bucket definitions used by Oracle Receivables and consumed by Oracle Lease and Finance Management (OKL). The view is classified as a "UV" (user view) and belongs to the Enterprise Territory and Resource Management / ETRM-documented object set.

The view presents only those aging bucket rows whose status is active, as enforced by the predicate WHERE STATUS = 'A'. This makes it a convenience object for reporting and integration scenarios that require the currently valid set of aging buckets without the need to filter inactive or obsolete definitions manually. Because it is defined over a public synonym of a core Receivables configuration table, it serves as a stable, read-only reference surface for aging bucket metadata at the OKL application tier.

Underlying Base Objects

The view is defined over a single referenced base object, documented in the ETRM metadata as AR_AGING_BUCKETS, accessed through a synonym. AR_AGING_BUCKETS is the Oracle Receivables configuration table that stores the aging bucket definitions used to categorize receivables balances by time period (for example, 0–30 days, 31–60 days, and so on). Each row represents one bucket, carrying an identifier, display name, status, aging type, and descriptive text.

OKL_AGING_BUCKETS_UV performs no joins, unions, or aggregations. Its definition is a simple projection of five columns from AR_AGING_BUCKETS, combined with the active-status filter. Consequently, the view carries no independent data of its own; every query against it resolves directly to the underlying Receivables table. The dependency is therefore one-to-one and purely logical, which means the view inherits the column data types, constraints, and referential relationships of AR_AGING_BUCKETS without modification.

Key Columns

  • AGING_BUCKET_ID — The primary identifier for the aging bucket. This is the unique key used to join bucket definitions to downstream aging and collection data.
  • BUCKET_NAME — The user-facing label of the bucket, typically describing a day range or aging interval.
  • STATUS — The record status of the bucket. Because the view filters on STATUS = 'A', every row returned carries the value 'A', denoting an active bucket.
  • AGING_TYPE — Identifies the aging classification or method associated with the bucket, allowing distinction between different aging schemes. This column directly answers the "aging_type" search term associated with this view.
  • DESCRIPTION — Free-form descriptive text providing additional explanation of the bucket's purpose or scope.

Common Use Cases and Queries

The view is commonly used in reporting, validation, and integration logic where only active aging buckets are relevant. Because it already restricts to active rows, consumers avoid redundant filtering and reduce the risk of reporting against retired definitions. Typical scenarios include aging reports, collections dashboards, and inbound data loads that must validate a bucket identifier or aging type before use.

The most direct query lists all active buckets:

  • SELECT AGING_BUCKET_ID, BUCKET_NAME, AGING_TYPE, DESCRIPTION FROM APPS.OKL_AGING_BUCKETS_UV;

To retrieve buckets for a specific aging type:

  • SELECT BUCKET_NAME, DESCRIPTION FROM APPS.OKL_AGING_BUCKETS_UV WHERE AGING_TYPE = :p_aging_type;

To look up a single bucket by identifier or name:

  • SELECT * FROM APPS.OKL_AGING_BUCKETS_UV WHERE AGING_BUCKET_ID = :p_id;
  • SELECT * FROM APPS.OKL_AGING_BUCKETS_UV WHERE BUCKET_NAME = :p_name;

Because the view resolves to AR_AGING_BUCKETS, it should be treated as read-only; maintaining bucket definitions is performed against the base table through the standard Receivables setup interface rather than through this view.