Mass Transfer Order Confirmation Upload Program
Short answer: 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.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 4
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Warehouse operations teams, warehouse automation integration owners and LE-WM key users.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| LTAKTransfer Order Header | Transfer order header; the confirmation indicator is updated | Read / write | ECC + S/4 |
| LTAPTransfer Order Item | Transfer order item: actual quantity, difference quantity, confirming user and time are written | Write | ECC + S/4 |
| LQUAQuants | Quants in source and destination bins are updated by the confirmation | Write | ECC + S/4 |
| LAGPStorage Bins | Destination bin check: does the bin exist, is there a putaway block | Read | ECC + S/4 |
BAPIs and functions used
- L_TO_CONFIRMConfirm Transfer Order. Confirms the transfer order with item quantities, differences and actual destination bin
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_FILE | Upload file (XLSX or CSV) | Single value | — | Yes | C:\temp\toplama_sonuclari.xlsx |
| P_LGNUM | Warehouse number | Single value | LTAK-LGNUM | Yes | 100 |
| P_TEST | Test mode (check without posting) | Checkbox | — | No | X |
| P_DIFF | Allow confirmation with differences (short pick) | Checkbox | — | No | X |
Input file columns
The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Transfer order | LTAP-TANUM | Yes |
| 2 | Item | LTAP-TAPOS | Yes |
| 3 | Actual qty | LTAP-NISTM | Yes |
| 4 | Difference qty | LTAP-NDIFM | No |
| 5 | Actual dest. bin | LTAP-NLPLA | No |
| 6 | Batch | LTAP-CHARG | No |
| 7 | Confirmed by | LTAP-QNAME | No |
Sample upload file
| 1 | Transfer order * | Item * | Actual qty * | Difference qty | Actual dest. bin | Batch | Confirmed by |
|---|---|---|---|---|---|---|---|
| 2 | 0000081245 | 0001 | 24 | 0 | TOPLAYICI01 | ||
| 3 | 0000081245 | 0002 | 110 | 10 | TOPLAYICI01 | ||
| 4 | 0000081310 | 0001 | 300 | 0 | 01-07-02 | B2611-04 | FORKLIFT01 |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Row | Calculated Row number in the file |
| 2 | Transfer order | LTAP-TANUM |
| 3 | Item | LTAP-TAPOS |
| 4 | Status | Calculated From the checks and confirmation: confirmed, test OK or error |
| 5 | Message | Calculated Check error or L_TO_CONFIRM exception message |
Sample result list
| Row | Transfer order | Item | Status | Message |
|---|---|---|---|---|
| 2 | 0000081245 | 0001 | Confirmed | Transfer order 81245 item 1 confirmed |
| 3 | 0000081245 | 0002 | Confirmed | 10 PC difference posted to interim type 999 |
| 4 | 0000081310 | 0001 | Error | Destination bin 01-07-02 is blocked for putaway |
How does the program work?
- 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.
- 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.
- 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.
- In test mode only the checks run and nothing is posted; all errors are visible per row.
- 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.
Performance notes
Confirmation runs once per transfer order; sending the items of one order in a single call reduces lock conflicts. Run files above a few thousand rows as a background job and avoid parallel runs for the same warehouse number.
Features
- Test mode (check without posting)
- Line-by-line result and error log
- Download failed lines as a separate file Failed rows can be corrected and uploaded again with the same template.
- Export to Excel An empty upload template can be downloaded as Excel.
- Runs as a background job Files dropped by an automation system can be read by a periodic job.
Authorization objects
- L_LGNUMProcessing authorization by warehouse number and storage type
- L_TCODEWM 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.
Related reports
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 …
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 …
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.