Results for “pa_rbs_mapping_rules”

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

Overview

PA_RBS_MAPPING_RULES is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the mapping rules created for each Resource Breakdown Structure (RBS) version. An RBS provides a hierarchical classification of project resources — persons, equipment, material, and financial elements — and this table defines how incoming transactions are algorithmically mapped to the appropriate RBS elements. Each rule row belongs to a specific element version, and together the rules drive the automated assignment of resources to the correct node of the RBS hierarchy.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. This suggests treating it as an independent construct rather than a strict hub, link, or satellite. In practice, however, its foreign keys to PA_PROJ_ELEMENT_VERSIONS and PA_RBS_ELEMENTS imply a role resembling a satellite attached to an element-version parent, with each row capturing rule definition attributes at a point in time. The table is owned by the PA schema and is reported as VALID.

Key Information Stored

The physical schema documents 29 columns. The most significant are:

• RULE_ID — the surrogate primary key, enforced by the unique index PA_RBS_MAPPING_RULES_U1. This is the business-key candidate for uniquely identifying a rule.
• ELEMENT_VERSION_ID — foreign key to PA_PROJ_ELEMENT_VERSIONS, tying each rule to a specific RBS version.
• RBS_ELEMENT_ID — foreign key to PA_RBS_ELEMENTS, identifying the target RBS element the rule maps to.
• LEVEL1 through LEVEL15 — fifteen positional columns holding the rule criteria values used to match transactions at each level of the RBS hierarchy.
• MAX_LEVEL — the deepest hierarchy level the rule evaluates, controlling matching depth.
• PERSON_RC_PRECEDENCE, EQUIPMENT_RC_PRECEDENCE, MATERIAL_RC_PRECEDENCE, FIN_ELEM_RC_PRECEDENCE — precedence values governing rule resolution order for each resource class (person, equipment, material, financial element).
• RULE_FLAG — a status or enablement indicator for the rule.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, standard WHO-style tracking.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include retrieving all rules for a given RBS version, reviewing precedence settings, and identifying rules that target a particular RBS element.

To list rules for a specific element version:

• SELECT r.rule_id, r.rbs_element_id, r.max_level, r.rule_flag FROM pa.pa_rbs_mapping_rules r WHERE r.element_version_id = :version_id ORDER BY r.rule_flag DESC;

To inspect precedence values by resource class for a target element:

• SELECT rbs_element_id, person_rc_precedence, equipment_rc_precedence, material_rc_precedence, fin_elem_rc_precedence FROM pa.pa_rbs_mapping_rules WHERE rbs_element_id = :element_id;

To count active rules per element version and audit recent changes:

• SELECT element_version_id, COUNT(*) FROM pa.pa_rbs_mapping_rules WHERE rule_flag = 'Y' GROUP BY element_version_id;
• SELECT rule_id, last_updated_by, last_update_date FROM pa.pa_rbs_mapping_rules WHERE last_update_date > SYSDATE - 30;

These queries support configuration audits, migration validation, and troubleshooting of resource mapping behavior.

Related Objects

The following objects are most significant to PA_RBS_MAPPING_RULES, based on documented foreign keys and typical Projects module dependencies:

• PA_RBS_ELEMENTS — joined on RBS_ELEMENT_ID; defines the target RBS element for each rule.
• PA_PROJ_ELEMENT_VERSIONS — joined on ELEMENT_VERSION_ID; represents the versioned element structure owning the rules.
• PA_RBS_VERSIONS / PA_RBS_STRUCTURES — provide the RBS version and hierarchy context for the element versions referenced.
• PA_PROJ_ELEMENTS — supplies the underlying element definitions that RBS elements classify.
• PA_TRANSACTION_MAPPING / PA_RESOURCE_MAPPING — downstream processes that consume mapping rules to assign transactions to RBS nodes.
• PA_PROJECTS and related resource tables — provide the transaction and resource context in which these mapping rules are applied at runtime.