SAP SCPR_AUTHORITY_CHECK Function Module for BC Sets: Check Authorization
SCPR_AUTHORITY_CHECK is a standard scpr authority 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 BC Sets: Check Authorization 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 scpr authority check FM, simply by entering the name SCPR_AUTHORITY_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCPR
Program Name: SAPLSCPR
Main Program: SAPLSCPR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCPR_AUTHORITY_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 'SCPR_AUTHORITY_CHECK'"BC Sets: Check Authorization.
EXPORTING
TASK = "BC Sets: Authorization Check Data Element
* ID = "Business Configuration Set
* CATEGORY = "BC Set: Category
EXCEPTIONS
WRONG_PARAMETERS = 1 NO_AUTHORITY = 2
IMPORTING Parameters details for SCPR_AUTHORITY_CHECK
TASK - BC Sets: Authorization Check Data Element
Data type: SCPRAUTHOptional: No
Call by Reference: No ( called with pass by value option)
ID - Business Configuration Set
Data type: SCPR_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
CATEGORY - BC Set: Category
Data type: SCPR_CTGRYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_PARAMETERS - FM Call with Invalid Parameters
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY - You are not authorized to perform this action
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SCPR_AUTHORITY_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_task | TYPE SCPRAUTH, " | |||
| lv_wrong_parameters | TYPE SCPRAUTH, " | |||
| lv_id | TYPE SCPR_ID, " | |||
| lv_no_authority | TYPE SCPR_ID, " | |||
| lv_category | TYPE SCPR_CTGRY. " |
|   CALL FUNCTION 'SCPR_AUTHORITY_CHECK' "BC Sets: Check Authorization |
| EXPORTING | ||
| TASK | = lv_task | |
| ID | = lv_id | |
| CATEGORY | = lv_category | |
| EXCEPTIONS | ||
| WRONG_PARAMETERS = 1 | ||
| NO_AUTHORITY = 2 | ||
| . " SCPR_AUTHORITY_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM SCPR_AUTHORITY_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.Search for further information about these or an SAP related objects