Results for “rbs_element_id”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_RBS_ELEMENTS_V is a valid, read-only view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2, delivered as part of the PA (Projects) product family. It exposes the definition of a Resource Breakdown Structure (RBS) — the hierarchical classification used to categorize resources such as people, expenditure categories, and organizations for planning, budgeting, and cost collection. The view presents element information together with the parent-child relationship for all elements in an RBS, making it the primary reference for reporting on RBS hierarchies without writing recursive queries against the underlying base table.

Its role is predominantly reporting and integration-facing. Because the hierarchy level and an indented display name are pre-computed in the view definition, external reports, Oracle Business Intelligence queries, and interfaces can consume RBS structures in a single SELECT, avoiding manual hierarchical traversal. The view is metadata-time (not date-tracked) and reflects the current definition of the underlying element records.

Underlying Base Objects

The view is defined over two documented base objects:

  • PA_RBS_ELEMENTS (SYNONYM) — the parent table holding each RBS element, its identifier, version, resource type, source, level, parent pointer, and the RULE_FLAG.
  • PA_RBS_ELEMENT_NAMES_TL (SYNONYM) — the translatable names table supplying the resource name by language.

The join is PA_RBS_ELEMENTS.RBS_ELEMENT_NAME_ID = PA_RBS_ELEMENT_NAMES_TL.RBS_ELEMENT_NAME_ID (+), an outer join so elements without a translated name are still returned. The view is also filtered by LANGUAGE = USERENV('LANG'), so it automatically returns names in the session language, and by USER_CREATED_FLAG = 'N', which restricts the result to seeded/system-delivered elements rather than user-created ones.

Key Columns

  • RBS_ELEMENT_ID — Unique identifier of the RBS element; the join key to other RBS-related tables.
  • RESOURCE_NAME — The element name, prefixed with a padding string of spaces equal to the element's level (LPAD(' ', RBS_LEVEL) || RESOURCE_NAME), producing a visually indented hierarchy label suitable for display.
  • RBS_VERSION_ID — The RBS version to which the element belongs.
  • RESOURCE_TYPE_ID — Identifies the resource type of the element (for example, a role or expenditure type category reference).
  • RESOURCE_SOURCE_ID — Identifies the source of the resource (system vs. user-defined), complementing the USER_CREATED_FLAG = 'N' filter in the view.
  • RBS_LEVEL — The depth of the element within the RBS hierarchy; drives the indentation and the top-level (root) identification.
  • PARENT_ELEMENT_ID — Points to the parent element's RBS_ELEMENT_ID; NULL for root elements. This column expresses the parent-child relationship.
  • RULE_FLAG — A flag indicating a rule characteristic of the element, exposed directly so reports can distinguish elements governed by a rule condition.

Common Use Cases and Queries

A frequent requirement is to list all elements of a given RBS version in hierarchy order for a report or LOV:

SELECT rbs_element_id, resource_name, rbs_level, parent_element_id, rule_flag
FROM   apps.pa_rbs_elements_v
WHERE  rbs_version_id = :p_version_id
ORDER  BY resource_name;

Filtering on the flag column — often the reason users search for "rule_flag" — selects only elements that carry a rule:

SELECT rbs_element_id, resource_name, rbs_level
FROM   apps.pa_rbs_elements_v
WHERE  rbs_version_id = :p_version_id
AND    rule_flag = 'Y';

To find immediate children of a specific element, join on the parent pointer:

SELECT child.rbs_element_id, child.resource_name
FROM   apps.pa_rbs_elements_v child
WHERE  child.parent_element_id = :p_element_id;

Because the view is restricted to USER_CREATED_FLAG = 'N', it should be treated as a source of seeded RBS elements; user-created elements are not returned and must be sourced from the base table. When using the indented RESOURCE_NAME in fixed-format output, note that leading spaces are significant and may affect ordering and alignment.