# 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 or Excel, processing actual quantity, difference quantity and actual destination bin. It checks in test mode first, then lists the result of every row.

- Type: Program, Custom development, Mass upload
- Module: WM
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/mass-transfer-order-confirmation-upload-program/


## Why is the standard not enough?

LT12 confirms transfer orders one at a time on screen; LT11 and LT15 do not read a file. In warehouses without RF, or with third-party handheld devices, picking results are written on paper or in Excel and each item is keyed manually. Confirming with differences (short picks) and actual destination bin changes create errors at this volume.

### Closest standard alternatives

- LT12: Confirms transfer orders one at a time on screen; does not confirm in bulk from a file.
- LT11: Gives a list of transfer orders to confirm; difference quantity and actual destination bin cannot come from a file.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LTAK | Transfer order header; the confirmation indicator is updated | Read / write | - | ECC + S/4 |
| LTAP | Transfer order item: actual quantity, difference quantity, confirming user and time are written | Write | LTAP-LGNUM = LTAK-LGNUM AND LTAP-TANUM = LTAK-TANUM | ECC + S/4 |
| LQUA | Quants in source and destination bins are updated by the confirmation | Write | LQUA-LGNUM = LTAP-LGNUM AND LQUA-LGPLA = LTAP-NLPLA | ECC + S/4 |
| LAGP | Destination bin check: does the bin exist, is there a putaway block | Read | LAGP-LGNUM = LTAP-LGNUM AND LAGP-LGTYP = LTAP-NLTYP AND LAGP-LGPLA = LTAP-NLPLA | ECC + S/4 |

## BAPIs and functions used

- L_TO_CONFIRM: Confirms the transfer order with item quantities, differences and actual destination bin

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_FILE | Upload file (XLSX or CSV) | Single value | - | Yes |
| P_LGNUM | Warehouse number | Single value | LTAK-LGNUM | Yes |
| P_TEST | Test mode (check without posting) | Checkbox | - | No |
| P_DIFF | Allow confirmation with differences (short pick) | Checkbox | - | No |

## Input file columns

| Column | Target field | Required |
|---|---|---|
| Transfer order | LTAP-TANUM | Yes |
| Item | LTAP-TAPOS | Yes |
| Actual qty | LTAP-NISTM | Yes |
| Difference qty | LTAP-NDIFM | No |
| Actual dest. bin | LTAP-NLPLA | No |
| Batch | LTAP-CHARG | No |
| Confirmed by | LTAP-QNAME | No |

## Result list columns

| Column | Source |
|---|---|
| Row | Calculated: Row number in the file |
| Transfer order | LTAP-TANUM |
| Item | LTAP-TAPOS |
| Status | Calculated: From the checks and confirmation: confirmed, test OK or error |
| Message | Calculated: Check error or L_TO_CONFIRM exception message |

## How does the program work?

1. The file (XLSX or CSV) is read from the user's PC or, in a background job, from a folder on the application server; the first row is skipped as the header.
2. For every row, LTAK/LTAP are read: does the transfer order exist, is the item unconfirmed (PQUIT blank), does actual quantity + difference quantity in the file match the target quantity (VSOLM), are batch and destination bin valid.
3. Rows of the same transfer order are grouped and the item table for L_TO_CONFIRM is prepared: actual quantity, difference quantity, actual destination bin and confirming user.
4. In test mode only the checks run and nothing is posted; all errors are visible per row.
5. In a real run L_TO_CONFIRM is called for each transfer order and committed; result and error message are listed per row, and failed rows can be downloaded as a separate file.

## Authorization objects

- L_LGNUM: Processing authorization by warehouse number and storage type
- L_TCODE: WM transaction authorization (same check as LT12)

## Frequently asked questions

### Where is the difference quantity posted?

Depending on the movement type settings, the difference quantity is written to the difference interim type (usually 999). It is later posted to IM with LI21 or the standard difference clearing process.

### Can the program connect directly to a handheld system?

Yes. Instead of a file, an interim table, IDoc or HTTP interface can use the same checks and confirmation logic; this interface version adds effort.

### Can this program be used on S/4HANA?

On S/4HANA systems with Stock Room Management or classic LE-WM, L_TO_CONFIRM works the same way. If EWM is used, confirmation is done on warehouse tasks and the program is rewritten for EWM.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=wm-to-confirmation-upload
