SAP FITP_DISPLAY_CAR_DETAILS Function Module for
FITP_DISPLAY_CAR_DETAILS is a standard fitp display car details SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for fitp display car details FM, simply by entering the name FITP_DISPLAY_CAR_DETAILS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FITP_CAR
Program Name: SAPLFITP_CAR
Main Program: SAPLFITP_CAR
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FITP_DISPLAY_CAR_DETAILS pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'FITP_DISPLAY_CAR_DETAILS'".
EXPORTING
PROVIDER = "Reservation System
VARIANT = "Travel Plan Variant
* WA_CAR = "Car Rental Request
EXCEPTIONS
NO_CAR_RULE_AVAILABLE = 1 INVALID_SYSTEM = 10 NO_CAR_RULE_DISPLAYABLE = 2 RFC_ERROR = 3 CONNECTION_ERROR = 4 NO_DESTINATION = 5 PARAMETER_ERROR = 6 INVALID_VARIANT = 7 INVALID_CALL = 8 GENERAL_API_ERROR = 9
IMPORTING Parameters details for FITP_DISPLAY_CAR_DETAILS
PROVIDER - Reservation System
Data type: TA21P-PROVIDEROptional: No
Call by Reference: No ( called with pass by value option)
VARIANT - Travel Plan Variant
Data type: FTPT_VARIANT-VARIANTOptional: No
Call by Reference: No ( called with pass by value option)
WA_CAR - Car Rental Request
Data type: TRPL_CAR_LISTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_CAR_RULE_AVAILABLE - No rate data available
Data type:Optional: No
Call by Reference: Yes
INVALID_SYSTEM -
Data type:Optional: No
Call by Reference: Yes
NO_CAR_RULE_DISPLAYABLE - No rate data displayable
Data type:Optional: No
Call by Reference: Yes
RFC_ERROR - RFC error
Data type:Optional: No
Call by Reference: Yes
CONNECTION_ERROR - Connection error
Data type:Optional: No
Call by Reference: Yes
NO_DESTINATION - No RFC destination exists
Data type:Optional: No
Call by Reference: Yes
PARAMETER_ERROR - Errors in passing parameters
Data type:Optional: No
Call by Reference: Yes
INVALID_VARIANT - Invalid travel plan variant
Data type:Optional: No
Call by Reference: Yes
INVALID_CALL - Invalid call of API module
Data type:Optional: No
Call by Reference: Yes
GENERAL_API_ERROR - General API error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FITP_DISPLAY_CAR_DETAILS Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_provider | TYPE TA21P-PROVIDER, " | |||
| lv_no_car_rule_available | TYPE TA21P, " | |||
| lv_invalid_system | TYPE TA21P, " | |||
| lv_variant | TYPE FTPT_VARIANT-VARIANT, " | |||
| lv_no_car_rule_displayable | TYPE FTPT_VARIANT, " | |||
| lv_wa_car | TYPE TRPL_CAR_LIST, " | |||
| lv_rfc_error | TYPE TRPL_CAR_LIST, " | |||
| lv_connection_error | TYPE TRPL_CAR_LIST, " | |||
| lv_no_destination | TYPE TRPL_CAR_LIST, " | |||
| lv_parameter_error | TYPE TRPL_CAR_LIST, " | |||
| lv_invalid_variant | TYPE TRPL_CAR_LIST, " | |||
| lv_invalid_call | TYPE TRPL_CAR_LIST, " | |||
| lv_general_api_error | TYPE TRPL_CAR_LIST. " |
|   CALL FUNCTION 'FITP_DISPLAY_CAR_DETAILS' " |
| EXPORTING | ||
| PROVIDER | = lv_provider | |
| VARIANT | = lv_variant | |
| WA_CAR | = lv_wa_car | |
| EXCEPTIONS | ||
| NO_CAR_RULE_AVAILABLE = 1 | ||
| INVALID_SYSTEM = 10 | ||
| NO_CAR_RULE_DISPLAYABLE = 2 | ||
| RFC_ERROR = 3 | ||
| CONNECTION_ERROR = 4 | ||
| NO_DESTINATION = 5 | ||
| PARAMETER_ERROR = 6 | ||
| INVALID_VARIANT = 7 | ||
| INVALID_CALL = 8 | ||
| GENERAL_API_ERROR = 9 | ||
| . " FITP_DISPLAY_CAR_DETAILS | ||
ABAP code using 7.40 inline data declarations to call FM FITP_DISPLAY_CAR_DETAILS
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single PROVIDER FROM TA21P INTO @DATA(ld_provider). | ||||
| "SELECT single VARIANT FROM FTPT_VARIANT INTO @DATA(ld_variant). | ||||
Search for further information about these or an SAP related objects