Dev - make qoh of serialized inventory 1.0 or 0.0
Locked
 
|
Hi everybody.
We're thinking about making the QOH quantity of serialized inventory either 1.0 or 0.0, depending on the status. That wold make certain valuation and counting operations much easier. Would that cause problems for anybody? Si _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Re: Dev - make qoh of serialized inventory 1.0 or 0.0
|
|
In general I'd say it's better for code to know the difference between serialized and non-serialized inventory. For customization as well as other reasons it makes it easier to work with. Is there a specific piece of existing code or a new process you are working on where considering the inventory item type and the status won't work? -David Si Chen wrote: > Hi everybody. > > We're thinking about making the QOH quantity of serialized inventory > either 1.0 or 0.0, depending on the status. That wold make certain > valuation and counting operations much easier. Would that cause > problems for anybody? > > Si > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
|
|
Under the current system, if there is serialized inventory, then we'd have to do another SELCT sum(unitCost) for InventoryItem where inventoryTypeId = "SERIALIZED_INV_ITEM" where status in (....). We may also in some cases have to add the results of the serialized and non-serialized queries to get one table of inventory and their values. If serialized inventory just had a qoh quantity = 1.0 or 0.0, then one query could handle everything. It would cut down on the code and complexity for this type of reporting quite significantly. Si David E. Jones wrote: In general I'd say it's better for code to know the difference between serialized and non-serialized inventory. For customization as well as other reasons it makes it easier to work with. Is there a specific piece of existing code or a new process you are working on where considering the inventory item type and the status won't work? -David Si Chen wrote:Hi everybody. We're thinking about making the QOH quantity of serialized inventory either 1.0 or 0.0, depending on the status. That wold make certain valuation and counting operations much easier. Would that cause problems for anybody? Si _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
Re: Dev - make qoh of serialized inventory 1.0 or 0.0
|
|
You're right it would be easier in that code. I guess the question is if it is "safe" or not... Perhaps it would be best to maintain these values through an EECA (entity ECA) like the current stuff for availableToPromiseTotal and quantityOnHandTotal values for non-serialized InventoryItems.
-David Si Chen wrote: > If we're doing an inventory valuation, the value of the inventory in > stock = quantity * unitCost for non-serialized inventory. > > Under the current system, if there is serialized inventory, then we'd > have to do another SELCT sum(unitCost) for InventoryItem where > inventoryTypeId = "SERIALIZED_INV_ITEM" where status in (....). We may > also in some cases have to add the results of the serialized and > non-serialized queries to get one table of inventory and their values. > > If serialized inventory just had a qoh quantity = 1.0 or 0.0, then one > query could handle everything. It would cut down on the code and > complexity for this type of reporting quite significantly. > > Si > > David E. Jones wrote: >> In general I'd say it's better for code to know the difference between serialized and non-serialized inventory. For customization as well as other reasons it makes it easier to work with. >> >> Is there a specific piece of existing code or a new process you are working on where considering the inventory item type and the status won't work? >> >> -David >> >> >> Si Chen wrote: >> >>> Hi everybody. >>> >>> We're thinking about making the QOH quantity of serialized inventory >>> either 1.0 or 0.0, depending on the status. That wold make certain >>> valuation and counting operations much easier. Would that cause >>> problems for anybody? >>> >>> Si >>> >>> _______________________________________________ >>> Dev mailing list >>> [hidden email] >>> http://lists.ofbiz.org/mailman/listinfo/dev >>> >> >> _______________________________________________ >> Dev mailing list >> [hidden email] >> http://lists.ofbiz.org/mailman/listinfo/dev >> >> > > ------------------------------------------------------------------------ > > > _______________________________________________ > Dev mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
|
|
David,
OK. That sounds like a good idea. Si David E. Jones wrote: You're right it would be easier in that code. I guess the question is if it is "safe" or not... Perhaps it would be best to maintain these values through an EECA (entity ECA) like the current stuff for availableToPromiseTotal and quantityOnHandTotal values for non-serialized InventoryItems. -David Si Chen wrote: _______________________________________________ Dev mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/dev |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |