Yes I think I posed that original one in haste. When I started doing the work yesterday for it I quickly realized that it would make much more sense to leverage the statusId on an inventory item. So what I ended up doing was extending the facility entity to have a defaultLocationSeqId.
This change I did in our own hot-deploy because I was unsure if it is something that has community appeal. From memory I believe most of the Ofbiz screens would ask for a location using a lookup field (and would accept blank). In our UI we are more apt to use a dropdown for locations with-in a facility so the default lends itself nicely to pre-populating the dropdown (blank is allowed). Do you think it makes sense to extend Facility in this way? If so I can replace my entity-extend with a modification to Facility and make the minor change to the add/edit form and provide the patch. Naturally, its value would not be used anywhere initially ... Do you think there is value in doing this? Jacopo Cappellato-4 wrote: > > 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 > > -- View this message in context: http://www.nabble.com/Inventory-reservation-fulfillment-and-the-notion-of-a-salable-location-tp24878041p24893785.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
