HiltonXML

Hilton is an online hotel supplier with over 540 hotels in 78 locations around the world.

Prerequisites

Before setting up the Hilton interface in the system, Hilton needs to provide you with:

• Requester ID

• User name

• Password

• Customer ID

• Credit Card OTA code

Setting Up the Hilton Interface

1. Go to Setup – Business Environment - Supplier Accounts.

2. Create a supplier account for Hilton.

   The account currency should be USD.

3. In the Services expander of the supplier account, define hotel as a service.

4. The Income Type should be Comm VAT Exempt, and the amount is determined according to your commercial agreement with Hilton.

5. Open the Online Supplier expander of the supplier account.

6. In the CRS Interface field, select HiltonXML from the drop-down list.

7. Select the Active check box.

8. Click the link in the text: Click Here to update interface properties.

   The configuration dialog box for Hilton is displayed:

   

9. Enter the configuration details:

   1. In the Requestor ID field, enter the Requestor ID supplied to you by Hilton.

   2. In the User Name field, enter the user name supplied to you by Hilton.

   3. In the Password field, enter the password supplied to you by Hilton.

   4. In the Customer ID field, enter the customer ID supplied to you by Hilton.

   5. In the Server field, enter the following URL:

      https://hte.hilton.com:11201/ota/OTA.pl

   6. In the Images URL field, enter the URL where the interface images are located.

   7. In the Default phone number field, enter your business' phone number.

   8. In the Credit Card OTA code field, enter the credit card OTA code supplied to you by Hilton.

   9. In the Remark field, enter a remark defined to you by Hilton.

   10. Hilton's policy is to add VAT in every country. In some countries tourists are exempt from VAT taxes. If your company sells hotels in such country, select Reduced VAT from price.

   11. In Hotel Extended Details Source, select Local.

   12. TBA Users only. Select Debug Flag to create XML files on the server.

   13. Click Save.

10. Click Match Destinations.

Click here for more information on the Match Destinations process . This process can take several minutes to complete. The Match Destinations process works as follows: The process runs on all the destinations returned from the interface and saved in the system. When matching destinations: The following characters are ignored: dash (-), and apostrophe ('). For example, if HiltonXML returns New-York and the destination saved in the system is New York, the process will ignore the dash and match the destinations. And vice-versus if the destination returned is New-York and the destination saved in the system is New York. The following words are ignored: island, isle, isla, district, prefecture, and area. The process is not case sensitive. For example if the interface returns Manhattan Island, and the destination saved in the system is Manhattan, the process will ignore the word Island and match the destinations. The process converts the words St and Sankt to Saint. For example, if  HiltonXML returns St. Joseph and the destination saved in the system is Saint Joseph, the process confirms St to Saint and match the destinations.

A table is displayed, presenting the destination values in the local database with those in the supplier’s database.



A supplier destination value with a corresponding identical local destination value is automatically matched and the two values appear on the same row in the table. Rows with unmatched values appear at the beginning of the table, followed by the matched values.

11. Map the unmatched supplier destination values.

    • To map automatically: Click by the supplier destination value to automatically add the supplier destination value to the local database and map the supplier value to the local value.

    • Use this action with caution as this action copies the supplier's destination value to your database and in some cases may result in duplicate values. For example: If your local database includes the value London and the supplier's database includes London, UK Then, the action copies London, UK to your database, after which both London and London, UK will be included in your database. It is recommended to consult your Account Manager prior to mapping the supplier destination values.

    • To map manually:

    • 1. Click by the supplier destination value.

         A drop-down list of local database destinations is displayed.

      2. Select the relevant local database entry to match the supplier value.

      3. Click to save the entry or to revert

    • To map the supplier destination to more than one value in the local database:

    • 1. Click  and select Multiple Mapping.

         A multi-selection list which includes all the local destination values is displayed.

      2. Click the destination values in the Not Selected list to map to the supplier destination value.

         These values are displayed in the Selected list.

      3. To save the mapping, click Save.

12. After completing the mapping process, click Hilton.

13. Click Save on the main page.

Special Notes

1. The Hilton interface does not include descriptions or images, only prices and availability. To add images and descriptions, you need to manually configure an online hotel display rule for each hotel.

2. The interface only displays hotels that are available.

3. You can only reserve one room at a time. This is a Hilton limitation.

4. An additional passenger cannot be added to the same travel file. You need to open a new travel file for that passenger.

5. Hilton does not distinguish between countries - only regions. Therefore, when there are Hilton hotels near the region where you are selling, but in different countries, use the unpublish option in the online hotel display rules.

6. When adding or deleting a remark to an online transaction, a new reservation record with the same details is created, the remark is added or deleted, and the old transaction is cancelled.