I have created an Essbase app in EPMA (normally use EAS Console) so that I can utilise the dimensions being used by Planning and HFM. The app has deployed and I have noticed that there are several rules files created - one for each dmension (but two for Accounts).
I then double-clicked a rules file to see what is in it, but get the message "Cannot open rules file created in Essbase Studio". I assume that this means that Essbase apps created in EPMA are actually using Essbase Studio and that rules files are being generated (via Essbase Studio) in order to build the dimensions?
I'm a bit confused as to how and why Essbase Studio enters the picture (as I am not directly using it and was not previously aware that it was part of our install)!?
Essbase Studio and EPMA use the same private API to create the load rule. I'm guessing a flag is set on the rule to say "Don't allow to be opened" and since Studio was the first to do this, the message was written to say Essbase Studio created this. By the way if you are trying to look at a SQL statement in the rul, you could open it in Notepad and the SQL will be in clear text (Do this at your own risk, don't blame me if you mess up your rule)
Thank you for that great information. I had a question here -
Is that a bug or a feature, since I am at the same step and I see extra rules file created when I deploy an EPMA essbase application. What can be done to avoid the extra rules files from generating itself automatically?
This is not a bug, it is as they designed it. There is no way to stop Studiofrom generating the rules files. You say extra, they are not extra but based on what you are building, how Studio thinks the rules need to be created to do everything (Alternate rollups, attribute dimensions , special properties, etc