When using the Job Split process (something we use quite often) we noticed that when the process hits a material sequence where the Required Qty is 0 that all of the material sequences after that have a 0 in the Issued Qty on the new job. Here’s an example, I have a job with 10 material sequences. Sequence 4 and 5 have 0 required qty but the others all have a required qty of 2 and a issued qty of 2. After the split the new job has 10 material sequences except that lines 1 - 3 have an issued qty of 1 while 4 - 10 have 0 even though lines 6 - 10 should be 1. The original job shows an issued qty of 1 on lines 1 - 3, a 0 on 4 - 5, and 2 on 6 - 10. Has anyone else ran into this issue? It appears that the process is loading 0 in the issued qty for all material sequences after the ones with a 0 required qty.
No they are different operations. Reason for splitting in this particular example is expediting an order. This is what I got from EPICOR:
I managed to replicate the issue in a training environment and reported it as a new bug, you can follow its progress here on the portal under these numbers:
PD System Number have been updated to: ERPS-159772
PD State have been updated to: Submitted to Development
The split job functionality is very sensitive. I have always told people to reduce the original job and create a new one. I did extensive testing a couple of years back and if you don’t do exactly what the system is expecting, you get very unexpected results.
When you split a job, the “new” job gets any available (issued) material. Any shortfall in material will be on the original job after the split.
When you split a job, the “new” job gets any available (reported complete) labor. Any shortfall in labor (reported complete) will be on the original job after the split.