Search Results planning_method

Overview

WMS_WP_PLANNING_CRITERIA_VL is a language-dependent (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the Warehouse Management (WMS) product family. It exposes warehouse planning criteria configuration in a translated form, resolving the internal numeric key into a user-facing descriptive name based on the session language. The view is a standard seed-data object used by Oracle Warehouse Management's wave planning, picking, and labor management engines, and it serves as a canonical reporting and integration surface for planning criteria metadata. The _VL suffix indicates that the view joins a base (_B) table to a translation (_TL) table and returns only the row corresponding to USERENV('LANG'), ensuring a single language-specific row per planning criteria record. In release 12.1.1 and 12.2.2, the underlying tables and view definition are functionally identical; the primary differences between the two releases relate to platform and online patching architecture rather than to the structure of this particular view.

Underlying Base Objects

The view is defined over two documented base objects, referenced through synonyms pointing to the underlying WMS tables:

• WMS_WP_PLANNING_CRITERIA_B — the base table holding all language-independent attributes of a planning criteria record, keyed by PLANNING_CRITERIA_ID.
• WMS_WP_PLANNING_CRITERIA_TL — the translation table supplying the descriptive PLANNING_CRITERIA name, keyed by PLANNING_CRITERIA_ID and LANGUAGE.

The view text joins the two tables on B.PLANNING_CRITERIA_ID = T.PLANNING_CRITERIA_ID and filters on T.LANGUAGE = USERENV('LANG'). It also exposes the base table ROWID as ROW_ID. The join is an inner join, so a criteria ID that lacks a translation row for the session language will not appear in the result set — a subtlety worth noting when performing validation queries.

Key Columns

Because the view simply selects from the two base objects, all non-translated columns come from _B and the translated name comes from _TL. Important columns include:

• PLANNING_CRITERIA_ID — primary key and the identifier referenced by other WMS subsystems. This is the numeric counterpart to the descriptive name.
• PLANNING_CRITERIA — the language-specific descriptive name of the criteria set.
• CROSSDOCK_CRITERIA_ID and CROSSDOCK_CRITERIA — the crossdocking criteria identifier and its associated value, used to control crossdock planning behaviour. CROSSDOCK_CRITERIA_ID is the exact column the user searched for; it stores the internal ID linking a planning criteria configuration to a crossdock rule or type.
• PLANNING_METHOD and TYPE — the planning method and criteria type (e.g., picking vs. replenishment context).
• ALLOCATION_METHOD — the allocation strategy applied.
• PICKING_SUBINVENTORY and DESTINATION_SUBINVENTORY — default subinventories used by the planning engine.
• BULK_LABOR_PLANNING_FLAG, ENABLE_LABOR_PLANNING, LABOR_SETUP_MODE, TIME_UOM, DEPARTMENT_CODE, DEPARTMENT_ID — labor planning and timing attributes.
• Flag columns — BACKORDER_FLAG, REJECT_ORDER_LINE_FLAG, REJECT_ALL_LINES_SHIPSET_FLAG, REJECT_ALL_LINES_MODEL_FLAG, REJECT_ORDER_FLAG, RESERVE_STOCK_FLAG, AUTO_CREATE_DELIVERIES_FLAG, CREDIT_CHECK_HOLD_FLAG.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include validating which planning criteria reference a given crossdock configuration, driving custom reports that display planning rules in the user's language, and integrating WMS planning behaviour into downstream applications. A representative query retrieves all criteria associated with a specific crossdock criteria ID:

• SELECT planning_criteria_id, planning_criteria, planning_method, crossdock_criteria_id, crossdock_criteria FROM apps.wms_wp_planning_criteria_vl WHERE crossdock_criteria_id IS NOT NULL ORDER BY planning_criteria;
• SELECT planning_criteria_id, planning_criteria, allocation_method, picking_subinventory, destination_subinventory FROM apps.wms_wp_planning_criteria_vl WHERE picking_subinventory = :sub;
• SELECT planning_criteria_id, planning_criteria FROM apps.wms_wp_planning_criteria_vl WHERE crossdock_criteria_id = :crossdock_id;

Because the view enforces the session-language join, applications and reports obtain the correct descriptive name without manually joining the translation table. When a criteria ID is expected but the row is missing, verify the LANGUAGE value and confirm that a corresponding _TL translation row exists.