WM Program Custom development Fiori app

EWM Production Staging Cockpit with Pick Lists and Handover Tracking

Short answer: A custom cockpit that manages picking and staging the components of production and subcontracting orders to the production supply area (PSA) in EWM from one screen. Orders are filtered by order type, material type and date; normal, urgent and repeated execution, completion, pallet/pick list and label printing are done from the same place, and the handover to production is recorded.

Estimated effort
L · 15–20 working days
System
ECC and S/4HANA
Tables
9
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

In standard EWM the production supply steps are spread over several screens: the production material request in /SCWM/PMR, staging in /SCWM/STAGE and task monitoring in /SCWM/MON. Subcontracting components follow a separate outbound delivery flow. Urgent execution, repeated execution and completion are not in one list, and there is no handover report showing who handed material to whom at the production area and when.

Who uses it? EWM warehouse shift supervisors, production supply teams, production planning and subcontracting coordinators.

Closest standard alternatives

  • /SCWM/MON EWM Warehouse Management Monitor. Monitors tasks and requests; no per-order staging, execution and handover flow.
  • /SCWM/TO_CONF Confirm Warehouse Task in EWM. Confirms tasks; does not show staging status per order.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
AFKOOrder Header Data for PP OrdersProduction order and start dateReadECC + S/4
RESBReservation/Dependent RequirementsProduction and subcontracting order component requirementsReadECC + S/4
/SCDL/DB_PROCH_OEWM Outbound Delivery Order HeaderProduction material request / outbound document headerReadECC + S/4
/SCDL/DB_PROCI_OEWM Outbound Delivery Order ItemRequest items: product and quantityReadECC + S/4
/SCWM/AQUAEWM Available QuantityAvailable stock checkReadECC + S/4
/SCWM/ORDIM_OEWM Open Warehouse TasksOpen warehouse tasks; execution creates new tasksRead / writeECC + S/4
/SCWM/ORDIM_CEWM Confirmed Warehouse TasksConfirmed tasks: quantity staged to the PSAReadECC + S/4
/SCWM/WHOEWM Warehouse OrdersWarehouse orders (pick lists)ReadECC + S/4
/SCWM/HUHDREWM Handling Unit HeaderHandling unit handed overReadECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_LGNUMWarehouse numberSingle value/SCWM/ORDIM_O-LGNUMYesW100
S_AUFNRProduction orderRange / multipleAFKO-AUFNRNo1000418
S_AUARTOrder typeRange / multipleAUFK-AUARTNoPP01
S_MTARTMaterial typeRange / multipleMARA-MTARTNoROH
S_GSTRPOrder start dateRange / multipleAFKO-GSTRPYes18.11.2026 – 20.11.2026
S_PSAProduction supply areaRange / multiple/SCWM/ORDIM_O-PSANoPSA-MONT1
P_SUBCONInclude subcontracting ordersCheckbox—NoX

Result list columns

#ColumnSource
1OrderRESB-AUFNR
2StartAFKO-GSTRP
3ComponentRESB-MATNR
4RequiredRESB-BDMNG
5StagedCalculated Σ /SCWM/ORDIM_C-NISTA (to the PSA)
6Open tasksCalculated Σ /SCWM/ORDIM_O-VSOLM
7RemainingCalculated Required − staged − open tasks
8Warehouse order/SCWM/ORDIM_O-WHO
9PSA/SCWM/ORDIM_O-PSA
10HandoverCalculated Receiving user and time (handover table)
11StatusCalculated Waiting, released, urgent, staged, handed over, complete

Sample result list

OrderStartComponentRequiredStagedOpen tasksRemainingWarehouse orderPSAHandoverStatus
100041811/19/2026KRT-110140140002000001845PSA-MONT1U.Demir 07:42Handed over
100041811/19/2026VDA-M61,20080040002000001846PSA-MONT1Released
100042211/19/2026GVD-3002402402000001851PSA-TALASUrgent
450002187711/20/2026SAC-2MM35000350PSA-FASONWaiting
A view built with fictional sample data; not real system data.

How does the program work?

  1. For the selected warehouse number the related plants are found in /SCWM/TMAPSTLOC. Production orders are read from AFKO (GSTRP) and their components from RESB; subcontracting components come through RESB-EBELN. Order type and material type filters are applied.
  2. For each order the EWM production material request (/SCDL/DB_PROCH_O and /SCDL/DB_PROCI_O, document category PMR) or, for subcontracting, the outbound delivery is read; the product GUID is converted to the material number through /SAPAPO/MATKEY.
  3. Open warehouse tasks are read from /SCWM/ORDIM_O and confirmed ones from /SCWM/ORDIM_C (PSA, VSOLM, NISTA); requirement − staged − open tasks = remaining quantity. Available stock is checked in /SCWM/AQUA.
  4. Execution: warehouse tasks are created for the remaining quantity with /SCWM/TO_CREATE; urgent execution uses a separate priority queue, and repeated execution requests cancelled or short-confirmed quantities again. Warehouse orders (/SCWM/WHO) are printed as pick lists and pallet labels.
  5. Completion: when the remaining quantity is zero or the user closes it, the order line is marked complete.
  6. Handover: the handling unit (/SCWM/HUHDR) arriving at the PSA is scanned; the handing and receiving users, time and any difference are written to a custom handover table. The handover report lists by order, shift and PSA.

Performance notes

Limit orders by date and plant; read /SCWM/ORDIM_O and /SCWM/ORDIM_C only with the selected PSAs and document IDs. Buffer the product GUID conversion. Bundle task creation per order.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document Clicking a warehouse order opens its tasks in /SCWM/MON.
  • Line-by-line result and error log
  • Export to Excel The handover report can be exported to Excel at the end of a shift.

Authorization objects

  • /SCWM/TOCRAuthorization to create warehouse tasks
  • /SCWM/DLVEWM document processing authorization
  • C_AFKO_AWKProduction order display

Frequently asked questions

Does it work with decentralized EWM?

Yes, but because order and component data cannot be read from ERP directly, it is taken from the production material request in EWM. The order type filter is then mapped to the request document type; the adaptation adds about 2–3 days.

Can the handover be done with a handheld?

Yes. The handover step is also offered as an RF screen; the receiver scans and confirms the handling unit and the record goes to the same table.

Does the cockpit run in SAP GUI?

It can be built as an ALV cockpit in SAP GUI or as a Fiori app with the same logic; the choice depends on the number of users and the devices.

Related reports

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.

Related report: EWM Production Staging Cockpit with Pick Lists and Handover Tracking