SAP FITP_WEB_HOTEL_GETDETAILS Function Module for
FITP_WEB_HOTEL_GETDETAILS is a standard fitp web hotel getdetails 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 web hotel getdetails FM, simply by entering the name FITP_WEB_HOTEL_GETDETAILS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FITP_WEB_HOTEL
Program Name: SAPLFITP_WEB_HOTEL
Main Program: SAPLFITP_WEB_HOTEL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FITP_WEB_HOTEL_GETDETAILS 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_WEB_HOTEL_GETDETAILS'".
EXPORTING
I_HOTEL_CHAIN = "Hotel Chain
I_IATA_LOCATION = "Hotel Location
I_HOTEL_PROPERTY = "Hotel Code (Key for an Individual Hotel)
I_DATE_ARRIVAL = "
I_DATE_DEPARTURE = "Departure Date Hotel
I_HOTEL_CATALOGUE_ID = "Hotel Catalog Item (enterprise-specific)
IMPORTING
E_INFO_URL = "URL (Uniform Resource Locator) of Information Source
TABLES
ET_HOTEL_INFO_LIST = "Hotel Information
ET_RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for FITP_WEB_HOTEL_GETDETAILS
I_HOTEL_CHAIN - Hotel Chain
Data type: HOTEL_PROVIDEROptional: No
Call by Reference: No ( called with pass by value option)
I_IATA_LOCATION - Hotel Location
Data type: HOTEL_SLOCATIONOptional: No
Call by Reference: No ( called with pass by value option)
I_HOTEL_PROPERTY - Hotel Code (Key for an Individual Hotel)
Data type: HOTEL_PROPERTYOptional: No
Call by Reference: No ( called with pass by value option)
I_DATE_ARRIVAL -
Data type: HOTEL_DATE_ARROptional: No
Call by Reference: No ( called with pass by value option)
I_DATE_DEPARTURE - Departure Date Hotel
Data type: HOTEL_DATE_DEPOptional: No
Call by Reference: No ( called with pass by value option)
I_HOTEL_CATALOGUE_ID - Hotel Catalog Item (enterprise-specific)
Data type: HOTEL_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FITP_WEB_HOTEL_GETDETAILS
E_INFO_URL - URL (Uniform Resource Locator) of Information Source
Data type: INFO_URLOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FITP_WEB_HOTEL_GETDETAILS
ET_HOTEL_INFO_LIST - Hotel Information
Data type: FTPS_WEB_HOTEL_INFO_OUTPUT_TOptional: No
Call by Reference: Yes
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FITP_WEB_HOTEL_GETDETAILS 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_e_info_url | TYPE INFO_URL, " | |||
| lv_i_hotel_chain | TYPE HOTEL_PROVIDER, " | |||
| lt_et_hotel_info_list | TYPE STANDARD TABLE OF FTPS_WEB_HOTEL_INFO_OUTPUT_T, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_i_iata_location | TYPE HOTEL_SLOCATION, " | |||
| lv_i_hotel_property | TYPE HOTEL_PROPERTY, " | |||
| lv_i_date_arrival | TYPE HOTEL_DATE_ARR, " | |||
| lv_i_date_departure | TYPE HOTEL_DATE_DEP, " | |||
| lv_i_hotel_catalogue_id | TYPE HOTEL_ID. " |
|   CALL FUNCTION 'FITP_WEB_HOTEL_GETDETAILS' " |
| EXPORTING | ||
| I_HOTEL_CHAIN | = lv_i_hotel_chain | |
| I_IATA_LOCATION | = lv_i_iata_location | |
| I_HOTEL_PROPERTY | = lv_i_hotel_property | |
| I_DATE_ARRIVAL | = lv_i_date_arrival | |
| I_DATE_DEPARTURE | = lv_i_date_departure | |
| I_HOTEL_CATALOGUE_ID | = lv_i_hotel_catalogue_id | |
| IMPORTING | ||
| E_INFO_URL | = lv_e_info_url | |
| TABLES | ||
| ET_HOTEL_INFO_LIST | = lt_et_hotel_info_list | |
| ET_RETURN | = lt_et_return | |
| . " FITP_WEB_HOTEL_GETDETAILS | ||
ABAP code using 7.40 inline data declarations to call FM FITP_WEB_HOTEL_GETDETAILS
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.Search for further information about these or an SAP related objects