Search Results create_batch_record

Overview

WMS_WAVE_PLANNING_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, serving as the internal engine behind Warehouse Management System (WMS) wave planning and wave release. Wave planning groups released outbound demand lines into logical picking waves and then into executable batches, enabling warehouse operations to sequence picking, staging, and shipment activities against labor, resource, and order priority constraints. The package carries the PVT classification, meaning its members are not a public API: it is invoked by the WMS wave planning concurrent programs, by WMS HTML user interface flows, and by other internal APPS packages, but Oracle does not expose its signatures for customer extension.

The original source header is WMSWVPVS.pls 120.18.12020000.2, last revised 2013. Applying to both 12.1.1 and 12.2.2, the package is identical in structure; the 12.2.x file system re-homing changes only the deployment path. Wave planning logic is functionally shared across this release continuum.

Key Procedures and Functions

Of the 62 documented procedures and functions, the following define the public shape of the wave workflow:

• PLAN_WAVE and PLAN_WAVE_CP / CALL_PLAN_WAVE_CP — Core planning drivers. PLAN_WAVE performs the online planning logic; the CP variants wrap it for concurrent execution.
• RELEASE_ONLINE and RELEASE_BATCH_CP — Drive wave and batch release, converting planned wave lines into pickable tasks.
• CREATE_BATCH_RECORD, INSERT_WAVE_RECORD, INSERT_WAVE_HEADER, INSERT_RL_ROW — Persistence routines that create wave and batch rows and their release lines.
• LAUNCH_ONLINE, LAUNCH_CONCURRENT_CP, SUBMIT_WP_CONC_REQUEST — Entry-point dispatchers that choose online versus concurrent execution and submit the planning request.
• UPDATE_WAVE_HEADER_STATUS, UPDATE_TASK — Maintain wave header and task state as planning and release progress.
• GET_LINES, GET_DYNAMIC_SQL, INIT_CURSOR, GET_LINE_FILL_RATE, GET_ACTUAL_FILL_RATE, SET_GLOBAL_VARIABLE — Query and metric helpers that build dynamic SQL from saved queries, initialize cursors, and compute wave fill rates used for wave sizing.

The package also declares collection and record types used internally, including line_tbl_typ (a table of WMS_WP_WAVE_LINES rows), action_tbl_typ (a table of VARCHAR2(6) action codes), num_t, and the composite relRecTyp and labor_plan_Record structures. These types are the mechanism by which bulk wave line and action data are passed between internal procedures.

Tables Accessed

• WMS_WP_WAVE_LINES — Primary planning table; holds the candidate and planned wave lines.
• WMS_WP_TASKS_GTMP — Global temporary staging for tasks generated during wave release.
• WMS_SAVED_QUERIES — Supplies user-defined wave selection criteria used by GET_LINES and GET_DYNAMIC_SQL.
• MTL_MATERIAL_TRANSACTIONS_TEMP — Staging of inventory transactions produced by wave release and task creation.
• BOM_DEPARTMENT_RESOURCES, BOM_RESOURCES, BOM_DEPT_RES_INSTANCES, BOM_RESOURCE_EMPLOYEES, BOM_RESOURCE_EQUIPMENTS, BOM_STANDARD_OPERATIONS, BOM_STD_OP_RESOURCES — Supply resource, labor, and equipment capacity used in wave and labor planning.
• BOM_RESOURCE_SHIFTS, BOM_SHIFT_DATES, BOM_SHIFT_TIMES — Define available working time windows for capacity and labor scheduling.
• FND_LOOKUP_VALUES — Provides lookup codes used during planning and status handling.

Usage Notes

WMS_WAVE_PLANNING_PVT is normally reached indirectly. The WMS Wave Planning concurrent program and the WMS HTML wave planning pages call the LAUNCH_* and PLAN_WAVE* entry points; RELEASE_ONLINE and RELEASE_BATCH_CP are invoked from wave and batch release actions in the WMS UI. The package is referenced by six other APPS packages, confirming it functions as an internal dependency rather than a customer-facing API. Because it is PVT, its parameter lists are not guaranteed across patches, and callers should not embed calls to it in custom code.