How d/EPM Platform handles dirty cells olap and gets the best performance

Mauricio Mendoza

Hi.

I am new using this product and lately, I got a technical question about how d/EPM platform handles dirty cells on the OLAP. This platform is going to handle at least ten dimensions on the main budgeting cube (BPCMAIN) and every month the fact table can have at least 10.000.000 records. On average each dimension has three or four hierarchies and the greatest has 500 base elements. What is your advice in order to have the best performance during the following years? should I try to use the minimum dimensions as possible? Can you advise? How the application handles dirty cells? What tunning should I do before starting the first load?

I really appreciate your community advice. Thank you.

MikeLewis

Make sure sure don't store zeros.

On Imports:

Delete an area before importing:     OLAPDeleteDataArea(PMAINAreaToDelete);

Filter out zero values so they are not imported.

In Application Studio:

Use Cell Writes like this: =CELLWRITE(IF(C10=0,"#delete","#B"&C10),CubeName, Dimensions...)

The code above will delete the cell if C10 is zero, otherwise it will write C10 to the cube.