Results for “mapped_fin_task_name”

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

Overview

PA_MAP_WP_TO_FIN_TASKS_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the relationship between workplan tasks and their corresponding financial tasks within a project structure. Financial structures in Oracle Projects are frequently derived from workplan structures through structure sharing, and the mapping between the two is governed by the STRUCTURE_SHARING_CODE attribute on the project. This view abstracts that mapping logic by resolving both direct (shared) and indirect (mapped) financial task references through a set of PL/SQL utility functions.

The view is primarily intended for reporting, diagnostics, and integration scenarios where the identity of the financial task corresponding to a given workplan task must be determined. Because structure sharing can be configured in several modes — full sharing, partial sharing, split with mapping, and split without mapping — the view normalizes these variations into a consistent columnar output, allowing consumers to query a single object rather than reimplementing the mapping rules.

Underlying Base Objects

The view is defined over four base tables plus two helper PL/SQL packages:

• PA_PROJ_ELEMENT_VERSIONS — provides the workplan task element version records (ELEMENT_VERSION_ID, PROJ_ELEMENT_ID, PROJECT_ID, PARENT_STRUCTURE_VERSION_ID). The view filters OBJECT_TYPE = 'PA_TASKS'.
• PA_PROJ_ELEMENTS — supplies the task number (ELEMENT_NUMBER) and task name (NAME) for each element.
• PA_OBJECT_RELATIONSHIPS — joined via OBJECT_ID_TO1 = ELEMENT_VERSION_ID and RELATIONSHIP_TYPE = 'S', establishing the structural predecessor/successor linkage used to derive OBJECT_ID_FROM1.
• PA_PROJECTS_ALL — supplies STRUCTURE_SHARING_CODE, which drives the DECODE branching in the view logic.
• PA_PROJ_STRUC_MAPPING_UTILS — a package supplying GET_MAPPED_FIN_TASK_VERSION_ID, GET_MAPPED_FIN_TASK_ID, GET_MAPPED_FIN_TASK_NAME, and GET_MAPPED_STRUCT_VER_ID for non-SHARE_FULL sharing modes.
• PA_PROJ_ELEMENTS_UTILS — invoked via CHECK_IS_WORKPLAN_TASK to restrict output to elements that are genuine workplan tasks.

The PROJECT_ID in the PROJECTS_ALL predicate is restricted to projects whose STRUCTURE_SHARING_CODE is one of SHARE_FULL, SHARE_PARTIAL, SPLIT_MAPPING, or SPLIT_NO_MAPPING, excluding projects without structure sharing.

Key Columns

• ELEMENT_VERSION_ID — the workplan task element version identifier; the primary join key for the mapping.
• PROJ_ELEMENT_ID — the underlying project element identifier for the workplan task.
• OBJECT_TYPE — always 'PA_TASKS' as filtered by the view definition.
• TASK_NUMBER / TASK_NAME — the workplan task number and name from PA_PROJ_ELEMENTS.
• PROJECT_ID — the project that owns the workplan task.
• MAPPED_FIN_TASK_VERSION_ID — the element version ID of the corresponding financial task; under SHARE_FULL this equals ELEMENT_VERSION_ID; under SPLIT_NO_MAPPING it is NULL; otherwise resolved via PA_PROJ_STRUC_MAPPING_UTILS.
• MAPPED_FIN_TASK — the mapped financial task identifier (PROJ_ELEMENT_ID equivalent for the financial side).
• MAPPED_FIN_TASK_NAME — the financial task name, resolved through the mapping utility.
• PARENT_STRUCTURE_VERSION_ID — the parent structure version of the workplan task, enabling hierarchical traversal.

Common Use Cases and Queries

Typical usage includes reconciling workplan and financial task hierarchies, validating structure-sharing configuration after project setup, and populating integration extracts that require both task identities. A representative query listing all workplan tasks for a project alongside their financial counterparts is:

• SELECT project_id, task_number, task_name, mapped_fin_task, mapped_fin_task_name FROM pa_map_wp_to_fin_tasks_v WHERE project_id = :p_project_id ORDER BY task_number;
• SELECT task_number, task_name FROM pa_map_wp_to_fin_tasks_v WHERE mapped_fin_task IS NULL AND project_id = :p_project_id; — identifies workplan tasks lacking a financial mapping, useful under SPLIT_NO_MAPPING configurations.
• SELECT COUNT(*) FROM pa_map_wp_to_fin_tasks_v WHERE project_id = :p_project_id AND mapped_fin_task_version_id = element_version_id; — confirms full sharing behavior.

Because the view invokes PL/SQL functions per row for non-shared structures, queries should be restricted by PROJECT_ID to avoid full-table scans across large Projects implementations.