Search Results next_level_party_id




Overview

APPS.FII_AR_CUST_LOV_V is a reporting view in the Oracle E-Business Suite Financial Intelligence (FII) module, used primarily to populate the customer list of values (LOV) in Accounts Receivable and Financial Intelligence reporting screens. Its central purpose is to present a flattened, display-ready list of customers that participate in a customer hierarchy relationship, exposing both the child (next-level) party and its parent party as paired display values. The view derives its data from Oracle's Trading Community Architecture (TCA) party model and from the FII customer hierarchy definition table.

The view is significant for the child_party_id search context because the inline subquery over FII_CUSTOMER_HIERARCHIES filters specifically on the relationship where next_level_party_id = child_party_id and excludes self-referencing rows (parent_party_id <> child_party_id). This makes the view a compact representation of parent–child customer linkage for LOV consumption.

Underlying Base Objects

Per the ETRM metadata, no referenced base objects are separately documented, but the view text itself establishes the following dependencies:

  • HZ_PARTIES — referenced twice, aliased as CHIL (the child/next-level party) and PARENT (the parent party). The outer join PARENT.PARTY_ID(+) allows child parties with no matching parent to still appear.
  • FII_CUSTOMER_HIERARCHIES — the inline view supplying PARENT_PARTY_ID and NEXT_LEVEL_PARTY_ID, filtered on the child-party relationship.
  • FND_MESSAGE — accessed via FND_MESSAGE.GET_STRING to supply the localized label for the "Unidentified Customer" sentinel row.
  • DUAL — used to append the sentinel record with ID -2.

Key Columns

  • ID — the surrogate identifier used by the LOV. It returns NEXT_LEVEL_PARTY_ID for hierarchical rows, and the constant -2 for the unidentified-customer entry.
  • VALUE — the display text; the child party name from HZ_PARTIES.PARTY_NAME, or the FND message string for the sentinel row.
  • PARENT_VALUE — the display text of the parent party, or '-' when no parent name exists or for the sentinel row.

The UNION ALL construction guarantees that the unidentified customer option always appears at the end of the LOV result set regardless of hierarchy content.

Common Use Cases and Queries

Typical usage includes driving customer LOVs, validating hierarchy membership, and resolving child-to-parent naming for reporting extracts.

SELECT id, value, parent_value
FROM   apps.fii_ar_cust_lov_v
ORDER BY value;
SELECT id, value
FROM   apps.fii_ar_cust_lov_v
WHERE  parent_value = '-';

The second query isolates top-level or unparented customers, useful when reconciling hierarchy definitions. Because the view filters on the child_party_id relationship, it should be treated as a purpose-built LOV source rather than a general TCA party query.