Search Results pa_dlvr_type




Overview

APPS.PA_DELIVERABLE_TYPES_AMG_V is a reporting and integration view in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that exposes the set of deliverable type definitions used by Oracle Projects. The view is the primary source of record for deliverable types — the configurable classifications applied to project deliverables — and returns each type together with its assigned class, initial lifecycle status, and the flags and version identifiers that govern how deliverables of that type behave.

The view is named after the "AMG" (Application Message Generator) convention in Oracle Projects, indicating it is intended for programmatic consumption — form LOVs, concurrent processes, Web Services, and SOA/BPEL integrations — as well as ad hoc reporting. Because a deliverable type is referenced by its identifier and its meaning rather than by a hard-coded code, this view is the canonical lookup for populating deliverable-type selection lists. The object is frequently located by users searching on the term pa_dlvr_type, which is both the lookup type carried in PA_LOOKUPS and the value of the OBJECT_TYPE discriminator that filters the underlying PA_TASK_TYPES rows.

Underlying Base Objects

The view's text joins three documented objects:

  • PA_TASK_TYPES (synonym) — aliased PTT, the driving table. It is filtered by PTT.OBJECT_TYPE = 'PA_DLVR_TYPES', which restricts the query to deliverable type records rather than other task-type records stored in the same table.
  • PA_PROJECT_STATUSES (synonym) — aliased PPS, outer-joined on PTT.INITIAL_STATUS_CODE = PPS.PROJECT_STATUS_CODE(+). The outer join allows deliverable types whose initial status code has no matching project status to still be returned.
  • PA_LOOKUPS (view) — aliased PLL, joined on PLL.LOOKUP_TYPE = 'PA_DLVR_TYPE' and PLL.LOOKUP_CODE = PTT.TASK_TYPE_CLASS_CODE, supplying the translated meaning of each deliverable type class.

The relationship is therefore one deliverable type (PA_TASK_TYPES row) to one lookup meaning, optionally to one project status name.

Key Columns

  • TASK_TYPE_ID — the unique primary key of the deliverable type; the value stored as a foreign key on deliverable records.
  • TASK_TYPE — the deliverable type name shown to users.
  • TASK_TYPE_CLASS_CODE — the class code, joined to the lookup; note this column appears twice in the select list.
  • MEANING — the lookup meaning for the type class, providing the descriptive class label.
  • DESCRIPTION — free-text description of the deliverable type.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the active date range; users typically filter on SYSDATE between these values to return only currently enabled types.
  • INITIAL_STATUS_CODE and PROJECT_STATUS_NAME — the status assigned when a deliverable of this type is created, and its display name from the outer join.
  • PROG_ENTRY_ENABLE_FLAG — indicates whether progress entry is permitted for deliverables of this type.
  • ENABLE_DLVR_ACTIONS_FLAG — indicates whether deliverable actions are enabled.
  • RECORD_VERSION_NUMBER — optimistic locking/version stamp used by integration consumers.

Common Use Cases and Queries

Typical scenarios include populating deliverable-type LOVs in custom forms, validating a type ID during interface loading, and reporting which deliverable types are active and their default status.

List active deliverable types with their class and default status:

SELECT task_type_id, task_type, meaning, project_status_name
FROM   apps.pa_deliverable_types_amg_v
WHERE  SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

Resolve a type ID during an interface or reconciliation:

SELECT task_type, meaning, initial_status_code
FROM   apps.pa_deliverable_types_amg_v
WHERE  task_type_id = :p_task_type_id;

Identify types that allow progress entry and deliverable actions:

SELECT task_type, description
FROM   apps.pa_deliverable_types_amg_v
WHERE  prog_entry_enable_flag = 'Y'
AND    enable_dlvr_actions_flag = 'Y';