Search Results al_class_meaning




Overview
Explore in AI Chat

Overview

APPS.IGI_AR_PAYMENT_SCHEDULES_V is a reporting and integration view in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that exposes Accounts Receivable payment schedule information in a denormalized, presentation-ready form. The view is owned by the APPS schema and originates from the Oracle Grants/IGI product family, where it supports inquiry and reporting against receivables transactions — particularly those linked to awards, billing, and sponsored project activity. Functionally, it is a thin projection over AR_PAYMENT_SCHEDULES_V, re-exposing a curated column list that includes transaction identifiers, payment terms sequencing, currency, due dates, original and remaining amounts due, dispute information, days past due, and audit columns.

Because the view terminates in the "_V" naming convention, it is a read-only view intended for query, not for DML. It plays the role of a stable interface layer: reporting tools, concurrent programs, and external integrations can select from APPS.IGI_AR_PAYMENT_SCHEDULES_V without embedding the more complex join logic or function calls that exist in the underlying AR view. This decoupling is significant in the grants context, where dispute visibility and aging of receivables are relevant to collection and award management reporting.

Underlying Base Objects

The ETRM metadata documents three referenced base objects for this view: ARPT_SQL_FUNC_UTIL (PACKAGE), ARP_VIEW_CONSTANTS (PACKAGE), and AR_PAYMENT_SCHEDULES_V (VIEW). The view text itself selects exclusively from AR_PAYMENT_SCHEDULES_V; the two packages are referenced indirectly because the underlying AR view invokes them (for example, to resolve lookup meanings such as AL_CLASS_MEANING and AL_STATUS_MEANING, and to derive values such as days past due). Consequently, IGI_AR_PAYMENT_SCHEDULES_V inherits the row population, security, and translation behavior of AR_PAYMENT_SCHEDULES_V, including any Org or operating unit context applied at that lower layer.

The naming of ARPT_SQL_FUNC_UTIL and ARP_VIEW_CONSTANTS indicates that the AR view performs runtime function-based lookups and applies constant values rather than relying solely on stored columns. Any performance characteristic of this view — particularly the cost of resolving the meaning columns — derives from those packages rather than from the IGI view itself, which adds only a ROUND operation on DAYS_PAST_DUE.

Key Columns

  • TRX_NUMBER — the receivables transaction number, the primary human-readable identifier for the underlying invoice or debit memo.
  • CUSTOMER_TRX_ID — the internal foreign key to the transaction header, used for joins back to RA_CUSTOMER_TRX_ALL and related tables.
  • TERMS_SEQUENCE_NUMBER — identifies which installment or payment term line within a multi-schedule transaction the row represents.
  • INVOICE_CURRENCY_CODE — the currency in which the transaction and its amounts are denominated.
  • DUE_DATE and DAYS_PAST_DUE — the scheduled due date and the rounded number of days the balance is past due, the core aging attributes.
  • AMOUNT_DUE_ORIGINAL and AMOUNT_DUE_REMAINING — the original scheduled amount and the outstanding balance, respectively.
  • AMOUNT_IN_DISPUTE and DISPUTE_DATE — the monetary value under dispute and the date the dispute was recorded. Because the user searched for "dispute_date," these two columns are the relevant attributes; dispute_date is populated only for transactions carrying an active or recorded dispute.
  • AL_CLASS_MEANING and AL_STATUS_MEANING — translated meanings for the transaction class and status, resolved via the AR packages.
  • BILLING_NUMBER — the billing or document reference associated with the schedule line.
  • ROW_ID — a unique row identifier, useful for deduplication and for integration keys.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard audit columns supporting incremental extraction and change tracking.

Common Use Cases and Queries

The primary use case is receivables inquiry and dispute reporting. A query to identify outstanding disputed balances with dispute dates is typical:

SELECT trx_number, customer_trx_id, invoice_currency_code, due_date, amount_due_remaining, amount_in_dispute, dispute_date FROM apps.igi_ar_payment_schedules_v WHERE amount_in_dispute > 0 AND dispute_date IS NOT NULL ORDER BY dispute_date;

Aging analysis is equally common, using the pre-rounded DAYS_PAST_DUE to bucket exposure:

SELECT trx_number, due_date, days_past_due, amount_due_original, amount_due_remaining FROM apps.igi_ar_payment_schedules_v WHERE amount_due_remaining > 0 AND days_past_due > 30;

For integration and change-data-capture loads, the audit columns allow incremental extracts such as selecting rows where last_update_date exceeds a stored high-water mark. Because the view is read-only and carries no DML privileges, it should be used strictly for SELECT operations; all maintenance must occur against the underlying receivables tables.