SAP Function Modules

TMS_MGR_IMPORT_TR_QUEUE SAP Function module







TMS_MGR_IMPORT_TR_QUEUE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name TMS_MGR_IMPORT_TR_QUEUE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: TMSM
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM TMS_MGR_IMPORT_TR_QUEUE - TMS MGR IMPORT TR QUEUE





CALL FUNCTION 'TMS_MGR_IMPORT_TR_QUEUE' "
  EXPORTING
    iv_system =                 " tmscsys-sysnam
*   iv_domain =                 " tmscsys-domnam
*   iv_client =                 " stpa-client
*   iv_ctc_active =             " stms_flag
*   iv_overtake =               " stms_flag
*   iv_import_again =           " stms_flag
*   iv_ignore_originality =     " stms_flag
*   iv_ignore_repairs =         " stms_flag
*   iv_ignore_predec =          " stms_flag
*   iv_ignore_cvers =           " stms_flag
*   iv_test_import =            " stms_flag
*   iv_offline = 'X'            " stms_flag
*   iv_monitor = 'X'            " stms_flag
*   iv_verbose =                " stms_flag
*   is_batch =                  " stmscbatch
*   it_projects =               " trprojects
*   it_clients =                " stms_clients
  IMPORTING
    ev_tp_ret_code =            " stpa-retcode
    ev_tp_alog =                " stpa-file
    ev_tp_slog =                " stpa-file
    ev_tp_pid =                 " stpa-pid
    es_exception =              " stmscalert
* TABLES
*   tt_stdout =                 " tpstdout
  EXCEPTIONS
    READ_CONFIG_FAILED = 1      "
    .  "  TMS_MGR_IMPORT_TR_QUEUE

ABAP code example for Function Module TMS_MGR_IMPORT_TR_QUEUE





The ABAP code below is a full code listing to execute function module TMS_MGR_IMPORT_TR_QUEUE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ev_tp_ret_code  TYPE STPA-RETCODE ,
ld_ev_tp_alog  TYPE STPA-FILE ,
ld_ev_tp_slog  TYPE STPA-FILE ,
ld_ev_tp_pid  TYPE STPA-PID ,
ld_es_exception  TYPE STMSCALERT ,
it_tt_stdout  TYPE STANDARD TABLE OF TPSTDOUT,"TABLES PARAM
wa_tt_stdout  LIKE LINE OF it_tt_stdout .


SELECT single SYSNAM
FROM TMSCSYS
INTO @DATA(ld_iv_system).


SELECT single DOMNAM
FROM TMSCSYS
INTO @DATA(ld_iv_domain).


DATA(ld_iv_client) = Check type of data required
DATA(ld_iv_ctc_active) = 'Check type of data required'.
DATA(ld_iv_overtake) = 'Check type of data required'.
DATA(ld_iv_import_again) = 'Check type of data required'.
DATA(ld_iv_ignore_originality) = 'Check type of data required'.
DATA(ld_iv_ignore_repairs) = 'Check type of data required'.
DATA(ld_iv_ignore_predec) = 'Check type of data required'.
DATA(ld_iv_ignore_cvers) = 'Check type of data required'.
DATA(ld_iv_test_import) = 'Check type of data required'.
DATA(ld_iv_offline) = 'Check type of data required'.
DATA(ld_iv_monitor) = 'Check type of data required'.
DATA(ld_iv_verbose) = 'Check type of data required'.
DATA(ld_is_batch) = 'Check type of data required'.
DATA(ld_it_projects) = 'Check type of data required'.
DATA(ld_it_clients) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_tt_stdout to it_tt_stdout. . CALL FUNCTION 'TMS_MGR_IMPORT_TR_QUEUE' EXPORTING iv_system = ld_iv_system * iv_domain = ld_iv_domain * iv_client = ld_iv_client * iv_ctc_active = ld_iv_ctc_active * iv_overtake = ld_iv_overtake * iv_import_again = ld_iv_import_again * iv_ignore_originality = ld_iv_ignore_originality * iv_ignore_repairs = ld_iv_ignore_repairs * iv_ignore_predec = ld_iv_ignore_predec * iv_ignore_cvers = ld_iv_ignore_cvers * iv_test_import = ld_iv_test_import * iv_offline = ld_iv_offline * iv_monitor = ld_iv_monitor * iv_verbose = ld_iv_verbose * is_batch = ld_is_batch * it_projects = ld_it_projects * it_clients = ld_it_clients IMPORTING ev_tp_ret_code = ld_ev_tp_ret_code ev_tp_alog = ld_ev_tp_alog ev_tp_slog = ld_ev_tp_slog ev_tp_pid = ld_ev_tp_pid es_exception = ld_es_exception * TABLES * tt_stdout = it_tt_stdout EXCEPTIONS READ_CONFIG_FAILED = 1 . " TMS_MGR_IMPORT_TR_QUEUE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_ev_tp_ret_code  TYPE STPA-RETCODE ,
ld_iv_system  TYPE TMSCSYS-SYSNAM ,
it_tt_stdout  TYPE STANDARD TABLE OF TPSTDOUT ,
wa_tt_stdout  LIKE LINE OF it_tt_stdout,
ld_ev_tp_alog  TYPE STPA-FILE ,
ld_iv_domain  TYPE TMSCSYS-DOMNAM ,
ld_ev_tp_slog  TYPE STPA-FILE ,
ld_iv_client  TYPE STPA-CLIENT ,
ld_ev_tp_pid  TYPE STPA-PID ,
ld_iv_ctc_active  TYPE STMS_FLAG ,
ld_es_exception  TYPE STMSCALERT ,
ld_iv_overtake  TYPE STMS_FLAG ,
ld_iv_import_again  TYPE STMS_FLAG ,
ld_iv_ignore_originality  TYPE STMS_FLAG ,
ld_iv_ignore_repairs  TYPE STMS_FLAG ,
ld_iv_ignore_predec  TYPE STMS_FLAG ,
ld_iv_ignore_cvers  TYPE STMS_FLAG ,
ld_iv_test_import  TYPE STMS_FLAG ,
ld_iv_offline  TYPE STMS_FLAG ,
ld_iv_monitor  TYPE STMS_FLAG ,
ld_iv_verbose  TYPE STMS_FLAG ,
ld_is_batch  TYPE STMSCBATCH ,
ld_it_projects  TYPE TRPROJECTS ,
ld_it_clients  TYPE STMS_CLIENTS .


SELECT single SYSNAM
FROM TMSCSYS
INTO ld_iv_system.


"populate fields of struture and append to itab
append wa_tt_stdout to it_tt_stdout.

SELECT single DOMNAM
FROM TMSCSYS
INTO ld_iv_domain.


ld_iv_client = Check type of data required
ld_iv_ctc_active = 'Check type of data required'.
ld_iv_overtake = 'Check type of data required'.
ld_iv_import_again = 'Check type of data required'.
ld_iv_ignore_originality = 'Check type of data required'.
ld_iv_ignore_repairs = 'Check type of data required'.
ld_iv_ignore_predec = 'Check type of data required'.
ld_iv_ignore_cvers = 'Check type of data required'.
ld_iv_test_import = 'Check type of data required'.
ld_iv_offline = 'Check type of data required'.
ld_iv_monitor = 'Check type of data required'.
ld_iv_verbose = 'Check type of data required'.
ld_is_batch = 'Check type of data required'.
ld_it_projects = 'Check type of data required'.
ld_it_clients = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name TMS_MGR_IMPORT_TR_QUEUE or its description.