SAP FT_MMM_DISPLAY_MARC Function Module for NOTRANSL: Außenhandel: MMM: Protokoll der Massenänderung im Materialstamm
FT_MMM_DISPLAY_MARC is a standard ft mmm display marc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Außenhandel: MMM: Protokoll der Massenänderung im Materialstamm processing and below is the pattern details for this FM, 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 ft mmm display marc FM, simply by entering the name FT_MMM_DISPLAY_MARC into the relevant SAP transaction such as SE37 or SE38.
Function Group: VFMM
Program Name: SAPLVFMM
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FT_MMM_DISPLAY_MARC 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 'FT_MMM_DISPLAY_MARC'"NOTRANSL: Außenhandel: MMM: Protokoll der Massenänderung im Materialstamm.
EXPORTING
* I_VARI = "Layout
* I_CHECKBOX = 'X' "
I_CALLBACK_PROGRAM = "Predefined Type
* I_CALLBACK_PF_STATUS = "
* I_CALLBACK_USER_COMMAND = "
* I_SHOW_MAT_KTEXT = ' ' "
TABLES
IT_MARA = "Couple of Fields Added to MARA
IT_MARC = "Field TRANC Added to MARC
* IT_SELECTION_FIELDS_MARA = "
* IT_SELECTION_FIELDS_MARC = "
ET_MARA = "Couple of Fields Added to MARA
ET_MARC = "Field TRANC Added to MARC
IMPORTING Parameters details for FT_MMM_DISPLAY_MARC
I_VARI - Layout
Data type: DISVARIANT-VARIANTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CHECKBOX -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CALLBACK_PROGRAM - Predefined Type
Data type: SY-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
I_CALLBACK_PF_STATUS -
Data type: SLIS_FORMNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CALLBACK_USER_COMMAND -
Data type: SLIS_FORMNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SHOW_MAT_KTEXT -
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FT_MMM_DISPLAY_MARC
IT_MARA - Couple of Fields Added to MARA
Data type: MARA_UEBOptional: No
Call by Reference: No ( called with pass by value option)
IT_MARC - Field TRANC Added to MARC
Data type: MARC_UEBOptional: No
Call by Reference: No ( called with pass by value option)
IT_SELECTION_FIELDS_MARA -
Data type: VFMM_SELECTION_FIELDSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SELECTION_FIELDS_MARC -
Data type: VFMM_SELECTION_FIELDSOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_MARA - Couple of Fields Added to MARA
Data type: MARA_UEBOptional: No
Call by Reference: No ( called with pass by value option)
ET_MARC - Field TRANC Added to MARC
Data type: MARC_UEBOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FT_MMM_DISPLAY_MARC 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_vari | TYPE DISVARIANT-VARIANT, " | |||
| lt_it_mara | TYPE STANDARD TABLE OF MARA_UEB, " | |||
| lt_it_marc | TYPE STANDARD TABLE OF MARC_UEB, " | |||
| lv_i_checkbox | TYPE MARC_UEB, " 'X' | |||
| lv_i_callback_program | TYPE SY-REPID, " | |||
| lt_it_selection_fields_mara | TYPE STANDARD TABLE OF VFMM_SELECTION_FIELDS, " | |||
| lv_i_callback_pf_status | TYPE SLIS_FORMNAME, " | |||
| lt_it_selection_fields_marc | TYPE STANDARD TABLE OF VFMM_SELECTION_FIELDS, " | |||
| lt_et_mara | TYPE STANDARD TABLE OF MARA_UEB, " | |||
| lv_i_callback_user_command | TYPE SLIS_FORMNAME, " | |||
| lt_et_marc | TYPE STANDARD TABLE OF MARC_UEB, " | |||
| lv_i_show_mat_ktext | TYPE MARC_UEB. " ' ' |
|   CALL FUNCTION 'FT_MMM_DISPLAY_MARC' "NOTRANSL: Außenhandel: MMM: Protokoll der Massenänderung im Materialstamm |
| EXPORTING | ||
| I_VARI | = lv_i_vari | |
| I_CHECKBOX | = lv_i_checkbox | |
| I_CALLBACK_PROGRAM | = lv_i_callback_program | |
| I_CALLBACK_PF_STATUS | = lv_i_callback_pf_status | |
| I_CALLBACK_USER_COMMAND | = lv_i_callback_user_command | |
| I_SHOW_MAT_KTEXT | = lv_i_show_mat_ktext | |
| TABLES | ||
| IT_MARA | = lt_it_mara | |
| IT_MARC | = lt_it_marc | |
| IT_SELECTION_FIELDS_MARA | = lt_it_selection_fields_mara | |
| IT_SELECTION_FIELDS_MARC | = lt_it_selection_fields_marc | |
| ET_MARA | = lt_et_mara | |
| ET_MARC | = lt_et_marc | |
| . " FT_MMM_DISPLAY_MARC | ||
ABAP code using 7.40 inline data declarations to call FM FT_MMM_DISPLAY_MARC
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.| "SELECT single VARIANT FROM DISVARIANT INTO @DATA(ld_i_vari). | ||||
| DATA(ld_i_checkbox) | = 'X'. | |||
| "SELECT single REPID FROM SY INTO @DATA(ld_i_callback_program). | ||||
| DATA(ld_i_show_mat_ktext) | = ' '. | |||
Search for further information about these or an SAP related objects