Search Results parameter_description

Overview

WMS_PARAMETERS_LOV_V is a read-only Oracle E-Business Suite view owned by the APPS schema and shipped as part of the Warehouse Management (WMS) product family. It supplies the rows displayed by the Warehouse Management parameter list of values (LOV), the selection control that lets a user pick a valid parameter when configuring warehouse execution rules, label formats, cost group rules, put-away and picking strategies, and operation-selection criteria. The view projects a curated set of columns from the warehouse parameter definition model, adding runtime-resolved values such as the flexfield name and data type code that are not stored directly on the driving parameter table. Because it is a view rather than a table, it exposes no persistent data of its own; every row is computed at query time and reflects the current configuration in WMS_PARAMETERS_VL, WMS_OBJECTS_VL, and WMS_DB_OBJECTS. Its status is VALID in both 12.1.1 and 12.2.2, and it is documented in ETRM as the canonical source for parameter LOV lookups. Reporting and integration code that needs the same list of selectable parameters presented to an end user should query this view rather than reconstructing the join logic, since the availability filter encoded in the view is otherwise easy to reproduce incorrectly.

Underlying Base Objects

The view is defined over three referenced objects plus one package that supplies scalar functions used in the projection:

• WMS_PARAMETERS_VL (VIEW) — the primary driving object, aliased WPVL. It provides PARAMETER_ID, NAME, DESCRIPTION, OBJECT_ID, DB_OBJECT_ID, DB_OBJECT_REF_TYPE_CODE, PARAMETER_TYPE_CODE, DATA_TYPE_CODE, the flexfield attributes, and the ten USE_FOR_* usage flags.
• WMS_OBJECTS_VL (VIEW) — aliased WOVL, joined on OBJECT_ID = WPVL.OBJECT_ID. It contributes the object NAME and DESCRIPTION that identify the business object a parameter belongs to.
• WMS_DB_OBJECTS (SYNONYM) — aliased WDO, outer-joined on WPVL.DB_OBJECT_ID = WDO.DB_OBJECT_ID (+). The outer join is deliberate: parameters that are not bound to a database column still appear, with TABLE_ALIAS and TABLE_NAME returned as NULL.
• WMS_PARAMETER_PVT (PACKAGE) — supplies GETFLEXNAME, GETFLEXDATATYPECODE, and IFFLEXTHENAVAILABLE. The latter is applied as a row filter that must evaluate to 'Y', restricting output to parameters that are genuinely available for LOV selection.

No base tables are referenced directly; all access is mediated through the synonym and the two definition views.

Key Columns

The view exposes twenty-two columns. PARAMETER_ID is the unique surrogate key, with PARAMETER_NAME and PARAMETER_DESCRIPTION providing the user-facing labels. OBJECT_ID, OBJECT_NAME, and OBJECT_DESCRIPTION place each parameter in the context of the warehouse object it configures. TABLE_ALIAS, TABLE_NAME, and COLUMN_NAME describe the database binding; where COLUMN_NAME is NULL the view substitutes the literal 'EXPRESSION', indicating the parameter resolves through an expression rather than a physical column. DATA_TYPE_CODE carries the datatype resolved by WMS_PARAMETER_PVT.GETFLEXDATATYPECODE. The remaining ten columns — USE_FOR_PUT_SORT_FLAG, USE_FOR_PUT_REST_FLAG, USE_FOR_PUT_QTYF_FLAG, USE_FOR_PICK_SORT_FLAG, USE_FOR_PICK_REST_FLAG, USE_FOR_PICK_QTYF_FLAG, USE_FOR_TT_ASSN_FLAG, USE_FOR_LABEL_REST_FLAG, USE_FOR_CG_REST_FLAG, USE_FOR_PICK_CONSIST_FLAG, and USE_FOR_OP_SELECTION_FLAG — are Y/N indicators showing which functional areas permit the parameter.

Common Use Cases and Queries

The most frequent use is populating an LOV or validating a parameter selection. A basic listing ordered for presentation:

• SELECT parameter_id, parameter_name, parameter_description FROM apps.wms_parameters_lov_v ORDER BY parameter_name;

To find parameters usable for picking strategies only:

• SELECT object_name, parameter_name, data_type_code FROM apps.wms_parameters_lov_v WHERE use_for_pick_sort_flag = 'Y' OR use_for_pick_rest_flag = 'Y';

To distinguish column-bound parameters from expression-based ones:

• SELECT parameter_id, column_name, table_name FROM apps.wms_parameters_lov_v WHERE column_name <> 'EXPRESSION';

Because the view already embeds the IFFLEXTHENAVAILABLE filter and the outer join to WMS_DB_OBJECTS, queries against it return only selectable parameters; downstream code should not re-apply equivalent predicates, as doing so risks excluding valid flexfield-backed entries.