Results for “xnp_msg_attr_values”

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

Overview

XNP_MSG_ATTR_VALUES is a table in the XNP (Number Portability) product schema of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. It stores the individual attribute values that are attached to XML message elements exchanged between the EBS instance and the number portability service bureau or clearinghouse. In the Number Portability message framework, XML payloads are decomposed into elements and attributes; XNP_MSG_ELEMENT_ATTR defines the attribute definitions associated with each message element, while XNP_MSG_ATTR_VALUES holds the concrete value rows for those attributes on a per-message-instance basis. The table therefore acts as the value-bearing extension of the message attribute model and is populated and consumed by the portability message processing programs.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification: the table records descriptive attribute values keyed to a parent entity (XNP_MSG_ELEMENT_ATTR) rather than acting as an independent hub or as a linking table between two business entities.

Key Information Stored

The table contains ten documented columns, of which the following are the most significant:

• MSG_ATTR_VALUE_ID — Surrogate primary key of the table, enforced by the XNP_MSG_ATTR_VALUES_PK constraint. This is the unique identifier of each attribute value row.
• MSG_ELEMENT_ATTR_ID — Foreign key to XNP_MSG_ELEMENT_ATTR. This column identifies which message element attribute definition the value belongs to, tying each value to a specific attribute of a specific XML element.
• ATTR_VALUE — The actual value of the attribute for the message instance. This carries the operational payload data extracted from or destined for the portability XML message.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, applying multi-org / security group partitioning so that rows are visible only within the appropriate operating context.
• ZD_EDITION_NAME — Editioning column supporting the EBS online patching (Edition-Based Redefinition) model introduced in 12.2. This column participates in the unique index XNP_MSG_ATTR_VALUES_U1 (MSG_ATTR_VALUE_ID, ZD_EDITION_NAME).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who inserted and last modified the row, when, and through which login session.

The unique index XNP_MSG_ATTR_VALUES_U1 on (MSG_ATTR_VALUE_ID, ZD_EDITION_NAME) serves as the business-key candidate in the editioned 12.2 data model.

Common Use Cases and Queries

Typical usage centers on diagnosing, auditing, and reporting the attribute content of number portability messages. A common pattern joins the value table to its parent attribute definitions to produce a readable message payload:

• Message content inspection — Joining XNP_MSG_ATTR_VALUES to XNP_MSG_ELEMENT_ATTR on MSG_ELEMENT_ATTR_ID retrieves each attribute name together with its stored ATTR_VALUE, reconstructing the attribute portion of a submitted or received portability message.
• Audit and troubleshooting — Filtering by CREATION_DATE or LAST_UPDATE_DATE isolates values loaded during a specific batch window, useful when reconciling a failed portability request.
• Security group reporting — Restricting queries by SECURITY_GROUP_ID ensures that only values belonging to the caller's operating unit or security context are returned, consistent with EBS data security conventions.
• Volume and trend analysis — Aggregating counts per MSG_ELEMENT_ATTR_ID highlights which message attributes are populated most frequently, informing message template maintenance.

A representative query pattern selects MSG_ATTR_VALUE_ID, MSG_ELEMENT_ATTR_ID, and ATTR_VALUE from XNP_MSG_ATTR_VALUES, joining to XNP_MSG_ELEMENT_ATTR for attribute metadata and applying an appropriate SECURITY_GROUP_ID predicate.

Related Objects

The most significant objects that reference or depend on XNP_MSG_ATTR_VALUES are:

• XNP_MSG_ELEMENT_ATTR — Parent table referenced by MSG_ELEMENT_ATTR_ID. It defines the attribute metadata to which each value row is attached.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; governs row-level visibility of attribute values.
• XNP_MSG_ELEMENT / XNP_MSG_ATTR_VALUES family — The broader XNP message definition tables that, together with XNP_MSG_ELEMENT_ATTR, establish the XML message template hierarchy within which attribute values are stored.
• XNP Number Portability message processing concurrent programs and PL/SQL APIs — These load, validate, and consume the attribute values as part of portability request and response handling.

Because XNP_MSG_ATTR_VALUES is a child (satellite-leaning) object, direct DML should be avoided in favor of the supported XNP message APIs, and queries should always respect the security group and editioning columns.