Dead Stock report at sloc level

[lentini6]

The easiest way to explain my request is to refer to the SAP transaction: MC50 Analysis of dead stock
This reports dead stock for material at plant level. This transaction does exactly what I want, but I want it at sloc level, not at plant level. Does anyone know a way to make a dead stock report on sloc?

I can not use MB51 + MB52 + + and use vlookup and pivot table for all branch stores that need this dead stock inventory report. It will take too much time doing it this way for 100 branch warehouses and van stock. The main reason why I want this report is to see what material is in stock that there has been no movement on in for example the last 2 or 3 years. If we can get an overview of this, we may be able to scrap these materials and make room for materials we need and also have a higher stock quantity of these materials that we need in stock. But today this room is occupied by "dead stock material". I know that there is MC46 Slow-Moving items....this could also be usefull IF it was possible to do it at sloc level, not only plant level.

Hope someone can help me here.

Thanks.

[DominikTylczyn]

Hello lentini6

Your question actually touches several important topics. Let me address them one by one.

Organizational structure - as you see SAP provides stock management reports mainly on the plant level as that's the level on which MRP runs. Surely, it also runs on MRP areas level. Still, the reports are mainly on the plant level. So if you need to analyze stock on your warehouses level, then maybe they should have been implemented as plants not as storage location. I'm not advising here to change your configuration. I'm just pointing out that organizational structure definition has a huge impact on reporting capabilities.

Consumption - when analyzing inventory turns or slow movers what counts is consumption not necessarily all material movements. Not all material movements are regarded as consumption. That depends on material movements configuration. For instance, typically storage location to storage location 311 movement type is not counted as consumption. That works nicely when you analyze consumption on the plant level. However in your case you may want to set up 311 as consumption movement as you want to get down to the storage location level with your analysis. Also stock type to stock type movements e.g. release from quality inspection should not be regarded as consumption.

Consumption statistics - whenever a consumption movement is posted SAP updates the material consumption statistics in the MVER table on the plant level and the DVER table on the MRP area level. See the note 1832196 - General information on the consumption update MVER/DVER for the details on the consumption statistics update and how to rebuild the statistics after changes to material movement settings.

Dead stock vs slow movers - these are two different analysis. Dead stock is a minimum stock in the period of analysis. Theoretically dead stock is the excess stock that your carried in the given period. This is the stock that you didn't need to cover the requirements. In other words this is the stock reduction potential. In contrast slow movers are just materials that had not been consumed in the given period.

How to cover your requirements more or less in standard - I can see a couple options to do that depending if you need to dead stock or slow movers analysis.

Use DVER statistics - if you define your warehouses (storage locations) as MRP areas and rebuild consumption statistics. Then you can get the period of last consumption. That will give at least an estimate of your slow movers. Notice that statistics is aggregated to the period defined in the material master. Typically it's monthly aggregation.

Use last consumption date of MC.9 analysis - if your inventory controlling part of SAP LIS works fine (it should unless someone tampered with the standard configuration) then you can report the date of last consumption on the storage location level. This will show you slow movers down to each storage location. If you go this way, make sure to read the notes:

• 2013347 - Date fields not generated for S032 during program RMCBNEUB (OLI2) rebuild
• 1710020 - Last date fields are blank in MC.* reports
• 364607 - Date fields (last movement) after new setup

Use storage location stock of MC.9 analysis - MC.9 displays stock on the storage location level. So you can analyze your materials here and get the minimum stock in a given period for each material. That will be your dead stock analysis on the storage location level.

Use the storage location history stock table MARDH - the MARDH keeps historical stock on the storage location level. So you can write a relatively simple report and get minimum stock in a given period for each material from there. That will serve nicely as dead stock analysis on the storage location level. If you go this way, see the note 193554 - Stock/valuation data of previous periods on the update logic of MARDH and other stock history tables. If you are already on S/4HANA see the note 2600024 - Create a Material, updates History Tables, MCHBH, MARCH and MARDH, with past Years (LFGJA)... that explains differences of the update logic between ECC and S/4HANA.

Custom analysis - the above mentioned approaches give you limited time granularity, restricted either by period aggregation of consumption statistics or by update period of INVCO info structure. That's typically on monthly level. If that's not good enough, then your last option is to build a custom analysis. It should calculate either minimum stock level by day in the analysis period (dead stock analysis) or find the date of last consumption (slow movers).

Best regards

Dominik Tylczynski