Search Results deliverable_system_status_code

Overview

APPS.PA_DELIVERABLES_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as PA.PA_DELIVERABLES_V. It presents a denormalized, reporting-oriented picture of project deliverables and other project elements defined in Oracle Projects, joining element definitions, element versions, scheduling rows, progress and percent-complete records, project attributes, task types, and the managing person. The view carries a status of VALID and an Oracle Internal Use Only warning, meaning the object is not supported for direct customer access except through standard Oracle Applications programs. In practice the view is widely read by project reporting extracts, Discoverer workbooks, OBIEE/OTBI custom queries, and third-party integrations that need deliverable-level data without navigating the normalized Projects schema directly.

Underlying Base Objects

The documented dependency list shows the view is built over the following synonyms:

• PA_PROJ_ELEMENTS — the master element (deliverable, task, work package) definition.
• PA_PROJ_ELEMENT_VERSIONS — versioned attributes of each element.
• PA_PROJ_ELEM_VER_SCHEDULE — scheduled dates and weighting for each element version.
• PA_PROJECTS_ALL — project header data used for project name, number, and template flag.
• PA_PROJECT_STATUSES — status code and status name descriptions for projects.
• PA_PERCENT_COMPLETES — percent-complete records for each element version.
• PA_PROGRESS_ROLLUP — rolled-up progress status and progress comments.
• PA_TASK_TYPES — task type description for the associated project element.
• PER_ALL_PEOPLE_F — the manager of record for the deliverable.

The joins key on PROJ_ELEMENT_ID, ELEMENT_VERSION_ID, and PROJECT_ID, with effective-dated lookups against PER_ALL_PEOPLE_F and status descriptions supplied by the Projects status table. Because the base objects are synonyms beneath the APPS schema, the view resolves to the installed PA tables at runtime.

Key Columns

The column list below is drawn from the ETRM metadata; the searched attribute DLVR_TYPE_ID is included and identifies the deliverable type classification for the element.

• ELEMENT_NUMBER, ELEMENT_NAME — user-facing identifier and name of the deliverable.
• PROJ_ELEMENT_ID, ELEMENT_VERSION_ID, ELM_REC_VER_NUMBER, ELM_VER_REC_VER_NUM — primary and versioned keys that identify the specific element and its version.
• PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER, PROJECT_STATUS_NAME — project context, joining to PA_PROJECTS_ALL and PA_PROJECT_STATUSES.
• DLVR_TYPE_ID — numeric identifier of the deliverable type, the value users search on when filtering by deliverable type.
• MANAGER_PERSON_ID, FULL_NAME — the managing person from PER_ALL_PEOPLE_F.
• STATUS_CODE, DELIVERABLE_SYSTEM_STATUS_CODE — element status and system-calculated status.
• PROGRESS_STATUS_CODE, PROGRESS_STATUS_NAME, PROGRESS_COMMENT, PROG_DESCRIPTION, COMPLETED_PERCENTAGE, PERCENT_COMPLETE_ID, DATE_COMPUTED — progress tracking data rolled up from PA_PROGRESS_ROLLUP and PA_PERCENT_COMPLETES.
• DUE_DATE, COMPLETION_DATE — scheduling dates from PA_PROJ_ELEM_VER_SCHEDULE.
• PROGRESS_WEIGHT, TASK_TYPE, TEMPLATE_FLAG, OBJECT_TYPE — weighting and classification attributes.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — descriptive flexfield segments exposed for reporting.

Common Use Cases and Queries

Typical reporting scenarios include deliverable status dashboards, overdue deliverable extracts, progress roll-up analysis by project, and filtering on DLVR_TYPE_ID to isolate a specific class of deliverable. A representative query is:

SELECT d.project_number, d.project_name, d.element_number, d.element_name, d.dlvr_type_id, d.status_code, d.completed_percentage, d.due_date, d.completion_date, d.full_name AS manager FROM apps.pa_deliverables_v d WHERE d.dlvr_type_id = :p_dlvr_type_id AND d.status_code <> 'CANCELLED' ORDER BY d.project_number, d.element_number;

For overdue deliverable output, add AND d.completion_date IS NULL AND d.due_date < SYSDATE. For project-level progress summaries, aggregate completed_percentage and progress_weight grouped by project_id. Because the object is flagged Oracle Internal Use Only, integrations should prefer supported public APIs or documented interface views where equivalent, and any direct query should be treated as a custom, upgrade-sensitive solution.