Search Results deliverable_system_status_code

Overview

PA_DELIVERABLES_V is a Projects (PA) module view owned by the APPS schema. Its documented purpose is to select all attributes of a Deliverable, which in Oracle Projects terminology is a project element that represents a tangible or intangible output produced during the execution of a project. The view consolidates information from the core project element tables, project definition tables, progress rollup tables, and the HR person table into a single denormalized result set, exposing deliverable identity, status, progress, scheduling, and descriptive flexfield data.

Because Oracle EBS report and integration developers rarely need to reconstruct the multi-table join logic required to resolve a current, published deliverable record, PA_DELIVERABLES_V serves as the standard read-only interface for that purpose. It is commonly referenced in custom reports, Oracle Business Intelligence Publisher data templates, and inbound/outbound interfaces that must resolve deliverable metadata without touching base tables directly.

Underlying Base Objects

The view is defined over the following documented base objects, most of which are accessed through APPS synonyms:

• PA_PROJ_ELEMENTS — the driving table, filtered by OBJECT_TYPE = 'PA_DELIVERABLES'.
• PA_PROJ_ELEMENT_VERSIONS and PA_PROJ_ELEM_VER_SCHEDULE — provide version identity and schedule dates.
• PA_PROJECTS_ALL — supplies project name, number, and template flag.
• PA_PROJECT_STATUSES — resolves the system status code to its name, via an outer join.
• PA_TASK_TYPES — resolves the deliverable type (TYPE_ID) to a task type name.
• PA_PROGRESS_ROLLUP — provides the current, published workplan progress status and percentage complete, restricted to STRUCTURE_TYPE = 'WORKPLAN' and CURRENT_FLAG = 'Y'.
• PA_PERCENT_COMPLETES — supplies percent-complete identifiers and variance fields, matched on the progress rollup as-of date.
• PER_ALL_PEOPLE_F — resolves the deliverable manager, filtered to the effective-dated row active at SYSDATE via an outer join.

All joins other than the driving element/version join and the project ID equality are outer joins, so a deliverable is returned even where status, manager, progress, or percent-complete data is absent.

Key Columns

• ELEMENT_NUMBER / ELEMENT_NAME — the deliverable's user-visible identifier and description.
• PM_SOURCE_REFERENCE — the source reference carried from the originating project management or external system; this is the column users search for when tracing a deliverable back to its upstream system of record.
• OBJECT_TYPE — always 'PA_DELIVERABLES' for rows returned by this view.
• PROJ_ELEMENT_ID / PROJECT_ID / ELEMENT_VERSION_ID — primary and foreign key references linking the deliverable to its project and version.
• STATUS_CODE / PROJECT_STATUS_NAME / DELIVERABLE_SYSTEM_STATUS_CODE — the deliverable's status and its resolved name.
• MANAGER_PERSON_ID / FULL_NAME — the deliverable owner/manager and person name.
• DLVR_TYPE_ID / TASK_TYPE — the deliverable classification.
• PROGRESS_WEIGHT / COMPLETED_PERCENTAGE / COMPLETED_PERCENTAGE / PERCENT_COMPLETE_ID / DATE_COMPUTED — progress measurement and the as-of date on which it was computed.
• DUE_DATE / COMPLETION_DATE — planned and actual completion dates.
• PROGRESS_STATUS_CODE / PROGRESS_STATUS_NAME / PROGRESS_COMMENT — the published workplan progress state.
• PROJECT_NAME / PROJECT_NUMBER / TEMPLATE_FLAG — parent project context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments for customer-specific deliverable attributes.

Common Use Cases and Queries

A frequent requirement is locating deliverables by the source reference stored in PM_SOURCE_REFERENCE, for example when reconciling an external project-management tool against Oracle Projects:

SELECT element_number, element_name, pm_source_reference, project_number, project_name, status_code FROM apps.pa_deliverables_v WHERE pm_source_reference = :source_ref;

Deliverables nearing their due date or overdue can be listed with project context:

SELECT project_number, project_name, element_number, element_name, full_name, due_date FROM apps.pa_deliverables_v WHERE completion_date IS NULL AND due_date BETWEEN SYSDATE AND SYSDATE + 30 ORDER BY due_date;

Progress monitoring queries typically filter on the published workplan values:

SELECT element_number, progress_status_name, completed_percentage, progress_comment, date_computed FROM apps.pa_deliverables_v WHERE status_code = 'ACTIVE' AND completed_percentage < 100;

Because the view already restricts progress and percent-complete joins to CURRENT_FLAG = 'Y' and PUBLISHED_FLAG = 'Y', callers receive only the currently published progress snapshot without additional filtering, provided they are aware that a deliverable with no published workplan will show the outer-joined columns as null.