Results for “wms_objects_operand_lov_v”

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

Overview

The WMS_OBJECTS_OPERAND_LOV_V view is a Warehouse Management (WMS) dictionary object owned by the APPS schema. It is documented in Oracle E-Business Suite 12.1.1 and 12.2.2 as the "WMS restriction right operand LOV view." Its purpose is to supply the list of valid right-hand operands used when defining Warehouse Management restriction rules, such as put-away restrictions, picking restrictions, task-type assignments, label restrictions, cycle-count restrictions, and operation-selection rules. Because restriction setup screens require a bounded, pre-validated list of operands, this view serves as the underlying query for the operand list of values (LOV) presented in the WMS setup forms and self-service pages.

The view is read-only and is not a table; consumers query it rather than maintain it. In reporting and integration scenarios, it exposes the same operand vocabulary that the WMS engine uses when evaluating restrictions, allowing external reports, interfaces, and extensions to reference a consistent set of operand codes and descriptions.

Underlying Base Objects

The documented ETRM metadata identifies three referenced base objects, all of which are themselves views: MFG_LOOKUPS, WMS_OBJECTS_VL, and WMS_PARAMETERS_VL. The view definition is a two-branch UNION ALL.

The first branch joins WMS_OBJECTS_VL (alias WOVL) to WMS_PARAMETERS_VL (alias WPVL) on OBJECT_ID and aggregates with MAX() over the flag columns. It returns the literal value 4 as the operand type code, the object name and description, the object identifier, and the maximum values of the six usage flags.

The second branch selects from MFG_LOOKUPS where LOOKUP_TYPE equals 'WMS_OPERAND_TYPE', returning the lookup code and meaning, a null object identifier, and the literal 'Y' for each of the six usage flags. Rows whose lookup code is 4 or 7 are excluded, preventing duplication of the object-based branch values and omitting operand types that are not valid as generic right operands. The union therefore presents a combined operand list drawn from both configured WMS objects and seeded lookup values.

Key Columns

• OPERAND_TYPE_CODE — the primary operand identifier. From MFG_LOOKUPS this is the lookup code; from the object branch the literal 4 is supplied. This is the column most commonly filtered on when a user searches for "operand_type_code."
• OBJECT_NAME — the display name of the operand, derived either from the lookup meaning or from the WMS object name.
• OBJECT_DESCRIPTION — the descriptive text associated with the operand.
• OBJECT_ID — the WMS object identifier where applicable; null for lookup-based operands.
• USE_FOR_PUT_REST_FLAG — indicates whether the operand may be used in put-away restrictions.
• USE_FOR_PICK_REST_FLAG — indicates whether the operand may be used in picking restrictions.
• USE_FOR_TT_ASSN_FLAG — indicates whether the operand may be used in task-type assignment rules.
• USE_FOR_LABEL_REST_FLAG — indicates whether the operand may be used in label restrictions.
• USE_FOR_CG_REST_FLAG — indicates whether the operand may be used in cycle-count restrictions.
• USE_FOR_OP_SELECTION_FLAG — indicates whether the operand may be used in operation-selection rules.

Common Use Cases and Queries

Typical uses include validating operand codes before loading restriction definitions, building custom operand LOVs, and reporting on which operands support which restriction categories.

To retrieve all operands:

• SELECT operand_type_code, object_name, object_description FROM apps.wms_objects_operand_lov_v ORDER BY operand_type_code;

To find operands valid for picking restrictions:

• SELECT operand_type_code, object_name FROM apps.wms_objects_operand_lov_v WHERE use_for_pick_rest_flag = 'Y';

To look up a specific operand code and its description:

• SELECT operand_type_code, object_name, object_description FROM apps.wms_objects_operand_lov_v WHERE operand_type_code = :operand_type_code;

Because the view is defined over MFG_LOOKUPS and the WMS object and parameter views, it should be queried with the APPS schema or through a synonym, and it should be treated as read-only. Reporting joins to WMS restriction tables should use OPERAND_TYPE_CODE as the key, with the usage flags applied as filters to ensure only context-appropriate operands are presented.