Correcting Conversion Errors in the PARCONV Phase

Context

This procedure enables you to correct problems that occur in the PARCONV_UPG phase. The errors can roughly be divided into two classes:

Technical problems on the database

You can recognize these in the system log (transaction SM21), where they are marked with SQL-ERROR followed by an abbreviation with an error number. The problem is often caused by a lack of space.
Logical errors in the object definition

These could also appear in the form of SQL errors. Some of them, however, are already detected by the system before a command can be given to the database. This type of error frequently occurs if you decide to revert to the SAP standard when you use the modification adjustment functions in transaction SPDD (ACT_UPG phase).

Example

A field was added to an SAP table. This field was also used in an index or view. In the ACT_UPG phase, however, you decided to return to the standard definition of the table (using transaction SPDD) and this additional field was removed. The index or view definition is now incorrect since the relevant table field is missing. If the index definition is not corrected and the ACT_UPG phase was completed with ignore, errors occur when the objects are created.

Analyze the PARCONV.ELG log.
Remove the cause of the error.
- Technical problems on the database
  
  Read the documentation in the database system about how to correct the error. If necessary, extend the database.
- Logical errors in the object definition
  
  Correct the objects. To do this, you can use transaction SE11. In the above example, you could, for instance, remove the deleted field from the index or view definition or reinsert the deleted field into the table. In addition, check whether the objects that are not contained in the standard system and that are now incorrect can be deleted completely.
Repeat the PARCONV_UPG phase.

For more information about alternative procedures, see SAP Note 177680 .