Results for “pa_projects_it_all”

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

Overview

PA_PROJECTS_IT_ALL is a Projects (PA) module table in Oracle E-Business Suite that stores project information consumed by the Oracle Project Analysis Collection Pack. Its documented description states that it holds "information about projects for Oracle Project Analysis Collection Pack," positioning it as a foundational project-definition entity within the Project Analysis (PA) schema rather than as a transactional or accounting-movement table. The table is owned by the PA schema and is marked VALID in the documented ETRM metadata for the 12.1.1 and 12.2.2 releases, with the 12.2.2 physical schema comprising 27 columns.

From a heuristic Data Vault modeling perspective (mined from the foreign-key structure), this object is classified as hub-leaning. It should be regarded as a candidate project hub: the PROJECT_ID column serves as the surrogate primary key, and the table anchors dependent satellite-style detail tables that reference it through PROJECT_ID. The naming suffix "_IT_ALL" follows the Oracle pattern for the Projects implementation tables, and the "_ALL" suffix signals that the table is org-striping aware through the ORG_ID column, so rows are partitioned by operating unit context.

Key Information Stored

The table's documented structure centers on project identity and classification. The most significant columns are:

• PROJECT_ID — the surrogate primary key, backed by unique index PA_PROJECTS_IT_ALL_U1. It is the join column consumed by all dependent tables.
• NAME — the project name (business-key candidate for user-facing identification).
• SEGMENT1 — the project number segment, a common business-key candidate for external reference.
• PROJECT_TYPE — classifies the project; it participates in a foreign key to PA_PRJ_TYPES_IT_ALL alongside ORG_ID.
• CARRYING_OUT_ORGANIZATION_ID — the performing organization, referencing PA_PRJ_ORGS_IT.
• ORG_ID — the operating unit identifier enabling multi-org stripe filtering.
• DESCRIPTION — free-text project description.
• STATUS_CODE — the lifecycle status of the project definition.
• USER_COL1 through USER_COL10 — ten user-defined attribute columns available for descriptive extensibility.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns tracking who created and last modified each record.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent-program tracking columns identifying the process that last touched the row.

The surrogate key (PROJECT_ID) should be distinguished from business identifiers such as NAME and SEGMENT1; the documented unique index covers only PROJECT_ID, so no alternate unique constraint on project number is recorded.

Common Use Cases and Queries

Typical usage involves reporting and integration queries that resolve project identity and classification. Common patterns include:

• Listing active projects for an operating unit: SELECT project_id, name, segment1, status_code FROM pa.pa_projects_it_all WHERE org_id = :org_id AND status_code = 'A';
• Joining projects to their carrying-out organization: SELECT p.project_id, p.name, o.name FROM pa.pa_projects_it_all p, pa.pa_prj_orgs_it o WHERE p.carrying_out_organization_id = o.organization_id;
• Resolving project type descriptions by joining to PA_PRJ_TYPES_IT_ALL on ORG_ID and PROJECT_TYPE.
• Feeding the Project Analysis Collection Pack with a denormalized project dimension built from NAME, SEGMENT1, DESCRIPTION, and the USER_COL1–USER_COL10 attributes.
• Auditing recent maintenance using LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, and PROGRAM_ID to trace which concurrent program modified project records.

Because the table is org-striped via ORG_ID, all reporting queries should filter by operating unit to avoid cross-org row leakage.

Related Objects

The documented foreign-key relationships identify the following significant related objects:

• PA_PRJ_TYPES_IT_ALL — referenced through ORG_ID and PROJECT_TYPE, providing project type definitions.
• PA_PRJ_ORGS_IT — referenced through CARRYING_OUT_ORGANIZATION_ID, supplying the performing organization.
• PA_PRJ_BGT_LINES_IT_ALL — references this table through PROJECT_ID, holding project budget lines.
• PA_PRJ_CLASSES_IT — references this table through PROJECT_ID, holding project class assignments.
• PA_TOP_TASKS_IT — references this table through PROJECT_ID, holding top-task structures.
• PA_PRJ_ACT_CMT_IT_ALL — references this table through PROJECT_ID, holding commitment amounts.

Together these dependents form the project hub-and-satellite cluster, with PA_PROJECTS_IT_ALL as the central project definition entity.