Restricted members and aliases in Oracle Planning Cloud
Recently, while implementing Oracle Planning Cloud for a new client, we experienced an issue where attribute dimensions were not being deployed successfully to the underlying Essbase cube – which was definitely not ideal! As we had never experienced this issue before, we opened an SR with Oracle, and (long story short) the issue was occurring because we had unknowingly used a restricted word as a member name and also had trailing spaces in a couple of aliases. Once we removed the restricted member names/aliases, the attribute dimensions were successfully deployed during the refresh. Unfortunately, these restricted members do not show as an error when refreshing the database, even if used in the outline, so hopefully this is something Oracle can add either as an error or as a warning on the Activity Report. In the meantime, it’s worth double checking the naming restrictions, especially if you seem to be experiencing some strange behaviour with Essbase. Some of the main restrictio...