If the BSO calculation is just aggregating the cube then it should be okay. If the calculation script is executing any type of logic, then you will have to deteremine if that functionality can be replicated using MDX member formulas.
If it can't, then the application might not be a good candidate for ASO. It depends on the functional requirements. Marketing Advertising Analytics Email.
Contact [email protected] Privacy Policy Status. Oracle Hyperion - Essbase pages. These two Essbase cube types have their own strengths, which help the organizations to choose their best design options. The block Storage Option has lesser number of dimensions than the aggregate option but shows the business model and can perform numerous and complex calculations on the smaller outlines.
It provides special functionalities for Accounts and Time dimensions like Dynamic time series, Time balance, Variance reporting. There are 3 types of partitions Replicated, Transparent, Linked. There is no restriction of the number of databases under one application but performance costs. Data in BSO applications is manipulated using calculation scripts and business rules, which provide the math that Essbase needs to perform. In short BSO applications are great for the manipulation and transformation of data, such as calculating healthcare costs for next year based on a rate, or transforming data based on a series of exchange rates.
ASO cubes are designed to provide rapid aggregation capabilities for much larger Essbase outlines, typically supporting many more and larger dimensions. Aggregate storage databases enable dramatic improvements in both database aggregation time and dimensional scalability.
The aggregate storage option is an alternative to the block storage option. ASO allows only one database to be created under one application.
Also unlike BSO it is mandatory to follow the naming conventions of Application names. For example, Application name should not be like metadata, temp,log etc.. ASO does not support dynamic time series and Time balance properties. When the dimension build process builds any new member then the data will be erased else the data will be alive.
Only one type of partition available Transparent. There is no concept of Sparse and Dense dimensions, no Boolean attribute tag. ASO allows only storing data, and does not allow sharing.
Data is only stored at the detailed level, and aggregated when users request information. In our old retrieval, an ASO cube would only store Retrieval 1, and then aggregate the data on the fly for Retrieval 2. This is particularly useful when we have a large data set that is updated frequently. For some projects, combining the calculation strengths of BSO with the aggregation strengths of ASO offers the best fit for your Essbase analytical needs. Its highly advanced calculation engine includes more than prebuilt and out of the box functions.
It helps in accelerating complex business models development. This comprehensive library enables Oracle Essbase to scale from simple aggregations to complex, cross dimensional allocations. You can categorize data blocks in the following ways:. These blocks are created by loading data to cells in a block. Input blocks can be created for 1 sparse, level 0 member combinations or 2 sparse, upper-level member combinations, when at least one of the sparse members is a parent-level member.
Input blocks can be level 0 or upper-level blocks. These blocks are created through calculations. For example, in Sample. These blocks are created for sparse member combinations when all of the sparse members are level 0 members. Level 0 blocks can be input or noninput blocks; for example, a level 0 noninput block is created during an allocation process, where data is loaded at a parent level and then allocated down to level 0.
These blocks are created for sparse member combinations when at least one of the sparse members is a parent-level member.
0コメント