SAP FTR_GET_FLOW_FXT Function Module for Read Module for Flows
FTR_GET_FLOW_FXT is a standard ftr get flow fxt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Module for Flows 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 ftr get flow fxt FM, simply by entering the name FTR_GET_FLOW_FXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_BAPI_FLOW_MULTI
Program Name: SAPLFTR_BAPI_FLOW_MULTI
Main Program: SAPLFTR_BAPI_FLOW_MULTI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_GET_FLOW_FXT 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 'FTR_GET_FLOW_FXT'"Read Module for Flows.
EXPORTING
PI_FHA = "CFM: Table Type for VTBFHA
* PI_TAB_VTBFHAZU = "Table Type for VTBFHAZU
* PI_TAB_VTBFHAPO = "Treasury: Table Type for VTBFHAPO
PI_FLOWCONTEXT = "Context of GUI object
* PI_SIDE = '0' "Direction of transaction
* PI_ACTIVE_STATUS_ONLY = 'X' "Checkbox
* PI_PRODUCTCAT = "Product Category
IMPORTING
PE_TAB_FHAPO = "Treasury: Table Type for VTBFHAPO
TABLES
* RETURN = "Return Parameter(s)
* ERRORTAB_FTR_KEYS = "Schlüssel zu fehlerhaften Geschäften
IMPORTING Parameters details for FTR_GET_FLOW_FXT
PI_FHA - CFM: Table Type for VTBFHA
Data type: FTRY_VTBFHAOptional: No
Call by Reference: Yes
PI_TAB_VTBFHAZU - Table Type for VTBFHAZU
Data type: FTR_FHAZUOptional: Yes
Call by Reference: Yes
PI_TAB_VTBFHAPO - Treasury: Table Type for VTBFHAPO
Data type: FTR_FHAPOOptional: Yes
Call by Reference: Yes
PI_FLOWCONTEXT - Context of GUI object
Data type: TB_FTR_GUI_CONTEXTOptional: No
Call by Reference: Yes
PI_SIDE - Direction of transaction
Data type: VTBFHAPO-RKONDGRDefault: '0'
Optional: Yes
Call by Reference: Yes
PI_ACTIVE_STATUS_ONLY - Checkbox
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
PI_PRODUCTCAT - Product Category
Data type: TZAF-SANLFOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FTR_GET_FLOW_FXT
PE_TAB_FHAPO - Treasury: Table Type for VTBFHAPO
Data type: FTR_FHAPOOptional: No
Call by Reference: Yes
TABLES Parameters details for FTR_GET_FLOW_FXT
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
ERRORTAB_FTR_KEYS - Schlüssel zu fehlerhaften Geschäften
Data type: VTS_BAPI_KEY_FTROptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FTR_GET_FLOW_FXT 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_pi_fha | TYPE FTRY_VTBFHA, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_pe_tab_fhapo | TYPE FTR_FHAPO, " | |||
| lv_pi_tab_vtbfhazu | TYPE FTR_FHAZU, " | |||
| lt_errortab_ftr_keys | TYPE STANDARD TABLE OF VTS_BAPI_KEY_FTR, " | |||
| lv_pi_tab_vtbfhapo | TYPE FTR_FHAPO, " | |||
| lv_pi_flowcontext | TYPE TB_FTR_GUI_CONTEXT, " | |||
| lv_pi_side | TYPE VTBFHAPO-RKONDGR, " '0' | |||
| lv_pi_active_status_only | TYPE C, " 'X' | |||
| lv_pi_productcat | TYPE TZAF-SANLF. " |
|   CALL FUNCTION 'FTR_GET_FLOW_FXT' "Read Module for Flows |
| EXPORTING | ||
| PI_FHA | = lv_pi_fha | |
| PI_TAB_VTBFHAZU | = lv_pi_tab_vtbfhazu | |
| PI_TAB_VTBFHAPO | = lv_pi_tab_vtbfhapo | |
| PI_FLOWCONTEXT | = lv_pi_flowcontext | |
| PI_SIDE | = lv_pi_side | |
| PI_ACTIVE_STATUS_ONLY | = lv_pi_active_status_only | |
| PI_PRODUCTCAT | = lv_pi_productcat | |
| IMPORTING | ||
| PE_TAB_FHAPO | = lv_pe_tab_fhapo | |
| TABLES | ||
| RETURN | = lt_return | |
| ERRORTAB_FTR_KEYS | = lt_errortab_ftr_keys | |
| . " FTR_GET_FLOW_FXT | ||
ABAP code using 7.40 inline data declarations to call FM FTR_GET_FLOW_FXT
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.| "SELECT single RKONDGR FROM VTBFHAPO INTO @DATA(ld_pi_side). | ||||
| DATA(ld_pi_side) | = '0'. | |||
| DATA(ld_pi_active_status_only) | = 'X'. | |||
| "SELECT single SANLF FROM TZAF INTO @DATA(ld_pi_productcat). | ||||
Search for further information about these or an SAP related objects