Search Results billing_activity_amount_sec




Overview
Explore in AI Chat

Overview

APPS.FII_AR_NET_REC_AGRT_MV_S_V is a read-only reporting view in the Oracle E-Business Suite Receivables (AR) module, owned by the Applications schema (APPS). It exposes the contents of the materialized view FII_AR_NET_REC_AGRT_MV, which forms part of the Oracle Financials Intelligence / ETRM (Enterprise Transaction Reporting Model) reporting layer for Receivables. The view presents net receivables activity aggregated by agreement, party, customer account, collector, operating unit, and time period, together with a set of aged buckets that classify open balances as current or past due.

The suffix conventions are significant: the trailing _S_V indicates a secured view, meaning it is intended to enforce row-level security and organizational access restrictions when queried by reporting tools or integrated applications. Every amount column carries the _SEC suffix, which denotes that the value is expressed in the secured/preferred currency of the reporting context rather than the original transaction currency. This design allows downstream dashboards, such as the Receivables aging and collections analytics, to present consistent, currency-normalized figures without exposing cross-organization data.

Underlying Base Objects

The view is defined over a single object: the materialized view FII_AR_NET_REC_AGRT_MV. It performs a direct projection of all columns from that materialized view with no joins, filters, or calculations applied at the view layer. Consequently, all aggregation, bucketing, and currency conversion logic resides within the materialized view and its refresh program. No additional base tables are documented as referenced objects, and the ETRM metadata records no traditional base-table dependencies for this view. Performance characteristics therefore reflect the materialized view refresh schedule and the underlying indexes on its key dimensions (TIME_ID, ORG_ID, CUST_ACCOUNT_ID, and COLLECTOR_ID).

Key Columns

Common Use Cases and Queries

This view is typically consumed by collections dashboards, aging reports, and DSO analysis where secured, currency-normalized values are mandatory. A representative query to retrieve debit memo exposure by customer account for a given period follows:

  • SELECT cust_account_id, SUM(dm_amount_sec) AS dm_total FROM apps.fii_ar_net_rec_agrt_mv_s_v WHERE org_id = :p_org_id AND time_id = :p_time_id GROUP BY cust_account_id ORDER BY dm_total DESC;
  • SELECT collector_id, SUM(past_due_bucket_1_amount_sec) pd1, SUM(past_due_bucket_2_amount_sec) pd2, SUM(total_open_amount_sec) total_open FROM apps.fii_ar_net_rec_agrt_mv_s_v WHERE org_id = :p_org_id AND period_type_id = :p_period_type GROUP BY collector_id;
  • SELECT time_id, SUM(total_receipt_amount_sec) receipts, SUM(rev_amount_sec) revenue FROM apps.fii_ar_net_rec_agrt_mv_s_v WHERE cust_account_id = :p_cust_account_id GROUP BY time_id ORDER BY time_id;

Because the view enforces security, queries executed under a responsibility with restricted organization access return only the operating units that responsibility is authorized to see. Reporting integrations should therefore always bind ORG_ID and TIME_ID to benefit from the materialized view's indexing and to avoid full scans of the aggregated dataset.