# Automatic Putaway Transfer Order Creation Job for Goods Receipt Interim Storage

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

- Type: Program, Custom development, Background program
- Module: WM
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/automatic-putaway-transfer-order-creation-job/


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

### Closest standard alternatives

- LT04: Converts one transfer requirement to a transfer order on screen; no scheduled bulk conversion.
- LB10: Lists open transfer requirements; no automatic conversion with a waiting-time threshold.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| LTBK | Open transfer requirement header: movement type, status, creation time, material document | Read | - | ECC + S/4 |
| LTBP | Transfer requirement item: requested and converted quantity | Read | LTBP-LGNUM = LTBK-LGNUM AND LTBP-TBNUM = LTBK-TBNUM | ECC + S/4 |
| LQUA | Check of the quant in goods receipt interim storage | Read | LQUA-LGNUM = LTBP-LGNUM AND LQUA-MATNR = LTBP-MATNR AND LQUA-WERKS = LTBP-WERKS | ECC + S/4 |
| LTAK | Created transfer order header | Write | LTAK-LGNUM = LTBK-LGNUM AND LTAK-TBNUM = LTBK-TBNUM | ECC + S/4 |
| LTAP | Created items: destination storage type and bin | Write | LTAP-LGNUM = LTAK-LGNUM AND LTAP-TANUM = LTAK-TANUM | ECC + S/4 |

## BAPIs and functions used

- L_TO_CREATE_TR: Creates a transfer order from the transfer requirement using the putaway strategy

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_LGNUM | Warehouse number | Range / multiple | LTBK-LGNUM | Yes |
| S_BWLVS | WM movement type | Range / multiple | LTBK-BWLVS | No |
| S_VLTYP | Source (interim) storage type | Range / multiple | LTBK-VLTYP | No |
| S_BDATU | Requirement creation date | Range / multiple | LTBK-BDATU | No |
| P_MINAGE | Minimum waiting time (hours) | Single value | - | Yes |
| P_TEST | Test mode (list without creating transfer orders) | Checkbox | - | No |

## Result list columns

| Column | Source |
|---|---|
| Transfer req. | LTBP-TBNUM |
| Item | LTBP-TBPOS |
| Material | LTBP-MATNR |
| Open qty | Calculated: LTBP-MENGE − LTBP-TAMEN |
| Unit | LTBP-MEINS |
| Material doc. | LTBK-MBLNR |
| Transfer order | LTAK-TANUM |
| Dest. type | LTAP-NLTYP |
| Dest. bin | LTAP-NLPLA |
| Status | Calculated: Created, test or error |
| Message | Calculated: L_TO_CREATE_TR exception or success message |

## How does the program work?

1. 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.
2. Items with remaining quantity (MENGE − TAMEN) greater than zero are taken from LTBP; LQUA is checked for a matching quant in the interim bin.
3. In test mode, only the requirements to be converted and the expected destination storage type are listed.
4. 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.
5. 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.

## Authorization objects

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

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=wm-gr-interim-putaway-job
