Search Results aging_description

Overview

AR_CHARGE_SCHEDULE_HEADERS_V is an Oracle Receivables (AR) view owned by the APPS schema and stored within the E-Business Suite database. Its documented purpose is to present charge schedule header information, exposing the rows that define how charges are scheduled and segmented across aging buckets. The view joins charge schedule headers to tiered aging bucket definitions, returning both the raw foreign key and the denormalized, human-readable descriptions for the schedule header type and the associated aging bucket. Because it is a view rather than a base table, it carries no independent storage and inherits the read-only characteristics of its underlying objects.

In reporting and integration contexts, this view is consumed by concurrent programs, Oracle Reports, OAF/Forms-based inquiry pages, and custom extensions that need a joined, decode-ready representation of charge schedule data. The presence of the AGING_DESCRIPTION and AGING_BUCKET_NAME columns makes it particularly convenient for aging-related reporting without requiring the consumer to re-join AR_AGING_BUCKETS or invoke lookup decoding logic. The view is listed as VALID under ETRM 12.2.2 metadata and is available in both 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view definition selects from two primary sources combined with a package function. The documented referenced base objects are:

• AR_CHARGE_SCHEDULE_HDRS (accessed via synonym) — the driving table, aliased as A, supplying the schedule header identifier, schedule identifier, schedule header type, aging bucket foreign key, date ranges, status, the fifteen descriptive flexfield (DFF) attribute columns, and standard WHO audit columns.
• AR_AGING_BUCKETS (accessed via synonym) — aliased as B, joined on AGING_BUCKET_ID to supply the bucket name and description, exposed as AGING_BUCKET_NAME and AGING_DESCRIPTION respectively.
• ARPT_SQL_FUNC_UTIL (package) — its GET_LOOKUP_MEANING function is called to translate the SCHEDULE_HEADER_TYPE lookup code into a meaning, exposed as SCHEDULE_HEADER_MEANING.

The relationship is straightforward: the join is an inner equality join on AGING_BUCKET_ID. Consequently, charge schedule header rows whose AGING_BUCKET_ID does not resolve to a valid bucket are excluded from the result set. Results are ordered by SCHEDULE_ID and START_DATE.

Key Columns

• SCHEDULE_HEADER_ID — Primary identifier for the charge schedule header row.
• SCHEDULE_ID — Identifier of the parent schedule to which the header belongs; also the first sort key.
• SCHEDULE_HEADER_TYPE — Lookup code defining the nature of the schedule header.
• AGING_BUCKET_ID — Foreign key to AR_AGING_BUCKETS; the basis of the join.
• START_DATE / END_DATE — Effective date range of the header; START_DATE is the secondary sort key.
• STATUS — Current state of the schedule header.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segment values.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard concurrency and audit columns.
• SCHEDULE_HEADER_MEANING — Decoded meaning of SCHEDULE_HEADER_TYPE from the lookup utility.
• AGING_BUCKET_NAME — Name of the associated aging bucket.
• AGING_DESCRIPTION — Descriptive text of the aging bucket, the column most commonly targeted by users searching on "aging_description".

Common Use Cases and Queries

Typical scenarios include aging analysis, schedule maintenance reporting, and integration extracts requiring decoded bucket descriptions. A representative query listing active schedule headers with their aging bucket detail is:

• SELECT schedule_header_id, schedule_id, schedule_header_meaning, aging_bucket_name, aging_description, start_date, end_date, status FROM ar_charge_schedule_headers_v WHERE status = 'A' ORDER BY schedule_id, start_date;
• Filtering by aging bucket description: SELECT schedule_header_id, aging_description FROM ar_charge_schedule_headers_v WHERE aging_description LIKE '%30%';
• Joining flexfield attributes to other AR entities using ATTRIBUTE1 through ATTRIBUTE15 for customer-specific segment values.

Because access is through a synonym in the APPS schema, consumers should reference the view as APPS.AR_CHARGE_SCHEDULE_HEADERS_V or via the AR responsibility's standard synonym. As with all views over Receivables base tables, appropriate grants and read consistency apply; the view supplies no direct DML capability of its own.