Backflushing Default Bin Issues

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 :worried:

Does a manual change (via the UI) of the Primary Bin cause the problem to happen as well.

And does the Resource Grp’s backflush bin get changed when this happens?
(on either manually changed Prim Bin, or via DMT)

I have not tested manually changing it.

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?

How many warehouses?

Both from the same warehouse

What’s the In Bin set to?

FWIW - We don’t use resource groups or backflush, so I’m just throwing ideas out - and hopefully learning about them in the process.

edit

My question about the “In Bin” is because …

since we don’t have our resources or resource groups set as auto move, we don’t use the in or out bin (They are read only). Just the backflush bin.

I still understood it that it should follow this:

(1) Planning Contract
(2) Input/Output warehouse on resource
(3) Input/Output warehouse on resource group
(4) Backflush warehouse on resource
(5) Backflush warehouse on resource group
(6) Primary bin
(7) Bin that has same UOM that has an on hand qty greater than 0
(8) First bin associated with the material

Both bins have an on-hand quantity yet it is choosing the primary bin over the backflush warehouse on the resource/resource group.

The steps to make this repeat are:

  1. Setup part and its Prim Bin

  2. Setup Resource Group with desired Backflush Bin

  3. Process some jobs - Mtls pull from BF Bin, as expected

  4. Use DMT to change the Prim Bin on the part.

  5. 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…

This has me stumped

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.