Search Results pa_deliverable_types_amg_v




Overview
Explore in AI Chat

Overview

PA_DELIVERABLE_TYPES_AMG_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Projects (PA) product family. Its documented purpose is to select all attributes of a Deliverable Type. In EBS terminology, deliverable types are a specialized classification of task types. The underlying PA_TASK_TYPES table stores multiple categories of task structures, and deliverable types represent one specific class of them, distinguished by the value PA_DLVR_TYPES in the OBJECT_TYPE column. This view filters PA_TASK_TYPES accordingly and decorates the result with descriptive values drawn from lookup and project status reference data.

The view is read-only and is intended for inquiry, reporting, and integration scenarios rather than transactional maintenance. Because it exposes decoded meaning columns alongside raw codes, it is frequently used in custom reports, concurrent programs, and interfaces that must display deliverable type information in a user-readable form without performing additional lookup joins. The "AMG" naming convention indicates it is a generated or translated view used to expose attributes in a consistent, presentation-ready structure.

Underlying Base Objects

The view is defined over three referenced objects, as documented in the ETRM metadata:

  • PA_TASK_TYPES (referenced through a synonym) — the primary source of deliverable type records. The view restricts this table with PTT.OBJECT_TYPE = 'PA_DLVR_TYPES', ensuring that only deliverable types, and not other task type categories, are returned. Columns such as TASK_TYPE_ID, TASK_TYPE, DESCRIPTION, and the active date range originate here.
  • PA_PROJECT_STATUSES (synonym) — supplies the initial project status associated with each deliverable type. The join on INITIAL_STATUS_CODE is an outer join (PPS.PROJECT_STATUS_CODE(+)), so deliverable types without a matching status still appear in the result set, with a null status name.
  • PA_LOOKUPS (view) — resolves the deliverable type class code into a displayed meaning. The join uses LOOKUP_TYPE = 'PA_DLVR_TYPE' and matches LOOKUP_CODE to the TASK_TYPE_CLASS_CODE. This is an inner join, so a class code without a corresponding lookup entry will exclude the row.

The relationship structure is therefore a filtered fact source (PA_TASK_TYPES) enriched by two reference objects: one foreign-key-style lookup for class meaning and one optional project status for the initial status name.

Key Columns

Common Use Cases and Queries

Typical uses include populating list-of-values queries, validating deliverable types in interfaces, and joining to deliverable instances in custom extracts. A basic query listing all active deliverable types with their class and initial status is shown below.

SELECT deliverable_type_id,
       deliverable_type,
       deliverable_type_class_meaning,
       initial_status_meaning,
       effective_from_date,
       effective_to_date
  FROM apps.pa_deliverable_types_amg_v
 WHERE TRUNC(SYSDATE) BETWEEN effective_from_date AND NVL(effective_to_date, SYSDATE);

To restrict output to deliverable types permitting progress entry, add a predicate on prog_entry_enable_flag = 'Y'. For integration extracts, the view can be joined to PA_DELIVERABLES on the deliverable type identifier to report which types are in active use. Because the class code to meaning join is an inner join, queries expecting a null-safe class meaning should verify that all in-scope class codes exist in PA_LOOKUPS for lookup type PA_DLVR_TYPE.