Because of that, I would try to make a case to issue those materials as they are used, if I were in your position.
1 Like
Inventory accuracy is the thing of dreams and nightmaresā¦
Whether you are issuing or back flushing the procedure for physically
counting the parts on the floor needs to be followed carefully.
Either way the jobs released to production need to be considered as to
whether the physical parts pile you see in a given bin or location are
already issued or back flushed or not.
You can have problems either way. If you go to the extra steps needed to
issue parts I would recommend the people closest to the process own this
step.
Brad
2 Likes
You should setup KanBan for your backflush then. We transfer to a production bin and the job backflushes from that bin. The transfer can be completed through the material queue or fulfillment workbench. The KanBan monitor can be used to track your levels. If you are interested in this let me know and I can explain it in more detail.
@Chris_Conn - We are running into the exact issue you have described. Do you happen to have an up to date copy of the code you used? I am working on figuring out how to run the customization you describe.
Be careful here. MTL-MTL produces no GL transactions. STK-STK does (see attachment)
Make sure you check your tests in GL to make sure you arent creating other issues
Hey Brad,
Unfortunately I do not have access to it. Iāve since left the company to join the dark world of Epicor development consulting.
Ultimately, the goal was to leverage the functionality of the material request queue with stk-stk (inv transfers). Dave is correct in his warning, but in our case, we were still backflushing, we just wanted to flag move requests from inventory (warehouse/storage bin) to the backflush bin.
You can get around this is you do an Inventory Move Request instead. In my case, I wanted the functionality of picking material from a job bom, which is why I did this, Iāve learned a little since then, and it may even be easier to make a customization on the inventory move request screen to allow the user to enter a job and then list the bom mtls for them to pick. Then you arenāt forcing the system to bend to your will, eventhough its kinda fun sometimes.
If you wanted to go that route, you could start with a BAQ thatās lists the bom mtl for either a job or part param, then call it with DynamicQuery adapter. @josecgomez has a great video on the subject that I am sure you can find a link to here on the forum. You could then either use the resulting dataset to populate a grid or a combo the user can select from.
Let me know if you get hung up and Iāll see what advice I can offer. ps - you with aepl?
2 Likes
Thank you! Iām to new to this level of customization but can certainly appreciate how customizing the Move Inventory Request may be easier.
Yes, I am with AEPL - you wrote a customization to the handheld that I tested yesterday.
1 Like
Thanks Dave. We are trying to have our Warehouse receive a request from production to pick the part, it would then go into the material queue, and when the material queue is processed, the part now exists in a different bin as it has been picked. The production team then issues the material from the new bin to the job. Any suggestion on best practice to accomplish this is appreciated.
Does anyone have an example of a C# api rest call doing a material transfer? Really strange, Iāve tried tracing the material transfer and nothing is collected.