Search Results total_unapplied_amount_sec

Overview

FII_AR_RCT_AGING_AGRT_MV_S_V is an APPS-owned, VALID database view classified under the FII (Financial Intelligence) product family of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. FII is the subsystem that underpins Oracle Receivables' Advanced Collections, iReceivables, and related financial analytics reporting. The view is a secured ("_S_") layer over the materialized view FII_AR_RCT_AGING_AGRT_MV, and it presents pre-aggregated receivables aging data organized by collector, customer party, and time period.

Its primary role is to expose aggregated aging metrics — including unapplied and unidentified cash amounts and counts — to reporting tools and integrations, while enforcing organization-level (ORG_ID) security and row-level access filtering typical of the FII secured view pattern. Because it reads from a materialized view rather than base transaction tables, the view delivers fast response for dashboards and collection-agreement aging reports, at the cost of data that is only as current as the last refresh of the underlying materialized view.

Underlying Base Objects

Documented metadata records no separate referenced base objects other than the materialized view itself. The view text is a straightforward projection:

• FII_AR_RCT_AGING_AGRT_MV — the single documented source object. The view selects all columns from this materialized view without joins, filters, or aggregation in the view definition, so all computation occurs in the materialized view refresh.

Consequently, column definitions, aging bucket logic, and refresh scheduling are inherited from FII_AR_RCT_AGING_AGRT_MV. The view text draws columns such as TIME_ID, PARTY_ID, CUST_ACCOUNT_ID, COLLECTOR_ID, and the aging and unapplied metrics directly from that materialized view. Where the metadata lists column names without the "_SEC" suffix (for example, AGING_BUCKET_1_AMOUNT, UNID_AMOUNT, UNAPP_AMOUNT, TOTAL_UNAPPLIED_AMOUNT, TOTAL_UNAPPLIED_COUNT), these correspond to the secured columns projected in the view text.

Key Columns

• TIME_ID / PERIOD_TYPE_ID — identify the reporting period and its granularity (for example, calendar or fiscal bucket) to which the aging snapshot applies.
• PARTY_ID / PARENT_PARTY_ID — the customer party and its parent hierarchy node, enabling roll-up reporting across related customer organizations.
• CUST_ACCOUNT_ID — the customer account (site-level account) associated with the receivable balance.
• COLLECTOR_ID — the collections agent responsible for the account, the principal grouping dimension for collector productivity and aging reports.
• ORG_ID — the operating unit; drives multi-org security filtering applied through the secured view layer.
• AGING_BUCKET_1_AMOUNT_SEC / _COUNT through AGING_BUCKET_3_AMOUNT_SEC / _COUNT — aged receivable amounts and transaction counts distributed across three aging buckets.
• UNID_AMOUNT_SEC — unidentified (unapplied to any account) cash amounts.
• UNAPP_AMOUNT_SEC — unapplied cash amounts held against the account.
• TOTAL_UNAPPLIED_AMOUNT_SEC — the aggregate unapplied amount for the grouping.
• TOTAL_UNAPPLIED_COUNT — the count of unapplied items, corresponding to the commonly searched term total_unapplied_count; it is the metric used to quantify how many receipts or items remain unapplied for a collector, customer, or period.
• GID — the global identifier supporting cross-organization or global consolidation reporting.

Common Use Cases and Queries

Typical uses include Collections aging dashboards, collector-level unapplied cash tracking, and period-over-period comparison of receivable buckets. A representative query counts unapplied items by collector:

• SELECT collector_id, time_id, SUM(total_unapplied_amount_sec) total_amount, SUM(total_unapplied_count) total_unapplied_count FROM fii_ar_rct_aging_agrt_mv_s_v WHERE org_id = :p_org_id GROUP BY collector_id, time_id;
• SELECT party_id, cust_account_id, aging_bucket_1_amount_sec, aging_bucket_2_amount_sec, aging_bucket_3_amount_sec, unapp_amount_sec, total_unapplied_count FROM fii_ar_rct_aging_agrt_mv_s_v WHERE period_type_id = :p_period AND gid = :p_gid;

Because ORG_ID security is applied by the view, queries should supply a valid operating unit context. Reports requiring current data should confirm the refresh status of FII_AR_RCT_AGING_AGRT_MV, since the view itself performs no real-time computation.