3442018 - Warehouse Task creation through API call failed due to non EWM HUs

It's not possible to create Warehouse Task using API_WAREHOUSE_ORDER_TASK_2 API. When trying to create the warehouse task at header level or item level, the error message occurs:  "System could not determine source storage bin" - "/SCWM/L3 008" 

When checking the HU information related to the WT creation by API_HANDLINGUNIT, a Whse is not being display in the request.

SAP S/4HANA Cloud

You can retrieve LO & EWM Handling Units by the API API_HANDLINGUNIT. The Warehouse is only filled for EWM HUs. This is the differentiator. If you enter non EWM HU then it makes sense that the system can’t find the right stock/source bin.

In general only EWM HUs can be used. But during the lifecycle of a HU the application responsibility changes.

The HU could have the following lifecycle:

1. Handling Unit Created in LE during Inbound Delivery creation ->The API_HANDLINGUNIT doesn’t return the warehouse;
2. LE Delivery is replicated to EWM ->Now it’s a planned HU for an inbound delivery -> The API_HANDLIGNUNIT will return it with the warehouse number;
3. EWM Delivery is posted GR -> Now it’s an active HU -> The API_HANDLINGUNIT returns the warehouse number;
4. Putaway done for the HU -> Still an active HU but Delivery Reference is lost ->The API_HANDLINGUNIT returns the warehouse number;
5. An outbound delivery is created in LE and replicated to EWM;
6. EWM starts with the picking warehouse tasks;
7. HU is picked and assigned to the outbound delivery order -> The API_HANDLINGUNIT returns the warehouse numbser;
8. The outbound delivery order is posted GI in EWM -> HU left the warehouse and LO is now responsible in the lifecycle -> The API_HANDLINGUNIT doesn’t return the warehouse number anymore.

s/4hana cloud, EWM, WT, warehouse task, /SCWM/L3008, API_WAREHOUSE_ORDER_TASK_2 API, API_HANDLINGUNIT, VL864. VL 864.   , KBA , SCM-EWM-API-2CL , Remote APIs (Public Cloud) , Problem