Results for “rg_xbrl_map_elements”

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

Overview

RG_XBRL_MAP_ELEMENTS is a table in the RG (Application Report Generator) product module of Oracle E-Business Suite, residing in the RG schema. Its documented purpose is to record elements mapped to taxonomies, forming the association layer between XBRL taxonomy definitions and the individual elements they contain. In the context of Oracle EBS 12.1.1 and 12.2.2, this table supports the generation of XBRL (Extensible Business Reporting Language) output, which is used for regulatory and financial reporting formats such as those required by various statutory bodies.

The table carries a heuristic Data Vault classification of link, which is a modeling suggestion rather than an enforced characteristic. This classification is appropriate because the table resolves a many-to-many relationship between two parent entities — taxonomies and elements — through a composite key. Its role is purely associative: it does not function as a hub of business entities nor as a satellite capturing descriptive attributes over time, although it does carry standard EBS audit columns.

Key Information Stored

The table comprises eight documented columns. The most significant are the two that form both the primary key and the unique business-key candidate:

• TAXONOMY_ID — Identifies the taxonomy to which an element is mapped. Part of the composite primary key (RG_XBRL_MAP_ELEMENTS_PK) and of the unique index RG_XBRL_MAP_ELEMENTS_U1. Foreign key to RG_XBRL_TAXONOMIES.
• ELEMENT_ID — Identifies the XBRL element being mapped. The second component of the composite primary key and unique index. Foreign key to RG_XBRL_ELEMENTS.
• ENABLED_FLAG — Controls whether the mapping is active, allowing a taxonomy-element association to be retained but excluded from processing or reporting.
• CREATION_DATE — Timestamp when the mapping row was created.
• CREATED_BY — User identifier responsible for creating the row.
• LAST_UPDATE_DATE — Timestamp of the most recent modification.
• LAST_UPDATED_BY — User identifier of the most recent modification.
• LAST_UPDATE_LOGIN — Login/session identifier associated with the most recent update.

The composite primary key (TAXONOMY_ID, ELEMENT_ID) means there is no separate single-column surrogate key; the business identity is the pairing of taxonomy and element. The unique index RG_XBRL_MAP_ELEMENTS_U1 on the same two columns reinforces this as the natural business key and prevents duplicate mappings. The remaining six columns are standard Oracle EBS audit columns, providing change-tracking and accountability information rather than domain data.

Common Use Cases and Queries

Typical use cases center on enumerating which elements belong to a taxonomy, verifying that required elements are present before XBRL generation, and identifying enabled versus disabled mappings.

Listing enabled elements for a specific taxonomy:

SELECT m.taxonomy_id, m.element_id, m.enabled_flag
FROM   rg.rg_xbrl_map_elements m
WHERE  m.taxonomy_id = :p_taxonomy_id
AND    m.enabled_flag = 'Y';

Resolving the element and taxonomy names through the parent tables:

SELECT t.taxonomy_name, e.element_name
FROM   rg.rg_xbrl_map_elements m,
       rg.rg_xbrl_taxonomies  t,
       rg.rg_xbrl_elements    e
WHERE  m.taxonomy_id = t.taxonomy_id
AND    m.element_id  = e.element_id;

Detecting orphan or disabled mappings, and auditing recent changes, are also common reporting patterns. Because the table is small and associative, queries are typically join-driven and inexpensive.

Related Objects

The table participates in two documented foreign-key relationships and depends on the following objects:

• RG_XBRL_TAXONOMIES — Parent of TAXONOMY_ID; supplies taxonomy definitions.
• RG_XBRL_ELEMENTS — Parent of ELEMENT_ID; supplies element definitions.
• RG_XBRL_MAP_ELEMENTS_PK — Primary key constraint on (TAXONOMY_ID, ELEMENT_ID).
• RG_XBRL_MAP_ELEMENTS_U1 — Unique index on (TAXONOMY_ID, ELEMENT_ID), documenting the business key.
• RG schema report and XBRL generation logic that consumes these mappings as an input to rendering generated reports.

These objects should be treated as the authoritative dependencies for this table when assessing impact analysis or extension work.