SAP ISP_TECH_SYSTEM_START_CALL Function Module for IS-M/AM: Access RFC Function Module ISP_TECH_SYSTEM_START
ISP_TECH_SYSTEM_START_CALL is a standard isp tech system start call 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: Access RFC Function Module ISP_TECH_SYSTEM_START 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 tech system start call FM, simply by entering the name ISP_TECH_SYSTEM_START_CALL into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHTS
Program Name: SAPLJHTS
Main Program: SAPLJHTS
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_TECH_SYSTEM_START_CALL 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_TECH_SYSTEM_START_CALL'"IS-M/AM: Access RFC Function Module ISP_TECH_SYSTEM_START.
EXPORTING
* PAR_RJHABILOZ_ITAB = "
* PAR_RJHAK = "
* PAR_RJHATRZ_ITAB = "
* PAR_RJHAPLZ_ITAB = "
* PAR_RJHAUA_ITAB = "
* PAR_RJHAE_ITAB = "
X_CALL_DESIGNER = "
* PAR_RJHAISZ_ITAB = "
* PAR_RJHABPZ_ITAB = "
* PAR_RJHAEA_ITAB = "
* PAR_RJHADRV_ITAB = "
* PAR_RJHADRVA_ITAB = "
* PAR_RJHAMOZ_ITAB = "
* PAR_RJHAP = "
* PAR_RJHAPA = "
CHANGING
* PAR_RJHAMOT = "
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_SAPLJHTS_001 IS-M/AM: Check Whether Item Represents a Page-Defining Ad
EXIT_SAPLJHTS_002 IS-M/AM: Typing of Ads for Positioning System
EXIT_SAPLJHTS_003 IS-M/AM: Line Type Conversion in the Technical System
EXIT_SAPLJHTS_004 IS-M/AM: Word Type Conversion in the Technical System
EXIT_SAPLJHTS_005 IS-M/AM: Fill Structure RJHATMO for the Technical Interface
EXIT_SAPLJHTS_006 IS-M/AM: Fill Structure RJHATPAP for the Technical Interface
EXIT_SAPLJHTS_007 IS-M/AM: Fill Structure RJHATPAK for the Technical Interface
EXIT_SAPLJHTS_008 IS-M/AM: Fill Structure RJHATPS for the Technical Interface
EXIT_SAPLJHTS_009 IS-M/AM: Fill Structure RJHATBPZ for the Technical Interface
EXIT_SAPLJHTS_010 IS-M/AM: Fill Structure RJHATISZ for the Technical Interface
EXIT_SAPLJHTS_011 IS-M/AM: Fill Structure RJHATPLZA for the Technical Interface
EXIT_SAPLJHTS_012 IS-M/AM: Fill Structure RJHATPLZ for the Technical Interface
EXIT_SAPLJHTS_013 IS-M/AM: Read Structure RJHATMO from the Technical Interface
EXIT_SAPLJHTS_014 IS-M/AM: Provide Fields During External Order Transfer
EXIT_SAPLJHTS_015 IS-M/AM: Evaluate Message Returned by the Positioning System
EXIT_SAPLJHTS_016 IS-M/AM: Fill Structure RJHATSTAT for the Technical Interface
EXIT_SAPLJHTS_017 IS-M/AM: Fill Structure RJHATPRF for the Technical Interface
EXIT_SAPLJHTS_018
EXIT_SAPLJHTS_019 IS-M/AM: Read Structure RJHATSTAT from the Technical Interface
EXIT_SAPLJHTS_020 IS-M/AM: Read Structure RJHATPAP from the Technical Interface
EXIT_SAPLJHTS_021 IS-M/AM: Read Structure RJHATPSI from the Technical Interface
IMPORTING Parameters details for ISP_TECH_SYSTEM_START_CALL
PAR_RJHABILOZ_ITAB -
Data type: JHA1_RJHABILOZ_TABOptional: Yes
Call by Reference: Yes
PAR_RJHAK -
Data type: JHA1_RJHAK_STROptional: Yes
Call by Reference: Yes
PAR_RJHATRZ_ITAB -
Data type: JHA1_RJHATRZ_TABOptional: Yes
Call by Reference: Yes
PAR_RJHAPLZ_ITAB -
Data type: JHA1_RJHAPLZ_TABOptional: Yes
Call by Reference: Yes
PAR_RJHAUA_ITAB -
Data type: JHA1_RJHAUA_TABOptional: Yes
Call by Reference: Yes
PAR_RJHAE_ITAB -
Data type: JHA1_RJHAE_TABOptional: Yes
Call by Reference: Yes
X_CALL_DESIGNER -
Data type: SY-BATCHOptional: No
Call by Reference: No ( called with pass by value option)
PAR_RJHAISZ_ITAB -
Data type: JHA1_RJHAISZ_TABOptional: Yes
Call by Reference: Yes
PAR_RJHABPZ_ITAB -
Data type: JHA1_RJHABPZ_TABOptional: Yes
Call by Reference: Yes
PAR_RJHAEA_ITAB -
Data type: JHA1_RJHAEA_TABOptional: Yes
Call by Reference: Yes
PAR_RJHADRV_ITAB -
Data type: JHA1_RJHADRV_TABOptional: Yes
Call by Reference: Yes
PAR_RJHADRVA_ITAB -
Data type: JHA1_RJHADRVA_TABOptional: Yes
Call by Reference: Yes
PAR_RJHAMOZ_ITAB -
Data type: JHA1_RJHAMOZ_TABOptional: Yes
Call by Reference: Yes
PAR_RJHAP -
Data type: JHA1_RJHAP_STROptional: Yes
Call by Reference: Yes
PAR_RJHAPA -
Data type: JHA1_RJHAPA_STROptional: Yes
Call by Reference: Yes
CHANGING Parameters details for ISP_TECH_SYSTEM_START_CALL
PAR_RJHAMOT -
Data type: JHA1_RJHAMOT_STROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_TECH_SYSTEM_START_CALL 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_par_rjhamot | TYPE JHA1_RJHAMOT_STR, " | |||
| lv_par_rjhabiloz_itab | TYPE JHA1_RJHABILOZ_TAB, " | |||
| lv_par_rjhak | TYPE JHA1_RJHAK_STR, " | |||
| lv_par_rjhatrz_itab | TYPE JHA1_RJHATRZ_TAB, " | |||
| lv_par_rjhaplz_itab | TYPE JHA1_RJHAPLZ_TAB, " | |||
| lv_par_rjhaua_itab | TYPE JHA1_RJHAUA_TAB, " | |||
| lv_par_rjhae_itab | TYPE JHA1_RJHAE_TAB, " | |||
| lv_x_call_designer | TYPE SY-BATCH, " | |||
| lv_par_rjhaisz_itab | TYPE JHA1_RJHAISZ_TAB, " | |||
| lv_par_rjhabpz_itab | TYPE JHA1_RJHABPZ_TAB, " | |||
| lv_par_rjhaea_itab | TYPE JHA1_RJHAEA_TAB, " | |||
| lv_par_rjhadrv_itab | TYPE JHA1_RJHADRV_TAB, " | |||
| lv_par_rjhadrva_itab | TYPE JHA1_RJHADRVA_TAB, " | |||
| lv_par_rjhamoz_itab | TYPE JHA1_RJHAMOZ_TAB, " | |||
| lv_par_rjhap | TYPE JHA1_RJHAP_STR, " | |||
| lv_par_rjhapa | TYPE JHA1_RJHAPA_STR. " |
|   CALL FUNCTION 'ISP_TECH_SYSTEM_START_CALL' "IS-M/AM: Access RFC Function Module ISP_TECH_SYSTEM_START |
| EXPORTING | ||
| PAR_RJHABILOZ_ITAB | = lv_par_rjhabiloz_itab | |
| PAR_RJHAK | = lv_par_rjhak | |
| PAR_RJHATRZ_ITAB | = lv_par_rjhatrz_itab | |
| PAR_RJHAPLZ_ITAB | = lv_par_rjhaplz_itab | |
| PAR_RJHAUA_ITAB | = lv_par_rjhaua_itab | |
| PAR_RJHAE_ITAB | = lv_par_rjhae_itab | |
| X_CALL_DESIGNER | = lv_x_call_designer | |
| PAR_RJHAISZ_ITAB | = lv_par_rjhaisz_itab | |
| PAR_RJHABPZ_ITAB | = lv_par_rjhabpz_itab | |
| PAR_RJHAEA_ITAB | = lv_par_rjhaea_itab | |
| PAR_RJHADRV_ITAB | = lv_par_rjhadrv_itab | |
| PAR_RJHADRVA_ITAB | = lv_par_rjhadrva_itab | |
| PAR_RJHAMOZ_ITAB | = lv_par_rjhamoz_itab | |
| PAR_RJHAP | = lv_par_rjhap | |
| PAR_RJHAPA | = lv_par_rjhapa | |
| CHANGING | ||
| PAR_RJHAMOT | = lv_par_rjhamot | |
| . " ISP_TECH_SYSTEM_START_CALL | ||
ABAP code using 7.40 inline data declarations to call FM ISP_TECH_SYSTEM_START_CALL
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 BATCH FROM SY INTO @DATA(ld_x_call_designer). | ||||
Search for further information about these or an SAP related objects