SAP FVD_IA_IF_PAY_ON_REQUEST Function Module for Payment on Request for Investor Contract
FVD_IA_IF_PAY_ON_REQUEST is a standard fvd ia if pay on request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Payment on Request for Investor Contract processing and below is the pattern details for this FM, 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 fvd ia if pay on request FM, simply by entering the name FVD_IA_IF_PAY_ON_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_IA_INTERFACE
Program Name: SAPLFVD_IA_INTERFACE
Main Program: SAPLFVD_IA_INTERFACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FVD_IA_IF_PAY_ON_REQUEST 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 'FVD_IA_IF_PAY_ON_REQUEST'"Payment on Request for Investor Contract.
EXPORTING
I_COMP_CODE = "Company Code
I_CONTRACT_NO = "Contract Number
I_AMOUNT = "Amount in Document Currency
* I_DATE_TO = "Date in CHAR format
* I_CURRENCY = 'EUR' "Currency Key
* I_FLG_TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs
IMPORTING
E_FLG_ERROR = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
E_TAB_BAPIRET2 = "Table with BAPI Return Information
IMPORTING Parameters details for FVD_IA_IF_PAY_ON_REQUEST
I_COMP_CODE - Company Code
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_CONTRACT_NO - Contract Number
Data type: RANLOptional: No
Call by Reference: No ( called with pass by value option)
I_AMOUNT - Amount in Document Currency
Data type: WRBTROptional: No
Call by Reference: No ( called with pass by value option)
I_DATE_TO - Date in CHAR format
Data type: DATSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CURRENCY - Currency Key
Data type: WAERSDefault: 'EUR'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_TESTRUN - Switch to Simulation Mode for Write BAPIs
Data type: TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_IA_IF_PAY_ON_REQUEST
E_FLG_ERROR - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_BAPIRET2 - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVD_IA_IF_PAY_ON_REQUEST 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_e_flg_error | TYPE BOOLE_D, " | |||
| lv_i_comp_code | TYPE BUKRS, " | |||
| lv_i_contract_no | TYPE RANL, " | |||
| lv_e_tab_bapiret2 | TYPE BAPIRETTAB, " | |||
| lv_i_amount | TYPE WRBTR, " | |||
| lv_i_date_to | TYPE DATS, " | |||
| lv_i_currency | TYPE WAERS, " 'EUR' | |||
| lv_i_flg_testrun | TYPE TESTRUN. " SPACE |
|   CALL FUNCTION 'FVD_IA_IF_PAY_ON_REQUEST' "Payment on Request for Investor Contract |
| EXPORTING | ||
| I_COMP_CODE | = lv_i_comp_code | |
| I_CONTRACT_NO | = lv_i_contract_no | |
| I_AMOUNT | = lv_i_amount | |
| I_DATE_TO | = lv_i_date_to | |
| I_CURRENCY | = lv_i_currency | |
| I_FLG_TESTRUN | = lv_i_flg_testrun | |
| IMPORTING | ||
| E_FLG_ERROR | = lv_e_flg_error | |
| E_TAB_BAPIRET2 | = lv_e_tab_bapiret2 | |
| . " FVD_IA_IF_PAY_ON_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM FVD_IA_IF_PAY_ON_REQUEST
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.| DATA(ld_i_currency) | = 'EUR'. | |||
| DATA(ld_i_flg_testrun) | = ' '. | |||
Search for further information about these or an SAP related objects