Results for “wms_op_dest_selection_mode”

10 results




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

Overview

APPS.WMS_OP_PLAN_DETAILS_V is a reporting and integration view in the Oracle E-Business Suite Warehouse Management System (WMS) module. It exposes the detail-level configuration records of operation plans, where an operation plan defines how warehouse execution activities — such as picking, putaway, replenishment, and cross-docking — are sequenced and dispatched. Each row in this view describes one operation plan detail: its operation type, sequence, and the selection strategies used to determine destination zones, subinventory codes, locators, and LPNs during execution.

The view's primary design goal is to resolve internal foreign-key identifiers into user-readable meanings. Rather than returning raw lookup codes and API identifiers, it joins to MFG_LOOKUPS and translates the destination suggestion methods, drop-LPN options, material grouping rules, and consolidation methods into their displayable meanings. It also derives context values such as the operation name and the destination suggestion API from the parent operation plan. This makes the view suitable for inquiry screens, concurrent-program extracts, and downstream integrations that must interpret plan behavior without re-implementing lookup resolution. Because the view is read-mostly and joins several base objects, it is intended for querying rather than direct DML; modifications must be performed against the underlying WMS_OP_PLAN_DETAILS table.

Underlying Base Objects

The view is defined over WMS_OP_PLAN_DETAILS (exposed as a synonym), which supplies the primary detail columns including OPERATION_PLAN_ID, OPERATION_PLAN_DETAIL_ID, OPERATION_TYPE, OPERATION_SEQUENCE, and the selection criteria and API identifiers. It joins WMS_OP_PLANS_B (synonym), the base operation plan table, to obtain ACTIVITY_TYPE_ID, which drives the decode that yields LOC_DEST_SUG_API. WMS_OP_PLANS_VL (view) is referenced in the definition and provides the multi-language operation plan context used to derive the subsequent operation plan name and identifier, while its relationship supplies OPERATION_NAME via the OPERATION_TYPE lookup.

MFG_LOOKUPS (view) is joined multiple times to resolve lookup types such as WMS_OP_DEST_SELECTION_MODE for zone, subinventory, locator, and LPN suggestion methods, along with the drop-LPN option, material group rules, and consolidation method. WMS_ZONES_TL (synonym) provides the translated ZONE_NAME for the pre-specified zone. WMS_API_HOOK_CALLS (synonym) supplies the locator and LPN destination suggestion API hooks selected by ACTIVITY_TYPE_ID. MTL_ITEM_LOCATIONS_KFV (view) supplies the concatenated flexfield segments for the location (LOC_CONCATENATED_SEGMENTS), resolved through an outer join. In ETRM 12.2.2 all of these objects are documented as the referenced base set for the view.

Key Columns

Common Use Cases and Queries

The view is commonly used to audit plan configuration, to document how destinations are selected for a given operation, and to feed integration layers that drive warehouse execution.

  • Inventory the operations configured for a plan and their execution order.
  • Report the destination suggestion method and API in effect for each operation.
  • Extract plan details for migration or configuration comparison between environments.
  • Trace chained plans and consolidation methods for replenishment or cross-dock flows.
SELECT operation_plan_id,
       operation_plan_detail_id,
       operation_name,
       operation_sequence,
       dest_zone_sug_method,
       dest_sub_sug_method,
       dest_loc_sug_method,
       dest_lpn_sug_method,
       consolidation_method_id,
       SUBSEQUENT_OP_PLAN_NAME
FROM   apps.wms_op_plan_details_v
WHERE  operation_plan_id = :p_plan_id
ORDER  BY operation_sequence;
SELECT v.operation_plan_id,
       v.zone_name,
       v.loc_concatenated_segments,
       v.loc_dest_sug_API,
       v.lpn_dest_sug_API
FROM   apps.wms_op_plan_details_v v
WHERE  v.loc_dest_sug_API IS NOT NULL;

Because the view performs multiple lookup joins and outer joins, queries should filter on OPERATION_PLAN_ID or OPERATION_TYPE to limit the result set, and should be executed during off-peak periods when full scans are unavoidable.