SAP MI_MSD_CHECK_STRING_OF_CODE Function Module for









MI_MSD_CHECK_STRING_OF_CODE is a standard mi msd check string of code SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 mi msd check string of code FM, simply by entering the name MI_MSD_CHECK_STRING_OF_CODE into the relevant SAP transaction such as SE37 or SE38.

Function Group: ME_MSD_TOOLS
Program Name: SAPLME_MSD_TOOLS
Main Program: SAPLME_MSD_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MI_MSD_CHECK_STRING_OF_CODE 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 'MI_MSD_CHECK_STRING_OF_CODE'"
  EXPORTING
   I_NAME' ' =  "
   I_NAME =  "
   I_VERSION =  "

EXCEPTIONS
   NAMESPACE_ILLEGAL = 1    NAME_ILLEGAL = 2    VERSION_ILLEGAL = 3    NO_VALUES_DELIVERED = 4
.



IMPORTING Parameters details for MI_MSD_CHECK_STRING_OF_CODE

I_NAMESPACE -

Data type: NAMESPACE
Optional: No
Call by Reference: Yes

I_NAME -

Data type: MSDNAME
Optional: No
Call by Reference: Yes

I_VERSION -

Data type: BWAFVERS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NAMESPACE_ILLEGAL -

Data type:
Optional: No
Call by Reference: Yes

NAME_ILLEGAL -

Data type:
Optional: No
Call by Reference: Yes

VERSION_ILLEGAL -

Data type:
Optional: No
Call by Reference: Yes

NO_VALUES_DELIVERED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MI_MSD_CHECK_STRING_OF_CODE 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_i_namespace  TYPE NAMESPACE, "   
lv_namespace_illegal  TYPE NAMESPACE, "   
lv_i_name  TYPE MSDNAME, "   
lv_name_illegal  TYPE MSDNAME, "   
lv_i_version  TYPE BWAFVERS, "   
lv_version_illegal  TYPE BWAFVERS, "   
lv_no_values_delivered  TYPE BWAFVERS. "   

  CALL FUNCTION 'MI_MSD_CHECK_STRING_OF_CODE'  "
    EXPORTING
         I_NAMESPACE = lv_i_namespace
         I_NAME = lv_i_name
         I_VERSION = lv_i_version
    EXCEPTIONS
        NAMESPACE_ILLEGAL = 1
        NAME_ILLEGAL = 2
        VERSION_ILLEGAL = 3
        NO_VALUES_DELIVERED = 4
. " MI_MSD_CHECK_STRING_OF_CODE




ABAP code using 7.40 inline data declarations to call FM MI_MSD_CHECK_STRING_OF_CODE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!