SAP TMS_PM_READ_CURRENT_CONFIG Function Module for
TMS_PM_READ_CURRENT_CONFIG is a standard tms pm read current 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 read current config FM, simply by entering the name TMS_PM_READ_CURRENT_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_READ_CURRENT_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_READ_CURRENT_CONFIG'".
EXPORTING
* IV_SYSTEM = "
* IV_DOMAIN = "
* IV_PARAMETER = "
IMPORTING
EV_DOMAIN_NAME = "
EV_VERSION_NR = "
ES_VERSION = "
TABLES
* TT_VERSION = "TMS tp Profile Manager: Version Information
TT_CONFIG = "TMS tp Profile Manager: Configuration
EXCEPTIONS
PM_NOT_ACTIVE = 1 PARAMETER_NOT_FOUND = 2 READ_TP_CONFIG_FAILED = 3
IMPORTING Parameters details for TMS_PM_READ_CURRENT_CONFIG
IV_SYSTEM -
Data type: TMSPCONF-SYSNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_DOMAIN -
Data type: TMSPCONF-DOMNAMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PARAMETER -
Data type: TMSPCONF-NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TMS_PM_READ_CURRENT_CONFIG
EV_DOMAIN_NAME -
Data type: TMSMCONF-DOMNAMOptional: No
Call by Reference: Yes
EV_VERSION_NR -
Data type: TMSPVERS-VERSIONOptional: No
Call by Reference: Yes
ES_VERSION -
Data type: TMSPVERSOptional: No
Call by Reference: Yes
TABLES Parameters details for TMS_PM_READ_CURRENT_CONFIG
TT_VERSION - TMS tp Profile Manager: Version Information
Data type: TMSPVERSOptional: Yes
Call by Reference: Yes
TT_CONFIG - TMS tp Profile Manager: Configuration
Data type: TMSPCONFOptional: No
Call by Reference: Yes
EXCEPTIONS details
PM_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: Yes
PARAMETER_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
READ_TP_CONFIG_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TMS_PM_READ_CURRENT_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_iv_system | TYPE TMSPCONF-SYSNAME, " | |||
| lt_tt_version | TYPE STANDARD TABLE OF TMSPVERS, " | |||
| lv_pm_not_active | TYPE TMSPVERS, " | |||
| lv_ev_domain_name | TYPE TMSMCONF-DOMNAM, " | |||
| lv_iv_domain | TYPE TMSPCONF-DOMNAM, " | |||
| lt_tt_config | TYPE STANDARD TABLE OF TMSPCONF, " | |||
| lv_ev_version_nr | TYPE TMSPVERS-VERSION, " | |||
| lv_parameter_not_found | TYPE TMSPVERS, " | |||
| lv_es_version | TYPE TMSPVERS, " | |||
| lv_iv_parameter | TYPE TMSPCONF-NAME, " | |||
| lv_read_tp_config_failed | TYPE TMSPCONF. " |
|   CALL FUNCTION 'TMS_PM_READ_CURRENT_CONFIG' " |
| EXPORTING | ||
| IV_SYSTEM | = lv_iv_system | |
| IV_DOMAIN | = lv_iv_domain | |
| IV_PARAMETER | = lv_iv_parameter | |
| IMPORTING | ||
| EV_DOMAIN_NAME | = lv_ev_domain_name | |
| EV_VERSION_NR | = lv_ev_version_nr | |
| ES_VERSION | = lv_es_version | |
| TABLES | ||
| TT_VERSION | = lt_tt_version | |
| TT_CONFIG | = lt_tt_config | |
| EXCEPTIONS | ||
| PM_NOT_ACTIVE = 1 | ||
| PARAMETER_NOT_FOUND = 2 | ||
| READ_TP_CONFIG_FAILED = 3 | ||
| . " TMS_PM_READ_CURRENT_CONFIG | ||
ABAP code using 7.40 inline data declarations to call FM TMS_PM_READ_CURRENT_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 SYSNAME FROM TMSPCONF INTO @DATA(ld_iv_system). | ||||
| "SELECT single DOMNAM FROM TMSMCONF INTO @DATA(ld_ev_domain_name). | ||||
| "SELECT single DOMNAM FROM TMSPCONF INTO @DATA(ld_iv_domain). | ||||
| "SELECT single VERSION FROM TMSPVERS INTO @DATA(ld_ev_version_nr). | ||||
| "SELECT single NAME FROM TMSPCONF INTO @DATA(ld_iv_parameter). | ||||
Search for further information about these or an SAP related objects