SAP TH_REMOTE_TRANSACTION Function Module for









TH_REMOTE_TRANSACTION is a standard th remote transaction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 th remote transaction FM, simply by entering the name TH_REMOTE_TRANSACTION into the relevant SAP transaction such as SE37 or SE38.

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



Function TH_REMOTE_TRANSACTION 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 'TH_REMOTE_TRANSACTION'"
EXPORTING
TCODE = "Transaction to be called
DEST = "Destination
* USE_BDC = 0 "

IMPORTING
COMM_MESSAGE = "
SYST_MESSAGE = "

TABLES
* BDCTAB = "
.



IMPORTING Parameters details for TH_REMOTE_TRANSACTION

TCODE - Transaction to be called

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

DEST - Destination

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

USE_BDC -

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

EXPORTING Parameters details for TH_REMOTE_TRANSACTION

COMM_MESSAGE -

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

SYST_MESSAGE -

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

TABLES Parameters details for TH_REMOTE_TRANSACTION

BDCTAB -

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

Copy and paste ABAP code example for TH_REMOTE_TRANSACTION 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_tcode  TYPE SM04DIC-TCODE1, "   
lt_bdctab  TYPE STANDARD TABLE OF BDCDATA, "   
lv_comm_message  TYPE BDCDATA, "   
lv_dest  TYPE MSXXLIST-NAME, "   
lv_syst_message  TYPE MSXXLIST, "   
lv_use_bdc  TYPE SM04DIC-VBGETINFO. "   0

  CALL FUNCTION 'TH_REMOTE_TRANSACTION'  "
    EXPORTING
         TCODE = lv_tcode
         DEST = lv_dest
         USE_BDC = lv_use_bdc
    IMPORTING
         COMM_MESSAGE = lv_comm_message
         SYST_MESSAGE = lv_syst_message
    TABLES
         BDCTAB = lt_bdctab
. " TH_REMOTE_TRANSACTION




ABAP code using 7.40 inline data declarations to call FM TH_REMOTE_TRANSACTION

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 TCODE1 FROM SM04DIC INTO @DATA(ld_tcode).
 
 
 
"SELECT single NAME FROM MSXXLIST INTO @DATA(ld_dest).
 
 
"SELECT single VBGETINFO FROM SM04DIC INTO @DATA(ld_use_bdc).
 


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!