SAP RKD_DEPENDANCY_CHECK Function Module for
RKD_DEPENDANCY_CHECK is a standard rkd dependancy check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rkd dependancy check FM, simply by entering the name RKD_DEPENDANCY_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: KYP3
Program Name: SAPLKYP3
Main Program: SAPLKYP3
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RKD_DEPENDANCY_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 'RKD_DEPENDANCY_CHECK'".
EXPORTING
* I_MESSAGE_TYPE = 'S' "
* I_MODE = '1' "
I_APPLCLASS = "
I_RKB1F = "
I_RKB1X = "
* I_TABNAME = ' ' "
* I_TS_VRANGE = "
TABLES
* ADD_SEL_TAB = "
COTRL_TAB = "Control data table
DYNP_ERROR = "Table of the incorrect lines on the screen
FDEP_TAB = "
FIELD_TAB = "
FORM_TAB = "Row/column structure table
SEIG = "
VAR_TAB = "Variable table
IMPORTING Parameters details for RKD_DEPENDANCY_CHECK
I_MESSAGE_TYPE -
Data type: SY-MSGTYDefault: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MODE -
Data type: CDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_APPLCLASS -
Data type: RKB1D-APPLCLASSOptional: No
Call by Reference: No ( called with pass by value option)
I_RKB1F -
Data type: RKB1FOptional: No
Call by Reference: No ( called with pass by value option)
I_RKB1X -
Data type: RKB1XOptional: No
Call by Reference: No ( called with pass by value option)
I_TABNAME -
Data type: RKB1D-TABNAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TS_VRANGE -
Data type: RKD_TS_VRANGEOptional: Yes
Call by Reference: Yes
TABLES Parameters details for RKD_DEPENDANCY_CHECK
ADD_SEL_TAB -
Data type: CEDSTOptional: Yes
Call by Reference: No ( called with pass by value option)
COTRL_TAB - Control data table
Data type: CFBCD01Optional: No
Call by Reference: No ( called with pass by value option)
DYNP_ERROR - Table of the incorrect lines on the screen
Data type: CFBDE01Optional: No
Call by Reference: No ( called with pass by value option)
FDEP_TAB -
Data type: CDIDEPOptional: No
Call by Reference: No ( called with pass by value option)
FIELD_TAB -
Data type: CDIFIEOptional: No
Call by Reference: No ( called with pass by value option)
FORM_TAB - Row/column structure table
Data type: CFBFO01Optional: No
Call by Reference: No ( called with pass by value option)
SEIG -
Data type: CFBSE01Optional: No
Call by Reference: No ( called with pass by value option)
VAR_TAB - Variable table
Data type: CFBVP01Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RKD_DEPENDANCY_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.| DATA: | ||||
| lt_add_sel_tab | TYPE STANDARD TABLE OF CEDST, " | |||
| lv_i_message_type | TYPE SY-MSGTY, " 'S' | |||
| lv_i_mode | TYPE C, " '1' | |||
| lt_cotrl_tab | TYPE STANDARD TABLE OF CFBCD01, " | |||
| lt_dynp_error | TYPE STANDARD TABLE OF CFBDE01, " | |||
| lv_i_applclass | TYPE RKB1D-APPLCLASS, " | |||
| lv_i_rkb1f | TYPE RKB1F, " | |||
| lt_fdep_tab | TYPE STANDARD TABLE OF CDIDEP, " | |||
| lv_i_rkb1x | TYPE RKB1X, " | |||
| lt_field_tab | TYPE STANDARD TABLE OF CDIFIE, " | |||
| lt_form_tab | TYPE STANDARD TABLE OF CFBFO01, " | |||
| lv_i_tabname | TYPE RKB1D-TABNAME, " SPACE | |||
| lt_seig | TYPE STANDARD TABLE OF CFBSE01, " | |||
| lv_i_ts_vrange | TYPE RKD_TS_VRANGE, " | |||
| lt_var_tab | TYPE STANDARD TABLE OF CFBVP01. " |
|   CALL FUNCTION 'RKD_DEPENDANCY_CHECK' " |
| EXPORTING | ||
| I_MESSAGE_TYPE | = lv_i_message_type | |
| I_MODE | = lv_i_mode | |
| I_APPLCLASS | = lv_i_applclass | |
| I_RKB1F | = lv_i_rkb1f | |
| I_RKB1X | = lv_i_rkb1x | |
| I_TABNAME | = lv_i_tabname | |
| I_TS_VRANGE | = lv_i_ts_vrange | |
| TABLES | ||
| ADD_SEL_TAB | = lt_add_sel_tab | |
| COTRL_TAB | = lt_cotrl_tab | |
| DYNP_ERROR | = lt_dynp_error | |
| FDEP_TAB | = lt_fdep_tab | |
| FIELD_TAB | = lt_field_tab | |
| FORM_TAB | = lt_form_tab | |
| SEIG | = lt_seig | |
| VAR_TAB | = lt_var_tab | |
| . " RKD_DEPENDANCY_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RKD_DEPENDANCY_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.| "SELECT single MSGTY FROM SY INTO @DATA(ld_i_message_type). | ||||
| DATA(ld_i_message_type) | = 'S'. | |||
| DATA(ld_i_mode) | = '1'. | |||
| "SELECT single APPLCLASS FROM RKB1D INTO @DATA(ld_i_applclass). | ||||
| "SELECT single TABNAME FROM RKB1D INTO @DATA(ld_i_tabname). | ||||
| DATA(ld_i_tabname) | = ' '. | |||
Search for further information about these or an SAP related objects