This content has been marked as final. Show 8 replies
What is the error you get while running Copy Data?
MSG_COPY_DATA_OPTIONS_FAILED: An error occurred while running the specified calc script. Check the log for details.
The log says 'Invalid fix statement'
How is that even possible? It should be building a correct fix statement. Thus the need to see the actual calc this copy data function is building.
Is it the essbase application log that you have had a look at?
Yep. How can the 'Copy Data' function create an invalid calc? It's all pick and choose
When ever you run a copy data Planning creates a calc script on the basis of selection made on the web and pass it for calculation on Essbase (Along with few sql copy operations at relational database, if needed).
Now the reason you are getting this error (Most probable): The script which planning generates has a limit on number of characters (I don't remember the exact value), if the number of characters are less the specified limit then it works fine else you get the error for invalid script.
1. Try copying the data in chunks,
2. If you dont have annotation, supporting details, cell text etc then use calc script instead of data copy from web.
Does it store the calc script anywhere where I can open it in a text editor and look?
You can find it in Essbase Application log:1 person found this helpful
[Mon Nov 12 07:40:38 2012]Local/App1/Plan1/admin@Native Directory/8676/Info(1013162)
Received Command [Calculate] from user [admin@Native Directory]
[Mon Nov 12 07:40:39 2012]Local/App1/Plan1/admin@Native Directory/1380/Info(1012553)
Copying data from [version1] to [version2] with fixed members [Account(A1); Period(Jan); Year(FY12); Scenario(Current); Entity(Ent1)]
Above was small one so you can see the complete one, but if in case its length is more you wont be able to see the complete one here ,
More information you can find in the fiddler trace, below is the one on the basis of which this script is created:
I doubt you will be able to see any scripts, I am not even sure if it does actually create one or just generates the code and runs the datacopy on the fly.
Are planning and essbase outlines definitely in sync, have you tried simplifying the data copy to see if it works, what is the exact error messages being generated in the essbase application log.