[ANSWERED]How can I group on same caption but different MUN in a crosstab

[erwink]

Hi there

Again struggling with my strange dimension. I've a hierarchy like Segment>Portfolio>Project>Location>BudgetItem with budget the lowest element

My customer would like to have the Budget/Forecast per Segment per Location
                     
                      B           F
Segment1 CH  20k       22k
                 D 120k     170k
                 E   50k       50k
Segment 2 CH 12k       17k
                  A    5k       12k

But with my dimension, where the same location exist several times I get (see attachment)

Segment1 CH 5k    5k
                CH 10k   11k
                CH  5k    6k
                ...

Is there a way to explain to Report Studio that those location with the same caption do belong together?

Thank you for your help

[MFGF]

Hi there

Again struggling with my strange dimension. I've a hierarchy like Segment>Portfolio>Project>Location>BudgetItem with budget the lowest element

My customer would like to have the Budget/Forecast per Segment per Location
                     
                      B           F
Segment1 CH  20k       22k
                 D 120k     170k
                 E   50k       50k
Segment 2 CH 12k       17k
                  A    5k       12k

But with my dimension, where the same location exist several times I get (see attachment)

Segment1 CH 5k    5k
                CH 10k   11k
                CH  5k    6k
                ...

Is there a way to explain to Report Studio that those location with the same caption do belong together?

Thank you for your help

Hi,

The problem here is they are not the same location member. Each is a different member with a different MUN. What you are seeing in your report is a correct representation of the data based on how it has been modelled. You'd need to have a hierarchy where there is only one location member per segment with a specific caption to achieve the result you're looking for.

MF.

[erwink]

That is what I was afraid of

Thank you for your clarification

erwin