[jira] [Updated] (OFBIZ-5027) Product Facility record should be created in case of its no record when calling setLastInventoryCount service as EECA.

["Jacopo Cappellato (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OFBIZ-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacopo Cappellato updated OFBIZ-5027:
-------------------------------------

    Fix Version/s:     (was: Release Branch 12.04)
                       (was: Release Branch 11.04)
                       (was: Trunk)

> Product Facility record should be created in case of its no record when calling setLastInventoryCount service as EECA.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-5027
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5027
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>            Reporter: Amardeep Singh Jhajj
>            Priority: Minor
>             Fix For: Release Branch 10.04
>
>         Attachments: OFBIZ-5027-Release-10.04.patch, OFBIZ-5027-Release-11.04.patch, OFBIZ-5027-trunk.patch
>
>
> Currently, ProductFacility record is updated by setLastInventoryCount service when create-store-remove operation performed on InventoryItemDetail entity (by EECA). 
> This service is called to update lastInventoryCount field in ProductFacility and this field  helps us for checking product in-stock/out-of-stock.
> This service helps only when ProductFacility will already present. Suppose, if catalog manager forgot to setup facility or deleted it at
> https://demo-trunk.ofbiz.apache.org:8443/catalog/control/EditProductFacilities?productId=WG-9943-B3
> and just setup Inventory during product setup then setLastInventoryCount service would not be helpful.
> So in my opinion, here ProductFacility should be first created in case of its no record when updating lastInventoryCount in ProductFacility.
> I am attaching patch for the same here.



--
This message was sent by Atlassian JIRA
(v6.2#6252)