Results for “user_created_flag”

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

Overview

PA_RBS_ELEMENTS is a core Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores Resource Breakdown Structure (RBS) element information along with the parent-child relationship between those elements. An RBS is the hierarchical classification of resources — people, roles, jobs, organizations, expenditure types, revenue categories, inventory items, and non-labor resources — used to plan, budget, cost, and report project activity. Each row represents one node in an RBS hierarchy for a specific RBS version, and the PARENT_ELEMENT_ID and RBS_LEVEL columns together establish the tree structure. The table is owned by the PA schema and is documented as VALID, with 45 columns and a single unique index, PA_RBS_ELEMENTS_U1, on RBS_ELEMENT_ID.

From a dimensional modeling perspective, the mined foreign-key structure classifies this object as hub-leaning. In Data Vault terms, PA_RBS_ELEMENTS behaves like a hub that anchors the RBS element identity, with its descriptive attributes and parent lookup acting as satellite and self-referencing link content. This classification is a heuristic suggestion derived from FK topology, not a documented design mandate.

Key Information Stored

The primary key column is RBS_ELEMENT_ID, which is also the sole business-key candidate via unique index PA_RBS_ELEMENTS_U1. The most significant columns are:

• RBS_ELEMENT_ID — surrogate identifier for each RBS element; primary key and FK target for dependent tables.
• RBS_ELEMENT_NAME_ID — FK to PA_RBS_ELEMENT_NAMES_B, providing the display name of the element.
• RBS_VERSION_ID — FK to PA_RBS_VERSIONS_B, placing the element within a specific RBS version.
• PARENT_ELEMENT_ID — self-referencing FK that drives the hierarchy.
• RBS_LEVEL and LEVEL_CODE — depth and coded level of the node.
• RESOURCE_TYPE_ID — FK to PA_RES_TYPES_B, controlling which resource dimension applies (person, job, organization, expenditure type, and so on).
• PERSON_ID, JOB_ID, ORGANIZATION_ID, EXPENDITURE_TYPE_ID, REVENUE_CATEGORY_ID, INVENTORY_ITEM_ID, ROLE_ID, SUPPLIER_ID — resource-specific identifiers populated according to RESOURCE_TYPE_ID.
• OUTLINE_NUMBER and ORDER_NUMBER — sequencing of elements in outlines and reports.
• RBS_LEVEL, CONNECT_PATH, and LEAF_NODE — hierarchy navigation, path encoding, and terminal-node flag.
• ENABLE_FLAG, ELEMENT_IDENTIFIER, and COST_CODE — status, human-readable identifier, and cost classification.
• USER_DEFINED_CUSTOM1_ID through USER_DEFINED_CUSTOM5_ID — extensibility attributes.
• Audit columns such as LAST_UPDATE_DATE, CREATED_BY, and RECORD_VERSION_NUMBER.

Common Use Cases and Queries

Typical reporting scenarios include reconstructing the full RBS tree for a version, listing all elements by resource type, and joining elements to resource assignments for cost and effort reporting. A sample hierarchy query:

• SELECT RBS_ELEMENT_ID, PARENT_ELEMENT_ID, RBS_LEVEL, RESOURCE_TYPE_ID FROM PA_RBS_ELEMENTS WHERE RBS_VERSION_ID = :version_id AND ENABLE_FLAG = 'Y' ORDER BY RBS_LEVEL, ORDER_NUMBER;
• Join to names: SELECT e.RBS_ELEMENT_ID, n.NAME FROM PA_RBS_ELEMENTS e, PA_RBS_ELEMENT_NAMES_B n WHERE e.RBS_ELEMENT_NAME_ID = n.RBS_ELEMENT_NAME_ID;
• Resource utilization: join PA_RESOURCE_ASSIGNMENTS.RBS_ELEMENT_ID to PA_RBS_ELEMENTS to aggregate assigned resources per element.
• Hierarchy traversal: use CONNECT_PATH or recursive START WITH ... CONNECT BY PRIOR RBS_ELEMENT_ID = PARENT_ELEMENT_ID for level-based rollups.

Related Objects

The most significant related objects, based on documented FK relationships, are:

• PA_RBS_VERSIONS_B — joined on PA_RBS_ELEMENTS.RBS_VERSION_ID; defines the RBS version context.
• PA_RBS_ELEMENT_NAMES_B — joined on RBS_ELEMENT_NAME_ID; supplies element names.
• PA_RES_TYPES_B — joined on RESOURCE_TYPE_ID; defines the resource type dimension.
• PA_RESOURCE_ASSIGNMENTS — references PA_RBS_ELEMENTS.RBS_ELEMENT_ID; links assignments to RBS elements.
• PA_RBS_DENORM — references RBS_ELEMENT_ID via SUB_ID; denormalized RBS structure for reporting.
• PJI_RBS_DENORM — references RBS_ELEMENT_ID via SUP_ID and SUB_ID for project intelligence denormalization.
• PA_RBS_MAPPING_RULES — references RBS_ELEMENT_ID; drives RBS mapping logic.
• PJI_FP_XBS_ACCUM_F and PJI_FP_AGGR_PJP0/PJP1 — fact-style accumulation tables referencing RBS_ELEMENT_ID for forecasting and aggregation.