SAP CLB2_NOTIFY_AUTH Function Module for Remote access to BadI CLB2_NOTIFY_AUTH->AUTH_CHECK
CLB2_NOTIFY_AUTH is a standard clb2 notify auth SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Remote access to BadI CLB2_NOTIFY_AUTH->AUTH_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 clb2 notify auth FM, simply by entering the name CLB2_NOTIFY_AUTH into the relevant SAP transaction such as SE37 or SE38.
Function Group: CLB2_INT_RFC
Program Name: SAPLCLB2_INT_RFC
Main Program: SAPLCLB2_INT_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CLB2_NOTIFY_AUTH 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 'CLB2_NOTIFY_AUTH'"Remote access to BadI CLB2_NOTIFY_AUTH->AUTH_CHECK.
EXPORTING
* IV_APPLI_CONTEXT = ' ' "Application Context for Collaboration
IV_BO_KEY = "Business Object Key
IV_BO_TYPE = "Collaboration: Business Object Type
IV_USER_NAME = "User Name
IV_FILTER = "OData Filter
IV_SCENARIO = "Scenario (subscription or notification)
IMPORTING
EV_ERROR_MESSAGE = "Error Message
EXCEPTIONS
AUTHORIZATION_ERROR = 1
IMPORTING Parameters details for CLB2_NOTIFY_AUTH
IV_APPLI_CONTEXT - Application Context for Collaboration
Data type: CLB2_APPL_CONTEXTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_BO_KEY - Business Object Key
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
IV_BO_TYPE - Collaboration: Business Object Type
Data type: CLB2_BO_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
IV_USER_NAME - User Name
Data type: SYUNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_FILTER - OData Filter
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
IV_SCENARIO - Scenario (subscription or notification)
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CLB2_NOTIFY_AUTH
EV_ERROR_MESSAGE - Error Message
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
AUTHORIZATION_ERROR - No Authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CLB2_NOTIFY_AUTH 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_ev_error_message | TYPE STRING, " | |||
| lv_iv_appli_context | TYPE CLB2_APPL_CONTEXT, " SPACE | |||
| lv_authorization_error | TYPE CLB2_APPL_CONTEXT, " | |||
| lv_iv_bo_key | TYPE STRING, " | |||
| lv_iv_bo_type | TYPE CLB2_BO_TYPE, " | |||
| lv_iv_user_name | TYPE SYUNAME, " | |||
| lv_iv_filter | TYPE STRING, " | |||
| lv_iv_scenario | TYPE STRING. " |
|   CALL FUNCTION 'CLB2_NOTIFY_AUTH' "Remote access to BadI CLB2_NOTIFY_AUTH->AUTH_CHECK |
| EXPORTING | ||
| IV_APPLI_CONTEXT | = lv_iv_appli_context | |
| IV_BO_KEY | = lv_iv_bo_key | |
| IV_BO_TYPE | = lv_iv_bo_type | |
| IV_USER_NAME | = lv_iv_user_name | |
| IV_FILTER | = lv_iv_filter | |
| IV_SCENARIO | = lv_iv_scenario | |
| IMPORTING | ||
| EV_ERROR_MESSAGE | = lv_ev_error_message | |
| EXCEPTIONS | ||
| AUTHORIZATION_ERROR = 1 | ||
| . " CLB2_NOTIFY_AUTH | ||
ABAP code using 7.40 inline data declarations to call FM CLB2_NOTIFY_AUTH
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_iv_appli_context) | = ' '. | |||
Search for further information about these or an SAP related objects