Do Reporting and Budget Controlling with BPCMAIN Cube in Long-Term

unknown

Hello,

I am building a new Budgeting and Planning model in the new version of d/EPM (11-2021 On-Premisse).

For the elaboration of the Budget I will use the standard version of d/EPM (d/EPM Business Applications).

But I have some doubts about how I should carry out reporting and Budget Control. Because the BPCMAIN cube has some long-term limitations for history query, and information maintenance complexity, because of dimensions such as BPDCYCLE, BPDLEVEL, BPDSTEP, etc... and also because of the high number of dimensions that do not let's use it. Note: that these concepts make sense for the elaboration of the Budget.
To give you an idea of ??the constraints, on this client I will load actual data every day, and I will have a data history since 2018. After 3 years, I have 3 budget cycles produced in dEPM, and I will also have the actual data loaded 3 times (1 per budget cycle), which will take up space, will also have 3 actual versions which may be different. And at the level of compliance, it's a problem because if the data is closed it can't be moved or updated.

My solution is to create an intermediate cube (BPCMAIA_RPT), with only the dimensions I actually need (without BPDCYCLE, BPDLEVEL, BPDSTEP, etc...), where I will update the actual data daily, and when I close each Budget cycle I copy the budget for this cube every year.

What do you think about this solution? Is there anything I'm forgetting?

Best Regards

Rui

Nick Gladkov

Hi Rui, this sounds like a good enough solution from my perspective for now and we are working on releasing some additional functionality which will improve your experience like loading Actuals only once, having new concept of perspective of the cube which will show only relevant information based on the concept (so when you choose particular cycle, system will filter out all information which is not relevant) and archiving data by cycle