# Handheld (RF) Screens for Goods Receipt, Storage Location Transfer and Shipment

> Custom mobile screens sized for barcode handhelds that let warehouse staff post goods receipts against purchase orders, transfers between storage locations and picking with goods issue for deliveries. Every scan becomes a material document immediately, so nobody has to key in paper forms afterwards.

- Type: Program, Custom development, Fiori app
- Module: MM
- Estimated effort: L (12–18 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/handheld-rf-goods-receipt-transfer-shipment-screens/


## Why is the standard not enough?

MIGO and VL02N are designed for desktop screens and are not practical on the small display of a handheld. The standard RF menu opened with LM00 only works in warehouses managed with LE-WM; for plants that keep stock only at storage location (IM) level it does not cover goods receipts against orders or storage location transfers. The custom screens resolve material, batch and order from the barcode, warn immediately about missing or wrong scans and work without WM.

### Closest standard alternatives

- MIGO: Posts all goods movements; built for desktop screens, with no order or material resolution from barcodes.
- LM00: The standard RF menu; it only works in warehouses managed with LE-WM.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| MKPF | Material document header: posting date, user, delivery note number (written via BAPI) | Write | - | ECC + S/4 |
| MSEG | Material document items: movement type, material, batch, quantity, storage location | Write | MSEG-MBLNR = MKPF-MBLNR AND MSEG-MJAHR = MKPF-MJAHR | ECC + S/4 |
| EKPO | Open items and order quantity of the scanned order | Read | - | ECC + S/4 |
| EKBE | Quantity already received for the order item | Read | EKBE-EBELN = EKPO-EBELN AND EKBE-EBELP = EKPO-EBELP | ECC + S/4 |
| MEAN | Conversion of the EAN in the barcode to the material number | Read | MEAN-MATNR = EKPO-MATNR | ECC + S/4 |
| MCHB | Unrestricted batch stock check for transfers and shipments | Read | MCHB-MATNR = MSEG-MATNR AND MCHB-WERKS = MSEG-WERKS AND MCHB-LGORT = MSEG-LGORT AND MCHB-CHARG = MSEG-CHARG | ECC + S/4 |
| LIPS | Delivery items, requested and picked quantity | Read / write | - | ECC + S/4 |
| MATDOC | In S/4HANA the material document is written to this table; the BAPI stays the same | Write | - | S/4HANA only |

## BAPIs and functions used

- BAPI_GOODSMVT_CREATE: Posts goods receipts against orders (101) and storage location transfers (311)
- WS_DELIVERY_UPDATE: Updates the picked quantity of the delivery and posts the goods issue
- BAPI_TRANSACTION_COMMIT: Commits the posting after each completed transaction

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_WERKS | Default plant (user parameter) | Single value | MSEG-WERKS | Yes |
| P_LGORT | Default storage location | Single value | MSEG-LGORT | No |
| R_GR | Process: goods receipt against order | Radio button | - | No |
| R_TR | Process: storage location transfer | Radio button | - | No |
| R_GI | Process: delivery picking and goods issue | Radio button | - | No |
| P_LABEL | Print label after goods receipt | Checkbox | - | No |

## Result list columns

| Column | Source |
|---|---|
| User | MKPF-USNAM |
| Process | Calculated: Goods receipt (101), transfer (311) or shipment (601) |
| Reference document | Calculated: Scanned order or delivery number |
| Material | MSEG-MATNR |
| Batch | MSEG-CHARG |
| Quantity | MSEG-MENGE |
| Storage location | MSEG-LGORT |
| Material document | MSEG-MBLNR |
| Status | Calculated: Posted, error or incomplete |

## How does the program work?

1. The user picks the process from the handheld menu: goods receipt against an order, storage location transfer, or delivery picking with goods issue. The default plant and storage location come from the user parameters.
2. Goods receipt: the order or delivery note barcode is scanned; open items are read from EKPO and the quantity already received from EKBE. The material barcode is converted from EAN to the material number via MEAN and matched to the order item; a scan above the open quantity is rejected.
3. Transfer: source storage location, material and batch are scanned; unrestricted stock is checked in MCHB, and once the target storage location is scanned a 311 movement is prepared.
4. Shipment: the delivery number is scanned; LIPS items are compared with the scanned material and batch. When all items are complete, the picked quantity and goods issue are posted with WS_DELIVERY_UPDATE.
5. Goods receipts (101) and transfers (311) are posted with BAPI_GOODSMVT_CREATE; the resulting material document number is shown on the screen. Errors are shown on one line with an audible signal.
6. Every transaction is logged with user and time; the warehouse supervisor follows incomplete or failed transactions in the daily log list.

## Authorization objects

- M_MSEG_BWA: Goods movement authorization by movement type
- M_MSEG_WMB: Goods movement authorization by plant
- M_MSEG_LGO: Goods movement authorization by storage location
- V_LIKP_VST: Delivery change authorization by shipping point

## Frequently asked questions

### Which handhelds does it work with?

The screens run in a browser (ITS mobile or SAPUI5); industrial Android handhelds and tablets with a built-in scanner are enough. The scanner writes the value into the field like keyboard input, so no extra driver is needed.

### Is LE-WM or EWM required?

No. The screens work at storage location (IM) level. In warehouses with LE-WM they can be used next to the standard RF transactions; warehouses on EWM should use EWM's own RF framework.

### Does it work on S/4HANA?

Yes. BAPI_GOODSMVT_CREATE and WS_DELIVERY_UPDATE are also used in S/4HANA; the material document is written to MATDOC. The screens stay the same.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=mm-rf-mobile-warehouse
