SAP CREATE_RT_CONFIG Function Module for Create Single RT Configuration
CREATE_RT_CONFIG is a standard create rt config SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Single RT Configuration 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 create rt config FM, simply by entering the name CREATE_RT_CONFIG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SRT_WSP_CONFIG_API
Program Name: SAPLSRT_WSP_CONFIG_API
Main Program: SAPLSRT_WSP_CONFIG_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CREATE_RT_CONFIG 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 'CREATE_RT_CONFIG'"Create Single RT Configuration.
EXPORTING
CONSUMER = "X=SRT Client; space=SRT Server
RT_CONFIG = "Single Runtime Configuration
EXCEPTIONS
OBJECT_EXISTS_EXCEPTION = 1 INVALID_BEHAVIOR_EXCEPTION = 2 TECHNICAL_EXCEPTION = 3
IMPORTING Parameters details for CREATE_RT_CONFIG
CONSUMER - X=SRT Client; space=SRT Server
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
RT_CONFIG - Single Runtime Configuration
Data type: SRTIF_RT_CONFIGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_EXISTS_EXCEPTION - Configuration exists already
Data type:Optional: No
Call by Reference: Yes
INVALID_BEHAVIOR_EXCEPTION - Invalid configuration
Data type:Optional: No
Call by Reference: Yes
TECHNICAL_EXCEPTION - Technical problem
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CREATE_RT_CONFIG 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_consumer | TYPE BOOLEAN, " | |||
| lv_object_exists_exception | TYPE BOOLEAN, " | |||
| lv_rt_config | TYPE SRTIF_RT_CONFIG, " | |||
| lv_invalid_behavior_exception | TYPE SRTIF_RT_CONFIG, " | |||
| lv_technical_exception | TYPE SRTIF_RT_CONFIG. " |
|   CALL FUNCTION 'CREATE_RT_CONFIG' "Create Single RT Configuration |
| EXPORTING | ||
| CONSUMER | = lv_consumer | |
| RT_CONFIG | = lv_rt_config | |
| EXCEPTIONS | ||
| OBJECT_EXISTS_EXCEPTION = 1 | ||
| INVALID_BEHAVIOR_EXCEPTION = 2 | ||
| TECHNICAL_EXCEPTION = 3 | ||
| . " CREATE_RT_CONFIG | ||
ABAP code using 7.40 inline data declarations to call FM CREATE_RT_CONFIG
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.Search for further information about these or an SAP related objects