time.txtHi,
I wonder if anyone can throw out some pointers on this one.
We are required to change our financial year from from Oct-->Sep to Apr-->Mar to fall in line with our holding company. This means we need to have a "short" year from Oct 2017 to Mar 2018 to bridge the gap
So we have revised our TIME Dimension to reflect this.
The odd thing is that Currency Conversion now does not work for Periods in the "short" year. Seeing the TIME Dimension is the only thing that has changed, the problem is most likely there.
Other things:
- Currency Conversion still works on prior Periods.
- I have removed the TIMEID Property and processed the Dimension. I have then replaced it and re-processed.
- I have uploaded a CSV/TXT of the TIME Dimension.
System:
- SAP BPC 10.1 on BW 7.51 on HANA
Any hints would be welcome.
Kind Regards
Nick
With SAP Landscape Transformation 2.0 (licensed product) driven solution one can handle fiscal year conversion. Also for shortened fiscal year introduction you can use SAP service for a impact analysis and guide to implement.
Thanks, Manish
This is specific to BPC on NW. Not really ERP (in my case). So, at this point, it's just the reporting component and specifically how I need to configure the TIME Dimension to cater for the short year, plus the issue we are experiencing with Currency Conversion.
I hope I am understanding you correctly.
Kind Regards
Nick
From my experience, BPC doesn't respond very well when changing the time dimension..
What selections are passing onto the data manager package?
Have you considered running your consolidation and then changing the time dimension after it's finished?
Hi Lucas,
Thanks for the reply. (Sorry for the delay in responding - other issues).
I do know the TIME Dimension in NW is a lot more fiddly than in the MS version.
The selections are CATEGORY, PCENTRE and TIME. (We're not changing too much here. It normally runs out of preset Package Links.)
We can't really do that. We run translation packages on a very regular basis. (If I understand you correctly).
Kind Regards
Nick
The properties of time dimension has to be set according to fiscal year:
Mar has to be DEC and month number 12.
And it has to be done for all months of all years.
Hi Vadim,
Much appreciate you getting back to me. (Apologies for the delay in replying).
Let me give that a try and get back to you. This is going to be fiddly, I see.
We might have to have the ID as 2018.DEC but the description as "March 2018". The only issue is that we can't really change the past Time structure and the next fiscal year will be a complete 12 months with the new months.
Let me hack a bit more and I'll revert. Thanks, again.
Kind Regards
Nick
May be you can copy the environment (and use copy for historical reports)?
And change everything in the model...
In general I think it's not possible to successfully combine different fiscal years with a single time dimension.
BPC logic assumes that first month of the year has PERIOD - JAN (hard-coded in standard measure) and last month of the year - DEC (in some calculations).