Search Results source_taxonomy_id

Overview

The view APPS.RG_XBRL_MAP_V is a supplementary database view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, residing in the APPS schema with a status of VALID. Its design purpose, as documented in the ETRM metadata, is to simplify forms coding, acting as a database abstraction layer to streamline the development and maintenance of Oracle Forms interfaces related to XBRL (eXtensible Business Reporting Language) functionality. Specifically, this view serves as a mapping bridge, correlating taxonomy elements with their associated taxonomies. It exposes information critical for the generation of regulatory and financial reports that adhere to XBRL standards.

The view is central to the EBS reporting and integration infrastructure, particularly for modules requiring taxonomy mapping and element resolution, such as financial consolidation and statutory reporting. It inherits its definition from the underlying application dictionary design data (FND Design Data: RG.RG_XBRL_MAP_V), ensuring its structure is maintained across patch levels. The metadata carries a warning that Oracle does not recommend direct querying or alteration of the view's data for operational transactions, as its structure may change dramatically in subsequent releases. Consequently, its primary role is as a read-only reference for forms and concurrent programs, not as a transactional interface.

Underlying Base Objects

The view is defined over three base objects within the APPS schema, which are presented as synonyms in the documented dependency chain. These base objects are RG_XBRL_ELEMENTS, RG_XBRL_MAP_ELEMENTS, and RG_XBRL_TAXONOMIES. These tables constitute the relational foundation for the XBRL taxonomy and element mapping data model.

Functionally, the join connects three distinct data domains. The RG_XBRL_TAXONOMIES table supplies the taxonomy-level attributes, including the alias, URL, and the unique taxonomy identifier. The RG_XBRL_ELEMENTS table provides the element-level details, such as the element label, name, and its defining identifier. Bridging these two is the RG_XBRL_MAP_ELEMENTS table, which establishes the many-to-many or one-to-many relationships that map specific elements to their parent or related taxonomies, represented in the view by the MAP_TAXONOMY_ID column. This structure allows the view to present a consolidated picture of which element belongs to which taxonomy and under what mapping context.

Key Columns

The view exposes seven columns that collectively define the mapping metadata. These columns are:

• SOURCE_TAX_ALIAS (VARCHAR2 240): The alias of the source taxonomy, typically including its version identifier. This provides a human-readable reference for the taxonomy.
• SOURCE_TAX_URL (VARCHAR2 240): The Taxonomy Universal Resource Locator. This column stores the canonical URL that uniquely identifies the taxonomy, which is critical for external validation and integration with regulatory filing systems.
• SOURCE_TAXONOMY_ID (NUMBER 15): The primary key defining the source taxonomy. This is the unique internal identifier for the taxonomy record.
• ELEMENT_LABEL (VARCHAR2 240): The label assigned to the taxonomy element, used for display purposes in forms and reports.
• ELEMENT_NAME (VARCHAR2 240): The formal name of the taxonomy element.
• ELEMENT_ID (NUMBER 15): The defining column (unique identifier) for the element within the source taxonomy.
• MAP_TAXONOMY_ID (NUMBER 15): The taxonomy defining column, representing the taxonomy to which the element is mapped or associated.

Collectively, these columns allow a user to retrieve the full context of a taxonomy mapping: the source taxonomy's identity and location, the element's identity and label, and the target taxonomy context for the mapping.

Common Use Cases and Queries

A primary use case for RG_XBRL_MAP_V is the resolution of taxonomy element mappings during XBRL instance document generation. A forms-based application or concurrent program may query this view to retrieve the SOURCE_TAX_URL and ELEMENT_NAME for a given SOURCE_TAXONOMY_ID, enabling the correct tagging of financial facts.

Another scenario involves the audit and validation of taxonomy relationships. Analysts and support personnel can query the view to verify that elements are correctly mapped between taxonomies, ensuring data integrity before submission to regulatory bodies.

A representative SQL query, derived directly from the documented view source, is:

SELECT SOURCE_TAX_ALIAS, SOURCE_TAX_URL, SOURCE_TAXONOMY_ID, ELEMENT_LABEL, ELEMENT_NAME, ELEMENT_ID, MAP_TAXONOMY_ID FROM APPS.RG_XBRL_MAP_V;

A more targeted query to find the URL and label for a specific element name would be:

SELECT SOURCE_TAX_URL, ELEMENT_LABEL FROM APPS.RG_XBRL_MAP_V WHERE ELEMENT_NAME = '&element_name';

The view is referenced by the PL/SQL package APPS.RG_XBRL_PKG, indicating that programmatic logic within the application relies on this view for its operations, further underscoring its role as a stable interface for XBRL mapping data access within the EBS environment.