[jira] [Assigned] (OFBIZ-6964) Support for replenishment of a secondary warehouse from a main warehouse
[ https://issues.apache.org/jira/browse/OFBIZ-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Patidar reassigned OFBIZ-6964: --- Assignee: Arun Patidar (was: Pawan Verma) > Support for replenishment of a secondary warehouse from a main warehouse > > > Key: OFBIZ-6964 > URL: https://issues.apache.org/jira/browse/OFBIZ-6964 > Project: OFBiz > Issue Type: New Feature > Components: manufacturing, product >Reporter: Shrenik Bhura >Assignee: Arun Patidar >Priority: Major > Labels: features > Fix For: 17.12.01 > > Attachments: screenshot-1.png > > > At the onset let me define a few terms clearly as I mean it in the story > description below : > Requirement - A request generated for a particular product for a specific > quantity that needs to be purchased from a supplier for satisfying certain > inventory needs of a particular facility. > Replenishment - A request generated for a particular product for a specific > quantity that needs to be transferred from a "backup facility" for satisfying > certain inventory needs of a particular facility. > Fulfilment - The process of reserving, picking, packing and shipping the > ordered quantity of product(s) as per a sales order. > Terms 'warehouse' and 'facility' have been used interchangeably. > *The Use Case:* > Consider a scenario wherein there is a website and a physical retail store of > the same Company. > Each having its own facility i.e. 1:1 mapping. > {{Store A (webstore) -> associated with facility 1 (webstore facility)}} > {{Store B (retailstore) -> associated with facility 2 (retailstore facility)}} > However, both the stores share the same catalog/products. But both have > independent inventory requirement and replenishment rules for the same > product. > There is a Requirement Method Enum ID (RMEI) of each product which is > applicable irrespective of the store and supersedes the RMEI defined, if any, > on a store. > A product's inventory thresholds (Minimum Stock, Reorder Quantity) are > independently managed via the facilities tab for the product. A product has > its ATP and QOH levels on a per facility basis. _Do note that all these > inventory numbers are at a facility level and has no bearing at a store > level._ > Where the difficulty crops up with the current implementation is the way > requirements are generated. A product can have only one RMEI. When an order > is placed from any store, then based on the combination of a product's RMEI > and the store mapped facility's inventory threshold, requirements are > generated. This is without consideration of the inventory status (surplus or > otherwise) at another facility of the same Company. If a store has multiple > facilities associated with it then the one defined in the ProductStore entity > -> inventoryFacilityId field would be considered for picking the inventory > threshold values and thus for requirement generation. > Most typical real-world facility arrangements: > 1. Usually an organisation would have a main facility/warehouse where > all the purchases are received and sub-facilities which are replenished from > the main facility after QA, internal processes, etc. OR > 2. For each product there would be a primary facility where the product > is received from the supplier (to derive benefits of demographic convenience > and consumption patterns) and then replenished to other facilities on a > demand based pull basis. > To drive efficiencies across an organisation they need methods to consider > open fulfilment needs, in process purchase orders and inventory levels across > multiple facilities and thereafter propose inventory transfers across them to > facilitate better stocking and thus order fulfilment. > Coming back to our use case, the webstore warehouse is the main facility at > which incoming shipments from suppliers are received for the entire Company > but sales order fulfilment happens only for the webstore. The retail > warehouse is primarily 're-stocked' via replenishment requests raised upon > the webstore warehouse and thus need not issue direct purchase orders to > suppliers. However, if the need be, requirement generated based on the > product's RMEI and the retail facility's inventory thresholds can also be > approved, converted into Purchase order and issued. > *Proposed Solution:* > There doesn't seem to be an out of the box solution for this in OFBiz. This > could work if either we think of - > Approach A: Setting RMEI at a ProductFacility level as well which shall > supersede the Product level RMEI setting OR > Approach B: Build in support for a solution that I have encountered in > Opentaps (a system built atop OFBiz) i.e. implement support
[jira] [Assigned] (OFBIZ-6964) Support for replenishment of a secondary warehouse from a main warehouse
[ https://issues.apache.org/jira/browse/OFBIZ-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pawan Verma reassigned OFBIZ-6964: -- Assignee: Pawan Verma (was: Swapnil Shah) > Support for replenishment of a secondary warehouse from a main warehouse > > > Key: OFBIZ-6964 > URL: https://issues.apache.org/jira/browse/OFBIZ-6964 > Project: OFBiz > Issue Type: New Feature > Components: manufacturing, product >Reporter: Shrenik Bhura >Assignee: Pawan Verma >Priority: Major > Labels: features > Fix For: 17.12.01 > > Attachments: screenshot-1.png > > > At the onset let me define a few terms clearly as I mean it in the story > description below : > Requirement - A request generated for a particular product for a specific > quantity that needs to be purchased from a supplier for satisfying certain > inventory needs of a particular facility. > Replenishment - A request generated for a particular product for a specific > quantity that needs to be transferred from a "backup facility" for satisfying > certain inventory needs of a particular facility. > Fulfilment - The process of reserving, picking, packing and shipping the > ordered quantity of product(s) as per a sales order. > Terms 'warehouse' and 'facility' have been used interchangeably. > *The Use Case:* > Consider a scenario wherein there is a website and a physical retail store of > the same Company. > Each having its own facility i.e. 1:1 mapping. > {{Store A (webstore) -> associated with facility 1 (webstore facility)}} > {{Store B (retailstore) -> associated with facility 2 (retailstore facility)}} > However, both the stores share the same catalog/products. But both have > independent inventory requirement and replenishment rules for the same > product. > There is a Requirement Method Enum ID (RMEI) of each product which is > applicable irrespective of the store and supersedes the RMEI defined, if any, > on a store. > A product's inventory thresholds (Minimum Stock, Reorder Quantity) are > independently managed via the facilities tab for the product. A product has > its ATP and QOH levels on a per facility basis. _Do note that all these > inventory numbers are at a facility level and has no bearing at a store > level._ > Where the difficulty crops up with the current implementation is the way > requirements are generated. A product can have only one RMEI. When an order > is placed from any store, then based on the combination of a product's RMEI > and the store mapped facility's inventory threshold, requirements are > generated. This is without consideration of the inventory status (surplus or > otherwise) at another facility of the same Company. If a store has multiple > facilities associated with it then the one defined in the ProductStore entity > -> inventoryFacilityId field would be considered for picking the inventory > threshold values and thus for requirement generation. > Most typical real-world facility arrangements: > 1. Usually an organisation would have a main facility/warehouse where > all the purchases are received and sub-facilities which are replenished from > the main facility after QA, internal processes, etc. OR > 2. For each product there would be a primary facility where the product > is received from the supplier (to derive benefits of demographic convenience > and consumption patterns) and then replenished to other facilities on a > demand based pull basis. > To drive efficiencies across an organisation they need methods to consider > open fulfilment needs, in process purchase orders and inventory levels across > multiple facilities and thereafter propose inventory transfers across them to > facilitate better stocking and thus order fulfilment. > Coming back to our use case, the webstore warehouse is the main facility at > which incoming shipments from suppliers are received for the entire Company > but sales order fulfilment happens only for the webstore. The retail > warehouse is primarily 're-stocked' via replenishment requests raised upon > the webstore warehouse and thus need not issue direct purchase orders to > suppliers. However, if the need be, requirement generated based on the > product's RMEI and the retail facility's inventory thresholds can also be > approved, converted into Purchase order and issued. > *Proposed Solution:* > There doesn't seem to be an out of the box solution for this in OFBiz. This > could work if either we think of - > Approach A: Setting RMEI at a ProductFacility level as well which shall > supersede the Product level RMEI setting OR > Approach B: Build in support for a solution that I have encountered in > Opentaps (a system built atop OFBiz) i.e. implement support for
[jira] [Assigned] (OFBIZ-6964) Support for replenishment of a secondary warehouse from a main warehouse
[ https://issues.apache.org/jira/browse/OFBIZ-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Shah reassigned OFBIZ-6964: --- Assignee: Swapnil Shah (was: Divesh Dutta) > Support for replenishment of a secondary warehouse from a main warehouse > > > Key: OFBIZ-6964 > URL: https://issues.apache.org/jira/browse/OFBIZ-6964 > Project: OFBiz > Issue Type: New Feature > Components: manufacturing, product >Reporter: Shrenik Bhura >Assignee: Swapnil Shah > Labels: features > Fix For: Upcoming Release > > Attachments: screenshot-1.png > > > At the onset let me define a few terms clearly as I mean it in the story > description below : > Requirement - A request generated for a particular product for a specific > quantity that needs to be purchased from a supplier for satisfying certain > inventory needs of a particular facility. > Replenishment - A request generated for a particular product for a specific > quantity that needs to be transferred from a "backup facility" for satisfying > certain inventory needs of a particular facility. > Fulfilment - The process of reserving, picking, packing and shipping the > ordered quantity of product(s) as per a sales order. > Terms 'warehouse' and 'facility' have been used interchangeably. > *The Use Case:* > Consider a scenario wherein there is a website and a physical retail store of > the same Company. > Each having its own facility i.e. 1:1 mapping. > {{Store A (webstore) -> associated with facility 1 (webstore facility)}} > {{Store B (retailstore) -> associated with facility 2 (retailstore facility)}} > However, both the stores share the same catalog/products. But both have > independent inventory requirement and replenishment rules for the same > product. > There is a Requirement Method Enum ID (RMEI) of each product which is > applicable irrespective of the store and supersedes the RMEI defined, if any, > on a store. > A product's inventory thresholds (Minimum Stock, Reorder Quantity) are > independently managed via the facilities tab for the product. A product has > its ATP and QOH levels on a per facility basis. _Do note that all these > inventory numbers are at a facility level and has no bearing at a store > level._ > Where the difficulty crops up with the current implementation is the way > requirements are generated. A product can have only one RMEI. When an order > is placed from any store, then based on the combination of a product's RMEI > and the store mapped facility's inventory threshold, requirements are > generated. This is without consideration of the inventory status (surplus or > otherwise) at another facility of the same Company. If a store has multiple > facilities associated with it then the one defined in the ProductStore entity > -> inventoryFacilityId field would be considered for picking the inventory > threshold values and thus for requirement generation. > Most typical real-world facility arrangements: > 1. Usually an organisation would have a main facility/warehouse where > all the purchases are received and sub-facilities which are replenished from > the main facility after QA, internal processes, etc. OR > 2. For each product there would be a primary facility where the product > is received from the supplier (to derive benefits of demographic convenience > and consumption patterns) and then replenished to other facilities on a > demand based pull basis. > To drive efficiencies across an organisation they need methods to consider > open fulfilment needs, in process purchase orders and inventory levels across > multiple facilities and thereafter propose inventory transfers across them to > facilitate better stocking and thus order fulfilment. > Coming back to our use case, the webstore warehouse is the main facility at > which incoming shipments from suppliers are received for the entire Company > but sales order fulfilment happens only for the webstore. The retail > warehouse is primarily 're-stocked' via replenishment requests raised upon > the webstore warehouse and thus need not issue direct purchase orders to > suppliers. However, if the need be, requirement generated based on the > product's RMEI and the retail facility's inventory thresholds can also be > approved, converted into Purchase order and issued. > *Proposed Solution:* > There doesn't seem to be an out of the box solution for this in OFBiz. This > could work if either we think of - > Approach A: Setting RMEI at a ProductFacility level as well which shall > supersede the Product level RMEI setting OR > Approach B: Build in support for a solution that I have encountered in > Opentaps (a system built atop OFBiz) i.e. implement support for a new setting >