MRP Exception Report

[vbcoder85]

We are running Macola ES 9.5, and the MRP Exception report is less then desirable for us. Unless you have the exact amount required on order you are going to get an exception code for too many on order, or that that order is too early.

What we are looking for is a more logical report that we could customize the parameters (if need be) to accomodate what we feel is "too many on order" or what "order to early" really is.

Has anyone created or modified this integrated Crystal report? We've written many crystal reports in house, but this one may be a little tricky since we are dealing with the MREXPFIL and the exceptions are already defined.

Someone must have written this and I figure, why reinvent the wheel. We'd gladly purchase a proven report that start from scratch.

Any thoughts on this would be greatly appreciated!

Thanks

 

[dgillz]

Why is 'too many on order' not really too many on order? And why is 'too early' not really too early?

If we can address specifics we can likely get MRP to run the way you want it to.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"What version of URGENT!!! are you using?

 

[vbcoder85]

Too many on order and too early have very similar problems.

Too many is when our released PO's (qty on order) exceed our required order even though our po min and po mults are within an acceptable range. ie.. If we ordered 25 more then were required, we may have done so due to the fact that our PO min and PO mults wouldn't allow us to order the exact qty required.

As far as the too early goes... if our requested date or promise date (I forget which one) of a PO line item is before the required date (based on MRP), an exception code of too early will be assigned to that PO line item.

The bottom line is that if everything had a PO min and PO mult of 1 and we ordered EXACTLY what we needed and didn't have ANY inventory shrinkage, and ALL PO line items match EXACTLY with MRP requirements, then we wouldn't see these exceptions.

What we were looking for is setting up some limits like plus or minus 2 days... or plus or minus 10% of PO min/mult.

I was hoping someone else may have had similar needs as the exception report does not seem to allow for any tolerances.

 

[dgillz]

The MRP exception reports have a +/- x number of days where you can exclude the exceptions from the reports. If the PO multiple is the issue I believe this should be handled with the planning order multiple on the item master. I am away from an MRP install so I cannot test this.

What has Exact said about this?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"What version of URGENT!!! are you using?

 

[vbcoder85]

There is a due date range, but I can't see any (+/-) day settings to exclude. Even if I was to use a due date range, that doesn't change the fact that the excpetion codes still apply. If there is a +/- day setting I can't find it.

And when I asked our VAR who asked Exact, I get the standard... "This is by design" type of answer. I understand these are just suggestiongs, but I'd like to be able to use the exception report to track down blatent mistakes rather than onesy - twosy type issues.

I also noticed that the CP orders don't seem to take the Planning Ord Mult or Rec Minimu Order in Item Master into consideration, at least, not on a consistent basis. ie.. sometimes it appears to use the mult, sometimes the min. I determined this as I can see the CP orders having multiples of the min and sometimes having multiples of the mult.

Planning Ord Mult - Rec Minimum Order - Sample CP Qty
1 - 10 - 143, 144, 145...
1 - 50 - 100, 150, 200...
0 - 0 - 936, 134, 233...

I can't seem to determine what logic MRP uses to determine what qty to use to come up with the exception results.

Is anyone using the canned Crystal Report for MRP Exceptions?