SAP FVD_ADDFLOW_API_CREATE_FLOWS Function Module for Generate Flows Based on Condition Table
FVD_ADDFLOW_API_CREATE_FLOWS is a standard fvd addflow api create flows SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generate Flows Based on Condition Table 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 addflow api create flows FM, simply by entering the name FVD_ADDFLOW_API_CREATE_FLOWS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_ADDFLOW_API
Program Name: SAPLFVD_ADDFLOW_API
Main Program: SAPLFVD_ADDFLOW_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_ADDFLOW_API_CREATE_FLOWS 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_ADDFLOW_API_CREATE_FLOWS'"Generate Flows Based on Condition Table.
EXPORTING
I_LOANFUNC = "Application Subfunction
I_STR_LOAN = "Loan
* I_STR_COND_HEAD = "Condition header
* I_TAB_COND_POS = "Condition Items
* I_TAB_CASHFLOW = "Cash Flow
* I_TAB_DEBITOR = "Business Partner
* I_KEY_DATE = SY-DATUM "Key Date
* I_RBO = "Business operation number (loans)
* I_FLG_CHECK_WAIVE = 'X' "Check Waiver Rule
IMPORTING
E_TAB_FLOWS = "Erzeugte Plan-Bewegungen
EXCEPTIONS
FLOW_TYPE_NOT_FOUND = 1 CONDITION_NOT_FOUND = 2
IMPORTING Parameters details for FVD_ADDFLOW_API_CREATE_FLOWS
I_LOANFUNC - Application Subfunction
Data type: VVSLOANFUNCOptional: No
Call by Reference: Yes
I_STR_LOAN - Loan
Data type: VDARLOptional: No
Call by Reference: Yes
I_STR_COND_HEAD - Condition header
Data type: VZZKOKOOptional: Yes
Call by Reference: Yes
I_TAB_COND_POS - Condition Items
Data type: TRTY_VVZZKOPOOptional: Yes
Call by Reference: Yes
I_TAB_CASHFLOW - Cash Flow
Data type: TRTY_VZZBEPPOptional: Yes
Call by Reference: Yes
I_TAB_DEBITOR - Business Partner
Data type: TRTY_VDGPODEBOptional: Yes
Call by Reference: Yes
I_KEY_DATE - Key Date
Data type: DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: Yes
I_RBO - Business operation number (loans)
Data type: RBOOptional: Yes
Call by Reference: Yes
I_FLG_CHECK_WAIVE - Check Waiver Rule
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FVD_ADDFLOW_API_CREATE_FLOWS
E_TAB_FLOWS - Erzeugte Plan-Bewegungen
Data type: TRTY_RBOBEPPOptional: No
Call by Reference: Yes
EXCEPTIONS details
FLOW_TYPE_NOT_FOUND - keine zugeordnete Bewegung gefunden
Data type:Optional: No
Call by Reference: Yes
CONDITION_NOT_FOUND - keine Kondition in Tableau gefunden
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_ADDFLOW_API_CREATE_FLOWS 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_loanfunc | TYPE VVSLOANFUNC, " | |||
| lv_e_tab_flows | TYPE TRTY_RBOBEPP, " | |||
| lv_flow_type_not_found | TYPE TRTY_RBOBEPP, " | |||
| lv_i_str_loan | TYPE VDARL, " | |||
| lv_condition_not_found | TYPE VDARL, " | |||
| lv_i_str_cond_head | TYPE VZZKOKO, " | |||
| lv_i_tab_cond_pos | TYPE TRTY_VVZZKOPO, " | |||
| lv_i_tab_cashflow | TYPE TRTY_VZZBEPP, " | |||
| lv_i_tab_debitor | TYPE TRTY_VDGPODEB, " | |||
| lv_i_key_date | TYPE DATUM, " SY-DATUM | |||
| lv_i_rbo | TYPE RBO, " | |||
| lv_i_flg_check_waive | TYPE FLAG. " 'X' |
|   CALL FUNCTION 'FVD_ADDFLOW_API_CREATE_FLOWS' "Generate Flows Based on Condition Table |
| EXPORTING | ||
| I_LOANFUNC | = lv_i_loanfunc | |
| I_STR_LOAN | = lv_i_str_loan | |
| I_STR_COND_HEAD | = lv_i_str_cond_head | |
| I_TAB_COND_POS | = lv_i_tab_cond_pos | |
| I_TAB_CASHFLOW | = lv_i_tab_cashflow | |
| I_TAB_DEBITOR | = lv_i_tab_debitor | |
| I_KEY_DATE | = lv_i_key_date | |
| I_RBO | = lv_i_rbo | |
| I_FLG_CHECK_WAIVE | = lv_i_flg_check_waive | |
| IMPORTING | ||
| E_TAB_FLOWS | = lv_e_tab_flows | |
| EXCEPTIONS | ||
| FLOW_TYPE_NOT_FOUND = 1 | ||
| CONDITION_NOT_FOUND = 2 | ||
| . " FVD_ADDFLOW_API_CREATE_FLOWS | ||
ABAP code using 7.40 inline data declarations to call FM FVD_ADDFLOW_API_CREATE_FLOWS
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_key_date) | = SY-DATUM. | |||
| DATA(ld_i_flg_check_waive) | = 'X'. | |||
Search for further information about these or an SAP related objects