SAP MAM30_011_CREATE Function Module for Create Notification
MAM30_011_CREATE is a standard mam30 011 create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create 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 mam30 011 create FM, simply by entering the name MAM30_011_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ALM_MEREP_011
Program Name: SAPLALM_MEREP_011
Main Program: SAPLALM_MEREP_011
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MAM30_011_CREATE 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 'MAM30_011_CREATE'"Create Notification.
EXPORTING
USER = "User Name
NOTIFICATION_HEADER = "Notification Header
IMPORTING
NOTIF_NO = "Header Data for Notification
TABLES
* NOTIFICATION_ITEM = "Notification Items
* CE_NOTIF_CAUSE = "Copy user-speific fields to the mobile device
* CE_NOTIF_ACTIVITY = "Copy user-speific fields to the mobile device
* CE_NOTIF_TASK = "Copy user-speific fields to the mobile device
* RETURN = "Return Parameter
* WSAP_EXTENSION = "SAP Enhancement
* NOTIFICATION_CAUSE = "Notification Causes
* NOTIFICATION_ACTIVITY = "Notification activity
* NOTIFICATION_TASK = "Notification Task
* NOTIFICATION_PARTNER = "Partner
* NOTIFICATION_LONGTEXT = "Long Texts
* NOTIFICATION_STATUS = "Table with Status Changes for User Status
* CE_NOTIF_HEADER = "Copy user-speific fields to the mobile device
* CE_NOTIF_ITEM = "Copy user-speific fields to the mobile device
IMPORTING Parameters details for MAM30_011_CREATE
USER - User Name
Data type: ALM_ME_USER_DATA-USERIDOptional: No
Call by Reference: No ( called with pass by value option)
NOTIFICATION_HEADER - Notification Header
Data type: MAM_30_NOTIF_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MAM30_011_CREATE
NOTIF_NO - Header Data for Notification
Data type: MAM_30_NOTIF_HEADER-NOTIF_NOOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MAM30_011_CREATE
NOTIFICATION_ITEM - Notification Items
Data type: MAM_30_NOTIF_ITEMOptional: Yes
Call by Reference: Yes
CE_NOTIF_CAUSE - Copy user-speific fields to the mobile device
Data type: ALM_ME_CUSTOMER_ENHANCEMENTOptional: Yes
Call by Reference: No ( called with pass by value option)
CE_NOTIF_ACTIVITY - Copy user-speific fields to the mobile device
Data type: ALM_ME_CUSTOMER_ENHANCEMENTOptional: Yes
Call by Reference: No ( called with pass by value option)
CE_NOTIF_TASK - Copy user-speific fields to the mobile device
Data type: ALM_ME_CUSTOMER_ENHANCEMENTOptional: Yes
Call by Reference: No ( called with pass by value option)
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
WSAP_EXTENSION - SAP Enhancement
Data type: ALM_ME_SAP_EXTENSIONOptional: Yes
Call by Reference: No ( called with pass by value option)
NOTIFICATION_CAUSE - Notification Causes
Data type: MAM_30_NOTIF_CAUSEOptional: Yes
Call by Reference: Yes
NOTIFICATION_ACTIVITY - Notification activity
Data type: MAM_30_NOTIF_ACTIVITYOptional: Yes
Call by Reference: Yes
NOTIFICATION_TASK - Notification Task
Data type: MAM_30_NOTIF_TASKOptional: Yes
Call by Reference: Yes
NOTIFICATION_PARTNER - Partner
Data type: MAM_30_PARTNER_KEY_STRUCTOptional: Yes
Call by Reference: Yes
NOTIFICATION_LONGTEXT - Long Texts
Data type: MAM_30_LONGTEXTOptional: Yes
Call by Reference: Yes
NOTIFICATION_STATUS - Table with Status Changes for User Status
Data type: MAM_30_USER_STATUS_CHANGESOptional: Yes
Call by Reference: Yes
CE_NOTIF_HEADER - Copy user-speific fields to the mobile device
Data type: ALM_ME_CUSTOMER_ENHANCEMENTOptional: Yes
Call by Reference: No ( called with pass by value option)
CE_NOTIF_ITEM - Copy user-speific fields to the mobile device
Data type: ALM_ME_CUSTOMER_ENHANCEMENTOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MAM30_011_CREATE 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_user | TYPE ALM_ME_USER_DATA-USERID, " | |||
| lv_notif_no | TYPE MAM_30_NOTIF_HEADER-NOTIF_NO, " | |||
| lt_notification_item | TYPE STANDARD TABLE OF MAM_30_NOTIF_ITEM, " | |||
| lt_ce_notif_cause | TYPE STANDARD TABLE OF ALM_ME_CUSTOMER_ENHANCEMENT, " | |||
| lt_ce_notif_activity | TYPE STANDARD TABLE OF ALM_ME_CUSTOMER_ENHANCEMENT, " | |||
| lt_ce_notif_task | TYPE STANDARD TABLE OF ALM_ME_CUSTOMER_ENHANCEMENT, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_wsap_extension | TYPE STANDARD TABLE OF ALM_ME_SAP_EXTENSION, " | |||
| lt_notification_cause | TYPE STANDARD TABLE OF MAM_30_NOTIF_CAUSE, " | |||
| lv_notification_header | TYPE MAM_30_NOTIF_HEADER, " | |||
| lt_notification_activity | TYPE STANDARD TABLE OF MAM_30_NOTIF_ACTIVITY, " | |||
| lt_notification_task | TYPE STANDARD TABLE OF MAM_30_NOTIF_TASK, " | |||
| lt_notification_partner | TYPE STANDARD TABLE OF MAM_30_PARTNER_KEY_STRUCT, " | |||
| lt_notification_longtext | TYPE STANDARD TABLE OF MAM_30_LONGTEXT, " | |||
| lt_notification_status | TYPE STANDARD TABLE OF MAM_30_USER_STATUS_CHANGES, " | |||
| lt_ce_notif_header | TYPE STANDARD TABLE OF ALM_ME_CUSTOMER_ENHANCEMENT, " | |||
| lt_ce_notif_item | TYPE STANDARD TABLE OF ALM_ME_CUSTOMER_ENHANCEMENT. " |
|   CALL FUNCTION 'MAM30_011_CREATE' "Create Notification |
| EXPORTING | ||
| USER | = lv_user | |
| NOTIFICATION_HEADER | = lv_notification_header | |
| IMPORTING | ||
| NOTIF_NO | = lv_notif_no | |
| TABLES | ||
| NOTIFICATION_ITEM | = lt_notification_item | |
| CE_NOTIF_CAUSE | = lt_ce_notif_cause | |
| CE_NOTIF_ACTIVITY | = lt_ce_notif_activity | |
| CE_NOTIF_TASK | = lt_ce_notif_task | |
| RETURN | = lt_return | |
| WSAP_EXTENSION | = lt_wsap_extension | |
| NOTIFICATION_CAUSE | = lt_notification_cause | |
| NOTIFICATION_ACTIVITY | = lt_notification_activity | |
| NOTIFICATION_TASK | = lt_notification_task | |
| NOTIFICATION_PARTNER | = lt_notification_partner | |
| NOTIFICATION_LONGTEXT | = lt_notification_longtext | |
| NOTIFICATION_STATUS | = lt_notification_status | |
| CE_NOTIF_HEADER | = lt_ce_notif_header | |
| CE_NOTIF_ITEM | = lt_ce_notif_item | |
| . " MAM30_011_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM MAM30_011_CREATE
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.| "SELECT single USERID FROM ALM_ME_USER_DATA INTO @DATA(ld_user). | ||||
| "SELECT single NOTIF_NO FROM MAM_30_NOTIF_HEADER INTO @DATA(ld_notif_no). | ||||
Search for further information about these or an SAP related objects