SAP ISP_POST_LIST_ADDRESS_SELECT Function Module for IS-M/SD: Determine Address Numbers for Postal Units in a Geo. Unit
ISP_POST_LIST_ADDRESS_SELECT is a standard isp post list address select SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: Determine Address Numbers for Postal Units in a Geo. Unit 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 isp post list address select FM, simply by entering the name ISP_POST_LIST_ADDRESS_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JSS3
Program Name: SAPLJSS3
Main Program: SAPLJSS3
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_POST_LIST_ADDRESS_SELECT 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 'ISP_POST_LIST_ADDRESS_SELECT'"IS-M/SD: Determine Address Numbers for Postal Units in a Geo. Unit.
EXPORTING
* HERKUNFT = "
* ALLE_ATTRIBUTE = "
TABLES
* ADRESS_TAB = "Address Number Table
POST_EINH_TAB = "
* ADRESS_TAB_FULL = "IS-M: Extended Address Management
EXCEPTIONS
NO_DATA_FOUND = 1 NO_SUCH_LAND_FOUND = 2 NO_SUCH_POSTCODE_FOUND = 3 NO_SUCH_STREET_FOUND = 4 NO_SUCH_TOWN_FOUND = 5
IMPORTING Parameters details for ISP_POST_LIST_ADDRESS_SELECT
HERKUNFT -
Data type: JGTSADR-HERKOptional: Yes
Call by Reference: No ( called with pass by value option)
ALLE_ATTRIBUTE -
Data type: RJVSEL-XVERSVOROptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISP_POST_LIST_ADDRESS_SELECT
ADRESS_TAB - Address Number Table
Data type: RJLSS3Optional: Yes
Call by Reference: Yes
POST_EINH_TAB -
Data type: RJS0802Optional: No
Call by Reference: No ( called with pass by value option)
ADRESS_TAB_FULL - IS-M: Extended Address Management
Data type: JGTSADROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_DATA_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SUCH_LAND_FOUND - Country does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SUCH_POSTCODE_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SUCH_STREET_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SUCH_TOWN_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_POST_LIST_ADDRESS_SELECT 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_herkunft | TYPE JGTSADR-HERK, " | |||
| lt_adress_tab | TYPE STANDARD TABLE OF RJLSS3, " | |||
| lv_no_data_found | TYPE RJLSS3, " | |||
| lt_post_einh_tab | TYPE STANDARD TABLE OF RJS0802, " | |||
| lv_alle_attribute | TYPE RJVSEL-XVERSVOR, " | |||
| lv_no_such_land_found | TYPE RJVSEL, " | |||
| lt_adress_tab_full | TYPE STANDARD TABLE OF JGTSADR, " | |||
| lv_no_such_postcode_found | TYPE JGTSADR, " | |||
| lv_no_such_street_found | TYPE JGTSADR, " | |||
| lv_no_such_town_found | TYPE JGTSADR. " |
|   CALL FUNCTION 'ISP_POST_LIST_ADDRESS_SELECT' "IS-M/SD: Determine Address Numbers for Postal Units in a Geo. Unit |
| EXPORTING | ||
| HERKUNFT | = lv_herkunft | |
| ALLE_ATTRIBUTE | = lv_alle_attribute | |
| TABLES | ||
| ADRESS_TAB | = lt_adress_tab | |
| POST_EINH_TAB | = lt_post_einh_tab | |
| ADRESS_TAB_FULL | = lt_adress_tab_full | |
| EXCEPTIONS | ||
| NO_DATA_FOUND = 1 | ||
| NO_SUCH_LAND_FOUND = 2 | ||
| NO_SUCH_POSTCODE_FOUND = 3 | ||
| NO_SUCH_STREET_FOUND = 4 | ||
| NO_SUCH_TOWN_FOUND = 5 | ||
| . " ISP_POST_LIST_ADDRESS_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM ISP_POST_LIST_ADDRESS_SELECT
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 HERK FROM JGTSADR INTO @DATA(ld_herkunft). | ||||
| "SELECT single XVERSVOR FROM RJVSEL INTO @DATA(ld_alle_attribute). | ||||
Search for further information about these or an SAP related objects