Results for “pa_project_statuses”

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

Overview

PA_PROJECT_STATUSES is the Projects (PA) module reference table that defines the valid project status codes available in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row describes a status that a project, task, or control item can occupy during its lifecycle, together with the workflow behavior, activation dates, and presentation attributes associated with that status. The table is seeded with predefined Oracle statuses and can be extended with user-defined statuses where the module permits.

Within the PA schema, the table functions as a control and validation source: foreign key constraints from project entities and control-item entities guarantee that only statuses defined here can be assigned. From a Data Vault modeling perspective, the mined FK structure suggests classifying PA_PROJECT_STATUSES as a hub — a stable set of business keys (status codes) around which dependent descriptive attributes and relationships cluster. The primary key is PA_PROJECT_STATUSES_PK, defined on PROJECT_STATUS_CODE.

Key Information Stored

The table comprises 40 documented columns. The most consequential are:

• PROJECT_STATUS_CODE — the surrogate primary key and the value referenced by every dependent foreign key.
• PROJECT_STATUS_NAME — the user-facing status name displayed in forms, reports, and inquiry screens.
• STATUS_TYPE — category used to distinguish statuses applicable to projects versus tasks and to group statuses by functional role.
• PROJECT_SYSTEM_STATUS_CODE — identifies the Oracle-internal system status that corresponds to the user-defined status.
• DESCRIPTION — free-form explanation of the status for administrators and end users.
• START_DATE_ACTIVE / END_DATE_ACTIVE — date-range controls that determine when the status may be selected.
• PREDEFINED_FLAG — indicates Oracle-seeded statuses that cannot be deleted.
• STARTING_STATUS_FLAG — marks statuses permitted as the initial state of a project or task.
• ENABLE_WF_FLAG, WORKFLOW_ITEM_TYPE, WORKFLOW_PROCESS — control whether entering the status launches an Oracle Workflow process.
• WF_SUCCESS_STATUS_CODE / WF_FAILURE_STATUS_CODE — the statuses applied when the associated workflow completes successfully or fails.
• NEXT_ALLOWABLE_STATUS_FLAG — indicates whether permissible next statuses are governed through the PA_NEXT_ALLOW_STATUSES mapping.
• STATUS_ICON_IND, STATUS_ICON_ACTIVE_IND, PROJECT_STATUS_WEIGHT — presentation and sequencing attributes used in the Progress workbench and rollup logic.
• ZD_EDITION_NAME — the editioning column introduced for online patching in Release 12.2, present in the unique indexes PA_PROJECT_STATUSES_U2 (PROJECT_STATUS_CODE, ZD_EDITION_NAME) and PA_PROJECT_STATUSES_U3 (STATUS_TYPE, PROJECT_STATUS_NAME, ZD_EDITION_NAME).
• ATTRIBUTE1 through ATTRIBUTE15 and the standard WHO columns — the DFF flexfield segment and audit trail columns.

Common Use Cases and Queries

The table is routinely queried to resolve codes into meaningful names in operational and reporting SQL, to validate configuration of workflow-enabled statuses, and to audit the status-transition rules defined for projects and tasks.

Resolving status descriptions:

• SELECT p.project_number, p.name, s.project_status_name FROM pa_projects_all p, pa_project_statuses s WHERE p.project_status_code = s.project_status_code;
• SELECT project_status_code, project_status_name, status_type, predefined_flag FROM pa_project_statuses WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
• SELECT a.status_code, b.next_allowable_status_code FROM pa_next_allow_statuses a, pa_next_allow_statuses b WHERE a.status_code = b.next_allowable_status_code;

Reporting frequently joins PA_PROJECT_STATUSES to PA_PROJECTS_ALL for status dashboards, to PA_CONTROL_ITEMS and PA_PERCENT_COMPLETES for progress tracking, and to PA_PURGE_PROJECTS or PA_PURGE_BATCHES_ALL when filtering purge candidates by next project status.

Related Objects

The most significant dependent objects, based on the documented foreign key relationships, include:

• PA_PROJECTS_ALL — joins on PROJECT_STATUS_CODE; the primary consumer of status assignments.
• PA_PROJ_ELEMENTS — joins on PHASE_CODE to classify project elements and phases.
• PA_PROJECT_STATUS_CONTROLS — joins on PROJECT_STATUS_CODE and governs which functions are enabled while a project is in a given status.
• PA_NEXT_ALLOW_STATUSES — references both STATUS_CODE and NEXT_ALLOWABLE_STATUS_CODE, encoding the valid status transition graph.
• PA_CONTROL_ITEMS — joins on STATUS_CODE and PROGRESS_STATUS_CODE for control-item tracking.
• PA_PERCENT_COMPLETES and PA_PROGRESS_ROLLUP — join on STATUS_CODE or PROGRESS_STATUS_CODE for progress computation.
• PA_TASK_TYPES — joins on INITIAL_STATUS_CODE and INITIAL_PROGRESS_STATUS_CODE to set default task statuses.
• PA_ROLE_STATUS_MENU_MAP — joins on STATUS_CODE to control menu availability by role and status.
• PA_CI_ACTIONS, PA_CI_IMPACTS, and PA_SCHEDULES_HISTORY — join on STATUS_CODE for change-management and scheduling history.
• PA_PURGE_PROJECTS and PA_PURGE_BATCHES_ALL — join on LAST_PROJECT_STATUS_CODE, NEXT_P_PROJECT_STATUS_CODE, and NEXT_PP_PROJECT_STATUS_CODE for purge eligibility.