Results for “wms_rules_b”

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

Overview

WMS_RULES_B is the base table within the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite that stores the definition of warehouse execution rules. In WMS, a "rule" is the fundamental building block used to control how the system drives picking, put-away, replenishment, and other directed warehouse activities. The "_B" suffix denotes the base (language-independent) portion of a translated entity; the corresponding translations are held in WMS_RULES_TL. Each row in this table defines a single rule header, identified by a surrogate primary key and scoped to a specific inventory organization.

From a data-modeling perspective, the metadata's heuristic Data Vault classification is hub-leaning. This reflects the table's role as a durable registry of rule identities: RULE_ID behaves as a hub key, while descriptive attributes and the many downstream referencing tables attach as satellites and links. This is a modeling suggestion rather than a physical implementation constraint, but it accurately captures how WMS rules serve as the anchor for a wide network of dependent configuration.

The table is owned by the WMS schema and, in the documented 12.2.2 physical schema, contains 33 columns. Its primary key is WMS_RULES_B_PK on RULE_ID, with a unique business-key index WMS_RULES_B_U1 on (RULE_ID, ZD_EDITION_NAME), the latter supporting edition-based redefinition and Online Patching in 12.2.x.

Key Information Stored

The most significant columns describe rule identity, classification, scope, and operational behavior:

• RULE_ID — surrogate primary key (via WMS_RULES_B_PK) and, together with ZD_EDITION_NAME, a unique business-key candidate. This is the value propagated to all dependent tables.
• ORGANIZATION_ID — foreign key to MTL_PARAMETERS; scopes the rule to a specific inventory organization.
• TYPE_CODE and TYPE_HDR_ID — classify the rule type (for example, pick, put-away, or replenishment) and link it to its rule-type header definition.
• ENABLED_FLAG — indicates whether the rule is active and therefore eligible for evaluation.
• WMS_ENABLED_FLAG — distinguishes rules applicable specifically under WMS-enabled operations.
• USER_DEFINED_FLAG — separates seeded rules from customer-defined rules.
• RULE_WEIGHT — provides a relative weighting used when rules are evaluated or prioritized.
• MIN_PICK_TASKS_FLAG — controls whether pick tasks are minimized during rule execution.
• ALLOCATION_MODE_ID — references the allocation mode applied when the rule is used.
• QTY_FUNCTION_PARAMETER_ID — foreign key to WMS_PARAMETERS_B, linking the rule to a quantity function parameter.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive-flexfield columns for extensible, customer-defined attributes.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• ZD_EDITION_NAME — the edition column supporting 12.2.x Online Patching.

Common Use Cases and Queries

Configuration and support teams query this table to audit which rules are active in a given warehouse, and to trace how a rule propagates into restrictions, sort criteria, strategy membership, and consistencies. Typical reporting includes listing enabled rules by organization and reviewing weights to understand evaluation order.

Example — enabled rules for an organization:

• SELECT r.rule_id, r.type_code, r.rule_weight, r.enabled_flag
• FROM wms_rules_b r
• WHERE r.organization_id = :org_id
• AND r.enabled_flag = 'Y'
• ORDER BY r.rule_weight;

Example — joining to translations for user-facing names:

• SELECT b.rule_id, t.rule_name
• FROM wms_rules_b b, wms_rules_tl t
• WHERE b.rule_id = t.rule_id
• AND t.language = USERENV('LANG');

Note that in 12.2.x queries should account for ZD_EDITION_NAME, particularly when resolving rows across editions during patching cycles.

Related Objects

WMS_RULES_B is the hub of a tightly related rule configuration network. The most significant related objects are:

• WMS_RULES_TL — holds translated rule names and descriptions, joined on RULE_ID.
• WMS_RESTRICTIONS — defines restrictions attached to a rule, joined on RULE_ID.
• WMS_SORT_CRITERIA — defines sort criteria used by a rule, joined on RULE_ID.
• WMS_STRATEGY_MEMBERS — associates rules with execution strategies, joined on RULE_ID.
• WMS_RULE_CONSISTENCIES — governs consistency constraints between rules, joined on RULE_ID.
• WMS_TRANSACTIONS_TEMP — references RULE_ID during transactional processing.
• MTL_PARAMETERS — parent of ORGANIZATION_ID, providing organization context.
• WMS_PARAMETERS_B — referenced via QTY_FUNCTION_PARAMETER_ID.