Search Results function_code_name




Overview
Explore in AI Chat

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.

Key Columns

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.