Search Results ar_charge_schedule_lines




Overview
Explore in AI Chat

Overview

AR_CHARGE_SCHEDULE_LINES is a Receivables (AR) transactional configuration table that stores the individual line-level definitions belonging to a charge schedule. A charge schedule determines the finance charges, late charges, or interest amounts that Receivables applies to delinquent customer balances, and each schedule is composed of one or more lines that describe how those charges are calculated within a given aging context. The table resides in the AR schema and is documented as valid in Oracle E-Business Suite 12.1.1 and 12.2.2. Its physical schema comprises 29 columns, with SCHEDULE_LINE_ID serving as the primary key.

Under the heuristic Data Vault classification provided in the metadata, AR_CHARGE_SCHEDULE_LINES is modeled as standalone. In Data Vault terms this suggests the object can be treated as an independent structure rather than a strict child satellite, even though it carries foreign keys to header and aging objects. Analysts building a vault model may therefore materialize it as a hub or a link-like construct, depending on whether schedule line identity or the header-to-aging relationship is prioritized.

Key Information Stored

The most significant columns fall into three groups: identity, charge calculation, and standard audit/extension attributes.

The combination of SCHEDULE_HEADER_ID, AGING_BUCKET_ID, and AGING_BUCKET_LINE_ID is enforced by unique index AR_CHARGE_SCHEDULE_LINES_U2, making this triplet the principal business-key candidate that prevents duplicate bucket/line assignments within a schedule.

Common Use Cases and Queries

Typical uses include auditing finance charge configuration, validating that each aging bucket has exactly one line per schedule, and reporting charge rates by aging period. A representative join to the parent schedule:

  • SELECT l.schedule_line_id, l.schedule_header_id, l.aging_bucket_id, l.rate, l.amount FROM ar.ar_charge_schedule_lines l WHERE l.schedule_header_id = :p_header_id;
  • Detecting duplicate bucket assignments: SELECT schedule_header_id, aging_bucket_id, COUNT(*) FROM ar.ar_charge_schedule_lines GROUP BY schedule_header_id, aging_bucket_id HAVING COUNT(*) > 1;
  • Resolving bucket descriptions by joining AR_AGING_BUCKETS on aging_bucket_id and AR_CHARGE_SCHEDULE_HDRS on schedule_header_id.

Reporting is generally read-only; inserts and updates should be performed through Receivables setup forms or supported APIs rather than direct DML.

Related Objects

  • AR_CHARGE_SCHEDULE_HDRS — parent header; joined on SCHEDULE_HEADER_ID = SCHEDULE_HEADER_ID.
  • AR_AGING_BUCKETS — defines the aging bucket; joined on AGING_BUCKET_ID.
  • AR_AGING_BUCKET_LINES_B — base table for aging bucket lines; joined on AGING_BUCKET_LINE_ID.
  • AR_CHARGE_SCHEDULE_LINES_PK / _U1 / _U2 — primary key and unique index constraints governing line identity and uniqueness.
  • Receivables finance charge and dunning setup components that consume the schedule definitions when calculating late charges.