SAP DMC_MDS_EXEC_TP_COMMAND Function Module for Execute tp command via TIRNT_TP_INTERFACE

Search SAP Function Modules

DMC_MDS_EXEC_TP_COMMAND is a standard dmc mds exec tp command SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Execute tp command via TIRNT_TP_INTERFACE 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 dmc mds exec tp command FM, simply by entering the name DMC_MDS_EXEC_TP_COMMAND into the relevant SAP transaction such as SE37 or SE38.

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

Function DMC_MDS_EXEC_TP_COMMAND 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 'DMC_MDS_EXEC_TP_COMMAND'"Execute tp command via TIRNT_TP_INTERFACE
  EXPORTING
   IV_TP_COMMAND =  "tp command
*  IV_CLIENT =  "Client
*  IV_TRANSPORT_REQUEST =  "Request/Task
*  IV_TRANSPORT_ALL_FLAG =  "Flag ( 'X' or ' ' )
*  IV_SYSTEM_NAME =  "Name of an SAP System in the (active) transp. configuration

 IMPORTING
   ET_STDOUTS =  "Table Type for TPSTDOUT
   ET_LOG_LINES =  "Line for logs: technical and human readable
   ET_BUFFER_LINES =  "Lines of the tp buffer from SHOWBUFFER cmd / table type
   EV_TP_ALOG =  "File including path
   EV_TP_SLOG =  "File including path
   EV_TP_CMD_LINE =  "Command line for tp start via TRINT_TP_INTERFACE

EXCEPTIONS
   UNSUPPORTED_TP_COMMAND = 1    INSERT_TPSTAT_FAILED = 10    INSERT_TPLOG_FAILED = 11    INVALID_TP_COMMAND = 2    MISSING_PARAMETER = 3    INVALID_PARAMETER = 4    GET_TPPARAM_FAILED = 5    UPDATE_TP_DESTINATION_FAILED = 6    GET_TMS_INFO_FAILED = 7    PERMISSION_DENIED = 8    TP_CALL_FAILED = 9 

.

IMPORTING Parameters details for DMC_MDS_EXEC_TP_COMMAND

IV_TP_COMMAND - tp command

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

IV_CLIENT - Client

Data type: MANDT
Optional: Yes
Call by Reference: Yes

IV_TRANSPORT_REQUEST - Request/Task

Data type: TRKORR
Optional: Yes
Call by Reference: Yes

IV_TRANSPORT_ALL_FLAG - Flag ( 'X' or ' ' )

Data type: TRPARFLAG
Optional: Yes
Call by Reference: Yes

IV_SYSTEM_NAME - Name of an SAP System in the (active) transp. configuration

Data type: SYSNAME
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for DMC_MDS_EXEC_TP_COMMAND

ET_STDOUTS - Table Type for TPSTDOUT

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

ET_LOG_LINES - Line for logs: technical and human readable

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

ET_BUFFER_LINES - Lines of the tp buffer from SHOWBUFFER cmd / table type

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

EV_TP_ALOG - File including path

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

EV_TP_SLOG - File including path

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

EV_TP_CMD_LINE - Command line for tp start via TRINT_TP_INTERFACE

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

EXCEPTIONS details

UNSUPPORTED_TP_COMMAND - Command not supported by tp interface

Data type:
Optional: No
Call by Reference: Yes

INSERT_TPSTAT_FAILED -

Data type:
Optional: No
Call by Reference: Yes

INSERT_TPLOG_FAILED -

Data type:
Optional: No
Call by Reference: Yes

INVALID_TP_COMMAND - Command not known to tp interface

Data type:
Optional: No
Call by Reference: Yes

MISSING_PARAMETER -

Data type:
Optional: No
Call by Reference: Yes

INVALID_PARAMETER -

Data type:
Optional: No
Call by Reference: Yes

GET_TPPARAM_FAILED - Path of TPPARAM could not be determined

Data type:
Optional: No
Call by Reference: Yes

UPDATE_TP_DESTINATION_FAILED - The RFC destination could not be adapted

Data type:
Optional: No
Call by Reference: Yes

GET_TMS_INFO_FAILED -

Data type:
Optional: No
Call by Reference: Yes

PERMISSION_DENIED -

Data type:
Optional: No
Call by Reference: Yes

TP_CALL_FAILED - The tp call failed

Data type:
Optional: No
Call by Reference: Yes

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

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