SAP DD_DB_CONSISTENCY_CHECK Function Module for Test for Consistency Checks

Search SAP Function Modules

DD_DB_CONSISTENCY_CHECK is a standard dd db consistency check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Test for Consistency Checks processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for dd db consistency check FM, simply by entering the name DD_DB_CONSISTENCY_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDB5
Program Name: SAPLSDB5
Main Program: SAPLSDB5
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DD_DB_CONSISTENCY_CHECK pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'DD_DB_CONSISTENCY_CHECK'"Test for Consistency Checks
  EXPORTING
*  UNIQUE_IND_CHECK = ' ' "Find only tables without primary key
*  MISSING_IND_DISP = ' ' "Display missing indexes (from MONI)
*  MISSING_IND_COMP = ' ' "Compute missing indexes (in MONI)

 IMPORTING
   NO_DBTABLES =  "No. of tables missing on the DB
   NO_SAPTABLES =  "No. of unknown tables in the dictionary
   NO_DBINDICES =  "No. of indexes missing on the DB
   NO_SAPINDICES =  "No. of unknown indexes in the dictionary

TABLES
*  MISS_INDEX =  "Indexes missing on the DB
*  ADDTL_INDEX =  "Additional indexes on the DB

.

IMPORTING Parameters details for DD_DB_CONSISTENCY_CHECK

UNIQUE_IND_CHECK - Find only tables without primary key

Data type: DDREFSTRUC-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MISSING_IND_DISP - Display missing indexes (from MONI)

Data type: DDREFSTRUC-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MISSING_IND_COMP - Compute missing indexes (in MONI)

Data type: DDREFSTRUC-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for DD_DB_CONSISTENCY_CHECK

NO_DBTABLES - No. of tables missing on the DB

Data type: MONI_CHECK-DBTABLES
Optional: No
Call by Reference: No ( called with pass by value option)

NO_SAPTABLES - No. of unknown tables in the dictionary

Data type: MONI_CHECK-SAPTABLES
Optional: No
Call by Reference: No ( called with pass by value option)

NO_DBINDICES - No. of indexes missing on the DB

Data type: MONI_CHECK-DBINDICES
Optional: No
Call by Reference: No ( called with pass by value option)

NO_SAPINDICES - No. of unknown indexes in the dictionary

Data type: MONI_CHECK-SAPINDICES
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for DD_DB_CONSISTENCY_CHECK

MISS_INDEX - Indexes missing on the DB

Data type: MISSOBJ
Optional: Yes
Call by Reference: No ( called with pass by value option)

ADDTL_INDEX - Additional indexes on the DB

Data type: MISSOBJ
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DD_DB_CONSISTENCY_CHECK Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM DD_DB_CONSISTENCY_CHECK

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects