Search Results aging_bucket_2_amount_func

Overview

The view APPS.FII_AR_RCT_AGING_AGRT_MV_F_V is a Financial Intelligence (FII) reporting object shipped in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a curated projection of Accounts Receivable receipt and aging data that has already been consolidated into the materialized view FII_AR_RCT_AGING_AGRT_MV. The suffix convention _F_V denotes a "foreign" or reporting-facing view whose columns are renamed relative to the materialized view, so that downstream Oracle Business Intelligence (OBIEE) / Financial Intelligence dashboards and Discoverer workbooks can present the fields under stable, presentation-oriented names.

The view supplies receipt aging data at the intersection of time, party, customer account, collector, and operating unit. It is one of the primary sources behind the Receipts and Aging reporting subject areas delivered with the FII product family, and it is also commonly queried directly by customer-developed BI Publisher reports and SQL-based extracts where a flattened, column-renamed aging dataset is required.

Underlying Base Objects

The ETRM documentation records exactly one referenced object for this view: the materialized view FII_AR_RCT_AGING_AGRT_MV. No base tables are documented directly, which is expected, because the view is a thin projection layer over the materialized view rather than a join across transactional tables.

The relationship is a straightforward one-to-one column alias mapping. Every column selected in the view originates from a column of the same semantic content in the materialized view; the _FUNC suffix attached to several numeric measures signals that the corresponding materialized view column is stored in functional (ledger) currency rather than entered currency. The materialized view itself is populated by the FII collection programs, which aggregate AR receipt and aging balances by the dimensions carried through this view. Because the view contains no joins, filters, or aggregation of its own, its performance and currency characteristics are inherited entirely from the underlying materialized view and its refresh schedule.

Key Columns

• TIME_ID, PERIOD_TYPE_ID — Identify the reporting period and the period-type context (for example, day, week, or accounting period) to which each row's measures belong.
• PARENT_PARTY_ID, PARTY_ID — Support party-level and parent-party-level reporting hierarchies, allowing roll-ups from an individual party to its parent organization.
• CUST_ACCOUNT_ID, COLLECTOR_ID, ORG_ID — Provide the customer account, collections agent, and operating unit (ledger) dimensions used for filtering and drill-down.
• AGING_BUCKET_1_AMOUNT_FUNC, AGING_BUCKET_2_AMOUNT_FUNC, AGING_BUCKET_3_AMOUNT_FUNC — Functional-currency receivable amounts falling into each of the three aging buckets, typically representing current, past-due, and severely past-due balances.
• AGING_BUCKET_1_COUNT, AGING_BUCKET_2_COUNT, AGING_BUCKET_3_COUNT — Transaction or receipt counts corresponding to each aging bucket.
• UNID_AMOUNT_FUNC — Functional-currency amount of unapplied but identified receipts; that is, receipts that have a known application target but are not yet fully applied.
• UNAPP_AMOUNT_FUNC — The column most often referenced in the search term "unapp_amount_func". It carries the functional-currency amount of unapplied and unidentified receipts, representing cash held on account without a designated customer or invoice target. It is the primary measure for cash-in-hand and unapplied-receipt reporting.
• TOTAL_UNAPPLIED_AMOUNT_FUNC, TOTAL_UNAPPLIED_COUNT — The combined unapplied amount (identified plus unidentified) and its associated receipt count.
• GID — Warehouse group identifier used by Financial Intelligence for ETL lineage and refresh control.

Common Use Cases and Queries

Typical use cases include unapplied cash analysis, aging-bucket trend reporting, and collector-performance dashboards. The view is frequently joined to FII dimension views such as FII_AR_CUSTOMERS or FII_AR_COLLECTORS to render descriptive names.

• Unapplied receipts by operating unit:

  SELECT org_id,
         SUM(unapp_amount_func) AS unapplied_amt,
         SUM(unid_amount_func) AS unidentified_amt,
         SUM(total_unapplied_amount_func) AS total_unapplied
  FROM   apps.fii_ar_rct_aging_agrt_mv_f_v
  GROUP  BY org_id;

• Aging detail for a specific customer account and period:

  SELECT time_id, aging_bucket_1_amount_func,
         aging_bucket_2_amount_func, aging_bucket_3_amount_func
  FROM   apps.fii_ar_rct_aging_agrt_mv_f_v
  WHERE  cust_account_id = :cust_account_id
  AND    time_id = :time_id;

• Collector-level unapplied concentration:

  SELECT collector_id,
         SUM(unapp_amount_func) AS unapp,
         SUM(total_unapplied_count) AS receipt_count
  FROM   apps.fii_ar_rct_aging_agrt_mv_f_v
  GROUP  BY collector_id
  ORDER  BY unapp DESC;

Because the object is a view, no separate grants or synonyms beyond the standard APPS synonyms apply, and access is governed by the same APPS responsibility and security profiles that restrict the underlying materialized view.