SAP SALI_MSC_REPORT_T100_MESSAGE Function Module for









SALI_MSC_REPORT_T100_MESSAGE is a standard sali msc report t100 message SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sali msc report t100 message FM, simply by entering the name SALI_MSC_REPORT_T100_MESSAGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SALI
Program Name: SAPLSALI
Main Program: SAPLSALI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SALI_MSC_REPORT_T100_MESSAGE 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 'SALI_MSC_REPORT_T100_MESSAGE'"
  EXPORTING
*  VALUE = AL_VAL_GREEN "
*  MSGARG2 =  "2nd message argument
*  ARGTYPE2 = 'C' "Type of 2nd message argument
*  MSGARG3 =  "3rd message argument
*  ARGTYPE3 = 'C' "Type of 3rd message argument
*  MSGARG4 =  "4th message argument
*  ARGTYPE4 = 'C' "Type of 4th message argument
*  DEFAULT_MSGTEXT =  "
*  REPORTEDBY =  "
*  SEVERITY = 0 "
*  MANDT = SY-MANDT "Client
*  UNAME = SY-UNAME "SAP User Name
*  EXTERNAL_MSGLINE_ID = ' ' "
   MSGID =  "
   MSGNO =  "
*  MSGARG1 =  "1st message argument
*  ARGTYPE1 = 'C' "Type of 1st message argument

 IMPORTING
   DETAILED_ERROR_TEXT =  "
   NEW_ALERT_AID =  "Alert: Global Alert Identifier

CHANGING
   TID =  "

EXCEPTIONS
   INVALID_TID = 1    WRONG_TYPECLASS = 2    INVALID_PARAMETERS = 3    COMMUNICATION_FAILURE = 4    OTHER_PROBLEM = 5    WRONG_SEGMENT = 6    INTERNAL_FAILURE_SALS = 7
.



IMPORTING Parameters details for SALI_MSC_REPORT_T100_MESSAGE

VALUE -

Data type: ALMSCRVAL-VALUE
Default: AL_VAL_GREEN
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGARG2 - 2nd message argument

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

ARGTYPE2 - Type of 2nd message argument

Data type: SXMIMSGRAW-ARGTYPE2
Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGARG3 - 3rd message argument

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

ARGTYPE3 - Type of 3rd message argument

Data type: SXMIMSGRAW-ARGTYPE3
Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGARG4 - 4th message argument

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

ARGTYPE4 - Type of 4th message argument

Data type: SXMIMSGRAW-ARGTYPE4
Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEFAULT_MSGTEXT -

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

REPORTEDBY -

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

SEVERITY -

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

MANDT - Client

Data type: SY-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

UNAME - SAP User Name

Data type: SY-UNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXTERNAL_MSGLINE_ID -

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

MSGID -

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

MSGNO -

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

MSGARG1 - 1st message argument

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

ARGTYPE1 - Type of 1st message argument

Data type: SXMIMSGRAW-ARGTYPE1
Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SALI_MSC_REPORT_T100_MESSAGE

DETAILED_ERROR_TEXT -

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

NEW_ALERT_AID - Alert: Global Alert Identifier

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

CHANGING Parameters details for SALI_MSC_REPORT_T100_MESSAGE

TID -

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

EXCEPTIONS details

INVALID_TID -

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

WRONG_TYPECLASS -

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

INVALID_PARAMETERS - Invalid parameter

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

COMMUNICATION_FAILURE -

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

OTHER_PROBLEM -

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

WRONG_SEGMENT -

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

INTERNAL_FAILURE_SALS - Internal Error

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

Copy and paste ABAP code example for SALI_MSC_REPORT_T100_MESSAGE 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_tid  TYPE ALGLOBTID, "   
lv_value  TYPE ALMSCRVAL-VALUE, "   AL_VAL_GREEN
lv_invalid_tid  TYPE ALMSCRVAL, "   
lv_detailed_error_text  TYPE STRING, "   
lv_msgarg2  TYPE C, "   
lv_argtype2  TYPE SXMIMSGRAW-ARGTYPE2, "   'C'
lv_msgarg3  TYPE C, "   
lv_argtype3  TYPE SXMIMSGRAW-ARGTYPE3, "   'C'
lv_msgarg4  TYPE C, "   
lv_argtype4  TYPE SXMIMSGRAW-ARGTYPE4, "   'C'
lv_default_msgtext  TYPE C, "   
lv_reportedby  TYPE C, "   
lv_severity  TYPE ALMSCRVAL-SEVERITY, "   0
lv_new_alert_aid  TYPE ALGLOBAID, "   
lv_wrong_typeclass  TYPE ALGLOBAID, "   
lv_mandt  TYPE SY-MANDT, "   SY-MANDT
lv_invalid_parameters  TYPE SY, "   
lv_uname  TYPE SY-UNAME, "   SY-UNAME
lv_communication_failure  TYPE SY, "   
lv_other_problem  TYPE SY, "   
lv_external_msgline_id  TYPE ALMSCRVAL-MSCGLLID, "   ' '
lv_msgid  TYPE SY-MSGID, "   
lv_wrong_segment  TYPE SY, "   
lv_msgno  TYPE SY-MSGNO, "   
lv_internal_failure_sals  TYPE SY, "   
lv_msgarg1  TYPE C, "   
lv_argtype1  TYPE SXMIMSGRAW-ARGTYPE1. "   'C'

  CALL FUNCTION 'SALI_MSC_REPORT_T100_MESSAGE'  "
    EXPORTING
         VALUE = lv_value
         MSGARG2 = lv_msgarg2
         ARGTYPE2 = lv_argtype2
         MSGARG3 = lv_msgarg3
         ARGTYPE3 = lv_argtype3
         MSGARG4 = lv_msgarg4
         ARGTYPE4 = lv_argtype4
         DEFAULT_MSGTEXT = lv_default_msgtext
         REPORTEDBY = lv_reportedby
         SEVERITY = lv_severity
         MANDT = lv_mandt
         UNAME = lv_uname
         EXTERNAL_MSGLINE_ID = lv_external_msgline_id
         MSGID = lv_msgid
         MSGNO = lv_msgno
         MSGARG1 = lv_msgarg1
         ARGTYPE1 = lv_argtype1
    IMPORTING
         DETAILED_ERROR_TEXT = lv_detailed_error_text
         NEW_ALERT_AID = lv_new_alert_aid
    CHANGING
         TID = lv_tid
    EXCEPTIONS
        INVALID_TID = 1
        WRONG_TYPECLASS = 2
        INVALID_PARAMETERS = 3
        COMMUNICATION_FAILURE = 4
        OTHER_PROBLEM = 5
        WRONG_SEGMENT = 6
        INTERNAL_FAILURE_SALS = 7
. " SALI_MSC_REPORT_T100_MESSAGE




ABAP code using 7.40 inline data declarations to call FM SALI_MSC_REPORT_T100_MESSAGE

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 VALUE FROM ALMSCRVAL INTO @DATA(ld_value).
DATA(ld_value) = AL_VAL_GREEN.
 
 
 
 
"SELECT single ARGTYPE2 FROM SXMIMSGRAW INTO @DATA(ld_argtype2).
DATA(ld_argtype2) = 'C'.
 
 
"SELECT single ARGTYPE3 FROM SXMIMSGRAW INTO @DATA(ld_argtype3).
DATA(ld_argtype3) = 'C'.
 
 
"SELECT single ARGTYPE4 FROM SXMIMSGRAW INTO @DATA(ld_argtype4).
DATA(ld_argtype4) = 'C'.
 
 
 
"SELECT single SEVERITY FROM ALMSCRVAL INTO @DATA(ld_severity).
 
 
 
"SELECT single MANDT FROM SY INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
 
"SELECT single UNAME FROM SY INTO @DATA(ld_uname).
DATA(ld_uname) = SY-UNAME.
 
 
 
"SELECT single MSCGLLID FROM ALMSCRVAL INTO @DATA(ld_external_msgline_id).
DATA(ld_external_msgline_id) = ' '.
 
"SELECT single MSGID FROM SY INTO @DATA(ld_msgid).
 
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_msgno).
 
 
 
"SELECT single ARGTYPE1 FROM SXMIMSGRAW INTO @DATA(ld_argtype1).
DATA(ld_argtype1) = 'C'.
 


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!