cancel
Showing results for 
Search instead for 
Did you mean: 

Rate cube in Periodic or YTD?

Former Member
0 Kudos

Hello everyone,

I know that - with BPC - there are always several ways to do something, so I'd like to get your views on a conundrum I have.

A project I am working on will bring several different appsets in 7.5MS into one environment in 10.1NW.

However, I have conflicting views on what the (single) rate cube should be - YTD or Periodic.

The client has a consolidation model which is YTD, but carries out planning and forecasting in a seperate model which is periodic. I would like to rationalise as much as possible, including only having one rate cube.

But what impact would it have if it doesn't match the Measures of one model or the other? What extra steps would I need to take to enable FX translations with the non-matching model?

Interested to hear your views, as I'm not entirely convinced either way.

Thanks in advance

Best wishes,

Jason

Accepted Solutions (1)

Accepted Solutions (1)

former_member186338
Active Contributor
0 Kudos

Hi Jason,

Traditionally (if you look on the ENVONMENSHELL) the Rates cube is PERIODIC and it's used in both YTD Consolidation and Periodic Planning.

Vadim

former_member186338
Active Contributor
0 Kudos

P.S. Rate Accounts are AST - meaning that the values are stored as YTD in Periodic cube!

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Jason,

I have used YTD and PER rates models with (YTD) consolidation and (PER) planning models and have not found any differences in configuration I had to make. As Vadim said, because the accounts used in the rate model are typically AST the data is stored in YTD format anyway.

BR,

Arnold