Results for “wms_zones_tl”

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

Overview

WMS_ZONES_TL is a translation (TL) table belonging to the Oracle Warehouse Management (WMS) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-specific, user-facing attributes for warehouse zones, which are logical subdivisions of a warehouse used to group storage locations for put-away, picking, and inventory control. Because Oracle EBS is a multi-language application, descriptive text such as zone names and descriptions is held in a companion translation table rather than in the base entity, allowing a single zone definition to be presented in each installed language.

In ETRM 12.2.2 the object is owned by the WMS schema and exposes ten documented columns. Its primary key, WMS_ZONES_TL_PK, is a composite of ZONE_ID and LANGUAGE. The unique index WMS_ZONES_TL_U1 covers the same pair (ZONE_ID, LANGUAGE), confirming the natural business key of the translation row. The metadata classifies the object as standalone under the heuristic Data Vault analysis mined from its foreign-key structure; as a modeling suggestion, this positions it as a satellite-style table holding descriptive, language-dependent attributes keyed by a parent zone identifier plus a language code, rather than as a hub or link in its own right.

Key Information Stored

The most significant columns are as follows. ZONE_ID is the surrogate identifier linking each translation row to its parent zone definition and forms part of the composite primary key. LANGUAGE identifies the language of the translated text and, together with ZONE_ID, constitutes both the primary key and the documented business-key candidate (WMS_ZONES_TL_U1). ZONE_NAME holds the translated, user-visible name of the zone. DESCRIPTION carries the translated descriptive text used in forms and reports. SOURCE_LANG records the source language from which the translation was derived, supporting Oracle's language-handling conventions.

The audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN capture the standard Oracle who-and-when audit trail for each translated row. Together these ten columns provide the language-specific content and change history required to render zone information correctly across locales, while the language-independent zone attributes are retained in the base WMS_ZONES table.

Common Use Cases and Queries

Typical usage centers on reporting and configuration validation in multi-language warehouses. A common pattern joins the translation table to its base zone table, filtering on the appropriate language, for example:

• SELECT b.zone_id, t.zone_name, t.description FROM wms_zones b, wms_zones_tl t WHERE b.zone_id = t.zone_id AND t.language = USERENV('LANG');
• Reporting all installed translations for a zone: SELECT language, zone_name FROM wms_zones_tl WHERE zone_id = :zone_id ORDER BY language.
• Auditing recent changes: SELECT zone_id, language, last_updated_by, last_update_date FROM wms_zones_tl WHERE last_update_date > :since.

These queries support label printing, warehouse configuration reviews, localization testing, and extraction for downstream reporting or data-warehouse loads.

Related Objects

The principal relationships are:

• WMS_ZONES — the base zone definition; joined on ZONE_ID.
• WMS_ZONES_TL_PK and WMS_ZONES_TL_U1 — the primary key and unique index enforcing the composite ZONE_ID, LANGUAGE key.
• WMS_LOCATIONS / WMS_LPN tables representing warehouse storage and license-plate entities that reference zones for operational processing.
• FND_LANGUAGES — the language reference behind the LANGUAGE and SOURCE_LANG columns.
• WMS Zone setup and warehouse configuration forms and the WMS public APIs that maintain zone definitions.

These objects collectively govern how zones are defined, translated, and consumed across WMS operations.