Search Results wms_devices_tl




Overview

WMS_DEVICES_TL is the translation table for warehouse device definitions in the Oracle E-Business Suite Warehouse Management (WMS) module. It stores the language-dependent, translatable attributes of a device record — specifically the device name and description — while the language-independent attributes reside in the base table WMS_DEVICES_B. The DEVICE_ID column links each translation row back to its parent record in WMS_DEVICES_B, and the LANGUAGE column identifies the language of the translated text. Together these two columns form the composite primary key WMS_DEVICES_TL_PK1.

The table is owned by the WMS schema and is valid in both Oracle EBS 12.1.1 and 12.2.2. In EBS, translatable tables follow the standard multilingual ("_TL") convention: one row exists per installed language for each base record, ensuring users see device names and descriptions in their session language. The documented schema exposes 10 columns, consistent with a compact translation table that carries only descriptive attributes plus standard WHO audit columns.

From a Data Vault modeling perspective, the heuristic classification is satellite-leaning: the table hangs off the WMS_DEVICES_B parent by a foreign key and stores descriptive, time-stamped attributes rather than defining new business entities or relationships. It behaves like a multi-active satellite keyed by (DEVICE_ID, LANGUAGE), where LANGUAGE introduces an additional grain beyond the parent hub key. This classification is a modeling suggestion, not an enforced EBS construct.

Key Information Stored

The documented columns fall into three functional groups:

  • Primary key columns: DEVICE_ID and LANGUAGE together form WMS_DEVICES_TL_PK1. DEVICE_ID is the surrogate identifier inherited from WMS_DEVICES_B; LANGUAGE (typically an NLS language code such as US or ZHS) scopes the translation row.
  • Translatable business attributes: NAME and DESCRIPTION hold the user-facing device name and descriptive text in the row's language. These are the columns that justify the existence of the _TL table, since they differ per language.
  • Language and audit columns: SOURCE_LANG records the language in which the base record was originally created, supporting the Translation Synchronization process. The remaining columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — are standard EBS WHO audit attributes tracking insert and update context.

The surrogate primary key is therefore (DEVICE_ID, LANGUAGE), while DEVICE_ID alone is a foreign-key candidate mapping to WMS_DEVICES_B. Business-key uniqueness is defined by the combination of parent device and language, which is what prevents duplicate translations for the same device.

Common Use Cases and Queries

The primary use case is retrieving device names in the user's session language for LOVs, device administration screens, and printed warehouse documentation. A typical join pattern is:

  • Joining WMS_DEVICES_TL to WMS_DEVICES_B on DEVICE_ID to combine translated text with language-independent device attributes.
  • Filtering by LANGUAGE to return a single translation per device for a specific locale, for example WHERE LANGUAGE = USERENV('LANG').
  • Querying the translation table in isolation to audit which devices lack a translation in a given language, supporting localization completeness reporting.
  • Comparing NAME values across LANGUAGE rows for the same DEVICE_ID to verify translation consistency.
  • Extracting SOURCE_LANG to identify records pending regeneration through the EBS translation synchronization concurrent program.

Because the table lacks non-key descriptive columns beyond NAME and DESCRIPTION, reporting typically projects DEVICE_ID, LANGUAGE, NAME, and DESCRIPTION and resolves remaining attributes from the base table.

Related Objects

The documented relationship data identifies the key dependencies:

  • WMS_DEVICES_B — the base table; WMS_DEVICES_TL.DEVICE_ID references WMS_DEVICES_B.DEVICE_ID. This is the mandatory parent for every translation row.
  • WMS_DEVICES_TL_PK1 — the composite primary key constraint on (DEVICE_ID, LANGUAGE), enforcing one translation per device per language.
  • WMS_DEVICES_VL — the conventional multilingual view in EBS that joins the _B and _TL tables, presenting translated and base attributes as a single logical entity.
  • WMS_DEVICES_V — any non-translated operational view over the base device table used by runtime WMS logic.
  • Device administration forms and APIs in the Warehouse Management module, which read and write NAME and DESCRIPTION through this table when users create or update device definitions.

Collectively these objects implement the standard EBS translated-table pattern, with WMS_DEVICES_TL providing language-dependent text for the device entity defined in WMS_DEVICES_B.