Large Job - database blocks occur when trying to add subassys

We have a large job(150+ subassys, 2000 parts). Before the engineering BOM was fully complete we did a get details on the job. Now when we try to add additional parts or assemblies we are getting a timeout error and end up with a database block. Is there a way to remove the database blocks? We have on open case with Epicor and have uploaded a copy of our DB but would like to know if anyone else has seen this so we can speed the process along.

We have much larger jobs than that don’t have that problem, so something else is going on. Do you have any BPMs? Any Customizations? Are Cloud?

Just a few questions

  • What is your version
  • Manually entered the methods
  • results in Engineering Workbench --> Actions --> Revision --> Validate BOM?
  • MRP and/or Global Scheduling processes complete without errors?

I saw some issues with MRP bailing at site that had used the DMT to load/revise methods for larger structures. If I remember, a loop in the structure had been introduced somewhere along the line.

10.2.200.14 on premise
We have a few UD fields on job entry but nothing that has caused an issue before. No BPMs. MRP ran successfully last night. The method was entered manually. Validating Bill in engineering workbench was fine.

Now when we try to add additional parts or assemblies
A couple other questions

Are your sequence numbers for materials and operations all multiples of ten?
Any gaps in the numbering sequences for assemblies, materials or operations?

I seem to remember issue in some version where the system might try and renumbering.

Most sequence numbers are multiples of 10 but a few are not. I’ve heard of that issue back in E9 but we “squeeze” in operations/materials quite frequently now.

Thanks for your input guys. We ended up getting a data fix from Epicor to resolve the issue. Some of the child/priorpeer/nextpeer data on the JobAsmbl table seemed to get corrupted when moving assemblies around on the job.