SAP ISCD_BROK_STM_AUTHORITY Function Module for Broker Report - Authorization Check
ISCD_BROK_STM_AUTHORITY is a standard iscd brok stm authority SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Broker Report - Authorization Check 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 iscd brok stm authority FM, simply by entering the name ISCD_BROK_STM_AUTHORITY into the relevant SAP transaction such as SE37 or SE38.
Function Group: VKAG
Program Name: SAPLVKAG
Main Program: SAPLVKAG
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISCD_BROK_STM_AUTHORITY 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 'ISCD_BROK_STM_AUTHORITY'"Broker Report - Authorization Check.
EXPORTING
I_OK_CODE = "
IMPORTING
E_ACTIV_TEXT = "
EXCEPTIONS
NO_AUTHOR = 1
IMPORTING Parameters details for ISCD_BROK_STM_AUTHORITY
I_OK_CODE -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISCD_BROK_STM_AUTHORITY
E_ACTIV_TEXT -
Data type: CSEQUENCEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_AUTHOR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISCD_BROK_STM_AUTHORITY 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_ok_code | TYPE C, " | |||
| lv_no_author | TYPE C, " | |||
| lv_e_activ_text | TYPE CSEQUENCE. " |
|   CALL FUNCTION 'ISCD_BROK_STM_AUTHORITY' "Broker Report - Authorization Check |
| EXPORTING | ||
| I_OK_CODE | = lv_i_ok_code | |
| IMPORTING | ||
| E_ACTIV_TEXT | = lv_e_activ_text | |
| EXCEPTIONS | ||
| NO_AUTHOR = 1 | ||
| . " ISCD_BROK_STM_AUTHORITY | ||
ABAP code using 7.40 inline data declarations to call FM ISCD_BROK_STM_AUTHORITY
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