FITP_UTIL_FLIGHT_CANCEL SAP Function module

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

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

Pattern for FM FITP_UTIL_FLIGHT_CANCEL - FITP UTIL FLIGHT CANCEL

CALL FUNCTION 'FITP_UTIL_FLIGHT_CANCEL' "
* EXPORTING
*   it_flights_to_cancel =      " ftps_web_flight_input_t
  IMPORTING
    et_return =                 " bapirettab    Table with BAPI Return Information
  EXCEPTIONS
    CANCELLATION_FAILED = 1     "
    NO_ENTRY_IN_TABLE = 2       "
    GENERAL_API_ERROR = 3       "
    SEGMENT_CELL_UNSTABLE = 4   "
    CONNECTION_ERROR = 5        "
    NO_DESTINATION = 6          "
    NO_VALID_VARIANT = 7        "
    SYNCHRO_ERROR = 8           "
    NO_VARIANT_CONNECTED = 9    "
    NO_VALID_RES_SYSTEM = 10    "
    DISCONNECTION_ERROR = 11    "
    NO_DESTINATION_FOUND = 12   "
    INVALID_CONTEXT = 13        "
    RFC_ERROR = 14              "
    INVALID_SYSTEM = 15         "
    .  "  FITP_UTIL_FLIGHT_CANCEL

ABAP code example for Function Module FITP_UTIL_FLIGHT_CANCEL

The ABAP code below is a full code listing to execute function module FITP_UTIL_FLIGHT_CANCEL 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_return  
 
 TYPE BAPIRETTAB
.


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

CALL FUNCTION 'FITP_UTIL_FLIGHT_CANCEL'
* EXPORTING
*   it_flights_to_cancel =       ld_it_flights_to_cancel
  IMPORTING
    et_return =                  ld_et_return
  EXCEPTIONS
    CANCELLATION_FAILED =        1
    NO_ENTRY_IN_TABLE =          2
    GENERAL_API_ERROR =          3
    SEGMENT_CELL_UNSTABLE =      4
    CONNECTION_ERROR =           5
    NO_DESTINATION =             6
    NO_VALID_VARIANT =           7
    SYNCHRO_ERROR =              8
    NO_VARIANT_CONNECTED =       9
    NO_VALID_RES_SYSTEM =        10
    DISCONNECTION_ERROR =        11
    NO_DESTINATION_FOUND =       12
    INVALID_CONTEXT =            13
    RFC_ERROR =                  14
    INVALID_SYSTEM =             15
    .  "  FITP_UTIL_FLIGHT_CANCEL

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
ELSEIF SY-SUBRC EQ 8. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 9. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 10. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 11. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 12. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 13. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 14. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 15. "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_return
 
 TYPE BAPIRETTAB ,
ld_it_flights_to_cancel
 
 TYPE FTPS_WEB_FLIGHT_INPUT_T .


ld_it_flights_to_cancel = 'Check type of data required'.