SAP SALI_SMES_REPORT_T100_MESSAGE Function Module for

Search SAP Function Modules

SALI_SMES_REPORT_T100_MESSAGE is a standard sali smes 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 smes report t100 message FM, simply by entering the name SALI_SMES_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_SMES_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_SMES_REPORT_T100_MESSAGE'"
  EXPORTING
*  MSGVALUE = AL_VAL_GREEN "
*  MSGARG4 =  "4th message argument
*  ARGTYPE4 = 'C' "Type of 4th message argument
*  DEFAULT_MSGTEXT =  "Standard message or text message
*  REPORTEDBY =  "
   MSGID =  "
   MSGNO =  "
*  MSGARG1 =  "1st message argument
*  ARGTYPE1 = 'C' "Type of 1st message argument
*  MSGARG2 =  "2nd message argument
*  ARGTYPE2 = 'C' "Type of 2nd message argument
*  MSGARG3 =  "3rd message argument
*  ARGTYPE3 = 'C' "Type of 3rd message argument

 IMPORTING
   DETAILED_ERROR_TEXT =  "

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_SMES_REPORT_T100_MESSAGE

MSGVALUE -

Data type: ALSMSGRVAL-SMSGVALUE
Default: AL_VAL_GREEN
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 - Standard message or text message

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)

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)

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)

EXPORTING Parameters details for SALI_SMES_REPORT_T100_MESSAGE

DETAILED_ERROR_TEXT -

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

CHANGING Parameters details for SALI_SMES_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 -

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

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

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

Search for further information about these or an SAP related objects