SAP Function Modules

MENU_START_MIGRATION SAP Function module







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

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


Pattern for FM MENU_START_MIGRATION - MENU START MIGRATION





CALL FUNCTION 'MENU_START_MIGRATION' "
* EXPORTING
*   single_menu_name =          " smensapmig-par_menu
*   rfc_tcode_check = SPACE     " rfcdes-rfcdest
*   no_transport = SPACE        " char1
*   get_original_only = 'X'     " char1
*   no_messages = SPACE         " char1         Single-Character Flag
*   migrate_all = SPACE         " char1         Single-Character Flag
*   xpra = SPACE                " char1         Single-Character Flag
  IMPORTING
    num_of_menus =              " i
* TABLES
*   menus_to_be_migrated =      " menu_tcode
*   migrated_menus =            " menu_tcode
*   protocol =                  " menmigprot
    .  "  MENU_START_MIGRATION

ABAP code example for Function Module MENU_START_MIGRATION





The ABAP code below is a full code listing to execute function module MENU_START_MIGRATION 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_num_of_menus  TYPE I ,
it_menus_to_be_migrated  TYPE STANDARD TABLE OF MENU_TCODE,"TABLES PARAM
wa_menus_to_be_migrated  LIKE LINE OF it_menus_to_be_migrated ,
it_migrated_menus  TYPE STANDARD TABLE OF MENU_TCODE,"TABLES PARAM
wa_migrated_menus  LIKE LINE OF it_migrated_menus ,
it_protocol  TYPE STANDARD TABLE OF MENMIGPROT,"TABLES PARAM
wa_protocol  LIKE LINE OF it_protocol .


DATA(ld_single_menu_name) = some text here

SELECT single RFCDEST
FROM RFCDES
INTO @DATA(ld_rfc_tcode_check).

DATA(ld_no_transport) = 'Check type of data required'.
DATA(ld_get_original_only) = 'Check type of data required'.
DATA(ld_no_messages) = 'Check type of data required'.
DATA(ld_migrate_all) = 'Check type of data required'.
DATA(ld_xpra) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_menus_to_be_migrated to it_menus_to_be_migrated.

"populate fields of struture and append to itab
append wa_migrated_menus to it_migrated_menus.

"populate fields of struture and append to itab
append wa_protocol to it_protocol. . CALL FUNCTION 'MENU_START_MIGRATION' * EXPORTING * single_menu_name = ld_single_menu_name * rfc_tcode_check = ld_rfc_tcode_check * no_transport = ld_no_transport * get_original_only = ld_get_original_only * no_messages = ld_no_messages * migrate_all = ld_migrate_all * xpra = ld_xpra IMPORTING num_of_menus = ld_num_of_menus * TABLES * menus_to_be_migrated = it_menus_to_be_migrated * migrated_menus = it_migrated_menus * protocol = it_protocol . " MENU_START_MIGRATION
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_num_of_menus  TYPE I ,
ld_single_menu_name  TYPE SMENSAPMIG-PAR_MENU ,
it_menus_to_be_migrated  TYPE STANDARD TABLE OF MENU_TCODE ,
wa_menus_to_be_migrated  LIKE LINE OF it_menus_to_be_migrated,
ld_rfc_tcode_check  TYPE RFCDES-RFCDEST ,
it_migrated_menus  TYPE STANDARD TABLE OF MENU_TCODE ,
wa_migrated_menus  LIKE LINE OF it_migrated_menus,
ld_no_transport  TYPE CHAR1 ,
it_protocol  TYPE STANDARD TABLE OF MENMIGPROT ,
wa_protocol  LIKE LINE OF it_protocol,
ld_get_original_only  TYPE CHAR1 ,
ld_no_messages  TYPE CHAR1 ,
ld_migrate_all  TYPE CHAR1 ,
ld_xpra  TYPE CHAR1 .


ld_single_menu_name = some text here

"populate fields of struture and append to itab
append wa_menus_to_be_migrated to it_menus_to_be_migrated.

SELECT single RFCDEST
FROM RFCDES
INTO ld_rfc_tcode_check.


"populate fields of struture and append to itab
append wa_migrated_menus to it_migrated_menus.
ld_no_transport = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_protocol to it_protocol.
ld_get_original_only = 'Check type of data required'.
ld_no_messages = 'Check type of data required'.
ld_migrate_all = 'Check type of data required'.
ld_xpra = '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 MENU_START_MIGRATION or its description.