Results for “rg_xbrl_elements_u1”

10 results




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

Overview

RG.RG_XBRL_ELEMENTS is an Oracle E-Business Suite table owned by the RG schema, delivered as part of the ETRM (Enterprise Tax, Regulatory, and Reporting Management) module, also marketed as Oracle Financial Services Regulatory Reporting. It stores the individual taxonomy elements — concepts, line items, and structural nodes — that constitute an XBRL taxonomy used for regulatory and financial reporting in Oracle EBS 12.1.1 and 12.2.2. Each row represents a single element within a taxonomy hierarchy, carrying its identifier, label, type, group, and hierarchical positioning metadata. The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and its indexes reside in APPS_TS_TX_IDX, consistent with standard Oracle Applications transaction data conventions.

From a Data Vault modeling perspective, the mined relationship data classifies this object as hub-leaning. That is a heuristic suggestion: RG_XBRL_ELEMENTS behaves primarily as a hub, anchored by the unique business key ELEMENT_ID, with descriptive attributes (identifier, name, type, label, description) that could also be modeled as a satellite. This dual nature reflects the table's role as both a durable identity anchor for taxonomy concepts and a carrier of slowly changing descriptive metadata.

Key Information Stored

The table is defined with 18 columns. The most operationally significant are:

Two unique indexes exist: RG_XBRL_ELEMENTS_U1 on ELEMENT_ID (the surrogate primary key) and RG_XBRL_ELEMENTS_U2 on (TAXONOMY_ID, ELEMENT_IDENTIFIER), which enforces the natural business key. The U2 index is the reason a search for "rg_xbrl_elements_u2" surfaces this object; it guarantees that no two elements within the same taxonomy share an identifier.

Common Use Cases and Queries

Typical uses include listing elements within a taxonomy, resolving parent-child hierarchy, and mapping reporting lines to taxonomy concepts.

  • Retrieve all elements for a taxonomy:
    SELECT element_id, element_identifier, element_name
    FROM   rg.rg_xbrl_elements
    WHERE  taxonomy_id = :taxonomy_id
    ORDER BY hierarchy_level, element_identifier;
  • Traverse the hierarchy from a parent element:
    SELECT element_id, element_identifier, hierarchy_level
    FROM   rg.rg_xbrl_elements
    WHERE  parent_id = :parent_id;
  • Locate a concept by its natural key:
    SELECT element_id, element_name, element_type
    FROM   rg.rg_xbrl_elements
    WHERE  taxonomy_id = :taxonomy_id
    AND    element_identifier = :identifier;

Because this is an Oracle Internal Use Only object, queries should be read-only and not used to insert or update data outside standard Oracle Applications programs.

Related Objects

  • RG.RG_XBRL_TAXONOMIES — parent taxonomy; joined via RG_XBRL_ELEMENTS.TAXONOMY_ID = RG_XBRL_TAXONOMIES.TAXONOMY_ID.
  • RG.RG_REPORT_AXES — references RG_XBRL_ELEMENTS.ELEMENT_ID, linking reporting axes to taxonomy elements.
  • RG.RG_XBRL_MAP_ELEMENTS — references RG_XBRL_ELEMENTS.ELEMENT_ID, mapping internal accounts or lines to taxonomy elements.

Together these relationships position RG_XBRL_ELEMENTS as the central hub of the ETRM XBRL taxonomy model, connecting taxonomies to reporting axes and mapping definitions.