SAP CUD9_CONFIGURATION_EXECUTE Function Module for NOTRANSL: Aufruf Konfigurator auf Workstation
CUD9_CONFIGURATION_EXECUTE is a standard cud9 configuration execute SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Aufruf Konfigurator auf Workstation 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 cud9 configuration execute FM, simply by entering the name CUD9_CONFIGURATION_EXECUTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUD9
Program Name: SAPLCUD9
Main Program: SAPLCUD9
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUD9_CONFIGURATION_EXECUTE 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 'CUD9_CONFIGURATION_EXECUTE'"NOTRANSL: Aufruf Konfigurator auf Workstation.
EXPORTING
CUD9_KNOWLEDGE_BASE = "Master data
* CUD9_LANGUAGE_INTERFACE = SY-LANGU "Language
CUD9_PATH_WS = "Path for program and files
* CUD9_FILETYPE_WS = 'ASC' "File format
* CUD9_FILE_DIRECT = ' ' "
TABLES
CONFIGURATION_DATA = "Table for configuration data_
EXCEPTIONS
CONVERSION_ERROR = 1 NO_BATCH = 10 PROG_NOT_FOUND = 11 UNKNOWN_ERROR = 12 FILE_OPEN_ERROR = 2 FILE_READ_ERROR = 3 FILE_WRITE_ERROR = 4 FRONTEND_ERROR = 5 ILLEGAL_OPTION = 6 INVALID_FILESIZE = 7 INVALID_TABLE_WIDTH = 8 INVALID_TYPE = 9
IMPORTING Parameters details for CUD9_CONFIGURATION_EXECUTE
CUD9_KNOWLEDGE_BASE - Master data
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
CUD9_LANGUAGE_INTERFACE - Language
Data type: T002-SPRASDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
CUD9_PATH_WS - Path for program and files
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
CUD9_FILETYPE_WS - File format
Data type: RLGRAP-FILETYPEDefault: 'ASC'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CUD9_FILE_DIRECT -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CUD9_CONFIGURATION_EXECUTE
CONFIGURATION_DATA - Table for configuration data_
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CONVERSION_ERROR - Conversion error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_BATCH - Batch processing not allowed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROG_NOT_FOUND - Program not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_ERROR - Unknown error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FILE_OPEN_ERROR - Error opening file
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FILE_READ_ERROR - Error reading file
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FILE_WRITE_ERROR - Error saving file
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FRONTEND_ERROR - Frontend error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_OPTION - Invalid option
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_FILESIZE - Invalid file size
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_TABLE_WIDTH - Invalid table width
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_TYPE - Invalid file format
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUD9_CONFIGURATION_EXECUTE 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_conversion_error | TYPE STRING, " | |||
| lt_configuration_data | TYPE STANDARD TABLE OF STRING, " | |||
| lv_cud9_knowledge_base | TYPE C, " | |||
| lv_no_batch | TYPE C, " | |||
| lv_prog_not_found | TYPE C, " | |||
| lv_unknown_error | TYPE C, " | |||
| lv_file_open_error | TYPE C, " | |||
| lv_cud9_language_interface | TYPE T002-SPRAS, " SY-LANGU | |||
| lv_cud9_path_ws | TYPE C, " | |||
| lv_file_read_error | TYPE C, " | |||
| lv_cud9_filetype_ws | TYPE RLGRAP-FILETYPE, " 'ASC' | |||
| lv_file_write_error | TYPE RLGRAP, " | |||
| lv_frontend_error | TYPE RLGRAP, " | |||
| lv_cud9_file_direct | TYPE C, " SPACE | |||
| lv_illegal_option | TYPE C, " | |||
| lv_invalid_filesize | TYPE C, " | |||
| lv_invalid_table_width | TYPE C, " | |||
| lv_invalid_type | TYPE C. " |
|   CALL FUNCTION 'CUD9_CONFIGURATION_EXECUTE' "NOTRANSL: Aufruf Konfigurator auf Workstation |
| EXPORTING | ||
| CUD9_KNOWLEDGE_BASE | = lv_cud9_knowledge_base | |
| CUD9_LANGUAGE_INTERFACE | = lv_cud9_language_interface | |
| CUD9_PATH_WS | = lv_cud9_path_ws | |
| CUD9_FILETYPE_WS | = lv_cud9_filetype_ws | |
| CUD9_FILE_DIRECT | = lv_cud9_file_direct | |
| TABLES | ||
| CONFIGURATION_DATA | = lt_configuration_data | |
| EXCEPTIONS | ||
| CONVERSION_ERROR = 1 | ||
| NO_BATCH = 10 | ||
| PROG_NOT_FOUND = 11 | ||
| UNKNOWN_ERROR = 12 | ||
| FILE_OPEN_ERROR = 2 | ||
| FILE_READ_ERROR = 3 | ||
| FILE_WRITE_ERROR = 4 | ||
| FRONTEND_ERROR = 5 | ||
| ILLEGAL_OPTION = 6 | ||
| INVALID_FILESIZE = 7 | ||
| INVALID_TABLE_WIDTH = 8 | ||
| INVALID_TYPE = 9 | ||
| . " CUD9_CONFIGURATION_EXECUTE | ||
ABAP code using 7.40 inline data declarations to call FM CUD9_CONFIGURATION_EXECUTE
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 SPRAS FROM T002 INTO @DATA(ld_cud9_language_interface). | ||||
| DATA(ld_cud9_language_interface) | = SY-LANGU. | |||
| "SELECT single FILETYPE FROM RLGRAP INTO @DATA(ld_cud9_filetype_ws). | ||||
| DATA(ld_cud9_filetype_ws) | = 'ASC'. | |||
| DATA(ld_cud9_file_direct) | = ' '. | |||
Search for further information about these or an SAP related objects