tes
“No” in ASO:
^
1. An aggregate storage outline cannot be converted to a block storage outline.
2. Do not use the file system to copy a block storage outline into an aggregate storage application.
3. ASO can have only “Stored” and “Dynamic” hierarchies.
4. Multiple hierarchies enabled dimension is automatically tagged as label only.
5. Essbase automatically tags the dimension as a stored hierarchy.
6. You cannot specify the accounts dimension as a stored hierarchy. (Default dynamic)
7. The first hierarchy in a multiple hierarchies enabled dimension must be a stored hierarchy.
8. Stored hierarchies cannot have formulas.
9. Stored hierarchy dimensions cannot have shared members.
10. If a member has the no-consolidation operator (~) on all its children, the member must be tagged as label only.
11. A stored hierarchy cannot contain a non shared instance and a shared instance of the same member. Non shared instances of a member must be in the same dimension as the shared member (same for block storage outlines).
12. A stored hierarchy can contain a shared instance of a dynamic hierarchy member only if the dynamic hierarchy member is a level 0 member without a formula.
13. A shared member automatically shares any attributes that are associated with its non shared member.
14. Dynamic hierarchies can contain any consolidation operator.
15. Dynamic hierarchies can have formulas.
16. If a member has the no-consolidation operator (~) on all its children, the member must be tagged as label only.
17. Do not increase the maximum size of the aggregate storage cache beyond what is needed.
18. Time balance reporting is not supported with Dynamic “Time” dimension. Time dimension must be stored hierarchy to support Time balance reporting without Skip zeros and shared members must be at level zero.
19. No write back capability (ASO – BSO transparent partition is a workaround).
20. Cannot load data to non-level zero members in an aggregate storage outline.
Please refer Essbase Adim Guide for more information on Aggregate Storage Kernal (ASO).
No comments:
Post a Comment