Refresh of ASO Plan Type failing while setting up an Alternate Hierarchy in PBCS

I was working on PBCS application where the application had a BSO cube and ASO cube. After some initial setup and dimension creation we were creating an alternate hierarchy in Period dimension. Somehow Cube Refresh was failing for ASO plan type. It seemed that the issue was with the shared member but that was not the problem.

The error message I got for my ASOPlan (cube name) was as follows:

Cube refresh failed with Essbase Cube: ASOPlan, Error code: 1060053, Message:

The message was not clear but the issue was that I had one of the member defined as Ignore in the period hierarchy for ASO. It is suggested that all members must be set as Addition and then it will work (for ASO). This worked for me.

Following is the checklist if you encounter similar issue:
1. Check that the Hierarchy Type of Period Dimension is set to Multiple
2. Check the Hierarchy Type of hierarchies in Period dimension are set to "Stored"
3. Check all the members are set as "Addition" (for ASO)

If the point number 2 from above is not satisfied i.e. if the Hierarchy type is set to "Dynamic" then you may get the following error message:

ASO members with time balance members requires a time dimension to only contain stored hierarchies. Member: <Member name>

After appropriately updating the member / hierarchy, if the issue still persists then try re-creating the alternate hierarchy. I had similar problem post changing the properties and after re-creating the member(s) it worked.

Hope this helps.

Loading Data in Essbase: Have Sparse Dimension Members before Dense Dimension Members

Even after working in Essbase for quite some time, I have always learnt something new every time.

I got an extract from SQL to load data in Essbase. As far as I remember this was the first time when the format of the file was not provided by me or by my other team member. So, the columns received were in random order and I wanted to load data in Essbase. As expected there were few columns which were not required which I had to ignore during load.

I created a rule file and validated it successfully. When I tried to load the data, I got the following error in the error file for each record:

\\ Invalid number in data column

There were many account members as part of field and these were not assigned as data field.

I reviewed the data for each column but could not find any fault and then it was observed that one of the dense dimension column was appearing before the sparse dimension member and so the error. I moved that (sparse dimension) field before the dense dimension field and it worked.

Clearly, the error message was misleading as in many other cases.

This shows that when you unknowingly follow some standards we may not know until we experience it :)

Calculation Manager Business rule / Script validation issue

Business rule / Script not getting validated when line of code exceeds certain number

We have a calculation manager business rule that calls a script which calls a template around 22 times by passing different entity values. When we compiled the business rule it threw the following error:

A validation error was received from the Planning server 'http://<URL>:80/HyperionPlanning/servlet/HspAppManagerServlet?appname=<appname>'.

'Error:Error parsing formula for [<member name>] (line 5106): infinite loop in macro processing; current macro [@VAL] Rule <Rule Name>'.

On analysis, it is observed that when we made less than or equal to calls (17 – where line of code is less that 5000) to the template then it successfully compiled. In short, any further calls (more than 17 – i.e when line of code is probably greater than 5000) to the script system failed to compile.

To confirm where this is the issue with number of line, I created a rule with entire logic written as part of single script which had more than 5000+ lines. Again this time the system failed to validate and gave the same error.

Issues faced while creating first Hyperion Application

One of our clients were trying to create a classic planning application and while creating a data source non of the connections (SQL as well as Essbase) were getting validated.

For SQL database connection, the problem was that the user account was set with the password policy, (when tried manually, on first logon system was prompting  to change the password...)

For essbase connection, no port number was specified along with the server name.

Once these error was rectified, the data source was successfully created.

Secondly, they were also facing issue while creating an application. System used to give error as failed to create application, see the log. When trying to create an application manually with the given user credentials in EAS, the message displayed was as follows:

Error: 1056603 unable to spawn process for application []. Please ensure that adequate memory is available.

There were already too many Essbase applications and there was not enough memory to create another app. So, the IT team provided another server details. They had to recreate the data source connection and finally test Hyperion planning app was created.

Calculation Manager: Lexical Error. Encountered

In calculation manager, I was specifying the member name in “Member Range” manually and for one member I incorrectly included in a single quote instead of double quote. On validating I got an error with the message that includes:

Lexical Error. Encountered: <EOF> after: “”