Results for “elm_rec_ver_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_DLV_ASSCN_TASKS_V is an APPS-owned, VALID Oracle EBS view in the Projects (PA) module that exposes the complete attribute set of a Deliverable together with its associated task relationships. The view's stated purpose is to select all attributes of a Deliverable, and it accomplishes this by joining project element, version, scheduling, status, percent-complete, progress rollup, person, and object-relationship data into a single denormalized row set. It is available in both Oracle EBS 12.1.1 and 12.2.2, where the documented view metadata confirms the same set of referenced base objects.

Because deliverables in Oracle Projects are modeled as project elements with an object type of PA_DELIVERABLES, and because their linkage to tasks is stored as generic object relationships, the view serves as the canonical reporting interface for deliverable-to-task associations. It is typically used in project reporting, deliverable tracking, and integration extracts rather than for transactional data entry.

Underlying Base Objects

The documented referenced base objects for this view are listed below. Each is accessed via an APPS synonym in the view definition.

• PA_PROJ_ELEMENTS (SYNONYM) — the master project element record, filtered to OBJECT_TYPE = 'PA_DELIVERABLES'.
• PA_PROJ_ELEMENT_VERSIONS (SYNONYM) — version rows linked by PROJ_ELEMENT_ID and PROJECT_ID.
• PA_PROJ_ELEM_VER_SCHEDULE (SYNONYM) — schedule dates for the element version.
• PA_PROJECT_STATUSES (SYNONYM) — status descriptions for both element status and progress status (aliased twice as PPS and STA).
• PA_PERCENT_COMPLETES (SYNONYM) — percent-complete records matched on object id and as-of date.
• PA_PROGRESS_ROLLUP (SYNONYM) — rolled-up progress and completion percentage data.
• PER_ALL_PEOPLE_F (SYNONYM) — the deliverable manager's person name, joined with effective dates.
• PA_OBJECT_RELATIONSHIPS (SYNONYM) — the association rows defining deliverable-to-task relationships, filtered by RELATIONSHIP_TYPE = 'A' and RELATIONSHIP_SUBTYPE = 'TASK_TO_DELIVERABLE'.

The view is a direct projection over these objects; it does not materialize or aggregate beyond the supplied joins.

Key Columns

• ELEMENT_NUMBER, NAME — human-readable identifier and name of the deliverable.
• OBJECT_TYPE, PROJ_ELEMENT_ID, PROJECT_ID — element classification and keys.
• STATUS_CODE — deliverable status code, resolved to a description by the PROJECT_STATUS_NAME column.
• MANAGER_PERSON_ID and FULL_NAME — the responsible manager, sourced from PER_ALL_PEOPLE_F.
• ELEMENT_VERSION_ID, PARENT_STRUCTURE_VERSION_ID — version and parent structure identity.
• SCHEDULED_FINISH_DATE, ACTUAL_FINISH_DATE — schedule dates from PA_PROJ_ELEM_VER_SCHEDULE.
• PROGRESS_STATUS_CODE, COMPLETED_PERCENTAGE, PERCENT_COMPLETE_ID — progress and completion metrics.
• RELATIONSHIP_TYPE, RELATIONSHIP_SUBTYPE — the association type; the view restricts RELATIONSHIP_TYPE to 'A' and RELATIONSHIP_SUBTYPE to 'TASK_TO_DELIVERABLE'.
• OBJECT_ID_FROM1, OBJECT_ID_TO1, OBJECT_ID_FROM2, OBJECT_ID_TO2 — the generic relationship endpoints that bind deliverable and task.
• WEIGHTING_PERCENTAGE, OBJECT_RELATIONSHIP_ID — weighting and relationship identity.
• RECORD_VERSION_NUMBER — version control for concurrency.

Common Use Cases and Queries

The view is principally used to list deliverables and the tasks they are associated with, and to report progress against those deliverables by project.

• Deliverable-to-task mapping: SELECT ELEMENT_NUMBER, NAME, PROJECT_ID, OBJECT_ID_FROM1, OBJECT_ID_TO2, RELATIONSHIP_SUBTYPE FROM PA_DLV_ASSCN_TASKS_V WHERE PROJECT_ID = :p_project_id;
• Deliverable progress tracking: SELECT ELEMENT_NUMBER, NAME, COMPLETED_PERCENTAGE, PROGRESS_STATUS_CODE, SCHEDULED_FINISH_DATE, ACTUAL_FINISH_DATE FROM PA_DLV_ASSCN_TASKS_V WHERE PROJECT_ID = :p_project_id ORDER BY SCHEDULED_FINISH_DATE;
• Manager accountability: SELECT FULL_NAME, COUNT(*) FROM PA_DLV_ASSCN_TASKS_V GROUP BY FULL_NAME;
• Integration extracts filtering by RELATIONSHIP_SUBTYPE = 'TASK_TO_DELIVERABLE' to isolate task-based associations.

Because the relationship filter is embedded in the view definition, queries return only task-to-deliverable associations and require no additional predicate on the relationship subtype.