Results for “over_allocation_mode”

22 results




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

Overview

WMS_STRATEGIES_B is the base table in the Oracle Warehouse Management (WMS) schema that stores the header definitions for warehouse execution strategies in Oracle E-Business Suite 12.1.1 and 12.2.2. A "strategy" in this context represents an ordered rule set used by the WMS engine to direct put-away, picking, and replenishment operations within a specific warehouse organization. Each row defines a named, organization-scoped strategy along with its type, enablement status, over-allocation behavior, and tolerance thresholds.

The table resides in the WMS schema and is owned by the WMS product. Its primary key, WMS_STRATEGIES_B_PK, is defined on STRATEGY_ID, which serves as the surrogate identifier for each strategy. A secondary unique index, WMS_STRATEGIES_B_U1, is defined on (STRATEGY_ID, ZD_EDITION_NAME), reflecting the Edition-Based Redefinition (EBR) model introduced in 12.2.x and backported patterns; the ZD_EDITION_NAME column supports online patching by isolating edition-specific rows. From a Data Vault modeling perspective, this table behaves as a hub-leaning structure: STRATEGY_ID is a stable business key referenced by multiple downstream dependents, while descriptive and contextual attributes are distributed across sibling tables.

Key Information Stored

The table contains 30 documented columns. The most operationally significant are:

  • STRATEGY_ID — The surrogate primary key, uniquely identifying each warehouse strategy.
  • ORGANIZATION_ID — Foreign key to MTL_PARAMETERS, scoping the strategy to a specific inventory organization (warehouse).
  • TYPE_CODE — Indicates the strategy category, distinguishing put-away, picking, or related execution behaviors.
  • ENABLED_FLAG — Controls whether the strategy is active and eligible for use by the WMS engine.
  • WMS_ENABLED_FLAG — Additional WMS-specific enablement indicator.
  • USER_DEFINED_FLAG — Marks whether the strategy was seeded by Oracle or created by the customer.
  • OVER_ALLOCATION_MODE — Determines how over-allocation is handled during picking.
  • TOLERANCE_VALUE — Numeric threshold applied to strategy execution rules.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle DFF (Descriptive Flexfield) columns allowing customer-defined extensions.
  • ZD_EDITION_NAME — Edition identifier supporting EBR and online patching in 12.2.x.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

The translated/descriptive text for each strategy (name and description) resides in the companion table WMS_STRATEGIES_TL, not in the base table.

Common Use Cases and Queries

Consultants and developers query WMS_STRATEGIES_B to enumerate the strategies defined for a warehouse, to troubleshoot why a pick or put-away behaved unexpectedly, and to build reports on strategy configuration. A typical query joins the base table to its translation table for the strategy name:

  • Listing enabled pick strategies for an organization: SELECT s.strategy_id, t.strategy_name FROM wms_strategies_b s, wms_strategies_tl t WHERE s.strategy_id = t.strategy_id AND s.organization_id = :org AND s.type_code = 'PICK' AND s.enabled_flag = 'Y';
  • Identifying which strategies are actively assigned to subinventories or locators via WMS_STRATEGY_ASSIGNMENTS.
  • Auditing custom (user-defined) strategies using USER_DEFINED_FLAG to separate seeded Oracle content from customer configuration.
  • Reviewing OVER_ALLOCATION_MODE and TOLERANCE_VALUE settings when investigating allocation discrepancies.
  • Extracting DFF attribute values (ATTRIBUTE1–ATTRIBUTE15) for downstream integration or analytics.

Related Objects

The following objects are most significant in relation to WMS_STRATEGIES_B, based on documented foreign key relationships:

  • MTL_PARAMETERS — Referenced via WMS_STRATEGIES_B.ORGANIZATION_ID; defines the owning inventory organization.
  • WMS_STRATEGIES_TL — Translation table joined on STRATEGY_ID; supplies the strategy name and description.
  • WMS_STRATEGY_ASSIGNMENTS — References STRATEGY_ID; maps strategies to subinventories, locators, or other warehouse entities.
  • WMS_STRATEGY_MEMBERS — References STRATEGY_ID; holds the individual rule members that compose the strategy.
  • MTL_TXN_REQUEST_LINES — References STRATEGY_ID twice, via PICK_STRATEGY_ID and PUT_AWAY_STRATEGY_ID, linking move-order lines to the strategy applied during execution.

Together, these related objects form the complete strategy framework: header definition, translated text, assignments, and rule membership, all anchored by the STRATEGY_ID hub key.