Reserved Quantity (Base) Error

When attempting to Backflush the components for a production order the user is getting the message reserved quantity (base) must be reduced. I have looked at other posts regarding this but they say that it was fixed at V3.7 this is V4.0 SP1. WHen I look at the field is contains 0, is this a set up issue? The production line and component quantities are all ok, the reservation quantities are all ok ??? Any ideas?

Hi Damian Can you reproduce this on every production order? Are you doing this in Cronus? Are all items backflushed at order completion or routing? Are you using the production journal or the output journal? What are the reservation settings on the items? I have not tried SP1 for this but I have access to Cronus I will give it a go.

We are using 4.0 SP1 but we are still experiencing this problem. Have you guys figured out how to solve this?

Having a slight issue getting 4.0 SP1 working when I have 4.0 on my machine, it does not seem to like it, although if two of you are hitting the same issue it is probably not a setup issue. I will try as soon as I have a copy of 4.0 SP1 working

I have replicated the error on Cronus 4.0 SP1. I raise a Production Order for an manufactured Item, the components are set to always reserve and to backflush when the status of the Pr. Order is changed from Rel. to Fin. The Output journal is posted for a qty less than the expected quantity and the Finished field is ticked. I then change the order status to Finished, the program attempts to backflush the components but displays the error. Microsoft support have been working on this for at least a week and cannot work out why the error is happening. They seem to think that the reservation entries are being corrupted somehow!!!.

Lovely [:D] Are you using an established Cronus item and BOM or your own Damian? You would think they would be able to locate the change between 4.0 and 4.0 SP1 in this area, but obviously not. I see they have tried to do something with backflushing with bins and/or serial numbers which still is not working, but I have not actually got my hands on the software yet!

I create a brand new (end) Item and BOM, the component Item is an existing Cronus Item with the Flushing method changed to Backward and Reserve set to Always. I think I have used 80103 or something like it. It’s something within V4 SP1 as our testing on V4 did not bring out this error. Initially the message was something like “Assertion Failed”, Mircrosoft then gave a code fix which disabled this message but seems to moved the error and displayed the “must be reduced message”.

Have you tried it with your own component? 80103 is serialised (freeentry) sure it is not causing the issue but you may need to check. I will eventually catch you up on SP1.