SAP Function Modules

ME_SCR_SEND_VENDOR_MAIL SAP Function module







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

Associated Function Group: ME_SCR
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM ME_SCR_SEND_VENDOR_MAIL - ME SCR SEND VENDOR MAIL





CALL FUNCTION 'ME_SCR_SEND_VENDOR_MAIL' "
* EXPORTING
*   i_commit = SPACE            " xfeld
  IMPORTING
    et_messages =               " ldps_txt_tab
  CHANGING
    xt_vendor =                 " mescr_t_vendor
  EXCEPTIONS
    NOT_FOUND = 1               "
    NO_MESSAGE_TYPE = 2         "
    .  "  ME_SCR_SEND_VENDOR_MAIL

ABAP code example for Function Module ME_SCR_SEND_VENDOR_MAIL





The ABAP code below is a full code listing to execute function module ME_SCR_SEND_VENDOR_MAIL 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_messages  TYPE LDPS_TXT_TAB .

DATA(ld_xt_vendor) = 'Check type of data required'.
DATA(ld_i_commit) = 'Check type of data required'. . CALL FUNCTION 'ME_SCR_SEND_VENDOR_MAIL' * EXPORTING * i_commit = ld_i_commit IMPORTING et_messages = ld_et_messages CHANGING xt_vendor = ld_xt_vendor EXCEPTIONS NOT_FOUND = 1 NO_MESSAGE_TYPE = 2 . " ME_SCR_SEND_VENDOR_MAIL
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 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_xt_vendor  TYPE MESCR_T_VENDOR ,
ld_et_messages  TYPE LDPS_TXT_TAB ,
ld_i_commit  TYPE XFELD .

ld_xt_vendor = 'Check type of data required'.
ld_i_commit = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name ME_SCR_SEND_VENDOR_MAIL or its description.