[
https://issues.apache.org/jira/browse/OFBIZ-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15338146#comment-15338146 ]
Divesh Dutta commented on OFBIZ-7481:
-------------------------------------
I agree with [~pfm.smits] . Also I remember discussing similar scenario with [~mridul.pathak] in person that if this situation occurs that if you receive a product in warehouse and there is no pre existing record of ProductFacility then we should probably return error instead of creating ProductFacility record silently. This is because receiver might mistakenly receive a product in wrong warehouse and it might be the case that business don't want to manage inventory of that product in warehouse. So they have not set up the ProductFacility record for that product. And if this is the case then system will silently create ProductFacility in your proposal , which is wrong .
So returning an error might be the right approach here, and then once user creates ProductFacility record manually or get it done by his superior . And then proceed receiving the product in warehouse.
> ProductFacility record must exist before creating inventoryItem for a facility
> ------------------------------------------------------------------------------
>
> Key: OFBIZ-7481
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7481> Project: OFBiz
> Issue Type: Bug
> Components: product
> Affects Versions: 14.12.01, Upcoming Branch, 15.12.01, 13.07.04
> Reporter: Suraj Khurana
> Assignee: Suraj Khurana
>
> ProductFacility entity is used to decide that a particular product is maintained in which facility. So, in case of receiving a product in a facility or in case creating InventoryItem for a facility, the ProductFacility record must exist. But in these cases, currently in OFBiz inventoryItem gets created even if ProductFacility record doesn't exist.
> Proposed solution:
> 1) In receiveInventoryProduct service check and create ProductFacility record if not exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
