SAP Function Modules

TP_FLIGHT_AVAILABILITY SAP Function module - Flight Availability







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

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


Pattern for FM TP_FLIGHT_AVAILABILITY - TP FLIGHT AVAILABILITY





CALL FUNCTION 'TP_FLIGHT_AVAILABILITY' "Flight Availability
  EXPORTING
    provider =                  " char3
*   number_of_screens =         " int1
    context_number =            " ftpt_variant-variant
  TABLES
    t_avail_in =                " fitp_flight_avail_in
*   t_avail_for_sell_in =       " fitp_flight_avail_for_sell
*   t_avail_connections_in =    " fitp_flight_avail_connect
    t_avail_out =               " fitp_flight_avail_out  Flight Availability Output
    t_avail_class_out =         " fitp_flight_avail_class_out  Flight class output
  EXCEPTIONS
    NO_FLIGHTS_AVAILABLE = 1    "
    INVALID_CONTEXT = 2         "               Invalid context
    RFC_ERROR = 3               "
    CONNECTION_ERROR = 4        "
    NO_DESTINATION = 5          "
    GENERAL_API_ERROR = 6       "               Unspecified error
    INVALID_SYSTEM = 7          "
    .  "  TP_FLIGHT_AVAILABILITY

ABAP code example for Function Module TP_FLIGHT_AVAILABILITY





The ABAP code below is a full code listing to execute function module TP_FLIGHT_AVAILABILITY 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:
it_t_avail_in  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_IN,"TABLES PARAM
wa_t_avail_in  LIKE LINE OF it_t_avail_in ,
it_t_avail_for_sell_in  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_FOR_SELL,"TABLES PARAM
wa_t_avail_for_sell_in  LIKE LINE OF it_t_avail_for_sell_in ,
it_t_avail_connections_in  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_CONNECT,"TABLES PARAM
wa_t_avail_connections_in  LIKE LINE OF it_t_avail_connections_in ,
it_t_avail_out  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_OUT,"TABLES PARAM
wa_t_avail_out  LIKE LINE OF it_t_avail_out ,
it_t_avail_class_out  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_CLASS_OUT,"TABLES PARAM
wa_t_avail_class_out  LIKE LINE OF it_t_avail_class_out .

DATA(ld_provider) = 'Check type of data required'.
DATA(ld_number_of_screens) = 'Check type of data required'.

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


"populate fields of struture and append to itab
append wa_t_avail_in to it_t_avail_in.

"populate fields of struture and append to itab
append wa_t_avail_for_sell_in to it_t_avail_for_sell_in.

"populate fields of struture and append to itab
append wa_t_avail_connections_in to it_t_avail_connections_in.

"populate fields of struture and append to itab
append wa_t_avail_out to it_t_avail_out.

"populate fields of struture and append to itab
append wa_t_avail_class_out to it_t_avail_class_out. . CALL FUNCTION 'TP_FLIGHT_AVAILABILITY' EXPORTING provider = ld_provider * number_of_screens = ld_number_of_screens context_number = ld_context_number TABLES t_avail_in = it_t_avail_in * t_avail_for_sell_in = it_t_avail_for_sell_in * t_avail_connections_in = it_t_avail_connections_in t_avail_out = it_t_avail_out t_avail_class_out = it_t_avail_class_out EXCEPTIONS NO_FLIGHTS_AVAILABLE = 1 INVALID_CONTEXT = 2 RFC_ERROR = 3 CONNECTION_ERROR = 4 NO_DESTINATION = 5 GENERAL_API_ERROR = 6 INVALID_SYSTEM = 7 . " TP_FLIGHT_AVAILABILITY
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 ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 7. "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_provider  TYPE CHAR3 ,
it_t_avail_in  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_IN ,
wa_t_avail_in  LIKE LINE OF it_t_avail_in,
ld_number_of_screens  TYPE INT1 ,
it_t_avail_for_sell_in  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_FOR_SELL ,
wa_t_avail_for_sell_in  LIKE LINE OF it_t_avail_for_sell_in,
ld_context_number  TYPE FTPT_VARIANT-VARIANT ,
it_t_avail_connections_in  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_CONNECT ,
wa_t_avail_connections_in  LIKE LINE OF it_t_avail_connections_in,
it_t_avail_out  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_OUT ,
wa_t_avail_out  LIKE LINE OF it_t_avail_out,
it_t_avail_class_out  TYPE STANDARD TABLE OF FITP_FLIGHT_AVAIL_CLASS_OUT ,
wa_t_avail_class_out  LIKE LINE OF it_t_avail_class_out.

ld_provider = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_t_avail_in to it_t_avail_in.
ld_number_of_screens = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_t_avail_for_sell_in to it_t_avail_for_sell_in.

SELECT single VARIANT
FROM FTPT_VARIANT
INTO ld_context_number.


"populate fields of struture and append to itab
append wa_t_avail_connections_in to it_t_avail_connections_in.

"populate fields of struture and append to itab
append wa_t_avail_out to it_t_avail_out.

"populate fields of struture and append to itab
append wa_t_avail_class_out to it_t_avail_class_out.

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 TP_FLIGHT_AVAILABILITY or its description.