Basis Errors and Solutions

Symptom

You send a table with indexes. You then delete the indexes and transport the table as a new version with completely different column names.
In addition to the indexes to be deleted, the table contains other indexes that may also relate to these new fields. This causes activation errors in a combined request.
Note that the difference between this note and Note 1098054 is the existence of other indexes in addition to the indexes to be deleted.
Other terms

Mass activation, N versions during deletion, deleting indexes
Reason and Prerequisites

This is because the N version of the indexes has not been deleted. Since these indexes no longer correspond to the new version of the table and because the system checks all indexes when you activate the table, activation errors occur and the system does not activate the table.
In the mean time, the system deletes revised versions or new versions if you implement the related note or if you have imported the relevant Support Package into your system. However, the situation is changed because, in addition to the deleted indexes, other indexes exist.
Solution

The system also deletes N or L versions if the relevant subsequent investigations allow this.
Import the relevant Support Package or implement the attached correction instructions.
Note that you must have implemented the specified related note or imported the relevant Support Package. If this is not the case, you must implement the relevant correction instructions.
Note that this note does not solve the situation if it has already occurred. In this case, you must correct the situation manually. This means that you have to manually delete the indexes in transaction SE11.
Also note the following: The situation described under ‘Reasons’ is not corrected completely by the corrections available with the correction instructions. The reasons for this is that part of the corrections require an adjustment in the dictionary, which can only be completed manually and is very complicated. This part is therefore not available as correction instruction.
The situation described will no longer occur once the Support Package mentioned last has been imported. If the problem still occurs, solve the it manually.