SAP MALG_CHANGE_CHECK_1 Function Module for Check if MALG Was Changed
MALG_CHANGE_CHECK_1 is a standard malg change check 1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if MALG Was Changed 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 malg change check 1 FM, simply by entering the name MALG_CHANGE_CHECK_1 into the relevant SAP transaction such as SE37 or SE38.
Function Group: MG51
Program Name: SAPLMG51
Main Program: SAPLMG51
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MALG_CHANGE_CHECK_1 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 'MALG_CHANGE_CHECK_1'"Check if MALG Was Changed.
IMPORTING
FLGAEN = "Change Indicator
TABLES
PTAB_FULL_RT = "
EXCEPTIONS
BUFFER_WRONG = 1
EXPORTING Parameters details for MALG_CHANGE_CHECK_1
FLGAEN - Change Indicator
Data type: SY-DATAROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MALG_CHANGE_CHECK_1
PTAB_FULL_RT -
Data type: SPTAB_RTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
BUFFER_WRONG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MALG_CHANGE_CHECK_1 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_flgaen | TYPE SY-DATAR, " | |||
| lv_buffer_wrong | TYPE SY, " | |||
| lt_ptab_full_rt | TYPE STANDARD TABLE OF SPTAB_RT. " |
|   CALL FUNCTION 'MALG_CHANGE_CHECK_1' "Check if MALG Was Changed |
| IMPORTING | ||
| FLGAEN | = lv_flgaen | |
| TABLES | ||
| PTAB_FULL_RT | = lt_ptab_full_rt | |
| EXCEPTIONS | ||
| BUFFER_WRONG = 1 | ||
| . " MALG_CHANGE_CHECK_1 | ||
ABAP code using 7.40 inline data declarations to call FM MALG_CHANGE_CHECK_1
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 DATAR FROM SY INTO @DATA(ld_flgaen). | ||||
Search for further information about these or an SAP related objects