Search Results aging_bucket_2_amount_sec




Overview
Explore in AI Chat

Overview

The view APPS.FII_AR_RCT_AGING_BASE_MV_S_V is a dictionary view owned by the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is the primary, exposed layer of the Oracle Receivables (AR) aging base materialized view used by the Financial Intelligence (FII) analytics and Receivables collections reporting stack. The "_MV_S_V" suffix indicates that this object is a view built on top of an underlying materialized view (FII_AR_RCT_AGING_BASE_MV), a standard Oracle EBS pattern used to isolate a stable, published column interface from the potentially internal structure of the materialized view. Its functional purpose is to present aged receivables balances — totals and counts per aging bucket — and unapplied/unidentified cash amounts, aggregated along the standard Receivables dimensions: time, party, collector, operating unit, and customer class.

The view is intended for Oracle-internal use by delivered FII Reports, Dashboards, and the Receivables Collection Analytics (Collections "Aging") functionality. Because of the FND Design Data designation (FII.FII_AR_RCT_AGING_BASE_MV_S_V), it is registered as a design-time FII object and is populated by the delivered Collections data-refresh programs. Oracle's standard disclaimer applies: the object is documented and shipped as Oracle Internal Use Only, and Oracle Corporation does not support direct application data access through this object except from standard Oracle Applications programs. Nevertheless, technical teams routinely query it read-only for ad hoc aging analytics.

Underlying Base Objects

The documented dependency information states that FII_AR_RCT_AGING_BASE_MV_S_V references a single base object: APPS.FII_AR_RCT_AGING_BASE_MV. This confirms the "_S_V" pattern — the view is a thin wrapper over the aging materialized view rather than a join of multiple source tables. The materialized view itself derives its rows from the Receivables transactions and receipt/unapplied-cash tables (AR_PAYMENT_SCHEDULES_ALL, RA_CUSTOMER_TRX_ALL, AR_RECEIVABLE_APPLICATIONS_ALL, and AR_CASH_RECEIPTS_ALL), aggregated into pre-computed aging buckets at a defined snapshot (TIME_ID) granularity. The ETRM record does not document any business objects that reference FII_AR_RCT_AGING_BASE_MV_S_V; the view exposes data to the FII reporting layer rather than acting as a base object for further schema objects. There are no documented mandatory columns; each column is nullable in the dictionary.

Key Columns

  • TIME_ID, PERIOD_TYPE_ID — Snapshot and period type identifying the as-of date of the aging figures (e.g., a day, week, or accounting period snapshot).
  • PARTY_ID, PARENT_PARTY_ID, CUST_ACCOUNT_ID — Trading partner, parent party roll-up, and Receivables customer account identifying the debtor.
  • COLLECTOR_ID, ORG_ID — Collector (collections agent) responsible for the account and the operating unit (ORG_ID) that owns the receivable — the key Multi-Org access control column.
  • CLASS_CODE, CLASS_CATEGORY — Customer/transaction classification values used to slice aging by line of business or category.
  • AGING_BUCKET_1_AMOUNT / _COUNT through AGING_BUCKET_3_AMOUNT / _COUNT — Aged balance and transaction/item count for each of the delivered aging buckets (commonly "current," "1–30 days," and "31–60 days," extendable by configuration).
  • UNID_AMOUNT — Unapplied amount flagged as Unidentified cash: receipts received but not yet identified to any customer, appearing as an unapplied receipt in cash management. This is the column most commonly sought by users searching "unid_amount."
  • UNAPP_AMOUNT — Amount of receipts applied to the account/customer but not yet applied to a specific transaction.
  • TOTAL_UNAPPLIED_AMOUNT / TOTAL_UNAPPLIED_COUNT — Total unapplied and unidentified cash value and the associated count of items for the aggregation key.
  • GID — Group identifier used by the FII analytics engine to reconcile the aggregation grain (Time × GL segment × Party × Collector).

Common Use Cases and Queries

The view supports collections aging analysis, unapplied and unidentified cash exposure reporting, and collector productivity dashboards. Because the object is Oracle Internal Use Only, queries are typically run read-only in reporting schemas or custom reports, always constrained by ORG_ID to respect Multi-Org access.

SELECT time_id,
       period_type_id,
       party_id,
       cust_account_id,
       collector_id,
       org_id,
       SUM(aging_bucket_1_amount) AS current,
       SUM(aging_bucket_2_amount) AS b2,
       SUM(aging_bucket_3_amount) AS b3,
       SUM(unid_amount)           AS unidentified_cash,
       SUM(unapp_amount)          AS unapplied_cash,
       SUM(total_unapplied_amount) AS total_unapplied
FROM   apps.fii_ar_rct_aging_base_mv_s_v
WHERE  org_id = :p_org_id
AND    time_id = :p_time_id
GROUP BY time_id, period_type_id, party_id, cust_account_id, collector_id, org_id
ORDER BY total_unapplied DESC;

A second common pattern focuses specifically on the "unid_amount" search target — reporting unidentified and unapplied receipts at the customer account level for a given snapshot to drive cash-application follow-up. Note that the view returns pre-aggregated snapshot data; drill-down to individual receipts requires the underlying AR cash receipt and application tables. Because of the internal-use restriction, any custom use should be confined to read-only reporting and revalidated after applying FII/AR patches or a product upgrade.