Search Results na_edw




Overview
Explore in AI Chat

Overview

FII_PA_COST_F_FCV is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Financial Intelligence (FII) product family. Its documented purpose is to serve as the EDW Project Cost fact source view, meaning it exposes project cost transactions in a flattened, dimension-keyed form suitable for extraction, transformation, and loading into an Enterprise Data Warehouse. The view belongs to the fact-source layer of the FII/EDW integration model, where transactional detail from Oracle Projects is denormalized into a star-schema-friendly shape. It is valid in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it holds no data of its own; it projects and derives columns from underlying Projects cost tables at query time, which keeps the EDW extract aligned with the operational source without duplicating storage.

Underlying Base Objects

The ETRM metadata for this object does not enumerate referenced base objects, so the definitive dependency list must be confirmed by querying ALL_DEPENDENCIES or by inspecting the view DDL in the target instance. Functionally, the view is built to source project expenditure and cost records. The projection list includes COST_PK, a surrogate or primary identifier for the cost row, and a SEQ_ID, which is characteristic of FII fact-source views that assign a sequence key for warehouse loading. Also present are INSTANCE_FK and numerous foreign-key columns, confirming the view is defined over one or more Projects cost/expenditure tables plus dimension resolution logic. The GL_ACCT1_FK through GL_ACCT9_FK columns are derived, not stored, from a single concatenated GL_SEG value, indicating the base object carries an accounting flexfield string that the view parses into individual segment keys.

Key Columns

The view exposes both measures and dimension keys:

Common Use Cases and Queries

The primary use case is feeding the EDW Project Cost fact table. Analysts also query it directly for cost reporting and reconciliation. Typical patterns include aggregating burdened cost by project and accounting period, or filtering on the billable flag.

  • Cost by project: SELECT PROJECT_FK, SUM(BURDENED_COST_T) FROM APPS.FII_PA_COST_F_FCV GROUP BY PROJECT_FK;
  • Billable cost within a period: SELECT * FROM APPS.FII_PA_COST_F_FCV WHERE BILLABLE_FLAG = 'Y';
  • Accounting distribution: SELECT GL_ACCT1_FK, GL_ACCT2_FK, SUM(RAW_COST_T) FROM APPS.FII_PA_COST_F_FCV GROUP BY GL_ACCT1_FK, GL_ACCT2_FK;

Because the view resolves keys at runtime, performance depends on the base tables and indexes; large extracts should be restricted by date or project key.