SAP ISU_MIBAPI_IMPORT_CHECK Function Module for









ISU_MIBAPI_IMPORT_CHECK is a standard isu mibapi import check 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 isu mibapi import check FM, simply by entering the name ISU_MIBAPI_IMPORT_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_MIBAPI_IMPORT_CHECK 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 'ISU_MIBAPI_IMPORT_CHECK'"
EXPORTING
X_MICC = "
X_MICI = "
X_CNT = "

TABLES
TXY_CONTR = "
TXY_CONTRX = "
TX_ADR = "
TX_ADRX = "

EXCEPTIONS
INPUT_ERROR = 1
.



IMPORTING Parameters details for ISU_MIBAPI_IMPORT_CHECK

X_MICC -

Data type: BAPIISUMOVEINCR_C
Optional: No
Call by Reference: Yes

X_MICI -

Data type: BAPIISUMOVEINCR_I
Optional: No
Call by Reference: Yes

X_CNT -

Data type: BAPIBCONTACT
Optional: No
Call by Reference: Yes

TABLES Parameters details for ISU_MIBAPI_IMPORT_CHECK

TXY_CONTR -

Data type: BAPIISUCONTRACT
Optional: No
Call by Reference: Yes

TXY_CONTRX -

Data type: BAPIISUCONTRACTX
Optional: No
Call by Reference: Yes

TX_ADR -

Data type: BAPIISUBPA
Optional: No
Call by Reference: Yes

TX_ADRX -

Data type: BAPIISUBPAX
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INPUT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_MIBAPI_IMPORT_CHECK 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_x_micc  TYPE BAPIISUMOVEINCR_C, "   
lt_txy_contr  TYPE STANDARD TABLE OF BAPIISUCONTRACT, "   
lv_input_error  TYPE BAPIISUCONTRACT, "   
lv_x_mici  TYPE BAPIISUMOVEINCR_I, "   
lt_txy_contrx  TYPE STANDARD TABLE OF BAPIISUCONTRACTX, "   
lv_x_cnt  TYPE BAPIBCONTACT, "   
lt_tx_adr  TYPE STANDARD TABLE OF BAPIISUBPA, "   
lt_tx_adrx  TYPE STANDARD TABLE OF BAPIISUBPAX. "   

  CALL FUNCTION 'ISU_MIBAPI_IMPORT_CHECK'  "
    EXPORTING
         X_MICC = lv_x_micc
         X_MICI = lv_x_mici
         X_CNT = lv_x_cnt
    TABLES
         TXY_CONTR = lt_txy_contr
         TXY_CONTRX = lt_txy_contrx
         TX_ADR = lt_tx_adr
         TX_ADRX = lt_tx_adrx
    EXCEPTIONS
        INPUT_ERROR = 1
. " ISU_MIBAPI_IMPORT_CHECK




ABAP code using 7.40 inline data declarations to call FM ISU_MIBAPI_IMPORT_CHECK

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.

 
 
 
 
 
 
 
 


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!