Results for “get_mapped_struct_ver_id”

8 results




Overview
Explore in AI Chat

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

Overview

PA_PROJ_STRUC_MAPPING_UTILS is an internal PL/SQL utility package in the APPS schema that supports the project structure mapping framework within Oracle Projects. Its role centres on maintaining and resolving the relationships between project structures — tasks, workplans, financial tasks and structure versions — so that the correct identifiers and names are returned when one representation of a project hierarchy is mapped onto another. In Oracle EBS 12.1.1 and 12.2.2, project structures evolve through versioning and publication, and workplan tasks are frequently mapped to financial tasks. This package provides the low-level name parsing and identifier lookup services that the public project structure APIs rely on to translate between those representations. It is classified as an "OTHER" API object, indicating it is not part of the formally committed public interface and is intended for internal consumption by other Oracle Projects components rather than for direct customer use.

Key Procedures and Functions

The package exposes twelve documented procedures and functions, reflecting its role as a shared helper for name and identifier resolution.

  • CHECK_TASK_HAS_MAPPING — Determines whether a given task participates in an existing structural mapping, allowing callers to test mapping existence before taking further action.
  • CHECK_CREATE_MAPPING_OK — Validates whether creation of a mapping is permissible, providing a guard against invalid or duplicate mapping requests.
  • PARSE_NAMES — Splits or interprets structured task and structure names, supporting the parsing logic needed to align naming conventions between project structures.
  • GET_TASK_NAME_FROM_VERSION — Returns the task name associated with a particular structure version.
  • GET_MAPPED_FIN_TASK_VERSION_ID — Retrieves the version identifier of the financial task mapped to a given source entity.
  • GET_MAPPED_FIN_TASK_ID — Returns the financial task identifier corresponding to a mapped source task.
  • GET_MAPPED_FIN_TASK_NAME — Returns the financial task name for a mapped task.
  • GET_MAPPED_STRUCT_VER_ID — Resolves the mapped project structure version identifier.
  • GET_MAPPED_FIN_TASK_NAME_AMG — Provides the mapped financial task name in the context of associated mapping groups.
  • GET_MAPPED_FIN_TASK_ID_AMG — Returns the mapped financial task identifier within the AMG (associated mapping group) context.
  • GET_MAPPED_WKP_TASK_IDS — Returns the workplan task identifiers that map to a given entity.
  • GET_MAPPED_WKP_TASK_NAMES — Returns the corresponding workplan task names for those mappings.

Tables Accessed

The package reads and writes through APPS synonyms over four documented tables. PA_PROJ_ELEMENTS stores the project element definitions (tasks and structures) that underpin name and identifier lookup. PA_PROJ_ELEMENT_VERSIONS holds the versioned instances of those elements, which is essential for the version-based resolution functions. PA_OBJECT_RELATIONSHIPS records the mapping relationships themselves, forming the basis of the CHECK_* validation routines and the GET_MAPPED_* lookups. DUAL is used for single-row evaluations and simple utility computations. The package thus depends on the core project structure and relationship model rather than on any external interface tables.

Usage Notes

PA_PROJ_STRUC_MAPPING_UTILS is invoked indirectly rather than by end users. The ETRM metadata records that it is referenced by eight other objects, including PA_PROJ_STRUCTURE_PUB, PA_PROJ_STRUC_MAPPING_PUB, PA_TASK_UTILS, and several views such as PA_MAP_WP_TO_FIN_TASKS_V, PA_STRUCTURE_PUB_VERS_V, PA_STRUCTURE_UNPUB_VERS_V, PA_STRUCTURE_VERSIONS_V and PA_STRUCT_TASKS_AMG_V. Consequently the package executes during project structure maintenance, workplan-to-financial-task mapping operations, structure version publication and unpublication, and whenever those views are queried. Custom code should call the public packages (such as PA_PROJ_STRUCTURE_PUB or PA_PROJ_STRUC_MAPPING_PUB) instead of this utility package directly, because its signature is not a committed interface and may change without notice between 12.1.1 and 12.2.2. Its output is primarily consumed as lookup data by the views and public APIs that surface mapping information to Oracle Projects forms and concurrent processes.