Search Results ecx_standard_attributes




Overview
Explore in AI Chat

Overview

The ECX_STANDARD_ATTRIBUTES table is a core metadata object within the Oracle E-Business Suite XML Gateway module (product code ECX). It stores the individual attribute definitions that belong to a given XML Gateway standard. In EBS, a "standard" is the logical definition of an outbound or inbound business transaction (for example, a purchase order or an invoice) expressed as a set of attributes that map to E-Business Suite database columns and are rendered into an XML message. ECX_STANDARD_ATTRIBUTES therefore acts as the attribute-level registry: each row describes one attribute belonging to one standard, including its name and the corresponding XML element tag name used during message generation.

From a Data Vault modeling perspective, the documented metadata classifies this object heuristically as standalone, with no foreign-key relationships mined from the underlying constraint structure. This suggests modeling it as a hub-like reference entity keyed on its own business identity, rather than as a dependent link or satellite. In EBS terms, the table is configuration metadata maintained through the XML Gateway setup responsibilities and is not itself a transactional or high-volume data store.

Key Information Stored

The table contains ten documented columns. The most important are:

  • STANDARD_ATTRIBUTE_ID — the surrogate primary key, enforced by ECX_STANDARD_ATTRIBUTES_PK (and also referenced by SYS_C00407836). It uniquely identifies each attribute row.
  • STANDARD_ID — identifies the parent XML Gateway standard to which the attribute belongs. This is the principal business relationship column, although it is not enforced as a foreign key in the documented schema.
  • ATTRIBUTE_NAME — the logical name of the attribute as known within the standard definition.
  • ELEMENT_TAG_NAME — the XML element tag emitted (or expected) for this attribute when the message is generated or parsed. This drives the physical XML payload structure.
  • ZD_EDITION_NAME — the editioning column used by the EBS online patching (ADOP) architecture in 12.2, enabling edition-based redefinition of the table across patch cycles.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record who created and last modified each attribute definition and when.

Two unique indexes act as business-key candidates: ECX_STANDARD_ATTRIBUTES_U1 on (STANDARD_ID, ATTRIBUTE_NAME, ZD_EDITION_NAME) and ECX_STANDARD_ATTRIBUTES_U2 on (STANDARD_ATTRIBUTE_ID, ZD_EDITION_NAME). U1 is the functionally meaningful constraint, ensuring that attribute names are unique within a standard for a given edition; U2 enforces surrogate uniqueness across editions.

Common Use Cases and Queries

Typical uses include reviewing or troubleshooting the attribute composition of an XML Gateway standard, verifying XML tag mappings, and supporting impact analysis before changing a standard. A common query lists all attributes for a standard:

SELECT standard_attribute_id, attribute_name, element_tag_name
FROM   ecx.ecx_standard_attributes
WHERE  standard_id = :p_standard_id
ORDER  BY attribute_name;

To trace the XML tag that will be produced for a given attribute, query ELEMENT_TAG_NAME by ATTRIBUTE_NAME. For patch or audit analysis, filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY identifies recently changed definitions. Edition-aware queries should include ZD_EDITION_NAME to avoid mixing rows created under different editions during online patching.

Related Objects

These relationships are logical joins rather than enforced foreign keys; the documented schema exposes no FK constraints on ECX_STANDARD_ATTRIBUTES.