TP_1W_GETTHERE_LIST SAP Function module

TP_1W_GETTHERE_LIST 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 TP_1W_GETTHERE_LIST into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FITP_SABRE_GENERAL
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM TP_1W_GETTHERE_LIST - TP 1W GETTHERE LIST

CALL FUNCTION 'TP_1W_GETTHERE_LIST' "
* EXPORTING
*   context_number = '05'       " ftpt_variant-variant
*   queueing_office =           " office
*   request_date = SY-DATLO     " sy-datlo
*   request_time = SY-TIMLO     " sy-timlo
  IMPORTING
    et_pnr_list =               " ftps_queue_list_t
  EXCEPTIONS
    NO_DESTINATION = 1          "
    CONNECTION_ERROR = 2        "
    INVALID_CONTEXT = 3         "
    .  "  TP_1W_GETTHERE_LIST

ABAP code example for Function Module TP_1W_GETTHERE_LIST

The ABAP code below is a full code listing to execute function module TP_1W_GETTHERE_LIST 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_et_pnr_list  
 
 TYPE FTPS_QUEUE_LIST_T
.

 

SELECT single VARIANT 
  FROM FTPT_VARIANT 
  INTO @DATA(ld_context_number).


DATA(ld_queueing_office) = 'Check type of data required'.

DATA(ld_request_date) = '20210129'.

DATA(ld_request_time) = 'Check type of data required'.
.

CALL FUNCTION 'TP_1W_GETTHERE_LIST'
* EXPORTING
*   context_number =             ld_context_number
*   queueing_office =            ld_queueing_office
*   request_date =               ld_request_date
*   request_time =               ld_request_time
  IMPORTING
    et_pnr_list =                ld_et_pnr_list
  EXCEPTIONS
    NO_DESTINATION =             1
    CONNECTION_ERROR =           2
    INVALID_CONTEXT =            3
    .  "  TP_1W_GETTHERE_LIST

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "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_et_pnr_list
 
 TYPE FTPS_QUEUE_LIST_T ,
ld_context_number
 
 TYPE FTPT_VARIANT-VARIANT ,
ld_queueing_office
 
 TYPE OFFICE ,
ld_request_date
 
 TYPE SY-DATLO ,
ld_request_time
 
 TYPE SY-TIMLO .



SELECT single VARIANT 
  FROM FTPT_VARIANT 
  INTO ld_context_number.

ld_queueing_office = 'Check type of data required'.
ld_request_date = '20210129'.
ld_request_time = 'Check type of data required'.