SAP TMW_GET_OPEN_TRANSPORTS Function Module for









TMW_GET_OPEN_TRANSPORTS is a standard tmw get open transports 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 get open transports FM, simply by entering the name TMW_GET_OPEN_TRANSPORTS into the relevant SAP transaction such as SE37 or SE38.

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



Function TMW_GET_OPEN_TRANSPORTS 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_GET_OPEN_TRANSPORTS'"
  EXPORTING
*  IV_ALL_PROJECTS = 'T' "
*  IV_CLIENT =  "
*  IV_PROJECT =  "
*  IV_FROM_DATE =  "
*  IV_FROM_TIME =  "
*  IV_TO_DATE =  "
*  IV_TO_TIME =  "
*  IV_TIMEZONE_GET = ' ' "

 IMPORTING
   EV_COUNT =  "
   EV_TZONE =  "
   EV_TIMEZONE =  "

TABLES
   ET_TRLIST =  "
.



IMPORTING Parameters details for TMW_GET_OPEN_TRANSPORTS

IV_ALL_PROJECTS -

Data type: CHAR1
Default: 'T'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CLIENT -

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

IV_PROJECT -

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

IV_FROM_DATE -

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

IV_FROM_TIME -

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

IV_TO_DATE -

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

IV_TO_TIME -

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

IV_TIMEZONE_GET -

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

EXPORTING Parameters details for TMW_GET_OPEN_TRANSPORTS

EV_COUNT -

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

EV_TZONE -

Data type: SY-TZONE
Optional: No
Call by Reference: No ( called with pass by value option)

EV_TIMEZONE -

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

TABLES Parameters details for TMW_GET_OPEN_TRANSPORTS

ET_TRLIST -

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

Copy and paste ABAP code example for TMW_GET_OPEN_TRANSPORTS 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_ev_count  TYPE I, "   
lt_et_trlist  TYPE STANDARD TABLE OF TMW_TRACKLIST, "   
lv_iv_all_projects  TYPE CHAR1, "   'T'
lv_ev_tzone  TYPE SY-TZONE, "   
lv_iv_client  TYPE SY-MANDT, "   
lv_iv_project  TYPE TMW_TRACKLIST-PROJECT, "   
lv_ev_timezone  TYPE TIMEZONE, "   
lv_iv_from_date  TYPE TMW_TRACKLIST-A_DATE, "   
lv_iv_from_time  TYPE TMW_TRACKLIST-A_TIME, "   
lv_iv_to_date  TYPE TMW_TRACKLIST-A_DATE, "   
lv_iv_to_time  TYPE TMW_TRACKLIST-A_TIME, "   
lv_iv_timezone_get  TYPE FLAG. "   ' '

  CALL FUNCTION 'TMW_GET_OPEN_TRANSPORTS'  "
    EXPORTING
         IV_ALL_PROJECTS = lv_iv_all_projects
         IV_CLIENT = lv_iv_client
         IV_PROJECT = lv_iv_project
         IV_FROM_DATE = lv_iv_from_date
         IV_FROM_TIME = lv_iv_from_time
         IV_TO_DATE = lv_iv_to_date
         IV_TO_TIME = lv_iv_to_time
         IV_TIMEZONE_GET = lv_iv_timezone_get
    IMPORTING
         EV_COUNT = lv_ev_count
         EV_TZONE = lv_ev_tzone
         EV_TIMEZONE = lv_ev_timezone
    TABLES
         ET_TRLIST = lt_et_trlist
. " TMW_GET_OPEN_TRANSPORTS




ABAP code using 7.40 inline data declarations to call FM TMW_GET_OPEN_TRANSPORTS

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_all_projects) = 'T'.
 
"SELECT single TZONE FROM SY INTO @DATA(ld_ev_tzone).
 
"SELECT single MANDT FROM SY INTO @DATA(ld_iv_client).
 
"SELECT single PROJECT FROM TMW_TRACKLIST INTO @DATA(ld_iv_project).
 
 
"SELECT single A_DATE FROM TMW_TRACKLIST INTO @DATA(ld_iv_from_date).
 
"SELECT single A_TIME FROM TMW_TRACKLIST INTO @DATA(ld_iv_from_time).
 
"SELECT single A_DATE FROM TMW_TRACKLIST INTO @DATA(ld_iv_to_date).
 
"SELECT single A_TIME FROM TMW_TRACKLIST INTO @DATA(ld_iv_to_time).
 
DATA(ld_iv_timezone_get) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!