I am in the process of upgrading from 2.6 to 3.10a. We are testing the Requisition Worksheet and finding that no matter what we put in for reordering rules that we do not get correct reorder amounts. I believe there is a bug in Attain - Safety Stock seems to be ignored regardless, and when we try to use the Maximum Inventory field, it then ignores some orders. Does anyone know about this “bug”? Or how to get around it? Thanks, Debbie
Unfortunately the planning in 2.60 worked much better that in 3.10A. In 3.10 using some parameters like Safety Stock or Maximum Inventory makes the planning unpredictable. The problem is in codeunit 99000854: Inventory Profile Offseting. There are two versions of this codeunit: 3.10 and 3.10.01. The second version fixes some errors but the results of the planning using these two field are worse. The problem is that fixing it is not very simple becaouse of the complexity of the codeunit. [:(]
We went live in March this year (3.00), and we’ve finally obtained a satisfying Requisition Worksheet. But not until our NSC did much effort to design a complete adjustment in codeunit 99000854, named Limited Planning Flexibility. With this functionality the planning process is much more comfortable and meets daily practise requirements. I think the adjustment is for sale as Add On. For info: Foqus-ICT (www.foqus-ict.com) The Netherlands
Hi I´ve the same Problem. I think this change is the most problematic in Attain. Does anybody know the code to change in this Codeunit or send me an example ? Thanks !