SAP ISP_NAME_READ_FOR_ORDER Function Module for IS-M: Determine BP Name and Address for Order
ISP_NAME_READ_FOR_ORDER is a standard isp name read for order 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: Determine BP Name and Address for Order 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 name read for order FM, simply by entering the name ISP_NAME_READ_FOR_ORDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: JG04
Program Name: SAPLJG04
Main Program: SAPLJG04
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_NAME_READ_FOR_ORDER 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_NAME_READ_FOR_ORDER'"IS-M: Determine BP Name and Address for Order.
EXPORTING
* ADRNR_IN = "
* ANREDE_IN_NAMELANG = "
* GPNR_IN = "
* XFORCE_SELECT_JGTSADR = "
* XFORCE_SELECT_JGTADRA = CON_ANGEKREUZT "
IMPORTING
NAMEKURZ = "
NAMELANG = "
SADRWA_OUT = "
EXCEPTIONS
ADDRESS_NOT_FOUND = 1 GP_NOT_FOUND = 2 MISSING_INPUT = 3
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_SAPLJG04_002 IS-M/SD: Fill Business Partner SORTL
IMPORTING Parameters details for ISP_NAME_READ_FOR_ORDER
ADRNR_IN -
Data type: JGTSADR-ADRNROptional: Yes
Call by Reference: No ( called with pass by value option)
ANREDE_IN_NAMELANG -
Data type: SY-DATAROptional: Yes
Call by Reference: No ( called with pass by value option)
GPNR_IN -
Data type: JGTGPNR-GPNROptional: Yes
Call by Reference: No ( called with pass by value option)
XFORCE_SELECT_JGTSADR -
Data type: XFELDOptional: Yes
Call by Reference: Yes
XFORCE_SELECT_JGTADRA -
Data type: XFELDDefault: CON_ANGEKREUZT
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISP_NAME_READ_FOR_ORDER
NAMEKURZ -
Data type: RJG0103-NAMEKURZOptional: No
Call by Reference: No ( called with pass by value option)
NAMELANG -
Data type: RJG0103-NAMELANGOptional: No
Call by Reference: No ( called with pass by value option)
SADRWA_OUT -
Data type: JGTSADROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ADDRESS_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GP_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MISSING_INPUT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_NAME_READ_FOR_ORDER 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_adrnr_in | TYPE JGTSADR-ADRNR, " | |||
| lv_namekurz | TYPE RJG0103-NAMEKURZ, " | |||
| lv_address_not_found | TYPE RJG0103, " | |||
| lv_namelang | TYPE RJG0103-NAMELANG, " | |||
| lv_gp_not_found | TYPE RJG0103, " | |||
| lv_anrede_in_namelang | TYPE SY-DATAR, " | |||
| lv_gpnr_in | TYPE JGTGPNR-GPNR, " | |||
| lv_sadrwa_out | TYPE JGTSADR, " | |||
| lv_missing_input | TYPE JGTSADR, " | |||
| lv_xforce_select_jgtsadr | TYPE XFELD, " | |||
| lv_xforce_select_jgtadra | TYPE XFELD. " CON_ANGEKREUZT |
|   CALL FUNCTION 'ISP_NAME_READ_FOR_ORDER' "IS-M: Determine BP Name and Address for Order |
| EXPORTING | ||
| ADRNR_IN | = lv_adrnr_in | |
| ANREDE_IN_NAMELANG | = lv_anrede_in_namelang | |
| GPNR_IN | = lv_gpnr_in | |
| XFORCE_SELECT_JGTSADR | = lv_xforce_select_jgtsadr | |
| XFORCE_SELECT_JGTADRA | = lv_xforce_select_jgtadra | |
| IMPORTING | ||
| NAMEKURZ | = lv_namekurz | |
| NAMELANG | = lv_namelang | |
| SADRWA_OUT | = lv_sadrwa_out | |
| EXCEPTIONS | ||
| ADDRESS_NOT_FOUND = 1 | ||
| GP_NOT_FOUND = 2 | ||
| MISSING_INPUT = 3 | ||
| . " ISP_NAME_READ_FOR_ORDER | ||
ABAP code using 7.40 inline data declarations to call FM ISP_NAME_READ_FOR_ORDER
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 ADRNR FROM JGTSADR INTO @DATA(ld_adrnr_in). | ||||
| "SELECT single NAMEKURZ FROM RJG0103 INTO @DATA(ld_namekurz). | ||||
| "SELECT single NAMELANG FROM RJG0103 INTO @DATA(ld_namelang). | ||||
| "SELECT single DATAR FROM SY INTO @DATA(ld_anrede_in_namelang). | ||||
| "SELECT single GPNR FROM JGTGPNR INTO @DATA(ld_gpnr_in). | ||||
| DATA(ld_xforce_select_jgtadra) | = CON_ANGEKREUZT. | |||
Search for further information about these or an SAP related objects