I am receiving the error :
Cannot Open Cube View.Essbase Error(1054060): Essbase failed to select application XYZ , because test@Native Directory is not completely provisioned by planning.
I checked the provisioning through shared services and its fine. Please suggest what more steps can i take for the issue resolution.
Thanks in Advance.
There is a document 'A Specific User Cannot Access Essbase Even After Deleting and Recreating the User [ID 1365000.1]' in MOS that might be of help.
Delete/deprovison user "userX" completely in Shared Services. Check that the user is no longer visible within the interface of the various products (within Planning, in the EAS console, etc...)
Log into the EAS console as an Essbase administrator user
Right-click on the "Security" node at the bottom of the list of applications > Export security file. Enter a file name for the exported file.
Locate the exported security file under \Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin
Search through the security file in a text editor for the affected "userX". The presence of filters whose name may be based on the user (such as "fuserX") is expected, but the user itself should not be present.
If the user is present, return to the EAS console to remove it as follows.
File > New > Scripts tab > MaxL Script > OK. An empty script editing window opens.
Paste the following command into this window:
drop user "userX@Native Directory" from security_file;
Note that the example above assumes the user is native. This may not be the case. See the security file export for the full name of the affected user and the name of the directory it is in.
MaxL (drop down menu in toolbar) > Execute
The statement should now run successfully and remove user "userX". You can close the script without saving it.
At this point you should be able to recreate the "userX" user from scratch and they should no longer have issues connecting to Essbase.
Planning provisioning requires some steps I believe. Your error is specific to Planning: because test@Native Directory is not completely provisioned by planning
If you are using Planning: post inquiry here: Planning and Budgeting