RMXT231_BADI_ADD_CLASS_DEF SAP Function module

RMXT231_BADI_ADD_CLASS_DEF 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 RMXT231_BADI_ADD_CLASS_DEF into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RMXT231
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RMXT231_BADI_ADD_CLASS_DEF - RMXT231 BADI ADD CLASS DEF

CALL FUNCTION 'RMXT231_BADI_ADD_CLASS_DEF' "
  EXPORTING
    i_appl_context =            " ehsbe_vai_appl_context
    i_subscreen =               " sydynnr
    it_class_def =              " ehsbty_api_vai_class_def
  IMPORTING
    et_class_def =              " ehsbty_api_vai_class_def
    e_flg_error =               " esp1_boolean
  CHANGING
    xo_data_container =         " cl_rmxt_pp_data_container
    .  "  RMXT231_BADI_ADD_CLASS_DEF

ABAP code example for Function Module RMXT231_BADI_ADD_CLASS_DEF

The ABAP code below is a full code listing to execute function module RMXT231_BADI_ADD_CLASS_DEF 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_et_class_def  
 
 TYPE EHSBTY_API_VAI_CLASS_DEF
,
ld_e_flg_error  
 
 TYPE ESP1_BOOLEAN
.


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

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

DATA(ld_i_subscreen) = 'some text here'.

DATA(ld_it_class_def) = 'some text here'.
.

CALL FUNCTION 'RMXT231_BADI_ADD_CLASS_DEF'
  EXPORTING
    i_appl_context =             ld_i_appl_context
    i_subscreen =                ld_i_subscreen
    it_class_def =               ld_it_class_def
  IMPORTING
    et_class_def =               ld_et_class_def
    e_flg_error =                ld_e_flg_error
  CHANGING
    xo_data_container =          ld_xo_data_container
    .  "  RMXT231_BADI_ADD_CLASS_DEF

IF SY-SUBRC EQ 0.
  "All OK
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_xo_data_container
 
 TYPE CL_RMXT_PP_DATA_CONTAINER ,
ld_et_class_def
 
 TYPE EHSBTY_API_VAI_CLASS_DEF ,
ld_i_appl_context
 
 TYPE EHSBE_VAI_APPL_CONTEXT ,
ld_e_flg_error
 
 TYPE ESP1_BOOLEAN ,
ld_i_subscreen
 
 TYPE SYDYNNR ,
ld_it_class_def
 
 TYPE EHSBTY_API_VAI_CLASS_DEF .


ld_xo_data_container = 'some text here'.
ld_i_appl_context = 'some text here'.
ld_i_subscreen = 'some text here'.
ld_it_class_def = 'some text here'.