MATNR_NUMBER_RENAME SAP Function module

MATNR_NUMBER_RENAME is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name MATNR_NUMBER_RENAME into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MGV_NUMBER_CONVERSION
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM MATNR_NUMBER_RENAME - MATNR NUMBER RENAME

CALL FUNCTION 'MATNR_NUMBER_RENAME' "
  EXPORTING
*   matnr_ext =                 " matnr_ext
*   matnr_vers =                " matnr_vers
    matnr_int =                 " matnr_int
*   save_to_db = 'X'            " xfeld
*   save_on_commit =            " xfeld
*   check_unique = ' '          " xfeld
  EXCEPTIONS
    NUMBER_NOT_FOUND = 1        "
    NOT_UNIQUE = 2              "
    NUMBER_NOT_ALLOWED = 3      "
    .  "  MATNR_NUMBER_RENAME

ABAP code example for Function Module MATNR_NUMBER_RENAME

The ABAP code below is a full code listing to execute function module MATNR_NUMBER_RENAME including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_matnr_ext) = 'Check type of data required'.

DATA(ld_matnr_vers) = 'Check type of data required'.

DATA(ld_matnr_int) = 'Check type of data required'.

DATA(ld_save_to_db) = 'Check type of data required'.

DATA(ld_save_on_commit) = 'Check type of data required'.

DATA(ld_check_unique) = 'Check type of data required'.
.

CALL FUNCTION 'MATNR_NUMBER_RENAME'
  EXPORTING
*   matnr_ext =                  ld_matnr_ext
*   matnr_vers =                 ld_matnr_vers
    matnr_int =                  ld_matnr_int
*   save_to_db =                 ld_save_to_db
*   save_on_commit =             ld_save_on_commit
*   check_unique =               ld_check_unique
  EXCEPTIONS
    NUMBER_NOT_FOUND =           1
    NOT_UNIQUE =                 2
    NUMBER_NOT_ALLOWED =         3
    .  "  MATNR_NUMBER_RENAME

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_matnr_ext
 
 TYPE MATNR_EXT ,
ld_matnr_vers
 
 TYPE MATNR_VERS ,
ld_matnr_int
 
 TYPE MATNR_INT ,
ld_save_to_db
 
 TYPE XFELD ,
ld_save_on_commit
 
 TYPE XFELD ,
ld_check_unique
 
 TYPE XFELD .


ld_matnr_ext = 'Check type of data required'.
ld_matnr_vers = 'Check type of data required'.
ld_matnr_int = 'Check type of data required'.
ld_save_to_db = 'Check type of data required'.
ld_save_on_commit = 'Check type of data required'.
ld_check_unique = 'Check type of data required'.