Results for “wms_task_filter_b”

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

Overview

WMS_TASK_FILTER_B is the base (non-translated) definition table for task filters within the Oracle Warehouse Management (WMS) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the WMS schema and is classified as VALID in the ETRM repository. Task filters represent reusable selection criteria — combinations of warehouse, task type, priority, or other task attributes — that determine which material handling or execution tasks are surfaced to warehouse operators and mobile devices. The table serves as the transactional anchor that holds the filter identity and its descriptive definition, while dependent tables retain multilingual text and item-level filter detail.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object is hub-leaning. The documented unique indexes center on TASK_FILTER_ID and TASK_FILTER_NAME (each paired with ZD_EDITION_NAME), which supports treating WMS_TASK_FILTER_B as a business-key hub or a strongly natural-keyed entity rather than a pure satellite. This classification is heuristic and offered as a modeling suggestion only.

Key Information Stored

The table contains 24 documented columns. The most consequential are:

• TASK_FILTER_ID — the surrogate primary key, enforced by WMS_TASK_FILTER_B_PK1. It is the join column referenced by every dependent table.
• TASK_FILTER_NAME — the user-facing business key. It is captured in the unique index WMS_TASK_FILTER_B_U1 (with ZD_EDITION_NAME), making it a documented business-key candidate.
• ZD_EDITION_NAME — the editioning column introduced under the Edition-Based Redefinition (EBR) model used in 12.2.x. It participates in both unique indexes (WMS_TASK_FILTER_B_U1 and WMS_TASK_FILTER_B_U2), so the true business key of a filter is the combination of name or ID with edition.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing auditability and user accountability.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (Descriptive Flexfield) segment set, allowing customers to extend a task filter definition with site-specific attributes without modifying the seeded schema.

The surrogate key provides stable internal identity, while TASK_FILTER_NAME serves as the human-recognizable reference. Distinguishing the two is essential when building integrations that must remain resilient to renames.

Common Use Cases and Queries

Typical scenarios include auditing which task filters exist in a warehouse, resolving a filter name to its surrogate ID for downstream joins, and reporting on filter-level extension attributes.

A basic lookup joins the base and translated tables:

• SELECT b.task_filter_id, b.task_filter_name, t.description FROM wms_task_filter_b b JOIN wms_task_filter_tl t ON t.task_filter_id = b.task_filter_id WHERE b.task_filter_name = :name;

Enumerating filters per edition (12.2.2):

• SELECT task_filter_id, task_filter_name, zd_edition_name FROM wms_task_filter_b WHERE zd_edition_name = SYS_CONTEXT('USERENV','DB_EDITION');

Reporting a detail-driven view of filter logic requires joining WMS_TASK_FILTER_DTL:

• SELECT b.task_filter_name, d.* FROM wms_task_filter_b b JOIN wms_task_filter_dtl d ON d.task_filter_id = b.task_filter_id;

Flexfield-based reporting selects the ATTRIBUTE columns directly from the base table for the relevant ATTRIBUTE_CATEGORY.

Related Objects

The documented relationships identify the following significant dependents, all keyed on TASK_FILTER_ID:

• WMS_TASK_FILTER_DTL — holds the filter detail rows (the criteria that make up each task filter). Joins via WMS_TASK_FILTER_DTL.TASK_FILTER_ID → WMS_TASK_FILTER_B.TASK_FILTER_ID.
• WMS_TASK_FILTER_TL — the translation table for language-dependent names and descriptions. Joins via WMS_TASK_FILTER_TL.TASK_FILTER_ID → WMS_TASK_FILTER_B.TASK_FILTER_ID.

Together these two tables form the documented foreign-key footprint of WMS_TASK_FILTER_B; any reporting or extraction should treat the trio as a single logical unit, with the _B table supplying identity and audit columns, the _TL table supplying localized text, and the _DTL table supplying the actual selection logic consumed by WMS task dispatch.