SAP BAPI_SYSTEM_MTE_SETSMPROP Function Module for Set the Specific Status Attribute Properties
BAPI_SYSTEM_MTE_SETSMPROP is a standard bapi system mte setsmprop SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set the Specific Status Attribute Properties 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 bapi system mte setsmprop FM, simply by entering the name BAPI_SYSTEM_MTE_SETSMPROP into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALX
Program Name: SAPLSALX
Main Program: SAPLSALX
Appliation area: S
Release date: 15-Jan-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_SYSTEM_MTE_SETSMPROP 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 'BAPI_SYSTEM_MTE_SETSMPROP'"Set the Specific Status Attribute Properties.
EXPORTING
TID = "MTE ID
EXTERNAL_USER_NAME = "Name of the SAP-External User
* VARIANT_NAME = "Variant Used
* TID_SPECIFIC = ' ' "'X' if Only the MTE Should Be Changed
* ALERT_MODE = "Alert Mode Used
* ALERT_SHIFT = "Alert Shift Used
IMPORTING
RETURN = "BAPI Return Structure
IMPORTING Parameters details for BAPI_SYSTEM_MTE_SETSMPROP
TID - MTE ID
Data type: BAPITIDOptional: No
Call by Reference: No ( called with pass by value option)
EXTERNAL_USER_NAME - Name of the SAP-External User
Data type: BAPIXMLOGR-EXTUSEROptional: No
Call by Reference: No ( called with pass by value option)
VARIANT_NAME - Variant Used
Data type: BAPIVARINT-NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
TID_SPECIFIC - 'X' if Only the MTE Should Be Changed
Data type: BAPIPARAMS-BOOL_PARADefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
ALERT_MODE - Alert Mode Used
Data type: BAPISMPROP-ALERTMODEOptional: Yes
Call by Reference: No ( called with pass by value option)
ALERT_SHIFT - Alert Shift Used
Data type: BAPISMPROP-ALERTSHIFTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_SYSTEM_MTE_SETSMPROP
RETURN - BAPI Return Structure
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_SYSTEM_MTE_SETSMPROP 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 BAPITID, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_external_user_name | TYPE BAPIXMLOGR-EXTUSER, " | |||
| lv_variant_name | TYPE BAPIVARINT-NAME, " | |||
| lv_tid_specific | TYPE BAPIPARAMS-BOOL_PARA, " ' ' | |||
| lv_alert_mode | TYPE BAPISMPROP-ALERTMODE, " | |||
| lv_alert_shift | TYPE BAPISMPROP-ALERTSHIFT. " |
|   CALL FUNCTION 'BAPI_SYSTEM_MTE_SETSMPROP' "Set the Specific Status Attribute Properties |
| EXPORTING | ||
| TID | = lv_tid | |
| EXTERNAL_USER_NAME | = lv_external_user_name | |
| VARIANT_NAME | = lv_variant_name | |
| TID_SPECIFIC | = lv_tid_specific | |
| ALERT_MODE | = lv_alert_mode | |
| ALERT_SHIFT | = lv_alert_shift | |
| IMPORTING | ||
| RETURN | = lv_return | |
| . " BAPI_SYSTEM_MTE_SETSMPROP | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_SYSTEM_MTE_SETSMPROP
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 EXTUSER FROM BAPIXMLOGR INTO @DATA(ld_external_user_name). | ||||
| "SELECT single NAME FROM BAPIVARINT INTO @DATA(ld_variant_name). | ||||
| "SELECT single BOOL_PARA FROM BAPIPARAMS INTO @DATA(ld_tid_specific). | ||||
| DATA(ld_tid_specific) | = ' '. | |||
| "SELECT single ALERTMODE FROM BAPISMPROP INTO @DATA(ld_alert_mode). | ||||
| "SELECT single ALERTSHIFT FROM BAPISMPROP INTO @DATA(ld_alert_shift). | ||||
Search for further information about these or an SAP related objects