How to rename PlanType (database) name in Hyperion Planning

Say you have a Hyperion Planning application “Candy” with Plan Types “PlanType2,” “PlanType3,” and your main database “NYC.”

However, you need are told to rename “NYC” to “Handy” so that the App-DB name would be Candy-Handy.

This is how you can achieve this.

Before making any changes, however, make sure that you have stopped all the Services on the app server. Not doing so may lock tables.

After stopping the services, log on to Oracle SQL Developer (I have Oracle 11G and SQL Developer). You log on to what DB you use.

Find the HSP_OBJECT table for the Schema User used for the Application Candy. Mine is called Candy_adm. So, I choose the HSP_OBJECT table under user Candy_adm.

In the HSP_OBJECT table, under column OBJECT_NAME, find the old database name that you want to rename. In this case, since, I have three plan types (NYC for PlanType1, and PlanType2 and PlanType3), they fall under column OBJECT_ID – 100, 101, and 102.

Rename NYC to Handy as you want the new database to be Handy. Save

Now, open table HSP_PLAN_TYPE.

Rename NYC to Handy. Save.

If you already have the old database (NYC) created in Essbase, go to EAS console and rename the name of the database as well.

Start EPM services in the app server (the ones that you had stopped).

Open the planning application Candy. You should be able to see the Handy database name instead of NYC.

Refresh DATABASE so that you have it in Essbase as well.

Hyperion Planning Naming Restrictions

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