Results for “use_for_put_rest_flag”

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

Overview

WMS_OBJECTS_RULE_LOV_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the WMS (Warehouse Management) product. It is documented as a "WMS business object LOV view," meaning its primary purpose is to supply the list of values (LOV) that drives object selection in Warehouse Management setup and rule configuration screens. The view consolidates each WMS business object with the aggregate set of rule applicability flags defined for it, so that callers can determine, in a single query, which rule types and operations an object participates in.

The view is registered in APPS with a VALID status in both ETRM 12.1.1 and 12.2.2. Its identifier and behavior are stable across these releases, since it is defined purely over two localized WMS views and exposes no version-dependent logic. The name reflects its dual role: "OBJECTS" identifies the business object dimension, "RULE" identifies the rule applicability metadata, and "LOV" confirms its intended use as a selection source rather than a transactional object.

Underlying Base Objects

WMS_OBJECTS_RULE_LOV_V is defined over two documented base objects, both of which are themselves views:

• WMS_OBJECTS_VL — the translated (VL) object view, providing OBJECT_ID, NAME, and DESCRIPTION for each WMS business object.
• WMS_PARAMETERS_VL — the translated parameters view, providing the per-object rule flag columns that are aggregated by the query.

The two are joined on OBJECT_ID (WOVL.OBJECT_ID = WPVL.OBJECT_ID), and the result set is grouped by WPVL.OBJECT_ID, WOVL.NAME, and WOVL.DESCRIPTION. Because the parameters view may hold multiple rows per object, the view applies MAX() to each applicability flag and AVG() to the RULE_SUBTYPE_CODE, effectively collapsing the parameter rows into one summary row per business object.

Key Columns

The view exposes the object identity columns (OBJECT_ID, OBJECT_NAME, OBJECT_DESCRIPTION) plus the aggregated rule applicability flags. The flags of interest to rule and labeling configuration are:

• USE_FOR_PUT_SORT_FLAG, USE_FOR_PUT_REST_FLAG, USE_FOR_PUT_QTYF_FLAG — indicate whether the object is used for putaway sort, putaway restriction, and putaway quantity fulfillment rules respectively.
• USE_FOR_PICK_SORT_FLAG, USE_FOR_PICK_REST_FLAG, USE_FOR_PICK_QTYF_FLAG — the corresponding flags for picking operations.
• USE_FOR_TT_ASSN_FLAG — task type association applicability.
• USE_FOR_LABEL_REST_FLAG — the flag matching the user's search term, indicating whether the object can be used as a label restriction target in warehouse rule configuration.
• USE_FOR_CG_REST_FLAG, USE_FOR_PICK_CONSIST_FLAG, USE_FOR_OP_SELECTION_FLAG — consolidation group restriction, pick consistency, and operation selection applicability.
• RULE_SUBTYPE_CODE — an average of the numeric subtype code for objects valid for operation selection, computed with NVL(..., 1.5) so that unflagged rows are excluded from the average.

Common Use Cases and Queries

The view is most frequently used to populate LOVs in Warehouse Management rule setup and to drive validation logic that must confirm an object supports a given rule category before it is offered to the user. A representation query that filters on the user's term of interest would take the form:

• SELECT object_id, object_name, use_for_label_rest_flag FROM apps.wms_objects_rule_lov_v WHERE use_for_label_rest_flag = 'Y';

To review all applicability data for a specific object:

• SELECT object_name, use_for_put_rest_flag, use_for_pick_rest_flag, use_for_label_rest_flag, use_for_cg_rest_flag FROM apps.wms_objects_rule_lov_v WHERE object_id = :p_object_id;

Because the view aggregates with MAX(), any non-null 'Y' on any underlying parameter row surfaces as 'Y' at the object level. Consumers should remember that the RULE_SUBTYPE_CODE column is an average and therefore informational rather than a discrete identifier, and that the descriptive NAME and DESCRIPTION are drawn from the translated object view, so results respect the session language of the calling user.