On Jul 30, 2008, at 9:32 PM, David Jones wrote:
On Wed, 30 Jul 2008 15:23:47 -0400, "Len" <[EMAIL PROTECTED]> wrote:I intended for the user to specify the intended facility. Once the id has been saved on the order item the reservation services would treat the item as always except for the fact that it would simply know which facility tocheck reservations against.Okay, that sounds fine then. A new field would probably be needed, something like "desiredFacilityId".To make it more flexible, could we put it on the OrderItemShipGroupAssoc entity? That would make it possible to specify multiple desired facilities for a single OrderItem if the OrderItem is split among multiple ship groups.We might even be able to simplify it and put it on the OrderItemShipGroup and just say all item in that ship group should ship from the given facility. That would be easier to implement, but would be more restrictive... so nevermind, let's put it on the OrderItemShipGroupAssoc entity.
However adding the facilityId field to the OrderItemShipGroup could be interesting, and would also help to improve the way purchase orders are currently managed: during checkout you can select the facility address in which you will receive the po, but then in the OrderItemShipGroup only the contactMechId is stored; and in the order detail screen the list of facilities that you can use to receive the order is determined filtering them by that contactMechId... a bit funny in my opinion.
Having the facilityId would help to simplify the code. Jacopo
If not enough inventory the item becomes back ordered?Well, that's what the current code does, but is that what you want to have it do?-David
smime.p7s
Description: S/MIME cryptographic signature
