Comments
Agree, this should be an option in standard. We have customized to solve this many times and also agree that status loaded should give option to post and print packing slip. We have used Print Management to set up printer that has worked well for us as this gives many options to set up where to print.
Visualization didn't work as I designed it and I can't edit, so here's another attempt:
.................................................................sequence start
.................................................thread 1............................thread 2
.....................................................|.......................thread 3.............thread 4
.................................................step 1..........................|........................|
.....................................................|...............................|........................|
.................................................step 2 <<<.---------------|--------------------|
I would like that Microsoft adds an option on the request page of the report "Link to Accon" by which the user has the possibility to select the no. of digits (for g/l account ) to export. Of course, we all know that the No. in the chart of accounts is 20. There is no need to modify table 15. Just give the BE user the possibility to create a valid Accon file.
MRP as a philosophy is designed to run you out of stock. I.e. to optimise the stock holding. The original X++ design in earlier versions of AX of course handled the invoiced orders case. As someone with 36 + years of experience with ERP/MRP systems I can't see that this is usable for any customer who wants to upgrade or a new customer. It seems that planning optimisation is not optimising the stock and although I can see the this is listed as a difference between the original engine and the PO engine (https://learn.microsoft.com/en-us/dynamics365/supply-chain/master-planning/planning-optimization/planning-optimization-differences-with-built-in) - I don't think Microsoft should be advertising that its planning engine is not designed in line with MRP philosophy and all other MRP products in the marketplace !
MRP as a philosophy is designed to run you out of stock. I.e. to optimise the stock holding. The original X++ design in earlier versions of AX of course handled the invoiced orders case. As someone with 36 + years of experience with ERP/MRP systems I can't see that this is usable for any customer who wants to upgrade or a new customer. It seems that planning optimisation is not optimising the stock and although I can see the this is listed as a difference between the original engine and the PO engine (https://learn.microsoft.com/en-us/dynamics365/supply-chain/master-planning/planning-optimization/planning-optimization-differences-with-built-in) - I don't think Microsoft should be advertising that its planning engine is not designed in line with MRP philosophy and all other MRP products in the marketplace !