SAP OPEN_FI_PERFORM_00001825_P Function Module for









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

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



Function OPEN_FI_PERFORM_00001825_P 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_00001825_P'"
  EXPORTING
   I_BUKRS =  "Company Code
   I_VERTN =  "Contract Number
   I_VBEWA =  "Transaction Type
   I_BELNR =  "Accounting Document Number
   I_GJAHR =  "Fiscal Year
   I_BUZEI =  "Line Item Number Within the Accounting Document
   I_BVTYP =  "Partner Bank Type
*  I_ZBNKS =  "Country Key
*  I_ZBNKY =  "Bank key of the payee's bank
*  I_ZBNKN =  "Bank Account Number of the Payee
   I_VERTT =  "Contract Type

 IMPORTING
   E_REF_TYPE =  "
   E_REF_ID =  "
   E_MNDID =  "SEPA Mandate: Unique Reference to Mandate per Vendor

EXCEPTIONS
   NO_UNIQUE_RESULT = 1
.



IMPORTING Parameters details for OPEN_FI_PERFORM_00001825_P

I_BUKRS - Company Code

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

I_VERTN - Contract Number

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

I_VBEWA - Transaction Type

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

I_BELNR - Accounting Document Number

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

I_GJAHR - Fiscal Year

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

I_BUZEI - Line Item Number Within the Accounting Document

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

I_BVTYP - Partner Bank Type

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

I_ZBNKS - Country Key

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

I_ZBNKY - Bank key of the payee's bank

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

I_ZBNKN - Bank Account Number of the Payee

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

I_VERTT - Contract Type

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

EXPORTING Parameters details for OPEN_FI_PERFORM_00001825_P

E_REF_TYPE -

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

E_REF_ID -

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

E_MNDID - SEPA Mandate: Unique Reference to Mandate per Vendor

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

EXCEPTIONS details

NO_UNIQUE_RESULT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OPEN_FI_PERFORM_00001825_P 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 BUKRS, "   
lv_e_ref_type  TYPE SEPA_REF_TYPE, "   
lv_no_unique_result  TYPE SEPA_REF_TYPE, "   
lv_i_vertn  TYPE RANL, "   
lv_i_vbewa  TYPE SBEWART, "   
lv_i_belnr  TYPE BELNR_D, "   
lv_e_ref_id  TYPE SEPA_REF_ID, "   
lv_e_mndid  TYPE SEPA_MNDID, "   
lv_i_gjahr  TYPE GJAHR, "   
lv_i_buzei  TYPE BUZEI, "   
lv_i_bvtyp  TYPE BVTYP, "   
lv_i_zbnks  TYPE DZBNKS, "   
lv_i_zbnky  TYPE DZBNKY, "   
lv_i_zbnkn  TYPE DZBNKN, "   
lv_i_vertt  TYPE RANTYP. "   

  CALL FUNCTION 'OPEN_FI_PERFORM_00001825_P'  "
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_VERTN = lv_i_vertn
         I_VBEWA = lv_i_vbewa
         I_BELNR = lv_i_belnr
         I_GJAHR = lv_i_gjahr
         I_BUZEI = lv_i_buzei
         I_BVTYP = lv_i_bvtyp
         I_ZBNKS = lv_i_zbnks
         I_ZBNKY = lv_i_zbnky
         I_ZBNKN = lv_i_zbnkn
         I_VERTT = lv_i_vertt
    IMPORTING
         E_REF_TYPE = lv_e_ref_type
         E_REF_ID = lv_e_ref_id
         E_MNDID = lv_e_mndid
    EXCEPTIONS
        NO_UNIQUE_RESULT = 1
. " OPEN_FI_PERFORM_00001825_P




ABAP code using 7.40 inline data declarations to call FM OPEN_FI_PERFORM_00001825_P

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!