Results for “fii_collectors”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The FII_COLLECTORS table belongs to the Financial Intelligence (FII) product family within Oracle E-Business Suite. FII was Oracle's analytical layer for receivables and collections performance, intended to stage and expose data about collection agents, collection strategies, and the customer accounts assigned to them. In the documented reference for EBS 12.1.1, the table is explicitly flagged as Obsolete and is recorded as not implemented in this database. Consumers upgrading from earlier releases, or sites that applied FII historically, may still encounter the object in their schema, but it is not part of a standard 12.1.1 or 12.2.2 installation.

Functionally, the object describes a collector dimension: the mapping of a collector to the parties, customer accounts, and account sites for which that collector is responsible. In this sense it acts as an assignment (bridge) between the collections organization and the receivables customer model. Following the heuristic Data Vault classification supplied in the metadata, the table is modelled as standalone; however, its structure — a composite key over party, account, and site-use identifiers with a foreign key to a collector — is more naturally treated as a link entity connecting collectors to customer accounts and sites, rather than a hub or satellite.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

• COLLECTOR_ID — the identifier of the collection agent. This is the sole documented foreign key, resolving to AR_COLLECTORS, and carries the core business meaning of the row.
• PARTY_ID — the trading party (customer) the collector is associated with; part of the primary key.
• CUST_ACCOUNT_ID — the receivables customer account; part of the primary key and of the unique business key.
• SITE_USE_ID — the customer site-use, narrowing the assignment down to a specific location; part of both the primary key and the unique business key.
• CREATION_DATE, CREATED_BY — standard audit columns recording who created the assignment and when.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent change and the login under which it occurred.

Two key structures are documented. The primary key, FII_COLLECTORS_PK, is the composite (PARTY_ID, CUST_ACCOUNT_ID, SITE_USE_ID), indicating that at most one collector assignment is recorded per combination of party, account, and site. The unique index FII_COLLECTORS_U1 covers (CUST_ACCOUNT_ID, SITE_USE_ID) and represents the business-key candidate, reinforcing that a site belongs to exactly one account context. Notably, the primary key does not include COLLECTOR_ID, so the table is not a pure many-to-many bridge over collectors.

Common Use Cases and Queries

Where the table is present, its principal use is determining which collector owns a given customer account or site, typically to drive collections reporting, dunning ownership, or collector-level aged-balance analysis. A representative join to the collectors master is:

• SELECT fc.cust_account_id, fc.site_use_id, ac.name
  FROM fii_collectors fc, ar_collectors ac
 WHERE fc.collector_id = ac.collector_id;

Because the table is obsolete and unimplemented, queries against it in a 12.1.1 or 12.2.2 instance will generally fail with an ORA-00942 (table or view does not exist). Confirmation of its absence, or discovery of any historical remnants, is usually performed through data dictionary views:

• SELECT owner, table_name, num_rows
  FROM all_tables WHERE table_name = 'FII_COLLECTORS';
• SELECT column_name, data_type
  FROM all_tab_columns WHERE table_name = 'FII_COLLECTORS';

When reconstructing collections ownership on a supported release, equivalent information is sourced from AR_COLLECTORS and the Receivables customer tables rather than from FII.

Related Objects

The following objects are the most significant in relation to this table:

• AR_COLLECTORS — the collector master, joined via FII_COLLECTORS.COLLECTOR_ID = AR_COLLECTORS.COLLECTOR_ID; the only documented foreign key relationship.
• HZ_CUST_ACCOUNTS — the customer account, joined on CUST_ACCOUNT_ID.
• HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL — the account site and site-use entities, joined on SITE_USE_ID.
• HZ_PARTIES — the party master, joined on PARTY_ID.
• AR_COLLECTOR_ASSIGNMENTS (where present) and the Receivables collections APIs — the supported mechanism for collector-to-account assignment in current releases.

As FII is obsolete, no supported APIs or concurrent programs create or maintain FII_COLLECTORS; integrations should target the Receivables collections objects instead.