SAP /SDF/CD_CC_CONNECT_API_LOAD Function Module for Code Connect: Load external result
/SDF/CD_CC_CONNECT_API_LOAD is a standard /sdf/cd cc connect api load SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Code Connect: Load external result 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 /sdf/cd cc connect api load FM, simply by entering the name /SDF/CD_CC_CONNECT_API_LOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: /SDF/CD_CUST_CODE_CONNECT
Program Name: /SDF/SAPLCD_CUST_CODE_CONNECT
Main Program: /SDF/SAPLCD_CUST_CODE_CONNECT
Appliation area:
Release date: 17-Dec-2009
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /SDF/CD_CC_CONNECT_API_LOAD 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 '/SDF/CD_CC_CONNECT_API_LOAD'"Code Connect: Load external result.
EXPORTING
IV_ANALYSIS_MODE = "
* IV_RUN_ID = '/0SAP/SERVICE_RUN' "
* IV_FLG_ONLY_RUN_PARAM = "
* IV_FLG_INCL_NO_REF = "
IMPORTING
ET_PARAMS = "
EV_RUN_DATE = "
EV_RUN_TIME = "
ET_CONNECT_RESULT = "
EV_MESSAGE = "
EV_RC = "
IMPORTING Parameters details for /SDF/CD_CC_CONNECT_API_LOAD
IV_ANALYSIS_MODE -
Data type: /SDF/CD_CC_MODE_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_RUN_ID -
Data type: /SDF/CD_CC_RUN_IDDefault: '/0SAP/SERVICE_RUN'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_FLG_ONLY_RUN_PARAM -
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_FLG_INCL_NO_REF -
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for /SDF/CD_CC_CONNECT_API_LOAD
ET_PARAMS -
Data type: RSPARAMS_TTOptional: No
Call by Reference: No ( called with pass by value option)
EV_RUN_DATE -
Data type: SYDATUMOptional: No
Call by Reference: No ( called with pass by value option)
EV_RUN_TIME -
Data type: SYUZEITOptional: No
Call by Reference: No ( called with pass by value option)
ET_CONNECT_RESULT -
Data type: /SDF/CD_CC_CONNECT_RESULT_TOptional: No
Call by Reference: No ( called with pass by value option)
EV_MESSAGE -
Data type: CHAR100SMOptional: No
Call by Reference: No ( called with pass by value option)
EV_RC -
Data type: SYSUBRCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /SDF/CD_CC_CONNECT_API_LOAD 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_et_params | TYPE RSPARAMS_TT, " | |||
| lv_iv_analysis_mode | TYPE /SDF/CD_CC_MODE_ID, " | |||
| lv_iv_run_id | TYPE /SDF/CD_CC_RUN_ID, " '/0SAP/SERVICE_RUN' | |||
| lv_ev_run_date | TYPE SYDATUM, " | |||
| lv_ev_run_time | TYPE SYUZEIT, " | |||
| lv_iv_flg_only_run_param | TYPE CHAR1, " | |||
| lv_et_connect_result | TYPE /SDF/CD_CC_CONNECT_RESULT_T, " | |||
| lv_iv_flg_incl_no_ref | TYPE CHAR1, " | |||
| lv_ev_message | TYPE CHAR100SM, " | |||
| lv_ev_rc | TYPE SYSUBRC. " |
|   CALL FUNCTION '/SDF/CD_CC_CONNECT_API_LOAD' "Code Connect: Load external result |
| EXPORTING | ||
| IV_ANALYSIS_MODE | = lv_iv_analysis_mode | |
| IV_RUN_ID | = lv_iv_run_id | |
| IV_FLG_ONLY_RUN_PARAM | = lv_iv_flg_only_run_param | |
| IV_FLG_INCL_NO_REF | = lv_iv_flg_incl_no_ref | |
| IMPORTING | ||
| ET_PARAMS | = lv_et_params | |
| EV_RUN_DATE | = lv_ev_run_date | |
| EV_RUN_TIME | = lv_ev_run_time | |
| ET_CONNECT_RESULT | = lv_et_connect_result | |
| EV_MESSAGE | = lv_ev_message | |
| EV_RC | = lv_ev_rc | |
| . " /SDF/CD_CC_CONNECT_API_LOAD | ||
ABAP code using 7.40 inline data declarations to call FM /SDF/CD_CC_CONNECT_API_LOAD
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.| DATA(ld_iv_run_id) | = '/0SAP/SERVICE_RUN'. | |||
Search for further information about these or an SAP related objects