cancel
Showing results for 
Search instead for 
Did you mean: 

Identical ID in two or more dimensions encountered during transport issue.

Former Member
0 Kudos

Hi there,

we encountered an issue WHEN having members IDENTICAL ID in two or more dimensions. Example:

ACCOUNT Dim; member 1000 = Cash

MATERIAL Dim: member 1000 = Plastic Cup

When in a report, we are showing only ACCOUNT members in the rows (hardcoded). for the 1000 member we have to specifiy ACCOUNT:1000 for the correct account and description to appear. - When not specifiying the dimensionname before the account then 'for whatever reason' the MATERIAL member will be display and used in report.

Here is the problem! - When we transport the report, whith hardcoded ACCOUNT:1000 celll from SB to our DEV environment, then the report does NOT work appropriatly anymore! ... this is the case as the DEV environment does NOT have a member 1000 in the MATERIAL dimension. Hence the differenetiation or hardcoding is not needed. However in addition to not needed the transported Report is NOT working anymore due to that exact same. - One once we go in DEV to remove the 'ACCOUNT:' before 1000, then the correct discription and values are refreshed, before (ACCOUNT:1000) it does not refresh with values.

How come? How to handle this inconsistancy? --- When hardcoding ACCOUNT:1000 in dimension set where numerous dimension have the 1000 member, the report works. - However same report, in an environment without identical members in numerous dimension, the report does NOT work.

Any suggestions?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I think it is best practice not to have identical IDs in different dimensions. I have run into problems in input schedules as well and it can get a bit messy.

What we did to get around it was to assign some prefixes

ie

Account: A_1000

Material: M_1000

esjewett
Active Contributor
0 Kudos

Hi,

Interesting. This only happens when you are not using an expansion. This looks like a bug, as the members "ACCOUNT:1000" and "1000" should be treated exactly the same in your scenario. You should probably open a message with SAP.

One workaround you can use to guarantee that the report works in all systems is to use an =EVMBR("APPNAME","ACCOUNT:1000") function in your row/column-key range instead of hardcoding "ACCOUNT:1000" directly into the cell. You will have to format the cell where you do this as "General" instead of "Text" before Excel will evaluate the formula.

Hopefully that works for you as well,

Ethan