Results for “data_source_reference”

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

Overview

XNP_MSG_STRUCTURES is a core configuration table within the XNP - Number Portability module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The table stores the structural relationship, or hierarchy, of all elements that compose an XML message payload used during number portability processing. In practice, it defines which message elements are parents of which child elements, thereby describing the nesting and tree topology of each XML message type known to the application.

From a data modeling perspective, the metadata classifies this object heuristically as a link table. This is a modeling suggestion: the table primarily resolves relationships between message types and elements rather than holding descriptive attributes on its own. It sits between the message type definitions and the element definitions, binding them into a navigable structure.

Key Information Stored

• STRUCTURE_ID — Surrogate primary key, enforced by XNP_MSG_STRUCTURES_PK. It uniquely identifies each structural relationship row.
• MSG_CODE — Identifies the XML message type to which the structure belongs; foreign key to XNP_MSG_TYPES_B.
• PARENT_ELEMENT_ID — References the parent element in XNP_MSG_ELEMENTS; a null or root value implies a top-level element.
• CHILD_ELEMENT_ID — References the child element positioned beneath the parent; foreign key to XNP_MSG_ELEMENTS.
• SEQUENCE_IN_PARENT — Ordering of the child element within its parent, governing element sequence in the rendered message.
• CARDINALITY — Defines occurrence constraints (for example, single versus repeating elements) for the relationship.
• DATA_SOURCE, DATA_SOURCE_TYPE, DATA_SOURCE_REFERENCE — Describe how the element value is populated, its source category, and the referenced source object.
• ELEMENT_POSITION, ELEMENT_ALIGNMENT, PADDING — Formatting attributes controlling placement, alignment, and padding of element content.
• SECURITY_GROUP_ID — Multi-tenant security grouping; foreign key to FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.
• ZD_EDITION_NAME — Editioning column supporting Online Patching in 12.2.x.

Two unique indexes act as business-key candidates. XNP_MSG_STRUCTURES_U1 covers STRUCTURE_ID and ZD_EDITION_NAME, while XNP_MSG_STRUCTURES_U2 covers MSG_CODE, CHILD_ELEMENT_ID, PARENT_ELEMENT_ID, and ZD_EDITION_NAME. The UK1 key documented as MSG_CODE, CHILD_ELEMENT_ID, PARENT_ELEMENT_ID confirms that a given child may attach to a given parent only once per message type.

Common Use Cases and Queries

Typical scenarios include reconstructing the XML message hierarchy for a given message type, validating element nesting before message generation, and reporting the data sources that feed each element. A common query retrieves the direct children of a parent element:

• SELECT child_element_id, sequence_in_parent FROM xnp_msg_structures WHERE msg_code = :msg_code ORDER BY sequence_in_parent;
• Recursive queries using CONNECT BY PRIOR child_element_id = parent_element_id START WITH parent_element_id IS NULL render the full XML tree for a message type.
• Joining to XNP_MSG_ELEMENTS resolves element names and attributes for readable hierarchy reports.
• Reporting queries filter by SECURITY_GROUP_ID to respect multi-tenant boundaries.

Related Objects

• XNP_MSG_TYPES_B — joined on MSG_CODE; defines each message type.
• XNP_MSG_ELEMENTS — joined twice, on PARENT_ELEMENT_ID and CHILD_ELEMENT_ID, to resolve parent and child element definitions.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for multi-tenant security.