Search Results edw_proj_top_task_lstg

Overview

The EDW_PROJ_TOP_TASK_LSTG table is a staging object owned by the FII (Financial Intelligence) schema within Oracle E-Business Suite. Its documented description defines it as a "staging table for top task level," indicating that it serves as an intermediate landing area for project task data before that data is transformed, validated, and loaded into the enterprise data warehouse or another downstream reporting structure. Staging tables of this type are populated by extract, transformation, and load (ETL) processes and are typically transient in nature, with rows surviving only for the duration of a load cycle.

In the context of Oracle EBS 12.1.1 and 12.2.2, the FII module provides the analytical foundation for financial and project reporting, and this table supports the project costing and task-level detail that flows into those analytics. The metadata classifies the table heuristically as standalone within a Data Vault model. This modeling suggestion implies that, rather than functioning as a hub, link, or satellite with an integrated key structure, the object is treated as an independent staging artifact — useful for load-time processing but not intended to participate directly in a normalized Data Vault core.

Key Information Stored

The table carries 22 documented columns. The most operationally significant are:

• ROW_ID — a surrogate identifier for the staged row; the metadata shows a foreign-key relationship from EDW_PROJ_TOP_TASK_LSTG.ROW_ID to CS_SYSTEMS_ALL_B_TEMP, anchoring the staged record to the source-system instance.
• PROJECT_FK_KEY and PROJECT_FK — surrogate and business foreign keys identifying the parent project.
• TOP_TASK_PK and TOP_TASK — the primary-key and business identifiers for the top-level task being staged.
• TASK_NUMBER — the task's user-facing number.
• NAME — the descriptive name of the top task.
• TASK_START_DATE and TASK_END_DATE — the planned or actual task schedule boundaries.
• LABOR_COST_MULT — the labor cost multiplier applied to the task.
• SERVICE_TYPE_CODE, OPERATION_CODE, and INSTANCE — control and classification attributes describing the service and the source instance.
• REQUEST_ID, COLLECTION_STATUS, and ERROR_CODE — ETL control columns tracking the load request, the collection's processing state, and any failure indicator.
• DELETION_DATE — the effective removal date for the staged record.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — descriptive flexfield-style columns for client-specific extensions.

Of these, the metadata identifies ROW_ID as the surrogate primary key candidate, with PROJECT_FK, TOP_TASK_PK, and TASK_NUMBER serving as business-key candidates for the load.

Common Use Cases and Queries

Typical scenarios include monitoring load status, reconciling staged task counts against source projects, and diagnosing failed collections. A common pattern inspects error and status columns:

• SELECT REQUEST_ID, COLLECTION_STATUS, ERROR_CODE, COUNT(*) FROM FII.EDW_PROJ_TOP_TASK_LSTG GROUP BY REQUEST_ID, COLLECTION_STATUS, ERROR_CODE;
• Joining staged tasks to their projects on the surrogate key: SELECT t.TASK_NUMBER, t.NAME, t.TASK_START_DATE, t.TASK_END_DATE FROM FII.EDW_PROJ_TOP_TASK_LSTG t WHERE t.PROJECT_FK = :project_id;
• Identifying records pending deletion: SELECT * FROM FII.EDW_PROJ_TOP_TASK_LSTG WHERE DELETION_DATE IS NOT NULL AND DELETION_DATE <= SYSDATE;
• Reporting on labor cost multipliers by service type for downstream project-cost analytics.

Related Objects

• CS_SYSTEMS_ALL_B_TEMP — referenced via ROW_ID, linking the staged row to its source-system instance.
• EDW_PROJ_PROJECT_LSTG — the sibling project-level staging table, joined on PROJECT_FK / PROJECT_FK_KEY.
• EDW_PROJ_TASK_LSTG — the lower-level task staging counterpart, joined on task identifiers.
• PA_PROJECTS_ALL — the EBS project master supplying source project data.
• PA_TASKS — the source task definition table from Project Costing.

Because the table is classified as standalone, no downstream hubs or links depend on it within a Data Vault core; its consumers are the ETL and reporting layers of the FII module.