Search Results element_label

Overview

RG_XBRL_MAP_V is a reporting view owned by the APPS schema within the Application Report Generator (RG) product of Oracle E-Business Suite. It exposes the relationship between XBRL (eXtensible Business Reporting Language) taxonomy elements and the mapping records that associate those elements with reportable data. In EBS 12.1.1 and 12.2.2, the RG module provides the infrastructure used by Oracle Financials and related products to generate XBRL-tagged output, and this view serves as the consolidated read interface for taxonomy and element mapping metadata.

The view joins three underlying RG XBRL objects and filters mapping rows to those that are actively enabled. Because it resolves the taxonomy URL, alias, element label, and element name into a single rowset, it is the primary source for validation, troubleshooting, and reconciliation queries performed by implementers and DBAs when investigating XBRL tagging behavior.

Underlying Base Objects

The view is defined over three synonym-referenced base objects owned by APPS:

• RG_XBRL_TAXONOMIES — holds the taxonomy definitions, including alias, URL, and identifier.
• RG_XBRL_ELEMENTS — holds the individual XBRL elements belonging to each taxonomy, including element name, label, and taxonomy association.
• RG_XBRL_MAP_ELEMENTS — holds the mapping records that link an element to a taxonomy, carrying the ENABLED_FLAG.

Joins are established on MAP.ELEMENT_ID = ELM.ELEMENT_ID, ELM.TAXONOMY_ID = TAX.TAXONOMY_ID, and the filter MAP.ENABLED_FLAG = 'Y'. Only rows whose mapping is enabled therefore survive into the view, so disabled mappings are invisible to consumers of RG_XBRL_MAP_V.

Key Columns

The view returns the following columns, several of which are aliased from their underlying table names:

• SOURCE_TAX_ALIAS — the alias of the taxonomy as recorded in RG_XBRL_TAXONOMIES.
• SOURCE_TAX_URL — the taxonomy URL, identifying the published taxonomy location.
• SOURCE_TAXONOMY_ID — the taxonomy identifier used for the element association join.
• ELEMENT_LABEL — the descriptive element label; the view text applies NVL(ELEMENT_LABEL, ELEMENT_NAME), so this column carries the label when present and falls back to the element name otherwise.
• ELEMENT_NAME — the technical element name from RG_XBRL_ELEMENTS, also projected separately in its raw form.
• ELEMENT_ID — the unique element identifier, inherited from the mapping record.
• MAP_TAXONOMY_ID — the taxonomy identifier carried on the mapping record, permitting comparison against SOURCE_TAXONOMY_ID.

The interplay between ELEMENT_LABEL and ELEMENT_NAME is significant, because the NVL expression means an element without a populated label is reported under its technical name, which can affect both display and downstream comparison logic.

Common Use Cases and Queries

Typical scenarios include auditing which elements are actively mapped for a given taxonomy, confirming that label resolution behaves as expected, and diagnosing XBRL generation failures caused by disabled mappings. Because only enabled mappings are returned, the view is suited to positive-confirmation reporting rather than full mapping inventories.

Listing all enabled elements for a taxonomy alias:

SELECT source_tax_alias, element_name, element_label, element_id
FROM   apps.rg_xbrl_map_v
WHERE  source_tax_alias = :alias
ORDER BY element_name;

Detecting elements reported under their technical name because no label exists:

SELECT element_name, element_id
FROM   apps.rg_xbrl_map_v
WHERE  element_label = element_name;

Verifying that the source and mapping taxonomy identifiers agree:

SELECT element_id, source_taxonomy_id, map_taxonomy_id
FROM   apps.rg_xbrl_map_v
WHERE  source_taxonomy_id <> map_taxonomy_id;

Comparisons against the base tables are required whenever disabled mappings must also be examined, since RG_XBRL_MAP_ELEMENTS retains rows that RG_XBRL_MAP_V deliberately excludes.