Hybrid Planning / Essbase Gotchas
Having the best of both worlds, ASO and BSO, doesn’t come without some gotchas. Before you jump in with both feet, beware of some things that are not supported in hybrid. As of Friday, May 22, 2020, @ISMBR in planning does NOT work. I don’t know if this is a bug, but it is not documented as a function that doesn’t exist. What is documented is the following. There isn’t a ton in this post, but I thought it would be beneficial to share this as a warning, as well as an easy way to find the list. If you find more things that don’t work, please share with the community.
- @ACCUM
- @ALLOCATE
- @ANCEST
- @ANCESTVAL
- @AVGRANGE
- @COMPOUND
- @COMPOUNDGROWTH
- @CORRELATION
- @CREATEBLOCK
- @CURRMBR
- @CURRMBRRANGE
- @DECLINE
- @DISCOUNT
- @GROWTH
- @INTEREST
- @IRR
- @IRREX
- @MDALLOCATE
- @MDANCESTVAL
- @MDPARENTVAL
- @MDSHIFT
- @MEMBER
- @MOVAVG
- @MOVMAX
- @MOVMED
- @MOVMIN
- @MOVSUM
- @MOVSUMX
- @NPV
- @PARENT
- @PARENTVAL
- @PTD
- @SANCESTVAL
- @SHIFT
- @SLN
- @SPLINE
- @STDEV
- @STDEVP
- @STDEVRANGE
- @SYD
- @TREND
- @XRANGE
- @XREF
- @XWRITE
Leave a Reply
Want to join the discussion?Feel free to contribute!