Results for “share_full”

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

Overview

The view APPS.PA_MAP_WP_TO_FIN_TASKS_V is an Oracle Projects internal view that exposes the mapping between workplan (WP) task elements and their corresponding financial task elements. In Oracle EBS 12.1.1 and 12.2.2, projects may be managed through a workplan structure that is distinct from the financial structure; this view bridges the two by resolving each workplan task element to its mapped financial task element and version. It is particularly relevant to users searching on MAPPED_FIN_TASK_ID, which returns the identifier of the financial task corresponding to a given workplan task. The object carries the standard Oracle internal-use warning: it is not supported for direct customer access except through Oracle Applications programs, and its definition may change without notice across releases or patches. It is defined in the APPS schema, registered under FND Design Data as PA.PA_MAP_WP_TO_FIN_TASKS_V, and reported as VALID. The view is consumed primarily by Oracle Projects costing, budgeting, forecasting, and multi-currency processing logic rather than by end-user reporting, making it a supporting object within the Project Management and financial integration layer.

Underlying Base Objects

The view is defined over the following documented objects:

• PA_PROJ_ELEMENT_VERSIONS — supplies element version records, including ELEMENT_VERSION_ID, PARENT_ELEMENT_VERSION_ID, and the structure version identifiers.
• PA_PROJ_ELEMENTS — supplies the project element definitions and the PROJ_ELEMENT_ID.
• PA_PROJECTS_ALL — supplies the owning PROJECT_ID for the element.
• PA_OBJECT_RELATIONSHIPS — holds the relationship records that tie a workplan element version to its financial element version, forming the core of the mapping.
• PA_PROJ_ELEMENTS_UTILS (package) — provides element resolution and utility logic used in the view definition.
• PA_PROJ_STRUC_MAPPING_UTILS (package) — provides structure mapping logic that translates workplan structure versions to financial structure versions.

The view is in turn referenced by several Oracle Projects programs, including PA_FP_GEN_BILLING_AMOUNTS, PA_FP_GEN_BUDGET_AMT_PUB, PA_FP_GEN_FCST_AMT_PUB1, PA_FP_GEN_FCST_AMT_PVT, PA_MULTI_CURRENCY_TXN, and PA_TASK_ASSIGNMENT_UTILS. These consumers indicate the view is used in forecasting, budgeting, billing amount generation, and task assignment flows, where workplan-to-financial task alignment is required.

Key Columns

• ELEMENT_VERSION_ID — identifier of the workplan element version being mapped.
• PROJ_ELEMENT_ID — identifier of the underlying project element.
• OBJECT_TYPE — classifies the element type (for example, task).
• TASK_NUMBER / TASK_NAME — the workplan task's number and name.
• PROJECT_ID — the project to which the element belongs.
• MAPPED_FIN_TASK_VERSION_ID — version identifier of the mapped financial task.
• MAPPED_FIN_TASK_ID — the financial task identifier to which the workplan task maps; the column most commonly sought.
• MAPPED_FIN_TASK_NAME — descriptive name of the mapped financial task.
• PARENT_ELEMENT_VERSION_ID — parent workplan element version.
• MAPPED_FIN_STR_VERSION_ID — version identifier of the mapped financial structure.
• PARENT_STRUCTURE_VERSION_ID — parent structure version for the element.

Common Use Cases and Queries

Typical usage involves resolving a workplan task to its financial task for cost, budget, or forecast processing; validating that mappings exist before running financial plan generation; and tracing structure version mappings between workplan and financial structures.

Retrieve the financial task for a specific workplan element version:

• SELECT ELEMENT_VERSION_ID, MAPPED_FIN_TASK_ID, MAPPED_FIN_TASK_NAME FROM APPS.PA_MAP_WP_TO_FIN_TASKS_V WHERE ELEMENT_VERSION_ID = :element_version_id;

List all mapped tasks for a project:

• SELECT TASK_NUMBER, TASK_NAME, MAPPED_FIN_TASK_ID, MAPPED_FIN_TASK_NAME FROM APPS.PA_MAP_WP_TO_FIN_TASKS_V WHERE PROJECT_ID = :project_id ORDER BY TASK_NUMBER;

Because the view is Oracle-internal and unsupported for direct querying, such statements are best reserved for diagnostic or investigative purposes, with production logic driven through the supported Oracle Projects APIs and concurrent programs listed above.