SAP ISM_INTERFACE_00001030 Function Module for









ISM_INTERFACE_00001030 is a standard ism interface 00001030 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 ism interface 00001030 FM, simply by entering the name ISM_INTERFACE_00001030 into the relevant SAP transaction such as SE37 or SE38.

Function Group: JKRENEW_FI
Program Name: SAPLJKRENEW_FI
Main Program: SAPLJKRENEW_FI
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISM_INTERFACE_00001030 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_INTERFACE_00001030'"
  EXPORTING
   I_BKDF =  "
   I_UF05A =  "
*  I_XVBUP = 'X' "

TABLES
*  T_AUSZ1 =  "
   T_BSEU =  "
*  T_AUSZ2 =  "
*  T_AUSZ3 =  "
   T_BKP1 =  "
   T_BKPF =  "
   T_BSEC =  "
   T_BSED =  "
   T_BSEG =  "
   T_BSET =  "
.




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_SAPLJKRENEW_FI_001 Check Incoming Payment for IS-M Relevancy

IMPORTING Parameters details for ISM_INTERFACE_00001030

I_BKDF -

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

I_UF05A -

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

I_XVBUP -

Data type: OFIWA-XVBUP
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ISM_INTERFACE_00001030

T_AUSZ1 -

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

T_BSEU -

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

T_AUSZ2 -

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

T_AUSZ3 -

Data type: AUSZ_CLR
Optional: Yes
Call by Reference: Yes

T_BKP1 -

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

T_BKPF -

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

T_BSEC -

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

T_BSED -

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

T_BSEG -

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

T_BSET -

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

Copy and paste ABAP code example for ISM_INTERFACE_00001030 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_bkdf  TYPE BKDF, "   
lt_t_ausz1  TYPE STANDARD TABLE OF AUSZ1, "   
lt_t_bseu  TYPE STANDARD TABLE OF BSEU, "   
lv_i_uf05a  TYPE UF05A, "   
lt_t_ausz2  TYPE STANDARD TABLE OF AUSZ2, "   
lv_i_xvbup  TYPE OFIWA-XVBUP, "   'X'
lt_t_ausz3  TYPE STANDARD TABLE OF AUSZ_CLR, "   
lt_t_bkp1  TYPE STANDARD TABLE OF BKP1, "   
lt_t_bkpf  TYPE STANDARD TABLE OF BKPF, "   
lt_t_bsec  TYPE STANDARD TABLE OF BSEC, "   
lt_t_bsed  TYPE STANDARD TABLE OF BSED, "   
lt_t_bseg  TYPE STANDARD TABLE OF BSEG, "   
lt_t_bset  TYPE STANDARD TABLE OF BSET. "   

  CALL FUNCTION 'ISM_INTERFACE_00001030'  "
    EXPORTING
         I_BKDF = lv_i_bkdf
         I_UF05A = lv_i_uf05a
         I_XVBUP = lv_i_xvbup
    TABLES
         T_AUSZ1 = lt_t_ausz1
         T_BSEU = lt_t_bseu
         T_AUSZ2 = lt_t_ausz2
         T_AUSZ3 = lt_t_ausz3
         T_BKP1 = lt_t_bkp1
         T_BKPF = lt_t_bkpf
         T_BSEC = lt_t_bsec
         T_BSED = lt_t_bsed
         T_BSEG = lt_t_bseg
         T_BSET = lt_t_bset
. " ISM_INTERFACE_00001030




ABAP code using 7.40 inline data declarations to call FM ISM_INTERFACE_00001030

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 XVBUP FROM OFIWA INTO @DATA(ld_i_xvbup).
DATA(ld_i_xvbup) = 'X'.
 
 
 
 
 
 
 
 


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!