Results for “xnp_msg_elements”

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

Overview

XNP_MSG_ELEMENTS is a transactional configuration table in the XNP (Number Portability) product of Oracle E-Business Suite. It resides in the XNP schema and stores the individual XML message elements that make up the message definitions used during number portability processing. Each row represents a discrete field or tag within an XML message payload, capturing its name, data type, default value, length, and whether it is mandatory or parameter-driven. This table functions as the element-level metadata repository that drives message construction, validation, and parsing between carriers and the number portability gateway.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. XNP_MSG_ELEMENTS holds a stable business key (the combination of NAME and MSG_CODE) with descriptive attributes such as data type, length, and default value, making it behave similarly to a hub with a small attached satellite of descriptive attributes. This is a heuristic suggestion rather than a documented ETRM designation.

Key Information Stored

All documented columns are listed in the ETRM schema metadata, totalling 16 columns. The most significant are:

• MSG_ELEMENT_ID — surrogate primary key, defined by the XNP_MSG_ELEMENTS_PK constraint and also protected by unique index XNP_MSG_ELEMENTS_U1 when combined with ZD_EDITION_NAME. Used by all child tables as the FK target.
• NAME and MSG_CODE — the business-key candidates. Unique index XNP_MSG_ELEMENTS_U2 enforces (NAME, MSG_CODE, ZD_EDITION_NAME), guaranteeing that an element name is unique within a given message type. MSG_CODE is a foreign key to XNP_MSG_TYPES_B.
• MANDATORY_FLAG — indicates whether the element must be supplied in the message.
• PARAMETER_FLAG and PARAMETER_SEQUENCE — mark elements that are parameter-driven and control their ordering within the parameter list.
• ELEMENT_DATATYPE, DATA_LENGTH, and ELEMENT_DEFAULT_VALUE — define the format, size, and default value for the element content.
• ZD_EDITION_NAME — editioning column used by EBS 12.2 online patching, forming part of both unique indexes.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data segregation.
• Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include validating which elements are required for a given message type, extracting parameter-driven elements for a specific carrier, and auditing the data types and lengths applied to message fields. A common query joins the parent message type and filters on the mandatory flag:

• SELECT e.msg_element_id, e.name, e.element_datatype, e.data_length, e.mandatory_flag FROM xnp.xnp_msg_elements e WHERE e.msg_code = :msg_code;
• SELECT e.name, e.parameter_sequence FROM xnp.xnp_msg_elements e WHERE e.parameter_flag = 'Y' AND e.msg_code = :msg_code ORDER BY e.parameter_sequence;
• Join to XNP_MSG_TYPES_B to retrieve the human-readable message type name: SELECT t.name, e.name FROM xnp.xnp_msg_elements e, xnp.xnp_msg_types_b t WHERE e.msg_code = t.msg_code;

Related Objects

The table participates in a network of XNP metadata objects that together define message structure:

• XNP_MSG_TYPES_B — parent message type referenced through MSG_CODE; defines the message header that owns each element.
• XNP_MSG_ELEMENT_ATTR — child table referencing MSG_ELEMENT_ID; stores attribute-level detail for each element.
• XNP_MSG_STRUCTURES — references this table twice via PARENT_ELEMENT_ID and CHILD_ELEMENT_ID, defining the hierarchical nesting of message elements.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for row-level security.

Together these objects form the complete XNP message definition framework used during porting message assembly and validation.