Results for “user_attribute1”

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

Overview

FII_PROJ_CLS3_LCV is a Class 3 source view associated with Oracle Financial Intelligence (FII), the Financial Intelligence module that formed part of the Oracle E-Business Suite data warehousing and analytics stack. As documented in the ETRM metadata, this view is identified as obsolete and its description explicitly states that it is "the CLass 3 source view for the Project dimension in EDW" — that is, the Enterprise Data Warehouse. Within the EBS 12.1.1 and 12.2.2 architecture, Class 3 source views act as the third-tier abstraction layer that sits beneath the higher-level analytical and staging views consumed by the warehouse ETL processes, presenting Project dimension data in a normalized form aligned to the star-schema model of the EDW.

The view's role is to expose a Project class-3 (the third-level project classification) dimension to downstream extraction, transformation, and load routines. The suffix "LCV" conventionally denotes a "List of Values" (LOV) supporting view within the FII/EDW naming standards, indicating its intended use as a lookup source for value lists in the reporting and analytics layer.

Underlying Base Objects

Per the documented view text, FII_PROJ_CLS3_LCV is defined as a simple SELECT over a single underlying object: FIIBV_PROJ_CLS3_LCV. The view projects eleven output columns — the six substantive columns (PROJ_CLS3_PK, NAME, PROJECT_CLASS3, PROJ_CATEG3_FK, INSTANCE, LAST_UPDATE_DATE) and five trailing NULL placeholders that back the USER_ATTRIBUTE1 through USER_ATTRIBUTE5 columns.

The ETRM metadata lists no referenced base tables for this view, which is consistent with its status as a pass-through/derived view layered over another FII view rather than directly over application tables. The absence of documented base objects and the "Not implemented in this database" note indicate that in the 12.2.2 release, this specific view is not deployed; its functionality has been superseded by later FII/EDW objects. The INSTANCE column suggests multi-organization or multi-instance awareness, typical of FII warehouse source views.

Key Columns

• PROJ_CLS3_PK — The primary key surrogate for the Project class-3 dimension record, used as the unique identifier in the EDW star schema.
• NAME — The display name of the project class-3 value, used for labeling in reports and value lists.
• PROJECT_CLASS3 — The descriptive value of the third-level project classification.
• PROJ_CATEG3_FK — The foreign key linking this class-3 record to its parent project class-3 category; this column matches the user's search term and constitutes the join key to the corresponding category dimension.
• INSTANCE — Identifies the source EBS instance or organization, supporting multi-instance warehouse consolidation.
• LAST_UPDATE_DATE — The timestamp of the most recent change, used by incremental ETL processes to detect changed records.
• USER_ATTRIBUTE1–5 — Exposed as NULL in this view, reserved extension attributes with no populated source in the current definition.

Common Use Cases and Queries

Because the view is marked obsolete and unimplemented in the documented database, it should be treated primarily as a reference object; any query against it in a live instance would depend on the presence of the FIIBV_PROJ_CLS3_LCV base view. Where deployed, typical usage involves resolving class-3 project classifications for dimension joins and value-list population.

SELECT PROJ_CLS3_PK,
       NAME,
       PROJECT_CLASS3,
       PROJ_CATEG3_FK,
       INSTANCE,
       LAST_UPDATE_DATE
FROM   FII_PROJ_CLS3_LCV
WHERE  INSTANCE = :p_instance
ORDER  BY NAME;

A second common pattern joins the class-3 view to its parent category using the PROJ_CATEG3_FK key, enabling roll-up reporting across the project classification hierarchy for EDW extracts:

SELECT c.NAME AS CLASS3_NAME,
       c.PROJ_CATEG3_FK
FROM   FII_PROJ_CLS3_LCV c
WHERE  c.LAST_UPDATE_DATE >= :p_last_run_date;

Due to its obsolete status, implementations on 12.1.1 or 12.2.2 should validate object existence before relying on this view, and migrate to supported FII/EDW project dimension sources where available.