Results for “fii_ar_sic_code_base_v”

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

Overview

FII_AR_SIC_CODE_BASE_V is a view historically shipped with the Oracle Financial Intelligence (FII) product family in Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2 it is documented as part of FII, a module now classified as obsolete. The view exists to produce a consolidated, de-duplicated list of Standard Industrial Classification (SIC) codes drawn from multiple receivables-related and supplier-related sources across the EBS data model. Its role was to feed Financial Intelligence analytics, dimensional modeling, and cross-module reporting where a single unified list of industry classifications was required rather than querying each transactional table independently.

The object is registered in ETRM as a view, but the documented metadata explicitly states "Not implemented in this database." This indicates that in a typical 12.1.1 or 12.2.2 installation the view is not created by the standard AD utilities; it is only present when the FII product components were installed. As a legacy or obsolete object, it may not exist at all in a current environment, and any report or interface referencing it must be validated before use.

Underlying Base Objects

The ETRM documentation records no referenced base objects, but the published view text defines it precisely as a UNION ALL of three aggregation queries:

• HZ_PARTIES — Party records, filtered on SIC_CODE IS NOT NULL, grouped by SIC_CODE with MAX(LAST_UPDATE_DATE).
• HZ_CUST_SITE_USES_ALL — Customer site uses, filtered on SIC_CODE IS NOT NULL, grouped by SIC_CODE with MAX(LAST_UPDATE_DATE).
• PO_VENDORS — Supplier records, using the column STANDARD_INDUSTRY_CLASS aliased to SIC_CODE, grouped with MAX(LAST_UPDATE_DATE).

Because the view uses UNION ALL rather than UNION, the same SIC code can appear multiple times if it exists in more than one source table. The DISTINCT and GROUP BY operations remove duplicates only within each individual source, not across the combined result set. Consumers of the view must therefore apply their own de-duplication when a unique list is required.

Key Columns

• SIC_CODE — The industry classification value. Note that for rows sourced from PO_VENDORS this column is populated from STANDARD_INDUSTRY_CLASS, so the view normalizes two differently named attributes into one column. The result set is a mix of HZ party SIC codes and supplier standard industry classifications.
• LAST_UPDATE_DATE — The most recent last-update timestamp for any record carrying that SIC code within the originating table. This supports incremental extraction and change-detection patterns, allowing a consumer to identify SIC codes touched since a prior run.

No other columns are exposed. There is no source-table discriminator column, so the origin of a given SIC code cannot be determined from the view output alone.

Common Use Cases and Queries

Typical usage centers on populating a reference list of industry codes for analysis or LOV-style selection. A basic extraction is:

SELECT sic_code, last_update_date
FROM   fii_ar_sic_code_base_v
ORDER BY sic_code;

To obtain a truly unique list, apply DISTINCT at the outer level:

SELECT DISTINCT sic_code
FROM   fii_ar_sic_code_base_v
ORDER BY sic_code;

For incremental processing of recently changed codes:

SELECT sic_code, MAX(last_update_date) last_update_date
FROM   fii_ar_sic_code_base_v
WHERE  last_update_date >= :last_run_date
GROUP BY sic_code;

Before deploying any of these, confirm the view exists using ALL_VIEWS or DBA_VIEWS. Because FII is obsolete and the view is documented as not implemented, a safer approach in supported 12.2.2 environments is to build an equivalent query directly against HZ_PARTIES, HZ_CUST_SITE_USES_ALL, and PO_VENDORS, or to migrate to POZ_SUPPLIERS and the current party model.