Results for “xml_element”

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

Overview

The view APPS.EDR_XMLMAP_ELEMENTS_V belongs to the EDR (E-Records) product family within Oracle E-Business Suite, and is available in both the 12.1.1 and 12.2.2 releases. Its documented purpose is to present a cross-reference of XML elements against their corresponding DTD root elements. In practice, this view exposes the mapping metadata that Oracle EBS uses when constructing or interpreting XML documents against registered Document Type Definitions (DTDs).

Because the object is a view rather than a table, it holds no persistent data of its own; it is a read-only projection over the ECX mapping infrastructure. For users who begin their investigation from a search on ecx_mappings, this view is a convenient entry point: rather than navigating the four underlying ECX tables and reconstructing the join conditions manually, the view delivers a denormalised, human-readable relationship between an XML element name, its MAP_CODE, and the DTD root element to which it belongs. It is therefore primarily useful for diagnostics, mapping audits, and reporting on the XML map configuration rather than for transactional processing.

Underlying Base Objects

The view is defined entirely over synonyms referencing the ECX mapping tables. The documented base objects are ECX_MAPPINGS, ECX_OBJECTS, ECX_OBJECT_LEVELS, and ECX_OBJECT_ATTRIBUTES, all resolved through public or APPS synonyms. The view text, as recorded in the ETRM metadata, joins these four sources as follows:

• ECX_OBJECTS is restricted to rows where OBJECT_TYPE = 'DTD', isolating DTD object definitions and supplying ROOT_ELEMENT.
• ECX_OBJECT_LEVELS is joined on the shared MAP_ID and on OBJECT_ID, providing the object-level context.
• ECX_OBJECT_ATTRIBUTES is joined on MAP_ID and OBJECTLEVEL_ID, filtered to ATTRIBUTE_TYPE = 1 and PARENT_ATTRIBUTE_ID <> 0, which selects child-level XML elements rather than top-level attributes.
• ECX_MAPPINGS is joined on MAP_ID across all three of the above, and contributes MAP_CODE.

The join key throughout is MAP_ID, so the view effectively reports the coherent set of DTD object, level, and attribute definitions belonging to each mapping.

Key Columns

• ROOT_ELEMENT — sourced from ECX_OBJECTS.ROOT_ELEMENT. Identifies the root element of the DTD associated with the mapping, establishing the document root under which the listed XML element appears.
• MAP_CODE — sourced from ECX_MAPPINGS.MAP_CODE. The identifier of the mapping record that ties the object, level, and attribute definitions together; this is the value most commonly used to locate or reference a specific XML map.
• XML_ELEMENT — sourced from ECX_OBJECT_ATTRIBUTES.ATTRIBUTE_NAME. The name of the child XML element participating in the mapping. The column is aliased to XML_ELEMENT to reflect its role in XML document structure rather than its storage name.

Each row therefore represents a single XML element, its owning map, and the DTD root under which it is defined.

Common Use Cases and Queries

Typical uses include verifying that a given map code exposes the expected XML elements, auditing which DTD roots are in use, and troubleshooting XML interface or e-records failures where an element is not recognised.

To list all elements for a specific map:

• SELECT map_code, root_element, xml_element FROM apps.edr_xmlmap_elements_v WHERE map_code = :map_code ORDER BY xml_element;

To find every map that defines a particular XML element:

• SELECT map_code, root_element FROM apps.edr_xmlmap_elements_v WHERE xml_element = :element_name;

To enumerate the distinct DTD roots represented in the mapping repository:

• SELECT DISTINCT root_element FROM apps.edr_xmlmap_elements_v ORDER BY root_element;

Because the view joins four ECX tables, queries should be filtered on MAP_CODE or XML_ELEMENT wherever possible to limit the result set. Access is governed by the APPS schema, and the view should be treated as read-only reference data.