identify root cause for DDIC inconsistency related runtime errors

Everybody in SAP has faced with a partly active table which causes ST22 dumps in the system. Some of the Runtime Errors which is caused by ABAP object inconsistencies are listed below. As you can see most of them have a description containing DDIC string (Data Dictionary). But actually these incosistencies in data dictionary objects not only effects themselfes but also causes ABAP Program Library objects to throw Runtime Errors.

DBIF_INCL_DDIC_INCONSISTENT
DBIF_RSQL_DDIC_INCONSISTENT
DDIC_GROUP_ERROR
DDIC_ILLEGAL_KEY_COMP_NAME
DDIC_REFTYPE_INCONSISTENT
DDIC_STRUCLENG_INCONSISTENT
DDIC_TYPE_REF_ACCESS_ERROR
INCL_DDIC_INCONSISTENCY

 

In order to identify the problem and take an action, looking into ST22 log could be enough many times. But there are cases which we can not mean the real cause of these runtime errors. For such cases SAP has provided an awesome transaction named RSDDCHECK. In these report you can identify the problem according to 3 criteria.

RSDDCHECK

  • Individual Object
    You can give the table/structure name that causes the errors
  • All objects Belonging to Program or Class
    You can provide the ABAP Program/function module main program/ class
  • Runtime Errors
    You can filter with ST22 dumps according to most frequent search criteria

Executing report , all hierarchy of the provided objects will be searched and will be checked for consistency. And incorrect objects will be listed in a hierarchy tree.

 

 

You may also like

  • DYNPRO_FIELD_CONVERSION occurs in dialog screen (0)
    This type of runtime error occurs when dictionary element and screen element do not match each other. For instance you have a 5-digit length integer variable in your program and you […]
  • read table logs and extract table columns from DBTABLOG (2)
    As you may already know SAP keeps track of table content changes if you switch on 'Log Data Changes' option in table technical settings. Here you can see how to activate this small but […]
  • lock transaction just for the same user (0)
    Recently our client reported that some ABAP reports are retriggered by the same user many times which leads to memory and CPU leaks in SAP system. They have also stated that from […]