Stock type change in EWM is not getting updated in ERP

[former_member757278]

Hi,

I am setting up inbound process on S4HANA embedded EWM system. I have created two storage locations ROD and AFS respectively. When inbound delivery is created in ERP, it does get distributed to EWM successfully. I am able to create a WH task and a work order in EWM and then confirm the WO as well. The stock type changes from F1 to F2 successfully.

But the stocks are not getting updated in ERP. So in MMBE in ERP I only see the "on-order stock" quantity on ROD storage location. I checked in SMQ2 and found all the inbound deliveries stuck with the same error "Material MIPL-MAT3 MIPL AFS does not exist".(MIPL-MAT3 is material, MIPL is plant, AFS is storage location)

I have maintain all settings for mapping storage location to availability group & availability group with stock type. Also maintain availability group in storage type as mandatory.

Could someone please help me resolve this error and let me know how to update stocks in ERP? Thank you.

Regards,

Amol

[JuergenPitz · Accepted solution]

Hi,

the EWM settings you have maintained are not the solution. The problem is that the material does not exist for the storage location in ERP (the means the views for the plant/storage location). You either manually have to extend the material. Or automatically. The first link in my search leads me to this: https://blogs.sap.com/2010/11/23/config-settings-to-create-storage-location-automatically/.

Brgds

Juergen

---

All the above is no official SAP statement.

Want to learn EWM?

Check for EWM courses: https://training.sap.com/trainingpath/Applications-Extended+Warehouse+Management-EWM+in+S4HANA

Get a SAP Learning Hub Subscription: https://training.sap.com/learninghub

And it is EWM. NOT eWM - Duh!

And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!

[NorbertM]

Hi Amol,

Check if you have created storage location master data for the material, if not use MMSC t.code. The error clearly says that the material does not exist in storage location.