While working with Hyperion Planning applications, be it
creating applications, outlines, dimensions, members, developing calculation
scripts or formulas, or performing administrative works in Planning on a day to
day basis, it is a good idea to know about some restrictions that Planning has.
Application/database naming convention
Unicode-mode
application/database – no more than 30 characters
Non-unicode
mode application/database – no more than 8 bytes
No
spaces
No special
characters such as, asterisks, backslashes, brackets, colons, commas, equal
signs, greater than or less than signs, periods, plus signs, question marks,
quotation marks, semicolons, slashes, tabs, or vertical bars.
No
extended characters except for underscores for Planning application names in
relational database environments
No
DEFAULT, LOG, METADATA, or TEMP as application names in ASO databases.
Dimension, Members, Aliases, and Data Forms
Unicode-mode
dimensions, members, or aliases – no more than 80 characters
Non-unicode
mode dimensions, members, or aliases – no more than 80 bytes
Distinguish
between upper and lower case only if case sensitivity is enabled.
No HTML
tags in members names, dimension names, aliases and descriptions
No
quotation marks, brackets, backslashes, or tabs. Though permitted, brackets are
not recommended in BSO outlines. Cause error when converting to ASO outlines.
Do not use the following characters to begin
dimension/member names: at signs, backslashes, brackets, commas, dashes,
hyphens, equal or less than signs, parenthesis, periods, plus signs, quotation
marks, underscores or vertical bars
Do not place spaces at the beginning or end of names as
Essbase ignores such spaces
Do not use forward slashes in member names.
No spaces in prefixes for time periods in custom calendars
For member/dimension names, do not use: Calculation script
commands, operators, and keywords, report writer commands, Function names and
function arguments, Names of other dimension members, unless shared, and
generation names, level names, and aliases in the database.
In case Dynamic Time Series is enabled, do not use History,
Year, Season, Period, Quarter, Month, Week, or Day.
Planning User Names
Can be
up to 80 characters long
