Results for “prj_typ_pk”

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

Overview

FII_PROJ_PRJ_TYP_LCV is a Financial Intelligence (FII) view shipped with Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its name follows the standard FII convention: the _LCV suffix denotes a "list of values" (LOV) view, that is, a simplified projection whose purpose is to expose a clean, denormalized result set for use as a query source behind an LOV or a parameter list in Oracle Financial Intelligence reporting. The object presents project type information drawn from the FII staging and reporting layer so that report consumers, Discoverer worksheets, and concurrent program parameters can select a project type by primary key without joining the underlying transactional tables directly.

The ETRM metadata records this view under the product FII - Financial Intelligence, and explicitly marks that product as Obsolete. This classification is significant: FII was superseded by later Oracle financial reporting and analytics products, and the FII_PROJ_PRJ_TYP_LCV view should be treated as a legacy artifact retained for backward compatibility rather than an object intended for new development. In the documented environment the view is flagged "Not implemented in this database," indicating that in the source database used to generate the ETRM entry the view either was not deployed or was dropped. Implementations upgrading from 12.1.1 to 12.2.2 should therefore verify existence before referencing it.

Underlying Base Objects

The documented view text is a simple projection with no joins and no filters:

SELECT PRJ_TYP_PK, NAME, PROJECT_TYPE, ALL_FK, INSTANCE,
       LAST_UPDATE_DATE, NULL, NULL, NULL, NULL, NULL
FROM FIIBV_PROJ_PRJ_TYP_LCV

The single referenced base object is the FII Business View style object FIIBV_PROJ_PRJ_TYP_LCV. The FIIBV prefix identifies an FII business view, the intermediate abstraction layer that FII generates over its staging tables. The ETRM metadata records no further base tables, so no documented path exists from this view to the original Oracle Projects tables (for example, PA_PROJECT_TYPES); the dependency chain terminates at the business view layer. The five trailing NULL literals preserve a fixed column signature that the LOV framework expects, where the five USER_ATTRIBUTE descriptor columns are exposed in the view definition but have no populated value in this legacy form.

Ownership is not documented in the ETRM extract; in practice FII views of this class are owned by the applications schema (APPS) and granted to reporting responsibilities through the standard FII synonym and grant model.

Key Columns

• PRJ_TYP_PK — Surrogate primary key of the project type record; the value returned to the calling form or report when a user selects an LOV entry.
• NAME — Display name of the project type, used as the LOV description column shown to the user.
• PROJECT_TYPE — The functional project type classification value, distinguishing the category of project (for example, contract, indirect, or capital) within the FII reporting model.
• ALL_FK — Foreign key column linking the record into the FII reporting hierarchy; supports filtered LOV behavior in FII dashboards.
• INSTANCE — Identifies the source instance or FII reporting instance from which the row originates, enabling multi-instance and multi-source consolidation scenarios.
• LAST_UPDATE_DATE — Standard EBS audit column indicating the most recent modification timestamp of the source record; used for incremental refresh logic and stale-data detection.
• USER_ATTRIBUTE1 – USER_ATTRIBUTE5 — Descriptor columns exposed by the view signature but populated with NULL in the documented definition, an artifact of the legacy LOV template.

Common Use Cases and Queries

The principal use case is populating a project type LOV in an FII report or concurrent program parameter. A typical validation query confirms that the view is deployed and returns expected rows before a report is released:

SELECT PRJ_TYP_PK, NAME, PROJECT_TYPE
FROM   FII_PROJ_PRJ_TYP_LCV
ORDER BY NAME;

Because the view carries INSTANCE and LAST_UPDATE_DATE, it also supports refresh-oriented checks in consolidated FII environments:

SELECT INSTANCE, MAX(LAST_UPDATE_DATE) LAST_REFRESH
FROM   FII_PROJ_PRJ_TYP_LCV
GROUP BY INSTANCE;

Finally, where a legacy report references the view but the object is absent, DBAs should query ALL_VIEWS and ALL_OBJECTS to confirm the deployment state and reconcile against the FII business view FIIBV_PROJ_PRJ_TYP_LCV. Given the Obsolete product classification, the recommended long-term action is migration of any dependent report to a supported Oracle Projects or financial reporting source rather than restoration of the FII object.