Search Results ar_aging_buckets_pk

Overview

AR_AGING_BUCKETS is a Receivables module reference table that stores the header-level definitions of aging buckets used throughout Oracle E-Business Suite Receivables aging reports and related subledger accounting processes. Each row in AR_AGING_BUCKETS represents a named aging bucket set—for example, a standard "30/60/90/120" configuration or a custom domestic/international set—while the individual bracket lines (the day or period boundaries within that set) are held in the companion table AR_AGING_BUCKET_LINES_B. Together these two tables drive the "As of" aging reports, customer balance aging, credit management, and chargeback analysis.

The object resides in the AR schema and is owned by the Receivables product. In the documented 12.2.2 physical schema it contains 27 columns, carries a primary key constraint AR_AGING_BUCKETS_PK on AGING_BUCKET_ID, and a unique business constraint AR_AGING_BUCKETS_UK1 on BUCKET_NAME. The 12.2.2 edition includes a ZD_EDITION_NAME column, reflected in the unique index AR_AGING_BUCKETS_U1 on (AGING_BUCKET_ID, ZD_EDITION_NAME). From a heuristic Data Vault modeling perspective, this table is classified as hub-leaning: it is a stable, low-volatility list of business keys (the bucket sets) referenced by multiple downstream satellites and transactional tables.

Key Information Stored

The most significant columns documented for AR_AGING_BUCKETS are:

• AGING_BUCKET_ID — Surrogate primary key (AR_AGING_BUCKETS_PK); the value propagated to all child tables.
• BUCKET_NAME — Business-key candidate (AR_AGING_BUCKETS_UK1); the user-facing name of the aging bucket set.
• STATUS — Active/inactive indicator controlling whether the bucket set may be selected in aging reports and setup.
• AGING_TYPE — Classifies the aging method (for example, by due date, by transaction date, or by days past due) that the bucket set implements.
• DESCRIPTION — Free-form description of the bucket set for user reference.
• ZD_EDITION_NAME — Editioning discriminator introduced in the 12.2 online patching architecture; part of the AR_AGING_BUCKETS_U1 unique index.
• CREATED_BY, CREATION_DATE — Standard WHO audit creation columns.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit update columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield (DFF) columns allowing customers to store additional, site-defined bucket metadata.

The distinction between the surrogate key (AGING_BUCKET_ID) and the business key (BUCKET_NAME, and jointly with ZD_EDITION_NAME in AR_AGING_BUCKETS_U1) is important for integration and ETL: external extracts should compare on BUCKET_NAME, while all foreign-key joins use AGING_BUCKET_ID.

Common Use Cases and Queries

Receivables aging reports, credit management dashboards, and customer statement programs all reference this table to determine which bucket set to apply. Reporting queries typically join AR_AGING_BUCKETS to its child lines to retrieve both the set definition and its bracket boundaries:

• List active bucket sets: SELECT aging_bucket_id, bucket_name, aging_type FROM ar.ar_aging_buckets WHERE status = 'A';
• Retrieve lines for a named set: join AR_AGING_BUCKET_LINES_B on AGING_BUCKET_ID and filter by BUCKET_NAME.
• Identify the bucket set assigned to a charge schedule: join AR_CHARGE_SCHEDULE_HDRS on AGING_BUCKET_ID.
• Check credit management configuration: join AR_CMGT_SETUP_OPTIONS on AGING_BUCKET_ID.
• Analyse trade-management aging summaries: join OZF_AGING_SUMMARY_ALL and OZF_AGING_BUCKET_DATES on AGING_BUCKET_ID.

Because bucket definitions are configuration-grade reference data, ETL and data-migration routines should treat AGING_BUCKET_ID as the integration key and preserve BUCKET_NAME for reconciliation. In 12.2 environments, multi-tenant or multi-edition queries must include ZD_EDITION_NAME to avoid cross-edition row duplication.

Related Objects

The following tables are documented as referencing AR_AGING_BUCKETS via AGING_BUCKET_ID and are the most significant dependents:

• AR_AGING_BUCKET_LINES_B — Child table holding the individual aging bracket lines (day/period boundaries) for each bucket set.
• AR_CHARGE_SCHEDULE_HDRS — Charge schedule headers that assign an aging bucket set for dispute and chargeback aging.
• AR_CHARGE_SCHEDULE_LINES — Charge schedule lines inheriting the same aging bucket reference.
• AR_CMGT_SETUP_OPTIONS — Credit management setup, where the default aging bucket set is configured.
• OZF_AGING_SUMMARY_ALL — Trade Management aging summary facts that aggregate balances by bucket.
• OZF_AGING_BUCKET_DATES — Trade Management extension storing date attributes per aging bucket.

Setup and maintenance of these records is performed through the Receivables Aging Buckets setup form; no public PL/SQL API is documented for direct DML, so changes should be made through the standard Oracle Forms UI to preserve referential integrity with AR_AGING_BUCKET_LINES_B.