Search Results wms_selection_criteria_txn




Overview
Explore in AI Chat

Overview

The WMS_SELECTION_CRITERIA_TXN table is a Warehouse Management (WMS) repository object that stores the selection criteria and assignment matrix rules used to drive rule-based transaction processing within Oracle E-Business Suite. In the WMS module, this table acts as the governing configuration storefront that determines how inbound and outbound inventory transactions are routed, classified, or assigned to specific handling paths based on a rich set of dimension attributes. The table is owned by the WMS schema and is documented as VALID across both Oracle EBS 12.1.1 and 12.2.2 releases, holding approximately 41 columns in its documented physical schema.

From a data-modeling perspective, the ETRM heuristic classification for this object is standalone. This suggests that the table functions as an independent rule-definition entity rather than a classic Data Vault hub, link, or satellite. It is a configuration master whose rows participate as a referenced parent in downstream rule evaluation logic, but it does not sit on the core transactional fact path itself. Analysts modeling the WMS rule engine may therefore treat it as a reference/dimension-style entity.

Key Information Stored

The table's primary key is WMS_SELECTION_CRITERIA_TXN_PK1, defined on the composite of FROM_ORGANIZATION_ID, RULE_TYPE_CODE, and SEQUENCE_NUMBER. A separate unique index (documented as WMS_SELECTION_CRITERIA_TXN_PK1 on STG_ASSIGNMENT_ID) also appears in the business-key candidate list, indicating that the staging assignment identifier behaves as a unique business key in the documented schema.

The most significant columns include:

Common Use Cases and Queries

Typical reporting scenarios include auditing which rules are enabled for a given organization, tracing the rule sequence for a rule type, and reconciling rules against their referenced ABC classes or order types. A common query pattern retrieves active, currently effective rules for a source organization:

  • SELECT rule_type_code, sequence_number, from_organization_id, enabled_flag — filter by FROM_ORGANIZATION_ID, ENABLED_FLAG = 'Y', and date coverage between EFFECTIVE_FROM and EFFECTIVE_TO.
  • Join to MTL_ABC_CLASSES on ABC_CLASS_ID to report rule-to-class mappings.
  • Join to SO_ORDER_TYPES_115_ALL on ORDER_TYPE_ID to identify order-type-driven assignment rules.

Related Objects

The documented foreign-key relationships establish the table's dependency surface. The most significant related objects are:

  • MTL_ABC_ASSIGNMENT_GROUPS — referenced via ASSIGNMENT_GROUP_ID.
  • MTL_ABC_CLASSES — referenced via ABC_CLASS_ID.
  • SO_ORDER_TYPES_115_ALL — referenced via ORDER_TYPE_ID.
  • MTL_TXN_SOURCE_TYPES — referenced via TRANSACTION_SOURCE_TYPE_ID.
  • Inventory and category master tables implied by INVENTORY_ITEM_ID and CATEGORY_ID.