Re: Serialized Inventory issue with backorder item

[Deepak Dixit <de...@hotwaxsystems.com>]

Thank all for your valuable suggestion,
Here is the ticket for refactoring work OFBIZ-9475
<https://issues.apache.org/jira/browse/OFBIZ-9475>

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Fri, Dec 23, 2016 at 4:01 AM, Scott Gray <sc...@hotwaxsystems.com>
wrote:

> +1 on binding status to InventoryItemDetail.
>
> Regards
> Scott
>
> On 22 December 2016 at 21:50, Jacopo Cappellato <
> jacopo.cappellato@hotwaxsystems.com> wrote:
>
> > Very interesting thread, thanks to you all for the valuable exchange of
> > information.
> >
> > My two cents:
> > * it would be great to refactor Serialized items to maintain
> > InventoryItemDetails records (rather than statuses) for Serialized items
> > and then apply the same business of non-serialized items logic for
> counting
> > QOH/ATP: this will simplify the inventory logic, simplify reporting
> > (including SQL based reports) maintaining all the features of Serialized
> > and Non-Serialized items
> > * as regards the back-ordered items (aka negative ATP aka deficit aka
> > placeholder aka virtual aka dummy inventory): maybe we could introduce a
> > new inventory item type ("BACKORDER" or better name) that will always
> have
> > QOH=0 and ATP<=0; it will only be used as a placeholder to store
> > reservations when QOH is zero; its behavior would be the same of a
> > Non-Serialized item and the system will create such records if not
> already
> > there (in this way there will be up to one InventoryItem of this type for
> > each ProductFacility record)
> >
> > Regards,
> >
> > Jacopo
> >
>