Hello Deepak, IMO, It should be configurable that either *ProductFacility* is required or not. But we need to think on the respective points to proceed further
If ProductFacility is required then 1. The user needs to create a ProductFacility record before receiving inventory Or 2. Silently system can create a ProductFacility record for the specific one If ProductFacility is not required then need to check the following workflows 1. How to show the inventory of the product which is not associate with the respective facility 2. How inventory reservation will work? as of now, the reservation does not handle this type of inventory. 3. How inventory valuation entertain this inventory? As of now, the inventory valuation does not handle this type of inventory. 4. Do we need any other workflow to manage this type of inventory? Thanks & Regards Vaibhav Jain Sr. Enterprise Software Engineer HotWax Systems m: 782-834-1900 e: [email protected] On Wed, Sep 19, 2018 at 11:28 PM Scott Gray <[email protected]> wrote: > Sounds like there are 3 options available: > 1. Improve any view/report screens to not rely on ProductFacility but > instead report on what is actually in the warehouse via InventoryItem. > 2. Require ProductFacility but silently create it when it is absent > 3. Require ProductFacility and reject receipt of products when it is absent > > My first thought is that if ProductFacility were truly required then we > would have a foreign key constraint on InventoryItem to prevent them from > being created. So I'm guessing the original intent wasn't to require a > ProductFacility record. > > IMO we should first look to improving the view/report screens to not > require ProductFacility, if that is not possible or overly complicated then > we could look at requiring ProductFacility. If we wanted to require > ProductFacility in order to enforce business rules, then that should > probably be configurable. > > Regards > Scott > > On 19 September 2018 at 10:49, Deepak Nigam <[email protected]> > wrote: > > > Thanks, Suraj. > > > > @All, as per the suggestions provided in the Jira ticket, should we > > restrict the receiving of non-associated products and simply return an > > error message? WDYT? > > > > On Wed, Sep 19, 2018 at 2:45 PM Suraj Khurana < > > [email protected]> wrote: > > > > > Hello Deepak, > > > > > > Please have a look. > > > https://issues.apache.org/jira/browse/OFBIZ-7481 > > > > > > HTH. > > > > > > -- > > > Thanks and Regards, > > > Suraj Khurana > > > Omnichannel OMS Technical Expert > > > HotWax Systems > > > > > > > > > > > > On Wed, Sep 19, 2018 at 2:38 PM, deepak nigam < > > [email protected]> > > > wrote: > > > > > > > Hello All, > > > > > > > > We can directly receive inventory of a product into a facility by > using > > > the > > > > option 'Facility' -> 'Receive Inventory'. Here we can select a > product > > > for > > > > receiving which is not associated with the receiving facility (e.g. > > > product > > > > -> Purple Gizmo GZ-5005, facility -> WebS Store Warehouse). > > > > > > > > After a successful receive also, the product is not getting > associated > > > with > > > > the facility. Due to this, we can't find the newly received product > > under > > > > the 'Inventory' section of the facility. Should the product be > > associated > > > > with the facility after receiving? > > > > > > > > > > > > > > > > Thanks & Regards > > > > -- > > > > Deepak Nigam > > > > > > > > > >
