Travel Analytics Update - Wednesday, 4 September 2019

Travel Analytics Update

Wednesday, 4 September 2019

In this update:

  • Reference data mapping
  • Lost savings update
  • Delete (deactivate) line items within Travel Analytics
  • Duplicate hotel data updates
  • Table sort bug fixes
  • Subscription dashboards

Reference Data Mapping

Administrators can now map Tramada reference data so it appears in Travel Analytics report downloads.  We automatically import and display matter number, order number, the reason for travel code and reason for travel description for Raw Data and Yellowfin importers.  If you use the reference fields in either Raw Data or Yellowfin you will need to map them to display the data in the reports.

To get started, click on the Admin Menu > Settings.  In the settings table, click on the References tab and select the data source.  There are two options for the data source.  The first option is RAW DATA, which is the original Tramada / Travel Analytics importer and the second option is Yellowfin, which is the new daily importer.

Raw data supports references 1 to 5 and Yellowfin supports references 1 to 15.  You will need to map both data sources if you import data using both importers.

To map the references, select the customer from the table and click ‘add’.  In the pop-up, select the reference field you wish to map.  You now have the option to override an existing data field (i.e. cost centre) or rename the field so it can be displayed in the customer's reports (i.e. approver, employee number, travel fund, travel booker etc.).

Override Existing Data Field

This should only be used if you want to update an existing data field within Travel Analytics.  When you set this option, the data will only be overridden from the next import (i.e. next day) and not the historical data.  If you need the historical data updated, there will be a $250 charge to do this, as we need to manually reimport the customer's data.

Rename Data Field

When you select the Reference Field, simply type in the field name you want to appear in the download reports by entering the name in the Overriding Field / Rename text box.  For example, if Reference 2 in your Tramada data is the name of the person who approved the travel, simply enter Travel Approver in the text box (as shown below).  Add additional references by clicking on the + button.

Once you have mapped all the references, click OK and the application will be updated.

Lost Savings Update

We have made several changes to how lost savings are calculated and displayed in Travel Analytics.  First up, we have updated the importers to calculate a zero lost saving when we import data where the travel policy is any of the following: Lowest Fare, %Cheapest Fare Accepted (% is a wildcard), Cheapest Avail Fare Selected, Company Policy, Cheapest Available, Complies With Policy, Accepted Lowest Possible Fare, In Policy, Best Fare Selected, Best Fare of the Day, Best Fare of the Day Accepted, Best Airfare for this Itinerary, Best Fare in Policy Chosen, Cheapest Fare with Baggage Accepted, Cheapest Option Accepted, Lowest Fare Accepted, Lowest Practical Airfare Selected, Within Company Policy and Within Policy.  This is the same logic we used in Mark I. 

Where the non-compliant policy code is selected (i.e. Flexible Fare Required, Specific Routing Required, Preferred Airline etc.), we determine the lost saving by calculating the difference between the best fare (excluding gst) and the supplier amount (excluding gst).  The difference is the amount we display in the dashboards and download reports as a Lost Saving.

Lost Saving Data within the Dashboards

We have replaced best fare data with Lost Savings in all tables and download reports, including Travel Policy Compliance Data (table), Traveller Spend Data table (top 10 traveller click event), Travel Expenditure Data tables (Traveller dashboard) and booking drill-down data, and excel raw data reports.  Here are a few examples:

Travel Expenditure Data (Traveller Dashboard drill-down)

Traveller Spend Data (Top 10 Traveller data with the filter on lost saving)

Travel Policy Compliance Data (Flexibility required drill-down)

Delete Booking Line Items

Administrators now can now delete booking line items that you want to remove from the data (i.e. duplicate line items or incorrect costings etc.). 

To do this, navigate to data editing > bookings.  Enter the booking reference in the search box and click select.

In the table (above), click edit and deselect the Is Active checkbox to deactivate the line item in the booking (see below).

Click OK and the table will update showing the deactivated line item.

Duplicate Hotel / Car Hire Data

We have updated the importers to remove duplicate costings where an additional line item is created for a chargeback.  Here is a before and after screenshot so you can see how the update removes the duplicate data.

Before Duplicates Removed

After Duplicates Removed

Table Sorting Bug Fix

A fix has been applied to allow data to be sorted in the tables based on date and highest to lowest (and vice versa).

Subscription Modules

We will be releasing the first of our subscription modules later this month.  Traveller Tracking, Forward Bookings and Budget Manager will all be available for your customers through a subscription service.  These modules have been tested by a selected number of customers and the feedback we received has been fantastic, and we are really looking forward to rolling it out to your customers.  Further details will be released next week.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.