Results for “object_version_id”

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

Overview

PA_LAUNCH_PAGE_OBJECTS_TM_V is a consolidated reporting view owned by the APPS schema in Oracle E-Business Suite, filed under the Projects (PA) product family. Its documented description states that it "gives the consolidated list of objects," and in ETRM 12.2.2 its status is VALID. The view is intended to serve as the data source behind task- and object-oriented launch pages, surfacing a unified projection of project task elements together with their classification, ownership, status, schedule, and progress attributes. Rather than requiring the caller to join the PA_PROJ_ELEMENTS hierarchy, versioning, scheduling, and status tables independently, the view performs that consolidation in a single definition, allowing reporting pages, dashboards, and integration interfaces to retrieve a ready-to-consume task object list. The "_TM_V" suffix conventionally denotes a translated or materialized-for-launch representation, and the presence of TO_CHAR, TO_NUMBER, and NULL placeholders in the view text indicates that it is a positional projection designed to match a fixed launch-page interface contract.

Underlying Base Objects

The documented referenced base objects include synonyms and views spanning tasks, project definitions, parties, and lookups: PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_SCHEDULE, PA_TASK_TYPES, PA_PROJECTS_ALL, PA_PROJECT_STATUSES, PA_LOOKUPS, PA_PERCENT_COMPLETES, HZ_PARTIES, and PA_CI_TYPES_B / PA_CI_TYPES_TL. Utility logic is supplied by the packages PA_PROJECT_STRUCTURE_UTILS, PA_PROJ_ELEMENTS_UTILS, and PA_DELIVERABLE_UTILS, and control items are represented through PA_CONTROL_ITEMS. Structurally, PA_PROJ_ELEMENTS is the driving table, filtered to OBJECT_TYPE = 'PA_TASKS', and it is joined to PA_PROJECTS_ALL on PROJECT_ID to obtain the parent project. PA_PROJ_ELEMENT_VERSIONS is joined on PROJ_ELEMENT_ID, with its PARENT_STRUCTURE_VERSION_ID constrained through PA_PROJECT_STRUCTURE_UTILS.GET_LATEST_WP_VERSION(PPE.PROJECT_ID) so that only the latest workplan structure version is returned. PA_PROJ_ELEM_VER_SCHEDULE is outer-joined on ELEMENT_VERSION_ID to supply scheduled and actual dates. Owner information is resolved by matching HZ_PARTIES.ORIG_SYSTEM_REFERENCE to the PER: prefix plus the element's MANAGER_PERSON_ID. Lookups for priority (PA_TASK_PRIORITY_CODE) and object classification (PA_OBJECTS = 'PA_TASKS') are outer-joined from PA_LOOKUPS, while status and progress names come from PA_PROJECT_STATUSES filtered by STATUS_TYPE, and completion percentages come from PA_PERCENT_COMPLETES.

Key Columns

• PROJ_ELEMENT_ID / ELEMENT_VERSION_ID – primary identity of the task and its versioned workplan record.
• ELEMENT_NUMBER, NAME, DESCRIPTION – descriptive task attributes inherited from PA_PROJ_ELEMENTS.
• PROJECT_ID, SEGMENT1, project NAME – linkage to the parent project in PA_PROJECTS_ALL.
• TASK_TYPE – from PA_TASK_TYPES, classifying the task.
• LOOKUP_CODE / MEANING – classification ('PA_TASKS') and priority meaning ('PA_TASK_PRIORITY_CODE').
• OWNER.PARTY_NAME, PARTY_ID – the person record resolved through HZ_PARTIES.
• PROJECT_STATUS_NAME, STATUS_ICON_ACTIVE_IND, PROJECT_SYSTEM_STATUS_CODE – task status and its visual indicator.
• SCHEDULED_FINISH_DATE, ACTUAL_START_DATE, ACTUAL_FINISH_DATE – schedule data; a computed days-to-finish expression is also exposed.
• COMPLETED_PERCENTAGE, DATE_COMPUTED – progress metrics from PA_PERCENT_COMPLETES.

Common Use Cases and Queries

Typical usage includes populating launch-page task lists, feeding project management dashboards, and extracting task-level status and schedule data for integration. A representative query restricted to a project is:

SELECT element_number, name, task_type, project_status_name,
       scheduled_finish_date, completed_percentage, owner_party_name
FROM   apps.pa_launch_page_objects_tm_v
WHERE  project_id = :p_project_id;

Because task versions are constrained to the latest workplan version, the view consistently reflects current structure without additional filtering. The outer joins on status, priority, and schedule ensure tasks lacking those attributes still appear, making the view suitable for completeness-oriented reporting.