One of the most important factors for any successful Essbase database design is to determine up-front what data elements and attributes are required.
Our business customer is the director of sales forecasting and production planning for the Esscar Motor Company. What if our customer would like to have the ability to create a monthly sales forecast for the vehicles manufactured by Esscar Motor Company and then sold in the various markets they compete in? The customer also needs to see the effects of the sales forecast on the planned production volumes and the required stock of vehicles. In addition, with regard to future monthly planning, the data needs to be robust enough to provide historical looks at the data and year over year comparisons. As you can see in the following screenshot, you can use Oracle Essbase for predictive analysis for future or forecast periods:
Let us see what we have learned about data requirements from our customer. What data elements...
