SAP RSCC_DEBUG_STATUS_GET Function Module for Determines Whether Debugging Is Permitted in This System/for This User









RSCC_DEBUG_STATUS_GET is a standard rscc debug status get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines Whether Debugging Is Permitted in This System/for This User 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 rscc debug status get FM, simply by entering the name RSCC_DEBUG_STATUS_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSCC
Program Name: SAPLRSCC
Main Program: SAPLRSCC
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RSCC_DEBUG_STATUS_GET 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 'RSCC_DEBUG_STATUS_GET'"Determines Whether Debugging Is Permitted in This System/for This User
EXPORTING
* I_USER = SY-UNAME "User to Be Checked
* I_ONLY_USER_CHECK = "Check User Only, No System Check

IMPORTING
E_DEBUGGING = "Debugging Permitted
E_SYSTEMTYPE = "System Type (Customer/SAP)
.



IMPORTING Parameters details for RSCC_DEBUG_STATUS_GET

I_USER - User to Be Checked

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

I_ONLY_USER_CHECK - Check User Only, No System Check

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

EXPORTING Parameters details for RSCC_DEBUG_STATUS_GET

E_DEBUGGING - Debugging Permitted

Data type: RS_BOOL
Optional: No
Call by Reference: Yes

E_SYSTEMTYPE - System Type (Customer/SAP)

Data type: RS_SYSTP
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSCC_DEBUG_STATUS_GET 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_i_user  TYPE SYUNAME, "   SY-UNAME
lv_e_debugging  TYPE RS_BOOL, "   
lv_e_systemtype  TYPE RS_SYSTP, "   
lv_i_only_user_check  TYPE RS_BOOL. "   

  CALL FUNCTION 'RSCC_DEBUG_STATUS_GET'  "Determines Whether Debugging Is Permitted in This System/for This User
    EXPORTING
         I_USER = lv_i_user
         I_ONLY_USER_CHECK = lv_i_only_user_check
    IMPORTING
         E_DEBUGGING = lv_e_debugging
         E_SYSTEMTYPE = lv_e_systemtype
. " RSCC_DEBUG_STATUS_GET




ABAP code using 7.40 inline data declarations to call FM RSCC_DEBUG_STATUS_GET

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_i_user) = SY-UNAME.
 
 
 
 


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!