Hello Matt,
We had tried recreating the table the way you explained above before carrying out these deletions.
But after recreating database table, the runtime object was still inconsistent with same error as shown above.
So we tried activating and adjusting it with database but it generated abap error "LOAD_TYPE_VERSION_MISMATCH"
**************************************************************************************
| Runtime Errors | LOAD_TYPE_VERSION_MISMATCH |
| Date and Time | 05/05/2014 11:36:25 |
Short text
| Change of a Dictionary structure at runtime of a program. |
What happened?
| Runtime error |
| The current ABAP program "SAPLSDNT" had to be terminated because one | |
| of the statements could not be executed at runtime. |
What can you do?
| Restart the program. | |
| If the error persists, contact your SAP administrator. | |
| You can use the ABAP dump analysis transaction ST22 to view and manage | |
| termination messages, in particular for long term reference. |
Error analysis
| The ABAP runtime system detected that the Dictionary-type "DDXTF" changed | |
| during the flow of the transaction. | |
| As the type was already used in the old version | |
| and in the new type should be used in the same transaction in the new | |
version, the transaction had to be cancelled to avoid inconsistencies. Information on where terminated Termination occurred in the ABAP program "SAPLSDNT" - in "DD_PUT_NAMETAB". The main program was "SAPMSGTB ".
In the source code you have the termination point in line 71 of the (Include) program "LSDNTU10". |
Thanks for your quick response !!
Shradha