SAP ISM_DM_AUTHORITY_CHECK Function Module for IS-M DM: Authorization Check in RFC
ISM_DM_AUTHORITY_CHECK is a standard ism dm 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 IS-M DM: Authorization Check in RFC 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 ism dm authority check FM, simply by entering the name ISM_DM_AUTHORITY_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: ISM_DM_UTILS
Program Name: SAPLISM_DM_UTILS
Main Program: SAPLISM_DM_UTILS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_DM_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 'ISM_DM_AUTHORITY_CHECK'"IS-M DM: Authorization Check in RFC.
EXPORTING
PV_ACTIVITY = "Activity
PV_BUS_OBJ_TYPE = "Category of Objects in Persistent Object References
IMPORTING
PS_ERROR = "Return Parameter(s)
EXCEPTIONS
NOT_AUTHORIZED = 1
IMPORTING Parameters details for ISM_DM_AUTHORITY_CHECK
PV_ACTIVITY - Activity
Data type: ACTIV_AUTHOptional: No
Call by Reference: Yes
PV_BUS_OBJ_TYPE - Category of Objects in Persistent Object References
Data type: SIBFTYPEIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_DM_AUTHORITY_CHECK
PS_ERROR - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_AUTHORIZED - No authorization for activity
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_DM_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_ps_error | TYPE BAPIRET2, " | |||
| lv_pv_activity | TYPE ACTIV_AUTH, " | |||
| lv_not_authorized | TYPE ACTIV_AUTH, " | |||
| lv_pv_bus_obj_type | TYPE SIBFTYPEID. " |
|   CALL FUNCTION 'ISM_DM_AUTHORITY_CHECK' "IS-M DM: Authorization Check in RFC |
| EXPORTING | ||
| PV_ACTIVITY | = lv_pv_activity | |
| PV_BUS_OBJ_TYPE | = lv_pv_bus_obj_type | |
| IMPORTING | ||
| PS_ERROR | = lv_ps_error | |
| EXCEPTIONS | ||
| NOT_AUTHORIZED = 1 | ||
| . " ISM_DM_AUTHORITY_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ISM_DM_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