SAP CRS_READ_DNL_PARAMS Function Module for
CRS_READ_DNL_PARAMS is a standard crs read dnl params 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 crs read dnl params FM, simply by entering the name CRS_READ_DNL_PARAMS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM0
Program Name: SAPLCRM0
Main Program: SAPLCRM0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRS_READ_DNL_PARAMS 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 'CRS_READ_DNL_PARAMS'".
EXPORTING
I_OBJ_NAME = "
* I_STSHD = "
* I_REM_LOGSYS = "
I_DWNLOADTYPE = "
* I_DESTINATION = "
* I_RFC_QUEUE = "
* I_BAPINAME = "
* I_INFO = "
* I_CONSUMER = "
* I_BAPICRMDH2 = "
* I_TRANSFER_DATA = "
CHANGING
* E_USREXIT_OFF = "
* E_SERVER_REL = "
* E_SYNCHRONOUS_CALL = "
* E_INTERFACE_REL = "
* E_MASS_QUEUE = "
TABLES
* T_RFCDEST = "
* TI_BAPIMTCS = "
IMPORTING Parameters details for CRS_READ_DNL_PARAMS
I_OBJ_NAME -
Data type: BAPICRMOBJ-OBJ_NAMEOptional: No
Call by Reference: Yes
I_STSHD -
Data type: CRM_STSHDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REM_LOGSYS -
Data type: CRMRFCPAR-REM_LOGSYSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DWNLOADTYPE -
Data type: BAPICRMDH2-DWNLOADTYPOptional: No
Call by Reference: Yes
I_DESTINATION -
Data type: BAPICRMDH1-RFCSERVEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_RFC_QUEUE -
Data type: BAPICRMDH1-RFC_QUEUEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BAPINAME -
Data type: CRMRFCPAR-BAPINAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_INFO -
Data type: CRMRFCPAR-INFOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CONSUMER -
Data type: CRMCONSUM-CONSUMEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_BAPICRMDH2 -
Data type: BAPICRMDH2Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TRANSFER_DATA -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for CRS_READ_DNL_PARAMS
E_USREXIT_OFF -
Data type: CRMPAROLTP-PARVAL1Optional: Yes
Call by Reference: Yes
E_SERVER_REL -
Data type: BAPICRMDH1-SERVER_RELOptional: Yes
Call by Reference: Yes
E_SYNCHRONOUS_CALL -
Data type: CRMPAROLTP-PARVAL1Optional: Yes
Call by Reference: Yes
E_INTERFACE_REL -
Data type: BAPICRMDH2-SEND_IFRELOptional: Yes
Call by Reference: Yes
E_MASS_QUEUE -
Data type: CRMRFCPAR-RFC_IN_QUEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CRS_READ_DNL_PARAMS
T_RFCDEST -
Data type: CRMRFCPAROptional: Yes
Call by Reference: No ( called with pass by value option)
TI_BAPIMTCS -
Data type: BAPIMTCSOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CRS_READ_DNL_PARAMS 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_t_rfcdest | TYPE STANDARD TABLE OF CRMRFCPAR, " | |||
lv_i_obj_name | TYPE BAPICRMOBJ-OBJ_NAME, " | |||
lv_e_usrexit_off | TYPE CRMPAROLTP-PARVAL1, " | |||
lv_i_stshd | TYPE CRM_STSHD, " | |||
lv_i_rem_logsys | TYPE CRMRFCPAR-REM_LOGSYS, " | |||
lt_ti_bapimtcs | TYPE STANDARD TABLE OF BAPIMTCS, " | |||
lv_e_server_rel | TYPE BAPICRMDH1-SERVER_REL, " | |||
lv_i_dwnloadtype | TYPE BAPICRMDH2-DWNLOADTYP, " | |||
lv_i_destination | TYPE BAPICRMDH1-RFCSERVER, " | |||
lv_e_synchronous_call | TYPE CRMPAROLTP-PARVAL1, " | |||
lv_i_rfc_queue | TYPE BAPICRMDH1-RFC_QUEUE, " | |||
lv_e_interface_rel | TYPE BAPICRMDH2-SEND_IFREL, " | |||
lv_i_bapiname | TYPE CRMRFCPAR-BAPINAME, " | |||
lv_e_mass_queue | TYPE CRMRFCPAR-RFC_IN_QUE, " | |||
lv_i_info | TYPE CRMRFCPAR-INFO, " | |||
lv_i_consumer | TYPE CRMCONSUM-CONSUMER, " | |||
lv_i_bapicrmdh2 | TYPE BAPICRMDH2, " | |||
lv_i_transfer_data | TYPE BAPICRMDH2. " |
  CALL FUNCTION 'CRS_READ_DNL_PARAMS' " |
EXPORTING | ||
I_OBJ_NAME | = lv_i_obj_name | |
I_STSHD | = lv_i_stshd | |
I_REM_LOGSYS | = lv_i_rem_logsys | |
I_DWNLOADTYPE | = lv_i_dwnloadtype | |
I_DESTINATION | = lv_i_destination | |
I_RFC_QUEUE | = lv_i_rfc_queue | |
I_BAPINAME | = lv_i_bapiname | |
I_INFO | = lv_i_info | |
I_CONSUMER | = lv_i_consumer | |
I_BAPICRMDH2 | = lv_i_bapicrmdh2 | |
I_TRANSFER_DATA | = lv_i_transfer_data | |
CHANGING | ||
E_USREXIT_OFF | = lv_e_usrexit_off | |
E_SERVER_REL | = lv_e_server_rel | |
E_SYNCHRONOUS_CALL | = lv_e_synchronous_call | |
E_INTERFACE_REL | = lv_e_interface_rel | |
E_MASS_QUEUE | = lv_e_mass_queue | |
TABLES | ||
T_RFCDEST | = lt_t_rfcdest | |
TI_BAPIMTCS | = lt_ti_bapimtcs | |
. " CRS_READ_DNL_PARAMS |
ABAP code using 7.40 inline data declarations to call FM CRS_READ_DNL_PARAMS
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 OBJ_NAME FROM BAPICRMOBJ INTO @DATA(ld_i_obj_name). | ||||
"SELECT single PARVAL1 FROM CRMPAROLTP INTO @DATA(ld_e_usrexit_off). | ||||
"SELECT single REM_LOGSYS FROM CRMRFCPAR INTO @DATA(ld_i_rem_logsys). | ||||
"SELECT single SERVER_REL FROM BAPICRMDH1 INTO @DATA(ld_e_server_rel). | ||||
"SELECT single DWNLOADTYP FROM BAPICRMDH2 INTO @DATA(ld_i_dwnloadtype). | ||||
"SELECT single RFCSERVER FROM BAPICRMDH1 INTO @DATA(ld_i_destination). | ||||
"SELECT single PARVAL1 FROM CRMPAROLTP INTO @DATA(ld_e_synchronous_call). | ||||
"SELECT single RFC_QUEUE FROM BAPICRMDH1 INTO @DATA(ld_i_rfc_queue). | ||||
"SELECT single SEND_IFREL FROM BAPICRMDH2 INTO @DATA(ld_e_interface_rel). | ||||
"SELECT single BAPINAME FROM CRMRFCPAR INTO @DATA(ld_i_bapiname). | ||||
"SELECT single RFC_IN_QUE FROM CRMRFCPAR INTO @DATA(ld_e_mass_queue). | ||||
"SELECT single INFO FROM CRMRFCPAR INTO @DATA(ld_i_info). | ||||
"SELECT single CONSUMER FROM CRMCONSUM INTO @DATA(ld_i_consumer). | ||||
Search for further information about these or an SAP related objects