SAP FTR_CORR_EXECUTE_BY_MONITOR Function Module for Correspondence for Planned Records from Correspondence Monitor









FTR_CORR_EXECUTE_BY_MONITOR is a standard ftr corr execute by monitor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Correspondence for Planned Records from Correspondence Monitor 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 by monitor FM, simply by entering the name FTR_CORR_EXECUTE_BY_MONITOR 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_BY_MONITOR 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_BY_MONITOR'"Correspondence for Planned Records from Correspondence Monitor
  EXPORTING
*  SHOW = ' ' "Druckvorschau?
*  SELECTION_P = 'X' "Printer
*  SELECTION_F = 'X' "Fax
*  SELECTION_S = 'X' "SWIFT/Idoc
*  SELECTION_I = 'X' "
*  SELECTION_M = 'X' "
*  X_PROTOCOL =  "
*  I_RELEASE_CHECK = ' ' "Workflowfreigabe des Geschäfts prüfen

TABLES
   T_VTBKORES_TEXT =  "
.



IMPORTING Parameters details for FTR_CORR_EXECUTE_BY_MONITOR

SHOW - Druckvorschau?

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

SELECTION_P - Printer

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

SELECTION_F - Fax

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

SELECTION_S - SWIFT/Idoc

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

SELECTION_I -

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

SELECTION_M -

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

X_PROTOCOL -

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

I_RELEASE_CHECK - Workflowfreigabe des Geschäfts prüfen

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

TABLES Parameters details for FTR_CORR_EXECUTE_BY_MONITOR

T_VTBKORES_TEXT -

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

Copy and paste ABAP code example for FTR_CORR_EXECUTE_BY_MONITOR 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_show  TYPE BOOLE-BOOLE, "   SPACE
lt_t_vtbkores_text  TYPE STANDARD TABLE OF VTBKORES_TEXT, "   
lv_selection_p  TYPE BOOLE-BOOLE, "   'X'
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_x_protocol  TYPE BOOLE-BOOLE, "   
lv_i_release_check  TYPE BOOLE-BOOLE. "   SPACE

  CALL FUNCTION 'FTR_CORR_EXECUTE_BY_MONITOR'  "Correspondence for Planned Records from Correspondence Monitor
    EXPORTING
         SHOW = lv_show
         SELECTION_P = lv_selection_p
         SELECTION_F = lv_selection_f
         SELECTION_S = lv_selection_s
         SELECTION_I = lv_selection_i
         SELECTION_M = lv_selection_m
         X_PROTOCOL = lv_x_protocol
         I_RELEASE_CHECK = lv_i_release_check
    TABLES
         T_VTBKORES_TEXT = lt_t_vtbkores_text
. " FTR_CORR_EXECUTE_BY_MONITOR




ABAP code using 7.40 inline data declarations to call FM FTR_CORR_EXECUTE_BY_MONITOR

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_show).
DATA(ld_show) = ' '.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_selection_p).
DATA(ld_selection_p) = 'X'.
 
"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_x_protocol).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_release_check).
DATA(ld_i_release_check) = ' '.
 


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!