SAP SWA_CHECK_TABLE_FOR_KEYENTRY Function Module for









SWA_CHECK_TABLE_FOR_KEYENTRY is a standard swa check table for keyentry 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 swa check table for keyentry FM, simply by entering the name SWA_CHECK_TABLE_FOR_KEYENTRY into the relevant SAP transaction such as SE37 or SE38.

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



Function SWA_CHECK_TABLE_FOR_KEYENTRY 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 'SWA_CHECK_TABLE_FOR_KEYENTRY'"
EXPORTING
DBTABNAME = "
KEYSTRING = "

EXCEPTIONS
NO_SET_WITH_KEY_FOUND = 1 DBTAB_NOT_FOUND = 2 ENTRIES_ARE_CLIENTDEPENDANT = 3 ENTRIES_ARE_LANGUAGEDEPENDANT = 4 NOT_CHECKABLE = 5
.



IMPORTING Parameters details for SWA_CHECK_TABLE_FOR_KEYENTRY

DBTABNAME -

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

KEYSTRING -

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

EXCEPTIONS details

NO_SET_WITH_KEY_FOUND -

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

DBTAB_NOT_FOUND -

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

ENTRIES_ARE_CLIENTDEPENDANT -

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

ENTRIES_ARE_LANGUAGEDEPENDANT -

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

NOT_CHECKABLE -

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

Copy and paste ABAP code example for SWA_CHECK_TABLE_FOR_KEYENTRY 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_dbtabname  TYPE DFIES-TABNAME, "   
lv_no_set_with_key_found  TYPE DFIES, "   
lv_keystring  TYPE DFIES, "   
lv_dbtab_not_found  TYPE DFIES, "   
lv_entries_are_clientdependant  TYPE DFIES, "   
lv_entries_are_languagedependant  TYPE DFIES, "   
lv_not_checkable  TYPE DFIES. "   

  CALL FUNCTION 'SWA_CHECK_TABLE_FOR_KEYENTRY'  "
    EXPORTING
         DBTABNAME = lv_dbtabname
         KEYSTRING = lv_keystring
    EXCEPTIONS
        NO_SET_WITH_KEY_FOUND = 1
        DBTAB_NOT_FOUND = 2
        ENTRIES_ARE_CLIENTDEPENDANT = 3
        ENTRIES_ARE_LANGUAGEDEPENDANT = 4
        NOT_CHECKABLE = 5
. " SWA_CHECK_TABLE_FOR_KEYENTRY




ABAP code using 7.40 inline data declarations to call FM SWA_CHECK_TABLE_FOR_KEYENTRY

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 TABNAME FROM DFIES INTO @DATA(ld_dbtabname).
 
 
 
 
 
 
 


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!