Search Results ar_aging_bucket_lines_b_u1

Overview

The AR.AR_AGING_BUCKET_LINES_B table is a Receivables (AR) transaction data table that stores the individual aging period definitions used to group customer transactions on aging reports. Where the AR_AGING_BUCKETS table defines a named aging bucket set (for example, "Standard Collections Aging"), AR_AGING_BUCKET_LINES_B stores one row per interval within that set. A line such as "1 to 30 days past due" is persisted here with DAYS_START equal to 1 and DAYS_TO equal to 30. Oracle Receivables consumes both tables together whenever aging reports and aging-related concurrent programs are run.

The object is registered in FND Design Data as AR.AR_AGING_BUCKET_LINES_B, holds status VALID, and resides in the APPS_TS_TX_DATA tablespace with PCT Free 10. Under the 12.2.2 schema it exposes 28 columns, including the standard WHO audit columns, 15 descriptive flexfield attribute columns, and the Oracle E-Business Suite editioning column ZD_EDITION_NAME, consistent with the 12.2 online patching architecture. The documented primary key is AR_AGING_BUCKET_LINES_B_PK on AGING_BUCKET_LINE_ID. On the basis of the mined foreign-key structure — a single outbound reference to AR_AGING_BUCKETS with no child tables — the heuristic Data Vault classification is satellite-leaning, suggesting this table be modeled as a satellite attached to the aging bucket parent.

Key Information Stored

The most significant columns are:

• AGING_BUCKET_LINE_ID — Surrogate primary key, NUMBER(15). Identifies a single aging bucket line and is the parent reference for any dependent records.
• AGING_BUCKET_ID — NUMBER(15), foreign key to AR_AGING_BUCKETS. Identifies the aging bucket set to which the line belongs.
• BUCKET_SEQUENCE_NUM — NUMBER(15). Sequence number establishing the display and evaluation order of the interval within its bucket set.
• DAYS_START — NUMBER. Lower bound of the days range (for example, 1).
• DAYS_TO — NUMBER. Upper bound of the days range (for example, 30).
• TYPE — VARCHAR2(30). Lookup code in AR_LOOKUPS whose significant values are DISPUTE_ONLY, DISPUTE_PENDADJ, and PENDADJ_ONLY, controlling which transaction classes are included in the interval.
• ZD_EDITION_NAME — Editioning column supporting 12.2 online patching.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN for audit tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments available for customer-specific extension.

The documented unique index AR_AGING_BUCKET_LINES_B_U1, defined on (AGING_BUCKET_ID, BUCKET_SEQUENCE_NUM, ZD_EDITION_NAME), is the principal business-key candidate: it guarantees that a sequence number is unique within a given bucket set for a given edition. It resides in the APPS_TS_TX_IDX tablespace.

Common Use Cases and Queries

Typical use cases include validating aging bucket configuration, replicating receivable aging logic in custom reports, and troubleshooting aging reports that return unexpected interval assignments. The core pattern joins lines to their parent bucket:

SELECT l.aging_bucket_line_id, l.bucket_sequence_num,
       l.days_start, l.days_to, l.type
FROM   ar_aging_bucket_lines_b l
WHERE  l.aging_bucket_id = :p_aging_bucket_id
ORDER  BY l.bucket_sequence_num;

To list all bucket sets with their constituent intervals:

SELECT b.name, l.days_start, l.days_to, l.type
FROM   ar_aging_buckets b,
       ar_aging_bucket_lines_b l
WHERE  b.aging_bucket_id = l.aging_bucket_id
ORDER  BY b.name, l.bucket_sequence_num;

Because the aging interval drives how open items are distributed, customers frequently extract these lines into a staging table to apply the same DAYS_START/DAYS_TO boundaries within a custom SQL aging query. The TYPE column is used to segregate disputed or pending-adjustment items into dedicated intervals.

Related Objects

• AR.AR_AGING_BUCKETS — Parent header table. Joined on AR_AGING_BUCKET_LINES_B.AGING_BUCKET_ID = AR_AGING_BUCKETS.AGING_BUCKET_ID; the only documented foreign key target.
• AR.AR_LOOKUPS — Reference source for the TYPE column values DISPUTE_ONLY, DISPUTE_PENDADJ, and PENDADJ_ONLY.
• FND_USER — Lookup source for LAST_UPDATED_BY and CREATED_BY WHO columns.
• FND_LOGINS — Lookup source for the LAST_UPDATE_LOGIN WHO column.
• AR Aging reports and collections concurrent programs — Consumers that read AR_AGING_BUCKET_LINES_B together with AR_AGING_BUCKETS to format aging output.
• AR.AR_AGING_BUCKET_LINES_TL / _VL — Publication layer typically paired with the _B base table to expose translated or language-specific aging bucket line attributes.

When writing extensions, restrict updates to the descriptive flexfield attributes and avoid altering AGING_BUCKET_LINE_ID, AGING_BUCKET_ID, or BUCKET_SEQUENCE_NUM, since these participate in the primary key and unique business key.