SAP MSAM_MO_NOTIFICATION_CREATE Function Module for MSAM : Notification Create

Search SAP Function Modules

MSAM_MO_NOTIFICATION_CREATE is a standard msam mo notification 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 MSAM : Notification Create 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 msam mo notification create FM, simply by entering the name MSAM_MO_NOTIFICATION_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: MSAM_MO_NOTIFICATION
Program Name: SAPLMSAM_MO_NOTIFICATION
Main Program: SAPLMSAM_MO_NOTIFICATION
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MSAM_MO_NOTIFICATION_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 'MSAM_MO_NOTIFICATION_CREATE'"MSAM : Notification Create
  EXPORTING
   NOTIFICATION_HEADER =  "Notification Header
*  EXTERNAL_NUMBER =  "Notification number
   NOTIF_TYPE =  "Notification type
*  ORDERID =  "Order number
*  I_PARTNER_TPA_KEY = ' ' "

 IMPORTING
   NOTIFICATION_EXPORT =  "BAPI Service Notification Header

TABLES
*  NOTIFICATION_ITEM =  "Notification item for creation
*  NOTIFICATION_CAUSE =  "Notification causes for creation
*  NOTIFICATION_ACTIVITY =  "Notification activity for creation
*  NOTIFICATION_TASK =  "Notification task for creation
*  NOTIFICATION_PARTNER =  "Partners for creation/change
*  NOTIFICATION_LONGTEXT =  "Notification long text
*  NOTIFICATION_USERSTATUS =  "User Status Definitions
*  RETURN =  "Return parameter

EXCEPTIONS
   ERROR_IN_INPUT_DATA = 1    NOTIFICATION_ALREADY_EXISTS = 2    TASK_NOT_REL_OR_COMPL = 3    USER_STATUS_NOT_CHANGED = 4 

.

IMPORTING Parameters details for MSAM_MO_NOTIFICATION_CREATE

NOTIFICATION_HEADER - Notification Header

Data type: MSAM10_NOTIF_HEADER
Optional: No
Call by Reference: No ( called with pass by value option)

EXTERNAL_NUMBER - Notification number

Data type: MSAM10_NOTIF_HEADER-NOTIF_NO
Optional: Yes
Call by Reference: No ( called with pass by value option)

NOTIF_TYPE - Notification type

Data type: MSAM10_NOTIF_HEADER-NOTIF_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

ORDERID - Order number

Data type: MSAM10_NOTIF_HEADER-ORDERID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PARTNER_TPA_KEY -

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MSAM_MO_NOTIFICATION_CREATE

NOTIFICATION_EXPORT - BAPI Service Notification Header

Data type: BAPI2080_NOTHDRE
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MSAM_MO_NOTIFICATION_CREATE

NOTIFICATION_ITEM - Notification item for creation

Data type: MSAM10_NOTIF_ITEM
Optional: Yes
Call by Reference: Yes

NOTIFICATION_CAUSE - Notification causes for creation

Data type: MSAM10_NOTIF_CAUSE
Optional: Yes
Call by Reference: Yes

NOTIFICATION_ACTIVITY - Notification activity for creation

Data type: MSAM10_NOTIF_ACTIVITY
Optional: Yes
Call by Reference: Yes

NOTIFICATION_TASK - Notification task for creation

Data type: MSAM10_NOTIF_TASK
Optional: Yes
Call by Reference: Yes

NOTIFICATION_PARTNER - Partners for creation/change

Data type: MSAM10_NOTIF_PARTNER
Optional: Yes
Call by Reference: Yes

NOTIFICATION_LONGTEXT - Notification long text

Data type: MSAM10_LONGTEXT
Optional: Yes
Call by Reference: Yes

NOTIFICATION_USERSTATUS - User Status Definitions

Data type: MSAM10_USER_STATUS
Optional: Yes
Call by Reference: Yes

RETURN - Return parameter

Data type: BAPIRET2
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_IN_INPUT_DATA -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOTIFICATION_ALREADY_EXISTS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TASK_NOT_REL_OR_COMPL -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

USER_STATUS_NOT_CHANGED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MSAM_MO_NOTIFICATION_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.

ABAP code using 7.40 inline data declarations to call FM MSAM_MO_NOTIFICATION_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.

Search for further information about these or an SAP related objects