Results for “xnp_msg_element_attr”

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

Overview

XNP_MSG_ELEMENT_ATTR is a transactional configuration table in the XNP (Number Portability) product of Oracle E-Business Suite 12.1.1 and 12.2.2. As its ETRM description states, the table "contains attributes of XML elements" — it defines the attribute metadata associated with individual XML message elements processed or generated by the Number Portability framework. Each row describes one attribute belonging to a parent XML element, capturing the attribute name, its datatype, and an optional reference to the data source from which the attribute value is derived. In this respect the table functions as a metadata dictionary that drives runtime parsing, validation, and population of XML message payloads exchanged with external number-portability clearinghouses and service providers.

From a Data Vault modeling perspective the mined FK structure is classified as satellite-leaning. This suggests XNP_MSG_ELEMENT_ATTR is best understood as a descriptive satellite attached to the XNP_MSG_ELEMENTS hub, carrying the attribute-level descriptive context of each element rather than acting as an independent business hub or a pure link between hubs. The classification is heuristic and should be treated as a modeling suggestion, not a normative property of the physical table.

Key Information Stored

The documented physical schema comprises 12 columns. The most operationally significant are:

• MSG_ELEMENT_ATTR_ID — the surrogate primary key, enforced by XNP_MSG_ELEMENT_ATTR_PK. It is also the leading column of both unique indexes, XNP_MSG_ELEMENT_ATTR_U1 and XNP_MSG_ELEMENT_ATTR_U2.
• MSG_ELEMENT_ID — the foreign key to XNP_MSG_ELEMENTS that identifies the parent XML element to which this attribute belongs.
• NAME — the attribute name as it appears in the XML payload; it forms the business-key candidates together with MSG_ELEMENT_ID and ZD_EDITION_NAME in the U2 index.
• ATTR_DATATYPE — the datatype of the attribute, used to drive conversion and validation logic.
• DATA_SOURCE_REFERENCE — a reference identifying where the attribute value originates at runtime.
• SECURITY_GROUP_ID — the multi-tenant/security grouping key, referenced from FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — the editioning column supporting Online Patching in EBS 12.2.2, included in both unique indexes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns providing audit lineage.

The business-key candidates documented via unique indexes are (MSG_ELEMENT_ATTR_ID, ZD_EDITION_NAME) and (NAME, MSG_ELEMENT_ID, ZD_EDITION_NAME), distinguishing the surrogate identifier from the natural attribute name within an element.

Common Use Cases and Queries

The primary use case is metadata-driven XML processing: application code and PL/SQL load attribute definitions to know which XML attributes to expect, how to interpret them, and from which source to populate them. Reporting use cases include inventorying attributes per element, auditing datatype coverage, and validating that every attribute is reachable from a data source.

A representative query joining the parent element table:

SELECT a.NAME, a.ATTR_DATATYPE, a.DATA_SOURCE_REFERENCE FROM xnp.xnp_msg_element_attr a, xnp.xnp_msg_elements e WHERE a.msg_element_id = e.msg_element_id AND a.zd_edition_name = 'SET1';

A second pattern joins attribute values to their definitions:

SELECT v.*, a.NAME, a.ATTR_DATATYPE FROM xnp.xnp_msg_attr_values v, xnp.xnp_msg_element_attr a WHERE v.msg_element_attr_id = a.msg_element_attr_id;

Related Objects

• XNP_MSG_ELEMENTS — parent table; joined on MSG_ELEMENT_ATTR.MSG_ELEMENT_ID = XNP_MSG_ELEMENTS.MSG_ELEMENT_ID.
• XNP_MSG_ATTR_VALUES — child table; joined on XNP_MSG_ATTR_VALUES.MSG_ELEMENT_ATTR_ID = XNP_MSG_ELEMENT_ATTR.MSG_ELEMENT_ATTR_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security grouping.
• FND_APPLICATION / XNP installation tables — contextual objects for the Number Portability module's configuration.
• XNP_MSG_ELEMENT_ATTR_PK, _U1, _U2 — the primary and unique indexes enforcing row identity.

Together these objects form the XML-message metadata backbone of the Number Portability module.