Search Results prog_entry_enable_flag




Overview
Explore in AI Chat

Overview

PA_TASK_TYPES is a Projects (PA) module reference table that stores implementation-defined classifications of tasks. In Oracle EBS 12.1.1 and 12.2.2, a task type determines the behavior of a project task, including its default status, progress entry rules, weighting and percent-complete derivation methods, work quantity handling, and workflow integration. Because task types drive so much downstream validation and defaulting, this table functions as a central configuration repository consulted repeatedly by Oracle Projects forms, APIs, and concurrent programs.

The table resides in the PA schema and is owned by the Projects application. The primary key is defined by PA_TASK_TYPES_PK on the TASK_TYPE_ID column. Two unique indexes serve as business-key candidates: PA_TASK_TYPES_U1 on (TASK_TYPE_ID, ZD_EDITION_NAME) and PA_TASK_TYPES_U2 on (TASK_TYPE, ZD_EDITION_NAME), reflecting the Editioning feature introduced in 12.2. Under a heuristic Data Vault classification based on the foreign key structure, PA_TASK_TYPES is satellite-leaning, meaning it is best modeled as a descriptive satellite attached to a task-type hub, with its foreign keys to status and layout objects treated as reference lookups rather than as link relationships.

Key Information Stored

Each row in PA_TASK_TYPES describes a single task type and its associated processing rules. Forty-seven columns are documented in the 12.2.2 physical schema. The most significant include:

Common Use Cases and Queries

Typical usage includes validating that a task type is active, retrieving default status and progress behavior for a new task, and producing configuration reports for implementation reviews.

  • List active task types: SELECT task_type_id, task_type, task_type_class_code FROM pa_task_types WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
  • Join PA_PROJ_ELEMENTS to obtain the descriptive task type name: SELECT ppe.proj_element_id, ptt.task_type FROM pa_proj_elements ppe, pa_task_types ptt WHERE ppe.type_id = ptt.task_type_id;
  • Report status defaulting: join INITIAL_STATUS_CODE and INITIAL_PROGRESS_STATUS_CODE to PA_PROJECT_STATUSES to review each task type's defaults.
  • Identify types with workflow enabled using WF_ITEM_TYPE and WF_PROCESS.

These queries are commonly used in setup audits, migration validation, and custom reporting on project and task configuration.

Related Objects

  • PA_PROJ_ELEMENTS — references PA_TASK_TYPES via TYPE_ID, linking task type configuration to project elements.
  • PA_PROJECT_STATUSES — supplies the INITIAL_STATUS_CODE and INITIAL_PROGRESS_STATUS_CODE lookup values.
  • PA_PAGE_LAYOUTS — supplies TASK_PROGRESS_ENTRY_PAGE_ID for progress entry screens.
  • PA_TASKS — the primary consumer, applying task type rules to individual project tasks.
  • PA_PROJECTS — project structures that inherit task type behavior through their associated tasks.
  • Oracle Projects APIs — task-related PL/SQL APIs and concurrent programs that validate and default from PA_TASK_TYPES.
  • Oracle Workflow — consumes WF_ITEM_TYPE and WF_PROCESS for task scheduling and notifications.