Search Results fii_ar_unid_customer




Overview
Explore in AI Chat

Overview

APPS.FII_AR_COLLECTORS_V is a reporting and integration view within the Oracle E-Business Suite Receivables (AR) module, delivered as part of the FII (Financial Intelligence/analytics) application schema. Its purpose is to present a unified list of collectors that can be used in Receivables analysis and operational reporting. Functionally, the view extends the standard AR_COLLECTORS table by appending a single synthetic row representing an "Unidentified Customer" concept, identified by a constant COLLECTOR_ID of -1.

The view therefore behaves as a presentation-layer wrapper: consumers querying it receive all genuine collector records from the base table plus one additional pseudo-collector used as a placeholder or catch-all designation. This pattern is common in EBS analytics views, where a reserved row is added so that reports and dashboards can display or aggregate activity that has not been assigned to a real collector or customer.

Underlying Base Objects

The view text is documented as a UNION ALL of two SELECT statements. The first selects directly from AR_COLLECTORS, the base Receivables table that stores collector definitions. The second selects from DUAL and constructs a single hard-coded row. Although the ETRM metadata lists no formally documented referenced base objects, the view text explicitly names AR_COLLECTORS as its only physical source table. No joins to other tables are present.

  • AR_COLLECTORS — supplies COLLECTOR_ID, DESCRIPTION, EMPLOYEE_ID, INACTIVE_DATE, NAME, STATUS, TELEPHONE_NUMBER and ALIAS for real collectors.
  • DUAL — used to inject the synthetic "-1" collector row.
  • FND_MESSAGE.get_string — a standard EBS message-lookup function invoked twice to derive the translated description and name for the synthetic row, using the message name FII_AR_UNID_CUSTOMER.

Key Columns

The view exposes the same column list as AR_COLLECTORS, allowing it to be used as a drop-in replacement in queries against that table.

  • COLLECTOR_ID — Primary identifier for the collector. Real records carry the native AR_COLLECTORS key; the synthetic row always has the value -1, which callers can test for explicitly.
  • NAME — Collector name. For the synthetic row, this resolves to the FII_AR_UNID_CUSTOMER message text.
  • DESCRIPTION — Descriptive label. For the synthetic row, this also resolves from the FII_AR_UNID_CUSTOMER message.
  • EMPLOYEE_ID — The HR employee associated with the collector; NULL for the synthetic row.
  • STATUS — Collector status. The synthetic row is hard-coded to 'A' (active).
  • INACTIVE_DATE, TELEPHONE_NUMBER, ALIAS — Collector attributes taken from the base table; all NULL for the synthetic row.

Common Use Cases and Queries

This view is typically used in Receivables reporting where a complete, localized collector list is required, including the reserved unidentified-customer entry. A common pattern is to join the view to AR transactions or collections data so unassigned activity can be presented alongside assigned collectors.

To list all collectors, including the synthetic entry:

  • SELECT collector_id, name, description, status FROM apps.fii_ar_collectors_v;

To retrieve only real collectors (excluding the -1 placeholder):

  • SELECT collector_id, name, status FROM apps.fii_ar_collectors_v WHERE collector_id <> -1;

The FII_AR_UNID_CUSTOMER reference in the view — which corresponds to the searched term "fii_ar_unid_customer" — is the FND message that supplies the localized label for the synthetic unidentified-customer row. Because the label is resolved at runtime through FND_MESSAGE.get_string, the text respects the session's language, making the view suitable for multilingual deployments.