Scribd
Upload
42 views6 pages

How To Roll Back Table Conversion

This document provides guidance on how to roll back a table conversion in SAP when an incorrect update has been made to a table definition, leading to an error in the conversion process. It outlines the steps necessary to unlock the table, drop temporary tables, and reconstruct the original table definition. The article emphasizes the importance of taking backups to avoid data loss during the rollback process.

Uploaded by

aditya.rajak2024
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
42 views6 pages

How To Roll Back Table Conversion

This document provides guidance on how to roll back a table conversion in SAP when an incorrect update has been made to a table definition, leading to an error in the conversion process. It outlines the steps necessary to unlock the table, drop temporary tables, and reconstruct the original table definition. The article emphasizes the importance of taking backups to avoid data loss during the rollback process.

Uploaded by

aditya.rajak2024
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

SAP Knowledge Base Article

1925322 - How to roll back table conversion?


Component: BC-DWB-DIC-AC (Basis Components > ABAP Workbench, Java IDE and Infrastructure > ABAP
Dictionary and ABAP CDS > ABAP Dictionary Activation and Conversion), Version: 14, Released On: 20.02.2024

Symptom
A wrong update to a table definition was performed in SE11, which led to a table conversion in SE14. But this change is not the
correct one.
The table conversion stopped with "Error in step 5" in SE14:

Clicking "Analyze adjustment", more details can be found:


Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance
to real data is purely coincidental.

Environment
NetWeaver ABAP based systems

Reproducing the Issue


1. Execute transaction SE14
2. Input table name
3. Edit
4. Click "Continue adjustment"
5. "Error in step 5" occurs

Cause
There are multiple reasons for table conversions. After the table definition is edited in SE11, database table will be adjusted to
the modified table definition.
If the database table cannot be adjusted using SQL statement like "alter table <table name>...", a table conversion is needed.
For example, if table TAB has a field with length 6, and now you changed the length to 3 in SE11. This change
cannot be achieved by executing "alter table..." statement on database level.
So when trying to activate the table, error occurs as below:
TABL <Table_Nane> was not activated
Check table <Table_Name>
......
ALTER TABLE is not possible
Structure change at field level (convert table <Table_Name>) <<==!!
Go to transaction SE14, edit this table using function "Activate and adjust database" with selecting option "keep data", to
trigger a table conversion.
For more detailed information about table conversion, please refer to the wiki page Table Conversion - Frequently Asked
Questions.
But not all the table conversion necessary. Some table conversions were triggered by mistake due to incorrect update to the
table.

Resolution
Please note that table conversion discussed in this document is about transparent tables ONLY. If a
conversion roll back on a cluster table is needed, please refer to KBA 2769310 - Frequently-asked questions
about table conversion on cluster table such as BSEG.
Here is an example:
The field F3 of table ZTEST01 was changed from DEC 8/2 to DEC 8/4, which lead to "digit before decimal place" to
be shrinked from 6 to 4.
Generally such change is not acceptable. It is necessary to roll back the conversion, and change table definition to original
one.

(This example is based on Oracle databases, but this method should be applicable for other database types.
Table conversion is generally executed in 6 steps. In step 2, the original <table_name> is renamed to be QCM<table_name>.
So all entries in <table_name> should be contained in QCM<table_name> during table conversion.
To avoid data loss during/after rollback, take a backup of table QCM<Table_Name>. The QCM<table_name> can be found
via "Object Log" in SE14. )

To roll back a conversion, please follow the steps below:


Step 1: Unlock the table from conversion in SE14:
Step 2: Drop temporary database table QCM8ZTEST01 on database level.
Step 3: Rename temporary database table QCMZTEST01 to ZTEST01 on database level.
Step 4: Reconstruct table ZTEST01 via SE14 -> Table -> Reconstruct with user DDIC.
Step 5: Roll back the table definition (change from DEC 8/4 back to DEC 8/2 for field F3) in SE11 and activate the table.

After that, the table should become consistent with the original definition:

See Also
KBA 2465903 - Error DT064 "Structure change at field level (convert table ...)"
KBA 1925367 - Dump CONVT_NO_NUMBER occurred during table conversion
KBA 1925368 - Dump BCD_FIELD_OVERFLOW occurred during table conversion
KBA 2769310 - Frequently-asked questions about table conversion on cluster table such as BSEG
Keywords
table conversion, roll back, unlock table, error in step 5, step5, unlock adjustment, SE14, QCM table, QCM8 table, SE11,
continue adjustment, reconstruct, adjustment terminated in step 5, CONVT_NO_NUMBER，BCD_FIELD_OVERFLOW,
Convert data to new table, delete renamed table, create secondary indexes

Products
Products

SAP NetWeaver 2004

SAP NetWeaver 7.0

SAP NetWeaver 7.3

SAP NetWeaver 7.4

SAP NetWeaver 7.5

SAP enhancement package 1 for SAP NetWeaver 7.0

SAP enhancement package 1 for SAP NetWeaver 7.3

SAP enhancement package 2 for SAP NetWeaver 7.0

SAP enhancement package 3 for SAP NetWeaver 7.0

This document refers to


SAP Note/KBA Component Title

2769310 BC-DWB-DIC-AC Frequently-asked questions about table conversion on cluster tables such as BSEG

2465903 BC-DWB-DIC-AC Error DT064 "Structure change at field level (convert table ...)"

1925368 BC-DWB-DIC-AC Dump BCD_FIELD_OVERFLOW occurred during table conversion

1925367 BC-DWB-DIC-AC Dump CONVT_NO_NUMBER occurred during table conversion

Dump BCD_FIELD_OVERFLOW occurred during table conversion

Table Conversion - Frequently Asked Questions

Dump CONVT_NO_NUMBER occurred during table conversion

This document is referenced by


SAP Note/KBA Component Title

1925368 Dump BCD_FIELD_OVERFLOW occurred during table conversion

2806828 BC-DWB-DIC-AC Activation error during update of component SAP_HR in SPAM

2596448 BC-DWB-DIC How to determine table conversion duration?

2465903 BC-DWB-DIC-AC Error DT064 "Structure change at field level (convert table ...)"

2441365 BC-DWB-DIC-AC "Table not found in clone list" error during migration

2428810 BC-DWB-DIC-AC Frequently asked questions about table conversion

1925367 BC-DWB-DIC-AC Dump CONVT_NO_NUMBER occurred during table conversion

Attachments
File Name File Size Mime Type

analysis_adjustment.PNG 36 image/x-png
database_object.PNG 11 image/x-png

drop_table.PNG 9 image/x-png

step_5.PNG 30 image/x-png

runtime_object.PNG 13 image/x-png

unlock.PNG 26 image/x-png

rename_table.PNG 13 image/x-png

roll_back.PNG 28 image/x-png

You might also like