SAP SWY_TRANSACTION_EXISTS Function Module for









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

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



Function SWY_TRANSACTION_EXISTS 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 'SWY_TRANSACTION_EXISTS'"
EXPORTING
TRANSACTION = "Transaction Code

IMPORTING
TSTC_ENTRY = "

EXCEPTIONS
TRANSACTION_NOT_EXISTS = 1
.



IMPORTING Parameters details for SWY_TRANSACTION_EXISTS

TRANSACTION - Transaction Code

Data type: TSTC-TCODE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for SWY_TRANSACTION_EXISTS

TSTC_ENTRY -

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

EXCEPTIONS details

TRANSACTION_NOT_EXISTS - Transaction Does Not Exist

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SWY_TRANSACTION_EXISTS 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_tstc_entry  TYPE TSTC, "   
lv_transaction  TYPE TSTC-TCODE, "   
lv_transaction_not_exists  TYPE TSTC. "   

  CALL FUNCTION 'SWY_TRANSACTION_EXISTS'  "
    EXPORTING
         TRANSACTION = lv_transaction
    IMPORTING
         TSTC_ENTRY = lv_tstc_entry
    EXCEPTIONS
        TRANSACTION_NOT_EXISTS = 1
. " SWY_TRANSACTION_EXISTS




ABAP code using 7.40 inline data declarations to call FM SWY_TRANSACTION_EXISTS

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 TSTC INTO @DATA(ld_transaction).
 
 


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!