SAP TMS_ALT_LOG_RECORD Function Module for External: Generate a TMS log record
TMS_ALT_LOG_RECORD is a standard tms alt log record SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for External: Generate a TMS log record 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 tms alt log record FM, simply by entering the name TMS_ALT_LOG_RECORD into the relevant SAP transaction such as SE37 or SE38.
Function Group: TMSA
Program Name: SAPLTMSA
Main Program: SAPLTMSA
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TMS_ALT_LOG_RECORD 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 'TMS_ALT_LOG_RECORD'"External: Generate a TMS log record.
EXPORTING
IV_SERVICE = "
* IV_MSGID = "
* IV_MSGTY = "
* IV_MSGNO = "
* IV_MSGV1 = "
* IV_MSGV2 = "
* IV_MSGV3 = "
* IV_MSGV4 = "
IV_FUNCTION = "
* IV_ERROR = "
* IV_SEVERITY = "
* IV_SYSTEM = "
* IV_DOMAIN = "
IV_TEXT = "
* IV_CONTEXT = "
* IV_EXECMODE = "
IMPORTING
EV_ALERTID = "
IMPORTING Parameters details for TMS_ALT_LOG_RECORD
IV_SERVICE -
Data type: STMSC-SERVICEOptional: No
Call by Reference: No ( called with pass by value option)
IV_MSGID -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MSGTY -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MSGNO -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MSGV1 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MSGV2 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MSGV3 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MSGV4 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_FUNCTION -
Data type: STMSCALERT-FUNCTIONOptional: No
Call by Reference: No ( called with pass by value option)
IV_ERROR -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SEVERITY -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SYSTEM -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_DOMAIN -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_TEXT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IV_CONTEXT -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_EXECMODE -
Data type: STMSC-EXECMODEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TMS_ALT_LOG_RECORD
EV_ALERTID -
Data type: CIALERTIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for TMS_ALT_LOG_RECORD 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_ev_alertid | TYPE CIALERTID, " | |||
| lv_iv_service | TYPE STMSC-SERVICE, " | |||
| lv_iv_msgid | TYPE STMSC, " | |||
| lv_iv_msgty | TYPE STMSC, " | |||
| lv_iv_msgno | TYPE STMSC, " | |||
| lv_iv_msgv1 | TYPE STMSC, " | |||
| lv_iv_msgv2 | TYPE STMSC, " | |||
| lv_iv_msgv3 | TYPE STMSC, " | |||
| lv_iv_msgv4 | TYPE STMSC, " | |||
| lv_iv_function | TYPE STMSCALERT-FUNCTION, " | |||
| lv_iv_error | TYPE STMSCALERT, " | |||
| lv_iv_severity | TYPE STMSCALERT, " | |||
| lv_iv_system | TYPE STMSCALERT, " | |||
| lv_iv_domain | TYPE STMSCALERT, " | |||
| lv_iv_text | TYPE STMSCALERT, " | |||
| lv_iv_context | TYPE STMSCALERT, " | |||
| lv_iv_execmode | TYPE STMSC-EXECMODE. " |
|   CALL FUNCTION 'TMS_ALT_LOG_RECORD' "External: Generate a TMS log record |
| EXPORTING | ||
| IV_SERVICE | = lv_iv_service | |
| IV_MSGID | = lv_iv_msgid | |
| IV_MSGTY | = lv_iv_msgty | |
| IV_MSGNO | = lv_iv_msgno | |
| IV_MSGV1 | = lv_iv_msgv1 | |
| IV_MSGV2 | = lv_iv_msgv2 | |
| IV_MSGV3 | = lv_iv_msgv3 | |
| IV_MSGV4 | = lv_iv_msgv4 | |
| IV_FUNCTION | = lv_iv_function | |
| IV_ERROR | = lv_iv_error | |
| IV_SEVERITY | = lv_iv_severity | |
| IV_SYSTEM | = lv_iv_system | |
| IV_DOMAIN | = lv_iv_domain | |
| IV_TEXT | = lv_iv_text | |
| IV_CONTEXT | = lv_iv_context | |
| IV_EXECMODE | = lv_iv_execmode | |
| IMPORTING | ||
| EV_ALERTID | = lv_ev_alertid | |
| . " TMS_ALT_LOG_RECORD | ||
ABAP code using 7.40 inline data declarations to call FM TMS_ALT_LOG_RECORD
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 SERVICE FROM STMSC INTO @DATA(ld_iv_service). | ||||
| "SELECT single FUNCTION FROM STMSCALERT INTO @DATA(ld_iv_function). | ||||
| "SELECT single EXECMODE FROM STMSC INTO @DATA(ld_iv_execmode). | ||||
Search for further information about these or an SAP related objects