David,
I would like to keep this thread alive as I see adding the facility to the
order item ship group will be useful for all. I also have the time at the
moment to make the changes we discuss and submit as a JIRA back to the
community.
Before I make any changes I would just like to insure we are all on the same
page as to what the changes should be. So far I have identified the reserve
inventory services that need to change (see below). Do you want me to look
into writing up changes for the Data model and the shopping cart to accept
and process a facility id on order generation?
We can also look GUI changes needed for accepting a facility on order entry.
What do you think?
Order Services
Method: reserveInventory()
In the reserve inventory method of this service each order item is
interrogated to see if the fromInventoryItemId was passed. If so the
related facility of the item is passed to the reserve Inventory
service specifying where availability and reservations should be done.
Reserve Store Inventory
ProductStoreServices.xml
Simple Method: reserveStoreInventory
Modified the service parameters to accept an optional 'facilityId'
field.
If a specific facilityId is passed in to this method:
Perform sanity check against the entity:ProductStoreFacility to
insure the facility has been associated to the product store (required
param of the service). In other words does this Product Store ship
products from this facility?
Call Simple Method reserveProductInventoryByFacility.
- Len
-----Original Message-----
From: Jacopo Cappellato [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2008 7:45 AM
To: [email protected]
Cc: Nick Rosser; Dave Tenerowicz; [EMAIL PROTECTED]
Subject: Re: Creating Single orders whcih have products thatneed to ship
from differnt facilities
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 to
>> check 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
>
>
>
>
