Search Results pa_rbs_element_map_u2

Overview

PA.PA_RBS_ELEMENT_MAP is a transaction-data table in the Oracle E-Business Suite Projects (PA) schema. Its purpose is to assign and store numeric identifiers for all Resource Breakdown Structure (RBS) resource type instances that do not carry a native numeric identifier in the source transaction system. Typical examples include revenue categories and named roles, which are descriptive by nature and therefore require a surrogate numeric key before they can participate in RBS processing, costing, budgeting, and reporting.

The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, consistent with high-volume transactional data objects. From a Data Vault modeling perspective, the mined metadata classifies this object as standalone, meaning it does not function as a pure hub, link, or satellite with respect to other tables in the model. A reasonable modeling suggestion is to treat PA_RBS_ELEMENT_MAP as a reference or lookup hub that maps a natural business key (resource type plus resource name) to a surrogate resource identifier. It declares no outbound foreign keys in the heuristic dependency scan; its dependency list indicates it is referenced by the synonym-like object PA_RBS_ELEMENT_MAP#.

Key Information Stored

The table contains eight documented columns, of which three carry the substantive business payload:

• RESOURCE_TYPE_ID (NUMBER(15)) — Identifier for the resource type; the first component of the composite business key.
• RESOURCE_NAME (VARCHAR2(240)) — The name of the resource type instance, such as a revenue category or named role.
• RESOURCE_ID (NUMBER(15)) — Identifier for the numeric resource type instance; this is the surrogate identifier assigned to instances that lack one in the transaction system.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns providing auditability of record creation and maintenance.

The metadata documents two unique indexes that act as business-key candidates. PA_RBS_ELEMENT_MAP_U1 is a unique index on RESOURCE_ID, confirming that the surrogate resource identifier is unique. PA_RBS_ELEMENT_MAP_U2 is a unique index on the composite (RESOURCE_TYPE_ID, RESOURCE_NAME), confirming that a given resource name is unique within its resource type. The user query "pa_rbs_element_map_u2" therefore refers to the composite uniqueness constraint, which is the object that would raise an error if a duplicate resource-name-within-type combination is inserted. Both indexes reside in the APPS_TS_TX_IDX tablespace.

Common Use Cases and Queries

The most common usage is resolving a descriptive RBS element to its numeric identifier for downstream processing. For example, to look up the surrogate identifier for a named role:

SELECT RESOURCE_ID FROM PA.PA_RBS_ELEMENT_MAP WHERE RESOURCE_TYPE_ID = :p_type_id AND RESOURCE_NAME = :p_name;

Reverse lookups support reporting, translating internal identifiers back into human-readable names:

SELECT RESOURCE_NAME FROM PA.PA_RBS_ELEMENT_MAP WHERE RESOURCE_ID = :p_resource_id;

Diagnostic queries that enumerate all mapped instances by resource type are useful during RBS configuration validation. Because PA_RBS_ELEMENT_MAP_U1 and _U2 enforce uniqueness, administrators reviewing mapping completeness can join to PA_RESOURCE_TYPES on RESOURCE_TYPE_ID to confirm that every configured resource type has the expected instances. These patterns are also used in reconciliation reports to detect transaction records that reference identifiers absent from this mapping table.

Related Objects

The documented foreign-key relationship identifies the most significant parent object:

• PA.PA_RESOURCE_TYPES — referenced by PA_RBS_ELEMENT_MAP.RESOURCE_TYPE_ID; the parent definition of RBS resource types.
• PA.PA_RBS_ELEMENT_MAP# — the object listed as referencing PA_RBS_ELEMENT_MAP in the dependency scan.

Other closely associated objects, by functional context rather than documented FK, include the RBS definition tables and the resource-type tables within the PA schema that consume RESOURCE_ID values. However, the ETRM metadata explicitly documents only the PA_RESOURCE_TYPES foreign key and the PA_RBS_ELEMENT_MAP# reference, and this table does not reference any other database object in the provided dependency data.