Results for “resource_type_id”

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

Overview

PA_RBS_ELEMENT_MAP is a reference and mapping table in the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the numeric identifiers assigned to all RBS (Resource Breakdown Structure) resource type instances that do not already carry a numeric identifier in the source transaction system. Typical examples include revenue categories and named roles, which are captured as descriptive text in operational tables but must be resolved to a stable numeric key before they can participate in the RBS framework used for project resource planning, budgeting, and reporting.

The table therefore serves as a surrogate-key registry for resource classification values. When Oracle Projects encounters an RBS resource type instance that lacks a native numeric identifier, this table supplies one, ensuring that RBS hierarchies and resource assignments remain internally consistent regardless of whether the originating attribute is a coded value or a free-text description.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. From a modeling perspective, this suggests the table functions as an independent reference or mapping structure rather than a hub, link, or satellite within a Data Vault architecture. Its single documented foreign key to PA_RESOURCE_TYPES places it adjacent to the resource type dimension, but no downstream dependencies are recorded, reinforcing its self-contained nature.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

• RESOURCE_TYPE_ID — Foreign key to PA_RESOURCE_TYPES, identifying the RBS resource type to which the mapped element belongs.
• RESOURCE_NAME — The descriptive name of the resource type instance, such as a revenue category or named role.
• RESOURCE_ID — The numeric surrogate identifier generated for the resource instance. This column is the single-column unique key candidate, PA_RBS_ELEMENT_MAP_U1.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the mapping row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and the login under which it occurred.

The second unique index, PA_RBS_ELEMENT_MAP_U2, spans RESOURCE_TYPE_ID and RESOURCE_NAME. This is the primary business-key candidate: it enforces that within a given resource type, each resource name is mapped to exactly one numeric RESOURCE_ID. The distinction between the surrogate key (RESOURCE_ID) and the composite business key (RESOURCE_TYPE_ID plus RESOURCE_NAME) is central to understanding the table's purpose.

Common Use Cases and Queries

The principal use case is resolving descriptive RBS resource values to numeric identifiers for use in planning and budgeting engines, RBS hierarchy maintenance, and reporting joins where a numeric key is required. A typical lookup translates a revenue category or named role into its RESOURCE_ID:

• SELECT RESOURCE_ID, RESOURCE_NAME FROM PA.PA_RBS_ELEMENT_MAP WHERE RESOURCE_TYPE_ID = :p_resource_type_id AND RESOURCE_NAME = :p_name;
• Reverse resolution from a numeric identifier back to the descriptive label, used when rendering RBS assignment reports.
• Validation queries that detect duplicate or orphaned mappings within a resource type, supporting data-cleanup efforts during implementation or migration.
• Reconciliation reporting between transaction systems that store resource instances descriptively and the RBS structures that consume numeric keys.

Because the audit columns are present, reports can also identify recently created or modified mappings, which is useful during configuration audits and period-close activities.

Related Objects

The documented foreign-key relationship ties this table directly to the resource type dimension. Other objects that reference or depend on this table in practice include:

• PA_RESOURCE_TYPES — joined via RESOURCE_TYPE_ID; the parent definition of each RBS resource type.
• PA_RBS_ELEMENTS — the element definitions whose resource instances depend on the numeric identifiers registered here.
• PA_RESOURCE_ASSIGNMENTS — project resource assignments that resolve resource instances through the numeric keys in this table.
• PA_BUDGET_VERSIONS and PA_BUDGET_LINES — budgeting objects that consume RBS resource identifiers for plan line entries.
• PA_PROJECTS — the project context under which RBS-based resource planning is performed.

Together these objects form the RBS resource resolution path, with PA_RBS_ELEMENT_MAP acting as the bridge between descriptive resource instances and the numeric identifiers required by Oracle Projects planning and reporting logic.