SAP TMS_CI_DIRECT_SEND_COMMAND Function Module for









TMS_CI_DIRECT_SEND_COMMAND is a standard tms ci direct send command 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 ci direct send command FM, simply by entering the name TMS_CI_DIRECT_SEND_COMMAND into the relevant SAP transaction such as SE37 or SE38.

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



Function TMS_CI_DIRECT_SEND_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 'TMS_CI_DIRECT_SEND_COMMAND'"
  EXPORTING
   _TARSYSTEM =  "
   SELECTION =  "
   _TARDOMAIN =  "
   _SERVICE =  "
   _COMMAND =  "
*  _TARCLIENT =  "
*  _LOCALRFC =  "
*  _EXECMODE = 'ON' "
*  _CONTEXT =  "
*  _SUPER_ALLOWED = 'X' "

 IMPORTING
   _SUPER_USED =  "
   _EXCEPTION =  "
   RESULT =  "

EXCEPTIONS
   ALERT = 1    NOT_SUPPORTED = 2
.



IMPORTING Parameters details for TMS_CI_DIRECT_SEND_COMMAND

_TARSYSTEM -

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

SELECTION -

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

_TARDOMAIN -

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

_SERVICE -

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

_COMMAND -

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

_TARCLIENT -

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

_LOCALRFC -

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

_EXECMODE -

Data type: CIEXEMOD
Default: 'ON'
Optional: Yes
Call by Reference: No ( called with pass by value option)

_CONTEXT -

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

_SUPER_ALLOWED -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for TMS_CI_DIRECT_SEND_COMMAND

_SUPER_USED -

Data type: STMSC-FLAG
Optional: No
Call by Reference: Yes

_EXCEPTION -

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

RESULT -

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

EXCEPTIONS details

ALERT -

Data type:
Optional: No
Call by Reference: Yes

NOT_SUPPORTED -

Data type:
Optional: No
Call by Reference: Yes

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

DATA:
lv_alert  TYPE STRING, "   
lv__tarsystem  TYPE TMSSYSNAM, "   
lv__super_used  TYPE STMSC-FLAG, "   
lv_selection  TYPE STRING, "   
lv__exception  TYPE STMSCALERT, "   
lv__tardomain  TYPE TMSDOMNAM, "   
lv_not_supported  TYPE TMSDOMNAM, "   
lv_result  TYPE STRING, "   
lv__service  TYPE CISERVICE, "   
lv__command  TYPE CICOMMAND, "   
lv__tarclient  TYPE SYMANDT, "   
lv__localrfc  TYPE FLAG, "   
lv__execmode  TYPE CIEXEMOD, "   'ON'
lv__context  TYPE CICONTEXT, "   
lv__super_allowed  TYPE FLAG. "   'X'

  CALL FUNCTION 'TMS_CI_DIRECT_SEND_COMMAND'  "
    EXPORTING
         _TARSYSTEM = lv__tarsystem
         SELECTION = lv_selection
         _TARDOMAIN = lv__tardomain
         _SERVICE = lv__service
         _COMMAND = lv__command
         _TARCLIENT = lv__tarclient
         _LOCALRFC = lv__localrfc
         _EXECMODE = lv__execmode
         _CONTEXT = lv__context
         _SUPER_ALLOWED = lv__super_allowed
    IMPORTING
         _SUPER_USED = lv__super_used
         _EXCEPTION = lv__exception
         RESULT = lv_result
    EXCEPTIONS
        ALERT = 1
        NOT_SUPPORTED = 2
. " TMS_CI_DIRECT_SEND_COMMAND




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

 
 
"SELECT single FLAG FROM STMSC INTO @DATA(ld__super_used).
 
 
 
 
 
 
 
 
 
 
DATA(ld__execmode) = 'ON'.
 
 
DATA(ld__super_allowed) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!