SAP ISM_ADDRESS_FIELDS_GET Function Module for IS-M/AM: Make Entries in Address Fields 1 and 2 According to Customizing
ISM_ADDRESS_FIELDS_GET is a standard ism address fields get 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/AM: Make Entries in Address Fields 1 and 2 According to Customizing 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 ism address fields get FM, simply by entering the name ISM_ADDRESS_FIELDS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHPB
Program Name: SAPLJHPB
Main Program: SAPLJHPB
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_ADDRESS_FIELDS_GET 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 'ISM_ADDRESS_FIELDS_GET'"IS-M/AM: Make Entries in Address Fields 1 and 2 According to Customizing.
EXPORTING
* PV_FLG_CONTACT_PERSON = ' ' "
PV_LAND1 = "
PV_ANRED = "
PV_NAME1 = "
PV_NAME2 = "
PV_NAME3 = "
PV_NAME4 = "
IMPORTING
PV_ADR_FELD1 = "IS-M: Address Field for Business Partner Name
PV_ADR_FELD2 = "IS-M: Address Field for Business Partner Name
IMPORTING Parameters details for ISM_ADDRESS_FIELDS_GET
PV_FLG_CONTACT_PERSON -
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
PV_LAND1 -
Data type: TJHAF-LAND1Optional: No
Call by Reference: No ( called with pass by value option)
PV_ANRED -
Data type: TJHAF-ANREDOptional: No
Call by Reference: Yes
PV_NAME1 -
Data type: JGTSADR-NAME1Optional: No
Call by Reference: Yes
PV_NAME2 -
Data type: JGTSADR-NAME2Optional: No
Call by Reference: Yes
PV_NAME3 -
Data type: JGTSADR-NAME3Optional: No
Call by Reference: Yes
PV_NAME4 -
Data type: JGTSADR-NAME4Optional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_ADDRESS_FIELDS_GET
PV_ADR_FELD1 - IS-M: Address Field for Business Partner Name
Data type: RJHA1407-ADR_FELD1Optional: No
Call by Reference: Yes
PV_ADR_FELD2 - IS-M: Address Field for Business Partner Name
Data type: RJHA1407-ADR_FELD2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_ADDRESS_FIELDS_GET 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_pv_adr_feld1 | TYPE RJHA1407-ADR_FELD1, " | |||
| lv_pv_flg_contact_person | TYPE XFELD, " ' ' | |||
| lv_pv_land1 | TYPE TJHAF-LAND1, " | |||
| lv_pv_adr_feld2 | TYPE RJHA1407-ADR_FELD2, " | |||
| lv_pv_anred | TYPE TJHAF-ANRED, " | |||
| lv_pv_name1 | TYPE JGTSADR-NAME1, " | |||
| lv_pv_name2 | TYPE JGTSADR-NAME2, " | |||
| lv_pv_name3 | TYPE JGTSADR-NAME3, " | |||
| lv_pv_name4 | TYPE JGTSADR-NAME4. " |
|   CALL FUNCTION 'ISM_ADDRESS_FIELDS_GET' "IS-M/AM: Make Entries in Address Fields 1 and 2 According to Customizing |
| EXPORTING | ||
| PV_FLG_CONTACT_PERSON | = lv_pv_flg_contact_person | |
| PV_LAND1 | = lv_pv_land1 | |
| PV_ANRED | = lv_pv_anred | |
| PV_NAME1 | = lv_pv_name1 | |
| PV_NAME2 | = lv_pv_name2 | |
| PV_NAME3 | = lv_pv_name3 | |
| PV_NAME4 | = lv_pv_name4 | |
| IMPORTING | ||
| PV_ADR_FELD1 | = lv_pv_adr_feld1 | |
| PV_ADR_FELD2 | = lv_pv_adr_feld2 | |
| . " ISM_ADDRESS_FIELDS_GET | ||
ABAP code using 7.40 inline data declarations to call FM ISM_ADDRESS_FIELDS_GET
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 ADR_FELD1 FROM RJHA1407 INTO @DATA(ld_pv_adr_feld1). | ||||
| DATA(ld_pv_flg_contact_person) | = ' '. | |||
| "SELECT single LAND1 FROM TJHAF INTO @DATA(ld_pv_land1). | ||||
| "SELECT single ADR_FELD2 FROM RJHA1407 INTO @DATA(ld_pv_adr_feld2). | ||||
| "SELECT single ANRED FROM TJHAF INTO @DATA(ld_pv_anred). | ||||
| "SELECT single NAME1 FROM JGTSADR INTO @DATA(ld_pv_name1). | ||||
| "SELECT single NAME2 FROM JGTSADR INTO @DATA(ld_pv_name2). | ||||
| "SELECT single NAME3 FROM JGTSADR INTO @DATA(ld_pv_name3). | ||||
| "SELECT single NAME4 FROM JGTSADR INTO @DATA(ld_pv_name4). | ||||
Search for further information about these or an SAP related objects