Search Results wms_msg_templates_u1

Overview

WMS.WMS_MSG_TEMPLATES is a Warehouse Management System (WMS) configuration table that stores message templates used for parsing device responses. In the Oracle EBS 12.1.1 and 12.2.2 environments, it resides in the WMS schema and serves as the definition repository for the delimiters, structure types, and formats that the WMS device integration layer uses to interpret inbound messages from radio frequency (RF) handheld devices, barcode scanners, voice-directed picking units, and similar warehouse hardware. Each row describes how a specific message class is structured, enabling the parsing engine to split, tokenize, and map device responses back into WMS transactional data.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, which suggests it is best modeled as a reference or hub-style entity. Because it holds descriptive template definitions keyed by a stable business identifier, it functions as a foundational reference dimension rather than a transactional fact or an associative link. The classification is heuristic and should be treated as a modeling suggestion, not a declared Data Vault construct.

Key Information Stored

The table is defined with eleven columns and is created in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. The most important columns are:

• TEMPLATE_ID (NUMBER) — Surrogate primary key, enforced by the WMS_MSG_TEMPLATES_PK constraint. It uniquely identifies each message template.
• TEMPLATE_NAME (VARCHAR2(100)) — Business-key candidate, enforced as unique by index WMS_MSG_TEMPLATES_U1 in the APPS_TS_TX_IDX tablespace. This is the human-readable identifier used by administrators and integration code.
• WMS_MSG_TEMPLATE_TYPE (NUMBER) — Classifies the template structure. Documented values are 1 for XML, 2 for delimiter-based messages, 3 for messages without delimiters, and 4 for Vocollect message structures.
• START_MESSAGE_DELIMITER (VARCHAR2(80)) — Comma-separated ASCII values marking the beginning of a message.
• END_MESSAGE_DELIMITER (VARCHAR2(80)) — Comma-separated ASCII values marking the end of a message.
• PARAMETER_DELIMITER (NUMBER) — ASCII value of the delimiter separating individual parameters within a message.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing creation and modification metadata for change tracking and compliance.

Common Use Cases and Queries

Typical uses include reviewing active template definitions, troubleshooting device parsing failures, and auditing configuration changes. A common query retrieves all templates by name and type:

• Template lookup: SELECT TEMPLATE_ID, TEMPLATE_NAME, WMS_MSG_TEMPLATE_TYPE FROM WMS.WMS_MSG_TEMPLATES WHERE TEMPLATE_NAME = :name;
• Type-based reporting: Group templates by WMS_MSG_TEMPLATE_TYPE to inventory XML versus delimiter-based versus Vocollect configurations.
• Change auditing: Filter on LAST_UPDATE_DATE to identify templates modified during a deployment window.
• Delimiter analysis: Inspect START_MESSAGE_DELIMITER, END_MESSAGE_DELIMITER, and PARAMETER_DELIMITER when debugging messages that fail to parse.

Related Objects

Per the documented dependency metadata, WMS.WMS_MSG_TEMPLATES does not reference any other database object, confirming its standalone classification. It is referenced by the WMS-owned object WMS_MSG_TEMPLATES# (the materialized view or synonym form of the base table). Because no foreign keys are declared, joins to other WMS tables are made logically through TEMPLATE_ID and TEMPLATE_NAME rather than by enforced constraints. Administrators commonly correlate these definitions with device configuration and integration processing tables in the WMS schema, but the metadata confirms only the self-referencing dependency listed above as authoritative.