SAP FWTR_EXAMPLE_ADD_FLOW Function Module for Example of Event after Cash Flow Calculation









FWTR_EXAMPLE_ADD_FLOW is a standard fwtr example add flow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Example of Event after Cash Flow Calculation 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 fwtr example add flow FM, simply by entering the name FWTR_EXAMPLE_ADD_FLOW into the relevant SAP transaction such as SE37 or SE38.

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



Function FWTR_EXAMPLE_ADD_FLOW 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 'FWTR_EXAMPLE_ADD_FLOW'"Example of Event after Cash Flow Calculation
EXPORTING
I_MODE = "Processing Mode
I_TRANSACTION = "Transaction from Securities View
I_ACTIVITY = "Transaction Activity from Securities View
I_MAIN_FLOW = "Financial Flows from Securities View
I_CLASS_DATA = "Asset Master for Securities
I_TAB_ADD_FLOWS = "Tabelle mit Zusatzbewegungen
I_COND_HD_BOND = "Table Condition Header
I_COND_HD_STOCK = "Condition header for stock, subscrip.rights, investments
I_COND_POS = "Condition Items

CHANGING
C_TAB_USER_FLOWS = "Tabelle mit benutzerdefinierten Bewegungen
.



IMPORTING Parameters details for FWTR_EXAMPLE_ADD_FLOW

I_MODE - Processing Mode

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

I_TRANSACTION - Transaction from Securities View

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

I_ACTIVITY - Transaction Activity from Securities View

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

I_MAIN_FLOW - Financial Flows from Securities View

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

I_CLASS_DATA - Asset Master for Securities

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

I_TAB_ADD_FLOWS - Tabelle mit Zusatzbewegungen

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

I_COND_HD_BOND - Table Condition Header

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

I_COND_HD_STOCK - Condition header for stock, subscrip.rights, investments

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

I_COND_POS - Condition Items

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

CHANGING Parameters details for FWTR_EXAMPLE_ADD_FLOW

C_TAB_USER_FLOWS - Tabelle mit benutzerdefinierten Bewegungen

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

Copy and paste ABAP code example for FWTR_EXAMPLE_ADD_FLOW 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_mode  TYPE C, "   
lv_c_tab_user_flows  TYPE FTRTR_TAB_FHAPO, "   
lv_i_transaction  TYPE VWSFHA, "   
lv_i_activity  TYPE VWSFHAZU, "   
lv_i_main_flow  TYPE VWSFHAPO, "   
lv_i_class_data  TYPE VWPANLA, "   
lv_i_tab_add_flows  TYPE FTRTR_TAB_FHAPO, "   
lv_i_cond_hd_bond  TYPE VZZKOKO, "   
lv_i_cond_hd_stock  TYPE VZSKOKO, "   
lv_i_cond_pos  TYPE TRPM_IT_VVZZKOPO. "   

  CALL FUNCTION 'FWTR_EXAMPLE_ADD_FLOW'  "Example of Event after Cash Flow Calculation
    EXPORTING
         I_MODE = lv_i_mode
         I_TRANSACTION = lv_i_transaction
         I_ACTIVITY = lv_i_activity
         I_MAIN_FLOW = lv_i_main_flow
         I_CLASS_DATA = lv_i_class_data
         I_TAB_ADD_FLOWS = lv_i_tab_add_flows
         I_COND_HD_BOND = lv_i_cond_hd_bond
         I_COND_HD_STOCK = lv_i_cond_hd_stock
         I_COND_POS = lv_i_cond_pos
    CHANGING
         C_TAB_USER_FLOWS = lv_c_tab_user_flows
. " FWTR_EXAMPLE_ADD_FLOW




ABAP code using 7.40 inline data declarations to call FM FWTR_EXAMPLE_ADD_FLOW

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!