Search Results PA_PROJECTS_ALL

Overview

The PA_PROJECTS_ALL table is the fundamental master data table for the Oracle Projects module within Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It serves as the central repository for the highest-level unit of work, the project, which is the primary entity for planning, tracking, costing, billing, and revenue recognition. As an "ALL" table, it is multi-organization enabled, storing data partitioned by the operating unit (ORG_ID). This design is critical for installations with multiple business units, ensuring data isolation and security. The table's extensive foreign key relationships underscore its role as the nexus for integrating project definitions with other core EBS functionalities, including Human Resources, General Ledger, and Projects-specific setups.

Key Information Stored

The table's primary key is PROJECT_ID, a unique system-generated identifier for each project record. Beyond this, the table stores a comprehensive set of attributes that define a project's operational and financial characteristics. Key columns, as indicated by the foreign key relationships, include: PROJECT_TYPE, linking to PA_PROJECT_TYPES_ALL; CARRYING_OUT_ORGANIZATION_ID, linking to HR_ALL_ORGANIZATION_UNITS to define the executing department; and PROJECT_STATUS_CODE, linking to PA_PROJECT_STATUSES. Critical financial and control columns include COST_IND_RATE_SCH_ID, REV_IND_RATE_SCH_ID, and INV_IND_RATE_SCH_ID (and their override counterparts) for linking to indirect cost schedules (PA_IND_RATE_SCHEDULES_ALL_BG). Other significant fields are ROLE_LIST_ID for project team roles, WORK_TYPE_ID, LOCATION_ID, BILLING_CYCLE_ID, and job group IDs for billing and cost accounting (BILL_JOB_GROUP_ID, COST_JOB_GROUP_ID). The ORG_ID column is essential for multi-org data partitioning.

Common Use Cases and Queries

This table is central to virtually all project reporting, data extracts, and integration points. Common use cases include generating project master lists, building data warehouses for project analytics, and serving as the starting point for detailed transaction inquiries. A foundational query retrieves active project details for a specific operating unit, often joined to its related descriptive flexfields (DFF) and reference tables for meaningful reporting.

Sample Query Pattern:

• SELECT proj.PROJECT_ID, proj.SEGMENT1 AS Project_Number, proj.NAME, proj.DESCRIPTION, proj.PROJECT_STATUS_CODE, org.NAME AS Carrying_Out_Org FROM PA.PA_PROJECTS_ALL proj, HR.HR_ALL_ORGANIZATION_UNITS org WHERE proj.CARRYING_OUT_ORGANIZATION_ID = org.ORGANIZATION_ID AND proj.ORG_ID = 123 AND proj.PROJECT_STATUS_CODE = 'APPROVED';

Technical consultants frequently query this table to validate project setup, troubleshoot issues with rate schedules or organization assignments, and create custom integrations that require project master data.

Related Objects

PA_PROJECTS_ALL has a vast network of dependencies. It is the parent table for numerous key transactional and setup tables, including PA_TASKS, PA_EXPENDITURES_ALL, and PA_DRAFT_INVOICES_ALL. The provided metadata highlights critical foreign key relationships to reference tables: PA_PROJECT_TYPES_ALL, PA_PROJECT_STATUSES, HR_ALL_ORGANIZATION_UNITS, PA_IND_RATE_SCHEDULES_ALL_BG, PA_CC_TP_SCHEDULES_BG, PA_BILLING_CYCLES, PA_WORK_TYPES_B, PA_LOCATIONS, PA_ROLE_LISTS, and PER_JOB_GROUPS. For application development, the primary API for creating and maintaining records in this table is the PA_PROJECT_PUB package. The PA_PROJECTS view provides a public synonym and is often the preferred object for read-only access within custom code.