Introducing the Travel Configuration Page

Introducing the Agency Information

Objective

After completing this lesson, you will be able to define Agency Information Options on the Travel Configuration Page.

Introduction to Agency Information

On the Company Travel Configuration page, you’ll find the section for Agency Information at the top of the page just below the Configuration and Billing Tier fields. If you’re within another section of the company travel configuration, you can use the scroll bar or the back to top link to easily get back to the top of the page to access the Agency Information.

Screenshot shows the “Company Travel Configuration” page for “Northerly Accounting Inc. – CLIQCID-311298 – CLIQCONFIG-250018739.” The highlighted area at the top of the page shows an Agency Information section with fields for Agency Booking Config, BAR (Accounting Name), Accounting Code, Profile Template File, Travel Agency Ticketing Currency, Hotel Override IATA, and Car Override IATA.

The fields included in the Agency Information section are useful for ensuring accurate setup and management of travel configurations within SAP Concur. To learn more about the fields in the Agency Information section, review the following labeled graphic and corresponding table.

Screenshot shows the Agency Information section from a Company Travel Configuration page with numbered callouts 1–7. Field 1 is Agency Booking Config showing “NA Travel Partner Agency 15 Ap…”. Field 2 is BAR (Accounting Name) populated with “CONCURTECH”. Field 3 is Accounting Code (leave blank for Worldspan) and it is empty. Field 4 is Profile Template File, a dropdown set to “Default Apollo Template.xml”. Field 5 is Travel Agency Ticketing Currency, a dropdown set to “United States of America ($)”. Field 6 is Hotel Override IATA, empty. Field 7 is Car Override IATA, empty.
FieldDescription
1: Agency Booking Config.This field is where the Agency Booking Configuration is assigned to the company. Once the Agency Booking Configuration is created, it can be selected from the dropdown menu.

This should be the agency configuration created when the setup request work order is submitted. If you do not see the correct agency, contact SAP Concur support immediately.

2: BAR (Accounting Name)This field refers to the Business Accounting Record (BAR), which is the Profile in the Global Distribution System (GDS). Each GDS refers to the profile by a different name, most commonly known as BAR in Sabre, STAR in Apollo (Travelport) and Sabre, Worldfile in Amadeus. The specifications are (optionally) PCC- followed by the BAR/STAR/Worldfile name.
  • If you want to move the user-level profile (Apollo -OR- Sabre), put a * in front of the BAR/STAR/Worldfile
  • If you want to merge the two, use a ^
  • You can specify multiple moves by separating them with commas (except in Worldspan)
  • If you have a multiple BAR/Level 2 Star/Level 3 Worldfile/ Company Profile, use [ORG_UNIT_NAME]. The multiple levels all must be within the same PCC/SID/Office ID
3: Accounting Code (LEAVE BLANK FOR WORLDSPAN)If applicable, enter as appropriate with the following in mind:
  • Leave this field blank if the GDS is Worldspan
  • For Sabre, this field is typically referred to as the DK number
  • You do not need to fill in this field if the Accounting Code/DK Number is coming from the BAR/level 1 STAR/Company Profile that is being merged into the PNR
4: Profile Template FileSelect a profile sync template file.

Note

Sabre has its own Sabre Profile Templates. This field is not applicable to Sabre.
5: Travel Agency Ticketing CurrencySelect the currency that corresponds to your TMC's fulfillment currency for this configuration. The results in Concur Travel will appear in the currency that the GDS uses.

Note

The country named here is the default country used in Google Maps when a user searches for a location.
6: Hotel Override IATAEnter the IATA number to specify an IATA override for hotel segments.

Some companies have their own IATA number to track and collect their hotel commissions globally instead of through regional agencies. The PNR and flight segments must exist under the travel agency IATA, which requires an override for the hotel segments.

7: Car Override IATAEnter the IATA number to specify an IATA override for car segments.

Some companies have their own IATA number to track and collect their car commissions globally instead of through regional agencies. The PNR and flight segments must exist under the travel agency IATA, which requires an override for the car segments.

Sabre Specific Fields

For Sabre only, there are additional fields in the Agency Information section as depicted in the following graphic.

Screenshot shows the Company Travel Configuration page. A browser find bar at the top shows the search term “profiles template ID” with result 1/1. In the main panel for “Configuration for Northerly Accounting Inc.” a yellow-highlighted row beneath Profile Template File shows the Sabre-specific fields: Sabre Profiles Template ID, Sabre Profiles Name Field Remark, and Sabre Profiles Name Format.

Review the following table to learn more about each field.

FieldDescription
Sabre Profiles Template IDEnter the Sabre Template ID that SAP Concur will use when creating or updating traveler profiles in the Sabre Profiles system.
Sabre Profiles Name Field RemarkSpecify the format for the Sabre Name Field Remark. You can use one or multiple data elements, separated by a dash (-), dot (.), or asterisk (*). Supported elements include:
  • [EMP_ID] for Employee ID
  • [JOB_TITLE] for Position/Job Title
  • [ORG_UNIT] for Org Unit
  • [COST_CENTER] for Cost Center
  • [CUSTOM_FIELD_NAME] for Custom Profile Field
Sabre Profiles Name FormatDefine the format for naming traveler profiles in Sabre Profiles using a comma-separated list of format strings. The default format is: L/FI, L/NI, L/F, L/N.

Summary

  • Find Agency Information at the top; use scroll or Back to Top to return
  • Assign the Agency Booking Configuration; contact support if the correct agency is missing
  • Use BAR to identify the GDS profile; follow rules for moves, merges, and multiple profiles
  • Enter GDS-specific fields correctly: Accounting Code/DK, Profile Template applicability, and ticketing currency displays in GDS currency
  • Apply Sabre-specific template and naming settings when applicable