Changing Dim Tables via a program

[Former Member]

Hello,

We have a project underway replace two company codes with 1 new company code on R3. This will be accomplished by changing all references to the two company codes at the table level(all tables) in R3 Our R3 org is working closely with SAP on this project. This clearly becomes a problem for BW. We cannot reload all of our objects because of the time required. We are considering taking the same approach on BW--replacing all references in all tables. This includes ods active tables and dim tables. My question is does anyone have any experience doing this and if so are there any important learnings or issues that you can share. This seems doable and seems to be our only alternative to keep the two systems in sync.

Thanks, Carol

[Former Member]

Aneesh,

Thank you for responding so quickly. We understand the ODS issue. Let me explain a little more clearly.

In our situation, a new company code will be added in R3, we will reload 0comp_code to pick it up, thus a new entry in the sid table. Let us call this company code 3. So now the sid table has entries for company code 1, 2, and 3. We want company code 3 to replace company code 1 and 2. What we planned to do was for all the dimension tables in the system, change all co-code sids for comp codes 1 and 2 to 3. So dimids are not touched but the sid representing the new company code replaces the sids for co code 1 or 2 whereever they occur. We understand that now there will be two different dimids representing the same combination of sids in the dimension table but don't see that as a real problem. See example below.

Now:

dimid co-code-sid other-sid1 othersid-2 .....

1 2 (cc 1) 1 2

2 2 (cc 1) 3 8

3 4 (cc 2) 1 2

4 4 (cc 2) 3 8

After Change:

dimid co-code-sid other-sid1 othersid-2 .....

1 6 (cc 3) 1 2

2 6 " 3 8

3 6 " 1 2

4 6 " 3 8

This appears to us to be a workable solution without touching any other tables. I would like to understand better your references to other tables that we need to consider.

Thanks very much, Carol

[Former Member]

Aneesh,

Thank you for responding so quickly. We understand the ODS issue. Let me explain a little more clearly.

In our situation, a new company code will be added in R3, we will reload 0comp_code to pick it up, thus a new entry in the sid table. Let us call this company code 3. So now the sid table has entries for company code 1, 2, and 3. We want company code 3 to replace company code 1 and 2. What we planned to do was for all the dimension tables in the system, change all co-code sids for comp codes 1 and 2 to 3. So dimids are not touched but the sid representing the new company code replaces the sids for co code 1 or 2 whereever they occur. We understand that now there will be two different dimids representing the same combination of sids in the dimension table but don't see that as a real problem. See example below.

Now:

dimid co-code-sid other-sid1 othersid-2 .....

1 2 (cc 1) 1 2

2 2 (cc 1) 3 8

3 4 (cc 2) 1 2

4 4 (cc 2) 3 8

After Change:

dimid co-code-sid other-sid1 othersid-2 .....

1 6 (cc 3) 1 2

2 6 " 3 8

3 6 " 1 2

4 6 " 3 8

This appears to us to be a workable solution without touching any other tables. I would like to understand better your references to other tables that we need to consider.

Thanks very much, Carol

[Former Member]

Carol,

ODS should not be an issue. However, suggest that all change logs on the ODS be deleted off.

Cubes/Dim/SID/X-Y Tables - that is quite alot of changes. Would suggest that you put this into the mandate for SAP also or atleast get advice from them on paper. Changing descriptions so that they look the same is minor but going into chanigng the SID updawards would be quite major.

Cheers

Aneesh