Search Results pa_actions




Overview
Explore in AI Chat

Overview

APPS.PA_DLVR_TYPE_ACTIONS_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that exposes the relationship between deliverable types and the actions configured against them. In the Projects data model, deliverable types are stored as project elements with the discriminator OBJECT_TYPE = 'PA_DLVR_TYPES', while the actions performed against those deliverables are stored as project elements with OBJECT_TYPE = 'PA_ACTIONS'. The association between the two is captured in PA_OBJECT_RELATIONSHIPS as the 'A' relationship type. This view joins those elements together with version, scheduling, and status information, producing a single denormalized result set suitable for reporting, integration extracts, and diagnostic queries. It is commonly reached when users search on "pa_dlvr_types," since the view is the primary published access path for the deliverable-type-to-action linkage. The view is owned by APPS and is a read-only construct; no DML should be issued against it.

Underlying Base Objects

The view is defined over five documented base objects and one PL/SQL package:

Key Columns

  • ELEMENT_NUMBER, NAME, DESCRIPTION — identity of the action element.
  • OBJECT_TYPE — will resolve to 'PA_ACTIONS' for rows returned by this view.
  • PROJ_ELEMENT_ID, PROJECT_ID, ELEMENT_VERSION_ID — primary identifiers used to join to other Projects entities.
  • STATUS_CODE / PROJECT_STATUS_NAME — status of the element plus the decoded status name.
  • SCHEDULED_FINISH_DATE — planned completion date from the version schedule.
  • FUNCTION_CODE plus the GET_PA_LOOKUP_MEANING expression — the action's function and its translated lookup meaning from the PA_DLVR_ACTION_FUNCTION lookup.
  • OBJECT_ID_FROM1 / OBJECT_ID_FROM2 — the identifiers of the originating deliverable type in PA_OBJECT_RELATIONSHIPS.
  • OBJECT_RELATIONSHIP_ID, OBJECT_TYPE_FROM — the relationship record identifier and the source object type ('PA_DLVR_TYPES').
  • RECORD_VERSION_NUMBER — appears multiple times, once from PPE and once from PPV, supporting optimistic locking and change detection.

Common Use Cases and Queries

Typical scenarios include retrieving all actions defined for a given deliverable type, verifying that a relationship exists in PA_OBJECT_RELATIONSHIPS, and feeding downstream extracts for project planning reports.

Example — list actions for a specific deliverable type:

  • SELECT element_number, name, function_code, project_status_name, scheduled_finish_date FROM apps.pa_dlvr_type_actions_v WHERE object_id_from1 = :deliverable_type_id;

Example — audit relationship coverage:

  • SELECT v.project_id, v.object_id_from1, v.object_relationship_id, COUNT(*) FROM apps.pa_dlvr_type_actions_v v GROUP BY v.project_id, v.object_id_from1, v.object_relationship_id;

Because the view includes a package function call per row, queries returning large volumes should be restricted with predicates on PROJECT_ID or OBJECT_ID_FROM1 to avoid unnecessary function invocations. The join to PA_PROJECT_STATUSES is an outer join, so PROJECT_STATUS_NAME can be NULL when no matching status code exists.