Warehouse Picker Productivity Report
Short answer: A custom ALV report that groups confirmed transfer order items by confirming user, day and source storage type, and calculates items confirmed per hour, average time from creation to confirmation and the difference rate. Warehouse management tracks team capacity and target compliance with data.
- Estimated effort
- M · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 4
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
LT22 and LT23 list confirmed transfer orders per document, but they do not calculate items per hour per confirming user, active working time or performance against a target rate. To measure productivity, the records are usually downloaded to Excel and processed with a pivot table.
Who uses it? Warehouse managers, shift supervisors and operational excellence teams.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| LTAPTransfer Order Item | Confirmed items: confirming user, confirmation date/time, source storage type, difference quantity (driving table) | — | ECC + S/4 |
| LTAKTransfer Order Header | Movement type and creation date/time | LTAK-LGNUM = LTAP-LGNUM AND LTAK-TANUM = LTAP-TANUM | ECC + S/4 |
| T333WM Movement Types | WM movement type definition | T333-LGNUM = LTAK-LGNUM AND T333-BWLVS = LTAK-BWLVS | ECC + S/4 |
| T301WM Storage Types | Storage type definition | T301-LGNUM = LTAP-LGNUM AND T301-LGTYP = LTAP-VLTYP | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_LGNUM | Warehouse number | Range / multiple | LTAK-LGNUM | Yes | 100 |
| S_QDATU | Confirmation date | Range / multiple | LTAP-QDATU | Yes | 10.11.2026 – 16.11.2026 |
| S_QNAME | Confirmed by | Range / multiple | LTAP-QNAME | No | TOPLAYICI01 |
| S_BWLVS | WM movement type | Range / multiple | LTAK-BWLVS | No | 601 |
| S_VLTYP | Source storage type | Range / multiple | LTAP-VLTYP | No | 001 |
| P_TARGET | Target items/hour | Single value | — | No | 40 |
| R_DETAIL | View: user-day-storage type / user-day only | Radio button | — | No | kullanıcı-gün-depo tipi |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Confirmed by | LTAP-QNAME |
| 2 | Conf. date | LTAP-QDATU |
| 3 | Movement type | LTAK-BWLVS |
| 4 | Source type | LTAP-VLTYP |
| 5 | TO count | Calculated Count of distinct LTAP-TANUM |
| 6 | Item count | Calculated Count of confirmed LTAP items |
| 7 | First conf. | Calculated Minimum LTAP-QZEIT |
| 8 | Last conf. | Calculated Maximum LTAP-QZEIT |
| 9 | Active time (h) | Calculated Last conf. − first conf. − gaps longer than 30 minutes |
| 10 | Items/hour | Calculated Item count ÷ active time |
| 11 | Avg completion (min) | Calculated Σ (LTAP-QDATU/QZEIT − LTAK-BDATU/BZEIT) ÷ item count |
| 12 | Difference rate % | Calculated Items with LTAP-VDIFM ≠ 0 ÷ item count × 100 |
| 13 | vs target % | Calculated Items/hour ÷ target × 100 |
Sample output
| Confirmed by | Conf. date | Movement type | Source type | TO count | Item count | First conf. | Last conf. | Active time (h) | Items/hour | Avg completion (min) | Difference rate % | vs target % |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TOPLAYICI01 | 11/16/2026 | 601 | 001 | 48 | 312 | 07:05 | 14:50 | 7.10 | 43.90 | 38 | 0.60 | 110 |
| TOPLAYICI02 | 11/16/2026 | 601 | 002 | 55 | 268 | 07:20 | 15:10 | 7.30 | 36.70 | 46 | 1.90 | 92 |
| TOPLAYICI03 | 11/16/2026 | 601 | 001 | 31 | 190 | 15:05 | 22:40 | 6.40 | 29.70 | 64 | 3.70 | 74 |
| FORKLIFT01 | 11/16/2026 | 999 | 902 | 62 | 62 | 07:00 | 14:30 | 6.90 | 9 | 95 | 0 | 22 |
How does the report work?
- Confirmed items (PQUIT = X) in the selected confirmation date range are read from LTAP; the confirming user (QNAME), confirmation date and time (QDATU, QZEIT), source storage type and difference quantity (VDIFM) are taken.
- Movement type and creation date/time (BDATU, BZEIT) are added from LTAK; the movement type description is read from T333.
- Records are grouped by user, day, movement type and source storage type (or summarized only at user-day level, depending on the selection).
- Active time = last confirmation time − first confirmation time; gaps longer than 30 minutes are deducted. Items per hour = item count ÷ active time.
- Average completion time = Σ (QDATU/QZEIT − BDATU/BZEIT) ÷ item count. Difference rate = items with a difference quantity ÷ item count. Rows below the target rate are flagged.
Performance notes
Read LTAP by warehouse number and confirmation date; large warehouses may need a secondary index on the confirmation date. Do the aggregation in the database with GROUP BY. Running the report as a weekly background job reduces online load.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Export to Excel
- Runs as a background job Can be scheduled as a background job for weekly or monthly summaries.
- Send the result by email
Authorization objects
- L_LGNUMDisplay authorization by warehouse number and storage type
- L_BWLVSAuthorization by WM movement type
Frequently asked questions
Can this report be used for employee performance appraisal?
The report gives operational data per user ID. If it is used for individual appraisal, the decision should be made with HR and employee representatives under the company's labour law and data protection rules; the report can also run as an anonymous team or shift summary.
Are items confirmed with mobile (RF) devices included?
Yes. Confirmations made with RF are also written to LTAP-QNAME, QDATU and QZEIT; the report does not depend on the device used.
How are jobs of different weight compared?
The split by source storage type and movement type separates pallet and piece picking. If needed, weighted productivity using the item weight (LTAP-BRGEW) or a distance factor can be added.
Related reports
Mass Transfer Order Confirmation Upload Program
A custom program that confirms hundreds of transfer order items in one run from picking results that come from handheld scanners, warehouse automation …
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 report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.