cancel
Showing results for 
Search instead for 
Did you mean: 

SE14 and DDSTORAGE for BW partitioned indexes

Former Member
0 Kudos

We have a cube whose underlying table is /BIC/ZBACKAGG.

It has 5 indexes.

The cube is used to backup APO Demand Planning data.

Every time the DP backup runs, the indexes are deleted.

So I goto SE14 and recreate them.

The next day ther are gone again!

They do not appear in DDSTORAGE.

If I use SE14 to recreate their definition (without actually creating the indexes) they appear in DDSTORAGE.

As soon as I actually create them they disappear.

This has only started happening since we migrated to another OS, and only happens with this table/cube.

Our Production system, which hasn't been migrated yet, is fine.

Any ideas why, SE14 removes the entries from DDSTORAGE?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Maybe.

However everything worked before the migration but this small probelm started after the migration.

It isn't causing any problems but nevertheless is something not quite right.

former_member204746
Active Contributor
0 Kudos

IMHO, I believe that your APO functional should be responsible of configuring these indexes. I know that this is the case in BW system and APO is derived from BW.