Search Results pa_rbs_mapping_rules_u1

Overview

PA.PA_RBS_MAPPING_RULES is a transaction-data table in the Oracle Projects (PA) schema that stores the mapping rules which drive Resource Breakdown Structure (RBS) generation and resource assignment in Oracle E-Business Suite. An RBS defines the hierarchical categorization of resources — people, equipment, materials, and financial elements — used for project planning, budgeting, costing, and reporting. This table associates each rule with a specific RBS structure version and records the type, level placement, and precedence attributes that determine how resources are mapped into the RBS hierarchy.

The table resides in the APPS_TS_TX_DATA tablespace and is classified as VALID in the ETRM 12.2.2 physical schema. It contains 29 documented columns and is flagged with the standard Oracle warning that it is intended for access only through Oracle Applications programs. Based on heuristic Data Vault modeling, this object is best characterized as a standalone satellite — it carries descriptive, version-scoped rule attributes keyed by RULE_ID and ELEMENT_VERSION_ID rather than acting as a hub or a connector between multiple business entities.

Key Information Stored

The surrogate primary key and business-key candidate is RULE_ID, enforced by the unique index PA_RBS_MAPPING_RULES_U1 in the APPS_TS_TX_IDX tablespace. The RBS structure version context is captured by ELEMENT_VERSION_ID, which links the rule to a specific RBS element version. RBS_ELEMENT_ID identifies the RBS element the rule applies to. The rule's hierarchical placement is defined by the fifteen level columns LEVEL1 through LEVEL15, each a VARCHAR2(30) that encodes both the rule type and rule details at that level. MAX_LEVEL records the deepest applicable level, while RULE_FLAG indicates rule status.

Resource-category precedence is governed by four columns: PERSON_RC_PRECEDENCE, EQUIPMENT_RC_PRECEDENCE, MATERIAL_RC_PRECEDENCE, and FIN_ELEM_RC_PRECEDENCE. Standard audit columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The nonunique index PA_RBS_MAPPING_RULES_N1 supports retrieval by ELEMENT_VERSION_ID.

Common Use Cases and Queries

Typical scenarios include auditing which rules are active for a given RBS version, tracing how a resource was mapped into a specific level, and reporting on precedence configuration across resource categories. A representative query retrieves all rules for a version:

• SELECT RULE_ID, ELEMENT_VERSION_ID, RBS_ELEMENT_ID, MAX_LEVEL, RULE_FLAG FROM PA_RBS_MAPPING_RULES WHERE ELEMENT_VERSION_ID = :version_id;
• Join to PA_PROJ_ELEMENT_VERSIONS on ELEMENT_VERSION_ID to resolve version metadata.
• Join to PA_RBS_ELEMENTS on RBS_ELEMENT_ID to obtain the element name and description.
• Filter by RULE_FLAG to isolate active rules for generation logic validation.
• Compare PERSON_RC_PRECEDENCE, EQUIPMENT_RC_PRECEDENCE, MATERIAL_RC_PRECEDENCE, and FIN_ELEM_RC_PRECEDENCE for tie-break analysis.

Related Objects

Foreign key relationships anchor this table to two core PA objects:

• PA.PA_PROJ_ELEMENT_VERSIONS — referenced via ELEMENT_VERSION_ID; supplies the RBS structure version context.
• PA.PA_RBS_ELEMENTS — referenced via RBS_ELEMENT_ID; defines the RBS elements the rules target.
• PA.PA_RBS_MAPPING_RULES_U1 — unique index on RULE_ID, the primary lookup path.
• PA.PA_RBS_MAPPING_RULES_N1 — nonunique index on ELEMENT_VERSION_ID, used for version-scoped reporting.

Given its role, RBS generation and resource assignment programs in the PA schema are the principal consumers of this table through standard Oracle Applications APIs.