SAP OPEN_FI_PERFORM_00001720_E Function Module for









OPEN_FI_PERFORM_00001720_E is a standard open fi perform 00001720 e 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 open fi perform 00001720 e FM, simply by entering the name OPEN_FI_PERFORM_00001720_E into the relevant SAP transaction such as SE37 or SE38.

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



Function OPEN_FI_PERFORM_00001720_E 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 'OPEN_FI_PERFORM_00001720_E'"
  EXPORTING
   I_MAHNV =  "Current Dunning Run
   I_F150V =  "Work Fields for Dunning Run
   I_MHNK =  "Header Data of Dunning Run
   I_ITCPO =  "Print Parameter
   I_UPDATE =  "Test Run/Update Run
   I_MOUT =  "
   I_OFI =  "

 IMPORTING
   E_FUNCTION_CALLED =  "Function Name

CHANGING
   E_COMREQ =  "
   E_RETCODE =  "

TABLES
   T_MHND =  "Dunning Data
   T_FIMSG =  "
.



IMPORTING Parameters details for OPEN_FI_PERFORM_00001720_E

I_MAHNV - Current Dunning Run

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

I_F150V - Work Fields for Dunning Run

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

I_MHNK - Header Data of Dunning Run

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

I_ITCPO - Print Parameter

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

I_UPDATE - Test Run/Update Run

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

I_MOUT -

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

I_OFI -

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

EXPORTING Parameters details for OPEN_FI_PERFORM_00001720_E

E_FUNCTION_CALLED - Function Name

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

CHANGING Parameters details for OPEN_FI_PERFORM_00001720_E

E_COMREQ -

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

E_RETCODE -

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

TABLES Parameters details for OPEN_FI_PERFORM_00001720_E

T_MHND - Dunning Data

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

T_FIMSG -

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

Copy and paste ABAP code example for OPEN_FI_PERFORM_00001720_E 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:
lt_t_mhnd  TYPE STANDARD TABLE OF MHND, "   
lv_i_mahnv  TYPE MAHNV, "   
lv_e_comreq  TYPE BOOLE-BOOLE, "   
lv_e_function_called  TYPE FUNCNAME, "   
lv_i_f150v  TYPE F150V, "   
lt_t_fimsg  TYPE STANDARD TABLE OF FIMSG, "   
lv_e_retcode  TYPE C, "   
lv_i_mhnk  TYPE MHNK, "   
lv_i_itcpo  TYPE ITCPO, "   
lv_i_update  TYPE BOOLE-BOOLE, "   
lv_i_mout  TYPE BOOLE-BOOLE, "   
lv_i_ofi  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'OPEN_FI_PERFORM_00001720_E'  "
    EXPORTING
         I_MAHNV = lv_i_mahnv
         I_F150V = lv_i_f150v
         I_MHNK = lv_i_mhnk
         I_ITCPO = lv_i_itcpo
         I_UPDATE = lv_i_update
         I_MOUT = lv_i_mout
         I_OFI = lv_i_ofi
    IMPORTING
         E_FUNCTION_CALLED = lv_e_function_called
    CHANGING
         E_COMREQ = lv_e_comreq
         E_RETCODE = lv_e_retcode
    TABLES
         T_MHND = lt_t_mhnd
         T_FIMSG = lt_t_fimsg
. " OPEN_FI_PERFORM_00001720_E




ABAP code using 7.40 inline data declarations to call FM OPEN_FI_PERFORM_00001720_E

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 BOOLE FROM BOOLE INTO @DATA(ld_e_comreq).
 
 
 
 
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_update).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_mout).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_ofi).
 


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!