3801645 - Putaway tasks created for lowest HU instead of Top HU after usage decision recording - sap s/4hana cloud public edition

Putaway task was created for Lowest HUs instead of Top HU after recording Usage Decision for inspection lots, multiple warehouse tasks are created instead of one for top HU.

SAP S/4HANA Cloud Public Edition

1. Create an inbound delivery from production and distribute it to EWM.
2. Pack the stock into handling units: 1 top HU with multiple nested/lower-level HU.
3. Post goods receipt for the inbound delivery.
4. Record the Usage Decision separately for each nested/lower-level HU.
5. Observe that the system automatically creates putaway tasks for each lowest HU instead of a single task for the top level (Top HU).

Recording the Usage Decision per nested/lower-level HU leads, by design, to automatic putaway task creation at the lowest HU level, because different decisions can be recorded per HU.

1. When recording the Usage Decision, use the main page to enter a collective decision code so the same decision applies to all nested HU.
2. Save the Usage Decision; the system will create a single putaway task at the top HU (Top HU) level.
3. If putaway tasks were already created at the lowest HU level, cancel them, apply the collective decision code at the main level, and recreate the putaway so it is created for Top HU.

ewm, putaway task, lowest hu, nested hu, top hu, Top HU, usage decision, inspection decision, inbound delivery, goods receipt, pallet, warehouse order processing, automatic putaway, collective decision code, s/4hana cloud public edition , KBA , SCM-EWM-WOP-2CL , Warehouse Order Processing (Public Cloud) , Bug Filed