Search Results schedule_header_type




Overview
Explore in AI Chat

Overview

The APPS.AR_CHARGE_SCHEDULE_HEADERS_V view is a reporting and integration object within the Oracle E-Business Suite Receivables (AR) module. It exposes charge schedule header information maintained in the Oracle Receivables charge schedule functionality, which supports the grouping of receivables activity into time-bounded schedules that reference aging buckets. The view is owned by the APPS schema and is intended primarily for inquiry, reporting, and downstream integration consumption rather than for direct transactional maintenance.

The view presents a denormalized, human-readable form of charge schedule headers. Unlike the underlying transactional table, it resolves coded values into descriptive text. Specifically, it derives SCHEDULE_HEADER_MEANING through a call to ARPT_SQL_FUNC_UTIL.get_lookup_meaning for the SCHEDULE_HEADER_TYPE lookup, and it joins to aging bucket data to surface AGING_BUCKET_NAME and AGING_DESCRIPTION. This makes the view particularly useful for reports, concurrent programs, and interfaces that require schedule header context without additional lookup resolution logic.

Underlying Base Objects

The view is defined over the following documented base objects:

  • AR_CHARGE_SCHEDULE_HDRS (referenced via synonym) — the primary transactional source supplying schedule header attributes such as schedule identifiers, dates, status, descriptive flexfield attributes, and standard WHO audit columns.
  • AR_AGING_BUCKETS (referenced via synonym) — joined on AGING_BUCKET_ID to supply bucket name and description.
  • ARPT_SQL_FUNC_UTIL (package) — invoked as a scalar function to translate SCHEDULE_HEADER_TYPE into a lookup meaning.

The join between AR_CHARGE_SCHEDULE_HDRS and AR_AGING_BUCKETS is an inner equijoin on AGING_BUCKET_ID, with results ordered by SCHEDULE_ID and START_DATE. Because the two base objects are referenced through synonyms, the view can be deployed consistently across the APPS schema in both 12.1.1 and 12.2.2 environments.

Key Columns

  • SCHEDULE_HEADER_ID — primary identifier of the schedule header row.
  • SCHEDULE_ID — identifier of the parent charge schedule; used in ordering and grouping.
  • SCHEDULE_HEADER_TYPE — the coded lookup value describing the header type; the value specifically associated with the "schedule_header_type" search.
  • SCHEDULE_HEADER_MEANING — the decoded, user-facing meaning of SCHEDULE_HEADER_TYPE returned by ARPT_SQL_FUNC_UTIL.get_lookup_meaning.
  • AGING_BUCKET_ID — foreign key to the aging bucket referenced by the header.
  • AGING_BUCKET_NAME / AGING_DESCRIPTION — descriptive attributes from AR_AGING_BUCKETS.
  • START_DATE / END_DATE — the effective date range of the schedule header.
  • STATUS — the current status of the schedule header.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns for extensibility.
  • OBJECT_VERSION_NUMBER — optimistic locking version indicator.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Because the view resolves the schedule header type lookup and aging bucket descriptors, it is commonly used in Receivables aging and charge schedule reporting, in integration extracts, and in diagnostic queries that investigate schedule header configuration.

A typical query lists headers of a given meaning with their aging bucket context:

  • SELECT schedule_header_id, schedule_id, schedule_header_type, schedule_header_meaning, aging_bucket_name, start_date, end_date, status FROM apps.ar_charge_schedule_headers_v WHERE status = 'A' ORDER BY schedule_id, start_date;

To filter directly on the searched attribute, the following returns all headers of a specific type with its decoded meaning:

  • SELECT schedule_header_id, schedule_id, schedule_header_meaning, aging_bucket_name, start_date, end_date FROM apps.ar_charge_schedule_headers_v WHERE schedule_header_type = :p_schedule_header_type;

For integration extracts, selecting the descriptive flexfield attributes together with the resolved lookup meaning produces a fully self-describing record set suitable for downstream systems.