Results for “operand_constant_character”

20 results




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

Overview

WMS_RESTRICTIONS is a Warehouse Management (WMS) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual condition lines that make up a warehouse rule definition, where each row contributes one comparison expression to the rule's Boolean predicate. Together with WMS_RULES_B, which holds the rule header, WMS_RESTRICTIONS forms the rule engine used by WMS to determine which put-away, picking, replenishment, or allocation behaviour applies to a given inventory context.

The table resides in the WMS schema and is classified as VALID in the ETRM data dictionary for 12.2.2. Its primary key, WMS_RESTRICTIONS_PK, is a composite key on (RULE_ID, SEQUENCE_NUMBER). From a heuristic Data Vault modelling perspective, this object is best treated as a link: it resolves the many-to-many association between a rule (WMS_RULES_B) and the parameters, constants, and flex value sets referenced by each restriction line. The metadata's Data Vault classification confirms this "link" heuristic, mined from the foreign-key structure.

Key Information Stored

Of the 36 documented columns, the following are the most significant for functional and technical understanding:

The surrogate identity of a row is (RULE_ID, SEQUENCE_NUMBER). The unique index WMS_RESTRICTIONS_U1 (RULE_ID, SEQUENCE_NUMBER, ZD_EDITION_NAME) is the business-key candidate, ensuring one restriction line per sequence per edition of a rule.

Common Use Cases and Queries

Typical reporting scenarios include reconstructing the full predicate of a rule for audit or troubleshooting, listing all rules that reference a given parameter, and identifying rules dependent on a specific flex value set. A representative query joining the header to its restriction lines:

  • Reconstruct a rule: SELECT r.rule_id, s.sequence_number, s.parameter_id, s.operator_code, s.operand_type_code, s.operand_constant_character, s.logical_operator_code FROM wms_rules_b r JOIN wms_restrictions s ON s.rule_id = r.rule_id WHERE r.rule_id = :rule_id ORDER BY s.sequence_number.
  • Impact analysis by parameter: SELECT rule_id, sequence_number FROM wms_restrictions WHERE parameter_id = :parameter_id OR operand_parameter_id = :parameter_id.
  • Flex value set dependency: SELECT rule_id, sequence_number FROM wms_restrictions WHERE operand_flex_value_set_id = :flex_value_set_id.
  • Rule maintenance auditing via CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Related Objects

  • WMS_RULES_B — Parent rule header; joined on WMS_RESTRICTIONS.RULE_ID = WMS_RULES_B.RULE_ID.
  • WMS_PARAMETERS_B — Parameter definitions; referenced twice, via WMS_RESTRICTIONS.PARAMETER_ID and WMS_RESTRICTIONS.OPERAND_PARAMETER_ID.
  • FND_FLEX_VALUE_SETS — Value set definitions; referenced via WMS_RESTRICTIONS.OPERAND_FLEX_VALUE_SET_ID.
  • WMS_RULES_TL — Translated rule names and descriptions; joined through the rule header.

These relationships make WMS_RESTRICTIONS the connective layer between rule definitions and the warehouse parameters and value sets they evaluate at runtime.