Results for “pa_project_assignments”

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

Overview

PA_PROJECT_ASSIGNMENTS is the core Projects (PA) table that stores the details of every assignment defined for a project in Oracle E-Business Suite 12.1.1 and 12.2.2. An assignment represents the intersection of a project and a resource — typically a person or an organization unit — together with the role, effort, dates, and financial terms under which that resource is engaged. It is the object that project managers create when staffing a project, when building a project team from a template, or when a resource is nominated and later confirmed against a staffing requirement.

The table belongs to the PA schema and is owned by the Projects module. Its documented structure contains 92 columns, which reflects the breadth of information the assignment record carries: identification, scheduling, financial, forecasting, and staffing attributes are all held on this single row. A heuristic Data Vault classification mined from the foreign key structure places the table as satellite-leaning, meaning it behaves primarily as a descriptive satellite attached to the project and resource hubs rather than as a pure hub or link. This classification is a modeling suggestion only; in native EBS terms the table is a transactional master-detail entity within the PA schema.

Key Information Stored

The surrogate primary key is ASSIGNMENT_ID, enforced by the constraint PA_PROJECT_ASSIGNMENTS_PK. A unique index, PA_PROJECT_ASSIGNMENTS_U1, also exists on ASSIGNMENT_ID. ASSIGNMENT_NUMBER and ASSIGNMENT_NAME act as the human-readable business identifiers used in the Projects forms and reports.

The most significant columns include:

• ASSIGNMENT_ID — surrogate primary key; the value carried by nearly every downstream PA table.
• PROJECT_ID — foreign key to PA_PROJECTS_ALL, identifying the project to which the assignment belongs.
• RESOURCE_ID — foreign key to PA_RESOURCES, identifying the assigned resource.
• PROJECT_ROLE_ID — foreign key to PA_PROJECT_ROLE_TYPES, defining the role the resource fills.
• PROJECT_PARTY_ID — foreign key to PA_PROJECT_PARTIES, linking the assignment to the project party record.
• STATUS_CODE — foreign key to PA_PROJECT_STATUSES, indicating the current assignment lifecycle status.
• ASSIGNMENT_TYPE and ASSIGNMENT_EFFORT — describe the nature of the assignment and the planned effort.
• START_DATE and END_DATE — the effective period of the assignment.
• WORK_TYPE_ID, EXPENDITURE_TYPE, and EXPENDITURE_ORGANIZATION_ID — drive expenditure classification and owning organization.
• REVENUE_BILL_RATE, REVENUE_CURRENCY_CODE, EXPENSE_LIMIT, and EXPENSE_LIMIT_CURRENCY_CODE — commercial terms attached to the assignment.
• SOURCE_ASSIGNMENT_ID — self-referencing foreign key to PA_PROJECT_ASSIGNMENTS, used where an assignment is derived from another.
• ASSIGNMENT_TEMPLATE_ID — foreign key to PA_TEAM_TEMPLATES, recording the team template that generated the assignment.
• CALENDAR_ID, LOCATION_ID, and FCST_JOB_ID — scheduling and forecasting attributes.

Common Use Cases and Queries

The table is queried for project team rosters, resource utilization reporting, bill rate analysis, and staffing pipeline review. A typical roster query joins to PA_PROJECTS_ALL and PA_RESOURCES:

• SELECT a.assignment_number, a.assignment_name, r.name, a.start_date, a.end_date FROM pa.pa_project_assignments a, pa.pa_projects_all p, pa.pa_resources r WHERE a.project_id = p.project_id AND a.resource_id = r.resource_id AND p.segment1 = :project_number;
• Staffing and candidate tracking queries join PA_PROJECT_ASSIGNMENTS to PA_CANDIDATES on ASSIGNMENT_ID to list active candidates per assignment.
• Financial reporting joins PA_EXPENDITURE_ITEMS_ALL on ASSIGNMENT_ID to attribute actual costs to an assignment, and PA_SCHEDULES to obtain the assignment schedule rows.
• Lifecycle and audit queries join PA_PROJECT_ASSIGNMENTS_HISTORY on ASSIGNMENT_ID to reconstruct historical changes to assignment dates, effort, or status.

Related Objects

PA_PROJECT_ASSIGNMENTS is heavily referenced across the PA schema. The most significant related objects are:

• PA_PROJECTS_ALL — parent project, joined on PROJECT_ID.
• PA_RESOURCES — the assigned resource, joined on RESOURCE_ID.
• PA_PROJECT_ROLE_TYPES — role definition, joined on PROJECT_ROLE_ID.
• PA_PROJECT_PARTIES — project party record, joined on PROJECT_PARTY_ID.
• PA_PROJECT_STATUSES — assignment status, joined on STATUS_CODE.
• PA_CANDIDATES — candidate nominations per assignment, joined on ASSIGNMENT_ID.
• PA_EXPENDITURE_ITEMS_ALL — expenditure transactions attributed to the assignment, joined on ASSIGNMENT_ID.
• PA_SCHEDULES and PA_SCHEDULES_HISTORY — assignment schedule rows, joined on ASSIGNMENT_ID.
• PA_ASSIGNMENTS_HISTORY — historical audit of assignment changes, joined on ASSIGNMENT_ID.
• PA_TRANSACTION_INTERFACE_ALL — cost interface rows that carry ASSIGNMENT_ID into costing.