SAP ADDR_COMPOSE_STREET_LINE Function Module for
ADDR_COMPOSE_STREET_LINE is a standard addr compose street line 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 addr compose street line FM, simply by entering the name ADDR_COMPOSE_STREET_LINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SADR
Program Name: SAPLSADR
Main Program: SAPLSADR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ADDR_COMPOSE_STREET_LINE 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 'ADDR_COMPOSE_STREET_LINE'".
EXPORTING
STREET = "
* HOUSE_NUMBER = ' ' "House Number
* HOUSE_NUMBER2 = ' ' "
* LENGTH = 80 "
* RULE = "
* ADDRESS_LAYOUT_KEY = "
* COUNTRY = "Country
LANGUAGE = "
IMPORTING
STREET_LINE = "
RESULT_SHORTENED = "
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_SAPLSADR_001
IMPORTING Parameters details for ADDR_COMPOSE_STREET_LINE
STREET -
Data type: ADRC-STREETOptional: No
Call by Reference: No ( called with pass by value option)
HOUSE_NUMBER - House Number
Data type: ADRC-HOUSE_NUM1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
HOUSE_NUMBER2 -
Data type: ADRC-HOUSE_NUM2Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LENGTH -
Data type: IDefault: 80
Optional: Yes
Call by Reference: No ( called with pass by value option)
RULE -
Data type: AD_STRRULEOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDRESS_LAYOUT_KEY -
Data type: T005A-ADDRSOptional: Yes
Call by Reference: No ( called with pass by value option)
COUNTRY - Country
Data type: ADRC-COUNTRYOptional: Yes
Call by Reference: No ( called with pass by value option)
LANGUAGE -
Data type: ADRC-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ADDR_COMPOSE_STREET_LINE
STREET_LINE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RESULT_SHORTENED -
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ADDR_COMPOSE_STREET_LINE 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_street | TYPE ADRC-STREET, " | |||
| lv_street_line | TYPE ADRC, " | |||
| lv_house_number | TYPE ADRC-HOUSE_NUM1, " SPACE | |||
| lv_result_shortened | TYPE XFELD, " | |||
| lv_house_number2 | TYPE ADRC-HOUSE_NUM2, " SPACE | |||
| lv_length | TYPE I, " 80 | |||
| lv_rule | TYPE AD_STRRULE, " | |||
| lv_address_layout_key | TYPE T005A-ADDRS, " | |||
| lv_country | TYPE ADRC-COUNTRY, " | |||
| lv_language | TYPE ADRC-LANGU. " |
|   CALL FUNCTION 'ADDR_COMPOSE_STREET_LINE' " |
| EXPORTING | ||
| STREET | = lv_street | |
| HOUSE_NUMBER | = lv_house_number | |
| HOUSE_NUMBER2 | = lv_house_number2 | |
| LENGTH | = lv_length | |
| RULE | = lv_rule | |
| ADDRESS_LAYOUT_KEY | = lv_address_layout_key | |
| COUNTRY | = lv_country | |
| LANGUAGE | = lv_language | |
| IMPORTING | ||
| STREET_LINE | = lv_street_line | |
| RESULT_SHORTENED | = lv_result_shortened | |
| . " ADDR_COMPOSE_STREET_LINE | ||
ABAP code using 7.40 inline data declarations to call FM ADDR_COMPOSE_STREET_LINE
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 STREET FROM ADRC INTO @DATA(ld_street). | ||||
| "SELECT single HOUSE_NUM1 FROM ADRC INTO @DATA(ld_house_number). | ||||
| DATA(ld_house_number) | = ' '. | |||
| "SELECT single HOUSE_NUM2 FROM ADRC INTO @DATA(ld_house_number2). | ||||
| DATA(ld_house_number2) | = ' '. | |||
| DATA(ld_length) | = 80. | |||
| "SELECT single ADDRS FROM T005A INTO @DATA(ld_address_layout_key). | ||||
| "SELECT single COUNTRY FROM ADRC INTO @DATA(ld_country). | ||||
| "SELECT single LANGU FROM ADRC INTO @DATA(ld_language). | ||||
Search for further information about these or an SAP related objects