Search Results edw_proj_project_lstg

Overview

FII.EDW_PROJ_PROJECT_LSTG is a staging table within the Financial Intelligence (FII) product family of Oracle E-Business Suite, documented as VALID in the ETRM repository and present in both 12.1.1 and 12.2.2 environments. Its stated purpose is to hold project-level data during extract, transform, and load processing into the Enterprise Data Warehouse (EDW). As a staging object, it serves as a transient landing zone where project master attributes are collected, validated, and prepared before they are promoted into the dimensional or historical structures used for reporting and analytics.

The table is owned by the FII schema and carries 35 documented columns. Because the ETRM metadata records no primary key constraint or unique index on the object, the heuristic Data Vault classification derived from the foreign key structure is standalone. In Data Vault modeling terms, this suggests the object functions less as a conformed hub or link and more as a raw or lightly transformed staging artifact feeding downstream loads, rather than as a governed integration point itself.

Key Information Stored

The most significant columns fall into three functional groupings: project identity, classification, and load control.

• PROJECT_PK and PROJECT_NUMBER — the primary surrogate identifier and the business-friendly project number; together these form the natural candidate business key for matching staging rows to source project records.
• PROJECT and NAME — the descriptive project name and internal project reference used in downstream reporting.
• PROJECT_MANAGER and PROJECT_STATUS_CODE — the assigned manager and lifecycle status, commonly filtered in project performance reports.
• PROJ_CLS1_FK through PROJ_CLS7_FK — the seven project classification flexfield foreign keys used for segment-level rollups.
• PRJ_TYP_FK — the project type reference.
• REQUEST_ID, COLLECTION_STATUS, INSTANCE, OPERATION_CODE, ERROR_CODE, and DELETION_DATE — load-control and error-tracking columns that govern the ETL lifecycle.
• ROW_ID and USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — the source row identifier and five extensibility attributes for customer-specific enrichment.

Common Use Cases and Queries

Typical usage centers on monitoring and reconciling EDW project loads. Analysts frequently check collection status and isolate failed rows before retry:

• Identify load failures: SELECT PROJECT_NUMBER, ERROR_CODE, COLLECTION_STATUS FROM FII.EDW_PROJ_PROJECT_LSTG WHERE COLLECTION_STATUS <> 'COMPLETE';
• Reconcile a specific batch: SELECT COUNT(*) FROM FII.EDW_PROJ_PROJECT_LSTG WHERE REQUEST_ID = :req_id;
• Audit project classification distribution using PROJ_CLS1_FK through PROJ_CLS7_FK for dimension validation before the warehouse load completes.
• Purge processed rows, applying DELETION_DATE and REQUEST_ID predicates to retain only the current cycle's staging set.

Related Objects

The only foreign key documented in the ETRM metadata links ROW_ID to CS_SYSTEMS_ALL_B_TEMP, tying staging rows back to the source collection. Downstream, the staged project keys and classification foreign keys resolve against the FII project dimensions and the standard EBS project tables (PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and the project classification flexfield views). Load orchestration is driven by the FII ETL request framework populating REQUEST_ID and COLLECTION_STATUS.