Search Results supply_crossdock

Overview

WMS_SELECTION_CRITERIA_TXN_V is an APPS-owned database view within the Warehouse Management (WMS) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It exposes selection criteria records used by the WMS rules engine, which drives putaway, picking, task, label, costing, and crossdocking decisions in warehouse operations. Rather than storing data itself, the view projects transactional selection criteria from the underlying WMS_SELECTION_CRITERIA_TXN table and enriches each row with decoded and human-readable values resolved through the WMS_RULES_WORKBENCH_PVT package.

The view's primary role is reporting and integration. It converts numeric codes—rule types, item types, ABC classes, category sets, customer, vendor, freight, and organization identifiers—into display-friendly names and codes. This makes the view well suited for operational reporting, troubleshooting rule configuration, and feeding external or custom processes that must interpret WMS rule assignments without reproducing the decoding logic. Because several transformations depend on package function calls, the view functions as a query convenience layer over the workbench presentation logic.

Underlying Base Objects

The documented base objects referenced by the view are WMS_SELECTION_CRITERIA_TXN (SYNONYM), WMS_RULES_B (SYNONYM), WMS_STRATEGIES_B (SYNONYM), and the WMS_RULES_WORKBENCH_PVT package. WMS_SELECTION_CRITERIA_TXN is the driving source: each row corresponds to a staging assignment of selection criteria identified by STG_ASSIGNMENT_ID and ordered by SEQUENCE_NUMBER. WMS_RULES_B supplies rule definitions associated with the assignment, WMS_STRATEGIES_B provides the strategy context against which rules are grouped, and WMS_RULES_WORKBENCH_PVT supplies the PL/SQL functions that resolve descriptive values for the decoded columns.

Key Columns

• STG_ASSIGNMENT_ID / SEQUENCE_NUMBER — Unique assignment identifier and evaluation order for criteria within a rule.
• RULE_TYPE_CODE / RULE_TYPE — Numeric code decoded into PICK, PUTAWAY, TASK, LABEL, COST_CROUP, SUPPLY_CROSSDOCK, or DEMAND_CROSSDOCK.
• RETURN_TYPE_CODE / RETURN_TYPE_NAME — Return type and its resolved name via GET_RETURN_TYPE_NAME.
• INVENTORY_ITEM_ID / ITEM / ITEM_TYPE / ITEM_TYPE_NAME — Item identifier, resolved item description via GET_ITEM, and the item type with its decoded name via GET_ITEM_TYPE_NAME, which is the column most relevant to the "item_type_name" search.
• FROM_ORGANIZATION_ID / FROM_ORGANIZATION_CODE, TO_ORGANIZATION_ID / TO_ORGANIZATION_CODE — Source and destination organizations with resolved codes.
• FROM_SUBINVENTORY_NAME / TO_SUBINVENTORY_NAME — Subinventory scope for the criteria.
• CUSTOMER_ID / CUSTOMER_NAME, VENDOR_ID — Party identifiers and resolved names.
• FREIGHT_CODE / FREIGHT_CODE_NAME — Freight classification and resolved name.
• ABC_CLASS_ID / ABC_GROUP_CLASS_NAME, CATEGORY_SET_ID / CATEGORY_ID / CATEGORY_SET_NAME — ABC and category-set classification attributes.
• ORDER_TYPE_ID / ORDER_TYPE_NAME — Order type and its resolved name.
• ENABLED_FLAG, EFFECTIVE_FROM/TO, DATE_TYPE_CODE/FROM/TO — Enablement and effective-dating controls.

Common Use Cases and Queries

Typical uses include auditing which items, item types, or categories a rule targets; verifying effective-date and enablement status; and extracting rule criteria for migration or external planning systems. To retrieve criteria by item type name and rule category:

• SELECT stg_assignment_id, sequence_number, rule_type, item, item_type_name, from_organization_code, from_subinventory_name FROM wms_selection_criteria_txn_v WHERE rule_type = 'PUTAWAY' AND item_type_name = :p_item_type_name ORDER BY stg_assignment_id, sequence_number;
• SELECT stg_assignment_id, rule_type, from_organization_code, customer_name, category_set_name, abc_group_class_name, enabled_flag FROM wms_selection_criteria_txn_v WHERE from_organization_id = :p_org_id AND enabled_flag = 'Y' ORDER BY rule_type, sequence_number;

Because some columns are derived through WMS_RULES_WORKBENCH_PVT calls, queries returning large result sets can incur extra PL/SQL overhead; restricting by organization, assignment, or rule type improves performance.