I believe EPMA tier should not effect the aggregation behavior and the outline structure, but since this is an Oracle product, I cannot be so sure about it. Then the outcome is magic! This problem disappear and I can't even reproduce it. After this operation, I deploy every application again. I detached and delete the problematic dimension for the application, and choose to "Add to app view" from Shared Library to brought it back. (Why I say "may" is that, I did encountered one application in another environment that still suffered this issue until I did point 2 below.)Ģ. If detach the problematic dimension in EPMA Dimension Library to make it "local" and deploy the application again, it "may" help. However, I did find that when I detach this dimension in EPMA Dimension Library and deploy the applications again, the outcome turned normal again. I haven't found a 100% correct workaround toward this issue so far. skipped the description for those variables since they appeared to be quite self-descriptive. However, we would like to put a variable of Entity member here. * If following is changed to "AGG("Entity")" then it works. The aggregation result would be correct if set to "0", while performance is heavily impacted. * Following is the parallel calc settings. Following is the script I used for testing: Please kindly help us on this topic if anyone has encountered this problem before. I wondered if there is change of the underlying calculation logic of parallel calculation in Essbase kernel, because we have aggregate with for a long while in version 11.1.1.3 and we adopt the same settings in Essbase.cfg in version 11.1.2.2. But we cannot define the exact member(s) to calculate to, failing to meet our client's need. If aggregate Entity dimension with "AGG()" command, the outcome is right. If I "SET CALCPARALLEL 0", which overrides our parallel calc settings (which is 4) defined in Essbase.cfg, the outcome is correct.Ĥ. However, it is much more time consuming and it does not meet our client's need for business logic.ģ. If I aggregate with "CALC ALL" it worked. Aggregation of every dimension for all level 0 Entity members are correct.Ģ. After a lot of experiments I found following conclusions:ġ. Aggregation of "Local" and "JPY" is OK, but "USD" always failed to be aggregated for some Entity members, causing upper-level number failed to tie with other currencies. After some test run we noticed that the currency conversion did not work normally. Our application is multiple currency enabled, and we wrote customized BR to perform the currency conversion and aggregation in a single Calculation Manager rule as usual. We use to aggregate Essbase for a long while and every thing was fine until we migrate to version 11.1.2.2 from 11.1.1.3 recently.
0 kommentar(er)
