on ā2016 Mar 02 2:49 PM
Dear Friends!!!!
I have encountered a weird issue with my planning and consolidation model. We are with BPC10.0 currently.
My standard TIME dimension from environment shell is seen as below sorted based on TIMEID and MONTH NUM
which is very good.
As required in our respective project Environment, we created a custom TIME dimension as below.
Back end the table generated with attributes as below - showing the technical names with Alphabetical order for TIMEID & MONTHNUM
From the above screen, the attributes/ properties in BW server is been created as per the technical name of the DIMENSION.
/CPMB/J3P1Q73
/CPMB/J3P8EPD
Due to this, the sorting order of data in the table is based on BASE PERIOD, where i need the sorting to be done as per the TIMEID & MONTHNUM.
Due to the above display, based on the MDX logic (LAG-1) TIME ID is being picked for the Q1 ..Q2...etc which is resulting to wrong reporting.
Our expectations are as below.
We attempted to move the position of the attributes(TIME & Month) to first position for the generated structure in BW. But still no use.
Any suggestions on how could we sort the data which will reflect front end.?
Can someone suggest how to achieve this?
Best Regards
Siddhu
Request clarification before answering.
Please show the administration of the TIME dimension in Web client!
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vadim Kalinin
Below is the screen from admin of the TIME dimension.
Basically the reason to say sorting order of the attributes is the issue with P&L report on EPM.
More in detail:
Our current versions are as below
We came across a thread with similar issue.
As of now we are not planning to upgrade but looking for any alternatives other than upgrade.
Appreciate your response.
Best Regards
Siddhu
Hi Siddhu,
Are you using HANA and enabled HANA MDX? If that is true please see OSS Notes for HANA_NUMERIC_TIME_INDEX. It was introduced specifically for such cases.
Regards,
Gersh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A couple things you mentioned were things I also experienced on my first model in 10.0 versus the previous BPC versions. Try this to see if they resolve the default sort of Alphanumeric.
I can include screenshots if you get lost, but this worked for us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 17 | |
| 8 | |
| 7 | |
| 6 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.