R30601 - how long does it take to run?

[Zaki Ahmed]

Hi,

We are having performance issues with R30601. It runs for 22 long hours every night in Production and we run it every night because we have daily changes in BOM structure and need to fix Lower Level Codes.

My question is, how long does it take to run for you? Because, in our lower environments, we have seen it finishing in 6 hrs or so and we don't know why it runs for longer hours in production as file size between PY/PD is not much different. Our F3002 file size is about 8.5 million records.

Is there anyway we can improve the performance?

 

[Larry_Jones]

Hello Noor,

We also run R30601 every night. Our run time is ~ 35 minutes but . . . our F3002 is only 850K rows - 1/10th the size of yours.

I'm guessing that the other environments run on a different (test) hardware setup, right? The biggest slow down for a large batch job like this is contention from other batch jobs running at the same time. Given that even by itself its running 6+ hours you probably don't have a time window to run without contention. You probably have MRP running at the same time as R30601 and possibly Leadtime rollup? Cost rollup? etc . . . Some of these batch jobs should never run simultaneous with each other for reasons other than performance.

If the majority of the assemblies in your F3002 are historical (not actively sold / manufactured) consider using some sort of data selection in R30601 to reduce the items processed.

Otherwise you can investigate tuning your database but as long as you're doing the basics in updating the stats regularly you're not going to get enough out of that to fix your situation. Because even a 6 hour window is too long. Either management is going to have to step up to the plate and purchase hardware sized for your needs or you need to give up running this job on a nightly basis and switch to weekends.

 

[DSauve]

Are you using standard JDE applications to maintain your BOM's? If so, you can turn on the "On-Line BOM Validation" option in your Manufacturing Constants program (P3009), and your low level codes will then be maintained as BOM records are being added. And if you do this, you should only need to run R30601 periodically as a "catch-all" cleanup -- maybe weekly or monthly, unless you have some other reason to run it.

 

[Zaki Ahmed]

No, we are not using online application to maintain BOM. Instead we use Agile Interface with JDE and Agile to JDE Adapter times out if it doesn't receive communication back from JDE if Online Validation is turned on and it takes too long to run. That's the issue.

And, R30601 doesn't allow any data selection so that we could limit the data to be processed. Bummer!