Search Results original_line_amount




Overview
Explore in AI Chat

Overview

ARBV_AR_PAYMENT_SCHEDULES is a business view owned by the APPS schema in Oracle E-Business Suite Receivables. It exposes the payment schedule records that form the collection backbone of the AR subledger, one row per installment owed by a customer against a transaction. The view is registered as FND Design Data AR.ARBV_AR_PAYMENT_SCHEDULES and is flagged VALID in both 12.1.1 and 12.2.2. It carries the Oracle Internal Use Only restriction: Oracle Corporation does not support access to applications data through this object except from standard Oracle Applications programs. Consequently it should be treated as a read-only reporting and integration surface, not as a transactional interface. Its columns span due dates, original and remaining amounts, discounts, freight, tax, dispute and collection attributes, and the foreign keys that tie each schedule line back to the transaction, customer, site, and cash receipt. For the searched term original_line_amount, the view is the primary consolidated source, alongside remaining_line_amount, original_amount_due, and balance_due.

Underlying Base Objects

The documented dependency list identifies two referenced objects, both reached through synonyms: AR_PAYMENT_SCHEDULES (SYNONYM) and AR_CONS_INV (SYNONYM). AR_PAYMENT_SCHEDULES is the core AR table holding every payment schedule line, including installment sequencing, amounts, discounts, disputes, dunning, and collection state. AR_CONS_INV is the consolidated invoice object used for consolidated billing, which explains the inclusion of CONSOLIDATED_BILLING_NUMBER and the associated _LA: classification columns that derive display values for consolidated billing contexts. The view is therefore a thin, denormalized presentation layer over AR_PAYMENT_SCHEDULES, enriched where consolidated billing data applies. The _LA: prefixed columns (for example _LA:CLASS, _LA:ITEM_STATUS, _LA:IN_COLLECTION_FLAG) are lookup-derived attributes rather than stored base columns, reflecting the view's role in presenting code values in a report-friendly form.

Key Columns

Common Use Cases and Queries

Typical use cases include open-receivables aging, installment-level collection reporting, dispute tracking, and reconciliation of receipt applications to scheduled installments. A representative query on the searched column is:

  • SELECT payment_schedule_id, customer_trx_id, due_date, original_line_amount, remaining_line_amount, balance_due, invoice_currency_code FROM apps.arbv_ar_payment_schedules WHERE org_id = :p_org_id AND remaining_line_amount > 0 ORDER BY due_date;
  • SELECT customer_trx_id, SUM(original_line_amount) original_scheduled, SUM(remaining_line_amount) still_open FROM apps.arbv_ar_payment_schedules WHERE org_id = :p_org_id GROUP BY customer_trx_id;
  • SELECT payment_schedule_id, dispute_amount, dispute_date FROM apps.arbv_ar_payment_schedules WHERE dispute_amount IS NOT NULL;

Because the view is documented as internal use only, production reporting should prefer supported public views where they exist, and any direct querying should be limited to read-only selection against the columns documented above.