SAP RP_25_MAP_ER_ADDRESS_NEW Function Module for Mapping ER address from ADRC to the New format required by tax authority
RP_25_MAP_ER_ADDRESS_NEW is a standard rp 25 map er address new SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Mapping ER address from ADRC to the New format required by tax authority 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 rp 25 map er address new FM, simply by entering the name RP_25_MAP_ER_ADDRESS_NEW into the relevant SAP transaction such as SE37 or SE38.
Function Group: ADDRSG
Program Name: SAPLADDRSG
Main Program:
Appliation area:
Release date: 18-Sep-2000
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RP_25_MAP_ER_ADDRESS_NEW 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_25_MAP_ER_ADDRESS_NEW'"Mapping ER address from ADRC to the New format required by tax authority.
EXPORTING
SUBAREA = "Personal Area
IMPORTING
BLOCKNUMBER = "House Number
STORYNUMBER = "Floor in building
UNITNUMBER = "Identification of an apartment in a building
STREETNAME = "Line in Form
POSTALCODE = "Postal Code
RETURNCODE = "Return value, return value after ABAP statements
STREETNAME1 = "2nd address line
TABLES
I500P = "Personnel Areas
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLADDRSG_001 Exit for address conversion function
IMPORTING Parameters details for RP_25_MAP_ER_ADDRESS_NEW
SUBAREA - Personal Area
Data type: T500P-PERSAOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RP_25_MAP_ER_ADDRESS_NEW
BLOCKNUMBER - House Number
Data type: P0006-HSNMROptional: No
Call by Reference: No ( called with pass by value option)
STORYNUMBER - Floor in building
Data type: P0006-FLOOROptional: No
Call by Reference: No ( called with pass by value option)
UNITNUMBER - Identification of an apartment in a building
Data type: P0006-POSTAOptional: No
Call by Reference: No ( called with pass by value option)
STREETNAME - Line in Form
Data type: P0006-STRASOptional: No
Call by Reference: No ( called with pass by value option)
POSTALCODE - Postal Code
Data type: P0006-PSTLZOptional: No
Call by Reference: No ( called with pass by value option)
RETURNCODE - Return value, return value after ABAP statements
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
STREETNAME1 - 2nd address line
Data type: P0006-LOCATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RP_25_MAP_ER_ADDRESS_NEW
I500P - Personnel Areas
Data type: T500POptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RP_25_MAP_ER_ADDRESS_NEW 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: | ||||
| lt_i500p | TYPE STANDARD TABLE OF T500P, " | |||
| lv_subarea | TYPE T500P-PERSA, " | |||
| lv_blocknumber | TYPE P0006-HSNMR, " | |||
| lv_storynumber | TYPE P0006-FLOOR, " | |||
| lv_unitnumber | TYPE P0006-POSTA, " | |||
| lv_streetname | TYPE P0006-STRAS, " | |||
| lv_postalcode | TYPE P0006-PSTLZ, " | |||
| lv_returncode | TYPE SY-SUBRC, " | |||
| lv_streetname1 | TYPE P0006-LOCAT. " |
|   CALL FUNCTION 'RP_25_MAP_ER_ADDRESS_NEW' "Mapping ER address from ADRC to the New format required by tax authority |
| EXPORTING | ||
| SUBAREA | = lv_subarea | |
| IMPORTING | ||
| BLOCKNUMBER | = lv_blocknumber | |
| STORYNUMBER | = lv_storynumber | |
| UNITNUMBER | = lv_unitnumber | |
| STREETNAME | = lv_streetname | |
| POSTALCODE | = lv_postalcode | |
| RETURNCODE | = lv_returncode | |
| STREETNAME1 | = lv_streetname1 | |
| TABLES | ||
| I500P | = lt_i500p | |
| . " RP_25_MAP_ER_ADDRESS_NEW | ||
ABAP code using 7.40 inline data declarations to call FM RP_25_MAP_ER_ADDRESS_NEW
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 PERSA FROM T500P INTO @DATA(ld_subarea). | ||||
| "SELECT single HSNMR FROM P0006 INTO @DATA(ld_blocknumber). | ||||
| "SELECT single FLOOR FROM P0006 INTO @DATA(ld_storynumber). | ||||
| "SELECT single POSTA FROM P0006 INTO @DATA(ld_unitnumber). | ||||
| "SELECT single STRAS FROM P0006 INTO @DATA(ld_streetname). | ||||
| "SELECT single PSTLZ FROM P0006 INTO @DATA(ld_postalcode). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_returncode). | ||||
| "SELECT single LOCAT FROM P0006 INTO @DATA(ld_streetname1). | ||||
Search for further information about these or an SAP related objects