Search Results fii_ar_cust_lov_v

Overview

The view FII_AR_CUST_LOV_V belongs to the FII (Financial Intelligence) product family, a legacy Oracle EBS reporting and analytics layer that is documented as obsolete in the ETRM reference set for releases 12.1.1 and 12.2.2. The view is designed to expose a flattened, list-of-values (LOV) oriented representation of the Customer Dimension used by FII analytics. Specifically, it returns the party hierarchy in association with customer account identifiers so that downstream reports, dashboards, and value-set style pickers can present customers in their correct parent-child context.

The name of the view — combining the FII prefix, the AR (Receivables) module indicator, and the CUST_LOV suffix — signals its intended purpose: it is a convenience object for populating customer LOVs and hierarchy-aware selections within FII customer dimension reporting. It is not a transactional view; it delivers reference and hierarchy metadata rather than balances or receivable activity.

The documented metadata states plainly that the view is "Not implemented in this database." In practice this means the object frequently does not exist as a deployed database object even in environments where FII was licensed, and any reference to it in custom code should be validated against the target instance before use.

Underlying Base Objects

The ETRM metadata records no referenced base objects for this view, but the supplied view text identifies the objects actually queried. The view selects from HZ_PARTIES twice — once as the child alias (CHIL) and once as the parent alias (PARENT) in an outer-join configuration. A third source is the FII_CUSTOMER_HIERARCHIES table, which supplies the parent/child party relationships from which the hierarchy is derived.

The join logic filters records so that the hierarchy row matches the child party (NEXT_LEVEL_PARTY_ID = CHILD_PARTY_ID) and excludes self-referencing rows (PARENT_PARTY_ID <> CHILD_PARTY_ID). The second half of the view is a UNION ALL that manufactures a single synthetic row via FND_MESSAGE.GET_STRING, using the FII message token FII_AR_UNID_CUSTOMER, with ID fixed at -2 and a placeholder parent value of '-'. This synthetic row typically represents an "unidentified" or catch-all customer member in the FII dimension, ensuring the LOV always contains at least one default entry.

Key Columns

• ID — The party identifier of the next-level party (NEXT_LEVEL_PARTY_ID). The synthetic row returns -2.
• VALUE — The display value for the LOV, taken from the child party's PARTY_NAME (HZ_PARTIES.PARTY_NAME as CHIL). The synthetic row returns the FII message string FII_AR_UNID_CUSTOMER.
• PARENT_VALUE — The parent party's name, derived from HZ_PARTIES.PARTY_NAME via the outer join. When no parent exists, NVL substitutes a '-'. The synthetic row also returns '-'.

These three columns map cleanly to the conventions expected by Oracle Forms LOVs and by BI/XML Publisher parameter LOVs, where an ID, a display value, and a parent/grouping value are required.

Common Use Cases and Queries

The primary use case is populating a customer selection list that respects hierarchy. A typical retrieval mirrors the view's own projection:

• Full LOV retrieval — SELECT id, value, parent_value FROM fii_ar_cust_lov_v ORDER BY parent_value, value;
• Child lookup for a known ID — SELECT value, parent_value FROM fii_ar_cust_lov_v WHERE id = :party_id;
• Top-level or orphan parties — SELECT id, value FROM fii_ar_cust_lov_v WHERE parent_value = '-';

Because the view is documented as obsolete and "not implemented," any implementation that still references it should be treated as legacy. Where the object is absent, equivalent logic must be reconstructed directly against HZ_PARTIES and the relevant hierarchy source, or the FII customer dimension should be replaced with the current Oracle EBS customer hierarchy and Receivables reporting objects. This view should be regarded as a migration and remediation concern rather than a supported integration point in 12.1.1 or 12.2.2.