We use FDM to load data to Essbase and then run a script after export to Aggregate the data using Vlaidation Entities in FDM. We wrote a new Agg Script and so I changed the Validation entity from CalcALL to CALCCMA and now I get the below error.
Error: Essbase API Procedure: [EsbCalcFile] Threw code: 1030214 - 1030214 - [Tue Aug 03 13:25:25 2010]XXXXX/PLANNING/IncStmt/admin/Error(1030214)
User [admin] cannot access calc script: CALCCMA
The script is in the same folder as the old one. What is also strange is that when I try to change back the Script to CalcALL in the FDM valdiation entity I get an error as well. I checked all the integration settings and they are correct. I checked every script in FDM and asearched the adapter XML and found no references to the CalcALL script. I can't figure out where else the script would be referenced in FDM or if I need to change something on the Essbase side.
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.
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?
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.
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.