This content has been marked as final. Show 9 replies
You may want to check the LOAD action script of the Essbase adapter in FDM, calc scripts can be hard coded in that action or reference other parameters. These can be accessed using the workbench client.1 person found this helpful
Thanks for the response.
I went through all of the Event scripts and Action scripts in the Apapter and couldnt find that Calc Script referenced anywhere.
I think this may have been covered before on this board. Have you set the "Enable String Load" integration setting. If set to off, only Essbase admin users can load to essbase. I assume your "admin" user is the FDM user rather than an essbase user?1 person found this helpful
Enable String Load is on. I've search the boards and found some related posts and checked all integration settings for the adapter and they are set correctly.
Has security been set as per the info given at the end of the adaptor readme document?1 person found this helpful
I just read the ReadMe and here is the relevant part:
Essbase Security Requirements
Some FDM tasks require the user to have certain security privileges for Essbase. The following table outlines the tasks and Essbase privileges required.
Perform a consolidation (assigning a Validation Entity to the FDM location).
Add Calc privilege (ESB_PRIV_CALC) to the active database
I'm assuming I will need a DBA to check this. The funny thing is that this was working before perfectly fine and then I changed the script in the validation entity and got the error. When I changed it back to the original script that worked I recive the same error. I was not involved in the implementation so I don't know how this was set up.
I haven't used the latest version, but have you checked in shared services to see if the CALC function has been provisioned for the user?
Yes, all of the calcs are provisioned for the admin user.
Jft85's point is that you can write the command to execute the calc script directly within the LOAD action script within the FDM adapter. This would be a direct call and would bypass using the validation entities.