SAP MYMS_RENAME_MATNR Function Module for NOTRANSL: Umbenennen der Materialnummer nach interner Nummernvergabe
MYMS_RENAME_MATNR is a standard myms rename 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: Umbenennen der Materialnummer nach interner Nummernvergabe 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 myms rename matnr FM, simply by entering the name MYMS_RENAME_MATNR into the relevant SAP transaction such as SE37 or SE38.
Function Group: MG30
Program Name: SAPLMG30
Main Program: SAPLMG30
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MYMS_RENAME_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 'MYMS_RENAME_MATNR'"NOTRANSL: Umbenennen der Materialnummer nach interner Nummernvergabe.
EXPORTING
OMATNR = "Material Number
NMATNR = "Material Number
IMPORTING Parameters details for MYMS_RENAME_MATNR
OMATNR - Material Number
Data type: MARA-MATNROptional: No
Call by Reference: Yes
NMATNR - Material Number
Data type: MARA-MATNROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MYMS_RENAME_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_omatnr | TYPE MARA-MATNR, " | |||
| lv_nmatnr | TYPE MARA-MATNR. " |
|   CALL FUNCTION 'MYMS_RENAME_MATNR' "NOTRANSL: Umbenennen der Materialnummer nach interner Nummernvergabe |
| EXPORTING | ||
| OMATNR | = lv_omatnr | |
| NMATNR | = lv_nmatnr | |
| . " MYMS_RENAME_MATNR | ||
ABAP code using 7.40 inline data declarations to call FM MYMS_RENAME_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 MARA INTO @DATA(ld_omatnr). | ||||
| "SELECT single MATNR FROM MARA INTO @DATA(ld_nmatnr). | ||||
Search for further information about these or an SAP related objects