Results for “ar_trx_schedules_rep_itf_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_TRX_SCHEDULES_REP_ITF_V is a reporting interface view owned by the APPS schema in Oracle E-Business Suite Receivables. It is classified as a VIEW with VALID status and is available in both 12.1.1 and 12.2.2. The view exposes transaction schedule data drawn from the Oracle Receivables reporting interface table AR_TRANSACTIONS_REP_ITF, denormalized with customer, term, payment method, tax, document sequence, and payment schedule attributes. Its principal role is to provide a stable, presentation-ready projection of receivable transaction and scheduled payment information for reporting tools, concurrent programs, and downstream integration extracts, so that consumers do not need to reconstruct the join logic against the base Receivables tables themselves.

The "_REP_ITF" naming convention indicates a reporting interface object. In practice, these views are consumed by Receivables reporting and by external reporting layers that need a flat, human-readable view of transaction classes, types, customers, and scheduled amounts without navigating the normalized AR schema. Because the view already resolves many lookup meanings (for example, transaction class and tax calculation level), it is particularly useful where a report or extract must display decoded values rather than raw code values.

Underlying Base Objects

The documented metadata for this view lists the following referenced base objects: AR_LOOKUPS (view), AR_PAYMENT_SCHEDULES_ALL, AR_RECEIPT_METHODS, AR_TRANSACTIONS_REP_ITF, FND_DOCUMENT_SEQUENCES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, RA_CUST_TRX_TYPES_ALL, and RA_TERMS.

AR_TRANSACTIONS_REP_ITF is the driving table, providing the transaction-level columns (aliased RX in the view text). AR_PAYMENT_SCHEDULES_ALL supplies the schedule lines — scheduled due date, original amount, and remaining scheduled amount — joined via PS. RA_CUST_TRX_TYPES_ALL provides the transaction type name, and AR_LOOKUPS resolves the transaction class meaning through TRX_CLASS.MEANING. AR_RECEIPT_METHODS supplies the payment method name. RA_TERMS contributes the payment terms name. FND_DOCUMENT_SEQUENCES supplies the document sequence name. The HZ objects (HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL) resolve ship-to and bill-to customer names, account numbers, and site locations, with phonetic organization names derived through HZ_PARTIES. The presence of AR_LOOKUPS as a view, rather than a synonym, is notable and reflects the lookup-based decoding embedded in the definition.

Key Columns

The view exposes a broad set of transaction and schedule attributes. Identification and audit columns include ROW_ID, REQUEST_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

• TRX_NUMBER, TRX_CLASS, TRX_TYPE — the transaction number, the decoded transaction class meaning (from AR_LOOKUPS), and the transaction type name (from RA_CUST_TRX_TYPES_ALL). These are central to any query filtered on transaction class.
• TRX_DATE, TRX_DUE_DATE, RECEIVABLES_GL_DATE — transaction date, due date, and the GL date used for Receivables accounting.
• SHIP_TO_* and BILL_TO_* columns — customer name, phonetic organization name, account number, and site location for ship-to and bill-to parties, length-limited via SUBSTRB.
• TRX_CURRENCY, EXCHANGE_RATE, EXCHANGE_DATE, EXCHANGE_TYPE — currency and conversion attributes.
• REC_ACCOUNT, REC_BALANCE, REC_NATACCT and their _DESC counterparts — Receivables accounting flexfield segment values and descriptions, plus REC_POSTABLE_FLAG.
• TRX_AMOUNT, TRX_ACCTD_AMOUNT — entered and accounted transaction amounts.
• PAYMENT_TERMS, PAYMENT_METHOD, TAX_CALCULATION_LEVEL, DOC_SEQUENCE_NAME, DOC_SEQUENCE_VALUE — decoded terms, method, tax level, and document sequence metadata.
• SCHEDULED_DUE_DATE, ORIGINAL_AMOUNT, SCHEDULED_AMOUNT — payment schedule line attributes from AR_PAYMENT_SCHEDULES_ALL, representing the due date, original amount due, and remaining scheduled amount.

Common Use Cases and Queries

Because the view decodes both transaction class and transaction type, it is commonly used to report receivables by class — for example, separating invoices, credit memos, debit memos, chargebacks, and commitments — while retaining schedule-level installment detail. A typical query filtering on transaction class is:

SELECT trx_number, trx_class, trx_type, trx_date,
       trx_due_date, trx_currency, trx_amount,
       scheduled_due_date, original_amount, scheduled_amount
FROM   apps.ar_trx_schedules_rep_itf_v
WHERE  trx_class = 'Invoice'
ORDER BY trx_date, trx_number;

The view is also used for aging and collections analysis, joining schedule lines to due dates, and for customer-facing extracts that require both bill-to and ship-to data with phonetic organization names. A further common scenario is document sequencing and tax reporting, where TAX_CALCULATION_LEVEL, DOC_SEQUENCE_NAME, and DOC_SEQUENCE_VALUE are required alongside the accounting flexfield descriptions. Because the view is request-aware through REQUEST_ID, it supports extraction driven by a specific concurrent program request, allowing a report to read only the rows populated by its own run.