Search Results amount_applied_trx_func

Overview

The view APPS.FII_AR_RECEIPTS_F_V is a Financial Intelligence (FII) reporting object in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is owned by the APPS schema and is documented as VALID in the ETRM repository. The view presents receipt and credit memo application facts used by the Financial Intelligence product, which is the EBS-embedded historical reporting and analytics layer for subledger data. The underlying description states the view is based on the table FII_AR_RECEIPTS_F, and that it stores receipts and credit memos.

The view exposes both receipt-level and application-level attributes, allowing analytics over cash receipts, credit memos, their applied amounts, and their accounting status. It also derives several calculated columns such as UNAPP_AMOUNT, UNAPP_AMOUNT_FUNC, and UNAPP_AMOUNT_PRIM, which represent unapplied cash amounts under controlled conditions. Because it includes currency and organizational dimensions, the view is suitable for standardized subledger reporting across ledgers.

Underlying Base Objects

The documented base object referenced by the view is the FII fact table FII_AR_RECEIPTS_F. In ETRM metadata for 12.2.2, no additional base objects are documented for the view; its definition is a direct projection with inline CASE expressions rather than a multi-table join. The columns returned map field-for-field to the columns of the fact table, with added derived columns.

Operationally, FII_AR_RECEIPTS_F is populated from Oracle Receivables subledger entities such as AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_RECEIVABLE_APPLICATIONS, and RA_CUSTOMER_TRX_ALL. The view therefore sits downstream of those transactional tables and is intended for read-only reporting rather than for transaction processing. It should not be used in place of the AR transactional tables for operational updates.

Key Columns

• HEADER_STATUS — The status of the receipt header. This is the column most directly relevant to the user's search. Documented values appearing in the view logic include REV (reversed), NSF (non-sufficient funds), and STOP (stopped payment). The unapplied-amount calculations exclude these statuses.
• APPLICATION_STATUS — The status of the application itself; UNAPP indicates unapplied cash and is used together with HEADER_STATUS in the derived columns.
• CASH_RECEIPT_ID and RECEIPT_NUMBER — Identifiers for the receipt header in Oracle Receivables.
• RECEIVABLE_APPLICATION_ID, APPLIED_CUSTOMER_TRX_ID, CUSTOMER_TRX_ID, PAYMENT_SCHEDULE_ID, APPLIED_PAYMENT_SCHEDULE_ID — Application and transaction linkage keys.
• AMOUNT_APPLIED_RCT, AMOUNT_APPLIED_TRX and their _FUNC, _PRIM, and _SEC counterparts — Applied amounts in receipt, functional, primary, and secondary currencies.
• EARNED_DISCOUNT_AMOUNT_TRX/FUNC/PRIM/SEC and UNEARNED_DISCOUNT_AMOUNT_TRX/FUNC/PRIM/SEC — Earned and unearned discount amounts for the application.
• UNAPP_AMOUNT, UNAPP_AMOUNT_FUNC, UNAPP_AMOUNT_PRIM — Derived unapplied cash amounts, calculated when the application is unapplied, the header is not reversed, NSF, or stopped, a payment schedule exists, and the application type is cash.
• APPLY_DATE, GL_DATE, FILTER_DATE, TRX_DATE, DUE_DATE, RECEIPT_DATE, RCT_ACTUAL_DATE_CLOSED, TIME_ID — Date and time dimensions used for period-based analytics.
• RECEIPT_TYPE, RECEIPT_METHOD_ID, CURRENCY_CODE, ORG_ID, APPLICATION_TYPE — Classification and dimensional attributes.
• BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID, COLLECTOR_BILL_TO_CUSTOMER_ID, COLLECTOR_BILL_TO_SITE_USE_ID — Customer and site dimensions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, AR_CREATION_DATE — Standard audit columns.

Common Use Cases and Queries

Typical scenarios include monitoring unapplied cash, analyzing receipt status distribution, and building FII reports that reconcile receipt applications by currency and organization. Because HEADER_STATUS is central to filtering out reversed, NSF, and stopped receipts, queries frequently constrain on it.

• List receipts by header status for a period.
• Total applied and unapplied amounts per customer.
• Identify receipts excluded from unapplied cash due to HEADER_STATUS values of REV, NSF, or STOP.

Sample query grouping by header status and currency:

SELECT header_status, currency_code, SUM(amount_applied_rct_func) applied_func, SUM(unapp_amt_func) unapplied_func FROM apps.fii_ar_receipts_f_v WHERE time_id BETWEEN :p_start AND :p_end GROUP BY header_status, currency_code;

Sample query for unapplied cash detail:

SELECT receipt_number, customer_trx_id, header_status, application_status, amount_applied_rct, unapp_amt, apply_date FROM apps.fii_ar_receipts_f_v WHERE header_status NOT IN ('REV','NSF','STOP') AND application_status = 'UNAPP' AND org_id = :p_org_id;

These patterns are consistent with documented view logic, in which unapplied amounts are non-zero only for cash applications that satisfy the stated header status and payment schedule conditions.