Display values in different versions for 3 specific years

[Former Member]

Hi

I want to show in a dynamic report and in a dynamic input schedule values for different versions ACT and PLAN via Excel client.

In the rows are entity, time (for 2009, 2010, 2011) and version. And in the columns are special time dimension to show month. Sounds very strange - and it is so... Now I want to show only values for ACT for year 2010 and PLAN for 2011.

How can I enter the dimension within the expansion area? Is there a way to combine 2 different dimensions like a statement "where time is 2010 and version is ACT"?

Thank you very much for your ideas

[Former Member · Accepted solution]

Hi Marco,

The design of the schedule has to be based on the way you want to display your records.

If you want only ACT for 2010 and PLAN for 2011, you can make it static instead of dynamic. Another alternative, if you want the time to be dynamic, then you can get the first year based on the CV of time and the next year can be populated using EVTIM function.

Hope you got some idea.

[Former Member · Accepted solution]

Hi Nilanjan

Thank you for your post.

I'll give EVTIME a try. But it will not solve my problem I guess. EVTIM is helpful for columns to use offset I do understand. Can I use it within expansion area of EVDRE function?

The display behavior has to be dynamaic. Cause there is in the first expansion dimension entity with a hierarchy. 2.nd expansion is year and 3.rd is version. And I only want to see ACT row for 2009, FC row for 2010 and PLAN row for 2011. Next 3 rows must be the next item of dimension entity and so on...

Currently I see 2009 ACT, 2010 ACT and 2011 ACT same like 3 HR and 3 PLAN rows.

Any ideas?

[Former Member · Accepted solution]

Hi Marco,

I would suggest you to have expansion only on rows. Keep the columns static. Keep Entity in the row expansion. In the columns, you will be having year and category (however, without any expansion). You can get one of the years from EVCVW and the rest 2 years can be populated using the EVTIM function. The categories can be hardcoded. In the first column, it will be ACT, then FC and then PLAN.

Hope you got the idea.

[Former Member · Accepted solution]

Thank you very much!

That would be a very clean way to design this view. But the client wants to have 2009 ACT, 2010 FC and 2011 PLAN among each other in rows. The columns are static and with month populated.

Maybe a kind of work around with using attributes? But how till in expansion area a command like use for ACT only 2009.

[Former Member · Accepted solution]

Hi Marco,

I am really sorry if I am not able to follow you.

Are you not able to get the year? or do you want the months also to be populated for each year?

[Former Member · Accepted solution]

Hi Nilanjan

It is maybe hard to explain without showing a pic of the table. My main issue is to find a way to show in a simple table in column A February and column B March. First row has entity knot with 2009 (time dimension) ACT values. Second row entity knot with 2010 Forecast values. Third row again entity knot with 2011 PLAN values. And then same struktur for each entity bas member in the following rows.

Maybe it is hard to imagine cause I'm using 2 different time dimension. One is standard with days, week, month and year for currently 3 years and one is new with only weeks and month under a total.

This time better?

Thank you!

[Former Member · Accepted solution]

Hi Marco,

Let me try to picturize the format. Lets see if I understood it properly or not.

                         FEB      MAR    and so on
E1    2009    ACT
E1    2010    FC
E1    2011    PLAN

Is it what you are looking at?

[Former Member · Accepted solution]

Perfect!

Didn't know the possibility to post a table...

[Former Member · Accepted solution]

Hi Marco,

Thanks for confirming. So, we are in the right direction.

Now, if we take that design, then you will have 3 dimensions in rows - Entity, Time (the standard dimension), and Category. You will have 1 dimension across the columns - the other time dimension (hoping that this is a user defined dimension).

Hope this helps.

[Former Member · Accepted solution]

Correct!

And now I want to design a dynamic report for this, where only TIME 2009 and VERSION ACT are shown in one cell; same for TIME 2010 and VERSION FC. And so on with the PLAN values, right?

[Former Member · Accepted solution]

Yes absolutely.

We have the option of using Suppress parameter for this purpose. However, this might be little cumbersome. Please refer to the below link:

http://help.sap.com/saphelp_bpc75/helpdata/en/2c/e37096b9264faa8645020bb211a1fc/content.htm

What we need to do is suppress (ACT, 2010), (ACT, 2011), (FC, 2009) and so on.

Hope this helps.

[Former Member · Accepted solution]

Thank's for that hint! That's what I was looking for.

Unfortunetly I'm not able to handle this. I used "2011.#;[IST,HR]" for suppressing values of IST and HR for 2011. I have entered the command in all possible expansion area cells for value suppress. Of course only one times. Before that I have seen all values, afterwards I see nothing in the table.

I also tried ";" instead of having "," . But no difference. Where is my mistake?

Edited by: Marco Rückert on Sep 20, 2010 7:06 PM

[Former Member · Accepted solution]

Hi Marco,

Is 2011.# a member in your dimension?

Secondly, if you are having a suppression based on multiple dimensions, then you can have single members from each of the dimensions. For example,

(2011.JAN, IST), (2011.JAN, HR)

Hope your got the idea.

[Former Member · Accepted solution]

Thank's.

Yes, 2010.# is a additionally member in the time dimension.

Do I have to use in the suppresion all leaves or can I use knots?

[Former Member · Accepted solution]

Hi Marco,

You can use any node in the suppression. However, you should have only one member from a dimension. In the earlier post, you had mentioned (2010.#, HR, IS). This is wrong because both HR and IS are from same dimension.

Hope you got the idea.

[Former Member · Accepted solution]

Hi Nilanjan

Thank you for your help!

Now we are using a new property for selecting data on different dimensions.

Points signed.

Regards,

Marco