SAP TSY_MGR_CHECK_SYNCHRONIZATION Function Module for
TSY_MGR_CHECK_SYNCHRONIZATION is a standard tsy mgr check synchronization 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 tsy mgr check synchronization FM, simply by entering the name TSY_MGR_CHECK_SYNCHRONIZATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: TSY_MGR
Program Name: SAPLTSY_MGR
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TSY_MGR_CHECK_SYNCHRONIZATION 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 'TSY_MGR_CHECK_SYNCHRONIZATION'".
EXPORTING
* IV_SYSTEM = "TMS: System Name
* IV_DOMAIN = "TMS: Transport Domain
* IV_CLIENT = "TMS: Client
* IV_MONITOR = 'X' "General Flag
* IV_REREAD_SYSNAM = "TMS: System Name
* IV_FULL_REREAD = "General Flag
IT_IMPREQS = "
IMPORTING
ET_TSYIMPSTAT = "Transport Request Import Status
ET_TSYREQUEST = "Correlation of Transport Requests Between Systems
EXCEPTIONS
NO_SYNC_REQUEST = 1 GET_IMPSTAT_FAILED = 2 INTERNAL_ERROR = 3
IMPORTING Parameters details for TSY_MGR_CHECK_SYNCHRONIZATION
IV_SYSTEM - TMS: System Name
Data type: TMSSYSNAMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_DOMAIN - TMS: Transport Domain
Data type: TMSDOMNAMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CLIENT - TMS: Client
Data type: TMSCLIENTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_MONITOR - General Flag
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_REREAD_SYSNAM - TMS: System Name
Data type: TMSSYSNAMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_FULL_REREAD - General Flag
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_IMPREQS -
Data type: TSYIMPREQSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TSY_MGR_CHECK_SYNCHRONIZATION
ET_TSYIMPSTAT - Transport Request Import Status
Data type: TSYIMPSTATSOptional: No
Call by Reference: Yes
ET_TSYREQUEST - Correlation of Transport Requests Between Systems
Data type: TSYREQUESTSOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_SYNC_REQUEST -
Data type:Optional: No
Call by Reference: Yes
GET_IMPSTAT_FAILED -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TSY_MGR_CHECK_SYNCHRONIZATION 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 TMSSYSNAM, " | |||
| lv_et_tsyimpstat | TYPE TSYIMPSTATS, " | |||
| lv_no_sync_request | TYPE TSYIMPSTATS, " | |||
| lv_iv_domain | TYPE TMSDOMNAM, " | |||
| lv_et_tsyrequest | TYPE TSYREQUESTS, " | |||
| lv_get_impstat_failed | TYPE TSYREQUESTS, " | |||
| lv_iv_client | TYPE TMSCLIENT, " | |||
| lv_internal_error | TYPE TMSCLIENT, " | |||
| lv_iv_monitor | TYPE FLAG, " 'X' | |||
| lv_iv_reread_sysnam | TYPE TMSSYSNAM, " | |||
| lv_iv_full_reread | TYPE FLAG, " | |||
| lv_it_impreqs | TYPE TSYIMPREQS. " |
|   CALL FUNCTION 'TSY_MGR_CHECK_SYNCHRONIZATION' " |
| EXPORTING | ||
| IV_SYSTEM | = lv_iv_system | |
| IV_DOMAIN | = lv_iv_domain | |
| IV_CLIENT | = lv_iv_client | |
| IV_MONITOR | = lv_iv_monitor | |
| IV_REREAD_SYSNAM | = lv_iv_reread_sysnam | |
| IV_FULL_REREAD | = lv_iv_full_reread | |
| IT_IMPREQS | = lv_it_impreqs | |
| IMPORTING | ||
| ET_TSYIMPSTAT | = lv_et_tsyimpstat | |
| ET_TSYREQUEST | = lv_et_tsyrequest | |
| EXCEPTIONS | ||
| NO_SYNC_REQUEST = 1 | ||
| GET_IMPSTAT_FAILED = 2 | ||
| INTERNAL_ERROR = 3 | ||
| . " TSY_MGR_CHECK_SYNCHRONIZATION | ||
ABAP code using 7.40 inline data declarations to call FM TSY_MGR_CHECK_SYNCHRONIZATION
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.| DATA(ld_iv_monitor) | = 'X'. | |||
Search for further information about these or an SAP related objects