Search Results ar_payment_schedules_all




Overview
Explore in AI Chat

Overview

The AR_PAYMENT_SCHEDULES_ALL table is a core transactional table within the Oracle E-Business Suite Receivables (AR) module, central to the management of customer obligations. As indicated by its description, it stores records for all receivable transactions except adjustments and miscellaneous cash receipts. This includes invoices, debit memos, credit memos, chargebacks, and commitments. Its primary role is to track the payment schedule for each transaction, recording critical financial details such as the original amount, remaining balance, due date, and aging status. The table is multi-org enabled, as signified by the "_ALL" suffix, meaning it stores data for all operating units and requires a security predicate (e.g., ORG_ID) in queries.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which anchor it within the Receivables data model. The primary key, PAYMENT_SCHEDULE_ID, uniquely identifies each payment schedule record. Key columns include CUSTOMER_TRX_ID, linking to the base transaction in RA_CUSTOMER_TRX_ALL, and TERMS_SEQUENCE_NUMBER for installment tracking. Critical financial columns are AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING, and GL_DATE_CLOSED. Status is managed through columns like CLASS (e.g., 'INV', 'CM') and STATUS (e.g., 'OP', 'CL'). The table also holds currency information (INVOICE_CURRENCY_CODE), due dates (DUE_DATE, TRX_DATE), and references to the last applied activity via columns like CASH_RECEIPT_ID_LAST, CASH_APPLIED_ID_LAST, and ADJUSTMENT_ID_LAST.

Common Use Cases and Queries

This table is fundamental for accounts receivable reporting and processes. Common use cases include generating aging reports, calculating outstanding balances, and identifying overdue invoices for collection activities. A typical query to find open invoices for a customer would join to related customer and transaction tables:

  • SELECT aps.trx_number, aps.amount_due_remaining, aps.due_date FROM ar_payment_schedules_all aps, ra_customer_trx_all rct WHERE aps.customer_trx_id = rct.customer_trx_id AND aps.customer_id = :cust_id AND aps.status = 'OP' AND aps.class = 'INV' AND aps.org_id = :org_id;

It is also central to the cash application process, as applications (AR_RECEIVABLE_APPLICATIONS_ALL) are made against specific payment schedule records. Developers often query this table to validate transaction status before allowing adjustments or write-offs.

Related Objects

As shown in the metadata, AR_PAYMENT_SCHEDULES_ALL has extensive foreign key relationships, making it a hub within the AR schema. Key related objects include:

  • RA_CUSTOMER_TRX_ALL: The source transaction header.
  • AR_RECEIVABLE_APPLICATIONS_ALL: Applications of cash, credit, or adjustments against the schedule.
  • AR_CASH_RECEIPTS_ALL: Linked via CASH_RECEIPT_ID_LAST for the most recent receipt activity.
  • AR_ADJUSTMENTS_ALL: Linked via ADJUSTMENT_ID_LAST for the most recent adjustment.
  • HZ_CUST_ACCOUNTS: The customer definition.
  • RA_CUST_TRX_TYPES_ALL: The transaction type.
  • RA_TERMS_B: The payment terms.

Important views like AR_PAYMENT_SCHEDULES (a single-org view) and APIs such as AR_INVOICE_API_PUB often interact with or are based on this underlying table.