Results for “pa_task_history”

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

Overview

PA_TASK_HISTORY is a table in the Oracle E-Business Suite Projects (PA) module, owned by the PA schema. It stores service type and task organization history for project tasks, capturing changes over time to how a task is classified and which organization is responsible for carrying it out. In Oracle Projects, tasks form the lowest level of the project work breakdown structure, and the organization carrying out a task determines ownership, costing, and cross-charge behavior. When the service type or the carrying-out organization of a task is changed, PA_TASK_HISTORY preserves the prior values so that historical assignments remain auditable even after the task record itself has been updated.

From a data modeling perspective, the mined foreign key relationships indicate this table is classified as a standalone structure. This heuristic Data Vault classification is best read as a modeling suggestion: PA_TASK_HISTORY does not sit as a conventional hub, link, or satellite within a normalized dependency graph in the documented metadata, but functions as a history or audit record surrounding the task entity. Analysts building a Data Vault layer over Projects data should generally treat it as a satellite-like historical store of task attribute changes, dependent on the task and top task business keys, rather than as an independent hub.

Key Information Stored

The table contains 17 documented columns. The most significant are:

• TASK_HISTORY_ID — The surrogate primary key, defined by PA_TASK_HISTORY_PK. It also appears in the unique index PA_TASK_HISTORY_U1, making it the documented business-key candidate for uniquely identifying a history row.
• TASK_ID — The task whose service type or organization assignment is being tracked. This is the principal business key linking a history row to PA_TASKS.
• SERVICE_TYPE_CODE — The service type associated with the task at the time of the recorded change; drives project costing and revenue treatment.
• CARRYING_OUT_ORGANIZATION_ID — The organization responsible for performing the task at the time of the historical record. Changes to this value are a primary reason rows exist in this table.
• TOP_TASK_ID — Reference to the top-level task, documented as a foreign key to PA_TOP_TASKS_IT. It anchors the history record within the broader task hierarchy.
• PROJECT_ID — The project to which the task belongs, supporting project-level filtering and reporting.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard EBS who/when auditability.
• Concurrent program columns — REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE identify the concurrent request and program that created or last modified the row.
• ADW_INTERFACE_FLAG and ADW_NOTIFY_FLAG — Flags controlling interface and notification behavior for the Projects data warehouse / ADW integration.

Common Use Cases and Queries

Typical uses include auditing service type changes, reconstructing the organization responsible for a task at a point in time, and feeding historical assignments into reporting or the ADW.

A basic audit query retrieving the history for a specific task:

• SELECT th.task_history_id, th.task_id, th.service_type_code, th.carrying_out_organization_id, th.last_update_date, th.last_updated_by FROM pa.pa_task_history th WHERE th.task_id = :p_task_id ORDER BY th.last_update_date DESC;

To trace history across all tasks belonging to a project:

• SELECT th.project_id, th.task_id, th.service_type_code, th.carrying_out_organization_id, th.creation_date FROM pa.pa_task_history th WHERE th.project_id = :p_project_id ORDER BY th.task_id, th.creation_date;

To identify rows pending ADW notification or interface processing:

• SELECT th.task_history_id, th.task_id, th.adw_interface_flag, th.adw_notify_flag FROM pa.pa_task_history th WHERE th.adw_notify_flag = 'Y';

Because the table is primarily read for audit and reporting, queries should generally filter on TASK_ID or PROJECT_ID and rely on the TASK_HISTORY_ID unique index for direct key access.

Related Objects

• PA_TASKS — The parent task table; join on TASK_ID to relate historical assignments to current task definitions.
• PA_TOP_TASKS_IT — Referenced by the documented foreign key PA_TASK_HISTORY.TOP_TASK_ID → PA_TOP_TASKS_IT; provides the top-level task context.
• PA_PROJECTS — The project master; join on PROJECT_ID for project-level reporting.
• PA_SERVICE_TYPES — Supplies the meaning behind SERVICE_TYPE_CODE values.
• HR_ALL_ORGANIZATION_UNITS — Resolves CARRYING_OUT_ORGANIZATION_ID to an organization name.
• PA_PROJECT_STATUS_HISTORY — A comparable history table useful for combined project/task change analysis.
• FND_CONCURRENT_REQUESTS — Join on REQUEST_ID to identify the concurrent program run that created a history row.