SAP ISP_ADDRESS_IN_ORDER_EXTEND Function Module for IS-M/SD: Extend Business Partner Address in Order
ISP_ADDRESS_IN_ORDER_EXTEND is a standard isp address in order extend 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: Extend Business Partner Address in 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 address in order extend FM, simply by entering the name ISP_ADDRESS_IN_ORDER_EXTEND into the relevant SAP transaction such as SE37 or SE38.
Function Group: JK24
Program Name: SAPLJK24
Main Program: SAPLJK24
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_ADDRESS_IN_ORDER_EXTEND 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_ADDRESS_IN_ORDER_EXTEND'"IS-M/SD: Extend Business Partner Address in Order.
EXPORTING
GPNR = "Business Partner Number
* GUELTIGBIS = CON_TIME_INFINITY "
* GUELTIGVON = CON_TIME_ZERO "
ROLLE = "Business Partner Role
* XABHOLUNG = ' ' "
* XPOSTVERSAND = 'X' "
LOGADR = "
* ADRESSVAR = "
* XALL_TIME_SLICES = ' ' "Screens, display user entry
TABLES
ORDER_ADDRESS = "
EXCEPTIONS
NO_ADDRESS_FOR_MAILING = 1 NO_DATA_FOUND = 2 NO_PICKUP_POSSIBLE = 3 NO_SELECTION = 4 ADRESSVAR_WRONG = 5 ADDRESS_INCONSISTENT = 6
IMPORTING Parameters details for ISP_ADDRESS_IN_ORDER_EXTEND
GPNR - Business Partner Number
Data type: JKPA-GPNROptional: No
Call by Reference: No ( called with pass by value option)
GUELTIGBIS -
Data type: JKAP-GUELTIGBISDefault: CON_TIME_INFINITY
Optional: Yes
Call by Reference: No ( called with pass by value option)
GUELTIGVON -
Data type: JKAP-GUELTIGVONDefault: CON_TIME_ZERO
Optional: Yes
Call by Reference: No ( called with pass by value option)
ROLLE - Business Partner Role
Data type: JKPA-JPARVWOptional: No
Call by Reference: No ( called with pass by value option)
XABHOLUNG -
Data type: SY-DATARDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
XPOSTVERSAND -
Data type: SY-DATARDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOGADR -
Data type: JGTADRA-LOGADROptional: No
Call by Reference: No ( called with pass by value option)
ADRESSVAR -
Data type: JKPA-ADRESSVAROptional: Yes
Call by Reference: No ( called with pass by value option)
XALL_TIME_SLICES - Screens, display user entry
Data type: SY-DATARDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISP_ADDRESS_IN_ORDER_EXTEND
ORDER_ADDRESS -
Data type: RJK0203Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_ADDRESS_FOR_MAILING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_DATA_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PICKUP_POSSIBLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SELECTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ADRESSVAR_WRONG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ADDRESS_INCONSISTENT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISP_ADDRESS_IN_ORDER_EXTEND 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_gpnr | TYPE JKPA-GPNR, " | |||
| lt_order_address | TYPE STANDARD TABLE OF RJK0203, " | |||
| lv_no_address_for_mailing | TYPE RJK0203, " | |||
| lv_gueltigbis | TYPE JKAP-GUELTIGBIS, " CON_TIME_INFINITY | |||
| lv_no_data_found | TYPE JKAP, " | |||
| lv_gueltigvon | TYPE JKAP-GUELTIGVON, " CON_TIME_ZERO | |||
| lv_no_pickup_possible | TYPE JKAP, " | |||
| lv_rolle | TYPE JKPA-JPARVW, " | |||
| lv_no_selection | TYPE JKPA, " | |||
| lv_xabholung | TYPE SY-DATAR, " ' ' | |||
| lv_adressvar_wrong | TYPE SY, " | |||
| lv_xpostversand | TYPE SY-DATAR, " 'X' | |||
| lv_address_inconsistent | TYPE SY, " | |||
| lv_logadr | TYPE JGTADRA-LOGADR, " | |||
| lv_adressvar | TYPE JKPA-ADRESSVAR, " | |||
| lv_xall_time_slices | TYPE SY-DATAR. " ' ' |
|   CALL FUNCTION 'ISP_ADDRESS_IN_ORDER_EXTEND' "IS-M/SD: Extend Business Partner Address in Order |
| EXPORTING | ||
| GPNR | = lv_gpnr | |
| GUELTIGBIS | = lv_gueltigbis | |
| GUELTIGVON | = lv_gueltigvon | |
| ROLLE | = lv_rolle | |
| XABHOLUNG | = lv_xabholung | |
| XPOSTVERSAND | = lv_xpostversand | |
| LOGADR | = lv_logadr | |
| ADRESSVAR | = lv_adressvar | |
| XALL_TIME_SLICES | = lv_xall_time_slices | |
| TABLES | ||
| ORDER_ADDRESS | = lt_order_address | |
| EXCEPTIONS | ||
| NO_ADDRESS_FOR_MAILING = 1 | ||
| NO_DATA_FOUND = 2 | ||
| NO_PICKUP_POSSIBLE = 3 | ||
| NO_SELECTION = 4 | ||
| ADRESSVAR_WRONG = 5 | ||
| ADDRESS_INCONSISTENT = 6 | ||
| . " ISP_ADDRESS_IN_ORDER_EXTEND | ||
ABAP code using 7.40 inline data declarations to call FM ISP_ADDRESS_IN_ORDER_EXTEND
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 GPNR FROM JKPA INTO @DATA(ld_gpnr). | ||||
| "SELECT single GUELTIGBIS FROM JKAP INTO @DATA(ld_gueltigbis). | ||||
| DATA(ld_gueltigbis) | = CON_TIME_INFINITY. | |||
| "SELECT single GUELTIGVON FROM JKAP INTO @DATA(ld_gueltigvon). | ||||
| DATA(ld_gueltigvon) | = CON_TIME_ZERO. | |||
| "SELECT single JPARVW FROM JKPA INTO @DATA(ld_rolle). | ||||
| "SELECT single DATAR FROM SY INTO @DATA(ld_xabholung). | ||||
| DATA(ld_xabholung) | = ' '. | |||
| "SELECT single DATAR FROM SY INTO @DATA(ld_xpostversand). | ||||
| DATA(ld_xpostversand) | = 'X'. | |||
| "SELECT single LOGADR FROM JGTADRA INTO @DATA(ld_logadr). | ||||
| "SELECT single ADRESSVAR FROM JKPA INTO @DATA(ld_adressvar). | ||||
| "SELECT single DATAR FROM SY INTO @DATA(ld_xall_time_slices). | ||||
| DATA(ld_xall_time_slices) | = ' '. | |||
Search for further information about these or an SAP related objects