Results for “taxonomy_import_flag”

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

Overview

The RG_XBRL_TAXONOMIES table is a core repository object within the Oracle E-Business Suite Application Report Generator (RG) product. It stores the master definitions of XBRL (eXtensible Business Reporting Language) taxonomies that are available to the EBS instance for regulatory and financial reporting purposes. A taxonomy in XBRL terms defines the structured vocabulary — concepts, element hierarchies, and dimensional relationships — against which instance documents are tagged. In Oracle EBS, this table serves as the registration point for each imported or referenced taxonomy, allowing downstream mapping, axis set configuration, and element resolution to occur against a valid taxonomy identifier.

From a data modeling perspective, the metadata's heuristic Data Vault classification identifies RG_XBRL_TAXONOMIES as hub-leaning. This is a modeling suggestion rather than a physical designation: the table behaves as a hub because it holds a stable business key (TAXONOMY_ID) that is referenced by multiple dependent tables via foreign keys, with descriptive attributes attached. The table is owned by the RG schema and is documented as VALID in ETRM 12.2.2, comprising 11 columns.

Key Information Stored

The table's structure centers on taxonomy identity and descriptive metadata. The most significant columns are:

• TAXONOMY_ID — the surrogate primary key defined by constraint RG_XBRL_TAXONOMIES_PK, and also a business-key candidate via the unique index RG_XBRL_TAXONOMIES_U1.
• TAXONOMY_ALIAS — a short human-readable identifier, secured as a business-key candidate through the unique index RG_XBRL_TAXONOMIES_U2. This dual uniqueness makes the alias the practical natural key for lookups.
• TAXONOMY_NAME — the full descriptive name of the taxonomy.
• TAXONOMY_DESCR — free-text description providing business context for the taxonomy.
• TAXONOMY_URL — the location from which the taxonomy definition is sourced or referenced.
• TAXONOMY_IMPORT_FLAG — indicates import status or behavior, relevant to how the taxonomy was loaded into EBS.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

The distinction between TAXONOMY_ID as the surrogate primary key and TAXONOMY_ALIAS as an additional unique business key is important for integration design: conformed references should ideally resolve through the alias for stability while joins within the schema use the numeric identifier.

Common Use Cases and Queries

Typical scenarios include enumerating available taxonomies, validating that a taxonomy has been imported before mapping elements, and reporting on taxonomy-to-axis-set configuration. A representative query to list registered taxonomies is:

• SELECT taxonomy_id, taxonomy_alias, taxonomy_name, taxonomy_import_flag FROM rg.rg_xbrl_taxonomies ORDER BY taxonomy_alias;
• Joining to dependents to identify taxonomies lacking element mappings: SELECT t.taxonomy_alias FROM rg.rg_xbrl_taxonomies t WHERE NOT EXISTS (SELECT 1 FROM rg.rg_xbrl_elements e WHERE e.taxonomy_id = t.taxonomy_id);
• Auditing recent imports via the audit columns: WHERE last_update_date > :from_date.

These patterns support XBRL filing preparation, taxonomy governance reviews, and reconciliation of report axis sets against their governing taxonomy.

Related Objects

The FK metadata establishes RG_XBRL_TAXONOMIES as a referenced parent. The most significant related objects are:

• RG_REPORT_AXIS_SETS — joins on TAXONOMY_ID; defines axis (dimensional) configurations governed by a taxonomy.
• RG_XBRL_ELEMENTS — joins on TAXONOMY_ID; holds the elements belonging to each taxonomy.
• RG_XBRL_MAP_ELEMENTS — joins on TAXONOMY_ID; maps report data to taxonomy elements.

Together these dependents consume the taxonomy hub, confirming its central role in the RG XBRL reporting subsystem.