SAP ISP_GET_CONFIG_OF_EVENT Function Module for









ISP_GET_CONFIG_OF_EVENT is a standard isp get config of event SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 get config of event FM, simply by entering the name ISP_GET_CONFIG_OF_EVENT into the relevant SAP transaction such as SE37 or SE38.

Function Group: JU00
Program Name: SAPLJU00
Main Program: SAPLJU00
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISP_GET_CONFIG_OF_EVENT 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_GET_CONFIG_OF_EVENT'"
  EXPORTING
*  I_APPKL = 'J' "
*  I_BUKRS = ' ' "
   I_EVENT =  "

 IMPORTING
   E_LOGSYS =  "
   E_MAPN =  "
   E_RFCTYPE =  "
   E_RFNAME =  "
   E_ANWEN =  "

EXCEPTIONS
   NO_ANWEN = 1    NO_RFCDES_FOUND = 2    NO_TJU01_FOUND = 3    NO_TJU03_FOUND = 4    NO_TJU04_FOUND = 5    EXTERNAL_ERROR_IN_ISPAM = 6
.



IMPORTING Parameters details for ISP_GET_CONFIG_OF_EVENT

I_APPKL -

Data type: TJU01-APPKL
Default: 'J'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BUKRS -

Data type: TJU01-BUKRS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_EVENT -

Data type: TJU01-EVENT
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISP_GET_CONFIG_OF_EVENT

E_LOGSYS -

Data type: TJU03-LOGSYS
Optional: No
Call by Reference: No ( called with pass by value option)

E_MAPN -

Data type: TJU01-MAPN
Optional: No
Call by Reference: No ( called with pass by value option)

E_RFCTYPE -

Data type: RFCDES-RFCTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

E_RFNAME -

Data type: TJU01-RFNAME
Optional: No
Call by Reference: No ( called with pass by value option)

E_ANWEN -

Data type: TJU07-ANWEN
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_ANWEN -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_RFCDES_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_TJU01_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_TJU03_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_TJU04_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXTERNAL_ERROR_IN_ISPAM -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISP_GET_CONFIG_OF_EVENT 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_i_appkl  TYPE TJU01-APPKL, "   'J'
lv_e_logsys  TYPE TJU03-LOGSYS, "   
lv_no_anwen  TYPE TJU03, "   
lv_e_mapn  TYPE TJU01-MAPN, "   
lv_i_bukrs  TYPE TJU01-BUKRS, "   SPACE
lv_no_rfcdes_found  TYPE TJU01, "   
lv_i_event  TYPE TJU01-EVENT, "   
lv_e_rfctype  TYPE RFCDES-RFCTYPE, "   
lv_no_tju01_found  TYPE RFCDES, "   
lv_e_rfname  TYPE TJU01-RFNAME, "   
lv_no_tju03_found  TYPE TJU01, "   
lv_e_anwen  TYPE TJU07-ANWEN, "   
lv_no_tju04_found  TYPE TJU07, "   
lv_external_error_in_ispam  TYPE TJU07. "   

  CALL FUNCTION 'ISP_GET_CONFIG_OF_EVENT'  "
    EXPORTING
         I_APPKL = lv_i_appkl
         I_BUKRS = lv_i_bukrs
         I_EVENT = lv_i_event
    IMPORTING
         E_LOGSYS = lv_e_logsys
         E_MAPN = lv_e_mapn
         E_RFCTYPE = lv_e_rfctype
         E_RFNAME = lv_e_rfname
         E_ANWEN = lv_e_anwen
    EXCEPTIONS
        NO_ANWEN = 1
        NO_RFCDES_FOUND = 2
        NO_TJU01_FOUND = 3
        NO_TJU03_FOUND = 4
        NO_TJU04_FOUND = 5
        EXTERNAL_ERROR_IN_ISPAM = 6
. " ISP_GET_CONFIG_OF_EVENT




ABAP code using 7.40 inline data declarations to call FM ISP_GET_CONFIG_OF_EVENT

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 APPKL FROM TJU01 INTO @DATA(ld_i_appkl).
DATA(ld_i_appkl) = 'J'.
 
"SELECT single LOGSYS FROM TJU03 INTO @DATA(ld_e_logsys).
 
 
"SELECT single MAPN FROM TJU01 INTO @DATA(ld_e_mapn).
 
"SELECT single BUKRS FROM TJU01 INTO @DATA(ld_i_bukrs).
DATA(ld_i_bukrs) = ' '.
 
 
"SELECT single EVENT FROM TJU01 INTO @DATA(ld_i_event).
 
"SELECT single RFCTYPE FROM RFCDES INTO @DATA(ld_e_rfctype).
 
 
"SELECT single RFNAME FROM TJU01 INTO @DATA(ld_e_rfname).
 
 
"SELECT single ANWEN FROM TJU07 INTO @DATA(ld_e_anwen).
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!