Search Results receivable_g




Overview
Explore in AI Chat

Overview

APPS.FII_AR_DISPUTE_REC_PMV is a seeded Oracle E-Business Suite database view owned by the APPS schema and registered in the FND Design Data repository under the application short name FII. It is classified as an internal view with a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. Its name follows the FII (Financial Intelligence) naming convention and the _PMV suffix common to Oracle's packaged materialized-view-style reporting objects, indicating that it is designed to expose pre-aggregated or pre-joined dispute and receivable data for downstream analytical consumption rather than for transactional processing.

The view presents one row per disputed receivable installment, combining invoice-level attributes, dispute timing metrics, and currency information. Because it is documented as Oracle Internal Use Only, Oracle Corporation does not support direct access to this object from customer-written SQL or external integrations except through standard Oracle Applications programs. In practice it surfaces as the data source behind seeded FII dispute dashboards and receivables-related analytics in the Oracle Business Intelligence and Financial Intelligence product families.

Underlying Base Objects

The documented dependency list identifies APPS.FII_AR_OPEN_INSTALLMENT_F as the single referenced base object. FII_AR_OPEN_INSTALLMENT_F is a Financial Intelligence fact-like object that stores open receivable installment records drawn from the Oracle Receivables transaction and payment schedules. The view therefore inherits its grain from that object: each row corresponds to an open or disputed installment associated with an AR invoice.

The metadata further states that FII_AR_DISPUTE_REC_PMV is not referenced by any other database object. This confirms it sits at the top of its dependency chain and is consumed directly by reporting layers rather than by further packaged objects. No additional base tables, synonyms, or joins are documented beyond FII_AR_OPEN_INSTALLMENT_F, so column derivations such as DAYS_PAST_DUE, DAYS_IN_DISPUTE, and the currency display fields should be understood as being computed within the view definition itself.

Key Columns

  • SOB_ID — Set of Books identifier, anchoring the record to the ledger under which the receivable was recorded in 12.1.1 (replaced conceptually by ledger identifiers in 12.2.2).
  • ORG_ID — Organization identifier, used for multi-org security filtering so that only operating unit data is returned to authorized users.
  • CUSTOMER_ID / CUSTOMER_NAME — The bill-to customer party identifier and its display name (VARCHAR2 120).
  • INVOICE_NUMBER — The AR invoice number (VARCHAR2 30) associated with the disputed installment.
  • DUE_DATE / DISPUTE_DATE — The installment due date and the date the dispute was recorded.
  • DAYS_PAST_DUE / DAYS_IN_DISPUTE — Derived numeric aging metrics supporting dispute aging and collections analysis.
  • FUNCTIONAL_CURRENCY / INVOICE_CURRENCY — The ledger functional currency and the transaction currency of the invoice (VARCHAR2 80 each), enabling dual-currency comparison.
  • RECEIVABLE_G — The receivable amount. The _G suffix denotes a global or generic currency amount used by Financial Intelligence aggregation across currencies; this column corresponds directly to the "receivable_g" search term and represents the primary monetary measure exposed by the view.

Common Use Cases and Queries

Typical usage centers on dispute aging, collections prioritization, and receivables exposure reporting. A standard projection is:

  • SELECT ORG_ID, CUSTOMER_NAME, INVOICE_NUMBER, DUE_DATE, DISPUTE_DATE, DAYS_IN_DISPUTE, INVOICE_CURRENCY, RECEIVABLE_G FROM APPS.FII_AR_DISPUTE_REC_PMV;
  • Filtering by DAYS_IN_DISPUTE to bucket disputes into 0–30, 31–60, and 60+ aging bands.
  • Aggregating SUM(RECEIVABLE_G) GROUP BY CUSTOMER_ID or ORG_ID to quantify disputed exposure per customer or operating unit.
  • Joining on CUSTOMER_ID or INVOICE_NUMBER to HZ_CUST_ACCOUNTS or RA_CUSTOMER_TRX_ALL for supplemental collection attributes.

Because the object is unsupported for direct customer access, these queries should be treated as investigative or diagnostic, and production reporting should route through the supported Oracle Financial Intelligence extracts and dashboards.