SAP FVD_API_EXP_GET_CASHFLOW Function Module for API: Get Detailed Data for Cash Flow of a Contract
FVD_API_EXP_GET_CASHFLOW is a standard fvd api exp get cashflow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for API: Get Detailed Data for Cash Flow of a 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 api exp get cashflow FM, simply by entering the name FVD_API_EXP_GET_CASHFLOW into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_API_EXP_GET
Program Name: SAPLFVD_API_EXP_GET
Main Program: SAPLFVD_API_EXP_GET
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_API_EXP_GET_CASHFLOW 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_API_EXP_GET_CASHFLOW'"API: Get Detailed Data for Cash Flow of a Contract.
EXPORTING
I_BUKRS = "Company Code
I_RANL = "Contract Number
* I_NO_REVERSED_FLOW = ' ' "Lesen der stornierten Bewegungen: X = Nein
* I_CASHFLOW_CALCULATE = ' ' "Indicator for Calculation of Cash Flow: X = Yes
* I_DISBURSEMENT_SIMULATE = ' ' "Simulation of Full Disbursement: X = Yes
IMPORTING
E_TAB_VDBEKI = "Table Type for Table VDBEKI
E_TAB_VDBEPI = "Table Type for Table VDBEPI
E_TAB_VDBEPP = "Table Type for Table VDBEPP
E_TAB_VZZBEPP = "Table Type for Structure VZZBEPP
E_TAB_VDAUSZ = "Table Type for VDAUSZ (Sorted Table)
EXCEPTIONS
COMPANY_CODE_NOT_FOUND = 1 CONTRACT_NOT_FOUND = 2 SIM_DISBURSE_ERROR = 3 CALCULATION_ERROR = 4
IMPORTING Parameters details for FVD_API_EXP_GET_CASHFLOW
I_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_RANL - Contract Number
Data type: RANLOptional: No
Call by Reference: No ( called with pass by value option)
I_NO_REVERSED_FLOW - Lesen der stornierten Bewegungen: X = Nein
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CASHFLOW_CALCULATE - Indicator for Calculation of Cash Flow: X = Yes
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DISBURSEMENT_SIMULATE - Simulation of Full Disbursement: X = Yes
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_API_EXP_GET_CASHFLOW
E_TAB_VDBEKI - Table Type for Table VDBEKI
Data type: TRTY_VDBEKIOptional: No
Call by Reference: Yes
E_TAB_VDBEPI - Table Type for Table VDBEPI
Data type: TRTY_VDBEPIOptional: No
Call by Reference: Yes
E_TAB_VDBEPP - Table Type for Table VDBEPP
Data type: TRTY_VDBEPPOptional: No
Call by Reference: Yes
E_TAB_VZZBEPP - Table Type for Structure VZZBEPP
Data type: TRTY_VZZBEPPOptional: No
Call by Reference: Yes
E_TAB_VDAUSZ - Table Type for VDAUSZ (Sorted Table)
Data type: TRTY_VDAUSZOptional: No
Call by Reference: Yes
EXCEPTIONS details
COMPANY_CODE_NOT_FOUND - Company Code was not Found
Data type:Optional: No
Call by Reference: Yes
CONTRACT_NOT_FOUND - Contract not found
Data type:Optional: No
Call by Reference: Yes
SIM_DISBURSE_ERROR - Fehler bei der Simulation der Auszahlung
Data type:Optional: No
Call by Reference: Yes
CALCULATION_ERROR - Fehler bei der Finanzstromberechnung
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_API_EXP_GET_CASHFLOW 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_tab_vdbeki | TYPE TRTY_VDBEKI, " | |||
| lv_company_code_not_found | TYPE TRTY_VDBEKI, " | |||
| lv_i_ranl | TYPE RANL, " | |||
| lv_e_tab_vdbepi | TYPE TRTY_VDBEPI, " | |||
| lv_contract_not_found | TYPE TRTY_VDBEPI, " | |||
| lv_e_tab_vdbepp | TYPE TRTY_VDBEPP, " | |||
| lv_i_no_reversed_flow | TYPE XFELD, " SPACE | |||
| lv_sim_disburse_error | TYPE XFELD, " | |||
| lv_e_tab_vzzbepp | TYPE TRTY_VZZBEPP, " | |||
| lv_calculation_error | TYPE TRTY_VZZBEPP, " | |||
| lv_i_cashflow_calculate | TYPE XFELD, " SPACE | |||
| lv_e_tab_vdausz | TYPE TRTY_VDAUSZ, " | |||
| lv_i_disbursement_simulate | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'FVD_API_EXP_GET_CASHFLOW' "API: Get Detailed Data for Cash Flow of a Contract |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RANL | = lv_i_ranl | |
| I_NO_REVERSED_FLOW | = lv_i_no_reversed_flow | |
| I_CASHFLOW_CALCULATE | = lv_i_cashflow_calculate | |
| I_DISBURSEMENT_SIMULATE | = lv_i_disbursement_simulate | |
| IMPORTING | ||
| E_TAB_VDBEKI | = lv_e_tab_vdbeki | |
| E_TAB_VDBEPI | = lv_e_tab_vdbepi | |
| E_TAB_VDBEPP | = lv_e_tab_vdbepp | |
| E_TAB_VZZBEPP | = lv_e_tab_vzzbepp | |
| E_TAB_VDAUSZ | = lv_e_tab_vdausz | |
| EXCEPTIONS | ||
| COMPANY_CODE_NOT_FOUND = 1 | ||
| CONTRACT_NOT_FOUND = 2 | ||
| SIM_DISBURSE_ERROR = 3 | ||
| CALCULATION_ERROR = 4 | ||
| . " FVD_API_EXP_GET_CASHFLOW | ||
ABAP code using 7.40 inline data declarations to call FM FVD_API_EXP_GET_CASHFLOW
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_no_reversed_flow) | = ' '. | |||
| DATA(ld_i_cashflow_calculate) | = ' '. | |||
| DATA(ld_i_disbursement_simulate) | = ' '. | |||
Search for further information about these or an SAP related objects