SAP TMW_OLE_FAILOVER Function Module for TMW_OLE_FAILOVER









TMW_OLE_FAILOVER is a standard tmw ole failover SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for TMW_OLE_FAILOVER 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 tmw ole failover FM, simply by entering the name TMW_OLE_FAILOVER into the relevant SAP transaction such as SE37 or SE38.

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



Function TMW_OLE_FAILOVER 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 'TMW_OLE_FAILOVER'"TMW_OLE_FAILOVER
EXPORTING
I_TM_PATH = "Predefined Type
I_TTX_PATH = "Predefined Type
I_TLANG = "Translation Language
I_WBS_PATH = "Predefined Type

IMPORTING
E_STATS_S = "Translation Memory Middleware Analysis Statistics
E_STATS_W = "Translation Memory Middleware Analysis Statistics

EXCEPTIONS
OLE_CREATION = 1 OLE_OPENTM = 2 OLE_GET_DOCUMENTS = 3 OLE_CLEAR = 4 OLE_ADD = 5 OLE_EXECUTE = 6 OLE_CLOSETM = 7 OLE_WBS = 8
.



IMPORTING Parameters details for TMW_OLE_FAILOVER

I_TM_PATH - Predefined Type

Data type: STRING
Optional: No
Call by Reference: Yes

I_TTX_PATH - Predefined Type

Data type: STRING
Optional: No
Call by Reference: Yes

I_TLANG - Translation Language

Data type: LXEISOLANG
Optional: No
Call by Reference: Yes

I_WBS_PATH - Predefined Type

Data type: STRING
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for TMW_OLE_FAILOVER

E_STATS_S - Translation Memory Middleware Analysis Statistics

Data type: TMW_ASTATS
Optional: No
Call by Reference: Yes

E_STATS_W - Translation Memory Middleware Analysis Statistics

Data type: TMW_ASTATS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

OLE_CREATION - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

OLE_OPENTM - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

OLE_GET_DOCUMENTS - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

OLE_CLEAR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

OLE_ADD - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

OLE_EXECUTE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

OLE_CLOSETM - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

OLE_WBS - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TMW_OLE_FAILOVER 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_stats_s  TYPE TMW_ASTATS, "   
lv_i_tm_path  TYPE STRING, "   
lv_ole_creation  TYPE STRING, "   
lv_e_stats_w  TYPE TMW_ASTATS, "   
lv_i_ttx_path  TYPE STRING, "   
lv_ole_opentm  TYPE STRING, "   
lv_i_tlang  TYPE LXEISOLANG, "   
lv_ole_get_documents  TYPE LXEISOLANG, "   
lv_ole_clear  TYPE LXEISOLANG, "   
lv_i_wbs_path  TYPE STRING, "   
lv_ole_add  TYPE STRING, "   
lv_ole_execute  TYPE STRING, "   
lv_ole_closetm  TYPE STRING, "   
lv_ole_wbs  TYPE STRING. "   

  CALL FUNCTION 'TMW_OLE_FAILOVER'  "TMW_OLE_FAILOVER
    EXPORTING
         I_TM_PATH = lv_i_tm_path
         I_TTX_PATH = lv_i_ttx_path
         I_TLANG = lv_i_tlang
         I_WBS_PATH = lv_i_wbs_path
    IMPORTING
         E_STATS_S = lv_e_stats_s
         E_STATS_W = lv_e_stats_w
    EXCEPTIONS
        OLE_CREATION = 1
        OLE_OPENTM = 2
        OLE_GET_DOCUMENTS = 3
        OLE_CLEAR = 4
        OLE_ADD = 5
        OLE_EXECUTE = 6
        OLE_CLOSETM = 7
        OLE_WBS = 8
. " TMW_OLE_FAILOVER




ABAP code using 7.40 inline data declarations to call FM TMW_OLE_FAILOVER

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



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!