Hi Bob,
another thing you could consider to use (or expand) is the statusId in
the InventoryItem: there should be already code in place that ignore
(for reservations etc...) items based on their status.
Then you could implement some user friendly screens (or even business
processes) to manage the status of the inventory items in a given
location (or a defaultStatusId for all the items in the location);
during stock moves you could change status of items to make them ready
for sales.
Regards,
Jacopo
On Aug 8, 2009, at 8:16 PM, Bob Morley wrote:
Right now we primarily use Ofbiz to model a b&m store. Part of
doing this
means POS driven interaction with the customer and immediate
fulfillment as
part of order entry. What this means for us is that the act of
choosing
particular inventory items and having them selected form the proper
facility/location is very important.
In a number of business processes we have the notion of inventory
items not
being "salable". This is often based on the physical location of the
inventory item (or perhaps even at the facility level). Here are some
examples:
a) Inventory is purchased and has been initially "received" but is not
necessarily available to sell at this particular facility. We model
the
notion of a "primary store" that does ordering and when a shipment
comes in
they will group up and inventory transfer to a destination store.
During
this business process inventory should be in a location in that
facility,
but should not be pickable during inventory reservation, etc.
b) Inventory is marked as damaged and needs to have work done on
it. These
items often will be fixed on premises but again should not be sold.
You
also have the reverse situation where the items are going to be
shipped
offsite, but right now remain in your facility waiting for shipment.
c) The first party of inventory reconcilation is "inventory counting";
individual locations are counted and variance in items result in
those items
being moved to a "lost and found" location. When other locations
are done
these variances may be resolved form the "lost and found" but
ultimately a
true reconciliation is performed on the "lost & found". Naturally
"l&f"
inventory items can not be sold.
So the million dollar question -- what is the best way to model
this. One
approach would be to model these other locations as difference
facilities in
that product store. Since we (currently) use a single inventory
facility
they would not be salable. While that is an approach my gut tells
me it is
not necessarily the best approach.
What I was planning on doing is expanding the notion of
facilityLocation to
have the idea of being "salable" or not. If memory serves, the
current
inventory reservation services will go through all "PICKLOC" and
"BULK"
types when doing reservation. Initially I had added new types that
would
not be salable; but I am thinking it might be better to actually
have an
attribute on the facilityLocation that indicates if you can sell
from that
location or not. I guess I could also go with a "NOPICKLOC" or
something
similar for these other locations ...
Am I modeling this completely incorrectly, is there something I
missing,
does anyone have any advice?
--
View this message in context:
http://www.nabble.com/Inventory-reservation-fulfillment-and-the-notion-of-a-salable-location-tp24878041p24878041.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
