MRP Inventory Aging Report

[rvb001]

In Macola Progression 7.6.200, I am running the MRP Inventory Aging Report. According to the Macola help screens this report -
provides demand, supply, inventory, and inventory value in a user-defined aging format. This report uses a cutoff based on the combination of last issue, last usage, last sold, and last receipt to evaluate slow moving items. The user definable buckets allow for future projections for those slow moving items.

I run it, and I don't see this happening. Has anybody used this sucessfully? Is it necessary to have a history of regens to get historic data? My GM is looking for a method to look for the value of inventory that has not been used in 90 - 180 days.

 

[kstickler]

We have never used this report.

What you really want to do is get a value of your unused inventory. We use a Crystal Report for this. It looks at the IMINVLOC Prior Year Usage for our purposes.

I believe that you could use the IMINVHST file. It tracks PTD usage for the last 24 periods (If 24 periods are set up in your IM Setup - we use 12). At the end of each period, when the clear accumulators process is run, the oldest period "rolls off" to make room for the new period. So if you are looking at unused inventory for the last 90 days, you would check for 0 for periods PTD_USAGE_01, PTD_USAGE_12, PTD_USAGE_11 etc....

 

[SusanD5320]

If you use the IMINVHST file, be careful if your fiscal year is different from the calendar year.

Our year ends on 4/30 so the December 2005 data in the IMINVHST file appears in period 8. Period 9 currently contains the data from January 2005 and will be over-written with Jan 06 data when we close that month.

 

[AKPolarBear]

Also be careful of accounting "oops" when they close twice by mistake in one month. That will roll your period buckets off by one. I.E. if they do this in Feb: period 1 = Jan, per2 = Feb, per3 = Feb, per4 = Mar. Conversely per 13 should be Jan unless errors are made. Then you need to keep the years straight, year 1 = per1 - per12, year 2 = per13 - per24 and then it rolls over after 24. Also data in those buckets is not cleared out until the actual current period overwrites it so they may contain old data.

We used this method for a while but it became a hassle to maintain. I finally came up with a crystal using the history file and running totals based on current year or currentyear-1. I am about to modify this further to allow input to select years to compare. Not a perfect solution as it requires additional information to work but it works.