Results for “element_usage”

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

Overview

The EDR_IDX_XML_ELEMENT_USAGES table is a core metadata object within the EDR (E-Records) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented purpose is to record the usage of indexed XML elements associated with E-Records — that is, the structured associations between XML element identifiers and the way those elements are consumed or indexed during e-record processing, rendering, or retrieval. Because E-Records rely on XML payloads to preserve structured business document content, the module requires a registry that tracks which XML elements are referenced and how. This table serves as that registry, allowing indexing and search subsystems to map a document's XML structure to the elements that participate in query and retrieval operations.

The documented Data Vault classification is standalone, indicating that the ETRM metadata exposes no foreign-key dependencies for this object. As a heuristic modeling suggestion, this implies the table behaves as an independent reference entity rather than as a link or dependent satellite. Its key semantics are driven by its own surrogate identifier rather than by relationships to parent hubs. This classification should be treated as a modeling observation derived from the FK structure rather than as a definitive constraint, since EDR metadata frequently uses logical rather than enforced database relationships.

Key Information Stored

The table contains nine documented columns. The most significant are:

• USAGE_ID — the surrogate primary key, defined by the unique index EDR_IDX_XML_ELEMENT_USAGES_P. In the 12.2.2 documented physical schema, the unique index is (USAGE_ID, ZD_EDITION_NAME), making the composite pair the effective business-key candidate under the multi-edition (ZD) model introduced in 12.2.
• ELEMENT_ID — identifies the XML element being tracked. This is the principal business attribute, linking a usage row back to the element definition it describes.
• ELEMENT_USAGE — captures the usage classification or role assigned to the element, distinguishing one usage context from another.
• ZD_EDITION_NAME — the edition qualifier that enables multiple logical editions of the same usage definition to coexist within a single physical table, which is central to EBS 12.2 edition-based redefinition.
• CREATED_BY, CREATION_DATE — standard audit attributes capturing the creating user and creation timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit attributes capturing the most recent modification, its user, and the login session.

The presence of the standard WHO columns confirms the table participates in the standard EBS audit convention and can be audited through the standard Audit Trail facility.

Common Use Cases and Queries

Typical scenarios include determining which XML elements are indexed for a given e-record type, auditing changes to element usage definitions, and diagnosing retrieval failures caused by mismatched element usage. A representative query listing usage records for a specific element is:

SELECT usage_id, element_id, element_usage,
       created_by, creation_date
FROM   edr.edr_idx_xml_element_usages
WHERE  element_id = :p_element_id
ORDER  BY creation_date DESC;

A reporting query auditing recently modified usages is:

SELECT element_id, element_usage, last_updated_by, last_update_date
FROM   edr.edr_idx_xml_element_usages
WHERE  last_update_date >= :p_since
ORDER  BY last_update_date;

In 12.2 environments, queries should generally restrict to the active edition unless historical comparison is required, which can be accomplished by filtering on ZD_EDITION_NAME.

Related Objects

The documented FK structure classifies this object as standalone, so no enforced parent/child relationships are asserted in the metadata. Logically associated objects within the EDR schema include:

• EDR_IDX_XML_ELEMENTS — the XML element definition reference, joined on ELEMENT_ID.
• EDR_IDX_XML_ELEMENT_USAGES_P — the primary key / unique index enforcing USAGE_ID and ZD_EDITION_NAME uniqueness.
• EDR_IDX_* tables — sibling indexing metadata tables in the EDR schema, including element and index registries.
• EDR_INDEXED_* tables — indexed e-record content tables consulted when resolving element usages at retrieval time.
• Standard audit/WHO views — views exposing CREATED_BY, LAST_UPDATED_BY, and related audit columns.

Because the table is a standalone reference entity, joins should be validated against the actual EDR data model rather than assumed from naming conventions alone.