Search Results completion_flag

Overview

PA_DLVR_ACTIONS_AMG_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. Its documented purpose is to select all attributes of a Deliverable Action, presenting action records together with the deliverable to which each action is linked. The view is classified as VALID and is available in both EBS 12.1.1 and 12.2.2, with the same implementation documented in ETRM 12.2.2. It exposes a denormalized, business-friendly projection of data that is otherwise spread across the project element, element version, schedule, relationship, and person tables. The "AMG" suffix indicates that the view is part of Oracle's Application Management Group pattern of views, typically intended for reporting, self-service, or integration use rather than for transactional inserts, updates, or deletes. Its role is therefore to supply deliverable action information to reports, ADF/Java-based user interfaces, Oracle Application Framework pages, and external integration payloads where the consumer requires both action-level detail and the parent deliverable name.

Underlying Base Objects

The documented referenced base objects are PA_PROJ_ELEMENTS (accessed through a synonym), PA_PROJ_ELEMENT_VERSIONS (synonym), PA_PROJ_ELEM_VER_SCHEDULE (synonym), PA_OBJECT_RELATIONSHIPS (synonym), PER_ALL_PEOPLE_F (synonym), and the PA_PROJ_ELEMENTS_UTILS package. The view drives its primary selection from PA_PROJ_ELEMENTS aliased as PPE, restricting rows to those with OBJECT_TYPE = 'PA_ACTIONS'. It joins PA_PROJ_ELEMENT_VERSIONS (PPV) on both PROJ_ELEMENT_ID and PROJECT_ID, and PA_PROJ_ELEM_VER_SCHEDULE (PSC) on ELEMENT_VERSION_ID to obtain scheduled and actual finish dates. PA_OBJECT_RELATIONSHIPS (OBJ) provides the linkage between an action and its deliverable: the action appears as OBJECT_ID_TO2 and the deliverable as OBJECT_ID_FROM2, constrained by RELATIONSHIP_TYPE = 'A' and RELATIONSHIP_SUBTYPE = 'DELIVERABLE_TO_ACTION'. A second reference to PA_PROJ_ELEMENTS, aliased DLV, is joined on OBJECT_TYPE = 'PA_DELIVERABLES' and matching PROJECT_ID to resolve the deliverable name and element number. PER_ALL_PEOPLE_F (PPF) is outer-joined on MANAGER_PERSON_ID and current SYSDATE to resolve the action owner's display name. The PA_PROJ_ELEMENTS_UTILS package function GET_PA_LOOKUP_MEANING is invoked with the lookup type PA_DLVR_ACTION_FUNCTION to translate the function code into a meaning.

Key Columns

• ACTION_ID — the PROJ_ELEMENT_ID of the action record.
• ACTION_NAME — the name of the action (PPE.NAME).
• DESCRIPTION — descriptive text for the action.
• ACTION_OWNER_ID / ACTION_OWNER_NAME — manager person identifier and resolved full name from PER_ALL_PEOPLE_F.
• DUE_DATE — scheduled finish date from PA_PROJ_ELEM_VER_SCHEDULE.
• COMPLETION_DATE — actual finish date.
• COMPLETION_FLAG — derived via DECODE on STATUS_CODE, returning 'Y' for DLVR_COMPLETED and 'N' otherwise.
• FUNCTION_CODE / FUNCTION_CODE_NAME — the action function code and its lookup meaning.
• RECORD_VERSION_NUMBER — optimistic locking version.
• PM_ACTION_REFERENCE / PM_SOURCE_CODE — the PM source reference and source code (PPE.PM_SOURCE_REFERENCE, PPE.PM_SOURCE_CODE).
• DELIVERABLE_ID — OBJECT_ID_FROM2, the deliverable identifier.
• DELIVERABLE_NAME / DELIVERABLE_SHORT_NAME — the deliverable name and element number.
• PROJECT_ID — owning project of the action.

Common Use Cases and Queries

This view is typically queried for deliverable action tracking reports, project status dashboards, and integration extracts. A frequent query retrieves all actions for a given deliverable, using the searched term:

• SELECT action_id, action_name, deliverable_name, completion_flag, due_date FROM pa_dlvr_actions_amg_v WHERE deliverable_name = :p_deliverable_name AND project_id = :p_project_id;
• SELECT action_name, action_owner_name, due_date, completion_date FROM pa_dlvr_actions_amg_v WHERE completion_flag = 'N' AND project_id = :p_project_id ORDER BY due_date;
• SELECT deliverable_name, COUNT(*) FROM pa_dlvr_actions_amg_v GROUP BY deliverable_name;

Because the view already resolves the deliverable linkage, the lookup meaning, and the owner name, consumers avoid replicating the multi-table joins across PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_SCHEDULE, PA_OBJECT_RELATIONSHIPS, and PER_ALL_PEOPLE_F. As with other AMG views, no DML should be issued against it; inserts and updates must target the underlying base tables or the corresponding public APIs.