Inbound delivery
An ASN or ERP inbound delivery (created from a PO with confirmation control) is distributed to EWM, creating the EWM inbound delivery. In older EWM releases, an inbound delivery notification (IDN) was saved first and then activated; in current S/4HANA releases the inbound delivery is created directly.
- Delivery type and item type determine the process (e.g. standard inbound item type IDLV).
- Warehouse process type determination uses document type, item type, process indicator and product indicator.
- The delivery status profile tracks unloading, GR, putaway and planning statuses.
- T-codes & apps
VL31N/SCWM/PRDI/SCWM/MON
Yard, check-in & unloading
Trucks are represented as transportation units (TU) or vehicles. They are checked in at the yard, assigned to a door and unloaded — optionally with unloading warehouse tasks scanned by RF.
- Yard management (advanced) models parking spaces and yard movements.
- Simple unloading just sets the status without warehouse tasks.
- Check-in/check-out with /SCWM/CICO; TU processing in /SCWM/TU.
- T-codes & apps
/SCWM/CICO/SCWM/TU
Goods receipt posting
GR in EWM can be posted per delivery, per TU or automatically at unloading. It updates the IM stock in S/4HANA (movement type 101 against the PO via the delivery) into the 'putaway' stock type.
- Partial GR is possible per item.
- GR reversal is done by correcting the delivery and reversing GR in EWM.
- Automatic GR at unloading is set in the process type / delivery settings.
- T-codes & apps
/SCWM/PRDI
Deconsolidation, HU breakdown & quality inspection
Mixed pallets are routed to a deconsolidation work centre and split by putaway area. If the product is QM-relevant, the Quality Inspection Engine (QIE) or QM integration creates an inspection document and stock goes to the QI work centre or remains blocked until the decision.
- Process steps (UNLO, DECO, QINS, PTWY…) are defined in POSC.
- Inspection rules decide sampling and inspection at product, delivery or HU level.
- Usage decision posts stock to F2 (accepted) or blocked/return.
- T-codes & apps
/SCWM/PACK (work centre UI)QA32
Putaway strategies & destination determination
Putaway searches for a destination using the storage type search sequence (from the putaway control indicator) and then a putaway rule per storage type: empty bin, addition to existing stock, fixed bin, general storage, near fixed bin, or bulk storage.
- Storage section search and bin type search further narrow the bin.
- Capacity checks use weight, volume and capacity consumption keys.
- Manual destination entry can be allowed for exceptions.
- Configuration
- IMG › SCM Extended Warehouse Management › Extended Warehouse Management › Goods Receipt Process › Strategies › Define Storage Type Search Sequence / Specify Putaway Search Sequence
Putaway execution & completion
Putaway warehouse tasks are bundled into warehouse orders, executed by RF or desktop, and confirmed. On completion the stock type changes from putaway to available, and the delivery reaches 'putaway completed'.
- Exceptions (bin full, quantity difference) use exception codes.
- Confirmation can be HU-based or product-based.
- Desktop confirmation: /SCWM/TO_CONF.
- T-codes & apps
/SCWM/RFUI/SCWM/TO_CONF/SCWM/MON
A mixed pallet arrives with a QM-relevant product
A supplier's pallet holds three products: two go to high-rack, one is QM-relevant. Describe the POSC steps, the warehouse tasks created, the stock types at each step and when IM shows stock as available.
Interview-style questions
What determines the storage type search sequence in putaway?
The putaway control indicator of the warehouse product (plus optional parameters such as stock type, HU type and process type).
Name four putaway rules.
Empty bin, addition to existing stock, fixed bin, general storage (also near fixed bin and bulk storage).
Does an inbound delivery notification still exist in current S/4HANA EWM?
In current releases the inbound delivery is created directly; the IDN is found in older/decentralised setups.