copying calculated data

Good day Community.

We are trying to copy data using the OLAPCopyDataArea function. This works for loaded or captured data but doesn't copy calculated data (data created by a business rule).

A business case example would be copying a calculated version of data into a storage version that doesn't have rules applied to it.

Can anyone offer any suggestions?

Thanks,
Bilal

Find more posts tagged with

Infor EPM Discussions

Comments

martin-reischl

Hi Bilal,

the last parameter of the OLAPCopyDataArea function, useOnlyBasicElements, will define if rules calculated values are included in your source query. Set the parameter to false to also query rules calculated elements. In this case, make sure that your data area is restricted to just base elements for all dimensions - otherwise querying the data area may take quite long, and copying (numeric) data to C elements will not work anyway.

Best Regards

Martin

John Robson

I would just add that before the copy can take place the results of any calculations not already stored in the rules cache need to be calculated. In many cases more calculations will be triggered than in normal interactive use. It's important to test the performance of the copy process in a test environment before deploying it and think about scoping the copy e.g. user picks a year but can't pick all years.

unknown

I reduced the scope as much as possbile and set the param to false to include base values and calculated values.“ OLAPCopyDataArea(dActualsData, "CSTMAIN", "Relative", 1.0, targetElements, sourceElements, true, false);

I ran the copy from Application Studio. It completed in 2 hours. (Process Editor times out in 10 minutes so App studio is a better option)

Even though the process didn't give any errors, it doesn't seem to have copied my test calculated line.

Any suggestions?

John Robson

I have seen two causes of poor performance.
Filters not applied as expected because of poor process design e.g. a filter on period not being applied to the source data area.
More importantly the copy triggers any and all OLAP rules to be calculated. Some rules may execute slowly and/or result in huge numbers of calculated values - example IF(Inventory Count > 0, 1, 0) to count the # of SKUs with inventory. In 99% of use cases you should replace the assignment of 0 with N/A. There are many other use cases like DB() references in nested IF statements which can't be prefetched.

Temporarily enable the Rules debug function and look at the start and end timing for rules calcs and see where the time is going. Bad rules gobble resource like RAM and they may time out.

Some of my consulting colleagues are expert at tuning OLAP rules and if you aren't confident in analysing rule performance it may be advantageous to engage one of them to analyse your model and process.

John

Peter Mayall

Make sure you use OlapDataAreaBCells instead of OlapDataAreaAllCells for wildcard source elements.

unknown

Hi Peter

Yes I made sure its using the OlapDataAreaBCells .

Thanks,

unknown

Has anyone noticed the copy scripts behave differently when executed in App studio compared to Process Editor. For example on the script I loop through accounts. The loops work but the copy seems to be ignored as it finishes way too fast. For example the code below in the Process editor executes but when run synchronous in app studio it seems to be ignored without error. ( I want to run it synchronous to read the debug notices)

OLAPDataArea dActualsData = OLAPCreateDataArea(oConnection, "CSTMAIN",
                                                       OlapDataAreaIncludeB | OlapDataAreaSuppressNull, OlapDataAreaOperatorNone,
                                                       0.0, OlapDataAreaOperatorNone, 0, sourceElements);

  OLAPCopyDataArea(dActualsData, "CSTMAIN", "Relative", 1.0, targetElements, sourceElements, true, false);

Regards,

Bilal

Copyright © 2025 Infor. All rights reserved.