SAP ISU_MSAM10_NOTIFICATION_CREATE Function Module for Create new IS-U related data for notification









ISU_MSAM10_NOTIFICATION_CREATE is a standard isu msam10 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 Create new IS-U related data 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 notification create FM, simply by entering the name ISU_MSAM10_NOTIFICATION_CREATE 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_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 'ISU_MSAM10_NOTIFICATION_CREATE'"Create new IS-U related data for notification
  EXPORTING
   IS_NOTIFICATION_HEADER =  "Notification Header

CHANGING
*  CT_NOTIF_ISU_MTR_RDNG_NOTE =  "MSAM-ISU: Meter Reading Note Data
*  CT_NOTIF_ISU_MTR_REPLACEMENT =  "Meter Replacement Results
*  CT_NOTIF_ISU_MTR_REP_DEVICE =  "ISU : Meter Reading Device Data
*  CT_NOTIF_ISU_MTR_REP_REGISTER =  "MSAM ISU - Meter Replacement Register
*  CT_NOTIF_ISU_MR_REP_TRANSFORM =  "MSAM - ISU : Meter replacement Transformer
*  CT_NOTIF_ISU_MR_RESULT =  "MSAM - ISU : Meter Reading Result
*  CT_WSAP_EXTENSION =  "Table for SAP extension
*  CT_CUST_EXTENSION =  "Table for customer enhancement
*  CT_RETURN =  "Return parameter table
.



IMPORTING Parameters details for ISU_MSAM10_NOTIFICATION_CREATE

IS_NOTIFICATION_HEADER - Notification Header

Data type: MSAM10_NOTIF_HEADER
Optional: No
Call by Reference: Yes

CHANGING Parameters details for ISU_MSAM10_NOTIFICATION_CREATE

CT_NOTIF_ISU_MTR_RDNG_NOTE - MSAM-ISU: Meter Reading Note Data

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

CT_NOTIF_ISU_MTR_REPLACEMENT - Meter Replacement Results

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

CT_NOTIF_ISU_MTR_REP_DEVICE - ISU : Meter Reading Device Data

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

CT_NOTIF_ISU_MTR_REP_REGISTER - MSAM ISU - Meter Replacement Register

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

CT_NOTIF_ISU_MR_REP_TRANSFORM - MSAM - ISU : Meter replacement Transformer

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

CT_NOTIF_ISU_MR_RESULT - MSAM - ISU : Meter Reading Result

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

CT_WSAP_EXTENSION - Table for SAP extension

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

CT_CUST_EXTENSION - Table for customer enhancement

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

CT_RETURN - Return parameter table

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

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

DATA:
lv_is_notification_header  TYPE MSAM10_NOTIF_HEADER, "   
lv_ct_notif_isu_mtr_rdng_note  TYPE MSAM10_METER_READING_NOTE_T, "   
lv_ct_notif_isu_mtr_replacement  TYPE MSAM10_METER_REPLACEMENT_T, "   
lv_ct_notif_isu_mtr_rep_device  TYPE MSAM10_MR_DEVICE_T, "   
lv_ct_notif_isu_mtr_rep_register  TYPE MSAM10_MR_REGISTER_T, "   
lv_ct_notif_isu_mr_rep_transform  TYPE MSAM10_MR_TRANSFORMER_T, "   
lv_ct_notif_isu_mr_result  TYPE MSAM10_MR_RESULT_T, "   
lv_ct_wsap_extension  TYPE MSAM_MO_SAP_ENHANCEMENT_T, "   
lv_ct_cust_extension  TYPE MSAM_MO_CUSTOMER_ENHANCEMENT_T, "   
lv_ct_return  TYPE BAPIRET2_T. "   

  CALL FUNCTION 'ISU_MSAM10_NOTIFICATION_CREATE'  "Create new IS-U related data for notification
    EXPORTING
         IS_NOTIFICATION_HEADER = lv_is_notification_header
    CHANGING
         CT_NOTIF_ISU_MTR_RDNG_NOTE = lv_ct_notif_isu_mtr_rdng_note
         CT_NOTIF_ISU_MTR_REPLACEMENT = lv_ct_notif_isu_mtr_replacement
         CT_NOTIF_ISU_MTR_REP_DEVICE = lv_ct_notif_isu_mtr_rep_device
         CT_NOTIF_ISU_MTR_REP_REGISTER = lv_ct_notif_isu_mtr_rep_register
         CT_NOTIF_ISU_MR_REP_TRANSFORM = lv_ct_notif_isu_mr_rep_transform
         CT_NOTIF_ISU_MR_RESULT = lv_ct_notif_isu_mr_result
         CT_WSAP_EXTENSION = lv_ct_wsap_extension
         CT_CUST_EXTENSION = lv_ct_cust_extension
         CT_RETURN = lv_ct_return
. " ISU_MSAM10_NOTIFICATION_CREATE




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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!