Forecast Management
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
Contents
- 1 Status
- 2 Contributors
- 3 Overview
- 4 Purpose
- 5 References
- 6 Design Considerations
- 7 Glossary
- 8 Functional Requirements
- 9 Functional team
- 10 Acceptance criteria
- 11 QA and test cases
- 12 Development infrastructure
- 13 Technical Requirements
- 14 Technical team
- 15 Data Requirements
- 16 Non-Functional Requirements
- 17 Open Discussion Items
- 18 Closed Discussion Items
Status
In production use
Contributors
Overview
This functionality allows an estimate of future sales of physical units and / or monetary of the products or services over a period of time, using quantitative and statistical methods based on historical data and market statistics.
The projected quantities and sales amounts are used for decision making, pricing, cash flow, estimated future demand, calculating master production schedule, supply plan and future capacity requirements.
Purpose
Forecast Sales Management User Guide
References
Business Dictionary Definition
Design Considerations
Assumptions
Dependencies
- The supported methods for calculating the forecast are based on the library open forecast
Constraints
- Is requires having a historic sales by product at least a year to be imported.
Glossary
Functional Requirements
Functional team
- Volunteers for analyzing:
- Mario Calderon 11:00, 16 June 2013 (UTC) - Functional Review
Result of review by Mario Calderon, June 16th, 2013
- Analyzing document ( https://docs.google.com/a/e-evolution.com/document/d/1T1dh2JyncjCMqwlUqnIHEla9tywwHLEqBa2mw1gttEc/pub )
- Goal of module: to create forecasts that will be considered during execution of MRP. The forecasts can be generated based on different rules and the results can be simulated before being brought into the forecast table.
- Definition of forecast calendar and forecast periods
- Automatically, weekwise
- Generation of sales history, based on different parameters
- Possibility of importing sales history, created on csv files
- Import sales history: works (from file into table C_SalesHistory
- Definition of forecast rules in Application Dictionary
- Double Exponential Smoothing
- Simple Exponential Smoothing
- Triple Exponential Smoothing
- Polynomial Regression
- Regression
- Naive Forecasting
- Multiple Linear Regression
- Best Forecast Model
- Moving Average
- Forecast definition
- Lines for different concepts: products, product categories, business partners
- Factors definable (alpha, beta, gamma)
- Sequence definable
- Forecast calculation
- Forecast run is calculated based on parameters and sales history
- Forecast calculation is possible to run repeatedly
- Parameters for calculation
- Forecast definition
- Forecast rule
- Calendar
- Source and target warehouse
- Base and target period
- Forecast run result
- Is a Smart Browser
- Two filter fields with same name (Period definition): is not clearly explained what they are for; this makes the filtering difficult.
- Zoom doesn't work
- Export works
- Process Calculate forecast
- not to confound with Forecast calculation
- This calculates the real forecast, based on Forecast run
- Different parameters selectable (action, load type)
- It is possible to do simulations for different scenarios and do the forecast for the most suitable/acceptable
- If the company has an own Forecast application, the forecast can be imported directly from a csv file
- Conclusion: accepted
User roles & profiles
- Sales Manager
- Product Manager
- Marketing Manager
Business process definition
User stories
Functional requirements based on business processes
User Interface Mockups
Acceptance criteria
QA and test cases
Development infrastructure
- The feature has been integrated into Adempiere Repository
- branch: feature/ADEMPIERE-98-Forecast-Management
- JIRA-URL: https://adempiere.atlassian.net/browse/ADEMPIERE-98
Technical Requirements
Technical team
- Volunteers for analyzing: Kthiemann 14:41, 24 June 2013 (UTC)
- Result of analysis: