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

Function TMS_PM_MODIFY_CONFIG 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_PM_MODIFY_CONFIG'".
EXPORTING
* IV_PROFILE_NAME = "
* IV_INACTIVE = "
* IV_VERBOSE = "
IMPORTING
EV_ALERTID = "
EV_NO_CHANGES = "Configuration not changed
TABLES
* TT_CONFIG_MOD = "
* TT_CONFIG_DEL = "
EXCEPTIONS
PM_NOT_ACTIVE = 1 READ_DOMAIN_CONFIG_FAILED = 2 NOT_A_CONTROLLER = 3 READ_TP_CONFIG_FAILED = 4 UPDATE_TP_CONFIG_FAILED = 5 DIST_TP_CONFIG_ALERT = 6
IMPORTING Parameters details for TMS_PM_MODIFY_CONFIG
IV_PROFILE_NAME -
Data type: TMSPVERS-PRONAMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_INACTIVE -
Data type: STMS_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_VERBOSE -
Data type: STMS_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TMS_PM_MODIFY_CONFIG
EV_ALERTID -
Data type: STMSCALERT-IDOptional: No
Call by Reference: Yes
EV_NO_CHANGES - Configuration not changed
Data type: STMS-FLAGOptional: No
Call by Reference: Yes
TABLES Parameters details for TMS_PM_MODIFY_CONFIG
TT_CONFIG_MOD -
Data type: TMSPCONFOptional: Yes
Call by Reference: No ( called with pass by value option)
TT_CONFIG_DEL -
Data type: TMSPCONFOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PM_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
READ_DOMAIN_CONFIG_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_A_CONTROLLER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
READ_TP_CONFIG_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UPDATE_TP_CONFIG_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DIST_TP_CONFIG_ALERT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TMS_PM_MODIFY_CONFIG 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_ev_alertid | TYPE STMSCALERT-ID, " | |||
| lv_pm_not_active | TYPE STMSCALERT, " | |||
| lt_tt_config_mod | TYPE STANDARD TABLE OF TMSPCONF, " | |||
| lv_iv_profile_name | TYPE TMSPVERS-PRONAM, " | |||
| lv_iv_inactive | TYPE STMS_FLAG, " | |||
| lv_ev_no_changes | TYPE STMS-FLAG, " | |||
| lt_tt_config_del | TYPE STANDARD TABLE OF TMSPCONF, " | |||
| lv_read_domain_config_failed | TYPE TMSPCONF, " | |||
| lv_iv_verbose | TYPE STMS_FLAG, " | |||
| lv_not_a_controller | TYPE STMS_FLAG, " | |||
| lv_read_tp_config_failed | TYPE STMS_FLAG, " | |||
| lv_update_tp_config_failed | TYPE STMS_FLAG, " | |||
| lv_dist_tp_config_alert | TYPE STMS_FLAG. " |
|   CALL FUNCTION 'TMS_PM_MODIFY_CONFIG' " |
| EXPORTING | ||
| IV_PROFILE_NAME | = lv_iv_profile_name | |
| IV_INACTIVE | = lv_iv_inactive | |
| IV_VERBOSE | = lv_iv_verbose | |
| IMPORTING | ||
| EV_ALERTID | = lv_ev_alertid | |
| EV_NO_CHANGES | = lv_ev_no_changes | |
| TABLES | ||
| TT_CONFIG_MOD | = lt_tt_config_mod | |
| TT_CONFIG_DEL | = lt_tt_config_del | |
| EXCEPTIONS | ||
| PM_NOT_ACTIVE = 1 | ||
| READ_DOMAIN_CONFIG_FAILED = 2 | ||
| NOT_A_CONTROLLER = 3 | ||
| READ_TP_CONFIG_FAILED = 4 | ||
| UPDATE_TP_CONFIG_FAILED = 5 | ||
| DIST_TP_CONFIG_ALERT = 6 | ||
| . " TMS_PM_MODIFY_CONFIG | ||
ABAP code using 7.40 inline data declarations to call FM TMS_PM_MODIFY_CONFIG
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 ID FROM STMSCALERT INTO @DATA(ld_ev_alertid). | ||||
| "SELECT single PRONAM FROM TMSPVERS INTO @DATA(ld_iv_profile_name). | ||||
| "SELECT single FLAG FROM STMS INTO @DATA(ld_ev_no_changes). | ||||
Search for further information about these or an SAP related objects