Results for “wms_task_filter_tl”

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

Overview

WMS_TASK_FILTER_TL is the translation (language) table for Warehouse Management task filters in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides in the WMS schema and stores the multilingual, language-specific attributes of a task filter: primarily its user-facing name and description. Each row in this table corresponds to one language translation of a task filter defined in the base table, WMS_TASK_FILTER_B.

The object is owned by the WMS - Warehouse Management product and is documented as a VALID table in the ETRM repository. Its defining characteristic is the pairing of a language-independent business entity key (TASK_FILTER_ID) with a LANGUAGE code, which is precisely the pattern used throughout EBS for translated reference data.

From a Data Vault modeling perspective, the metadata classifies this object as satellite-leaning. This is a heuristic suggestion rather than a physical attribute: the table depends on a parent (via a foreign key to WMS_TASK_FILTER_B) and carries descriptive, language-specific attributes keyed by that parent plus a language qualifier. That is the classic shape of a satellite attached to a hub (the task filter). The LANGUAGE column functions as a secondary key that expands the parent hub key, so a hub-plus-satellite design remains a reasonable modeling interpretation.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• TASK_FILTER_ID — The identifier of the underlying task filter defined in WMS_TASK_FILTER_B. This is the foreign key to the base table and forms the first component of the primary key.
• LANGUAGE — The two-character (or NLS) language code identifying which translation this row provides. It forms the second component of the primary key.
• USER_TASK_FILTER_NAME — The translated, user-visible name of the task filter for the given language. This is the principal business-facing attribute.
• TASK_FILTER_DESCRIPTION — The translated descriptive text associated with the filter.
• SOURCE_LANG — The language from which the current translation was derived or copied, used by the translation framework to track the origin of each row.
• ZD_EDITION_NAME — The editioning column supporting Oracle EBS Edition-Based Redefinition, enabling online patching across editions in 12.2.x.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY and LAST_UPDATE_LOGIN record who created and last modified each translation row and when.

The documented primary key is WMS_TASK_FILTER_TL_PK1 on (TASK_FILTER_ID, LANGUAGE). A separate unique index, WMS_TASK_FILTER_TL_U1 on (TASK_FILTER_ID, LANGUAGE, ZD_EDITION_NAME), is the business-key candidate because it adds the editioning column, guaranteeing one translation per language per edition. Because the PK does not include the edition column here, the U1 index is the more precise uniqueness guarantee under EBR.

Common Use Cases and Queries

The dominant use case is presenting task filter names and descriptions in the user's session language. Standard EBS translation queries join the translation table to the base table and filter on the current language. A representative pattern is:

• Retrieve translated names for a filter: SELECT b.task_filter_id, tl.user_task_filter_name, tl.task_filter_description FROM wms_task_filter_b b, wms_task_filter_tl tl WHERE b.task_filter_id = tl.task_filter_id AND tl.language = USERENV('LANG').
• Cross-language reporting: group by LANGUAGE to audit which task filters have translations and which fall back to SOURCE_LANG or the base definition.
• Data-quality checks: identify base rows in WMS_TASK_FILTER_B with no matching translation row, revealing missing localization.
• Edition-aware queries: in 12.2.x, constrain ZD_EDITION_NAME when querying outside the runtime edition to avoid returning rows from multiple editions.

Report developers frequently build inline views against this table to supply a localized filter name as a label for warehouse operational reports, task prioritization dashboards, and filter-selection LOVs.

Related Objects

• WMS_TASK_FILTER_B — The base table holding language-independent task filter definitions. Joined on WMS_TASK_FILTER_TL.TASK_FILTER_ID = WMS_TASK_FILTER_B.TASK_FILTER_ID. This is the only documented foreign key relationship.
• WMS_TASK_FILTER_TL_PK1 — The primary key constraint/index on (TASK_FILTER_ID, LANGUAGE).
• WMS_TASK_FILTER_TL_U1 — The unique index on (TASK_FILTER_ID, LANGUAGE, ZD_EDITION_NAME), the business-key candidate.
• WMS_TASK_FILTERS_VL / translation views — The EBS _VL view pattern typically unions base and translation rows to present the current-language filter, depending directly on this table.
• WMS_TASK_FILTER_... functional objects — Task-filter assignment and rule tables in the WMS module reference the same TASK_FILTER_ID, indirectly relying on this table for localized display.
• FND_LANGUAGES / FND_LANGUAGE — Provides the valid LANGUAGE codes and the installed-language settings used to filter rows.

In summary, WMS_TASK_FILTER_TL is a compact translation satellite for warehouse task filters, central to any query that must render filter names and descriptions in a specific language.