Automatic Putaway Transfer Order Creation Job for Goods Receipt Interim Storage
Short answer: A custom background job that finds open transfer requirements waiting in goods receipt interim storage longer than a set time, converts them into transfer orders using the putaway strategy, and lists the result and errors. Goods receipts left over at night or at shift end start the morning already put away to their bins.
- Estimated effort
- M · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
LT04 converts one transfer requirement to a transfer order on screen; LB10 lists open requirements but does not convert them in bulk on a schedule. Automatic transfer order creation (in the movement type) is either always on or always off; a controlled job that converts only requirements above a certain age and from certain movement types does not exist in the standard.
Who uses it? Goods receiving teams, warehouse shift supervisors 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 |
|---|---|---|---|
| LTBKTransfer Requirement Header | Open transfer requirement header: movement type, status, creation time, material document | Read | ECC + S/4 |
| LTBPTransfer Requirement Item | Transfer requirement item: requested and converted quantity | Read | ECC + S/4 |
| LQUAQuants | Check of the quant in goods receipt interim storage | Read | ECC + S/4 |
| LTAKTransfer Order Header | Created transfer order header | Write | ECC + S/4 |
| LTAPTransfer Order Item | Created items: destination storage type and bin | Write | ECC + S/4 |
BAPIs and functions used
- L_TO_CREATE_TRCreate Transfer Order for Transfer Requirement. Creates a transfer order from the transfer requirement using the putaway strategy
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_LGNUM | Warehouse number | Range / multiple | LTBK-LGNUM | Yes | 100 |
| S_BWLVS | WM movement type | Range / multiple | LTBK-BWLVS | No | 101 |
| S_VLTYP | Source (interim) storage type | Range / multiple | LTBK-VLTYP | No | 902 |
| S_BDATU | Requirement creation date | Range / multiple | LTBK-BDATU | No | 01.11.2026 – 17.11.2026 |
| P_MINAGE | Minimum waiting time (hours) | Single value | — | Yes | 2 |
| P_TEST | Test mode (list without creating transfer orders) | Checkbox | — | No | X |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Transfer req. | LTBP-TBNUM |
| 2 | Item | LTBP-TBPOS |
| 3 | Material | LTBP-MATNR |
| 4 | Open qty | Calculated LTBP-MENGE − LTBP-TAMEN |
| 5 | Unit | LTBP-MEINS |
| 6 | Material doc. | LTBK-MBLNR |
| 7 | Transfer order | LTAK-TANUM |
| 8 | Dest. type | LTAP-NLTYP |
| 9 | Dest. bin | LTAP-NLPLA |
| 10 | Status | Calculated Created, test or error |
| 11 | Message | Calculated L_TO_CREATE_TR exception or success message |
Sample result list
| Transfer req. | Item | Material | Open qty | Unit | Material doc. | Transfer order | Dest. type | Dest. bin | Status | Message |
|---|---|---|---|---|---|---|---|---|---|---|
| 0000004521 | 0001 | RM-1002 | 300 | KG | 5000012834 | 0000081402 | 001 | 01-07-02 | Created | Transfer order 81402 created |
| 0000004560 | 0001 | RM-3105 | 180 | L | 5000012901 | 0000081403 | 005 | 05-01-04 | Created | Transfer order 81403 created |
| 0000004571 | 0001 | RM-2040 | 800 | KG | 5000012930 | Error | No suitable empty bin found in storage type 001 |
How does the program work?
- Open or partially processed transfer requirements for the selected warehouse number and movement types are read from LTBK; those created more recently than the threshold are skipped.
- Items with remaining quantity (MENGE − TAMEN) greater than zero are taken from LTBP; LQUA is checked for a matching quant in the interim bin.
- In test mode, only the requirements to be converted and the expected destination storage type are listed.
- In a real run, L_TO_CREATE_TR is called for each transfer requirement; the destination bin is determined by the storage type’s putaway strategy. If no bin is found because of capacity or a block, the requirement stays open and the error message is logged.
- The created transfer order numbers and destination bins are read from LTAK/LTAP and written to the result list; the list is kept in the job log and can be emailed.
Performance notes
Schedule the job with separate variants per warehouse number and do not run it in parallel for the same warehouse; transfer order creation takes locks at warehouse number level. Committing after each requirement isolates failed ones.
Features
- Runs as a background job Can be scheduled at shift ends or every hour.
- Test mode (check without posting)
- Line-by-line result and error log
- Send the result by email Failed requirements can be sent to the goods receiving owner.
Authorization objects
- L_LGNUMProcessing authorization by warehouse number and storage type
- L_BWLVSAuthorization by WM movement type
Frequently asked questions
How is this different from automatic TO creation in the movement type?
The automatic setting creates a transfer order immediately for every goods receipt. This job converts only requirements older than a set time and from selected movement types, so the team can manage requirements manually during the day and the rest is processed automatically at shift end.
What happens to requirements where no bin is found?
The requirement stays open and the error message is written to the result list. It is retried in the next run; if the capacity issue persists, the warehouse owner gets an email.
Can the transfer orders be confirmed automatically?
Yes, depending on the movement type settings or an extra option, the transfer order can be confirmed immediately on creation. If physical putaway happens separately, confirmation should be done by handheld or the mass confirmation program.
Related reports
Interim Storage Stuck and Negative Stock Report
A custom ALV report that lists quants in goods receipt, shipping, posting change and difference interim storage types that have been waiting longer …
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 …
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.