# Warehouse Picker Productivity Report

> 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.

- Type: Report, Custom development, ALV report
- Module: WM
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/warehouse-picker-productivity-report/


## 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.

### Closest standard alternatives

- LT23: Lists confirmed transfer orders per document; does not calculate items per hour per user.
- LT22: Shows transfer orders by storage type; has no productivity or target comparison.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LTAP | Confirmed items: confirming user, confirmation date/time, source storage type, difference quantity (driving table) | Read | - | ECC + S/4 |
| LTAK | Movement type and creation date/time | Read | LTAK-LGNUM = LTAP-LGNUM AND LTAK-TANUM = LTAP-TANUM | ECC + S/4 |
| T333 | WM movement type definition | Read | T333-LGNUM = LTAK-LGNUM AND T333-BWLVS = LTAK-BWLVS | ECC + S/4 |
| T301 | Storage type definition | Read | T301-LGNUM = LTAP-LGNUM AND T301-LGTYP = LTAP-VLTYP | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_LGNUM | Warehouse number | Range / multiple | LTAK-LGNUM | Yes |
| S_QDATU | Confirmation date | Range / multiple | LTAP-QDATU | Yes |
| S_QNAME | Confirmed by | Range / multiple | LTAP-QNAME | No |
| S_BWLVS | WM movement type | Range / multiple | LTAK-BWLVS | No |
| S_VLTYP | Source storage type | Range / multiple | LTAP-VLTYP | No |
| P_TARGET | Target items/hour | Single value | - | No |
| R_DETAIL | View: user-day-storage type / user-day only | Radio button | - | No |

## Output columns

| Column | Source |
|---|---|
| Confirmed by | LTAP-QNAME |
| Conf. date | LTAP-QDATU |
| Movement type | LTAK-BWLVS |
| Source type | LTAP-VLTYP |
| TO count | Calculated: Count of distinct LTAP-TANUM |
| Item count | Calculated: Count of confirmed LTAP items |
| First conf. | Calculated: Minimum LTAP-QZEIT |
| Last conf. | Calculated: Maximum LTAP-QZEIT |
| Active time (h) | Calculated: Last conf. − first conf. − gaps longer than 30 minutes |
| Items/hour | Calculated: Item count ÷ active time |
| Avg completion (min) | Calculated: Σ (LTAP-QDATU/QZEIT − LTAK-BDATU/BZEIT) ÷ item count |
| Difference rate % | Calculated: Items with LTAP-VDIFM ≠ 0 ÷ item count × 100 |
| vs target % | Calculated: Items/hour ÷ target × 100 |

## How does the report work?

1. 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.
2. Movement type and creation date/time (BDATU, BZEIT) are added from LTAK; the movement type description is read from T333.
3. Records are grouped by user, day, movement type and source storage type (or summarized only at user-day level, depending on the selection).
4. Active time = last confirmation time − first confirmation time; gaps longer than 30 minutes are deducted. Items per hour = item count ÷ active time.
5. 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.

## Authorization objects

- L_LGNUM: Display authorization by warehouse number and storage type
- L_BWLVS: Authorization 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=wm-warehouse-picker-productivity
