Search Results action_status_code

Overview

PA_DLVR_TYPE_ACTIONS_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. It selects all attributes of a Deliverable Type Action, joining project element, version, scheduling, status, and object relationship data into a single denormalized result set. Its status is documented as VALID in ETRM for releases 12.1.1 and 12.2.2.

The view presents deliverable type actions as first-class reporting entities. Because it resolves lookup codes into meanings and resolves status codes into descriptive names, it is well suited for read-only reporting, operational dashboards, and integration extracts that must present human-readable values without embedding FND_LOOKUPS or PA_PROJECT_STATUSES logic in every consumer. The view itself is a query surface only; it holds no data and performs no DML.

Underlying Base Objects

The documented referenced base objects are PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_SCHEDULE, PA_PROJECT_STATUSES, PA_OBJECT_RELATIONSHIPS, and the package PA_PROJ_ELEMENTS_UTILS.

• PA_PROJ_ELEMENTS is the driving table, restricted to OBJECT_TYPE = 'PA_ACTIONS'. It supplies element number, name, description, status, and function code.
• PA_PROJ_ELEMENT_VERSIONS is joined on both PROJ_ELEMENT_ID and PROJECT_ID, supplying the element version identifier and version record number.
• PA_PROJ_ELEM_VER_SCHEDULE is joined on ELEMENT_VERSION_ID, supplying the scheduled finish date used as the action due date.
• PA_PROJECT_STATUSES is outer-joined on STATUS_CODE to PROJECT_STATUS_CODE(+), so actions with no matching status still return a row.
• PA_OBJECT_RELATIONSHIPS is joined on PROJ_ELEMENT_ID = OBJECT_ID_TO2 with OBJECT_TYPE_FROM = 'PA_DLVR_TYPES', OBJECT_TYPE_TO = 'PA_ACTIONS', and RELATIONSHIP_TYPE = 'A', resolving the owning deliverable type.
• PA_PROJ_ELEMENTS_UTILS.GET_PA_LOOKUP_MEANING is invoked with lookup type PA_DLVR_ACTION_FUNCTION to translate FUNCTION_CODE.

Key Columns

• ELEMENT_NUMBER, ELEMENT_NAME, DESCRIPTION — identification attributes of the action.
• OBJECT_TYPE — always PA_ACTIONS for rows returned by this view.
• PROJ_ELEMENT_ID, PROJECT_ID, ELEMENT_VERSION_ID — primary and foreign key identifiers for joining to other PA entities.
• ACTION_STATUS_CODE and ACTION_STATUS_MEANING — the action status code and its resolved project status name.
• DUE_DATE — derived from the element version schedule's scheduled finish date.
• FUNCTION_CODE and FUNCTION_CODE_NAME — the raw function code and its lookup meaning from PA_DLVR_ACTION_FUNCTION. This pair is the target of the function_code_name search term.
• ELEM_REC_VER_NUMBER, ELEM_VER_REC_VER_NUMBER, OBJECT_REC_VER_NUMBER — record version numbers for the element, element version, and object relationship respectively.
• PARENT_ELEMENT_ID, PARENT_ELEM_VERSION_ID — parent identifiers resolved from the relationship.
• OBJECT_RELATIONSHIP_ID, PARENT_OBJECT_TYPE — relationship identifier and the parent object type, typically PA_DLVR_TYPES.

Common Use Cases and Queries

The view is typically used to report deliverable type actions with their owning deliverable type, resolve action function and status descriptions, and export action data to external systems. A representative query filtering on function code name is:

• SELECT project_id, proj_element_id, element_name, function_code, function_code_name, action_status_meaning, due_date FROM apps.pa_dlvr_type_actions_v WHERE function_code_name = 'Approval' ORDER BY due_date;
• SELECT v.element_number, v.element_name, v.function_code_name, v.action_status_meaning FROM apps.pa_dlvr_type_actions_v v WHERE v.project_id = :project_id AND v.object_type = 'PA_ACTIONS';
• SELECT function_code, function_code_name, COUNT(*) FROM apps.pa_dlvr_type_actions_v GROUP BY function_code, function_code_name ORDER BY 3 DESC;

Because FUNCTION_CODE_NAME and ACTION_STATUS_MEANING are computed through a PL/SQL lookup call and an outer join respectively, queries filtering on those columns cannot use a simple index on the base table and may force full scans of the join result. For high-volume extracts, filtering on PROJECT_ID or PROJ_ELEMENT_ID first is advisable. Consumers should also note that the outer join to PA_PROJECT_STATUSES can yield null ACTION_STATUS_MEANING values for actions whose status code has no matching project status row.