We’re going to start using fulfillment workbench to populate our material queue with parts ready to be picked. The issue I’m running into is that once the materials are released for picking, they default to an incorrect “To Bin” and “To Warehouse”. Regardless of operation or resource group, all materials are defaulting to the same warehouse and bin.
The materials are on the job with the correct warehouse, and tied to an operation via the “related operation” setting. The resource groups also have the correct in/out bins. Shouldn’t Epicor know that those materials are tied to the resource group’s “in warehouse” and “in bin” via it’s related operation, and populate those values on the material queue?
I cleared the settings here. It removed the defaulting bin but shouldn’t it be smart enough to display the resource group’s bin to which that material will need to be moved to? Now it doesn’t display anything.
Yes, it should populate the RG In bin. If your material queue records are already created, it’s like a snapshot and won’t update. Try going to fulfillment workbench and unreserve and unreleased and then re-release or allocate the parts. If that doesn’t work, try again with a new job.
I created a brand new job, scheduled and released it, released materials for picking through the fulfillment workbench, and the materials still display nothing for To warehouse and bin in the material queue.
Problem PRB0226545: To Warehouse and To Bin are blank in Material Request Queue grid for STK-MTL transactions
This problem was marked as Closed/Resolved on 2024-11-12.
The answer I received from Epicare was to set up allocation templates and assign materials from the fulfillment workbench to those templates to control the to warehouses and bins. That worked, but then the job number, asm seq, and mtl seq disappear from the material queue.
What kind of allocation template did you set up? Was it a wave? When allocating by part, using a Job Pick template I created, I’m seeing the record with the job/asm/seq (but still missing the to location information) in the material queue. It does live within the individual record; I just can’t search/sort in any meaningful way.
Yes, I used a wave initially. It seems that with the wave you don’t get the job information, and with the job allocation, you don’t get a “to” location. It would be nice to get both so we can pick for the job while still being able to determine where it should land.
Wave is designed to be used to pick for multiple jobs/orders at once to help with picking efficiency. When you initiate wave pick, it initially generates a stk-stk transaction; that’s why you lose the job info. After that initial txn, is completed, it creates a new txn for the stk-shp or stk-mtl transaction which regains the job info.
For a standard pick, I have been told that since the values exist in the transaction, you could create a BPM to populate the material request queue table, but I have not tested this myself.
