SAP FTR_CORR_EXECUTE_CHECK Function Module for FM Checks Executability of Correspondence Based on Planned Records









FTR_CORR_EXECUTE_CHECK is a standard ftr corr execute check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FM Checks Executability of Correspondence Based on Planned Records 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 check FM, simply by entering the name FTR_CORR_EXECUTE_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function FTR_CORR_EXECUTE_CHECK 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_CHECK'"FM Checks Executability of Correspondence Based on Planned Records
EXPORTING
* PI_OREF_APPL_CTRL = "TR Transaction Management: Application Control
* SELECTION_F = 'X' "Selection Fax
* SELECTION_S = 'X' "Selection Swift
* SELECTION_I = 'X' "
* SELECTION_M = 'X' "
* CHECK_GBL_VTBKORES = 'X' "
* I_TAB_VTBKORES = "wenn nicht übergeben: Plansätze aus glob. Memory
* AUTOMATIC = 'X' "KZ nur automatische Korrespondenzen erstellen
* I_BUKRS = "Company Code
* I_RFHA = "Financial Transaction
* I_RFHAZU = "Transaction Activity
* I_CORTYP = ' ' "Correspondence Type
* I_SGSART = "Produktart der übergebenen VTBKORES-Plansätze
* I_SFHAART = "Finanzgeschäftsart der übergebenen VTBKORES-Pl
* SELECTION_P = 'X' "Selection Printer

TABLES
* EXP_MESG = "Fehlertabelle (MESG-Struktur)
.



IMPORTING Parameters details for FTR_CORR_EXECUTE_CHECK

PI_OREF_APPL_CTRL - TR Transaction Management: Application Control

Data type: CL_FTR_APPL_CTRL
Optional: Yes
Call by Reference: Yes

SELECTION_F - Selection Fax

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: Yes

SELECTION_S - Selection Swift

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: Yes

SELECTION_I -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: Yes

SELECTION_M -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: Yes

CHECK_GBL_VTBKORES -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_TAB_VTBKORES - wenn nicht übergeben: Plansätze aus glob. Memory

Data type: TRTB_TKORES
Optional: Yes
Call by Reference: No ( called with pass by value option)

AUTOMATIC - KZ nur automatische Korrespondenzen erstellen

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BUKRS - Company Code

Data type: VTBFHA-BUKRS
Optional: Yes
Call by Reference: Yes

I_RFHA - Financial Transaction

Data type: VTBFHA-RFHA
Optional: Yes
Call by Reference: Yes

I_RFHAZU - Transaction Activity

Data type: VTBFHAZU-RFHAZU
Optional: Yes
Call by Reference: Yes

I_CORTYP - Correspondence Type

Data type: AT80-CORTYP
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_SGSART - Produktart der übergebenen VTBKORES-Plansätze

Data type: VTBFHA-SGSART
Optional: Yes
Call by Reference: Yes

I_SFHAART - Finanzgeschäftsart der übergebenen VTBKORES-Pl

Data type: VTBFHA-SFHAART
Optional: Yes
Call by Reference: Yes

SELECTION_P - Selection Printer

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for FTR_CORR_EXECUTE_CHECK

EXP_MESG - Fehlertabelle (MESG-Struktur)

Data type: MESG
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FTR_CORR_EXECUTE_CHECK 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:
lt_exp_mesg  TYPE STANDARD TABLE OF MESG, "   
lv_pi_oref_appl_ctrl  TYPE CL_FTR_APPL_CTRL, "   
lv_selection_f  TYPE BOOLE-BOOLE, "   'X'
lv_selection_s  TYPE BOOLE-BOOLE, "   'X'
lv_selection_i  TYPE BOOLE-BOOLE, "   'X'
lv_selection_m  TYPE BOOLE-BOOLE, "   'X'
lv_check_gbl_vtbkores  TYPE BOOLE-BOOLE, "   'X'
lv_i_tab_vtbkores  TYPE TRTB_TKORES, "   
lv_automatic  TYPE BOOLE-BOOLE, "   'X'
lv_i_bukrs  TYPE VTBFHA-BUKRS, "   
lv_i_rfha  TYPE VTBFHA-RFHA, "   
lv_i_rfhazu  TYPE VTBFHAZU-RFHAZU, "   
lv_i_cortyp  TYPE AT80-CORTYP, "   SPACE
lv_i_sgsart  TYPE VTBFHA-SGSART, "   
lv_i_sfhaart  TYPE VTBFHA-SFHAART, "   
lv_selection_p  TYPE BOOLE-BOOLE. "   'X'

  CALL FUNCTION 'FTR_CORR_EXECUTE_CHECK'  "FM Checks Executability of Correspondence Based on Planned Records
    EXPORTING
         PI_OREF_APPL_CTRL = lv_pi_oref_appl_ctrl
         SELECTION_F = lv_selection_f
         SELECTION_S = lv_selection_s
         SELECTION_I = lv_selection_i
         SELECTION_M = lv_selection_m
         CHECK_GBL_VTBKORES = lv_check_gbl_vtbkores
         I_TAB_VTBKORES = lv_i_tab_vtbkores
         AUTOMATIC = lv_automatic
         I_BUKRS = lv_i_bukrs
         I_RFHA = lv_i_rfha
         I_RFHAZU = lv_i_rfhazu
         I_CORTYP = lv_i_cortyp
         I_SGSART = lv_i_sgsart
         I_SFHAART = lv_i_sfhaart
         SELECTION_P = lv_selection_p
    TABLES
         EXP_MESG = lt_exp_mesg
. " FTR_CORR_EXECUTE_CHECK




ABAP code using 7.40 inline data declarations to call FM FTR_CORR_EXECUTE_CHECK

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 BOOLE FROM BOOLE INTO @DATA(ld_selection_f).
DATA(ld_selection_f) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_selection_s).
DATA(ld_selection_s) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_selection_i).
DATA(ld_selection_i) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_selection_m).
DATA(ld_selection_m) = 'X'.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_check_gbl_vtbkores).
DATA(ld_check_gbl_vtbkores) = 'X'.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_automatic).
DATA(ld_automatic) = 'X'.
 
"SELECT single BUKRS FROM VTBFHA INTO @DATA(ld_i_bukrs).
 
"SELECT single RFHA FROM VTBFHA INTO @DATA(ld_i_rfha).
 
"SELECT single RFHAZU FROM VTBFHAZU INTO @DATA(ld_i_rfhazu).
 
"SELECT single CORTYP FROM AT80 INTO @DATA(ld_i_cortyp).
DATA(ld_i_cortyp) = ' '.
 
"SELECT single SGSART FROM VTBFHA INTO @DATA(ld_i_sgsart).
 
"SELECT single SFHAART FROM VTBFHA INTO @DATA(ld_i_sfhaart).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_selection_p).
DATA(ld_selection_p) = 'X'.
 


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!