Search Results pa_resource_maps




Overview
Explore in AI Chat

Overview

The PA_RESOURCE_MAPS table is a core transactional table within the Oracle E-Business Suite Projects (PA) module, specifically in versions 12.1.1 and 12.2.2. Its primary function is to store the detailed mapping rules that link a member of a resource list to a specific combination of resource transaction attributes. This mapping is a critical component of the Project Resource Management functionality, enabling the system to automatically determine the correct resource—be it an employee, job, vendor, or non-labor item—to charge when a transaction is entered, based on attributes like expenditure type, category, event type, and organization. It acts as the execution layer for resource list assignments, translating high-level assignment rules into precise, actionable mappings.

Key Information Stored

The table stores the linkage between a resource list member and the transaction context. Key columns include the foreign key RESOURCE_LIST_ASSIGNMENT_ID, which ties the map to its parent assignment rule. The RESOURCE_LIST_MEMBER_ID identifies the specific member within a resource list. Crucially, the table holds attribute columns that define the transaction context for the mapping, such as EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, EVENT_TYPE, ORGANIZATION_ID, and JOB_ID. The resulting target resource is identified by either RESOURCE_ID (for labor), VENDOR_ID, or NON_LABOR_RESOURCE. The SYSTEM_LINKAGE_FUNCTION column links to integration points with other modules like Purchasing or General Ledger.

Common Use Cases and Queries

This table is central to transaction processing and audit reporting. A common operational use case is troubleshooting why a particular resource was automatically selected for a project expenditure item. Administrators query this table to validate and audit mapping rules. A typical diagnostic SQL pattern joins PA_RESOURCE_MAPS to PA_RESOURCE_LIST_ASSIGNMENTS and PA_RESOURCE_LIST_MEMBERS to see all active mappings for a given project or resource list. For reporting, queries often aggregate mappings by expenditure type or organization to analyze coverage and identify gaps in resource assignment rules. Sample query:

  • SELECT prm.expenditure_type, prm.resource_id, prl.name resource_list_name FROM pa_resource_maps prm, pa_resource_lists_all_bg prl WHERE prm.resource_list_id = prl.resource_list_id AND prm.organization_id = 100;

Related Objects

PA_RESOURCE_MAPS has extensive foreign key relationships, underscoring its integrative role. Key documented dependencies include: