Wave Picking Transfer Order Creation Job by Loading Time
Short answer: A background job that splits deliveries into waves (WM groups) by route and loading time, creates a group for each wave and automatically creates the picking transfer orders of the deliveries. Partial-pick rules apply, and deliveries that could not be processed because of missing stock are listed separately.
- Estimated effort
- L · 9–14 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
LT03 creates a transfer order per delivery; VL06P lists deliveries for picking but does not build waves by truck loading time or create the group automatically. Preparing wave groups by hand takes time at the start of every shift, and picks for later trucks can jump the queue.
Who uses it? Shipping planners, warehouse shift supervisors and distribution center managers.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| LIKPDelivery Header | Delivery header: shipping point, route, loading date and time | Read | ECC + S/4 |
| LIPSDelivery Item Data | Delivery items: material, warehouse number, quantity | Read | ECC + S/4 |
| VBUKSales Document Header Status (ECC) | Picking and WM status of the delivery in ECC | Read | ECC only |
| KNA1Customer Master (General Section) | Ship-to party name | Read | ECC + S/4 |
| T311Definition of WM Groups | WM group created for the wave | Write | ECC + S/4 |
| LTAKTransfer Order Header | Created picking transfer order header (via L_TO_CREATE_DN) | Write | ECC + S/4 |
| LTAPTransfer Order Item | Created transfer order items | Write | ECC + S/4 |
S/4HANA notes
- VBUK → VBAK: VBUK is not used in S/4HANA. The status fields moved to the respective document header: VBAK for sales, LIKP for deliveries, VBRK for billing. It is one of the most common fixes when custom reports move from ECC.
BAPIs and functions used
- L_REF_CREATECreate Reference Number. Creates a WM group per wave and assigns the deliveries
- L_TO_CREATE_DNCreate Transfer Order for Delivery. Creates the picking transfer order for the delivery
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_LGNUM | Warehouse number | Range / multiple | LIKP-LGNUM | Yes | 100 |
| S_VSTEL | Shipping point | Range / multiple | LIKP-VSTEL | Yes | 1000 |
| S_ROUTE | Route | Range / multiple | LIKP-ROUTE | No | TR0001 |
| S_WADAT | Planned goods issue date | Range / multiple | LIKP-WADAT | Yes | 17.11.2026 |
| P_WAVE | Wave interval (minutes) | Single value | — | No | 60 |
| P_LEAD | Hours before loading time to release the wave | Single value | — | No | 3 |
| P_PARTL | Allow partial picking | Checkbox | — | No | — |
| P_TEST | Test mode (show the wave plan only) | Checkbox | — | No | X |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Wave group | T311-REFNR |
| 2 | Loading date | LIKP-LDDAT |
| 3 | Loading time | LIKP-LDUHR |
| 4 | Route | LIKP-ROUTE |
| 5 | Delivery | LIKP-VBELN |
| 6 | Ship-to party | KNA1-NAME1 |
| 7 | Items | Calculated Number of LIPS items in the delivery |
| 8 | Transfer order | LTAK-TANUM |
| 9 | Status | Calculated Created, partial, skipped (no stock) or error |
| 10 | Message | Calculated Exception or system message from L_TO_CREATE_DN |
Sample result list
| Wave group | Loading date | Loading time | Route | Delivery | Ship-to party | Items | Transfer order | Status | Message |
|---|---|---|---|---|---|---|---|---|---|
| W17110800 | 11/17/2026 | 08:00 | TR0001 | 0080041120 | Anadolu Gıda Dağıtım A.Ş. | 6 | 0000419311 | Created | Transfer order 419311 created |
| W17110800 | 11/17/2026 | 08:30 | TR0001 | 0080041124 | Kuzey Market Zinciri Ltd. | 3 | 0000419312 | Created | Transfer order 419312 created |
| W17111000 | 11/17/2026 | 10:15 | TR0004 | 0080041131 | Ege Toptan Ticaret A.Ş. | 4 | Skipped | Not enough stock for FG-5003 in storage type 001 |
How does the program work?
- Deliveries are read from LIKP for the selected shipping point, warehouse number and planned goods issue date; in ECC those without transfer orders yet are taken from VBUK WM status (LVSTK) (in S/4HANA the status fields are in LIKP).
- Items are added from LIPS and the ship-to name from KNA1.
- Deliveries are split into waves by route and loading time (LDDAT, LDUHR), using the wave interval on the selection screen (e.g. 60 minutes); the earliest wave is processed first.
- For each wave a WM group (T311) is created with L_REF_CREATE and the deliveries are assigned to it.
- L_TO_CREATE_DN is called for each delivery; when “Allow partial picking” is not selected, deliveries whose stock is not fully covered are skipped.
- In test mode no group or transfer order is created; only the planned waves are listed. Results are written to the log per delivery.
Performance notes
The job is designed to run several times per shift (e.g. every hour) and selects only deliveries without transfer orders. Delivery locks are checked so the same delivery is not processed by two jobs; L_TO_CREATE_DN is called in a separate LUW per delivery.
Features
- Runs as a background job Scheduled as an hourly job during the shift.
- Test mode (check without posting)
- Line-by-line result and error log
- ALV list (sort, filter, subtotals)
- Send the result by email Skipped deliveries can be emailed to the shift supervisor.
Authorization objects
- L_LGNUMAuthorization to create transfer orders by warehouse number and storage type
- L_BWLVSAuthorization for the picking WM movement type
- V_LIKP_VSTDelivery authorization by shipping point
Frequently asked questions
Why this job instead of wave pick templates?
Standard wave templates work with fixed time slots and need Customizing to maintain. This job builds the wave from each delivery's own loading time; no configuration change is needed when routes or truck times change.
What happens when stock is missing?
If partial picking is not allowed, the delivery is skipped and retried in the next run. If it is allowed, a transfer order is created for the quantity found and the missing item appears in the log.
How is this need covered in EWM?
Wave management is standard in EWM (/SCWM/WAVEHDR). For companies on LE-WM, this job gives a similar way of working until the move to EWM and makes it easier to carry the wave rules into the EWM design.
Related reports
Picked but Not Goods-Issued Deliveries Report
A custom ALV report that lists deliveries whose picking is complete but whose goods issue has not been posted, with the number of days they have been …
Unconfirmed Transfer Orders Aging Report
A custom ALV report that lists transfer order items that were created but not confirmed across a warehouse number, by hours waiting, planned goods …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.