Serialized Inventory issue with backorder item
Locked
Serialized Inventory issue with backorder item
 
|
Hello All,
In OFBiz, when we create an order for product with serialized inventory with quantity more than ATP then a negative ATP Inventory Item record is created, which is of type Non-Serialized. It should be of type serialized . If we resolve this issue, we need to check all scenarios related to this process. Please let me know your thoughts. If it looks good I will open a ticket for the same. Thanks -- Regards, Renuka Srishti |
Re: Serialized Inventory issue with backorder item
|
|
Hi Renuka,
In this case, the non-serialized inventory acts as a placeholder to ensure the final ATP is correct. This is correct behaviour, and not a bug. Regards, James
|
Re: Serialized Inventory issue with backorder item
|
|
Hi James,
System create new inventory item each time, it does not use single InventoryItem for all backorder. So it create incorrect inventory item(s) data for serialized inventory item. I think we can refine serialized inventory item support under https://issues.apache.org/jira/browse/OFBIZ-7762 As per current implementation serialized inventory logic implemented on status, and non-serialized inventory logic implemented on InventoryItemDetail. Ideally both should use IID and if item is serialized than qoh can't be greater then one, if we go with this route than we can implement status base check on both type of inventory item. Like if inventory item is defective than we can set its ATP to zero for both cases etc.... Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Sat, Dec 17, 2016 at 8:42 PM, james yong <[hidden email]> wrote: > Hi Renuka, > > In this case, the non-serialized inventory acts as a placeholder to ensure > the final ATP is correct. > This is correct behaviour, and not a bug. > > Regards, > James > > > Renuka Srishti-2 wrote > > Hello All, > > > > In OFBiz, when we create an order for product with serialized inventory > > with quantity more than ATP then a negative ATP Inventory Item record is > > created, which is of type Non-Serialized. > > It should be of type serialized . > > > > If we resolve this issue, we need to check all scenarios related to this > > process. Please let me know your thoughts. If it looks good I will open a > > ticket for the same. > > > > Thanks > > > > -- > > Regards, > > Renuka Srishti > > > > > > -- > View this message in context: http://ofbiz.135035.n4.nabble. > com/Serialized-Inventory-issue-with-backorder-item-tp4700367p4700409.html > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > |
Re: Serialized Inventory issue with backorder item
|
|
Hi Deepak,
Issue ==== Renuka: “when we create an order for product with serialized inventory with quantity more than ATP then a negative ATP Inventory Item record is created, which is of type Non-Serialized.” Pro for using Non-Serialized type ======================== 1. As the placeholder record in Inventory Item is of type Non-Serialized, it can be used to store any number of negative ATP quantity. 2. If the sales order is cancelled, we only need to update that one record. Con for using Non-Serialized type ========================= 1. The placeholder record in Inventory Item cannot be reused when the actual Inventory Item is received. Yes we can further discuss / refine on the serialised inventory item support in the JIRA. I also concur with you that InventoryItemDetail should also be used for serialised item, and the logics for ATP/QOH of a serialised inventory item. Thank you. Regards, James
|
Re: Serialized Inventory issue with backorder item
|
|
In reply to this post by Deepak Dixit-3
Thank you so much Deepak for the detailed explanation.
Thanks James for sharing your thoughts. Regards, Renuka Srishti On Mon, Dec 19, 2016 at 12:24 PM, Deepak Dixit < [hidden email]> wrote: > Hi James, > > System create new inventory item each time, it does not use single > InventoryItem for all backorder. So it create incorrect inventory item(s) > data for serialized inventory item. > I think we can refine serialized inventory item support under > https://issues.apache.org/jira/browse/OFBIZ-7762 > > As per current implementation serialized inventory logic implemented on > status, and non-serialized inventory logic implemented on > InventoryItemDetail. > > Ideally both should use IID and if item is serialized than qoh can't be > greater then one, if we go with this route than we can implement status > base check on both type of inventory item. > Like if inventory item is defective than we can set its ATP to zero for > both cases etc.... > > > > > > > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > > On Sat, Dec 17, 2016 at 8:42 PM, james yong <[hidden email]> wrote: > > > Hi Renuka, > > > > In this case, the non-serialized inventory acts as a placeholder to > ensure > > the final ATP is correct. > > This is correct behaviour, and not a bug. > > > > Regards, > > James > > > > > > Renuka Srishti-2 wrote > > > Hello All, > > > > > > In OFBiz, when we create an order for product with serialized inventory > > > with quantity more than ATP then a negative ATP Inventory Item record > is > > > created, which is of type Non-Serialized. > > > It should be of type serialized . > > > > > > If we resolve this issue, we need to check all scenarios related to > this > > > process. Please let me know your thoughts. If it looks good I will > open a > > > ticket for the same. > > > > > > Thanks > > > > > > -- > > > Regards, > > > Renuka Srishti > > > > > > > > > > > > -- > > View this message in context: http://ofbiz.135035.n4.nabble. > > com/Serialized-Inventory-issue-with-backorder-item- > tp4700367p4700409.html > > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > > > |
|
|
In reply to this post by james yong
For most of the businesses serialized inventory tracking starts only after
such eligible products come into physical existence (in Ofbiz parlance we generally try identifying it with inventory having QOH > 0). At application level as well any real & definitive serial number could be assigned once products are physically received or produced in system and are ready to be scanned/shelved at warehouse or store level for further tracking. Backorders in Ofbiz world create nothing but virtual(dummy) inventory pegged to such orders to identify how much demand still remains unfulfilled after exhausting on hand stock. It doesn't matter whether at application level such virtual inventory data is serialized or non-serialized. Of course any virtual inventory representation in serialized from would create more data debt than non-serialized ones. So if we decide to retain BOs against serialized product tagged with non-serialized inventory (via OISGIR), upon receiving and allocating actual reservations we can make sure to release all non-serialized inventory and reserve them using available serialized inventory (having ATP > 0). Thanks & Regards, Swapnil -----Original Message----- From: james yong [mailto:[hidden email]] Sent: Tuesday, December 20, 2016 11:20 AM To: [hidden email] Subject: Re: Serialized Inventory issue with backorder item Hi Deepak, Issue ==== Renuka: “when we create an order for product with serialized inventory with quantity more than ATP then a negative ATP Inventory Item record is created, which is of type Non-Serialized.” Pro for using Non-Serialized type ======================== 1. As the placeholder record in Inventory Item is of type Non-Serialized, it can be used to store any number of negative ATP quantity. 2. If the sales order is cancelled, we only need to update that one record. Con for using Non-Serialized type ========================= 1. The placeholder record in Inventory Item cannot be reused when the actual Inventory Item is received. Yes we can further discuss / refine on the serialised inventory item support in the JIRA. I also concur with you that InventoryItemDetail should also be used for serialised item, and the logics for ATP/QOH of a serialised inventory item. Thank you. Regards, James Deepak Dixit-3 wrote > Hi James, > > System create new inventory item each time, it does not use single > InventoryItem for all backorder. So it create incorrect inventory > item(s) data for serialized inventory item. > I think we can refine serialized inventory item support under > https://issues.apache.org/jira/browse/OFBIZ-7762 > > As per current implementation serialized inventory logic implemented > on status, and non-serialized inventory logic implemented on > InventoryItemDetail. > > Ideally both should use IID and if item is serialized than qoh can't > be greater then one, if we go with this route than we can implement > status base check on both type of inventory item. > Like if inventory item is defective than we can set its ATP to zero > for both cases etc.... > > > > > > > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > > On Sat, Dec 17, 2016 at 8:42 PM, james yong < > i_yongbl@.com > > wrote: > >> Hi Renuka, >> >> In this case, the non-serialized inventory acts as a placeholder to >> ensure the final ATP is correct. >> This is correct behaviour, and not a bug. >> >> Regards, >> James >> >> >> Renuka Srishti-2 wrote >> > Hello All, >> > >> > In OFBiz, when we create an order for product with serialized >> > inventory with quantity more than ATP then a negative ATP Inventory >> > Item record >> is >> > created, which is of type Non-Serialized. >> > It should be of type serialized . >> > >> > If we resolve this issue, we need to check all scenarios related to >> this >> > process. Please let me know your thoughts. If it looks good I will >> > open >> a >> > ticket for the same. >> > >> > Thanks >> > >> > -- >> > Regards, >> > Renuka Srishti >> >> >> >> >> >> -- >> View this message in context: http://ofbiz.135035.n4.nabble. >> com/Serialized-Inventory-issue-with-backorder-item-tp4700367p4700409. >> html Sent from the OFBiz - Dev mailing list archive at Nabble.com. >> -- View this message in context: http://ofbiz.135035.n4.nabble.com/Serialized-Inventory-issue-with-backorder-item-tp4700367p4700614.html Sent from the OFBiz - Dev mailing list archive at Nabble.com. |
RE: Serialized Inventory issue with backorder item
|
|
Hi Swapnil,
One enhancement we can do for the non-serialised dummy inventory item is to use a different numbering sequence with a letter prefix, e.g. 'X100001', for the Inventory Item Id. In this way, the numbering sequence for the actual inventory item is not affected by the dummies. When the dummy inventory items get too many, job scheduler can be setup to periodically remove the dummies that are not associated with any OISGIR. Regards, James
|
Re: Serialized Inventory issue with backorder item
|
In reply to this post by Deepak Dixit-3
Hi Renuka, James and Deepak,
You could argue that an InventoryItem can only have a type of Serialized when there actually *is* inventory with a serial number. In other words, if I see a type of Serialized, I should be able to discover what the serial numbers are. So when there's a deficit, maybe the InventoryItem should say Non-serialized, provided the type is set to Serialized when stock arrives. What do you think? Cheers Paul Foxworthy On 19 December 2016 at 17:54, Deepak Dixit <[hidden email]> wrote: > Hi James, > > System create new inventory item each time, it does not use single > InventoryItem for all backorder. So it create incorrect inventory item(s) > data for serialized inventory item. > I think we can refine serialized inventory item support under > https://issues.apache.org/jira/browse/OFBIZ-7762 > > As per current implementation serialized inventory logic implemented on > status, and non-serialized inventory logic implemented on > InventoryItemDetail. > > Ideally both should use IID and if item is serialized than qoh can't be > greater then one, if we go with this route than we can implement status > base check on both type of inventory item. > Like if inventory item is defective than we can set its ATP to zero for > both cases etc.... > > > > > > > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > > On Sat, Dec 17, 2016 at 8:42 PM, james yong <[hidden email]> wrote: > > > Hi Renuka, > > > > In this case, the non-serialized inventory acts as a placeholder to > ensure > > the final ATP is correct. > > This is correct behaviour, and not a bug. > > > > Regards, > > James > > > > > > Renuka Srishti-2 wrote > > > Hello All, > > > > > > In OFBiz, when we create an order for product with serialized inventory > > > with quantity more than ATP then a negative ATP Inventory Item record > is > > > created, which is of type Non-Serialized. > > > It should be of type serialized . > > > > > > If we resolve this issue, we need to check all scenarios related to > this > > > process. Please let me know your thoughts. If it looks good I will > open a > > > ticket for the same. > > > > > > Thanks > > > > > > -- > > > Regards, > > > Renuka Srishti > > > > > > > > > > > > -- > > View this message in context: http://ofbiz.135035.n4.nabble. > > com/Serialized-Inventory-issue-with-backorder-item- > tp4700367p4700409.html > > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > > > -- Coherent Software Australia Pty Ltd PO Box 2773 Cheltenham Vic 3192 Australia Phone: +61 3 9585 6788 Web: http://www.coherentsoftware.com.au/ Email: [hidden email]
--
Coherent Software Australia Pty Ltd http://www.coherentsoftware.com.au/ Bonsai ERP, the all-inclusive ERP system http://www.bonsaierp.com.au/ |
Re: Serialized Inventory issue with backorder item
|
|
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 |
Re: Serialized Inventory issue with backorder item
|
|
+1 on binding status to InventoryItemDetail.
Regards Scott On 22 December 2016 at 21:50, Jacopo Cappellato < [hidden email]> 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 > |
Re: Serialized Inventory issue with backorder item
|
|
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 <[hidden email]> wrote: > +1 on binding status to InventoryItemDetail. > > Regards > Scott > > On 22 December 2016 at 21:50, Jacopo Cappellato < > [hidden email]> 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 > > > |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |