SAP SAA_REMOTE_TRANSACTION Function Module for









SAA_REMOTE_TRANSACTION is a standard saa 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 saa remote transaction FM, simply by entering the name SAA_REMOTE_TRANSACTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: SENV
Program Name: SAPLSENV
Main Program: SAPLSENV
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SAA_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 'SAA_REMOTE_TRANSACTION'"
EXPORTING
* TCODE = "Transaction Code
* FUNCMODULE = "Function Module
* ACCEPT = "Task confirmed without execution
* ISAACONTS = "
* OPSYS = "R/3 System, Operating System of Application Server
* OFFLINE = "

EXCEPTIONS
NO_AUTHORIZATION = 1 NOT_FOUND = 2 FUNCTION_ERROR = 3 NO_OPSYS = 4
.



IMPORTING Parameters details for SAA_REMOTE_TRANSACTION

TCODE - Transaction Code

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

FUNCMODULE - Function Module

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

ACCEPT - Task confirmed without execution

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

ISAACONTS -

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

OPSYS - R/3 System, Operating System of Application Server

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

OFFLINE -

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

EXCEPTIONS details

NO_AUTHORIZATION - No Authorization

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FUNCTION_ERROR - Internal Error

Data type:
Optional: No
Call by Reference: Yes

NO_OPSYS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SAA_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 SY-TCODE, "   
lv_no_authorization  TYPE SY, "   
lv_not_found  TYPE SY, "   
lv_funcmodule  TYPE RS38L_FNAM, "   
lv_accept  TYPE SAACONTS-EXEACCEPT, "   
lv_function_error  TYPE SAACONTS, "   
lv_no_opsys  TYPE SAACONTS, "   
lv_isaaconts  TYPE SAACONTS, "   
lv_opsys  TYPE SY-OPSYS, "   
lv_offline  TYPE CHAR1. "   

  CALL FUNCTION 'SAA_REMOTE_TRANSACTION'  "
    EXPORTING
         TCODE = lv_tcode
         FUNCMODULE = lv_funcmodule
         ACCEPT = lv_accept
         ISAACONTS = lv_isaaconts
         OPSYS = lv_opsys
         OFFLINE = lv_offline
    EXCEPTIONS
        NO_AUTHORIZATION = 1
        NOT_FOUND = 2
        FUNCTION_ERROR = 3
        NO_OPSYS = 4
. " SAA_REMOTE_TRANSACTION




ABAP code using 7.40 inline data declarations to call FM SAA_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 TCODE FROM SY INTO @DATA(ld_tcode).
 
 
 
 
"SELECT single EXEACCEPT FROM SAACONTS INTO @DATA(ld_accept).
 
 
 
 
"SELECT single OPSYS FROM SY INTO @DATA(ld_opsys).
 
 


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!