SAP MARC_MD_SINGLE_READ Function Module for DE-EN-LANG-SWITCH-NO-TRANSLATION
MARC_MD_SINGLE_READ is a standard marc md single read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DE-EN-LANG-SWITCH-NO-TRANSLATION 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 marc md single read FM, simply by entering the name MARC_MD_SINGLE_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: MG22
Program Name: SAPLMG22
Main Program: SAPLMG22
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MARC_MD_SINGLE_READ 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 'MARC_MD_SINGLE_READ'"DE-EN-LANG-SWITCH-NO-TRANSLATION.
EXPORTING
* KZRFB = ' ' "Indicator: Refresh Buffer Entry
* MAXTZ = 0 "Max. No. of Entries in Buffer
MATNR = "
WERKS = "
* SPERRMODUS = ' ' "Lock mode (none, shared, excl.)
* STD_SPERRMODUS = ' ' "Standard lock mode (if different)
* STAWN_READ = ' ' "Commodity Code
IMPORTING
WMARC_MD = "Generated Table for View
O_MARC_MD = "Generated Table for View
EXCEPTIONS
LOCK_ON_MARC = 1 LOCK_SYSTEM_ERROR = 2 WRONG_CALL = 3 NOT_FOUND = 4
IMPORTING Parameters details for MARC_MD_SINGLE_READ
KZRFB - Indicator: Refresh Buffer Entry
Data type: MTCOM-KZRFBDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
MAXTZ - Max. No. of Entries in Buffer
Data type: MTCOM-MAXTZOptional: Yes
Call by Reference: No ( called with pass by value option)
MATNR -
Data type: MARC-MATNROptional: No
Call by Reference: No ( called with pass by value option)
WERKS -
Data type: MARC-WERKSOptional: No
Call by Reference: No ( called with pass by value option)
SPERRMODUS - Lock mode (none, shared, excl.)
Data type: TVGVI-SPERADefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
STD_SPERRMODUS - Standard lock mode (if different)
Data type: TVGVI-SPERADefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
STAWN_READ - Commodity Code
Data type: FLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MARC_MD_SINGLE_READ
WMARC_MD - Generated Table for View
Data type: V_MARC_MDOptional: No
Call by Reference: No ( called with pass by value option)
O_MARC_MD - Generated Table for View
Data type: V_MARC_MDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LOCK_ON_MARC -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOCK_SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_CALL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MARC_MD_SINGLE_READ 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_kzrfb | TYPE MTCOM-KZRFB, " ' ' | |||
| lv_wmarc_md | TYPE V_MARC_MD, " | |||
| lv_lock_on_marc | TYPE V_MARC_MD, " | |||
| lv_maxtz | TYPE MTCOM-MAXTZ, " 0 | |||
| lv_o_marc_md | TYPE V_MARC_MD, " | |||
| lv_lock_system_error | TYPE V_MARC_MD, " | |||
| lv_matnr | TYPE MARC-MATNR, " | |||
| lv_wrong_call | TYPE MARC, " | |||
| lv_werks | TYPE MARC-WERKS, " | |||
| lv_not_found | TYPE MARC, " | |||
| lv_sperrmodus | TYPE TVGVI-SPERA, " ' ' | |||
| lv_std_sperrmodus | TYPE TVGVI-SPERA, " ' ' | |||
| lv_stawn_read | TYPE FLAG. " ' ' |
|   CALL FUNCTION 'MARC_MD_SINGLE_READ' "DE-EN-LANG-SWITCH-NO-TRANSLATION |
| EXPORTING | ||
| KZRFB | = lv_kzrfb | |
| MAXTZ | = lv_maxtz | |
| MATNR | = lv_matnr | |
| WERKS | = lv_werks | |
| SPERRMODUS | = lv_sperrmodus | |
| STD_SPERRMODUS | = lv_std_sperrmodus | |
| STAWN_READ | = lv_stawn_read | |
| IMPORTING | ||
| WMARC_MD | = lv_wmarc_md | |
| O_MARC_MD | = lv_o_marc_md | |
| EXCEPTIONS | ||
| LOCK_ON_MARC = 1 | ||
| LOCK_SYSTEM_ERROR = 2 | ||
| WRONG_CALL = 3 | ||
| NOT_FOUND = 4 | ||
| . " MARC_MD_SINGLE_READ | ||
ABAP code using 7.40 inline data declarations to call FM MARC_MD_SINGLE_READ
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 KZRFB FROM MTCOM INTO @DATA(ld_kzrfb). | ||||
| DATA(ld_kzrfb) | = ' '. | |||
| "SELECT single MAXTZ FROM MTCOM INTO @DATA(ld_maxtz). | ||||
| "SELECT single MATNR FROM MARC INTO @DATA(ld_matnr). | ||||
| "SELECT single WERKS FROM MARC INTO @DATA(ld_werks). | ||||
| "SELECT single SPERA FROM TVGVI INTO @DATA(ld_sperrmodus). | ||||
| DATA(ld_sperrmodus) | = ' '. | |||
| "SELECT single SPERA FROM TVGVI INTO @DATA(ld_std_sperrmodus). | ||||
| DATA(ld_std_sperrmodus) | = ' '. | |||
| DATA(ld_stawn_read) | = ' '. | |||
Search for further information about these or an SAP related objects