Fields Inconsistent with the runtime object

[Former Member]

We have created a new append structure for a table in our development environment and both the append structure and the table have been activated.   Now, when attempting to access the table, we are getting dumps.  After investigating the issue we have recognized that there are database inconsistencies which are listed in the database utility checks (transaction se14).  The additional fields from the append structure are all listed in the runtime object but do not exist in the database object.  We attempted to use the “Activate and adjust database” option within SE14, but it completes without any changes to the database.  

As possible solutions we attempted to remove the fields and recreate with no difference in results.  We also tried to just remove the append structure just to avoid this issue and SAP will not allow us to delete the append.  We attempted this delete by accessing from both the table’s append structure list as well as the direct deletion of the append structure from the SE11 main screen.  Neither approach worked and the error remains.

Any thoughts on either how these discrepancies occur so I may investigate further or any resolution procedures will be appreciated.

[TuncayKaraca]

@Nicholas

There is a good information here: Editing Tables and Indexes in the Database

You may compare table definition and runtime object Extras ® Runtime object ® Check

And you can force conversion, reconstruct the table, etc...

[Former Member]

Hi Tuncay,

Thank you for the quick reply and the link to the documentation.  I have referenced this as I was doing my investigation and I have done the Runtime object check which states that my runtime object is correct and active.  I have done a check on the database object which resulted in the screenshot attached to my original post.

I also tried the force conversion previously and it came back with an activation error about the main table not being able to be activated during the conversion due to the inconsistencies.

Thanks again for the input but it seems like the issue may be a little deeper than this.

[Former Member]

Just as closure for anyone referencing this posting.  The resolution that worked for us was to have the BASIS team member log in with the DDIC account and run the "Table >> Reconstruct" menu path.  The details of the procedure we followed is well documented in note #1248769.   

[TuncayKaraca]

Hi Nicholas,

I am glad you resolved the issue. It's nice to know.