Many customers ask to consume production DBA in back flushing at report as finished or at route registration. This operation is not correctly possible at the moment in a WHS warehouse, because WMSlocations are not compiled in production picking list. I understand that procedure should be: -reservation -release to warehouse -elaborate wave that find material already in correct WMSlocation (default production input or resource location) and transaction become picked or reserved physical. This procedure doesn't match back flushing requirements, because I cannot consume or reserve anything at realease but only at report as finished or at process registration: the first material I consume/reserve must be the first material actually used and not the first material released. Thank you in advance for you rfeedback

Johan Hoffmann (administrator) on 4/21/2022 9:13:09 AM
Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Johan Hoffmann
PM, Microsoft