SAP FTR_OTC_SE_BAPI_CHECK Function Module for Check BAPI









FTR_OTC_SE_BAPI_CHECK is a standard ftr otc se bapi 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 Check BAPI 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 otc se bapi check FM, simply by entering the name FTR_OTC_SE_BAPI_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function FTR_OTC_SE_BAPI_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_OTC_SE_BAPI_CHECK'"Check BAPI
EXPORTING
I_TEST = "Switch to Simulation Mode for Write BAPIs
I_FLAG_BAPI = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* I_OREF_APPL_CTRL = "TR Transaction Management: Application Control

IMPORTING
E_TAB_MESSAGE = "
.



IMPORTING Parameters details for FTR_OTC_SE_BAPI_CHECK

I_TEST - Switch to Simulation Mode for Write BAPIs

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

I_FLAG_BAPI - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

I_OREF_APPL_CTRL - TR Transaction Management: Application Control

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

EXPORTING Parameters details for FTR_OTC_SE_BAPI_CHECK

E_TAB_MESSAGE -

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

Copy and paste ABAP code example for FTR_OTC_SE_BAPI_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:
lv_i_test  TYPE TESTRUN, "   
lv_e_tab_message  TYPE FTRG_TAB_APPL_MESSAGE, "   
lv_i_flag_bapi  TYPE BOOLE-BOOLE, "   
lv_i_oref_appl_ctrl  TYPE CL_FTR_APPL_CTRL. "   

  CALL FUNCTION 'FTR_OTC_SE_BAPI_CHECK'  "Check BAPI
    EXPORTING
         I_TEST = lv_i_test
         I_FLAG_BAPI = lv_i_flag_bapi
         I_OREF_APPL_CTRL = lv_i_oref_appl_ctrl
    IMPORTING
         E_TAB_MESSAGE = lv_e_tab_message
. " FTR_OTC_SE_BAPI_CHECK




ABAP code using 7.40 inline data declarations to call FM FTR_OTC_SE_BAPI_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_i_flag_bapi).
 
 


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!