Search Results current_open_amount_prim

Overview

FII_AR_NET_REC_BASE_MV_P_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the Financial Intelligence (FII) product family. It exposes the primary-currency (functional currency) presentation layer of the Accounts Receivable net receivables base materialized view used by Oracle Receivables and Financial Intelligence reporting, dashboards, and analytics. The view serves as the "prim" mode of access: every amount column is suffixed _PRIM, indicating that balances are stored and returned in the ledger's primary currency rather than a converted reporting currency. Because it is a thin projection over a materialized view rather than a transactional table, queries against it return pre-aggregated, pre-computed period snapshots rather than live subledger transactions, which makes it suitable for high-volume analytic workloads such as collections efficiency, Days Sales Outstanding (DSO), aging analysis, and receivables performance reporting.

Underlying Base Objects

The view is defined over a single documented object: FII_AR_NET_REC_BASE_MV, the AR net receivables base materialized view. ETRM metadata for this specific view records no further referenced base objects, and the view text is a direct column-selection statement with no joins, filters, or transformations. In practice, the underlying materialized view is refreshed from Receivables transactional data — invoice, receipt, adjustment, and customer account records aggregated by time and party — but the view itself performs no such aggregation; it simply renames and exposes the pre-materialized result set. Consequently, data currency is governed entirely by the refresh schedule of FII_AR_NET_REC_BASE_MV, not by query execution.

Key Columns

• TIME_ID / PERIOD_TYPE_ID — The reporting time dimension and granularity (for example day, week, or period) to which each aggregated snapshot belongs.
• PARTY_ID / PARENT_PARTY_ID / CUST_ACCOUNT_ID / COLLECTOR_ID / ORG_ID — Customer, party hierarchy, account, collector, and operating unit dimensions used to slice receivables by ownership and responsibility.
• CLASS_CODE / CLASS_CATEGORY — Receivables class and category classifications used to isolate transaction types such as invoices, debit memos, chargebacks, and deposits.
• CURRENT_OPEN_AMOUNT_PRIM / CURRENT_OPEN_COUNT — The current open receivable amount and transaction count in primary currency; this is the column most commonly targeted by searches for current_open_amount_prim and represents the core "what is currently outstanding" measure.
• PAST_DUE_OPEN_AMOUNT_PRIM / PAST_DUE_COUNT — The overdue open amount and count, complementing the current-open measure for aging analysis.
• CURRENT_BUCKET_1..3 and PAST_DUE_BUCKET_1..7 — Amount and count columns for the standard aging buckets (current plus up to seven past-due buckets), each suffixed _AMOUNT_PRIM or _COUNT.
• TOTAL_OPEN_AMOUNT_PRIM / TOTAL_OPEN_COUNT — Aggregate open receivables across current and past-due categories.
• WTD_TERMS_OUT_OPEN_NUM_PRIM, WTD_DDSO_DUE_NUM_PRIM, WTD_DAYS_PAID_NUM_PRIM — Weighted terms, DSO, and days-paid metrics supporting collections and credit performance reporting.
• HEADER_FILTER_DATE, GID, UMARKER — Control and lineage columns used for filtering report headers and identifying extract generations.

Common Use Cases and Queries

Typical usage is aggregation of open balances by collector, customer, or operating unit, and aging or DSO reporting by period. Because the view already supplies primary-currency amounts, no currency conversion is required. A representative query selecting the current open amount alongside past-due exposure is:

SELECT time_id, org_id, cust_account_id, collector_id,
  current_open_amount_prim,
  past_due_open_amount_prim,
  total_open_amount_prim,
  past_due_bucket_1_amount_prim
FROM apps.fii_ar_net_rec_base_mv_p_v
WHERE period_type_id = :p_period_type
  AND org_id = :p_org_id
ORDER BY total_open_amount_prim DESC;

A second common pattern sums the primary-currency open amount by collector to drive collections scorecards, and a third calculates the proportion of overdue to total open receivables to derive a past-due ratio. In all cases, callers should account for materialized view refresh lag, use the ORG_ID and CLASS_CODE predicates to scope results correctly, and reference CURRENT_OPEN_AMOUNT_PRIM rather than the unconverted counterparts found in the broader FII_AR_NET_REC_BASE_MV object.