Search Results payment_schedule_status

Overview

APPS.OE_RMA_INVOICE_NUMBER_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as ONT.OE_RMA_INVOICE_NUMBER_V. It exposes invoice information associated with Return Merchandise Authorization (RMA) transactions processed through Oracle Order Management and Oracle Receivables. The view consolidates invoice header attributes drawn from Receivables base objects into a single, denormalized projection, allowing callers to retrieve the invoice number, transaction date, invoice creation date, currency, payment status, and customer identifier for a given customer transaction.

The object is documented with an Internal view type and carries the standard Oracle warning that it is intended for use only by standard Oracle Applications programs. Oracle Corporation does not support direct customer access to application data through this object. Consequently, its principal role is as an internal reporting and integration artifact used by EBS application logic rather than as a sanctioned public interface. Because the view is declared VALID and is not referenced by any other database object, it functions as a terminal, read-only projection at the top of its dependency chain.

Underlying Base Objects

The view is defined over four documented base objects. The primary source is RA_CUSTOMER_TRX, accessed through a synonym, which supplies the invoice header record and the CUSTOMER_TRX_ID, TRX_NUMBER, and TRX_DATE columns. RA_PAYMENT_SCHEDULES, also accessed through a synonym, contributes payment-related information that populates the PAYMENT_STATUS column. RA_BATCH_SOURCES, likewise referenced via synonym, supplies the BATCH_SOURCE_NAME value associated with the transaction batch. AR_LOOKUPS, referenced as a view, is the standard Receivables lookup source and provides the decoded meaning for the payment status value.

All four dependencies reside in the APPS schema. The view does not reference or derive from Oracle Order Management base tables directly, despite its ONT design-data classification; the RMA linkage is expressed through relationship and association columns rather than through explicit ONT table joins in the documented metadata. No database object references OE_RMA_INVOICE_NUMBER_V, confirming its position as a leaf object in the dependency graph.

Key Columns

• CUSTOMER_TRX_ID (NUMBER(15)) — The unique identifier of the customer transaction in Receivables. This is the primary join key to RA_CUSTOMER_TRX and related invoice tables.
• TRX_NUMBER (VARCHAR2(20)) — The user-facing invoice or transaction number.
• TRX_DATE (DATE) — The transaction date recorded on the invoice header.
• BATCH_SOURCE_NAME (VARCHAR2(50)) — The name of the Receivables batch source through which the transaction was created.
• SOLD_TO_CUSTOMER_ID (NUMBER(15)) — The identifier of the sold-to customer associated with the invoice.
• INVOICE_CURRENCY_CODE (VARCHAR2(15)) — The currency in which the invoice was denominated.
• INVOICE_CREATION_DATE (DATE) — The date the invoice record was created. This column directly addresses searches for invoice_creation_date and is distinct from TRX_DATE, which reflects the accounting or transaction date.
• PAYMENT_STATUS (VARCHAR2(80)) — The decoded status of the payment schedule, sourced via AR_LOOKUPS and AR_PAYMENT_SCHEDULES.

Common Use Cases and Queries

The view is typically queried to reconcile RMA-related invoices, audit invoice creation timing against transaction dates, and report on outstanding or settled receivables. A representative query retrieving all invoices created after a given date follows:

SELECT CUSTOMER_TRX_ID, TRX_NUMBER, TRX_DATE, INVOICE_CREATION_DATE, INVOICE_CURRENCY_CODE, PAYMENT_STATUS FROM APPS.OE_RMA_INVOICE_NUMBER_V WHERE INVOICE_CREATION_DATE >= TO_DATE('01-JAN-2024','DD-MON-YYYY');

To isolate unpaid invoices for a specific customer, callers may filter on SOLD_TO_CUSTOMER_ID combined with a PAYMENT_STATUS predicate. Because Oracle does not support direct access to this internal object, organizations requiring supported extraction should build custom views or concurrent programs over the underlying RA_CUSTOMER_TRX and AR_PAYMENT_SCHEDULES tables instead of querying OE_RMA_INVOICE_NUMBER_V directly.