SAP MG_BATCH_CHECK_MCH1 Function Module for NOTRANSL: Prüfen, ob noch MCH1-Sätze in den internen Tabellen zum Schlüsse
MG_BATCH_CHECK_MCH1 is a standard mg batch check mch1 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: Prüfen, ob noch MCH1-Sätze in den internen Tabellen zum Schlüsse 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 mg batch check mch1 FM, simply by entering the name MG_BATCH_CHECK_MCH1 into the relevant SAP transaction such as SE37 or SE38.
Function Group: MGR2
Program Name: SAPLMGR2
Main Program: SAPLMGR2
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MG_BATCH_CHECK_MCH1 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 'MG_BATCH_CHECK_MCH1'"NOTRANSL: Prüfen, ob noch MCH1-Sätze in den internen Tabellen zum Schlüsse.
EXPORTING
MDATA = "Batches
TABLES
* MCH1_1 = "Batches (if Batch Management Cross-Plant)
* MCH1_2 = "Batches (if Batch Management Cross-Plant)
EXCEPTIONS
IN_USE = 1
IMPORTING Parameters details for MG_BATCH_CHECK_MCH1
MDATA - Batches
Data type: MCHAOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MG_BATCH_CHECK_MCH1
MCH1_1 - Batches (if Batch Management Cross-Plant)
Data type: MCH1Optional: Yes
Call by Reference: No ( called with pass by value option)
MCH1_2 - Batches (if Batch Management Cross-Plant)
Data type: MCH1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
IN_USE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MG_BATCH_CHECK_MCH1 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_mdata | TYPE MCHA, " | |||
| lv_in_use | TYPE MCHA, " | |||
| lt_mch1_1 | TYPE STANDARD TABLE OF MCH1, " | |||
| lt_mch1_2 | TYPE STANDARD TABLE OF MCH1. " |
|   CALL FUNCTION 'MG_BATCH_CHECK_MCH1' "NOTRANSL: Prüfen, ob noch MCH1-Sätze in den internen Tabellen zum Schlüsse |
| EXPORTING | ||
| MDATA | = lv_mdata | |
| TABLES | ||
| MCH1_1 | = lt_mch1_1 | |
| MCH1_2 | = lt_mch1_2 | |
| EXCEPTIONS | ||
| IN_USE = 1 | ||
| . " MG_BATCH_CHECK_MCH1 | ||
ABAP code using 7.40 inline data declarations to call FM MG_BATCH_CHECK_MCH1
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.Search for further information about these or an SAP related objects