We have a part with a primary warehouse and bin assigned to it. It is set to backflush on a job, and the operation resource group has a different bin setup as the backflush bin. From what I understand in the backflushing heirarchy is that primary bin should be last. It should be pulling from what is assigned in the resource/resource group section first.
I recently DMT’d primary bin for some parts and it will jump straight to backflushing from this bin versus the one assigned in the resource group. Any ideas why it is skipping the hierarchy?
I saw this thread exists:
but it didn’t fully answer it. I had tested the same set up in our QA environment and it was backflushing correctly
The resource group/resource group was not changed at all. Primary bin on the part is Bin07, and the backflush bin on the resource and resource group is still Bin03. The DMT was only to the part, so I am stumped on why that would change the hierarchy logic?
Process some jobs - Mtls pull from BF Bin, as expected
Use DMT to change the Prim Bin on the part.
Process some jobs - Mtls pull from Prim Bin, not BF Bin
That’s what your’e seeing?
If the Resource Grp’s BF Bin is changed to something else, saved, and then changed back to the desierd BF Bin, do future Mtl Trans now use the correct bin?
I tested the manual change in QA, everything worked great. I DMT’d the same list into QA and everything still works great. I checked site config, company config, warehouse settings, bin settings, resource and resource group settings. Everything is the same…
For anyone curious, finally found the issue. We have an external application that submits the labor dtl data to Epicor through REST API. Just found out we do not always pass the resource group or resource ID. Since the labor dtl is missing those values, it goes to the next step in the hierarchy since it has nothing assigned for that transaction.