Search Results module_hook_id

Overview

WMS_OP_PLAN_DETAILS_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the WMS (Warehouse Management) product family. It exposes detail-level operation information for warehouse operation plans, resolving the denormalized identifier columns in the base detail table into human-readable lookup meanings, zone names, location concatenated segments, and API hook package references. In practice the view functions as the reporting and integration surface for downstream warehouse execution logic, because it flattens the many foreign-key style code columns stored on WMS_OP_PLAN_DETAILS into the descriptive values that functional users, reports, and mobile device integrations require.

The object is documented with STATUS = VALID, and its referenced base objects include a mix of synonyms, keys flex views, translatable tables, and lookup views. This confirms that the view is a read-only construct intended for querying rather than direct DML.

Underlying Base Objects

The documented base objects for this view are WMS_OP_PLAN_DETAILS (accessed via synonym), WMS_OP_PLANS_B (synonym), WMS_OP_PLANS_VL (view), MFG_LOOKUPS (view), MTL_ITEM_LOCATIONS_KFV (view), WMS_API_HOOK_CALLS (synonym), and WMS_ZONES_TL (synonym). The primary driving table is WMS_OP_PLAN_DETAILS, aliased D in the view text, which supplies operation plan detail rows including operation type, sequence, selection criteria, and the descriptor flexfield attributes ATTRIBUTE1 through ATTRIBUTE15. WMS_OP_PLANS_B is joined via OPERATION_PLAN_ID to supply plan-level context such as ACTIVITY_TYPE_ID, which the view uses in a DECODE to select the appropriate location destination suggestion API. WMS_OP_PLANS_VL provides the translatable plan name, exposed as SUBSEQUENT_OP_PLAN_NAME, along with SUBSEQUENT_OP_PLAN_ID. MFG_LOOKUPS is referenced multiple times (aliases ML1 through ML10) against the lookup types WMS_OP_DEST_SELECTION_MODE and related WMS lists, translating codes such as DROP_LPN_OPTION, CONSOLIDATION_METHOD_ID, zone/sub/location/LPN suggestion methods, and material group rules into their meanings. MTL_ITEM_LOCATIONS_KFV supplies the concatenated location segments via LOC_CONCATENATED_SEGMENTS. WMS_ZONES_TL supplies ZONE_NAME. WMS_API_HOOK_CALLS provides the LOC_DEST_SUG_API and LPN_DEST_SUG_API package entry points used at runtime.

Key Columns

• OPERATION_PLAN_ID / OPERATION_PLAN_DETAIL_ID — primary and detail identifiers that uniquely locate a row within the planning hierarchy.
• OPERATION_TYPE, OPERATION_SEQUENCE, OPERATION_NAME — the operation classification and ordering; OPERATION_NAME is resolved from lookups for display.
• BULK_PICK_TYPE, DROP_LPN_OPTION, DROP_LPN_OPTION_NAME — LPN handling behavior, with the descriptive name joined from lookups.
• ZONE_SELECTION_CRITERIA, PRE_SPECIFIED_ZONE_ID, ZONE_NAME — destination zone selection rules and the resulting zone.
• SUB_SELECTION_CRITERIA, PRE_SPECIFIED_SUB_CODE — destination subinventory selection parameters.
• LOC_SELECTION_CRITERIA, PRE_SPECIFIED_LOC_ID, LOC_CONCATENATED_SEGMENTS — location selection rules and the resolved flexfield location string.
• LPN_SELECTION_CRITERIA, LPN_SELECTION_API_ID — LPN selection parameters.
• DEST_ZONE_SUG_METHOD, DEST_SUB_SUG_METHOD, DEST_LOC_SUG_METHOD, DEST_LPN_SUG_METHOD — human-readable destination suggestion methods derived from lookups.
• LOC_DEST_SUG_API, LPN_DEST_SUG_API — the API hook names used to determine destination locations and LPNs.
• SUBSEQUENT_OP_PLAN_NAME / SUBSEQUENT_OP_PLAN_ID — the next operation plan in the sequence, supporting chained execution.
• CONSOLID_METHOD_NAME, CONSOLIDATION_METHOD_ID — consolidation strategy details.
• IS_IN_INVENTORY, SYSTEM_DISPATCHED, OP_SEGMENT_COMPLETED, WAIT_FOR_GROUP_COMPLETION — status flags controlling execution behavior.
• Attribute flexfields and audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and ATTRIBUTE_CATEGORY/ATTRIBUTE1-15.

Common Use Cases and Queries

The view is used to drive warehouse operation plan configuration reports, to verify destination selection methods, and to extract the API hook identifiers required by mobile or integration components. A typical query returning the descriptive operation information for a given plan is:

SELECT operation_plan_id, operation_sequence, operation_name, drop_lpn_option_name, dest_zone_sug_method, dest_loc_sug_method, loc_dest_sug_api, zone_name FROM apps.wms_op_plan_details_v WHERE operation_plan_id = :plan_id ORDER BY operation_sequence;

To inspect how a plan chains into a subsequent plan:

SELECT operation_plan_name, subsequent_op_plan_name, subsequent_op_plan_id FROM apps.wms_op_plan_details_v WHERE subsequent_op_plan_id IS NOT NULL;

Because the view resolves lookup meanings and API hook identifiers at query time, it is well suited to diagnostic and reconciliation queries, provided callers treat it as read-only and rely on the underlying base tables for any DML.