SAP RP_EDIT_NAME Function Module for
RP_EDIT_NAME is a standard rp edit name 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 rp edit name FM, simply by entering the name RP_EDIT_NAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPNA
Program Name: SAPLRPNA
Main Program: SAPLRPNA
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RP_EDIT_NAME 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 'RP_EDIT_NAME'".
EXPORTING
FORMAT = "Formatting parameter for T522N-KNZNM
LANGU = "Language
MOLGA = "Country modifier
* PP0002 = ' ' "Infotype 0002
* PP0021 = ' ' "Infotype 0021
* PP0148 = ' ' "Infotype 0148
* NAMEL = "
* PPINFTV = "
* TCLAS = 'A' "
IMPORTING
EDIT_NAME = "Name
RETCODE = "Return code
IMPORTING Parameters details for RP_EDIT_NAME
FORMAT - Formatting parameter for T522N-KNZNM
Data type: P0002-KNZNMOptional: No
Call by Reference: No ( called with pass by value option)
LANGU - Language
Data type: SY-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
MOLGA - Country modifier
Data type: T001P-MOLGAOptional: No
Call by Reference: No ( called with pass by value option)
PP0002 - Infotype 0002
Data type: P0002Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PP0021 - Infotype 0021
Data type: P0021Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PP0148 - Infotype 0148
Data type: P0148Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NAMEL -
Data type: PAD_NAMELOptional: Yes
Call by Reference: No ( called with pass by value option)
PPINFTV -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
TCLAS -
Data type: PSPAR-TCLASDefault: 'A'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RP_EDIT_NAME
EDIT_NAME - Name
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
RETCODE - Return code
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RP_EDIT_NAME 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_format | TYPE P0002-KNZNM, " | |||
lv_edit_name | TYPE C, " | |||
lv_langu | TYPE SY-LANGU, " | |||
lv_retcode | TYPE SY-SUBRC, " | |||
lv_molga | TYPE T001P-MOLGA, " | |||
lv_pp0002 | TYPE P0002, " SPACE | |||
lv_pp0021 | TYPE P0021, " SPACE | |||
lv_pp0148 | TYPE P0148, " SPACE | |||
lv_namel | TYPE PAD_NAMEL, " | |||
lv_ppinftv | TYPE PAD_NAMEL, " | |||
lv_tclas | TYPE PSPAR-TCLAS. " 'A' |
  CALL FUNCTION 'RP_EDIT_NAME' " |
EXPORTING | ||
FORMAT | = lv_format | |
LANGU | = lv_langu | |
MOLGA | = lv_molga | |
PP0002 | = lv_pp0002 | |
PP0021 | = lv_pp0021 | |
PP0148 | = lv_pp0148 | |
NAMEL | = lv_namel | |
PPINFTV | = lv_ppinftv | |
TCLAS | = lv_tclas | |
IMPORTING | ||
EDIT_NAME | = lv_edit_name | |
RETCODE | = lv_retcode | |
. " RP_EDIT_NAME |
ABAP code using 7.40 inline data declarations to call FM RP_EDIT_NAME
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 KNZNM FROM P0002 INTO @DATA(ld_format). | ||||
"SELECT single LANGU FROM SY INTO @DATA(ld_langu). | ||||
"SELECT single SUBRC FROM SY INTO @DATA(ld_retcode). | ||||
"SELECT single MOLGA FROM T001P INTO @DATA(ld_molga). | ||||
DATA(ld_pp0002) | = ' '. | |||
DATA(ld_pp0021) | = ' '. | |||
DATA(ld_pp0148) | = ' '. | |||
"SELECT single TCLAS FROM PSPAR INTO @DATA(ld_tclas). | ||||
DATA(ld_tclas) | = 'A'. | |||
Search for further information about these or an SAP related objects