SAP TMS_CFG_START_DISTRIBUTION Function Module for









TMS_CFG_START_DISTRIBUTION is a standard tms cfg start distribution 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 cfg start distribution FM, simply by entering the name TMS_CFG_START_DISTRIBUTION into the relevant SAP transaction such as SE37 or SE38.

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



Function TMS_CFG_START_DISTRIBUTION 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_CFG_START_DISTRIBUTION'"
EXPORTING
IV_SRC_SYSTEM = "
IV_SRC_DOMAIN = "
IV_DIST_MODE = "
* IV_CI_CONF = "
* IV_TP_CONF = "
* IV_CE_CONF = "
* IV_FORCE = "

IMPORTING
EV_CLIENT_UPDATED = "
ES_EXCEPTION = "

EXCEPTIONS
READ_CONFIG_FAILED = 1 SYSTEM_IS_NOT_A_CONTROLLER = 2 SYSTEM_NOT_ALLOWED = 3 DISTRIBUTION_REJECTED = 4 DIST_CONFIG_ALERT = 5 DIST_CONFIG_FAILED = 6 NOTHING_DONE = 7
.



IMPORTING Parameters details for TMS_CFG_START_DISTRIBUTION

IV_SRC_SYSTEM -

Data type: TMSCSYS-SYSNAM
Optional: No
Call by Reference: No ( called with pass by value option)

IV_SRC_DOMAIN -

Data type: TMSCSYS-DOMNAM
Optional: No
Call by Reference: No ( called with pass by value option)

IV_DIST_MODE -

Data type: TMSCDOM-DISTMODE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_CI_CONF -

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

IV_TP_CONF -

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

IV_CE_CONF -

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

IV_FORCE -

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

EXPORTING Parameters details for TMS_CFG_START_DISTRIBUTION

EV_CLIENT_UPDATED -

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

ES_EXCEPTION -

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

EXCEPTIONS details

READ_CONFIG_FAILED -

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

SYSTEM_IS_NOT_A_CONTROLLER -

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

SYSTEM_NOT_ALLOWED -

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

DISTRIBUTION_REJECTED -

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

DIST_CONFIG_ALERT -

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

DIST_CONFIG_FAILED -

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

NOTHING_DONE -

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

Copy and paste ABAP code example for TMS_CFG_START_DISTRIBUTION 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_iv_src_system  TYPE TMSCSYS-SYSNAM, "   
lv_ev_client_updated  TYPE STMS_FLAG, "   
lv_read_config_failed  TYPE STMS_FLAG, "   
lv_es_exception  TYPE STMSCALERT, "   
lv_iv_src_domain  TYPE TMSCSYS-DOMNAM, "   
lv_system_is_not_a_controller  TYPE TMSCSYS, "   
lv_iv_dist_mode  TYPE TMSCDOM-DISTMODE, "   
lv_system_not_allowed  TYPE TMSCDOM, "   
lv_iv_ci_conf  TYPE STMS_FLAG, "   
lv_distribution_rejected  TYPE STMS_FLAG, "   
lv_iv_tp_conf  TYPE STMS_FLAG, "   
lv_dist_config_alert  TYPE STMS_FLAG, "   
lv_iv_ce_conf  TYPE STMS_FLAG, "   
lv_dist_config_failed  TYPE STMS_FLAG, "   
lv_iv_force  TYPE STMS_FLAG, "   
lv_nothing_done  TYPE STMS_FLAG. "   

  CALL FUNCTION 'TMS_CFG_START_DISTRIBUTION'  "
    EXPORTING
         IV_SRC_SYSTEM = lv_iv_src_system
         IV_SRC_DOMAIN = lv_iv_src_domain
         IV_DIST_MODE = lv_iv_dist_mode
         IV_CI_CONF = lv_iv_ci_conf
         IV_TP_CONF = lv_iv_tp_conf
         IV_CE_CONF = lv_iv_ce_conf
         IV_FORCE = lv_iv_force
    IMPORTING
         EV_CLIENT_UPDATED = lv_ev_client_updated
         ES_EXCEPTION = lv_es_exception
    EXCEPTIONS
        READ_CONFIG_FAILED = 1
        SYSTEM_IS_NOT_A_CONTROLLER = 2
        SYSTEM_NOT_ALLOWED = 3
        DISTRIBUTION_REJECTED = 4
        DIST_CONFIG_ALERT = 5
        DIST_CONFIG_FAILED = 6
        NOTHING_DONE = 7
. " TMS_CFG_START_DISTRIBUTION




ABAP code using 7.40 inline data declarations to call FM TMS_CFG_START_DISTRIBUTION

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 SYSNAM FROM TMSCSYS INTO @DATA(ld_iv_src_system).
 
 
 
 
"SELECT single DOMNAM FROM TMSCSYS INTO @DATA(ld_iv_src_domain).
 
 
"SELECT single DISTMODE FROM TMSCDOM INTO @DATA(ld_iv_dist_mode).
 
 
 
 
 
 
 
 
 
 


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!