Results for “edr_idx_xml_element_vl”

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

Overview

EDR_IDX_XML_ELEMENT_VL is a multilingually-enabled (MLS) view owned by the APPS schema within the EDR – E-Records product module of Oracle E-Business Suite. It presents the translated, user-facing representation of records that define the XML elements indexed by the E-Records indexing engine. In Oracle EBS 12.1.1 and 12.2.2, the "_VL" suffix denotes a view that joins a base ("_B") table containing language-independent attributes with a translation ("_TL") table containing language-specific display text. The view therefore exposes one row per indexed XML element, resolved to the session's current language, and is the interface through which E-Records components and custom reports retrieve element names and descriptions.

The view is documented as VALID in the ETRM repository, confirming it is a supported, queryable object rather than a deprecated artifact. Its principal role is to support reporting and integration against the E-Records indexing configuration, allowing developers and administrators to enumerate which XML tags, DTD root elements, and index sections are registered for indexing without querying the underlying base tables directly.

Underlying Base Objects

The view is defined over two synonyms resolving to EDR base tables:

• EDR_IDX_XML_ELEMENT_B – the base table holding language-independent data for each indexed XML element, including its identifiers, tag names, owning application, and audit columns.
• EDR_IDX_XML_ELEMENT_TL – the translation table holding the DISPLAY_NAME and DESCRIPTION columns for each supported language.

The defining query joins the two tables on ELEMENT_ID and filters the translation row with T.LANGUAGE = USERENV('LANG'), so that only the row matching the current session language is returned. This pattern is the standard Oracle MLS construct and ensures each element appears exactly once in the result set regardless of how many translations exist in the TL table.

Key Columns

The view exposes the following columns, drawn from the base table unless noted:

• ROW_ID – the ROWID of the base table row, supplied for updatable-view and row-identification semantics.
• ELEMENT_ID – the primary key linking a base row to its translations.
• XML_ELEMENT – the XML element (tag) name registered for indexing.
• DTD_ROOT_ELEMENT – the root element of the DTD to which the indexed element belongs.
• APPLICATION_ID – the Oracle Application owning the indexed element.
• INDEX_SECTION_NAME and INDEX_TAG – the index section and tag under which the element is catalogued.
• STATUS – the active/inactive state of the element definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE – standard EBS audit columns.
• DISPLAY_NAME and DESCRIPTION – translated, user-facing text sourced from EDR_IDX_XML_ELEMENT_TL and resolved for the session language.

Common Use Cases and Queries

Typical uses include enumerating the indexing configuration for an application, validating that a given XML tag is registered before relying on indexed search results, and building custom reports or LOVs over the E-Records index metadata.

List all active indexed elements for a specific application:

• SELECT element_id, xml_element, dtd_root_element, index_section_name, index_tag, display_name FROM apps.edr_idx_xml_element_vl WHERE application_id = :app_id AND status = 'A' ORDER BY xml_element;

Look up a specific XML element by its tag and root element:

• SELECT element_id, display_name, description, index_section_name FROM apps.edr_idx_xml_element_vl WHERE xml_element = :tag AND dtd_root_element = :root;

Because the view resolves translations through USERENV('LANG'), the DISPLAY_NAME and DESCRIPTION returned reflect the language of the connected session; alternative-language text for the same element is available by querying EDR_IDX_XML_ELEMENT_TL directly. All queries should be issued against the APPS schema or through a synonym, consistent with standard EBS customization practice.