The Job Completion Dashboard will backflush any remaining stock material issues for top-level assembly, record remaining production quantities on sub-assemblies, backflushing component material, record remaining production on top-level assembly, mark the job Complete Complete. This is a great-to-have custom process where we are going to have to accept a level of trade-off. Originally, it was written by Cre8tive and Yoram has improved it greatly. Still,
However, we have some issues with very large jobs. The processing completes, but the screen gets locked on these larger jobs. Yoram reviewed the job in your screenshot and found it has more than 500 labor records. In large Jobs, for example with 500 or so labor records It has improved greatly, but we are going to have to accept a level of trade-off.
In order to accommodate these large jobs, he might try try using the number of assemblies on each job to help create smaller runs, splitting the posting of Job labor to one assembly at a time, rather than 1 job at a time. That will slow down the process but accommodate these larger jobs. It was decided to accept Or, just let the process as it is. It works and it’s a whole lot better than it used to be. Also, we’re entering the Transformation project where we’ll be rethinking all out processes. run. Even though the screen locks, the process completes.