[
https://issues.apache.org/jira/browse/OFBIZ-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295577#comment-15295577 ]
Pierre Smits commented on OFBIZ-7079:
-------------------------------------
I haven't thought of that kind of scenario. But then again, would one do that for product that weren't worth the effort to set the setting on creation? These kind of goods often have a low value per unit, and business often opt for reimbursement (and have the customer dealing with scrapping) and not having the goods returned. If goods are that valuable that the company would consider having them returned for maintenance and/or decompositioning (as an example),then the company would consider serialisation up front.
Just providing food for thought ;-)
> Extend Product entity and add serialized field
> ----------------------------------------------
>
> Key: OFBIZ-7079
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7079> Project: OFBiz
> Issue Type: Improvement
> Reporter: Deepak Dixit
> Assignee: Deepak Dixit
> Attachments: OFBIZ-7079.patch
>
>
> Extend Product entity and add serialized field to recognize product behavior.
> Will use product.serialized at the time of receiving to identified inventory item behavior.
> This will be setup time configuration, At the time of Product creation will set this flag.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
