Results for “xnp_msg_types_tl”

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

Overview

XNP_MSG_TYPES_TL is the translation (language-specific) table for message type definitions within the Oracle E-Business Suite Number Portability module (XNP). XNP supports regulatory number portability requirements, in which subscribers may transfer their telephone numbers between carriers; the module coordinates port requests, messages, and responses exchanged with number portability administrations and trading partners. Message types classify the business events carried by those exchanges, such as port request submission, confirmation, rejection, or cancellation notices.

The table's documented role is precisely that of a translation table to XNP_MSG_TYPES_B: the _B table holds the base, language-independent definition of each message type, while XNP_MSG_TYPES_TL holds the translatable attributes—display name and description—for each installed language. It is owned by the XNP schema and is valid in EBS 12.1.1 and 12.2.2.

Mined from the foreign-key structure, the heuristic Data Vault classification for this table is satellite-leaning. In Data Vault terms this suggests it behaves as a descriptive satellite of the message type hub, carrying multi-language descriptive attributes keyed by the hub business key plus a language or edition discriminator. It should be treated as a modeling suggestion rather than a documented architectural fact.

Key Information Stored

The documented physical schema of XNP_MSG_TYPES_TL contains 12 columns. The most significant are:

• MSG_CODE — the message type code; part of the composite primary key and the business identifier inherited from XNP_MSG_TYPES_B.
• LANGUAGE — the language code for the translated content; the second component of the primary key.
• SOURCE_LANG — the source language from which the translation was derived, used by the multilingual (MLS) framework for translation tracking.
• DISPLAY_NAME — the user-facing, language-specific name of the message type.
• DESCRIPTION — the language-specific description of the message type's purpose.
• ZD_EDITION_NAME — the edition discriminator supporting Oracle's edition-based redefinition (EBR) in 12.2.x; part of the unique index XNP_MSG_TYPES_TL_U1.
• SECURITY_GROUP_ID — the security group (operating unit) context; foreign key to FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording insert and update activity.

The surrogate primary key is defined by XNP_MSG_TYPES_TL_PK on (MSG_CODE, LANGUAGE). The unique index XNP_MSG_TYPES_TL_U1 on (MSG_CODE, LANGUAGE, ZD_EDITION_NAME) is the business-key candidate, extending the primary key with the edition column to distinguish rows across editions in 12.2.x environments.

Common Use Cases and Queries

Typical uses include populating message type lists on portability request screens, rendering messages and error descriptions in the user's session language, and reporting on message type definitions across operating units. A standard join retrieves the default-language display text:

SELECT b.msg_code, t.display_name, t.description
FROM xnp_msg_types_b b, xnp_msg_types_tl t
WHERE b.msg_code = t.msg_code
AND t.language = USERENV('LANG');

Reporting queries commonly filter by security_group_id to restrict results to the relevant operating unit, and by zd_edition_name to return only the run edition in 12.2.x. Translation maintenance and verification reports typically compare the row counts of XNP_MSG_TYPES_B and XNP_MSG_TYPES_TL by language to identify untranslated or missing message types.

Related Objects

• XNP_MSG_TYPES_B — the base table; joined on XNP_MSG_TYPES_TL.MSG_CODE = XNP_MSG_TYPES_B.MSG_CODE, the documented foreign key.
• FND_SECURITY_GROUPS — referenced via the documented foreign key on SECURITY_GROUP_ID.
• FND_LANGUAGES — the language repository used to validate and display values of LANGUAGE and SOURCE_LANG.
• FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — define the XNP application context in which these message types are installed and licensed.
• Oracle Number Portability message-processing and request tables in the XNP schema — consume MSG_CODE values defined in the base table when constructing and interpreting portability messages.
• Multilingual (MLS) framework objects — underlying views and APIs that manage translated rows, including _VL views for XNP_MSG_TYPES, which join the base and translation tables for display purposes.