Search Results mapped_fin_task_id




Overview
Explore in AI Chat

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

Overview

PA_MAP_WP_TO_FIN_TASKS_TMP is a temporary staging table in the Oracle Projects (PA) schema. It supports the mapping between Workplan (WP) task elements and their corresponding financial task structures during integration and synchronization routines within Oracle E-Business Suite 12.1.1 and 12.2.2. The table operates as a transient workspace where the Projects application materializes the relationship between project workplan element versions and financial task versions before committing them to permanent structures such as PA_PROJ_ELEMENT_VERSIONS and the corresponding financial task tables.

From a Data Vault modeling perspective, the object is heuristically classified as standalone. This classification reflects that the table has no inbound foreign keys from other tables and only one outbound reference, meaning it does not function as a hub, link, or satellite in a strict Data Vault sense. Instead, it behaves as a staging or interface table whose lifecycle is bounded by the concurrent program or process that populates and consumes it.

Key Information Stored

The table contains twelve documented columns. The most significant are:

No surrogate primary key or unique index is documented in the ETRM metadata, which is consistent with the table's role as a temporary staging object rather than a persistent entity. Business-key candidates would typically be the combination of PROJECT_ID, TASK_NUMBER, and the mapped financial task identifiers, but these are not enforced by documented constraints.

Common Use Cases and Queries

This table is primarily consumed by Oracle Projects concurrent programs that synchronize workplan tasks with financial tasks, such as the processes that maintain consistency between project workplan structures and their financial counterparts. Typical use cases include:

  • Diagnosing mapping failures during workplan-to-financial-task synchronization.
  • Reconciling workplan tasks that lack a corresponding financial task mapping.
  • Auditing the parent-child hierarchy used during a mapping run.

A representative query to identify unmapped workplan tasks is:

SELECT t.project_id, t.task_number, t.task_name FROM pa_map_wp_to_fin_tasks_tmp t WHERE t.mapped_fin_task_id IS NULL;

A query to join back to the source element versions is:

SELECT t.task_number, t.task_name, v.element_version_id FROM pa_map_wp_to_fin_tasks_tmp t, pa_proj_element_versions v WHERE t.element_version_id = v.element_version_id;

Because the table is temporary, its contents are only meaningful during the execution window of the mapping process. Reports should therefore be run in conjunction with, or immediately after, the relevant concurrent request.

Related Objects

The most significant related objects are:

  • PA_PROJ_ELEMENT_VERSIONS – Referenced via ELEMENT_VERSION_ID; the authoritative source of project element version data.
  • PA_PROJECTS_ALL – Provides project context via PROJECT_ID.
  • PA_TASKS – Supplies financial task definitions that MAPPED_FIN_TASK_ID resolves against.
  • PA_STRUCTURES – Relates to the financial structure versions referenced by MAPPED_FIN_STR_VERSION_ID.
  • PA_PROJ_ELEMENTS – Underlies PROJ_ELEMENT_ID and parent element relationships.

These objects together form the context in which the temporary mapping data is validated and ultimately persisted.