Results for “rule_type_meaning”

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

Overview

WMS_SORT_CRITERIA_V is a Warehouse Management (WMS) reporting view owned by the APPS schema. It presents the rules that govern the ordered evaluation of parameters during warehouse execution operations such as picking, put-away, and task sequencing. Each row represents one sort criterion — an instruction to order a set of candidate records according to a specified parameter and sort direction within a named rule. The view consolidates the sort criterion itself with the parent rule definition, the parameter being sorted, the object the parameter belongs to, and the decode values for the rule type and sort order. This makes it suitable for operational reporting, implementation diagnostics, and integration extracts where the full rule context is required without joining four or five separate base objects manually. Because the view resolves the USER_DEFINED_FLAG on the parent rule (exposed as RULE_USER_DEFINED_FLAG), it supports the common requirement of isolating seeded versus customer-created rules — the flag most frequently queried by implementers investigating why a user-defined sort rule is or is not being applied by the WMS engine.

Underlying Base Objects

The view is defined over a mix of base tables, translated views, and a PL/SQL package function. The central table is WMS_SORT_CRITERIA, referenced in the APPS schema through a synonym; it supplies the row identity, rule identifier, sequence, parameter identifier, sort order code, audit columns, and the fifteen descriptive flexfield attributes. WMS_RULES_VL provides the rule name, description, organization, user-defined flag, and type code. WMS_PARAMETERS_VL supplies the parameter name, description, and object identifier, while WMS_OBJECTS_VL resolves the object name and description. Two independent joins to MFG_LOOKUPS decode the rule type (lookup type WMS_ACTION_TYPE) and the sort order (lookup type WMS_SORT_ORDER). Finally, the WMS_PARAMETER_PVT package function GETFLEXNAME is invoked to derive the parameter's display flex name from its flexfield attributes, allowing the view to present a human-readable parameter label rather than a raw column reference.

Key Columns

• ROW_ID, RULE_ID, SEQUENCE_NUMBER, PARAMETER_ID — Identify the criterion row, its parent rule, its ordinal position within the rule, and the parameter being sorted.
• RULE_NAME, RULE_DESCRIPTION, RULE_ORGANIZATION_ID — Descriptive attributes of the parent rule. A null organization typically indicates a global rule.
• RULE_USER_DEFINED_FLAG, RULE_TYPE_CODE, RULE_TYPE_MEANING, RULE_TYPE_DESCRIPTION — Distinguish seeded from user-defined rules and decode the rule action type.
• PARAMETER_NAME, PARAMETER_DESCRIPTION, OBJECT_ID, OBJECT_NAME, OBJECT_DESCRIPTION — The parameter and its owning object, resolved through the translated views and the GETFLEXNAME function.
• ORDER_CODE, ORDER_MEANING, ORDER_DESCRIPTION — The sort direction decoded from MFG_LOOKUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit trail for change tracking and troubleshooting.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments on the underlying sort criterion record.

Common Use Cases and Queries

Typical uses include auditing the sort sequence applied to a rule, reporting all user-defined sort criteria for an organization, and tracing which object and parameter drive a given ordering step. The following query lists user-defined criteria with their decoded order direction:

SELECT rule_name, rule_organization_id, sequence_number, parameter_name,
  object_name, order_meaning, rule_user_defined_flag
FROM apps.wms_sort_criteria_v
WHERE rule_user_defined_flag = 'Y'
ORDER BY rule_name, sequence_number;

To examine the complete sort sequence for one rule, filter on RULE_ID and order by SEQUENCE_NUMBER, returning PARAMETER_NAME, OBJECT_NAME, and ORDER_MEANING. Because the view performs its own joins to the translated views and lookup tables, custom SQL should avoid redundant joins and rely on the decoded columns directly. Filtering on ORGANIZATION_ID (or its rule equivalent) is advisable in multi-organization deployments to prevent cross-organization rows from appearing in the result set.