SAP TMS_CE_CONFIG_ACTIVATE Function Module for

Search SAP Function Modules

TMS_CE_CONFIG_ACTIVATE is a standard tms ce config activate 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 ce config activate FM, simply by entering the name TMS_CE_CONFIG_ACTIVATE into the relevant SAP transaction such as SE37 or SE38.

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

Function TMS_CE_CONFIG_ACTIVATE 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_CE_CONFIG_ACTIVATE'"
  EXPORTING
*  IV_FORCE = ' ' "
*  IS_VERSION =  "

 IMPORTING
   ET_CORRLOG =  "Table Type for SPROT_U (Log Interface)
   ET_RC =  "TMS: Activation Errors
   ES_EXCEPTION =  "TMS CI: Alert Structure
   EV_OKCNT =  "

CHANGING
*  CT_SYSLIST =  "
*  CT_SELSYS =  "

EXCEPTIONS
   TCE_NOTHING_TO_DO = 1    TMS_NOT_CONFIGURED = 2    TMS_IS_NOT_ACTIVE = 3    NO_AUTHORITY_FOR_CONTROL = 4    TCE_TMS_CONFIGURATION_MISMATCH = 5    ALERT = 6 

.

IMPORTING Parameters details for TMS_CE_CONFIG_ACTIVATE

IV_FORCE -

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

IS_VERSION -

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

EXPORTING Parameters details for TMS_CE_CONFIG_ACTIVATE

ET_CORRLOG - Table Type for SPROT_U (Log Interface)

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

ET_RC - TMS: Activation Errors

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

ES_EXCEPTION - TMS CI: Alert Structure

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

EV_OKCNT -

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

CHANGING Parameters details for TMS_CE_CONFIG_ACTIVATE

CT_SYSLIST -

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

CT_SELSYS -

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

EXCEPTIONS details

TCE_NOTHING_TO_DO -

Data type:
Optional: No
Call by Reference: Yes

TMS_NOT_CONFIGURED -

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

TMS_IS_NOT_ACTIVE -

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

NO_AUTHORITY_FOR_CONTROL -

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

TCE_TMS_CONFIGURATION_MISMATCH -

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

ALERT -

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

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

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