Thanks David, I'll use the code as is and see if anyone bitches. I agree that the logic is complicated, especially considering that a person can just exit their browser and leave things hanging.
Skip -----Original Message----- From: David E Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, October 04, 2007 6:21 PM To: [email protected] Subject: Re: availableToPromiseTotal Most retailers don't consider an add to cart to be sufficient commitment on the customer's part to even try to guarantee that they will get it. I have actually done stuff like that before, but I really wouldn't recommend it because you end up with lots of funny exceptions and it is too easy for data to get in bad states, or for reservations to never get cleaned up and such. This also puts a lot of traffic on certain entities too and can increase chances of locking and other concurrency problems. If you DO want to do this, I would recommend NOT using the current availableToPromise counts and the OrderItemShipGrpInvRes records as those are meant for something a little different, and a little more important to get write (ie reduce chances of interfering with it and what what). -David On Oct 4, 2007, at 7:04 PM, [EMAIL PROTECTED] wrote: > In my wonderings through the ofbiz code, I have noted that > availableToPromiseTotal for items on an order is not reduced until > createOrder is called. I expected availableToPromiseTotal to be > reduced > (assuming there was any) when the "Add To Order" button was pressed. > > This means that if there are 10 people using your system and 5 want > the same > product which has 3 in stock, all 5 will show AOH=3 when they press > Add to > Order, but two will get their order rejected when the order is > processed. > > This is easy enough to change, but I wondered why it was done this > way in > case I am missing something. > > Skip >
