Search Results logical_operator_code

Overview

WMS_RESTRICTIONS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Warehouse Management (WMS) product family. In both 12.1.1 and 12.2.2, the object carries a VALID status and is documented in ETRM as "WMS restriction view." Its purpose is to present the rule-level restrictions that govern how WMS rules operate—each restriction pairs a rule parameter with an operator and an operand, forming the conditional logic evaluated during warehouse execution activities such as put-away, picking, and task planning.

The view denormalizes technical foreign keys into human-readable meanings and canonical operand values, allowing reporting tools, concurrent programs, and integration layers to consume restriction definitions without re-implementing the decoding logic. It is commonly joined to WMS_RULES_VL and WMS_PARAMETERS_VL to reconstruct complete rule definitions.

Underlying Base Objects

The view is defined over the WMS_RESTRICTIONS synonym, augmented by joined lookups and descriptive entities. Documented referenced objects include:

• WMS_RESTRICTIONS (synonym) — the header restriction rows supplying RULE_ID, SEQUENCE_NUMBER, PARAMETER_ID, OPERATOR_CODE, operand type and operand constants (OPERAND_CONSTANT_NUMBER, OPERAND_CONSTANT_CHARACTER, OPERAND_CONSTANT_DATE, OPERAND_EXPRESSION, OPERAND_FLEX_VALUE_SET_ID, OPERAND_PARAMETER_ID).
• WMS_RULES_VL — rule name and description (WRVL.NAME, WRVL.DESCRIPTION).
• WMS_PARAMETERS_VL — parameter names and descriptions for both the left-hand parameter (WPVL) and the operand parameter (WPVR).
• WMS_OBJECTS_VL — object identifiers and names for parameters and operands (WOVL, WOVR).
• MFG_LOOKUPS — lookup meanings for operator, operand type, and related codes (MLR, MLX1, MLX2).
• WMS_PARAMETER_PVT — PL/SQL package supplying GETFLEXNAME and GETFLEXDATATYPECODE for flexfield-backed parameters.
• FND_FLEX_VALUE_SETS — value set name and description when the operand is a flex value set (operand type 6).
• FND_NUMBER and FND_DATE — canonical conversion of numeric and date constants via NUMBER_TO_CANONICAL and DATE_TO_CANONICAL.

Key Columns

• RULE_ID, SEQUENCE_NUMBER — identify the owning rule and ordering of restrictions within it.
• NAME, DESCRIPTION, ORGANIZATION_ID, USER_DEFINED_FLAG, TYPE_CODE — rule attributes from the rules view.
• PARAMETER_ID, GETFLEXNAME(...) — the parameter being constrained and its resolved flexfield name.
• OPERATOR_CODE, MLX1.MEANING — comparison operator and its decoded meaning.
• OPERAND_TYPE_CODE, MLX2.MEANING — operand category (constant, parameter, expression, flex value set, and so on).
• OPERAND_CONSTANT_NUMBER, OPERAND_CONSTANT_CHARACTER, OPERAND_CONSTANT_DATE — the literal constant values, one populated per operand type.
• OPERAND_PARAMETER_ID, OPERAND_EXPRESSION, OPERAND_FLEX_VALUE_SET_ID — references for parameter, expression, and value-set operands.
• DECODE(...) expressions produce a unified operand value, operand description, and operand object identifier/name, and normalize the data type code.

Common Use Cases and Queries

Typical scenarios include auditing rule configuration, diagnosing rule evaluation failures, migrating restrictions between environments, and building custom warehouse rule reports. The decode logic makes the view suitable for direct reporting without additional lookup joins.

Sample query listing restrictions for a rule:

SELECT r.rule_id,
       r.name            rule_name,
       r.sequence_number,
       r.operator_code,
       r.meaning         operator_meaning,
       r.operand_constant_number,
       r.operand_constant_character,
       r.operand_constant_date
FROM   apps.wms_restrictions_v r
WHERE  r.rule_id = :p_rule_id
ORDER  BY r.sequence_number;

For example, to locate restrictions using a character constant operand (the "operand_constant_character" search term), filter on the decoded operand type or simply on the constant column:

SELECT rule_id, name, operator_code, operand_constant_character
FROM   apps.wms_restrictions_v
WHERE  operand_constant_character IS NOT NULL;

Because the view normalizes number, date, and character constants into distinct columns while exposing a unified decoded operand, it remains the preferred access path for restrictions in both 12.1.1 and 12.2.2.