Results for “completed_percentage”

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

Overview

PA_DELIVERABLES_AMG_V is a Projects (PA) module view owned by the APPS schema and defined as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to select all attributes of a Deliverable, a workplan entity used in Oracle Projects to track contract or project-level deliverables apart from, or in addition to, tasks. The _AMG suffix reflects its role in the Application Management/AMI-style reporting layer that presents denormalized project element information for integration and reporting consumers. The view is a UNION ALL construct: the first branch returns live rows from the base deliverable tables, while the second branch supplies a parallel set of columns with placeholder (NULL) values cast via TO_CHAR(NULL), TO_NUMBER(NULL), and TO_DATE(NULL) to align both branches to a common column list. This design lets Oracle Projects surface deliverables both through the standard progress-tracking path and through alternate representations without altering the underlying data model. Because the view exposes PROGRESS_COMMENT, it is commonly queried by users searching for deliverable-level progress notes and status narrative.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_PROJ_ELEMENTS — the master record for the deliverable, filtered by OBJECT_TYPE = 'PA_DELIVERABLES'.
• PA_PROJ_ELEMENT_VERSIONS — version details keyed by ELEMENT_VERSION_ID.
• PA_PROJ_ELEM_VER_SCHEDULE — scheduling data, providing scheduled and actual finish dates.
• PA_PROJECTS_ALL — project name, number, and project ID context.
• PA_PROJECT_STATUSES — project status name, joined via an outer ((+)) join on STATUS_CODE.
• PA_TASK_TYPES — deliverable type information, filtered on OBJECT_TYPE = 'PA_DLVR_TYPES'.
• PER_ALL_PEOPLE_F — manager full name, resolved through an effective-date outer join (SYSDATE BETWEEN EFFECTIVE_START_DATE(+) AND EFFECTIVE_END_DATE(+)).
• PA_LOOKUPS — deliverable type classification via LOOKUP_TYPE = 'PA_DLVR_TYPE'.
• PA_PROGRESS_ROLLUP, PA_PERCENT_COMPLETES — used in progress/rollup logic and referenced in the documented metadata.

A NOT EXISTS predicate on PA_PROGRESS_ROLLUP (matching project, object, object type, and STRUCTURE_TYPE = 'WORKPLAN' with a NULL structure version) excludes deliverables already represented in the workplan rollup.

Key Columns

• PROJECT_ID, NAME, SEGMENT1 — project identifier, name, and project number.
• PROJ_ELEMENT_ID, ELEMENT_NUMBER — unique deliverable identifier and its element number.
• PROGRESS_COMMENT — narrative comment associated with deliverable progress, the column most relevant to users searching progress notes.
• PROGRESS_STATUS_CODE, PROGRESS_WEIGHT, COMPLETED_PERCENTAGE — progress tracking attributes.
• MANAGER_PERSON_ID, FULL_NAME — deliverable manager reference and name.
• SCHEDULED_FINISH_DATE, ACTUAL_FINISH_DATE — key schedule milestones.
• STATUS_CODE, PROJECT_STATUS_NAME, TASK_TYPE, TYPE_ID — classification and status fields.
• PM_SOURCE_REFERENCE, PM_SOURCE_CODE, RECORD_VERSION_NUMBER — integration and concurrency attributes.

Common Use Cases and Queries

The view supports deliverable reporting, progress tracking extracts, and integration feeds into external project management tools. A typical query retrieving progress comments is shown below.

• Listing deliverables with their progress narrative: SELECT project_id, name, element_number, progress_status_code, progress_comment FROM apps.pa_deliverables_amg_v WHERE progress_comment IS NOT NULL ORDER BY project_id;
• Retrieving schedule data for active deliverables: SELECT project_id, element_number, scheduled_finish_date, actual_finish_date FROM apps.pa_deliverables_amg_v WHERE actual_finish_date IS NULL;
• Extracting deliverables by manager: SELECT element_number, name, full_name FROM apps.pa_deliverables_amg_v WHERE full_name = :manager_name;

Because both UNION ALL branches present a uniform column list, consumers can treat the view as a single, consistent deliverable source, while filtering on any exposed attribute such as PROGRESS_COMMENT to isolate human-authored status notes.