Results for “wms_operand_type”

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

Overview

APPS.WMS_OBJECTS_OPERAND_LOV_V is a Warehouse Management System (WMS) list-of-values view shipped in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a unified list of operands — the values upon which WMS business rules and constraint conditions are evaluated — drawn from two independent sources. The first source consists of WMS objects registered in the WMS Objects and WMS Parameters tables, which represent the physical and logical entities (such as Locator, Item, or container attributes) that a rule can inspect. The second source consists of seeded lookup codes maintained under the WMS_OPERAND_TYPE lookup type in MFG_LOOKUPS.

The view's role is to feed the operand selection list-of-values used in the WMS Rules workbench and related setup pages, allowing a user to pick a valid operand when constructing a put-away, picking, task, label, cycle count, or operation selection rule. Because it is a standard APPS-owned database view, it is also a legitimate target for custom reporting and integration queries that need to enumerate the operands available to the WMS rules engine without replicating the underlying union logic.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over three referenced base objects, all of which are themselves views:

• WMS_OBJECTS_VL — supplies the WMS object identifier, name, and description for objects registered in WMS.
• WMS_PARAMETERS_VL — supplies the per-object parameter rows and, critically, the flags indicating whether the object is valid for use in a given rule category (put-away restriction, pick restriction, task assignment, label restriction, cycle count restriction, and operation selection).
• MFG_LOOKUPS — supplies the seeded operand lookup codes under lookup type WMS_OPERAND_TYPE.

The view body is a UNION ALL of two branches. The first branch joins WMS_OBJECTS_VL to WMS_PARAMETERS_VL on OBJECT_ID, groups by object, and applies MAX() to each of the six usage flags so that a single row is produced per object. It emits the literal 4 in the leading column (the operand type/class identifier). The second branch selects from MFG_LOOKUPS where LOOKUP_TYPE = 'WMS_OPERAND_TYPE', excluding lookup codes 4 and 7, and hard-codes all six usage flags to 'Y', with a NULL object ID. Because UNION ALL is used, no de-duplication occurs between the two branches.

Key Columns

• Leading literal (4) / LOOKUP_CODE — the operand type or code. The first branch always returns 4; the second returns the lookup code, except for codes 4 and 7, which are intentionally omitted.
• NAME / MEANING — the display name of the operand. The first branch returns the WMS object name; the second returns the lookup meaning.
• DESCRIPTION — the descriptive text for the operand from either source.
• OBJECT_ID — the WMS object identifier from WMS_PARAMETERS_VL; NULL for the lookup-derived rows.
• USE_FOR_PUT_REST_FLAG — whether the operand may be used in put-away restriction rules.
• USE_FOR_PICK_REST_FLAG — whether the operand may be used in picking restriction rules.
• USE_FOR_TT_ASSN_FLAG — whether the operand may be used in task type assignment rules.
• USE_FOR_LABEL_REST_FLAG — whether the operand may be used in label restriction rules.
• USE_FOR_CG_REST_FLAG — whether the operand may be used in cycle count (count group) restriction rules.
• USE_FOR_OP_SELECTION_FLAG — whether the operand may be used in operation selection rules.

Common Use Cases and Queries

The principal use case is providing the operand LOV in WMS rule setup, filtered by the rule category in which the user is working. A report or form can restrict the list to operands valid for a specific rule type by filtering on the relevant flag.

Sample query listing all operands valid for put-away restriction rules:

• SELECT name, description, object_id FROM apps.wms_objects_operand_lov_v WHERE use_for_put_rest_flag = 'Y' ORDER BY name;

Sample query enumerating operands that carry an object identifier (i.e., the WMS-object branch), useful when reconciling rule definitions against registered objects:

• SELECT object_id, name, description FROM apps.wms_objects_operand_lov_v WHERE object_id IS NOT NULL ORDER BY name;

Sample query identifying operands usable across every rule category, which is helpful when auditing broadly applicable operands:

• SELECT name FROM apps.wms_objects_operand_lov_v WHERE use_for_put_rest_flag = 'Y' AND use_for_pick_rest_flag = 'Y' AND use_for_tt_assn_flag = 'Y' AND use_for_label_rest_flag = 'Y' AND use_for_cg_rest_flag = 'Y' AND use_for_op_selection_flag = 'Y';

Because the view is defined with UNION ALL and an aggregate, queries should be treated as read-only and not relied upon for row-level uniqueness of OBJECT_ID. For integration, the view is best consumed as a lookup source rather than as a transactional interface.