Diagnosis
Index &V1& is not unique as required.
A possible cause is the availability of data records with the same keyvalues in fact table &V2& for the time of the creation of the index.

System Response
Data records having the same key values after compression or afterrolling-up data is an inconsistency of data. This can lead to incorrectreporting.

Procedure
Check whether duplicate data records occur in the table and deletethese. Proceed as described in SAP Note 481450.
If duplicate data records no longer occur in the table, you can correctthe index in which you execute the action "Repair Indexes (Now)". Youcan also activate the InfoCube in the background processing intransaction RSDCUBE in "InfoCube Utilities" (recommended for very largefact tables and when the timeout for foreground actions is exceededwith "Repair Indexes (Now)".
Note that index &V1& needs to be deleted and recreated with eachrepair. With large fact tables, this can lead to long run times. Ifduplicate data records still occur in the table, the index is recreatedas not being unique.