Results for “pa_fin_latest_pub_tasks_v”

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

Overview

PA_FIN_LATEST_PUB_TASKS_V is a financial reporting view in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and documented as VALID in ETRM 12.2.2. Its purpose, per the ETRM description, is to select the tasks belonging to the latest published structure version together with the financial structure version. This makes it a convenience layer for consumers that need the intersection of the most recently published workplan structure and the financial (budgeted/costed) structure, without having to reconstruct the multi-table join themselves.

In practice, the view is consumed by financial reporting extracts, budget and commitment roll-up logic, and integration interfaces that must resolve the effective task hierarchy. Because it filters on LATEST_EFF_PUBLISHED_FLAG, it reflects only the currently effective published element versions, which prevents stale or superseded structure versions from leaking into downstream calculations.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_PROJ_ELEMENTS (synonym) — the project element master, filtered to OBJECT_TYPE = 'PA_TASKS'.
• PA_PROJ_ELEMENT_VERSIONS (synonym) — the versioned element records, linked by PROJECT_ID and PROJ_ELEMENT_ID.
• PA_PROJ_ELEM_VER_STRUCTURE (synonym) — the element-version-to-structure link, where LATEST_EFF_PUBLISHED_FLAG = 'Y' restricts the result to the latest published version.
• PA_PROJ_STRUCTURE_TYPES (synonym) — associates each project element with a structure type.
• PA_STRUCTURE_TYPES (synonym) — supplies STRUCTURE_TYPE_CLASS_CODE; the view explicitly requires this to equal 'WORKPLAN'.
• PA_LOOKUPS (view) — joined on LOOKUP_TYPE = 'PA_STRUCTURE_TYPE_CLASS' and LOOKUP_CODE = PST.STRUCTURE_TYPE to produce a translated MEANING.
• PA_PROJECT_STATUSES (synonym) — used to exclude projects whose system status is 'CANCELLED'.

Two notable structural filters appear in the SQL: the UNION branches select elements having either two structure types or one structure type respectively, and the condition PPE.LINK_TASK_FLAG <> 'Y' suppresses linked tasks. This explains why the searched term "pa_structure_type_class" is central to the object: the structure type class determines whether a structure qualifies as a workplan.

Key Columns

• NAME — the project element (task) name.
• ELEMENT_NUMBER — the task's element number.
• PROJ_ELEMENT_ID — the surrogate key of the project element.
• PROJECT_ID — the owning project identifier.
• STRUCTURE_TYPE_ID — the structure type associated with the element.
• STRUCTURE_TYPE_CLASS_CODE — the class of the structure type, constrained to 'WORKPLAN'.
• MEANING — the lookup-derived description of the structure type, sourced from PA_LOOKUPS for lookup type PA_STRUCTURE_TYPE_CLASS.

Common Use Cases and Queries

A typical use is enumerating currently published workplan tasks for a project:

SELECT project_id, proj_element_id, element_number, name, structure_type_class_code
FROM apps.pa_fin_latest_pub_tasks_v
WHERE project_id = :p_project_id
ORDER BY element_number;

The structure type class is often used to confirm a row represents workplan content, and the MEANING column supports reporting without an additional lookup join. Because the view already excludes cancelled projects and linked tasks, it is a suitable source for budget and cost integrations that must operate only on valid, published task structures.