[
https://issues.apache.org/jira/browse/OFBIZ-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215733#comment-15215733
]
Swapnil Shah edited comment on OFBIZ-6964 at 3/29/16 9:26 AM:
--------------------------------------------------------------
It looks like ProductStoreFacility could be used to maintain one to many
association between a Store and multiple facilities. Setting ReqMEI at
ProductStoreFacility would essentially signify that business would be able to
honor different replenishment policies for a single store with respect to each
of the associated facilities (technically we could have many to many
association between store and facility).
I am not too sure but perhaps we can try to understand more about it from a
generic business scenario prespective i.e., If we allow system to honor many to
many association between Store & Facility then should replenishment requirement
be triggered based on item's inventory level at Store itself or based on the
inventory level at each of the associated facilities?
For instance, Let's consider following simple case and here what should be
criteria to suggest requirement per store,
||Item||Store||Facility||Safety Stock (SS)||ATP||QOH||ReqMEI||
|A|S1|F1|20|18|25|ATP falls below SS|
|A|S2|F2|35|30|35|ATP falls below SS|
|A|S2|F3|35|40|45|QOH falls below SS|
|A|S3|F1|20|18|25|QOH falls below SS|
How such conflicts as presented in above example should be handled:
# As item A is sold via two stores S1 & S3 served by single warehouse facility
F1 for replenishment but both have different setting for ReqMEI. Should the
requirement be triggered for item A based on ReqMEI setting for S1-F1 combo
ahead of S3-F3.
# Another possible case where Item A sold via store S2 can be served via two
different warehouses F2 & F3. Here should system trigger the requirement based
on ReqMEI set for S2-F2 combo even if there is sufficient stock available in F3
to serve S2 for item A.
It's definitely doable theoretically but would require us to handle all such
further complexities at code level for MRP engine (or any other customized
transfer mechanism).
was (Author: swash78):
It looks like ProductStoreFacility could be used to maintain one to many
association between a Store and multiple facilities. Setting ReqMEI at
ProductStoreFacility would essentially signify that business would be able to
honor different replenishment policies for a single store with respect to each
of the associated facilities (technically we could have many to many
association between store and facility).
I am not too sure but perhaps we can try to understand more about it from a
generic business scenario prespective i.e., If we allow system to honor many to
many association between Store & Facility then should replenishment requirement
be triggered based on item's inventory level at Store itself or based on the
inventory level at each of the associated facilities? And what if the facility
serves multiple stores.
For instance, Let's consider following simple case and here what should be
criteria to suggest requirement per store,
||Item||Store||Facility||Safety Stock (SS)||ATP||QOH||ReqMEI||
|A|S1|F1|20|18|25|ATP falls below SS|
|A|S2|F2|35|30|35|ATP falls below SS|
|A|S2|F3|35|40|45|QOH falls below SS|
|A|S3|F1|20|18|25|QOH falls below SS|
How such conflicts as presented in above example should be handled:
# As item A is sold via two stores S1 & S3 served by single warehouse facility
F1 for replenishment but both have different setting for ReqMEI. Should the
requirement be triggered for item A based on ReqMEI setting for S1-F1 combo
ahead of S3-F3.
# Another possible case where Item A sold via store S2 can be served via two
different warehouses F2 & F3. Here should system trigger the requirement based
on ReqMEI set for S2-F2 combo even if there is sufficient stock available in F3
to serve S2 for item A.
It's definitely doable theoretically but would require us to handle all such
further complexities at code level for MRP engine (or any other customized
transfer mechanism).
> 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
> Labels: features
> Fix For: Upcoming Branch
>
>
> Consider a use case wherein there is a website and a physical retail store.
> Each having its own store and facility (for example, retail facility and
> webstore facility). Both the stores share the same catalog/products.
> *Store A (webstore) -> associated with facility 1 (webstore facility)*
> *Store B (retailstore) -> associated with facility 2 (retailstore facility)*
> However, both have different inventory management rules for the same product.
> Store A has a Requirement Method Enum ID (RMEI) of its own for the product
> and Store B also needs a mechanism to fulfil its own requirement.
> The inventory quantities can continue to be independently managed via the
> facilities tab for a product.
> Where the difficulty crops up is the management of Requirements. A product
> can have only one RMEI.
> The webstore warehouse is the main facility at which replenishment from
> suppliers and order fulfilment and shipping happens. The retail warehouse is
> just 'stocked' via indents/replenishment requests from the webstore warehouse
> and does not issue direct purchase orders to suppliers.
> The desired behaviour is that whenever item quantity is below ATP for the
> retail facility, then a request to re-stock is sent to the webstore facility.
> In turn if the webstore facility has ample quantity in stock(ATP) then it
> should approve and initiate a transfer else it should generate a requirement
> based on its RMEI setting.
> There doesn't seem to be an out of the box solution for this in OFBiz. This
> could work if either we build in support for store specific RMEI or there is
> another solution that I have encountered in Opentaps (a system built atop
> OFBiz) - Introduce a facility specific *Replenishment Method Enum ID (RPMEI)*
> with values such as -
> {code:xml}
> <!-- Enumeration for ProductFacility replenishMethodEnumId -->
> <EnumerationType enumTypeId="PFAC_RESPL_METHOD" hasTable="N"
> description="Product Facility Resplenish Methods"/>
> <Enumeration enumId="PF_RM_NEVER" description="Never transfer"
> enumTypeId="PFAC_RESPL_METHOD"/>
> <Enumeration enumId="PF_RM_BACKUP" description="Transfer from backup
> warehouse if available" enumTypeId="PFAC_RESPL_METHOD"/>
> <Enumeration enumId="PF_RM_SPECIF" description="Transfer from specified
> warehouse if available" enumTypeId="PFAC_RESPL_METHOD"/>
> <Enumeration enumId="PF_RM_BACKUP_ALW" description="Always transfer from
> backup warehouse" enumTypeId="PFAC_RESPL_METHOD"/>
> <Enumeration enumId="PF_RM_SPECIF_ALW" description="Always transfer from
> specified warehouse" enumTypeId="PFAC_RESPL_METHOD"/>
> {code}
> Once a product is configured with a facility specific RPMEI, an MRP run
> should create the appropriate Inventory Transfer request and then the flow
> can continue from there.
> This seems to be a rather important feature without which many businesses
> operating brick and mortar stores as well as an ecommerce web-front can't
> easily use OFBiz.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
