Search Results ar_charge_schedule_lines_u2

Overview

AR.AR_CHARGE_SCHEDULE_LINES is a transaction data table in the Oracle Receivables (AR) schema that stores the individual line-level detail of a charge schedule. A charge schedule defines the interest, late charges, or finance charges applied to overdue customer balances, and this table holds one row for each aging bucket and aging bucket line combination against which a schedule header draws its amounts and rates. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is available in both Oracle E-Business Suite 12.1.1 and 12.2.2. Under the heuristic Data Vault classification supplied with the metadata, the object is marked as standalone; in practice it behaves as a link entity, resolving the many-to-many association between charge schedule headers and AR aging bucket lines, with the AMOUNT and RATE columns functioning as link-level descriptive attributes.

Key Information Stored

The primary key is the surrogate identifier SCHEDULE_LINE_ID, which is enforced by the unique index AR_CHARGE_SCHEDULE_LINES_U1. The remaining attributes are structured around three foreign key relationships and a small set of business values:

• SCHEDULE_LINE_ID — surrogate primary key (NUMBER 15), uniquely identifying each schedule line.
• SCHEDULE_HEADER_ID — foreign key to AR_CHARGE_SCHEDULE_HDRS, tying the line to its parent charge schedule.
• SCHEDULE_ID — foreign key to the underlying schedule definition.
• AGING_BUCKET_ID — foreign key to AR_AGING_BUCKETS, the aging bucket the line applies to.
• AGING_BUCKET_LINE_ID — foreign key to AR_AGING_BUCKET_LINES_B, the specific aging bucket line.
• AMOUNT — the charge amount associated with the line.
• RATE — the rate applied to the line.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield structure and segments, each VARCHAR2(150).
• OBJECT_VERSION_NUMBER — internal versioning column for optimistic locking.
• Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

The unique index AR_CHARGE_SCHEDULE_LINES_U2 (SCHEDULE_HEADER_ID, AGING_BUCKET_ID, AGING_BUCKET_LINE_ID) is the business-key candidate, guaranteeing that each aging bucket line appears only once per schedule header.

Common Use Cases and Queries

Typical reporting needs include reconciling charges to aging buckets, auditing rate and amount configuration, and rebuilding charge schedules. A join to the header and bucket tables illustrates the common pattern:

• Schedule line detail: SELECT l.schedule_line_id, l.schedule_header_id, l.amount, l.rate FROM ar.ar_charge_schedule_lines l WHERE l.schedule_header_id = :p_header_id;
• Bucket enrichment: Join AR_CHARGE_SCHEDULE_LINES to AR_AGING_BUCKETS on AGING_BUCKET_ID and to AR_AGING_BUCKET_LINES_B on AGING_BUCKET_LINE_ID to obtain bucket names and ranges.
• Rate/amount reports: Aggregate AMOUNT by AGING_BUCKET_ID for a schedule to review total configured charges.
• Concurrent processing validation: Query by the U2 key to detect duplicate bucket-line configuration before program runs.

Related Objects

• AR.AR_CHARGE_SCHEDULE_HDRS — parent header; join on AR_CHARGE_SCHEDULE_LINES.SCHEDULE_HEADER_ID = AR_CHARGE_SCHEDULE_HDRS.SCHEDULE_HEADER_ID.
• AR.AR_AGING_BUCKETS — join on AR_CHARGE_SCHEDULE_LINES.AGING_BUCKET_ID = AR_AGING_BUCKETS.AGING_BUCKET_ID.
• AR.AR_AGING_BUCKET_LINES_B — join on AR_CHARGE_SCHEDULE_LINES.AGING_BUCKET_LINE_ID = AR_AGING_BUCKET_LINES_B.AGING_BUCKET_LINE_ID.
• AR.AR_AGING_BUCKET_LINES_TL — translation table for bucket line descriptions.
• AR.AR_CHARGE_SCHEDULES — schedule definition referenced by SCHEDULE_ID.