SAP FTR_GET_DATA Function Module for Read Financial Transaction from the Database
FTR_GET_DATA is a standard ftr get data 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 Financial Transaction from the Database 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 data FM, simply by entering the name FTR_GET_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_02
Program Name: SAPLFTR_02
Main Program: SAPLFTR_02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_GET_DATA 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_DATA'"Read Financial Transaction from the Database.
EXPORTING
I_TAB_KEY_FHA = "Geschäftsschlüssel
IMPORTING
E_TAB_FHA = "Transaction
E_TAB_FHAZU = "Activity
E_TAB_FINKO = "Condition
E_TAB_AFINKO = "Alternativ-Kondition
E_TAB_FHAPO = "Flow
E_TAB_FHAPO_UNFIXED = "Plan-Bewegung
E_TAB_ZV = "Payment Details
E_TAB_KORES = "Correspondence
E_TAB_RATING = "Rating
IMPORTING Parameters details for FTR_GET_DATA
I_TAB_KEY_FHA - Geschäftsschlüssel
Data type: FTRTR_TAB_KEY_FHAOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FTR_GET_DATA
E_TAB_FHA - Transaction
Data type: FTRTR_TAB_FHAOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_FHAZU - Activity
Data type: FTRTR_TAB_FHAZUOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_FINKO - Condition
Data type: FTRTR_TAB_FINKOOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_AFINKO - Alternativ-Kondition
Data type: FTRTR_TAB_AFINKOOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_FHAPO - Flow
Data type: FTRTR_TAB_FHAPOOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_FHAPO_UNFIXED - Plan-Bewegung
Data type: FTRTR_TAB_FHAPO_UNFOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_ZV - Payment Details
Data type: FTRTR_TAB_ZVOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_KORES - Correspondence
Data type: FTRTR_TAB_KORESOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_RATING - Rating
Data type: FTRTR_TAB_RATINGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTR_GET_DATA 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_tab_fha | TYPE FTRTR_TAB_FHA, " | |||
| lv_i_tab_key_fha | TYPE FTRTR_TAB_KEY_FHA, " | |||
| lv_e_tab_fhazu | TYPE FTRTR_TAB_FHAZU, " | |||
| lv_e_tab_finko | TYPE FTRTR_TAB_FINKO, " | |||
| lv_e_tab_afinko | TYPE FTRTR_TAB_AFINKO, " | |||
| lv_e_tab_fhapo | TYPE FTRTR_TAB_FHAPO, " | |||
| lv_e_tab_fhapo_unfixed | TYPE FTRTR_TAB_FHAPO_UNF, " | |||
| lv_e_tab_zv | TYPE FTRTR_TAB_ZV, " | |||
| lv_e_tab_kores | TYPE FTRTR_TAB_KORES, " | |||
| lv_e_tab_rating | TYPE FTRTR_TAB_RATING. " |
|   CALL FUNCTION 'FTR_GET_DATA' "Read Financial Transaction from the Database |
| EXPORTING | ||
| I_TAB_KEY_FHA | = lv_i_tab_key_fha | |
| IMPORTING | ||
| E_TAB_FHA | = lv_e_tab_fha | |
| E_TAB_FHAZU | = lv_e_tab_fhazu | |
| E_TAB_FINKO | = lv_e_tab_finko | |
| E_TAB_AFINKO | = lv_e_tab_afinko | |
| E_TAB_FHAPO | = lv_e_tab_fhapo | |
| E_TAB_FHAPO_UNFIXED | = lv_e_tab_fhapo_unfixed | |
| E_TAB_ZV | = lv_e_tab_zv | |
| E_TAB_KORES | = lv_e_tab_kores | |
| E_TAB_RATING | = lv_e_tab_rating | |
| . " FTR_GET_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FTR_GET_DATA
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