Results for “xnp_msg_types_tl_u1”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
XNP.XNP_MSG_TYPES_TL is the translation (language) table associated with XNP_MSG_TYPES_B in the Oracle E-Business Suite XNP schema. XNP is the schema historically associated with Oracle's Advanced Planning and Scheduling and Supply Chain messaging infrastructure, and XNP_MSG_TYPES_B serves as the base (language-independent) definition of message types used to classify messages exchanged between EBS modules such as ASCP, GOP, and MSO. The _TL companion table stores the multilingual, user-facing text — display names and descriptions — keyed by MSG_CODE and LANGUAGE. Because rows in a translation table are descriptive attributes of a single parent entity, a reasonable Data Vault modeling suggestion is to treat this object as satellite-leaning: it holds context and descriptive attributes that hang off the MSG_CODE business key found in XNP_MSG_TYPES_B, rather than introducing new relationships between entities.
The table resides in the APPS_TS_SEED tablespace, consistent with its role as seeded reference metadata distributed with the application rather than transactional data. It is present and VALID in both EBS 12.1.1 and 12.2.2, though the 12.2.2 schema additionally exposes a ZD_EDITION_NAME column for Online Patching (editioning) support, which is absent from the 12.1.x definition.
Key Information Stored
The table's primary key is XNP_MSG_TYPES_TL_PK, defined on (MSG_CODE, LANGUAGE). Two business-key candidates are documented via unique indexes:
- XNP_MSG_TYPES_TL_U1 — UNIQUE index on (MSG_CODE, LANGUAGE) in 12.1.1; in 12.2.2 the definition is extended to (MSG_CODE, LANGUAGE, ZD_EDITION_NAME), reflecting edition-aware uniqueness.
- MSG_CODE — VARCHAR2(20); short name for the message type; the foreign key to XNP_MSG_TYPES_B.MSG_CODE.
- LANGUAGE — VARCHAR2(40); the target language of the translated text, supporting Oracle's Multi-Language Support (MLS) architecture.
- SOURCE_LANG — VARCHAR2(40); the language the text mirrors. When a translation is not yet complete, edits to the source-language row propagate into this row.
- DISPLAY_NAME — VARCHAR2(60); the user-visible label for the message type.
- DESCRIPTION — VARCHAR2(1996); extended free-text describing the message type's purpose.
- CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard WHO audit columns.
- SECURITY_GROUP_ID — NUMBER; used in hosted (multi-tenant, shared-schema) environments; FK to FND_SECURITY_GROUPS.
Common Use Cases and Queries
Reporting on message types — for example, building a labeled reference list for integration or troubleshooting dashboards — nearly always requires joining the translated text to the base row using MSG_CODE and filtering on the session language. A typical MLS-aware pattern follows:
SELECT b.msg_code, tl.display_name, tl.description
FROM xnp.xnp_msg_types_b b,
xnp.xnp_msg_types_tl tl
WHERE b.msg_code = tl.msg_code
AND tl.language = USERENV('LANG');
Other common scenarios include auditing which message types lack a translation for a given language (a LEFT OUTER JOIN where tl.msg_code IS NULL), reviewing change history through the WHO columns, and validating seeded data during a patch or upgrade by inspecting ZD_EDITION_NAME in 12.2.2 environments. Because the table is seeded reference data, it is generally queried and never updated by end users; DML against MLS text should be performed through the corresponding base-table maintenance forms or APIs rather than direct SQL.
Related Objects
- XNP.XNP_MSG_TYPES_B — the base table; joined on MSG_CODE. This is the parent of the translation row.
- FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID in hosted deployments; typically joined in multi-tenant reporting to scope rows to the correct security group.
- XNP_MSG_TYPES_TL_PK and XNP_MSG_TYPES_TL_U1 — the primary key constraint and unique index that enforce one translation per message code per language (per edition in 12.2.2).
- APPS.XNP_MSG_TYPES_TL — the APPS-owned synonym used by application code and reports in place of the XNP-owned object.
- Any message-type lookup views or concurrent programs in the XNP/ASCP messaging stack that resolve message type labels for display.
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
TABLE: XNP.XNP_MSG_TYPES_TL 12.1.1
-
12.1.1 DBA Data 12.1.1
-
TABLE: XNP.XNP_MSG_TYPES_TL 12.2.2
-
Translation table to XNP_MSG_TYPES_B
-
Translation table to XNP_MSG_TYPES_B
-
eTRM - XNP Tables and Views 12.1.1
Stores a list of all timers in progress
-
eTRM - XNP Tables and Views 12.2.2
Stores a list of all timers in progress