SAP DD_CHECK_NAME Function Module for Check dictionary object name for correctness

Search SAP Function Modules

DD_CHECK_NAME is a standard dd check name SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check dictionary object name for correctness 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 dd check name FM, simply by entering the name DD_CHECK_NAME into the relevant SAP transaction such as SE37 or SE38.

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

Function DD_CHECK_NAME 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 'DD_CHECK_NAME'"Check dictionary object name for correctness
  EXPORTING
   NAME =  "Object name
*  NAME2 = ' ' "Name enhancement; for example index ID
   OBJTYP =  "Type of object; for example DOMA, DTEL, TABL and so on
*  SUBTYP = ' ' "Subtype, e.g. table class or view type
*  NO_EXI_CHECK = ' ' "X: Do not check existence of object
*  NO_CREATE_CHECK = ' ' "X: object should not be newly created
*  ACTIVE_ONLY = ' ' "

 IMPORTING
   TYP_CONFLICT =  "Type of an object which already exists
   SAA_CONFLICT =  "X: Name not allowed
   OBJ_EXISTS =  "The object already exists
   MSG_FLAG =  "There is a message in SY-MSGNO etc.

EXCEPTIONS
   UNKNOWN_OBJTYPE = 1 

.

IMPORTING Parameters details for DD_CHECK_NAME

NAME - Object name

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

NAME2 - Name enhancement; for example index ID

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

OBJTYP - Type of object; for example DOMA, DTEL, TABL and so on

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

SUBTYP - Subtype, e.g. table class or view type

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

NO_EXI_CHECK - X: Do not check existence of object

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

NO_CREATE_CHECK - X: object should not be newly created

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

ACTIVE_ONLY -

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

EXPORTING Parameters details for DD_CHECK_NAME

TYP_CONFLICT - Type of an object which already exists

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

SAA_CONFLICT - X: Name not allowed

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

OBJ_EXISTS - The object already exists

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

MSG_FLAG - There is a message in SY-MSGNO etc.

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

EXCEPTIONS details

UNKNOWN_OBJTYPE - False entry in OBJTYP

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

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

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