Search Results pa_res_list_map_tmp1




Overview
Explore in AI Chat

Overview

The APPS.PA_RESOURCE_MAPPING package body is a core Oracle Projects (PA) utility responsible for resolving how planning resources, resource lists, and resource formats map to one another within the Oracle E-Business Suite. In Oracle EBS 12.1.1 and 12.2.2, Projects planning and budgeting depend on a flexible framework in which resource lists, resource formats, and precedence rules determine which planning resources are available and how they are presented on planning entry and reporting screens. PA_RESOURCE_MAPPING serves as the engine that evaluates these inputs and returns the resolved mapping used by downstream planning and resource-management flows.

The object is classified as OTHER in the ETRM documentation, indicating it is an internal supporting package rather than a published business API. It is a VALID package body owned by APPS and is referenced by five other packages, while itself depending extensively on foundational EBS APIs such as FND_API, FND_MSG_PUB, FND_PROFILE, and FND_INSTALLATION, as well as numerous PA planning entities.

Key Procedures and Functions

  • MAP_RESOURCE_LIST — The primary entry point for resolving a resource list into its mapped planning resources. It evaluates the applicable resource list definition and produces the mapped result, writing intermediate working data into temporary tables such as PA_RES_LIST_MAP_TMP1 and PA_RES_LIST_MAP_TMP3.
  • GET_FORMAT_PRECEDENCE — Determines the precedence order that governs how resource formats and precedence rules are applied when more than one format or list qualifies for a given planning context. It draws on PA_ACT_PRL_PRECEDENCE, PA_PLAN_RL_FORMATS, and related format definition tables.

Both routines are internal helpers; parameter lists are not documented in the ETRM metadata and should not be assumed. The temporary tables PA_RES_LIST_MAP_TMP1 and PA_RES_LIST_MAP_TMP3 — the first of which is the object name in the user's search — act as staging structures populated and consumed during this mapping process.

Tables Accessed

The package reads and writes a defined set of tables, accessed through APPS synonyms:

  • PA_RESOURCE_LISTS_ALL_BG and PA_RES_FORMATS_B — resource list and resource format definitions that form the basis of any mapping.
  • PA_PLAN_RL_FORMATS, PA_PLAN_RES_DEFAULTS, and PA_ACT_PRL_PRECEDENCE — planning-level format, default, and precedence rules that determine the resolved outcome.
  • PA_RESOURCE_CLASSES_B and PA_EXPENDITURE_TYPES — resource classification and expenditure type context.
  • PA_EVENT_TYPES — event type context used in mapping decisions.
  • MTL_ITEM_CATEGORIES — item category context where inventory items participate in resource mappings.
  • PA_RES_LIST_MAP_TMP1 and PA_RES_LIST_MAP_TMP3 — temporary staging tables holding intermediate mapping results.
  • DUAL and PLITBLM — utility constructs, including PL/SQL table (index-by table) support.

Usage Notes

PA_RESOURCE_MAPPING is not intended for direct invocation by end users or by typical custom integrations. It is a supporting package invoked internally by the Projects planning and resource-management stack, including PA_PLANNING_RESOURCE_PVT and PA_RESOURCE_PREC_PUB, both of which are listed as dependencies. Because it is referenced by five other packages, changes to its behavior can propagate broadly within the PA planning module.

In practice, the package is triggered when planning resource entry, resource list administration, or format precedence resolution requires the system to determine which resources map to a given context. The temporary tables PA_RES_LIST_MAP_TMP1 and PA_RES_LIST_MAP_TMP3 hold what are effectively session- or process-scoped working sets, so any monitoring or troubleshooting should account for their transient nature. Custom code should call the higher-level published APIs (such as PA_PLANNING_RESOURCE_PVT) rather than this package directly, and should never depend on the structure or contents of the temporary mapping tables.