Results for “dtd_root_element”

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

Overview

EDR_SECURE_ELEMENTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the EDR (E-Records) product family. Its documented purpose is to expose the set of indexed XML elements that have been defined for use when creating security rules. In other words, the view identifies which XML elements within a given DTD root structure may be referenced as the basis for applying record-level or element-level security within the E-Records framework.

In Oracle EBS 12.1.1 and 12.2.2, this view serves as a convenience access point for administrators, integrators, and developers who need to enumerate the security-eligible XML elements without navigating the underlying definition and usage tables directly. The view is documented with a status of VALID, and its view text filters the underlying data so that only elements marked with a status of 'I' and a usage of 'S' are surfaced. This deliberate filtering makes the view a curated list of the elements that are actively designated for security rule definition.

Underlying Base Objects

According to the documented view text, EDR_SECURE_ELEMENTS_V is defined over two base objects:

• EDR_IDX_XML_ELEMENT_VL — a view supplying the XML element definitions, including element identifiers, XML element names, DTD root elements, application ownership, section and tag indexing attributes, display names, and descriptions. The VL suffix indicates a translatable (multi-language) view, meaning display-oriented attributes such as DISPLAY_NAME and DESCRIPTION may resolve according to the session language.
• EDR_IDX_XML_ELEMENT_USAGES — documented as a SYNONYM, supplying usage records that associate each element with a particular usage classification. The join condition restricts results to records where ELEMENT_USAGE = 'S', identifying elements used for security purposes.

The two objects are joined on ELEMENT_ID. In combination with the filter on STATUS = 'I', the view returns only indexed, active elements whose usage is security-related. The referenced base objects are documented metadata for ETRM 12.2.2; the same structure applies across the 12.1.1 and 12.2.2 releases.

Key Columns

• ELEMENT_ID — the primary identifier of the indexed XML element and the join key between the definition and usage objects.
• XML_ELEMENT — the name of the XML element that can be secured.
• DTD_ROOT_ELEMENT — the root element of the DTD to which the XML element belongs, providing structural context.
• APPLICATION_ID — the application that owns the element definition.
• INDEX_SECTION_NAME — the indexing section to which the element is assigned; this is the attribute commonly referenced when organizing or searching for security-eligible elements, and corresponds directly to the user's search term.
• INDEX_TAG — the indexing tag associated with the element, used alongside the section name to locate elements within indexed XML content.
• DISPLAY_NAME and DESCRIPTION — user-facing labels and explanatory text, resolved through the translatable base view.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and LAST_UPDATE_DATE, providing standard Oracle EBS audit trail information.

Common Use Cases and Queries

This view is typically used to investigate or verify which XML elements are available for security rule configuration, to drive integration logic that maps security rules to element names, and to support troubleshooting when security rules do not behave as expected. A straightforward listing of all security-eligible elements is shown below:

SELECT element_id, xml_element, dtd_root_element,
       index_section_name, index_tag, display_name
  FROM apps.edr_secure_elements_v
 ORDER BY dtd_root_element, index_section_name;

Because the user searched on index_section_name, a targeted query filtering by that column is particularly relevant:

SELECT xml_element, index_tag, display_name
  FROM apps.edr_secure_elements_v
 WHERE index_section_name = :section_name;

Administrators may also restrict results by application to scope the elements to a single module:

SELECT element_id, xml_element, display_name
  FROM apps.edr_secure_elements_v
 WHERE application_id = :application_id;

Each of these queries respects the built-in filtering on status and security usage, so results reflect only elements that are genuinely available for security rule definition at the time of execution.