please check with this steps . and <b>for the Non-unique index see the step 6</b>..
A unique index does not permit these multiple entries. The index fields of a unique index thus have key function, that is they already uniquely identify each record of the table.
A unique index for a client-dependent table must contain the client field.
<b>Creating Secondary Indexes</b>
1.In the maintenance screen of the table, choose Indexes.
If indexes already exist on the table, a list of these indexes is displayed. Choose .
2.In the next dialog box, enter the index ID and choose
The maintenance screen for indexes appears.
3.Enter an explanatory text in the field Short text.
You can then use the short text to find the index at a later time, for example with the R/3 Repository Information System.
4.Select the table fields to be included in the index using the input help for the Field name column.
The order of the fields in the index is very important. See What to Keep in Mind for Secondary Indexes.
5.If the values in the index fields already uniquely identify each record of the table, select Unique index.
A unique index is always created in the database at activation because it also has a functional meaning (prevents double entries of the index fields).
6.<b>If it is not a unique index, leave Non-unique index selected.
In this case you can use the radio buttons to define whether the index should be created for all database systems, for selected database systems or not at all in the database.</b>
7.Select for selected database systems if the index should only be created for selected database systems.
Click on the arrow behind the radio buttons. A dialog box appears in which you can define up to 4 database systems with the input help. Select Selection list if the index should only be created on the given database systems. Select Exclusion list if the index should not be created on the given database systems. Choose .
8.Choose Activate .
reward points if it is usefull....
Girish
Bluesky
