SAP Function Modules

TP_1A_CAR_AVAILABILITY SAP Function module







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

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


Pattern for FM TP_1A_CAR_AVAILABILITY - TP 1A CAR AVAILABILITY





CALL FUNCTION 'TP_1A_CAR_AVAILABILITY' "
  EXPORTING
    context_number =            " ftpt_variant-variant  Context
    input_parameter =           " ftps_car_avail_in
  IMPORTING
    car_avail_out =             " ftps_car_avail_info_out  Rental Car Availability: Output
  TABLES
*   t_car_option_in =           " rsds_frange_t
    t_car_provider_out =        " ftps_car_avail_provider_out  Rental car vendor output
    t_car_out =                 " ftps_car_avail_out  Rental car price list
  EXCEPTIONS
    INVALID_CONTEXT = 1         "
    NO_CARS_AVAILABLE = 2       "
    RFC_ERROR = 3               "               RFC Error
    CONNECTION_ERROR = 4        "               Error when setting up connection
    NO_DESTINATION = 5          "
    UNEXPECTED_RESPONSE = 6     "
    PARAMETER_ERROR = 7         "               Errors in passing parameters
    INVALID_DATE_TIME = 8       "
    INVALID_PROVIDER_OR_CAR = 9  "
    INVALID_LOCATION = 10       "
    RATE_NOT_AVAILABLE = 11     "
    GENERAL_API_ERROR = 12      "               General API error
    .  "  TP_1A_CAR_AVAILABILITY

ABAP code example for Function Module TP_1A_CAR_AVAILABILITY





The ABAP code below is a full code listing to execute function module TP_1A_CAR_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:
ld_car_avail_out  TYPE FTPS_CAR_AVAIL_INFO_OUT ,
it_t_car_option_in  TYPE STANDARD TABLE OF RSDS_FRANGE_T,"TABLES PARAM
wa_t_car_option_in  LIKE LINE OF it_t_car_option_in ,
it_t_car_provider_out  TYPE STANDARD TABLE OF FTPS_CAR_AVAIL_PROVIDER_OUT,"TABLES PARAM
wa_t_car_provider_out  LIKE LINE OF it_t_car_provider_out ,
it_t_car_out  TYPE STANDARD TABLE OF FTPS_CAR_AVAIL_OUT,"TABLES PARAM
wa_t_car_out  LIKE LINE OF it_t_car_out .


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

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

"populate fields of struture and append to itab
append wa_t_car_option_in to it_t_car_option_in.

"populate fields of struture and append to itab
append wa_t_car_provider_out to it_t_car_provider_out.

"populate fields of struture and append to itab
append wa_t_car_out to it_t_car_out. . CALL FUNCTION 'TP_1A_CAR_AVAILABILITY' EXPORTING context_number = ld_context_number input_parameter = ld_input_parameter IMPORTING car_avail_out = ld_car_avail_out TABLES * t_car_option_in = it_t_car_option_in t_car_provider_out = it_t_car_provider_out t_car_out = it_t_car_out EXCEPTIONS INVALID_CONTEXT = 1 NO_CARS_AVAILABLE = 2 RFC_ERROR = 3 CONNECTION_ERROR = 4 NO_DESTINATION = 5 UNEXPECTED_RESPONSE = 6 PARAMETER_ERROR = 7 INVALID_DATE_TIME = 8 INVALID_PROVIDER_OR_CAR = 9 INVALID_LOCATION = 10 RATE_NOT_AVAILABLE = 11 GENERAL_API_ERROR = 12 . " TP_1A_CAR_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 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 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_car_avail_out  TYPE FTPS_CAR_AVAIL_INFO_OUT ,
ld_context_number  TYPE FTPT_VARIANT-VARIANT ,
it_t_car_option_in  TYPE STANDARD TABLE OF RSDS_FRANGE_T ,
wa_t_car_option_in  LIKE LINE OF it_t_car_option_in,
ld_input_parameter  TYPE FTPS_CAR_AVAIL_IN ,
it_t_car_provider_out  TYPE STANDARD TABLE OF FTPS_CAR_AVAIL_PROVIDER_OUT ,
wa_t_car_provider_out  LIKE LINE OF it_t_car_provider_out,
it_t_car_out  TYPE STANDARD TABLE OF FTPS_CAR_AVAIL_OUT ,
wa_t_car_out  LIKE LINE OF it_t_car_out.


SELECT single VARIANT
FROM FTPT_VARIANT
INTO ld_context_number.


"populate fields of struture and append to itab
append wa_t_car_option_in to it_t_car_option_in.
ld_input_parameter = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_t_car_provider_out to it_t_car_provider_out.

"populate fields of struture and append to itab
append wa_t_car_out to it_t_car_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_1A_CAR_AVAILABILITY or its description.