Search Results amount_applied_rct_func

Overview

APPS.FII_AR_RECEIPTS_F_V is a reporting and integration view in the Oracle E-Business Suite Receivables (AR) module, exposed under the APPS schema. It presents a denormalized, column-oriented view of receipt application activity, joining receipt header attributes to application-level rows so that each record represents a single receivable application (cash, unapplied, unapplied-on-account, claim, or chargeback) together with the relevant receipt header context. The "F" suffix denotes a fact-style view designed primarily for consumption by Oracle Financials Intelligence (FII) / Daily Business Intelligence (DBI) style reporting, extraction, and data warehouse loading processes rather than for transactional maintenance. Because the view precomputes functional, primary, and secondary currency amounts, it is especially convenient for multi-currency reporting in a 12.1.1 or 12.2.2 environment where ledger and reporting currencies differ from the receipt currency. The view is read-only in practice; consumers query it, they do not post against it.

Underlying Base Objects

The ETRM metadata excerpt characterizes this view as having no separately documented base objects, and its definition is expressed as a flat SELECT list rather than an explicit join graph. In practical terms, the view resolves against the AR receipt and application tables — principally AR_CASH_RECEIPTS and AR_RECEIVABLE_APPLICATIONS_ALL, together with the associated customer transaction and payment schedule tables referenced by columns such as CUSTOMER_TRX_ID, PAYMENT_SCHEDULE_ID, and APPLIED_CUSTOMER_TRX_ID. The QUERY exposes derived columns such as UNAPP_AMOUNT and its functional, primary, and secondary variants, which are computed with CASE expressions rather than stored in a single base table. Key derivations include:

• UNAPP_AMOUNT family: set to AMOUNT_APPLIED_RCT (or the corresponding functional, primary, secondary amount) when APPLICATION_STATUS = 'UNAPP', HEADER_STATUS is not REV, NSF, or STOP, NVL(APPLIED_PAYMENT_SCHEDULE_ID,1) > 0, and APPLICATION_TYPE = 'CASH'; otherwise zero.
• EARNED_DISCOUNT_AMOUNT_* and UNEARNED_DISCOUNT_AMOUNT_*: carried across TRX, FUNC, PRIM, and SEC currency bases.
• Amount applied columns AMOUNT_APPLIED_RCT_* and AMOUNT_APPLIED_TRX_*: receipt-side and transaction-side amounts in each currency basis.

Key Columns

The columns most relevant to the user's search for application_type are the following:

• APPLICATION_TYPE — the discriminator for the application row, with documented values including 'CASH' (used in the UNAPP_AMOUNT derivation). It governs whether a row participates in unapplied-cash reporting.
• APPLICATION_STATUS — status of the application, e.g. 'UNAPP' for unapplied. Combined with HEADER_STATUS it determines the unapplied amount.
• HEADER_STATUS — receipt header status; values REV, NSF, and STOP are expressly excluded from unapplied computations.
• CASH_RECEIPT_ID / RECEIPT_NUMBER / RECEIPT_TYPE / RECEIPT_DATE — receipt header identity and timing.
• RECEIVABLE_APPLICATION_ID / APPLIED_CUSTOMER_TRX_ID / APPLIED_PAYMENT_SCHEDULE_ID — the application and its target transaction.
• AMOUNT_APPLIED_RCT_TRX and the FUNC/PRIM/SEC variants; GL_DATE, APPLY_DATE, TRX_DATE, DUE_DATE; CURRENCY_CODE; ORG_ID; and audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include unapplied and on-account cash reporting, receipt application aging, and currency-basis reconciliation for FII extracts.

• Unapplied cash by application type: SELECT APPLICATION_TYPE, RECEIPT_NUMBER, CURRENCY_CODE, UNAPP_AMOUNT FROM APPS.FII_AR_RECEIPTS_F_V WHERE APPLICATION_TYPE = 'CASH' AND UNAPP_AMOUNT <> 0;
• Application volumes by status: SELECT APPLICATION_STATUS, HEADER_STATUS, COUNT(*), SUM(AMOUNT_APPLIED_RCT_FUNC) FROM APPS.FII_AR_RECEIPTS_F_V GROUP BY APPLICATION_STATUS, HEADER_STATUS;
• Org-scoped reconciliation: filter by ORG_ID and GL_DATE to align the view to a specific operating unit and accounting period.