SAP TMW_TU_TRACK_IMPORT Function Module for

Search SAP Function Modules

TMW_TU_TRACK_IMPORT is a standard tmw tu track import 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 tmw tu track import FM, simply by entering the name TMW_TU_TRACK_IMPORT into the relevant SAP transaction such as SE37 or SE38.

Function Group: TMW_CLIENT_INTERFACES
Program Name: SAPLTMW_CLIENT_INTERFACES
Main Program: SAPLTMW_CLIENT_INTERFACES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function TMW_TU_TRACK_IMPORT 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 'TMW_TU_TRACK_IMPORT'"
  EXPORTING
*  IV_SYSTEM =  "
*  IV_POPUP =  "
*  IV_MONITOR =  "
*  IV_VERBOSE =  "
   IV_FUNC_NAME =  "
*  IV_TARCLI =  "
*  IV_SYSLIST =  "
*  IV_JOBID =  "
*  IV_TPSTATID =  "
*  IV_START_DATE =  "
*  IV_START_TIME =  "
*  IV_END_DATE =  "
*  IV_END_TIME =  "
*  IV_IMPORTS =  "
*  IV_EXPORTS =  "
*  IV_ALL_ALOG_STEPS =  "
*  IV_TPSTAT_KEY =  "

EXCEPTIONS
   CANCELLED_BY_USER = 1    IMPORT_HISTORY_FAILED = 2    READ_CONFIGURATION_ERROR = 3 

.

IMPORTING Parameters details for TMW_TU_TRACK_IMPORT

IV_SYSTEM -

Data type: TMSSYSNAM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_POPUP -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_MONITOR -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_VERBOSE -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_FUNC_NAME -

Data type: RS38L_FNAM
Optional: No
Call by Reference: No ( called with pass by value option)

IV_TARCLI -

Data type: TRTARCLI
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SYSLIST -

Data type: TMSFSYSL-LISTNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_JOBID -

Data type: CIBJOBNUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TPSTATID -

Data type: TRTPTSTAMP
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_START_DATE -

Data type: DATS
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_START_TIME -

Data type: TIMS
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_END_DATE -

Data type: DATS
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_END_TIME -

Data type: TIMS
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_IMPORTS -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_EXPORTS -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_ALL_ALOG_STEPS -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TPSTAT_KEY -

Data type: TMSTPKEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CANCELLED_BY_USER -

Data type:
Optional: No
Call by Reference: Yes

IMPORT_HISTORY_FAILED -

Data type:
Optional: No
Call by Reference: Yes

READ_CONFIGURATION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TMW_TU_TRACK_IMPORT 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.

ABAP code using 7.40 inline data declarations to call FM TMW_TU_TRACK_IMPORT

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.

Search for further information about these or an SAP related objects