>>as non-stock and the costing method is average.And any backflushing?
I remember having mtl costs problems with Average costing and non-stock (job to job)
In my case... I believe mtl's weren't fully issued in the child job before that job part was issued it to it's parent
- either manually or by the system due to backflushing when "completed" qty(s) were entered on the final operation in MES.
I can't remember how I spotted it originally.
I built a series of reports that are run at the end of each shift now for listing any jobs with cost/qty exceptions.
As long as I catch them the same day, pretty easy to clean up.