MI_MSD_CHECK_STRING_OF_CODE SAP Function module

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

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

Pattern for FM MI_MSD_CHECK_STRING_OF_CODE - MI MSD CHECK STRING OF CODE

CALL FUNCTION 'MI_MSD_CHECK_STRING_OF_CODE' "
  EXPORTING
    i_namespace =               " namespace
    i_name =                    " msdname
    i_version =                 " bwafvers
  EXCEPTIONS
    NAMESPACE_ILLEGAL = 1       "
    NAME_ILLEGAL = 2            "
    VERSION_ILLEGAL = 3         "
    NO_VALUES_DELIVERED = 4     "
    .  "  MI_MSD_CHECK_STRING_OF_CODE

ABAP code example for Function Module MI_MSD_CHECK_STRING_OF_CODE

The ABAP code below is a full code listing to execute function module MI_MSD_CHECK_STRING_OF_CODE 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_i_namespace) = 'Check type of data required'.

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

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

CALL FUNCTION 'MI_MSD_CHECK_STRING_OF_CODE'
  EXPORTING
    i_namespace =                ld_i_namespace
    i_name =                     ld_i_name
    i_version =                  ld_i_version
  EXCEPTIONS
    NAMESPACE_ILLEGAL =          1
    NAME_ILLEGAL =               2
    VERSION_ILLEGAL =            3
    NO_VALUES_DELIVERED =        4
    .  "  MI_MSD_CHECK_STRING_OF_CODE

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_i_namespace
 
 TYPE NAMESPACE ,
ld_i_name
 
 TYPE MSDNAME ,
ld_i_version
 
 TYPE BWAFVERS .


ld_i_namespace = 'Check type of data required'.
ld_i_name = 'Check type of data required'.
ld_i_version = 'Check type of data required'.