Hallo,
this problem is driving me crazy.
Here’s the scenario:
I have a database of 15,000+ items, but only few hundreds are items that are regularly manufactured/purchased/sold (but I need them all as they all are “live” items). Some of them are sourced via purchasing, some other via production order. Navision W1 5.0
I calculate the regenerative plan every month to generate a 3-month worth of purchase orders and a year-long purchase forecast plan. I have Sales Orders in the system covering a month, and then Blanket Sales Orders covering one year (for forecasting purposes with my supplier, although effectively the 2nd and 3rd month are purchase orders on Blanket Sales Orders).
I noticed that the suggested Purchase Order proposals generated by calculating the regenerative plan, change (in volume, number of lines, etc.) depending on wheter the “No.” field in the “Item” tab of the Calculating regenerative Plan is left A: blank or B: “*”. This without changing any other setting, I tried few times running the two options back to back.
Moreover, even when calculating the plan leaving No. ="*" (which at first seemed “better” in output than leaving the field blank), I noticed that some purchase order suggestions (which I would have expected) were not generated. BUT, when re-calculating the regenerative plan for a specific item “A” (No.=“A”), then the expected suggestion are actually generated ?? This not only for one isolated item, there are actually quite a few.
I’ve been then suggested to calculate first the MPS regenerative plan, and then the MRP regenerative plan. The things seemed to be improving (i.e. a certain level of purchase order suggestion are generated almost as expected), but nonetheless I still see some items for which purchase order proposal are underestimated when looking at the Sales and Blanket Sales Order in the systems.
I can’t understand why this is happening. Despite any setting of the item card, I would expect that the Regenerative Plan would be consistent when ran with the different method I listed above, but it does not seem tha case.
Is this some sort of known (not to me!) bug ?
Your precious help woul be very much appreciated. Thanks!!