SAP MARD_EXIST_MATNR Function Module for NOTRANSL: Existenzcheck, ob MARD-Satz zu Materialnr vorhanden ist
MARD_EXIST_MATNR is a standard mard exist matnr 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: Existenzcheck, ob MARD-Satz zu Materialnr vorhanden ist 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 mard exist matnr FM, simply by entering the name MARD_EXIST_MATNR into the relevant SAP transaction such as SE37 or SE38.
Function Group: MG26
Program Name: SAPLMG26
Main Program: SAPLMG26
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MARD_EXIST_MATNR 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 'MARD_EXIST_MATNR'"NOTRANSL: Existenzcheck, ob MARD-Satz zu Materialnr vorhanden ist.
EXPORTING
MATNR = "Material Number
EXCEPTIONS
WRONG_CALL = 1 NOT_FOUND = 2
IMPORTING Parameters details for MARD_EXIST_MATNR
MATNR - Material Number
Data type: MARD-MATNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_CALL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND - No Record Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MARD_EXIST_MATNR 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_matnr | TYPE MARD-MATNR, " | |||
| lv_wrong_call | TYPE MARD, " | |||
| lv_not_found | TYPE MARD. " |
|   CALL FUNCTION 'MARD_EXIST_MATNR' "NOTRANSL: Existenzcheck, ob MARD-Satz zu Materialnr vorhanden ist |
| EXPORTING | ||
| MATNR | = lv_matnr | |
| EXCEPTIONS | ||
| WRONG_CALL = 1 | ||
| NOT_FOUND = 2 | ||
| . " MARD_EXIST_MATNR | ||
ABAP code using 7.40 inline data declarations to call FM MARD_EXIST_MATNR
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 MATNR FROM MARD INTO @DATA(ld_matnr). | ||||
Search for further information about these or an SAP related objects