CLM_UTL_REMOVE_MA_COMMENTS SAP Function module

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

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

Pattern for FM CLM_UTL_REMOVE_MA_COMMENTS - CLM UTL REMOVE MA COMMENTS

CALL FUNCTION 'CLM_UTL_REMOVE_MA_COMMENTS' "
  EXPORTING
    obj_type =                  " trobjtype     Object Type
    obj_name =                  " eu_aname      ABAP/4 Development Workbench: TADIR name
    sub_type =                  " trobjtype     Object Type
    sub_name =                  " eu_lname      ABAP/4 Development Workbench: LIMU name
    do_db_changes =             " char1
  IMPORTING
    return_code =               " char1
  EXCEPTIONS
    NOT_FOUND = 1               "               Object Not Found
    ERROR_OCCURED = 2           "               Error during Remove
    ENQUEUE_ERROR = 3           "               Locking Error
    WRONG_TYPE = 4              "
    .  "  CLM_UTL_REMOVE_MA_COMMENTS

ABAP code example for Function Module CLM_UTL_REMOVE_MA_COMMENTS

The ABAP code below is a full code listing to execute function module CLM_UTL_REMOVE_MA_COMMENTS 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_return_code  
 
 TYPE CHAR1
.


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

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

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

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

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

CALL FUNCTION 'CLM_UTL_REMOVE_MA_COMMENTS'
  EXPORTING
    obj_type =                   ld_obj_type
    obj_name =                   ld_obj_name
    sub_type =                   ld_sub_type
    sub_name =                   ld_sub_name
    do_db_changes =              ld_do_db_changes
  IMPORTING
    return_code =                ld_return_code
  EXCEPTIONS
    NOT_FOUND =                  1
    ERROR_OCCURED =              2
    ENQUEUE_ERROR =              3
    WRONG_TYPE =                 4
    .  "  CLM_UTL_REMOVE_MA_COMMENTS

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_return_code
 
 TYPE CHAR1 ,
ld_obj_type
 
 TYPE TROBJTYPE ,
ld_obj_name
 
 TYPE EU_ANAME ,
ld_sub_type
 
 TYPE TROBJTYPE ,
ld_sub_name
 
 TYPE EU_LNAME ,
ld_do_db_changes
 
 TYPE CHAR1 .


ld_obj_type = 'Check type of data required'.
ld_obj_name = 'Check type of data required'.
ld_sub_type = 'Check type of data required'.
ld_sub_name = 'Check type of data required'.
ld_do_db_changes = 'Check type of data required'.