SAP CHECK_CUSTOMER_NAMES Function Module for Determine whether table key is in SAP or customer namespace

Search SAP Function Modules

CHECK_CUSTOMER_NAMES is a standard check customer names SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine whether table key is in SAP or customer namespace processing and below is the pattern details for this FM, 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 check customer names FM, simply by entering the name CHECK_CUSTOMER_NAMES into the relevant SAP transaction such as SE37 or SE38.

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

Function CHECK_CUSTOMER_NAMES 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 'CHECK_CUSTOMER_NAMES'"Determine whether table key is in SAP or customer namespace
  EXPORTING
*  OBJECTTYPE = 'TABU' "Object type, for example, TABU for tables
   TABLEKEY =  "Table key you want to check
   TABLENAME =  "Table name you want to check

 IMPORTING
   KEY_ALLOWED =  "X, if key is in allowed range
   SYSTEM_SAP =  "X, if call made at SAP
   TABLE_NOT_FOUND =  "X, if no name ranges entered for table
   KEY_MIXED =  "X, if key is in allowed and non-allowed range

EXCEPTIONS
   OBJECTTYPE_NOT_FILLED = 1    TABLENAME_NOT_FILLED = 2 

.

IMPORTING Parameters details for CHECK_CUSTOMER_NAMES

OBJECTTYPE - Object type, for example, TABU for tables

Data type: TRESC-OBJECT
Default: 'TABU'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLEKEY - Table key you want to check

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

TABLENAME - Table name you want to check

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

EXPORTING Parameters details for CHECK_CUSTOMER_NAMES

KEY_ALLOWED - X, if key is in allowed range

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

SYSTEM_SAP - X, if call made at SAP

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

TABLE_NOT_FOUND - X, if no name ranges entered for table

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

KEY_MIXED - X, if key is in allowed and non-allowed range

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

EXCEPTIONS details

OBJECTTYPE_NOT_FILLED - Parameter OBJECTTYPE not filled

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

TABLENAME_NOT_FILLED - Parameter TABLENAME not filled

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

Copy and paste ABAP code example for CHECK_CUSTOMER_NAMES 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.

ABAP code using 7.40 inline data declarations to call FM CHECK_CUSTOMER_NAMES

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.

Search for further information about these or an SAP related objects