SAP DB6_DIAG_DDIC_CONSISTENCY Function Module for DB/DDIC Consistency Check









DB6_DIAG_DDIC_CONSISTENCY is a standard db6 diag ddic consistency SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DB/DDIC Consistency Check 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 db6 diag ddic consistency FM, simply by entering the name DB6_DIAG_DDIC_CONSISTENCY into the relevant SAP transaction such as SE37 or SE38.

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



Function DB6_DIAG_DDIC_CONSISTENCY 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 'DB6_DIAG_DDIC_CONSISTENCY'"DB/DDIC Consistency Check
EXPORTING
ACTION = "

IMPORTING
CHECKDATE = "SYSTEM: Current date
CHECKTIME = "SYSTEM: Time

TABLES
NODE_TAB = "Additional Information for Hierarchy Nodes

EXCEPTIONS
INVALID_PARAMETER_SET = 1
.



IMPORTING Parameters details for DB6_DIAG_DDIC_CONSISTENCY

ACTION -

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

EXPORTING Parameters details for DB6_DIAG_DDIC_CONSISTENCY

CHECKDATE - SYSTEM: Current date

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

CHECKTIME - SYSTEM: Time

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

TABLES Parameters details for DB6_DIAG_DDIC_CONSISTENCY

NODE_TAB - Additional Information for Hierarchy Nodes

Data type: SNODETEXT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_PARAMETER_SET -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for DB6_DIAG_DDIC_CONSISTENCY 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.

DATA:
lv_action  TYPE I, "   
lt_node_tab  TYPE STANDARD TABLE OF SNODETEXT, "   
lv_checkdate  TYPE SY-DATUM, "   
lv_invalid_parameter_set  TYPE SY, "   
lv_checktime  TYPE SY-UZEIT. "   

  CALL FUNCTION 'DB6_DIAG_DDIC_CONSISTENCY'  "DB/DDIC Consistency Check
    EXPORTING
         ACTION = lv_action
    IMPORTING
         CHECKDATE = lv_checkdate
         CHECKTIME = lv_checktime
    TABLES
         NODE_TAB = lt_node_tab
    EXCEPTIONS
        INVALID_PARAMETER_SET = 1
. " DB6_DIAG_DDIC_CONSISTENCY




ABAP code using 7.40 inline data declarations to call FM DB6_DIAG_DDIC_CONSISTENCY

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.

 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_checkdate).
 
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_checktime).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!