Search Results document_amount

Overview

AR_DOCS_RECEIVABLES_V is an Oracle E-Business Suite Receivables (AR) view owned by the APPS schema. It exposes receivable-related document information generated from receipt application activity. Its purpose is to present a document-oriented projection of applied receipts, where each row represents an applied payment schedule tied to an invoice or debit memo and its receipt origin. The view is one of several document views used by the ETRM (Electronic Tax Reporting and Management / document generation) framework to assemble data feeds required for statutory document reporting, particularly for documents such as invoices, debit notes, and credit notes produced for tax authorities or reporting bodies that require both document amounts and tax breakdowns. Because it joins receipts, applications, payment schedules, and transaction headers, AR_DOCS_RECEIVABLES_V is best understood as a consolidated receivables document source rather than a simple reporting view. It filters to applied, displayed receivables applications against receipts created through automatic receipt classes only.

Underlying Base Objects

The view text and documented metadata identify the following referenced base objects:

• RA_CUSTOMER_TRX (SYNONYM) — transaction header supplying invoice number, PO number, dates, currency, address information, and descriptive flexfield attributes.
• AR_PAYMENT_SCHEDULES (SYNONYM) — provides the payment schedule, amount due original, dispute date, and transaction number.
• AR_RECEIVABLE_APPLICATIONS (SYNONYM) — supplies the amount applied and links applications to cash receipts and payment schedules.
• AR_CASH_RECEIPTS (SYNONYM) — source of the receipt, its type, and payment transaction extension reference.
• AR_RECEIPT_CLASSES (SYNONYM) and AR_RECEIPT_METHODS (SYNONYM) — used to restrict to automatic receipt classes via creation method code 'AUTOMATIC'.
• IBY_FNDCPT_TX_EXTENSIONS (SYNONYM), referenced through the IBY_TRXN_EXTENSIONS_V construct — provides the payment system order number.
• ARP_TRX_LINE_UTIL (PACKAGE) — a PL/SQL utility package invoked inline to derive local tax (SALES_TAX) and VAT tax amounts for the transaction.

The joins relate each applied receivable (DISPLAY = 'Y', STATUS = 'APP') to its payment schedule, transaction header, receipt, and receipt method/class, excluding miscellaneous receipt types.

Key Columns

Columns exposed by the view include identifiers and financial amounts central to document reporting:

• DOC_UNIQUE_REF — payment trxn extension identifier, and ORDER_EXT_ID / ORDER_TANGIBLE_ID — receipt-linked ordering references.
• CALLING_APP_DOC_REF_NUMBER — the transaction number (TRX_NUMBER) of the underlying invoice.
• PO_NUMBER — purchase order reference from the transaction.
• DOCUMENT_DATE — transaction date.
• DOCUMENT_TYPE — hard-coded as 'INVOICE' in the view text.
• DOCUMENT_CURRENCY_CODE — invoice currency code.
• DOCUMENT_AMOUNT — populated from PS.AMOUNT_DUE_ORIGINAL, the original amount due on the payment schedule. This is the column users search for when reconciling document values.
• LOCAL_TAX_AMOUNT and VAT_TAX_AMOUNT — returned by ARP_TRX_LINE_UTIL.GET_TAX_AMOUNT for SALES_TAX and VAT respectively.
• NATIONAL_TAX_AMOUNT — derived from REC.AMOUNT_APPLIED, and DOCUMENT_CURR_ / FACTOR_DISCOUNT_AMOUNT — from the cash receipt's factor discount amount.

Attribute columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1–15) together with audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are passed through from RA_CUSTOMER_TRX. The view returns a constant literal 1 as its final column.

Common Use Cases and Queries

Typical usage involves extracting document records for tax or statutory reporting, reconciling applied receipts to invoices, and validating document_amount versus tax components. A representative query:

SELECT doc_unique_ref, calling_app_doc_ref_number, po_number, document_date, document_currency_code, document_amount, local_tax_amount, vat_tax_amount FROM apps.ar_docs_receivables_v WHERE document_date BETWEEN :p_from AND :p_to;

Analysts frequently filter on calling_app_doc_ref_number to trace a specific invoice, or aggregate document_amount by currency. Because tax columns are computed through ARP_TRX_LINE_UTIL, queries can be expensive; restricting by document_date or calling_app_doc_ref_number is recommended. Users searching the term "document_amount" should note it maps to AMOUNT_DUE_ORIGINAL on AR_PAYMENT_SCHEDULES and is distinct from AMOUNT_APPLIED, which drives national_tax_amount.