Search Results total_unapplied_amount_sec




Overview
Explore in AI Chat

Overview

APPS.FII_AR_RCT_AGING_AGRT_MV_S_V is a reporting view in the Oracle E-Business Suite Receivables (AR) module, exposed under the APPS schema. Its name follows the FII (Financial Intelligence) naming convention used by Oracle's embedded analytics and receivables reporting infrastructure, where the suffix _MV denotes a materialized view base object and _S_V denotes a synonym-style view layered over that materialized view. The view presents Accounts Receivable receipt and aging data aggregated by agreement, time period, party, customer account, collector, and operating unit. It surfaces secured (SEC) monetary amounts, which indicates the columns support Oracle's data security model so that rows returned are filtered according to the responsibility's data access privileges. In the context of Oracle EBS 12.1.1 and 12.2.2, this view is consumed by receivables aging and collection reporting, dashboards, and downstream integration extracts where pre-aggregated aging and unapplied receipt balances are required. The user-search term unapp_amount_sec maps directly to the UNAPP_AMOUNT_SEC column, the secured unapplied amount measure.

Underlying Base Objects

The documented metadata states the view is defined over a single base object: the materialized view FII_AR_RCT_AGING_AGRT_MV. The definition is a straightforward projection — the view selects the full column list from that materialized view without joins, filters, or transformations of its own. Consequently, all aggregation, security enforcement, and refresh behavior are inherited from the materialized view. No additional base tables are documented, so the aging buckets, unapplied balances, and identification amounts are pre-computed and stored by the materialized view rather than derived at query time. This design means query performance is entirely dependent on the refresh schedule of FII_AR_RCT_AGING_AGRT_MV; the _S_V layer exists primarily to provide a naming convention and access point consistent with Oracle's secured view pattern.

Key Columns

Common Use Cases and Queries

Typical uses include receivables aging analysis, unapplied receipt monitoring, and collector performance reporting. Queries generally filter on PERIOD_TYPE_ID, ORG_ID, and COLLECTOR_ID and aggregate across the party or account grain.

  • Unapplied receipts by collector:
    SELECT collector_id, org_id, SUM(unapp_amount_sec) unapplied, SUM(total_unapplied_amount_sec) total_unapplied FROM apps.fii_ar_rct_aging_agrt_mv_s_v WHERE time_id = :p_time_id GROUP BY collector_id, org_id;
  • Aging buckets for a customer account:
    SELECT cust_account_id, aging_bucket_1_amount_sec, aging_bucket_2_amount_sec, aging_bucket_3_amount_sec FROM apps.fii_ar_rct_aging_agrt_mv_s_v WHERE cust_account_id = :p_cust_account_id AND period_type_id = :p_period_type;
  • Unidentified versus unapplied comparison:
    SELECT party_id, unid_amount_sec, unapp_amount_sec FROM apps.fii_ar_rct_aging_agrt_mv_s_v WHERE org_id = :p_org_id;

Because amounts are secured via GID and the SEC columns, results automatically reflect the data access privileges of the querying responsibility. Reporting windows should align to the materialized view refresh schedule to avoid stale figures.