Handheld (RF) Screens for Goods Receipt, Storage Location Transfer and Shipment
Short answer: 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.
- Estimated effort
- L · 12–18 working days
- System
- ECC and S/4HANA
- Tables
- 8
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Warehouse operators, warehouse supervisors, goods receipt and shipping teams.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| MKPFMaterial Document Header | Material document header: posting date, user, delivery note number (written via BAPI) | Write | ECC + S/4 |
| MSEGMaterial Document Item | Material document items: movement type, material, batch, quantity, storage location | Write | ECC + S/4 |
| EKPOPurchasing Document Item | Open items and order quantity of the scanned order | Read | ECC + S/4 |
| EKBEPurchasing Document History | Quantity already received for the order item | Read | ECC + S/4 |
| MEANInternational Article Numbers (EANs) for Material | Conversion of the EAN in the barcode to the material number | Read | ECC + S/4 |
| MCHBBatch Stocks | Unrestricted batch stock check for transfers and shipments | Read | ECC + S/4 |
| LIPSDelivery Item Data | Delivery items, requested and picked quantity | Read / write | ECC + S/4 |
| MATDOCMaterial Documents (S/4HANA) | In S/4HANA the material document is written to this table; the BAPI stays the same | Write | S/4HANA only |
S/4HANA notes
- MKPF → MATDOC: In S/4HANA new material documents are written to MATDOC; reading MKPF works through a compatibility view. Use MATDOC or I_MaterialDocumentItem_2 directly in new reports.
- MSEG → MATDOC: In S/4HANA MATDOC replaces MSEG; reading MSEG works through a compatibility view but is slow at high volumes.
- MCHB → MATDOC: In S/4HANA batch stock quantities are calculated from MATDOC through a compatibility view; reads work, but test performance on large selections.
BAPIs and functions used
- BAPI_GOODSMVT_CREATEPost Goods Movement. Posts goods receipts against orders (101) and storage location transfers (311)
- WS_DELIVERY_UPDATEUpdate Delivery (Picking, Packing, Goods Issue). Updates the picked quantity of the delivery and posts the goods issue
- BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Commits the posting after each completed transaction
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_WERKS | Default plant (user parameter) | Single value | MSEG-WERKS | Yes | 1000 |
| P_LGORT | Default storage location | Single value | MSEG-LGORT | No | 0001 |
| R_GR | Process: goods receipt against order | Radio button | — | No | X |
| 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 | X |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | User | MKPF-USNAM |
| 2 | Process | Calculated Goods receipt (101), transfer (311) or shipment (601) |
| 3 | Reference document | Calculated Scanned order or delivery number |
| 4 | Material | MSEG-MATNR |
| 5 | Batch | MSEG-CHARG |
| 6 | Quantity | MSEG-MENGE |
| 7 | Storage location | MSEG-LGORT |
| 8 | Material document | MSEG-MBLNR |
| 9 | Status | Calculated Posted, error or incomplete |
Sample result list
| User | Process | Reference document | Material | Batch | Quantity | Storage location | Material document | Status |
|---|---|---|---|---|---|---|---|---|
| DEPO01 | Goods receipt (101) | 4500021450 | HM-1001 | L2611-07 | 1,200 | 0001 | 5000084512 | Posted |
| DEPO02 | Transfer (311) | SC-3300 | L2610-22 | 350 | 0003 | 4900031177 | Posted | |
| DEPO01 | Shipment (601) | 80012944 | BR-2100 | F2611-02 | 48 | 0005 | 4900031180 | Posted |
| DEPO03 | Goods receipt (101) | 4500021462 | SP-0045 | 500 | 0001 | Error: scanned quantity exceeds the open order quantity |
How does the program work?
- 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.
- 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.
- 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.
- 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.
- 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.
- Every transaction is logged with user and time; the warehouse supervisor follows incomplete or failed transactions in the daily log list.
Performance notes
Read a single record with key fields only on every scan; the secondary index on the EAN11 field of MEAN should be used. To survive Wi-Fi drop-outs, the document is posted in one step once scanning is complete; an interrupted transaction resumes where it stopped when it is reopened on the handheld.
Features
- Line-by-line result and error log Every scan and posting is logged with user, device and time.
- ALV list (sort, filter, subtotals) Daily list of incomplete and failed transactions for the warehouse supervisor.
Authorization objects
- M_MSEG_BWAGoods movement authorization by movement type
- M_MSEG_WMBGoods movement authorization by plant
- M_MSEG_LGOGoods movement authorization by storage location
- V_LIKP_VSTDelivery 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.
Related reports
Purchase Order Goods Receipt Upload from File Program
A custom interface program that posts order, item, quantity, storage location, batch and delivery note rows from a warehouse system, a supplier …
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 …
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.