UPDATE_RT_CONFIG SAP Function module - Modify RT Configuration

UPDATE_RT_CONFIG is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name UPDATE_RT_CONFIG into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SRT_WSP_CONFIG_API
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM UPDATE_RT_CONFIG - UPDATE RT CONFIG

CALL FUNCTION 'UPDATE_RT_CONFIG' "Modify RT Configuration
  EXPORTING
    consumer =                  " boolean       Boolean Variable (X=True, -=False, Space=Unknown)
    rt_config =                 " srtif_rt_config  Single Runtime Configuration
  EXCEPTIONS
    OBJECT_NOT_EXISTS_EXCEPTION = 1  "          Object does not exist
    OBJECT_NOT_LOCKED_EXCEPTION = 2  "          Object is not locked
    TECHNICAL_EXCEPTION = 3     "               Technical error
    INVALID_BEHAVIOR_EXCEPTION = 4  "           Invalid runtime configuration
    .  "  UPDATE_RT_CONFIG

ABAP code example for Function Module UPDATE_RT_CONFIG

The ABAP code below is a full code listing to execute function module UPDATE_RT_CONFIG including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_consumer) = 'Check type of data required'.

DATA(ld_rt_config) = 'Check type of data required'.
.

CALL FUNCTION 'UPDATE_RT_CONFIG'
  EXPORTING
    consumer =                   ld_consumer
    rt_config =                  ld_rt_config
  EXCEPTIONS
    OBJECT_NOT_EXISTS_EXCEPTION =    1
    OBJECT_NOT_LOCKED_EXCEPTION =    2
    TECHNICAL_EXCEPTION =        3
    INVALID_BEHAVIOR_EXCEPTION =    4
    .  "  UPDATE_RT_CONFIG

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_consumer
 
 TYPE BOOLEAN ,
ld_rt_config
 
 TYPE SRTIF_RT_CONFIG .


ld_consumer = 'Check type of data required'.
ld_rt_config = 'Check type of data required'.