SAP MOD_SAP_RENAME Function Module for









MOD_SAP_RENAME is a standard mod sap rename 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 mod sap rename FM, simply by entering the name MOD_SAP_RENAME into the relevant SAP transaction such as SE37 or SE38.

Function Group: SMOD
Program Name: SAPLSMOD
Main Program: SAPLSMOD
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MOD_SAP_RENAME 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 'MOD_SAP_RENAME'"
EXPORTING
* MESSAGE = 'X' "
MODNAME = "
* NMODNAME = ' ' "
* SCREEN = 'X' "

EXCEPTIONS
ATTR_ENQUEUED = 1 MOD_ENQUEUED = 2 NATTR_ENQUEUED = 3 NMOD_ENQUEUED = 4 NMOD_EXISTS = 5 NTEXT_ENQUEUED = 6 TEXT_ENQUEUED = 7 WRONG_INPUT = 8
.



IMPORTING Parameters details for MOD_SAP_RENAME

MESSAGE -

Data type:
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MODNAME -

Data type: MODSAP-NAME
Optional: No
Call by Reference: No ( called with pass by value option)

NMODNAME -

Data type: MODSAP-NAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SCREEN -

Data type:
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ATTR_ENQUEUED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

MOD_ENQUEUED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NATTR_ENQUEUED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NMOD_ENQUEUED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NMOD_EXISTS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NTEXT_ENQUEUED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TEXT_ENQUEUED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

WRONG_INPUT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MOD_SAP_RENAME 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_message  TYPE STRING, "   'X'
lv_attr_enqueued  TYPE STRING, "   
lv_modname  TYPE MODSAP-NAME, "   
lv_mod_enqueued  TYPE MODSAP, "   
lv_nmodname  TYPE MODSAP-NAME, "   SPACE
lv_nattr_enqueued  TYPE MODSAP, "   
lv_screen  TYPE MODSAP, "   'X'
lv_nmod_enqueued  TYPE MODSAP, "   
lv_nmod_exists  TYPE MODSAP, "   
lv_ntext_enqueued  TYPE MODSAP, "   
lv_text_enqueued  TYPE MODSAP, "   
lv_wrong_input  TYPE MODSAP. "   

  CALL FUNCTION 'MOD_SAP_RENAME'  "
    EXPORTING
         MESSAGE = lv_message
         MODNAME = lv_modname
         NMODNAME = lv_nmodname
         SCREEN = lv_screen
    EXCEPTIONS
        ATTR_ENQUEUED = 1
        MOD_ENQUEUED = 2
        NATTR_ENQUEUED = 3
        NMOD_ENQUEUED = 4
        NMOD_EXISTS = 5
        NTEXT_ENQUEUED = 6
        TEXT_ENQUEUED = 7
        WRONG_INPUT = 8
. " MOD_SAP_RENAME




ABAP code using 7.40 inline data declarations to call FM MOD_SAP_RENAME

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.

DATA(ld_message) = 'X'.
 
 
"SELECT single NAME FROM MODSAP INTO @DATA(ld_modname).
 
 
"SELECT single NAME FROM MODSAP INTO @DATA(ld_nmodname).
DATA(ld_nmodname) = ' '.
 
 
DATA(ld_screen) = 'X'.
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!