Search Results current_original_flag




Overview

FII_PA_PABU_BUDGET_LCV is an Oracle E-Business Suite view owned by the APPS schema and classified under the FII (Financial Intelligence) product family. It functions as the budget-level source view for the Project Budget dimension within the Enterprise Data Warehouse (EDW). In Oracle EBS 12.1.1 and 12.2.2, Financial Intelligence supplies the extract and staging layer that feeds the Oracle Business Intelligence Applications (OBIA) and related analytical repositories. Views such as this one normalize project budgeting data into a dimension-friendly shape so that downstream ETL processes can populate the Project Budget dimension without directly touching transactional PA tables.

The view is registered as VALID and operates as a thin pass-through wrapper, exposing a curated column list that includes the BUDGET_TYPE attribute referenced in the user's search. This design isolates the EDW from schema changes in the underlying project accounting objects and enforces a stable contract for reporting consumers.

Underlying Base Objects

The documented view definition is a direct selection over a single underlying object: FIIBV_PA_PABU_BUDGET_LCV. The FIIBV prefix indicates a Financial Intelligence base view, while the _LCV suffix denotes the "level source view" naming convention used within the FII layer. No further base tables are documented as referenced objects within the ETRM metadata.

The view text reveals the column projection:

Because the definition is a pure SELECT with no joins or filters, the wrapper adds only the column aliasing and standardization required by the EDW load process.

Key Columns

The columns exposed by FII_PA_PABU_BUDGET_LCV map naturally to the Project Budget dimension requirements:

  • BUDGET_PK — Primary key surrogate for the budget record; used as the dimension's unique identifier during ETL loads.
  • NAME — Descriptive name of the budget.
  • BUDGET_TYPE — Classifies the budget, distinguishing approved cost budgets, revenue budgets, or other budget categories derived from the PA budgeting model. This column directly answers the "budget_type" search and is a primary filter attribute in budget reporting.
  • VERSION_NAME — Identifies the specific version of the budget, supporting versioned comparisons.
  • PROJECT_NAME — The project associated with the budget, providing the hierarchical link to the Project dimension.
  • CURRENT_FLAG, ORIGINAL_FLAG, CURRENT_ORIGINAL_FLAG — Indicator flags that allow the EDW to distinguish the current baseline from the original baseline or other designations.
  • INSTANCE — Identifies the source EBS instance, relevant in multi-instance consolidations.
  • LAST_UPDATE_DATE — Supports incremental extraction and change detection.

Common Use Cases and Queries

This view is typically consumed by OBIA/EDW extract jobs, but it is also useful for diagnostic queries during implementation. A representative query filtered on budget type would read:

SELECT BUDGET_PK, NAME, BUDGET_TYPE, VERSION_NAME, PROJECT_NAME FROM APPS.FII_PA_PABU_BUDGET_LCV WHERE BUDGET_TYPE = 'APPROVED COST BUDGET';

To confirm current baselines per project:

SELECT PROJECT_NAME, VERSION_NAME, CURRENT_FLAG FROM APPS.FII_PA_PABU_BUDGET_LCV WHERE CURRENT_FLAG = 'Y';

Because the view carries no WHERE clause of its own, query performance depends entirely on the tuning of FIIBV_PA_PABU_BUDGET_LCV and its base project accounting objects. Reports should therefore filter on indexed attributes such as BUDGET_PK or PROJECT_NAME when querying large budget sets.