SAP CATT_CHECK_READ_TABLE Function Module for









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

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



Function CATT_CHECK_READ_TABLE 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 'CATT_CHECK_READ_TABLE'"
EXPORTING
TABLE = "
* VAL4 = ' ' "
* VAL5 = ' ' "
* FIELD = ' ' "
KEY1 = "
* KEY2 = ' ' "
* KEY3 = ' ' "
* KEY4 = ' ' "
* KEY5 = ' ' "
VAL1 = "
* VAL2 = ' ' "
* VAL3 = ' ' "

IMPORTING
E_VAL = "
E_COUNT = "

EXCEPTIONS
NO_TABLE_NAME = 1 NO_KEY_NAME = 2 NO_VALID_TABLEFIELD = 3 WRONG_FIELD_FORMAT = 4 WRONG_TABLENAME = 5
.



IMPORTING Parameters details for CATT_CHECK_READ_TABLE

TABLE -

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

VAL4 -

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

VAL5 -

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

FIELD -

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

KEY1 -

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

KEY2 -

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

KEY3 -

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

KEY4 -

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

KEY5 -

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

VAL1 -

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

VAL2 -

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

VAL3 -

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

EXPORTING Parameters details for CATT_CHECK_READ_TABLE

E_VAL -

Data type:
Optional: No
Call by Reference: Yes

E_COUNT -

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

EXCEPTIONS details

NO_TABLE_NAME -

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

NO_KEY_NAME -

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

NO_VALID_TABLEFIELD -

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

WRONG_FIELD_FORMAT -

Data type:
Optional: No
Call by Reference: Yes

WRONG_TABLENAME -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CATT_CHECK_READ_TABLE 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_val  TYPE STRING, "   
lv_table  TYPE STRING, "   
lv_no_table_name  TYPE STRING, "   
lv_val4  TYPE STRING, "   SPACE
lv_val5  TYPE STRING, "   SPACE
lv_field  TYPE STRING, "   SPACE
lv_key1  TYPE STRING, "   
lv_e_count  TYPE SY-DBCNT, "   
lv_no_key_name  TYPE SY, "   
lv_key2  TYPE SY, "   SPACE
lv_no_valid_tablefield  TYPE SY, "   
lv_key3  TYPE SY, "   SPACE
lv_wrong_field_format  TYPE SY, "   
lv_key4  TYPE SY, "   SPACE
lv_wrong_tablename  TYPE SY, "   
lv_key5  TYPE SY, "   SPACE
lv_val1  TYPE SY, "   
lv_val2  TYPE SY, "   SPACE
lv_val3  TYPE SY. "   SPACE

  CALL FUNCTION 'CATT_CHECK_READ_TABLE'  "
    EXPORTING
         TABLE = lv_table
         VAL4 = lv_val4
         VAL5 = lv_val5
         FIELD = lv_field
         KEY1 = lv_key1
         KEY2 = lv_key2
         KEY3 = lv_key3
         KEY4 = lv_key4
         KEY5 = lv_key5
         VAL1 = lv_val1
         VAL2 = lv_val2
         VAL3 = lv_val3
    IMPORTING
         E_VAL = lv_e_val
         E_COUNT = lv_e_count
    EXCEPTIONS
        NO_TABLE_NAME = 1
        NO_KEY_NAME = 2
        NO_VALID_TABLEFIELD = 3
        WRONG_FIELD_FORMAT = 4
        WRONG_TABLENAME = 5
. " CATT_CHECK_READ_TABLE




ABAP code using 7.40 inline data declarations to call FM CATT_CHECK_READ_TABLE

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.

 
 
 
DATA(ld_val4) = ' '.
 
DATA(ld_val5) = ' '.
 
DATA(ld_field) = ' '.
 
 
"SELECT single DBCNT FROM SY INTO @DATA(ld_e_count).
 
 
DATA(ld_key2) = ' '.
 
 
DATA(ld_key3) = ' '.
 
 
DATA(ld_key4) = ' '.
 
 
DATA(ld_key5) = ' '.
 
 
DATA(ld_val2) = ' '.
 
DATA(ld_val3) = ' '.
 


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!