SAP DEVELOPER_CHECK Function Module for









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

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



Function DEVELOPER_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 'DEVELOPER_CHECK'"
EXPORTING
* SUPPRESS_DIALOG = ' ' "

EXCEPTIONS
ACCESS_DENIED = 1 DISPLAY_ONLY = 2
.



IMPORTING Parameters details for DEVELOPER_CHECK

SUPPRESS_DIALOG -

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

EXCEPTIONS details

ACCESS_DENIED -

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

DISPLAY_ONLY -

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

Copy and paste ABAP code example for DEVELOPER_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_access_denied  TYPE STRING, "   
lv_suppress_dialog  TYPE SY-BATCH, "   SPACE
lv_display_only  TYPE SY. "   

  CALL FUNCTION 'DEVELOPER_CHECK'  "
    EXPORTING
         SUPPRESS_DIALOG = lv_suppress_dialog
    EXCEPTIONS
        ACCESS_DENIED = 1
        DISPLAY_ONLY = 2
. " DEVELOPER_CHECK




ABAP code using 7.40 inline data declarations to call FM DEVELOPER_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 BATCH FROM SY INTO @DATA(ld_suppress_dialog).
DATA(ld_suppress_dialog) = ' '.
 
 


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!