SAP ISU_MSAM10_NOTIF_GETLIST Function Module for GetList for notification
ISU_MSAM10_NOTIF_GETLIST is a standard isu msam10 notif getlist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for GetList for notification 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 isu msam10 notif getlist FM, simply by entering the name ISU_MSAM10_NOTIF_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEWM_MSAM_NOTIFICATION
Program Name: SAPLEEWM_MSAM_NOTIFICATION
Main Program: SAPLEEWM_MSAM_NOTIFICATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_MSAM10_NOTIF_GETLIST 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 'ISU_MSAM10_NOTIF_GETLIST'"GetList for notification.
CHANGING
* CT_NOTIFICATION_LIST = "Notification header table type
* CT_RETURN = "Return parameter table
CHANGING Parameters details for ISU_MSAM10_NOTIF_GETLIST
CT_NOTIFICATION_LIST - Notification header table type
Data type: MSAM10_NOTIF_HEADER_TOptional: Yes
Call by Reference: Yes
CT_RETURN - Return parameter table
Data type: BAPIRET2_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ISU_MSAM10_NOTIF_GETLIST 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_ct_notification_list | TYPE MSAM10_NOTIF_HEADER_T, " | |||
| lv_ct_return | TYPE BAPIRET2_T. " |
|   CALL FUNCTION 'ISU_MSAM10_NOTIF_GETLIST' "GetList for notification |
| CHANGING | ||
| CT_NOTIFICATION_LIST | = lv_ct_notification_list | |
| CT_RETURN | = lv_ct_return | |
| . " ISU_MSAM10_NOTIF_GETLIST | ||
ABAP code using 7.40 inline data declarations to call FM ISU_MSAM10_NOTIF_GETLIST
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