SAP TMS_TP_MAINTAIN_BUFFER Function Module for
TMS_TP_MAINTAIN_BUFFER is a standard tms tp maintain buffer 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 tms tp maintain buffer FM, simply by entering the name TMS_TP_MAINTAIN_BUFFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: TMST
Program Name: SAPLTMST
Main Program: SAPLTMST
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TMS_TP_MAINTAIN_BUFFER 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_TP_MAINTAIN_BUFFER'".
EXPORTING
IV_TP_COMMAND = "tp Command
* IV_PRID_TEXT = "
* IV_PRID_MIN = 0 "
* IV_PRID_MAX = 100 "
IV_SYSTEM_NAME = "
* IV_REQUEST = "
* IV_TARCLI = "
* IV_OLDCLI = "
* IV_NO_DELIVERY = "
* IV_WRONG_POS = "
* IV_REMOTE_SYS = "
* IV_TP_OPTIONS = "
IMPORTING
EV_TP_CMD_STRG = "
EV_TP_RET_CODE = "
EV_TP_MESSAGE = "
EV_TP_VERSION = "
EV_TP_ALOG = "
EV_TP_SLOG = "
EV_TP_PID = "
TABLES
* TT_BUFFER = "
* TT_STDOUT = "
EXCEPTIONS
INVALID_COMMAND = 1 PERMISSION_DENIED = 2 TP_CALL_FAILED = 3 TP_INTERFACE_ERROR = 4 TP_REPORTED_ERROR = 5
IMPORTING Parameters details for TMS_TP_MAINTAIN_BUFFER
IV_TP_COMMAND - tp Command
Data type: STPA-COMMANDOptional: No
Call by Reference: No ( called with pass by value option)
IV_PRID_TEXT -
Data type: STPA-MESSAGEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PRID_MIN -
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PRID_MAX -
Data type: IDefault: 100
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SYSTEM_NAME -
Data type: STPA-SYSNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_REQUEST -
Data type: STPA-TRKORROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_TARCLI -
Data type: STPA-CLIENTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OLDCLI -
Data type: STPA-CLIENTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_DELIVERY -
Data type: STPA-FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_WRONG_POS -
Data type: STPA-FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_REMOTE_SYS -
Data type: STPA-SYSNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_TP_OPTIONS -
Data type: STPA-OPTIONSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TMS_TP_MAINTAIN_BUFFER
EV_TP_CMD_STRG -
Data type: STPA-CMDSTRINGOptional: No
Call by Reference: Yes
EV_TP_RET_CODE -
Data type: STPA-RETCODEOptional: No
Call by Reference: Yes
EV_TP_MESSAGE -
Data type: STPA-MESSAGEOptional: No
Call by Reference: Yes
EV_TP_VERSION -
Data type: STPA-VERSIONOptional: No
Call by Reference: Yes
EV_TP_ALOG -
Data type: STPA-FILEOptional: No
Call by Reference: Yes
EV_TP_SLOG -
Data type: STPA-FILEOptional: No
Call by Reference: Yes
EV_TP_PID -
Data type: STPA-PIDOptional: No
Call by Reference: Yes
TABLES Parameters details for TMS_TP_MAINTAIN_BUFFER
TT_BUFFER -
Data type: TPBUFFEROptional: Yes
Call by Reference: No ( called with pass by value option)
TT_STDOUT -
Data type: TPSTDOUTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_COMMAND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PERMISSION_DENIED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TP_CALL_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TP_INTERFACE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TP_REPORTED_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TMS_TP_MAINTAIN_BUFFER 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: | ||||
| lt_tt_buffer | TYPE STANDARD TABLE OF TPBUFFER, " | |||
| lv_iv_tp_command | TYPE STPA-COMMAND, " | |||
| lv_ev_tp_cmd_strg | TYPE STPA-CMDSTRING, " | |||
| lv_invalid_command | TYPE STPA, " | |||
| lv_iv_prid_text | TYPE STPA-MESSAGE, " | |||
| lv_iv_prid_min | TYPE I, " 0 | |||
| lv_iv_prid_max | TYPE I, " 100 | |||
| lt_tt_stdout | TYPE STANDARD TABLE OF TPSTDOUT, " | |||
| lv_ev_tp_ret_code | TYPE STPA-RETCODE, " | |||
| lv_iv_system_name | TYPE STPA-SYSNAME, " | |||
| lv_permission_denied | TYPE STPA, " | |||
| lv_iv_request | TYPE STPA-TRKORR, " | |||
| lv_ev_tp_message | TYPE STPA-MESSAGE, " | |||
| lv_tp_call_failed | TYPE STPA, " | |||
| lv_iv_tarcli | TYPE STPA-CLIENT, " | |||
| lv_ev_tp_version | TYPE STPA-VERSION, " | |||
| lv_tp_interface_error | TYPE STPA, " | |||
| lv_iv_oldcli | TYPE STPA-CLIENT, " | |||
| lv_ev_tp_alog | TYPE STPA-FILE, " | |||
| lv_tp_reported_error | TYPE STPA, " | |||
| lv_ev_tp_slog | TYPE STPA-FILE, " | |||
| lv_iv_no_delivery | TYPE STPA-FLAG, " | |||
| lv_ev_tp_pid | TYPE STPA-PID, " | |||
| lv_iv_wrong_pos | TYPE STPA-FLAG, " | |||
| lv_iv_remote_sys | TYPE STPA-SYSNAME, " | |||
| lv_iv_tp_options | TYPE STPA-OPTIONS. " |
|   CALL FUNCTION 'TMS_TP_MAINTAIN_BUFFER' " |
| EXPORTING | ||
| IV_TP_COMMAND | = lv_iv_tp_command | |
| IV_PRID_TEXT | = lv_iv_prid_text | |
| IV_PRID_MIN | = lv_iv_prid_min | |
| IV_PRID_MAX | = lv_iv_prid_max | |
| IV_SYSTEM_NAME | = lv_iv_system_name | |
| IV_REQUEST | = lv_iv_request | |
| IV_TARCLI | = lv_iv_tarcli | |
| IV_OLDCLI | = lv_iv_oldcli | |
| IV_NO_DELIVERY | = lv_iv_no_delivery | |
| IV_WRONG_POS | = lv_iv_wrong_pos | |
| IV_REMOTE_SYS | = lv_iv_remote_sys | |
| IV_TP_OPTIONS | = lv_iv_tp_options | |
| IMPORTING | ||
| EV_TP_CMD_STRG | = lv_ev_tp_cmd_strg | |
| EV_TP_RET_CODE | = lv_ev_tp_ret_code | |
| EV_TP_MESSAGE | = lv_ev_tp_message | |
| EV_TP_VERSION | = lv_ev_tp_version | |
| EV_TP_ALOG | = lv_ev_tp_alog | |
| EV_TP_SLOG | = lv_ev_tp_slog | |
| EV_TP_PID | = lv_ev_tp_pid | |
| TABLES | ||
| TT_BUFFER | = lt_tt_buffer | |
| TT_STDOUT | = lt_tt_stdout | |
| EXCEPTIONS | ||
| INVALID_COMMAND = 1 | ||
| PERMISSION_DENIED = 2 | ||
| TP_CALL_FAILED = 3 | ||
| TP_INTERFACE_ERROR = 4 | ||
| TP_REPORTED_ERROR = 5 | ||
| . " TMS_TP_MAINTAIN_BUFFER | ||
ABAP code using 7.40 inline data declarations to call FM TMS_TP_MAINTAIN_BUFFER
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 COMMAND FROM STPA INTO @DATA(ld_iv_tp_command). | ||||
| "SELECT single CMDSTRING FROM STPA INTO @DATA(ld_ev_tp_cmd_strg). | ||||
| "SELECT single MESSAGE FROM STPA INTO @DATA(ld_iv_prid_text). | ||||
| DATA(ld_iv_prid_max) | = 100. | |||
| "SELECT single RETCODE FROM STPA INTO @DATA(ld_ev_tp_ret_code). | ||||
| "SELECT single SYSNAME FROM STPA INTO @DATA(ld_iv_system_name). | ||||
| "SELECT single TRKORR FROM STPA INTO @DATA(ld_iv_request). | ||||
| "SELECT single MESSAGE FROM STPA INTO @DATA(ld_ev_tp_message). | ||||
| "SELECT single CLIENT FROM STPA INTO @DATA(ld_iv_tarcli). | ||||
| "SELECT single VERSION FROM STPA INTO @DATA(ld_ev_tp_version). | ||||
| "SELECT single CLIENT FROM STPA INTO @DATA(ld_iv_oldcli). | ||||
| "SELECT single FILE FROM STPA INTO @DATA(ld_ev_tp_alog). | ||||
| "SELECT single FILE FROM STPA INTO @DATA(ld_ev_tp_slog). | ||||
| "SELECT single FLAG FROM STPA INTO @DATA(ld_iv_no_delivery). | ||||
| "SELECT single PID FROM STPA INTO @DATA(ld_ev_tp_pid). | ||||
| "SELECT single FLAG FROM STPA INTO @DATA(ld_iv_wrong_pos). | ||||
| "SELECT single SYSNAME FROM STPA INTO @DATA(ld_iv_remote_sys). | ||||
| "SELECT single OPTIONS FROM STPA INTO @DATA(ld_iv_tp_options). | ||||
Search for further information about these or an SAP related objects