Results for “edw_proj_task_lstg”

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

Overview

EDW_PROJ_TASK_LSTG is a Financial Intelligence (FII) staging table within the Oracle E-Business Suite that holds task-level project records prior to transformation into the enterprise data warehouse. The object is classified under product/module FII – Financial Intelligence and is documented as Obsolete in the ETRM repository. Its stated purpose is to serve as a landing area for project task data extracted from the operational EBS schema, where it can be validated, cleansed, and enriched before being loaded into downstream analytical structures.

Because the table functions purely as a staging construct, it does not participate in transactional processing. Records are written by extraction programs, amended by transformation logic, and consumed by warehouse load routines. The ETRM metadata explicitly notes "Not implemented in this database," and the object carries the Oracle Proprietary, Confidential Information designation.

From a heuristic Data Vault modeling perspective, the mined FK structure marks this object as standalone. A standalone classification suggests the table is best treated as an independent staging or reference entity rather than decomposed into hub, link, or satellite constructs. The single documented foreign key — ROW_ID referencing CS_SYSTEMS_ALL_B_TEMP — indicates a loosely coupled relationship to a temporary systems table rather than a durable model dependency.

Key Information Stored

The documented physical schema for ETRM 12.1.1 assigns ownership to the FII schema and defines 26 columns. The most consequential columns are:

• ROW_ID – The documented foreign key column, referencing CS_SYSTEMS_ALL_B_TEMP.ROW_ID. It anchors the staging row to its source system context.
• TASK_PK – The task-level primary key value carried from the source system; the principal business-key candidate for identifying a project task.
• TASK_NUMBER – The user-facing task identifier, typically the number displayed in project forms and reports.
• TASK and NAME – The short task code and descriptive task name, used for reporting labels.
• TOP_TASK_FK and TOP_TASK_FK_KEY – References to the top-level task in the project hierarchy, supporting rollup and drill-down analysis.
• DENORM_TASK_ORG_FK – A denormalized organization key associated with the task, used to avoid an extra join during warehouse loading.
• TASK_START_DATE and TASK_END_DATE – Planned or actual task duration boundaries.
• LABOR_COST_MULT – The labor cost multiplier applicable to the task, relevant for cost-basis derivation.
• SERVICE_TYPE_CODE and OPERATION_CODE – Classification attributes describing the task's service and operation category.
• COLLECTION_STATUS and ERROR_CODE – Staging control columns indicating load outcome and failure diagnostics.
• REQUEST_ID and INSTANCE – Concurrency and environment identifiers for traceability.
• EDW_RECORD_TYPE – A warehouse-specific discriminator used during transformation.

Audit columns CREATION_DATE, LAST_UPDATE_DATE, and DELETION_DATE track lifecycle timestamps. USER_ATTRIBUTE1 through USER_ATTRIBUTE5 provide the standard EBS descriptive flexfield extension slots.

Common Use Cases and Queries

Typical usage centers on extract-transform-load monitoring and reconciliation. A common pattern checks staging completeness for a given concurrent request:

SELECT TASK_NUMBER, NAME, COLLECTION_STATUS, ERROR_CODE FROM EDW_PROJ_TASK_LSTG WHERE REQUEST_ID = :request_id;

Error reconciliation queries isolate failed rows by joining to the source system context through ROW_ID:

SELECT l.TASK_PK, l.TASK_NUMBER, l.ERROR_CODE FROM EDW_PROJ_TASK_LSTG l, CS_SYSTEMS_ALL_B_TEMP s WHERE l.ROW_ID = s.ROW_ID AND l.COLLECTION_STATUS = 'ERROR';

Hierarchy reconstruction queries use TOP_TASK_FK to assemble parent-child task relationships for cost rollups. Warehouse load programs also select LABOR_COST_MULT and TASK_START_DATE/TASK_END_DATE to derive time-phased labor cost facts.

Related Objects

• CS_SYSTEMS_ALL_B_TEMP – Referenced via EDW_PROJ_TASK_LSTG.ROW_ID. The only documented FK relationship.
• EDW_PROJ_TASK_F – The target warehouse fact table typically loaded from this staging area.
• PA_TASKS – The operational Projects task table supplying source records.
• PA_PROJECTS_ALL – Provides project context for the task-level extraction.
• FII staging siblings – Parallel LSTG tables for project, expenditure, and resource levels loaded in the same batch cycle.
• FND_CONCURRENT_REQUESTS – Supplies the REQUEST_ID used for batch traceability.

Because the object is marked Obsolete and "Not implemented in this database," it should be treated as historical reference only; equivalent functionality in supported releases resides in successor FII or OBIA staging objects.