Search Results ar_charge_schedule_hdrs




Overview
Explore in AI Chat

Overview

AR_CHARGE_SCHEDULE_HDRS is a Receivables (AR) module table that stores the header records for charge schedules. A charge schedule defines a structured, date-bound plan of charges applied to a customer, contract, or receivable transaction, and the header row establishes the identity, type, validity window, and approval status that its associated line records inherit. Within Oracle EBS 12.1.1 and 12.2.2, the table is owned by the AR schema and is documented in ETRM as a VALID base table with 29 columns.

From a dimensional modeling perspective, the mined foreign-key structure classifies AR_CHARGE_SCHEDULE_HDRS as a standalone entity. The heuristic Data Vault classification suggests treating it as a hub, since it holds the durable business key (SCHEDULE_HEADER_ID) around which dependent detail and interface records are organized. No parent foreign keys were identified in the metadata, which reinforces the hub interpretation rather than a link or satellite role. The table is multi-organization aware in the sense that its transactions ultimately flow through Receivables, though the mined structure shows no direct foreign key to an operating unit table.

Key Information Stored

The table's physical schema contains 29 documented columns. The most significant are:

The unique index AR_CHARGE_SCHEDULE_HDRS_U1 (SCHEDULE_HEADER_ID, SCHEDULE_ID) is a candidate business key that, together with the primary key, uniquely identifies a charge schedule header.

Common Use Cases and Queries

Typical usage centers on querying charge schedules by type, status, or date range, and joining headers to their lines. A common pattern is:

  • Retrieving active schedules valid as of a given date: SELECT schedule_header_id, schedule_id, start_date, end_date, status FROM ar.ar_charge_schedule_hdrs WHERE status = 'A' AND SYSDATE BETWEEN start_date AND end_date;
  • Joining the header to its child lines to reconcile scheduled amounts: SELECT h.schedule_header_id, l.schedule_line_id FROM ar.ar_charge_schedule_hdrs h, ar.ar_charge_schedule_lines l WHERE h.schedule_header_id = l.schedule_header_id;
  • Reporting by schedule header type: SELECT schedule_header_type, COUNT(*) FROM ar.ar_charge_schedule_hdrs GROUP BY schedule_header_type;
  • Auditing recently modified records: SELECT schedule_header_id, last_updated_by, last_update_date FROM ar.ar_charge_schedule_hdrs WHERE last_update_date > SYSDATE - 7;
  • Flexfield reporting using the ATTRIBUTE_CATEGORY and ATTRIBUTE1..15 columns for site-specific segmentation.

Because the table is foundation data for downstream demand and exception processing, reconciliation reports frequently compare header counts against the RLM interface and exception tables listed below.

Related Objects

The following objects reference or depend on AR_CHARGE_SCHEDULE_HDRS through the documented foreign-key relationships:

  • AR_CHARGE_SCHEDULE_LINES — child table; joins on SCHEDULE_HEADER_ID to supply the individual scheduled charge lines.
  • RLM_DEMAND_EXCEPTIONS — references the header via SCHEDULE_HEADER_ID to record demand exceptions tied to a charge schedule.
  • RLM_INTERFACE_HEADERS_ALL — references the header via SCHEDULE_HEADER_ID for inbound interface processing.

The primary key AR_CHARGE_SCHEDULE_HDRS_PK (SCHEDULE_HEADER_ID) and the unique index AR_CHARGE_SCHEDULE_HDRS_U1 (SCHEDULE_HEADER_ID, SCHEDULE_ID) are the principal integrity constraints. Application logic in the Receivables module and its RLM extensions typically accesses this table through the corresponding OAF entity objects or PL/SQL APIs rather than direct DML.