- SAP Managed Tags:
A new feature which was requested lots of times comes with the latest releases of EWM:
Stock Consolidation.
Starting with releases EWM in S/4HANA OP 1709 and decentral EWM 9.5, you now have the power to:
As a start, familiarize yourself with Stock Consolidation in the online documentation.
This blog post will walk you through examples for consolidation on storage bins in the warehouse.
The stock consolidation functionality is a self-contained report with transaction code /SCWM/STOCK_CONS (SAP Easy Access Menu: Extended Warehouse Management → Work Scheduling → Consolidate Stock)
If you use the FIORI Launchpad, you will find the app in the catalogue under EWM - Work Scheduling - “Consolidate Stock”
There is no dedicated customizing required. Since stock consolidation builds on existing functions in EWM configuration, your setup in the warehouse is crucial.
You enter the criteria needed to consolidate stock in the selection criteria of the transaction itself.
The common business scenario is a warehouse supervisor who would usually prepare the warehouse tasks for stock consolidation during idle times in the warehouse. These warehouse tasks would either be phased in the queue for the affected storage types/activity areas, or a warehouse internal queue.
For stock consolidation, a warehouse supervisor could select the storage types for picking. His selection would include products with slow or moderate stock turnover rates. Such partial quantities would usually reside longer in the picking zones compared to fast-moving products. Such slower moving products are worth the effort to consolidate. Fast mover would leave the warehouse before they might cram up storage space.
Let us see how the example from the online documentation would look in the transaction.
The product in this example is contained in pallets (PAL). Eight pieces make up a full pallet. This is the largest unit of measure in the product master:
The following selection criteria would be entered in the stock consolidation transaction:
Execute the report and the results would look like this:
In the above list, you see the aggregated results of possible stock consolidation options. You see that you can reach one full pallet with one suggested consolidaton move. In the same line, you get the information that you can free one storage bin with this move.
Below, you see the detailed proposals for warehouse tasks. The list contains the move of the three pieces to the five pieces. This would yield the full pallet and free the source storage bin.
The standard behavior is always to move smaller partial quantities to larger partials.
When you are satisfied with the proposals, you can select the proposals and click “Create Warehouse Task”.
When clicking the button "Application Log" , you will find that a warehouse task was created and ready for execution:
The following selection comes closer to a realistic view for stock consolidation. A storage type is selected which contains stock for picking (type PM20). And a selection of products is entered (PM-ACME-*):
The result screen displays all possible consolidation options:
This result relates more to a business scenario with lots of partials. Though in the results, there are options which are not worth creating warehouse tasks because they would pose more effort in execution of tasks than gaining full quantitites.
For example, the first lines do not even yield half a pallet. In the details below, you see that line 3 has proposed moves which cannot free up storage bins. These moves would not even lead to a tenth of a full pallet.
You can already exclude such proposals beforehand by finetuning your selection. This will give you results worth the consideration for warehouse task creation.
Assume, you want to reach at least 80% of full quantities when you consolidate. Than you enter a minimal utilization of 80. In case you always want to reach a full quantity, just enter 100 (to represent full quantity => 100%). Though it is advisable to allow splitting partial quantities further to increate the chances to reach complete utilization.
With this additional parameter the results will only contain moves that finally yield full quantities:
These were some initial examples in this blog post. Stay tuned for following blog post and also posts about frequently asked questions (FAQs).
Did you already collect experiences with the new feature?
What are your questions?
Stock Consolidation.
Starting with releases EWM in S/4HANA OP 1709 and decentral EWM 9.5, you now have the power to:
Consolidate partial quantities of the same product which is scatterd on several storage bins into full quantities.
As a start, familiarize yourself with Stock Consolidation in the online documentation.
This blog post will walk you through examples for consolidation on storage bins in the warehouse.
The stock consolidation functionality is a self-contained report with transaction code /SCWM/STOCK_CONS (SAP Easy Access Menu: Extended Warehouse Management → Work Scheduling → Consolidate Stock)
If you use the FIORI Launchpad, you will find the app in the catalogue under EWM - Work Scheduling - “Consolidate Stock”
There is no dedicated customizing required. Since stock consolidation builds on existing functions in EWM configuration, your setup in the warehouse is crucial.
You enter the criteria needed to consolidate stock in the selection criteria of the transaction itself.
The common business scenario is a warehouse supervisor who would usually prepare the warehouse tasks for stock consolidation during idle times in the warehouse. These warehouse tasks would either be phased in the queue for the affected storage types/activity areas, or a warehouse internal queue.
For stock consolidation, a warehouse supervisor could select the storage types for picking. His selection would include products with slow or moderate stock turnover rates. Such partial quantities would usually reside longer in the picking zones compared to fast-moving products. Such slower moving products are worth the effort to consolidate. Fast mover would leave the warehouse before they might cram up storage space.
Let us see how the example from the online documentation would look in the transaction.
The product in this example is contained in pallets (PAL). Eight pieces make up a full pallet. This is the largest unit of measure in the product master:
The following selection criteria would be entered in the stock consolidation transaction:
- Warehouse Number
- Storage Type / Storage Section where consolidation should happen
- Product
- Largest Unit of Measure as Target UoM (selected by default)
- Warehouse Process Type (for creation of the warehouse tasks lateron)
Execute the report and the results would look like this:
In the above list, you see the aggregated results of possible stock consolidation options. You see that you can reach one full pallet with one suggested consolidaton move. In the same line, you get the information that you can free one storage bin with this move.
Below, you see the detailed proposals for warehouse tasks. The list contains the move of the three pieces to the five pieces. This would yield the full pallet and free the source storage bin.
The standard behavior is always to move smaller partial quantities to larger partials.
When you are satisfied with the proposals, you can select the proposals and click “Create Warehouse Task”.
When clicking the button "Application Log" , you will find that a warehouse task was created and ready for execution:
The following selection comes closer to a realistic view for stock consolidation. A storage type is selected which contains stock for picking (type PM20). And a selection of products is entered (PM-ACME-*):
The result screen displays all possible consolidation options:
This result relates more to a business scenario with lots of partials. Though in the results, there are options which are not worth creating warehouse tasks because they would pose more effort in execution of tasks than gaining full quantitites.
For example, the first lines do not even yield half a pallet. In the details below, you see that line 3 has proposed moves which cannot free up storage bins. These moves would not even lead to a tenth of a full pallet.
You can already exclude such proposals beforehand by finetuning your selection. This will give you results worth the consideration for warehouse task creation.
Assume, you want to reach at least 80% of full quantities when you consolidate. Than you enter a minimal utilization of 80. In case you always want to reach a full quantity, just enter 100 (to represent full quantity => 100%). Though it is advisable to allow splitting partial quantities further to increate the chances to reach complete utilization.
With this additional parameter the results will only contain moves that finally yield full quantities:
These were some initial examples in this blog post. Stay tuned for following blog post and also posts about frequently asked questions (FAQs).
Did you already collect experiences with the new feature?
What are your questions?
3 Comments
| User | Count |
|---|---|
| 12 | |
| 8 | |
| 5 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
