Results for “pm_project_reference”

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

Overview

PA_PM_REFERENCE_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, residing in the Projects (PA) product family. Its purpose is to expose the mapping between Oracle Projects identifiers and the reference identifiers assigned by an external project management (PM) system. The view joins project-level and task-level records so that third-party scheduling or project management tools — such as Primavera, Microsoft Project, or a customer-built PM interface — can be reconciled against the native Oracle Projects entities they represent. Because it is a view and not a table, it stores no data of its own; it presents a denormalized, read-only projection of the PA_PROJECTS and PA_TASKS tables. In Oracle EBS 12.1.1 and 12.2.2 it is used primarily for reporting, integration extracts, and troubleshooting of the PM reference columns maintained on projects and tasks.

Underlying Base Objects

The view is defined over two base objects, both referenced through APPS synonyms: PA_PROJECTS and PA_TASKS. The defining query joins them on PROJECT_ID:

FROM PA_TASKS T, PA_PROJECTS P
WHERE P.PROJECT_ID = T.PROJECT_ID

This is an inner join, so a row is returned only for tasks that belong to a valid project. The project columns are selected from the PA_PROJECTS alias P and the task columns from the PA_TASKS alias T. Consequently, the grain of the view is one row per project-task combination; projects with multiple tasks produce multiple rows, each repeating the parent project attributes. The view is documented as VALID, and the base tables are the authoritative source for the external reference values (PM_PROJECT_REFERENCE and PM_TASK_REFERENCE) that the external PM system writes back into Oracle Projects.

Key Columns

• ORG_ID — Operating unit identifier from the project, used for multi-org security and filtering.
• PROJECT_ID — Primary key of the project; the join key to PA_TASKS.
• PM_PROJECT_REFERENCE / PM_PRODUCT_CODE — The external PM system's project identifier and the product code identifying that system.
• DESCRIPTION / PROJECT_STATUS_CODE — Project description and status.
• PROJECT_START_DATE / PROJECT_COMPLETION_DATE — Project-level start and completion dates. Note that the user search term project_start_date maps to this column: the view text selects P.START_DATE and aliases it as PROJECT_START_DATE.
• TASK_ID, PARENT_TASK_ID, TOP_TASK_ID, TASK_NUMBER — Task hierarchy and identifiers.
• PM_TASK_REFERENCE — The external PM system's task identifier.
• TASK_START_DATE / TASK_COMPLETION_DATE — Task-level scheduled dates.
• SERVICE_TYPE_CODE, CHARGEABLE_FLAG, BILLABLE_FLAG — Task service type and chargeability/billability attributes.

Common Use Cases and Queries

The view is typically queried to extract the current PM reference mapping, to reconcile Oracle Projects dates and statuses against an external system, or to report on project and task schedules. A representative query returning project start dates for a given external reference is:

SELECT project_id,
       pm_project_reference,
       project_start_date,
       project_completion_date,
       project_status_code
FROM   apps.pa_pm_reference_v
WHERE  pm_project_reference = :pm_ref
ORDER BY project_id, task_number;

To list all tasks belonging to a project together with their external references and schedule dates, the same view can be filtered by PROJECT_ID. Because the source query uses an inner join, any project without tasks is excluded; callers that require task-less projects should query PA_PROJECTS directly. As with all APPS views, it should be accessed with the appropriate MO: Operating Unit and Projects security context in 12.1.1 and 12.2.2.