TP_1W_GETTHERE_OPEN_TRIP SAP Function module

TP_1W_GETTHERE_OPEN_TRIP 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_OPEN_TRIP 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_OPEN_TRIP - TP 1W GETTHERE OPEN TRIP

CALL FUNCTION 'TP_1W_GETTHERE_OPEN_TRIP' "
* EXPORTING
*   context_number = '05'       " variant_nr    Plan Variant Number (Sequential Number)
*   pnr_locator =               " pnr_record_locator  Passenger Name Record Locator
  IMPORTING
    vp_return =                 " i
    et_return =                 " bapirettab    Table with BAPI Return Information
    e_generic_pnr =             " ftps_pnr      Generic PNR (Passenger Name Record)
  EXCEPTIONS
    PNR_RETRIEVAL_ERROR = 1     "
    NO_DESTINATION = 2          "
    INVALID_VARIANT = 3         "
    CONNECTION_ERROR = 4        "
    .  "  TP_1W_GETTHERE_OPEN_TRIP

ABAP code example for Function Module TP_1W_GETTHERE_OPEN_TRIP

The ABAP code below is a full code listing to execute function module TP_1W_GETTHERE_OPEN_TRIP 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_vp_return  
 
 TYPE I
,
ld_et_return  
 
 TYPE BAPIRETTAB
,
ld_e_generic_pnr  
 
 TYPE FTPS_PNR
.


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

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

CALL FUNCTION 'TP_1W_GETTHERE_OPEN_TRIP'
* EXPORTING
*   context_number =             ld_context_number
*   pnr_locator =                ld_pnr_locator
  IMPORTING
    vp_return =                  ld_vp_return
    et_return =                  ld_et_return
    e_generic_pnr =              ld_e_generic_pnr
  EXCEPTIONS
    PNR_RETRIEVAL_ERROR =        1
    NO_DESTINATION =             2
    INVALID_VARIANT =            3
    CONNECTION_ERROR =           4
    .  "  TP_1W_GETTHERE_OPEN_TRIP

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
ELSEIF SY-SUBRC EQ 4. "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_vp_return
 
 TYPE I ,
ld_context_number
 
 TYPE VARIANT_NR ,
ld_et_return
 
 TYPE BAPIRETTAB ,
ld_pnr_locator
 
 TYPE PNR_RECORD_LOCATOR ,
ld_e_generic_pnr
 
 TYPE FTPS_PNR .


ld_context_number = 'Check type of data required'.
ld_pnr_locator = 'Check type of data required'.