SAP FMITPOMP_FMITPO_CALL Function Module for









FMITPOMP_FMITPO_CALL is a standard fmitpomp fmitpo call 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 fmitpomp fmitpo call FM, simply by entering the name FMITPOMP_FMITPO_CALL into the relevant SAP transaction such as SE37 or SE38.

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



Function FMITPOMP_FMITPO_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 'FMITPOMP_FMITPO_CALL'"
EXPORTING
I_BUKRS = "
* I_POPUP_NO_SOLL = "
* I_POPUP_NO_RUEL = "
I_GJAHR = "
I_BELNR = "
I_BUZEI = "
* I_POPUP = "
* I_POPUP_NO_BANZ = "
* I_POPUP_NO_UMBU = "
* I_POPUP_NO_ERST = "
* I_POPUP_NO_UMVT = "
.




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_SAPLFMITPOMP_101 Check Sender and Receiver Items
EXIT_SAPLFMITPOMP_801 Check Customer Bank Details

IMPORTING Parameters details for FMITPOMP_FMITPO_CALL

I_BUKRS -

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

I_POPUP_NO_SOLL -

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

I_POPUP_NO_RUEL -

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

I_GJAHR -

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

I_BELNR -

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

I_BUZEI -

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

I_POPUP -

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

I_POPUP_NO_BANZ -

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

I_POPUP_NO_UMBU -

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

I_POPUP_NO_ERST -

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

I_POPUP_NO_UMVT -

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

Copy and paste ABAP code example for FMITPOMP_FMITPO_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_i_bukrs  TYPE BKPF-BUKRS, "   
lv_i_popup_no_soll  TYPE BOOLE-BOOLE, "   
lv_i_popup_no_ruel  TYPE BOOLE-BOOLE, "   
lv_i_gjahr  TYPE BKPF-GJAHR, "   
lv_i_belnr  TYPE BSEG-BELNR, "   
lv_i_buzei  TYPE BSEG-BUZEI, "   
lv_i_popup  TYPE BOOLE-BOOLE, "   
lv_i_popup_no_banz  TYPE BOOLE-BOOLE, "   
lv_i_popup_no_umbu  TYPE BOOLE-BOOLE, "   
lv_i_popup_no_erst  TYPE BOOLE-BOOLE, "   
lv_i_popup_no_umvt  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'FMITPOMP_FMITPO_CALL'  "
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_POPUP_NO_SOLL = lv_i_popup_no_soll
         I_POPUP_NO_RUEL = lv_i_popup_no_ruel
         I_GJAHR = lv_i_gjahr
         I_BELNR = lv_i_belnr
         I_BUZEI = lv_i_buzei
         I_POPUP = lv_i_popup
         I_POPUP_NO_BANZ = lv_i_popup_no_banz
         I_POPUP_NO_UMBU = lv_i_popup_no_umbu
         I_POPUP_NO_ERST = lv_i_popup_no_erst
         I_POPUP_NO_UMVT = lv_i_popup_no_umvt
. " FMITPOMP_FMITPO_CALL




ABAP code using 7.40 inline data declarations to call FM FMITPOMP_FMITPO_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 BUKRS FROM BKPF INTO @DATA(ld_i_bukrs).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_popup_no_soll).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_popup_no_ruel).
 
"SELECT single GJAHR FROM BKPF INTO @DATA(ld_i_gjahr).
 
"SELECT single BELNR FROM BSEG INTO @DATA(ld_i_belnr).
 
"SELECT single BUZEI FROM BSEG INTO @DATA(ld_i_buzei).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_popup).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_popup_no_banz).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_popup_no_umbu).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_popup_no_erst).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_popup_no_umvt).
 


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!