SAP TMS_MGR_CHECK_PREDECESSORS Function Module for
TMS_MGR_CHECK_PREDECESSORS is a standard tms mgr check predecessors 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 mgr check predecessors FM, simply by entering the name TMS_MGR_CHECK_PREDECESSORS 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_MGR_CHECK_PREDECESSORS 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_MGR_CHECK_PREDECESSORS'".
EXPORTING
IT_IMPORT = "
IT_SUCCESSORS = "
IV_CTC = "
* IV_PRELIMINARY = ' ' "
IV_TARGET_SYSTEM = "Name of an R/3 System of the (active) transp. configuration
* IV_TARGET_DOMAIN = "TMS: transport domain
* IV_SHOW_CONFLICTS_ONLY = 'X' "
* IV_MONITOR = 'X' "
* IV_VERBOSE = "
IMPORTING
ET_SERIALS = "Predecessor-Successor Relationships Between Transports
EV_ALERTID = "CI: alert ID
EXCEPTIONS
CHECK_PREDECESSORS_FAILED = 1
IMPORTING Parameters details for TMS_MGR_CHECK_PREDECESSORS
IT_IMPORT -
Data type: TPREQUESTSOptional: No
Call by Reference: Yes
IT_SUCCESSORS -
Data type: TPREQUESTSOptional: No
Call by Reference: Yes
IV_CTC -
Data type: COptional: No
Call by Reference: Yes
IV_PRELIMINARY -
Data type: CDefault: SPACE
Optional: No
Call by Reference: Yes
IV_TARGET_SYSTEM - Name of an R/3 System of the (active) transp. configuration
Data type: SYSNAMEOptional: No
Call by Reference: Yes
IV_TARGET_DOMAIN - TMS: transport domain
Data type: TMSDOMNAMOptional: Yes
Call by Reference: Yes
IV_SHOW_CONFLICTS_ONLY -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_MONITOR -
Data type: STMS_FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_VERBOSE -
Data type: STMS_FLAGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for TMS_MGR_CHECK_PREDECESSORS
ET_SERIALS - Predecessor-Successor Relationships Between Transports
Data type: TMS_SERIALSOptional: No
Call by Reference: Yes
EV_ALERTID - CI: alert ID
Data type: STMSCALERT-IDOptional: No
Call by Reference: Yes
EXCEPTIONS details
CHECK_PREDECESSORS_FAILED - Function could not be performed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TMS_MGR_CHECK_PREDECESSORS 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_it_import | TYPE TPREQUESTS, " | |||
| lv_et_serials | TYPE TMS_SERIALS, " | |||
| lv_check_predecessors_failed | TYPE TMS_SERIALS, " | |||
| lv_ev_alertid | TYPE STMSCALERT-ID, " | |||
| lv_it_successors | TYPE TPREQUESTS, " | |||
| lv_iv_ctc | TYPE C, " | |||
| lv_iv_preliminary | TYPE C, " SPACE | |||
| lv_iv_target_system | TYPE SYSNAME, " | |||
| lv_iv_target_domain | TYPE TMSDOMNAM, " | |||
| lv_iv_show_conflicts_only | TYPE C, " 'X' | |||
| lv_iv_monitor | TYPE STMS_FLAG, " 'X' | |||
| lv_iv_verbose | TYPE STMS_FLAG. " |
|   CALL FUNCTION 'TMS_MGR_CHECK_PREDECESSORS' " |
| EXPORTING | ||
| IT_IMPORT | = lv_it_import | |
| IT_SUCCESSORS | = lv_it_successors | |
| IV_CTC | = lv_iv_ctc | |
| IV_PRELIMINARY | = lv_iv_preliminary | |
| IV_TARGET_SYSTEM | = lv_iv_target_system | |
| IV_TARGET_DOMAIN | = lv_iv_target_domain | |
| IV_SHOW_CONFLICTS_ONLY | = lv_iv_show_conflicts_only | |
| IV_MONITOR | = lv_iv_monitor | |
| IV_VERBOSE | = lv_iv_verbose | |
| IMPORTING | ||
| ET_SERIALS | = lv_et_serials | |
| EV_ALERTID | = lv_ev_alertid | |
| EXCEPTIONS | ||
| CHECK_PREDECESSORS_FAILED = 1 | ||
| . " TMS_MGR_CHECK_PREDECESSORS | ||
ABAP code using 7.40 inline data declarations to call FM TMS_MGR_CHECK_PREDECESSORS
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). | ||||
| DATA(ld_iv_preliminary) | = ' '. | |||
| DATA(ld_iv_show_conflicts_only) | = 'X'. | |||
| DATA(ld_iv_monitor) | = 'X'. | |||
Search for further information about these or an SAP related objects