Results for “wms_task_filter_vl”

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

Overview

WMS_TASK_FILTER_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema in Oracle E-Business Suite. It is part of the WMS (Warehouse Management) product family and exposes translated task filter definitions used by the Warehouse Management System. The "_VL" suffix denotes a "view with language" — a standard Oracle EBS naming convention for views that join a base ("_B") table with its translation ("_TL") table and return the row in the session's current language. This view is validated and documented in ETRM 12.2.2, and the same definition applies to 12.1.1.

Functionally, a "task filter" in WMS defines criteria that determine which warehouse tasks are displayed or processed by a user or mobile device session. Task filters allow warehouse operators to restrict the tasks returned to their RF (radio frequency) interface by attributes such as task type, subinventory, or other parameters. WMS_TASK_FILTER_VL provides the user-facing, translated name and description of these filters, making it the authoritative source for reporting and integration code that needs to present filter definitions in the user's own language.

Underlying Base Objects

The view is defined over two documented base objects, referenced via synonyms:

• WMS_TASK_FILTER_B — the base table holding language-independent filter attributes, including the primary key TASK_FILTER_ID, the internal TASK_FILTER_NAME, WHO audit columns, and the standard ATTRIBUTE1 through ATTRIBUTE15 DFF (descriptive flexfield) columns.
• WMS_TASK_FILTER_TL — the translation table holding USER_TASK_FILTER_NAME and TASK_FILTER_DESCRIPTION for each language.

The view joins the two tables on TASK_FILTER_ID and filters the translation with the predicate T.LANGUAGE = USERENV('LANG'). This user-environment call returns the language code of the current database session, so the view returns only the single translated row matching the session's NLS language. All columns are prefixed with the "B." alias for base-table columns and "T." for translation-table columns in the view text.

Key Columns

• ROW_ID — the physical ROWID of the base-table row, used by Oracle Forms for row identification.
• TASK_FILTER_ID — the primary key and foreign key linking the base and translation records; the join column between WMS_TASK_FILTER_B and WMS_TASK_FILTER_TL.
• TASK_FILTER_NAME — the internal (language-independent) name of the task filter, sourced from the base table.
• USER_TASK_FILTER_NAME — the translated, user-facing name of the filter, sourced from the translation table.
• TASK_FILTER_DESCRIPTION — the translated long description of the filter's purpose, sourced from the translation table.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns, populated from the base table only.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 .. ATTRIBUTE15 — the descriptive flexfield (DFF) context and segment columns, carried from the base table for extensions and reporting.

Common Use Cases and Queries

Typical reporting and integration scenarios include listing the task filters available in the current language, resolving a filter's translated name for a mobile or RF screen, and auditing filter definitions or their DFF attributes. Because the view restricts rows to the session language via USERENV('LANG'), it returns exactly one translation per filter, which avoids duplicate-row handling in reports.

Example 1 — list all task filters in the session language:

SELECT task_filter_id,
       task_filter_name,
       user_task_filter_name,
       task_filter_description
FROM   apps.wms_task_filter_vl
ORDER  BY user_task_filter_name;

Example 2 — retrieve a single filter by name:

SELECT task_filter_id,
       user_task_filter_name,
       task_filter_description
FROM   apps.wms_task_filter_vl
WHERE  task_filter_name = :p_filter_name;

Example 3 — inventory of filter definitions with DFF attributes:

SELECT task_filter_id,
       user_task_filter_name,
       attribute_category,
       attribute1,
       attribute2,
       last_update_date
FROM   apps.wms_task_filter_vl;

One practical caveat: if a translated row does not exist for the session language, the inner join to WMS_TASK_FILTER_TL suppresses that filter entirely. Queries that must return filters regardless of the current language should join WMS_TASK_FILTER_B directly or use the translation table with an explicit LANGUAGE predicate.