Results for “xnp_msg_acks”

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

Overview

XNP_MSG_ACKS is a table owned by the XNP schema within the Oracle E-Business Suite Number Portability module. It is documented as containing message relationships, meaning it defines which acknowledgment message type is issued in response to a given source message type. In the Number Portability message-exchange model, porting requests and their corresponding acknowledgments must be explicitly mapped so that the application can determine the correct response message when processing inbound or outbound porting transactions such as Local Service Request (LSR) submissions, responses, and confirmations.

The table is classified as VALID and carries a documented physical schema of ten columns in ETRM 12.2.2. Following heuristic Data Vault modeling conventions derived from its foreign key structure, XNP_MSG_ACKS is best characterized as a link table: it resolves a many-to-many style relationship between message types rather than storing descriptive attributes of a single business entity. The presence of two foreign keys both pointing to XNP_MSG_TYPES_B reinforces this interpretation, since a link table typically references the same hub from two distinct roles (here, a source role and an acknowledgment role). A secondary reference to FND_SECURITY_GROUPS indicates that rows are subject to Oracle Application Object Library security group partitioning.

Key Information Stored

The columns documented in the ETRM metadata are as follows:

• MSG_ACK_ID — the surrogate primary key, enforced by the XNP_MSG_ACKS_PK constraint. This is a system-generated identifier with no business meaning.
• SOURCE_MSG_CODE — the message code of the originating message. This is a foreign key to XNP_MSG_TYPES_B and identifies the message for which an acknowledgment is expected.
• ACK_MSG_CODE — the message code of the acknowledgment message. This is also a foreign key to XNP_MSG_TYPES_B and defines the response issued for the source message.
• SECURITY_GROUP_ID — the security group to which the row belongs, foreign keyed to FND_SECURITY_GROUPS. This enables multi-org–style filtering of Number Portability configuration data.
• ZD_EDITION_NAME — the edition identifier used by Oracle’s Editioning infrastructure and by the Online Patching framework in EBS 12.2.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns that capture audit and concurrency information for every row.

Two unique indexes are documented, both business-key candidates. XNP_MSG_ACKS_U1 covers (MSG_ACK_ID, ZD_EDITION_NAME), and XNP_MSG_ACKS_U2 covers (SOURCE_MSG_CODE, ACK_MSG_CODE, ZD_EDITION_NAME). The U2 index is the meaningful business constraint: it prevents duplicate definitions of the same source-to-acknowledgment pairing within an edition.

Common Use Cases and Queries

The primary use case is resolving the acknowledgment message type for a given inbound Number Portability message during processing. A typical lookup joins the table to XNP_MSG_TYPES_B twice to resolve both codes to their descriptive names:

• Querying the acknowledgment for a specific source code: SELECT ACK_MSG_CODE FROM XNP_MSG_ACKS WHERE SOURCE_MSG_CODE = :source;
• Reporting all configured message pairings joined to message type descriptions: SELECT a.SOURCE_MSG_CODE, s.MSG_NAME, a.ACK_MSG_CODE, t.MSG_NAME FROM XNP_MSG_ACKS a, XNP_MSG_TYPES_B s, XNP_MSG_TYPES_B t WHERE a.SOURCE_MSG_CODE = s.MSG_CODE AND a.ACK_MSG_CODE = t.MSG_CODE;
• Validating configuration completeness ahead of a porting interface go-live, or detecting orphaned pairings no longer backed by a valid message type.
• Security-group–scoped extraction for a given SECURITY_GROUP_ID when diagnosing why an acknowledgment is not being issued for a specific operating unit.

Because configuration rows are typically maintained through the Number Portability administrative setup rather than direct DML, queries against XNP_MSG_ACKS are predominantly read-only diagnostics and reconciliation reports.

Related Objects

The following objects are most significant in relation to XNP_MSG_ACKS:

• XNP_MSG_TYPES_B — the base table of message types, referenced twice via SOURCE_MSG_CODE and ACK_MSG_CODE. This is the principal dependency and the primary join target.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID and used to partition configuration rows.
• XNP_MSG_TYPES_TL — the translated table for message type names, joined on MSG_CODE and language for readable reporting.
• XNP_MSG_ACKS_PK / XNP_MSG_ACKS_U1 / XNP_MSG_ACKS_U2 — the supporting constraints and indexes that enforce uniqueness on the surrogate key and on the source-to-acknowledgment pairing per edition.
• Other XNP message-processing tables — message logging and transaction tables that consume the pairing defined here to determine the appropriate acknowledgment response during runtime processing.

Collectively, these objects form the message-type resolution layer of the Number Portability module, with XNP_MSG_ACKS acting as the join construct that maps requests to their required acknowledgments.