[
https://issues.apache.org/jira/browse/OFBIZ-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545170 ]
Jacopo Cappellato commented on OFBIZ-194:
-----------------------------------------
From an old discussion in the dev list:
"Proposed change to the SalesForecast entity"
* SalesForecast (leave as is now): used to set the period, the currency
and global amounts
* SalesForecastDetail (optional, can be used to specify detailled
forecasts, for units to be sold or amounts, by category or product):
### salesForecastId (PK)
### salesForecastDetailSeqId (PK)
### amount (in the currency set in SalesForecast)
### quantityUomId
### quantity
### productId
### productCategoryId
> Implement sales forecast analysis
> ---------------------------------
>
> Key: OFBIZ-194
> URL:
https://issues.apache.org/jira/browse/OFBIZ-194> Project: OFBiz
> Issue Type: New Feature
> Components: manufacturing
> Reporter: Jacopo Cappellato
> Priority: Minor
>
> At the beginning of the simulation process, the MRP algorithm collects information about real purchase orders, sales orders, production runs and stock levels.
> We should add to these the sales forecasts; this issue involves:
> * ui and services to manage (create/edit/delete) sales forcasts
> * mods to the MRP process
> Some of the implementation details (taken from a mail I've recently sent to the user list):
> let's say that your forecast is to sell 10000 t-shirt of type "A" in the next 2 months; the t-shirt "A" are virtual product that are available in two sizes, S and L.
> You would like to simulate (materials and resources needed) the manufacturing process to create 10000 t-shirt of type "A", regardless of their sizes.
> I'd recommend to implement something different:
> 1) introduce the concept of a "family of products"; this could be a special type of Product that is only used as a planning tool; in the example above, you could create a new product of type "family of products" to represent your type "A" t-shirts
> 2) create a bom for your family of products where each component is a variant product; for example: family "A" has two components, the variant product "t-shirt A size S" and "t-shirt A size L"; the bom coefficient is used here to forecast the number of sizes that will be sold (for example, 0.4 for S and 0.6 for L)
> 3) then you'll create one production run for the family "A" of 10000 units with start date in the future; the production run will never be executed (i.e. its components, the variant products, will not be taken from warehouse)
> 4) by running the MRP you'll get a simulation of the materials needed (to manufacture 4000 t-shirt of size S and 6000 t-shirt of size L) and it will generate the *requirements* for them (that once approved will become new production runs for real variant products).
> Comment by Jacopo Cappellato [01/Sep/06 02:59 AM]
> [ Permlink ]
> A follow-up to the above comment to specify some of the design details:
> a) a new product type for the family of products
> b) a new status for the requirements generated from MRP to specify that they are a "simulation"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Locked
