SAP DD_AUTH_CHECK Function Module for Authority check for Data Dictionary and database utility









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

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



Function DD_AUTH_CHECK 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_AUTH_CHECK'"Authority check for Data Dictionary and database utility
  EXPORTING
*  ACTION = ' ' "Action as String. See function documentation
*  ACTION_CODE = ' ' "Action as TACT-Code. See function documentation
*  DEVCLASS = ' ' "provided development class for new objects
*  MSG_TYP = ' ' "Category of message for missing authorization
   OBJNAME =  "Name of the object
*  ID = ' ' "
   OBJTYPE =  "Object type. For example DOMA, DTEL, TABL, VIEW

 IMPORTING
   RC =  "Return code as for AUTHORITY_CHECK

EXCEPTIONS
   ACTION_UNSUPPORTED = 1    OBJTYPE_UNSUPPORTED = 2    PARAM_ERROR = 3
.



IMPORTING Parameters details for DD_AUTH_CHECK

ACTION - Action as String. See function documentation

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

ACTION_CODE - Action as TACT-Code. See function documentation

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

DEVCLASS - provided development class for new objects

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

MSG_TYP - Category of message for missing authorization

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

OBJNAME - Name of the object

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

ID -

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

OBJTYPE - Object type. For example DOMA, DTEL, TABL, VIEW

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

EXPORTING Parameters details for DD_AUTH_CHECK

RC - Return code as for AUTHORITY_CHECK

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

EXCEPTIONS details

ACTION_UNSUPPORTED - Action is not supported.

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

OBJTYPE_UNSUPPORTED - Object type is not supported.

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

PARAM_ERROR - ACTION and ACTION_CODE were both supplied.

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

Copy and paste ABAP code example for DD_AUTH_CHECK 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_rc  TYPE SY-SUBRC, "   
lv_action  TYPE SY, "   SPACE
lv_action_unsupported  TYPE SY, "   
lv_action_code  TYPE TACT-ACTVT, "   SPACE
lv_objtype_unsupported  TYPE TACT, "   
lv_devclass  TYPE TDEVC-DEVCLASS, "   SPACE
lv_param_error  TYPE TDEVC, "   
lv_msg_typ  TYPE TDEVC, "   SPACE
lv_objname  TYPE TDEVC, "   
lv_id  TYPE DCOBJDEF-ID, "   SPACE
lv_objtype  TYPE DCOBJDEF. "   

  CALL FUNCTION 'DD_AUTH_CHECK'  "Authority check for Data Dictionary and database utility
    EXPORTING
         ACTION = lv_action
         ACTION_CODE = lv_action_code
         DEVCLASS = lv_devclass
         MSG_TYP = lv_msg_typ
         OBJNAME = lv_objname
         ID = lv_id
         OBJTYPE = lv_objtype
    IMPORTING
         RC = lv_rc
    EXCEPTIONS
        ACTION_UNSUPPORTED = 1
        OBJTYPE_UNSUPPORTED = 2
        PARAM_ERROR = 3
. " DD_AUTH_CHECK




ABAP code using 7.40 inline data declarations to call FM DD_AUTH_CHECK

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 SUBRC FROM SY INTO @DATA(ld_rc).
 
DATA(ld_action) = ' '.
 
 
"SELECT single ACTVT FROM TACT INTO @DATA(ld_action_code).
DATA(ld_action_code) = ' '.
 
 
"SELECT single DEVCLASS FROM TDEVC INTO @DATA(ld_devclass).
DATA(ld_devclass) = ' '.
 
 
DATA(ld_msg_typ) = ' '.
 
 
"SELECT single ID FROM DCOBJDEF INTO @DATA(ld_id).
DATA(ld_id) = ' '.
 
 


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!