Search Results schedule_header_id




Overview
Explore in AI Chat

Overview

AR_CHARGE_SCHEDULE_LINES_V is a reporting view in the Oracle E-Business Suite Receivables (AR) module, owned by the APPS schema. It presents charge schedule line data, exposing the terms under which late charges, finance charges, or similar charges are assessed against outstanding receivables. The view joins charge schedule line records to their parent charge schedule headers and to aging bucket definitions, producing a denormalized result set suited to inquiry screens, concurrent reports, and integration extracts without requiring the calling process to reproduce the underlying join logic.

Because the view draws from base tables that are subject to the standard EBS audit columns and the OBJECT_VERSION_NUMBER column, it is compatible with the Oracle Application Framework (OAF) row-level locking model used in Release 12.1.1 and 12.2.2. The view is documented as VALID in the ETRM repository and is registered as a synonym under APPS.

Underlying Base Objects

The view is defined over four documented base objects, all referenced as synonyms:

The joins are inner joins across all four objects, so a charge schedule line is returned only when its aging bucket and bucket line are both defined and its header exists. Results are ordered by ABL.BUCKET_SEQUENCE_NUM.

Key Columns

  • SCHEDULE_LINE_ID — primary key of the charge schedule line. This is the column most often sought when a user searches for schedule line detail.
  • SCHEDULE_HEADER_ID — foreign key to AR_CHARGE_SCHEDULE_HDRS, linking each line to its parent charge schedule. This is the column referenced when filtering or joining on a specific schedule.
  • SCHEDULE_ID — the charge schedule identifier carried on the line.
  • AGING_BUCKET_ID / AGING_BUCKET_LINE_ID — identify the aging bucket and bucket line to which the charge applies.
  • AMOUNT / RATE — the raw numeric values held on the line. Which one is meaningful depends on the header type.
  • VALUE — a derived column calculated as DECODE(H.SCHEDULE_HEADER_TYPE, 'AMOUNT', A.AMOUNT, A.RATE). When the header type is AMOUNT the view returns the amount; otherwise it returns the rate. This resolves the ambiguity of the two raw columns for consumers.
  • AGING_BL_LABEL — the aging bucket line report heading (ABL.REPORT_HEADING1), providing the display label used in reports.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment columns.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit and concurrency columns.

Common Use Cases and Queries

Typical uses include reviewing the charge schedule configuration for a customer or transaction, verifying the amount or rate applied per aging bucket, and driving reporting that displays predictable column labels via AGING_BL_LABEL.

Retrieve all lines for a known charge schedule header:
SELECT schedule_line_id, schedule_header_id, aging_bl_label, value
FROM apps.ar_charge_schedule_lines_v
WHERE schedule_header_id = :p_header_id;

Identify charge amounts only, filtering by header type and ordering by the view's built-in sequence:
SELECT schedule_header_id, aging_bucket_id, amount
FROM apps.ar_charge_schedule_lines_v
WHERE value = amount
ORDER BY schedule_header_id;

Join the view back to the charge schedule header for a complete listing:
SELECT h.schedule_header_id, h.name, v.aging_bl_label, v.value
FROM apps.ar_charge_schedule_hdrs h, apps.ar_charge_schedule_lines_v v
WHERE h.schedule_header_id = v.schedule_header_id;

Because the resulting set is already ordered by BUCKET_SEQUENCE_NUM, callers that require bucket-ordered output need not re-sort, though explicit ORDER BY is recommended when additional joins are introduced.