I managed to get Logic Accounts working now & populating the target database.
In terms of Validations I was simply attempting to produce a validation report at the end of the load with a title & sub title, hence my Validation Group simply has the #Title & #SubTitle display values, with some generic ‘Rule Text’ values specified
The Validation report that launches after the export step does not contain any of the Rule TExt values that I specified - it does not even contsain the name of the validation group, the location or the catagory
Yes - Validation has been set to 'Enabled' in integration settings, and i have imported all the Oracle reports from the XML file that is provided with the install.
I have set up a Validation Entity which references a single entity BE.0011 and its parent in the Essbase target cube - I have tried many combinations of options in the Validation Entity, but I consistently get the error "Consolidate failed:Essbase API procedure: [EsbCalcFile] threw code : 103001...............invalid character in name (BE.0011) in ESSAPI function EsbCalcFile"
When I don't specify the above Validation Entity in the Location specification, the data loads OK but the validation reports do not contain any meaningful content
this is more an Essbase issue than FDM, however, isn't there something in Essbase where a member name used in a Calc script which includes a special character (period) as part of the name must be enclosed in brackets.
Can you tell me what you’ve done to fix the logic account part of this post? I have exactly the same problem and, as you, I believe I’m doing something fundamentally wrong to not get the logic accounts values generated.
I have tried to put the simplest logic account and still does not have any impact…