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

Function FTR_CORR_EXECUTE_FORM 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_CORR_EXECUTE_FORM'"Function Module for Fax Implementation.
EXPORTING
IS_VTBFHA = "Financial Transaction
IS_VTBFHAZU = "Transaction Activity
IT_VTBFHAPO = "Financial Transaction Flow
IS_VTBKORES = "Correspondence data
IS_AT80 = "Treasury: Correspondence Control MM, FX, DE, SE
* IV_NEW = 'X' "Switch flag for EHP 4.0
* IS_SA_MAIN = "Securities account main data
* IT_SA_FLOWS = "TCO Data: Table type of Securities account flows information
IMPORTING
ET_CONTENT = "
ET_ERR_TR_COLLECT = "
ET_ERR_FO_COLLECT = "
CHANGING
* CT_HEADER = "
IMPORTING Parameters details for FTR_CORR_EXECUTE_FORM
IS_VTBFHA - Financial Transaction
Data type: VTBFHAOptional: No
Call by Reference: Yes
IS_VTBFHAZU - Transaction Activity
Data type: VTBFHAZUOptional: No
Call by Reference: Yes
IT_VTBFHAPO - Financial Transaction Flow
Data type: FTR_FHAPOOptional: No
Call by Reference: Yes
IS_VTBKORES - Correspondence data
Data type: VTBKORESOptional: No
Call by Reference: Yes
IS_AT80 - Treasury: Correspondence Control MM, FX, DE, SE
Data type: AT80Optional: No
Call by Reference: Yes
IV_NEW - Switch flag for EHP 4.0
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
IS_SA_MAIN - Securities account main data
Data type: TCORS_COSA_INCLOptional: Yes
Call by Reference: Yes
IT_SA_FLOWS - TCO Data: Table type of Securities account flows information
Data type: TCORY_COSAFL_INCLOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FTR_CORR_EXECUTE_FORM
ET_CONTENT -
Data type: TCORFY_CONTENTOptional: No
Call by Reference: Yes
ET_ERR_TR_COLLECT -
Data type: FTRC_T_ERR_TROptional: No
Call by Reference: Yes
ET_ERR_FO_COLLECT -
Data type: FTRC_T_ERR_FOOptional: No
Call by Reference: Yes
CHANGING Parameters details for FTR_CORR_EXECUTE_FORM
CT_HEADER -
Data type: TCORFY_FIELDLISTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FTR_CORR_EXECUTE_FORM 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_ct_header | TYPE TCORFY_FIELDLIST, " | |||
| lv_is_vtbfha | TYPE VTBFHA, " | |||
| lv_et_content | TYPE TCORFY_CONTENT, " | |||
| lv_is_vtbfhazu | TYPE VTBFHAZU, " | |||
| lv_et_err_tr_collect | TYPE FTRC_T_ERR_TR, " | |||
| lv_it_vtbfhapo | TYPE FTR_FHAPO, " | |||
| lv_et_err_fo_collect | TYPE FTRC_T_ERR_FO, " | |||
| lv_is_vtbkores | TYPE VTBKORES, " | |||
| lv_is_at80 | TYPE AT80, " | |||
| lv_iv_new | TYPE C, " 'X' | |||
| lv_is_sa_main | TYPE TCORS_COSA_INCL, " | |||
| lv_it_sa_flows | TYPE TCORY_COSAFL_INCL. " |
|   CALL FUNCTION 'FTR_CORR_EXECUTE_FORM' "Function Module for Fax Implementation |
| EXPORTING | ||
| IS_VTBFHA | = lv_is_vtbfha | |
| IS_VTBFHAZU | = lv_is_vtbfhazu | |
| IT_VTBFHAPO | = lv_it_vtbfhapo | |
| IS_VTBKORES | = lv_is_vtbkores | |
| IS_AT80 | = lv_is_at80 | |
| IV_NEW | = lv_iv_new | |
| IS_SA_MAIN | = lv_is_sa_main | |
| IT_SA_FLOWS | = lv_it_sa_flows | |
| IMPORTING | ||
| ET_CONTENT | = lv_et_content | |
| ET_ERR_TR_COLLECT | = lv_et_err_tr_collect | |
| ET_ERR_FO_COLLECT | = lv_et_err_fo_collect | |
| CHANGING | ||
| CT_HEADER | = lv_ct_header | |
| . " FTR_CORR_EXECUTE_FORM | ||
ABAP code using 7.40 inline data declarations to call FM FTR_CORR_EXECUTE_FORM
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_iv_new) | = 'X'. | |||
Search for further information about these or an SAP related objects