Apply Business Logic with Calculations

After planning your application and cube, consider how Essbase needs to derive, aggregate, and transform the business data in your model.

Some results can be produced simply by rolling detailed values up through a hierarchy. Other results require formulas, allocations, forecasts, or a series of calculations that implement a business process.

Understanding these requirements can help you finalize your choice between an aggregate storage (ASO) cube and a hybrid block storage (Hybrid BSO) cube.

Note:

The BSO cube category includes hybrid BSO and "classic" BSO. However, because only ASO and hybrid BSO are relevant for Essbase on Autonomous AI Lakehouse, all further references to BSO in this documentation should be considered to mean hybrid BSO.

• Start with aggregation
  The simplest calculations in an Essbase cube often come directly from its hierarchies.
• Add calculations with Essbase member formulas
  Not every business value comes directly from the source data.
• Consider whether you need allocations
  Many business processes require an amount recorded at one level to be distributed across other parts of the business.
• Consider forecasting requirements
  Essbase can also use existing business data as the basis for calculated future values.
• Decide whether you need a calculation process
  Some Essbase applications require several calc operations to work together as a repeatable business process.
• Finalize the cube type
  Using what you've learned about calculations, revisit the initial choice (ASO or BSO) that you made when you started planning your Essbase application.