Search Results allocation_mode

Overview

APPS.WMS_RULES_V is a Warehouse Management (WMS) dictionary view that presents the rule definitions used by the Warehouse Management rules engine in Oracle E-Business Suite 12.1.1 and 12.2.2. Rules drive the selection of picking, put-away, and replenishment strategies by evaluating weighted business conditions against candidate tasks or inventory. The view exists to expose a denormalized, user-readable form of the rule repository: meaning strings from MFG_LOOKUPS replace raw codes, and parameter/object identifiers are resolved to descriptive names for reporting and integration consumption. It is a UNION-based view, which means multiple rule families are surfaced through a single row structure with a stable column list, allowing reports, interfaces, and custom logic to query one object rather than several source tables. All rows are filtered so that only WMS-enabled rules are returned, and a synthetic flag indicates whether a rule applies across every organization.

Underlying Base Objects

The documented base objects referenced by WMS_RULES_V are BOM_STANDARD_OPERATIONS (synonym), CST_COST_GROUPS (synonym), MFG_LOOKUPS (view), WMS_LABEL_FORMATS (synonym), WMS_OBJECTS_VL (view), WMS_OP_PLANS_VL (view), WMS_PARAMETERS_VL (view), WMS_PARAMETER_PVT (package), and WMS_RULES_VL (view). WMS_RULES_VL is the primary rule definition table view and supplies row identity, organization, type code, name, weight, enabled and user-defined flags, and descriptive flexfield attributes. WMS_PARAMETERS_VL supplies the quantity/rule parameter context, joined on PARAMETER_ID, and the WMS_PARAMETER_PVT package function GETFLEXNAME resolves the parameter to a displayed flexfield name or column reference. WMS_OBJECTS_VL supplies the object name and description associated with the parameter. MFG_LOOKUPS is joined twice: once with LOOKUP_TYPE 'WMS_ACTION_TYPE' to translate TYPE_CODE into a meaning, and once with LOOKUP_TYPE 'WMS_RULE_ALLOCATION_MODE' to translate the allocation mode. WMS_OP_PLANS_VL, BOM_STANDARD_OPERATIONS, CST_COST_GROUPS, and WMS_LABEL_FORMATS contribute to the additional UNION branches that extend the rule view into operational plan and label scenarios.

Key Columns

• ROW_ID, RULE_ID: Unique row identifier and the rule identifier used for joins back to the base rule definition.
• ORGANIZATION_ID: Owning inventory organization; the value -1 denotes a rule available to all organizations, reflected by COMMON_TO_ALL_ORGS_FLAG set to 'Y'.
• TYPE_CODE, MEANING, DESCRIPTION: Rule action type code and its decoded lookup meaning and description.
• NAME, DESCRIPTION: User-facing rule name and rule description.
• QTY_FUNCTION_PARAMETER_ID: Identifier of the associated quantity function parameter.
• ENABLED_FLAG, USER_DEFINED_FLAG, WMS_ENABLED_FLAG: Status flags controlling whether the rule is active, seeded or user-created, and WMS-enabled.
• RULE_WEIGHT: Numeric weight used by the rules engine to rank competing rules.
• MIN_PICK_TASKS_FLAG: Indicates minimum pick task behavior for the rule.
• ALLOCATION_MODE_ID, ALLOCATION_MODE: Allocation mode identifier and decoded meaning, defaulted to 4 when null.
• PLAN_TYPE_ID, PLAN_TYPE_NAME, ACTIVITY_TYPE_ID, ACTIVITY_TYPE_NAME: Planning and activity attributes surfaced for plan-oriented rule branches; these are populated only where the corresponding UNION branch supplies data.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY: Descriptive flexfield segments carried through from the rule definition.

The literal expression TO_CHAR(NULL) PLAN_TYPE_NAME observed in the rule branch confirms that PLAN_TYPE_NAME is populated by a separate UNION branch, typically the WMS_OP_PLANS_VL branch. Because the name is synthetically produced, PLAN_TYPE_NAME has no dedicated base column in the rule tables and is derived for plan-related rules only.

Common Use Cases and Queries

Typical uses include auditing active rule sets per organization, reporting rule weights used in allocation and picking strategies, and validating that plan-specific rules expose a plan type. A representative query filtering on plan type name is:

• List active plan-level rules: SELECT rule_id, name, organization_id, common_to_all_orgs_flag, plan_type_name FROM apps.wms_rules_v WHERE plan_type_name IS NOT NULL AND enabled_flag = 'Y' ORDER BY organization_id, rule_weight;
• Report allocation modes: SELECT organization_id, name, allocation_mode, rule_weight FROM apps.wms_rules_v WHERE type_code IS NOT NULL ORDER BY organization_id;
• Identify global rules: SELECT rule_id, name, type_code, meaning FROM apps.wms_rules_v WHERE common_to_all_orgs_flag = 'Y';
• Search by plan type name: SELECT rule_id, name, plan_type_name FROM apps.wms_rules_v WHERE UPPER(plan_type_name) LIKE UPPER('%PICK%');

Queries should filter on ENABLED_FLAG and organization scope to avoid returning rules that are inactive or outside the intended operating unit. Because the view is UNION-based with literal NULL placeholders, columns such as PLAN_TYPE_NAME and ACTIVITY_TYPE_NAME should be treated as nullable and tested with IS NOT NULL rather than compared to empty strings. Joining RULE_ID back to the rule definition tables allows retrieval of additional detail not projected by the view.