MRP Processes Blank Title 130633

Yahoo Archive
1
I almost forgot - here is some SQL query you can run to try to find parts that take a long time to run.

SELECT  Plant, part.LowLevelCode LLC, pp.PartNum, PrepTime, MRPLastRunDate, 
        'Time' = MRPLastRunTime / 60.0, MRPRecalcNeeded [Recalc?], MRPLastCutOffDate, MRPLastScheduledDate,
        NeverReuseMRPJob [Recycle?], ProcessMRP, DeleteMRPJobs
FROM    Epicor905..PartPlant pp
        JOIN Epicor905..Part ON pp.Company = part.Company AND pp.PartNum = part.PartNum
WHERE   ProcessMRP = 1
ORDER   BY pp.ProcessMRP, pp.MRPLastRunDate, [time]

Just scan down the MRPLastRunDate until you find the date that had the extra long time, and then scan down the "Time" columns (which is minutes from midnight) until you find a big gap or jump.  That would indicate a part that took a long time.

2

Have others seen where your MRP process takes quite a bit longer on a given night?  We have our process setup as a scheduled task so the same parameters are ran each night.

 

Thanks

 

Michelle Chamberlain

ERP Analyst

Sabre Industries

Direct Line:  (712) 224-1452

Phone: (712) 258-6690 ext. 11452

Fax: (712) 279-0817

 

3
Ours takes close to twice as long if there is an abandoned processor (or a few).  Have you checked your main log for abandoned processors? 
4
We have a part number that is a planning bill - and we run net changes every night. The planning bill has as materials 20 or 30 of our finished good parts, which are like 7 layers deep of BOM - quite a few materials and operations. So if something touches that part (which happens fairly frequently) and the net change determines it needs to process that part, the MRP run will take hours longer than without that part.  Just a thought. May not fit your situation at all.