Secondary Index on ODS Change Table

[Former Member]

Hi All,

We have a process that does a lookup to the change table /bic/XXXX40 in the update rules while loading the ODS. We are having performance problems that can be resolved by putting a secondary index on the change table. We are able to create the index in the Dev env using SE11, but we can't put it in a package other than $TMP. Putting a secondary index on the ODS in the normal way didn't put the index on the change table so that doesn't help us.

Any ideas on how we can get our new index into a package that we can transport?

Thanks in advance!

[Former Member]

Just echoing Jorge's post - you'll need to open Prod and create it there, same is if you were creating secondary indices on master data tables or dimension tables, since the wkbench doesn't support creating indices on them either.

PS.

Put yourself on the SDN world map (http://sdn.idizaai.be/sdn_world/sdn_world.html) and earn 25 points.

Spread the wor(l)d!

[JoergLatza]

Hi Jason,

this is related to the fact, that the name of the table is generic in a sense that its been created in the transport target system during the after import method and you can not know the name of the table while in Dev System.

I think you need to open the box an create the index in the Prod System.

Hope this helps

Cheers

Joerg

[Former Member]

Thanks Joerg. That is exactly the conclusion we came to and we did end up opening the prod system and creating the index there.

Thanks again!

Jason