SAP MYMS_CHANGE_CHECK Function Module for
MYMS_CHANGE_CHECK is a standard myms change check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 myms change check FM, simply by entering the name MYMS_CHANGE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: MG30
Program Name: SAPLMG30
Main Program: SAPLMG30
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MYMS_CHANGE_CHECK 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 'MYMS_CHANGE_CHECK'".
EXPORTING
* IRMMG1 = ' ' "Org. Level Vals, Material No.,...
IMPORTING
FLGAEN = "Change Flag (U/I/X)
EXCEPTIONS
BUFFER_WRONG = 1
IMPORTING Parameters details for MYMS_CHANGE_CHECK
IRMMG1 - Org. Level Vals, Material No.,...
Data type: RMMG1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MYMS_CHANGE_CHECK
FLGAEN - Change Flag (U/I/X)
Data type: SY-DATAROptional: 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 MYMS_CHANGE_CHECK 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_irmmg1 | TYPE RMMG1, " SPACE | |||
| lv_buffer_wrong | TYPE RMMG1. " |
|   CALL FUNCTION 'MYMS_CHANGE_CHECK' " |
| EXPORTING | ||
| IRMMG1 | = lv_irmmg1 | |
| IMPORTING | ||
| FLGAEN | = lv_flgaen | |
| EXCEPTIONS | ||
| BUFFER_WRONG = 1 | ||
| . " MYMS_CHANGE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM MYMS_CHANGE_CHECK
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). | ||||
| DATA(ld_irmmg1) | = ' '. | |||
Search for further information about these or an SAP related objects