Results for “pa_resource_maps”

50+ results




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

Overview

PA_RESOURCE_MAPS is a Projects (PA) module table that defines the mapping between an individual resource list member and a specific combination of resource transaction attributes. In Oracle EBS, resource lists are used to constrain and qualify the resources that may be charged to a project, and PA_RESOURCE_MAPS supplies the attribute-level detail that resolves a member into concrete transaction qualifiers such as person, job, organization, vendor, expenditure type, expenditure category, revenue category, event type, and non-labor resource. The table is owned by the PA schema and is valid in both the 12.1.1 and 12.2.2 releases, with the documented physical schema carrying 25 columns.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure identifies this object as a link. This is a reasonable modeling suggestion: the table does not act as a descriptive hub in its own right, but rather associates a resource list assignment with a member and a set of referenced attribute entities. The primary key, PA_RESOURCE_MAPS_PK, is defined on RESOURCE_LIST_ASSIGNMENT_ID.

Key Information Stored

The most significant columns fall into three functional groups — identity keys, resource qualifiers, and audit columns.

Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present. The documented unique business key is the surrogate PK column; no alternate unique index is reported in the metadata.

Common Use Cases and Queries

Typical uses include reporting which resource list members map to which expenditure types or categories, auditing the attribute combinations allowed on a resource list, and troubleshooting why a transaction was accepted or rejected against a resource list. A representative query joins the mapping to its parent assignment and list:

  • SELECT m.RESOURCE_LIST_ID, m.RESOURCE_LIST_MEMBER_ID, m.PERSON_ID, m.JOB_ID, m.ORGANIZATION_ID, m.EXPENDITURE_TYPE, m.EXPENDITURE_CATEGORY FROM PA_RESOURCE_MAPS m WHERE m.RESOURCE_LIST_ID = :list_id;
  • SELECT m.* FROM PA_RESOURCE_MAPS m, PA_RESOURCE_LIST_MEMBERS mem WHERE m.RESOURCE_LIST_MEMBER_ID = mem.RESOURCE_LIST_MEMBER_ID AND m.EXPENDITURE_TYPE = :etype;
  • SELECT m.RESOURCE_LIST_ASSIGNMENT_ID, m.RESOURCE_ID, m.JOB_ID, m.ORGANIZATION_ID FROM PA_RESOURCE_MAPS m WHERE m.VENDOR_ID = :vendor_id;

These patterns support resource list validation, expenditure qualification analysis, and integration extracts feeding project costing and billing.

Related Objects

PA_RESOURCE_MAPS is densely linked to surrounding Projects and HR/Procurement entities through its foreign keys. The most significant related objects are:

  • PA_RESOURCE_LIST_MEMBERS — via RESOURCE_LIST_MEMBER_ID; the member definition this mapping qualifies.
  • PA_RESOURCE_LIST_ASSIGNMENTS — via RESOURCE_LIST_ASSIGNMENT_ID; the parent assignment and PK reference.
  • PA_RESOURCE_LISTS_ALL_BG — via RESOURCE_LIST_ID; the resource list header.
  • PA_RESOURCES — via RESOURCE_ID; the resource definition.
  • PA_EXPENDITURE_TYPES and PA_EXPENDITURE_CATEGORIES — via EXPENDITURE_TYPE and EXPENDITURE_CATEGORY.
  • PA_EVENT_TYPES and PA_NON_LABOR_RESOURCES — via EVENT_TYPE and NON_LABOR_RESOURCE.
  • PA_SYSTEM_LINKAGES — via SYSTEM_LINKAGE_FUNCTION.
  • PER_JOBS, HR_ALL_ORGANIZATION_UNITS, and PO_VENDORS — via JOB_ID, ORGANIZATION_ID, and VENDOR_ID.