SAP Concur Training - Travel: May 2020 Release Notes · Web viewFQ-GBP 284.00/USD 16.50GB/USD...

Travel: May 2020 Release Notes

SAP Concur Release Notes

Concur Travel

Concur Professional/Premium and Concur Standard

Month

Audience

Release Date: May 16, 2020

Update #1: Friday, May 15, 12:00 PM PT

SAP Concur Client FINAL

** FINAL **

The enhancements and changes described in this document may or may not be included in this release. SAP Concur reserves the right to postpone implementation of – or completely remove – any enhancement/change mentioned here.

The PREVIEW, DRAFT, and FINAL release notes contain information about Concur Professional/Premium and Concur Standard.

Each note contains a table that which indicates if the enhancement/change applies to Professional and/or Standard.

Contents

Release Notes1

Flight1

User-Abandoned Trips Containing Cleartrip Segments Placed in the Refund Request Queue1

Hotel3

**Ongoing** Direct Connect Content for Mobile App3

Sabre: Hotel - Content Services for Lodging Support5

Starwood Loyalty Numbers No Longer Used8

Miscellaneous9

Manage Holds and Purge Users Description Updated9

Modified Home Page Appears When Some Products and Services Are Unavailable10

Old Sign In Experience No Longer Available13

**Ongoing** Deprecation of HMAC Initiates Migration to SSO Self-Service15

**Ongoing** SAP Concur Legacy File Move Migration17

Retirement of Legacy Notifications for Profile Form of Payment, and Itinerary Changes19

Support for New Language (Thai)20

Users Connecting to the US Data Center Are Redirected21

Travel Operations / Technical Essentials22

Southwest Airlines Update22

**TMC Preview** Amadeus: Support for Amadeus Ticket Changer (ATC)25

**Ongoing** Apollo/Galileo: Migrate Legacy Web Services to Galileo Web Services34

**TMC Preview** Travelport Branded Fares – Full Support38

Planned Changes46

Administration46

**Planned Changes** Approve Then Book User Permission46

**Planned Changes** Retire Legacy Credit Card Feed48

**Planned Changes** Retire Legacy HR Feed Editor50

**Planned Changes** Retire Legacy Travel Assistant Feed51

Travel Operations / Technical Essentials53

**Planned Changes** HRS. Update Hotel Passive Segment53

Client Notifications56

Browser Certifications and Supported Configurations56

Monthly Browser Certifications and Supported Configurations56

Subprocessors56

SAP Concur Non-Affiliated Subprocessors56

Additional Release Notes and Other Technical Documentation57

Online Help – Admins57

SAP Concur Support Portal – Selected Users57

Legal Disclaimer

The information in this presentation is confidential and proprietary to SAP SE or an SAP affiliate company and may not be disclosed without the permission of SAP SE or the respective SAP affiliate company. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP SE or its affiliated companies. SAP SE and its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation and SAP SE or an SAP affiliate company’s strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP SE and its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP SE and its affiliated companies assume no responsibility for errors or omissions in this document, except if such damages were caused by SAP SE or an SAP affiliate company’s willful misconduct or gross negligence.

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

SAP Concur Release NotesPage 3Concur Travel

Release Date: May 16, 2020SAP Concur Client FINAL

Update #1: Friday, May 15, 12:00 PM PT

Release NotesFlightUser-Abandoned Trips Containing Cleartrip Segments Placed in the Refund Request Queue

Prof

Stan

Edition

X

X

On: Impacts end users who use this feature/vendor; no configuration/setup by agency/ admin; cannot be turned OFF (example: new icons or rate display, new Amtrak feature)

Available for use: No impact to end users unless/until configuration/setup by agency/admin (described below) (example: new rule, new Travelfusion airline)

Other: Refer to the release note below

Does not apply to this edition

Source / Solution Suggestion

GDS

All

Direct Connect

Cleartrip

Solution ID

Other

X

EMEA Data Center

Scan impact

X

North America Data Center

UI impact

China Data Center

X

File finishing impact

All data centers

Profile/Profile API/3rd Party XML Sync Impact

Affected Documentation

TSGs

Cleartrip Direct Connect

Fact Sheets

Admin Guides

Other

Overview

As of April 17, 2020, SAP Concur solutions has changed the queuing logic for user-abandoned or orphaned PNRs containing passive segments for reservations through the Cleartrip API. Such PNRs are now put onto the refund request queue.

To work with this change, TMCs should check their queue setup to ensure a refund request queue is set up for joint customers in India using Cleartrip.

Previous to this change, user-abandoned or orphaned PNRs with Cleartrip segments that were not finished by the user during the correction time window were moved to the TMCs ticketing queue. This is in keeping with SAP Concur solutions’ standard logic for instant ticketing direct connect flight bookings, since the ticket is already issued, and payment processed.

SAP Concur solutions decided to adapt the queuing logic for user abandoned or orphaned PNRs with Cleartrip segments to better meet requirements of customers and TMCs in India, honoring the differences in the distribution model of Cleartrip compared to other air direct connects available in Concur Travel.

In the regular process for a properly finished trip, Cleartrip processes the payment for all transactions against a deposit account, usually owned by the TMC. TMCs bill charges against this account back to the customer. When a user creates a booking with Cleartrip, the deposit account is used for a purchase. Concur Travel puts the PNR onto the ticketing queue for the TMC to follow up and bill back to the customer.

For an unfinished (user-abandoned or orphaned) trip, the reservation through the Cleartrip API and ticketing takes place and generates a hit against the deposit account, but due to the unclear state of the booking, the PNR finishing process of Concur Travel cannot add all remarks (for example, custom trip field values and other remarks) needed by the TMC to trigger their billing process.

A comparison of charges against their deposit account with invoices to the customer may show a discrepancy to the TMC but the task to research the unfinished bookings responsible for that discrepancy is largely manual and time-consuming.

SAP Concur solutions modified the queuing logic to place unfinished bookings with a Cleartrip segment into the refund request queue to make TMCs aware that manual intervention is needed.

For more information on Cleartrip, refer to the Cleartrip Travel Service Guide. For more information on the queuing logic for abandoned and orphaned trips, refer to the Auto Cancel Fact Sheet. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

User/Customer Benefit

Bringing awareness to TMCs of bookings that require manual intervention by placing them in the refund request queue helps them to follow up with travelers on unfinished bookings. TMCs can work with them to determine whether the booking should be canceled and refunded (if possible) or finished in manual action to enable processing by mid-office routines.

It also better supports TMCs in their efforts to reconcile Cleartrip charges against their account with invoices to their customer.

What the User Sees

This update generates no visible changes in the web application.

Configuration for Professional Travel

To apply the changed queuing logic, a refund request queue must be created in the GDS by the TMC and needs to be added to the queue set in the travel agency configuration page within Concur Travel.

Configuration for Standard Travel

To apply the changed queuing logic, a refund request queue must be created in the GDS by the TMC and must be added to the queue set in the travel agency configuration page within Concur Travel.

Hotel**Ongoing** Direct Connect Content for Mobile App

Prof

Stan

Edition

X

X






GDS

Direct Connect

TripSource, HRS, RoomIt

Solution ID

SS-0000027344, SS-0000018121, SS-0000000252

Other

X

EMEA Data Center

Scan impact

X


X

UI impact

China Data Center


All data centers



TSGs

Fact Sheets

Admin Guides

Other

UPDATE: Concur Travel has released HRS Direct Connect Content for Mobile App users. Product Teams are currently engaged with TripSource and RoomIt Direct Connect partners for follow up releases.

For more information, refer to Travel: HRS Direct Connect Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Overview

SAP Concur solutions mobile app users will have the ability to shop, book, and cancel content from Hotel Service V2.

Since the integration with Airbnb requires Concur Travel to link to the Airbnb website for checkout, Airbnb is available on desktop application only.


Travelers expect to be able to book travel on any device. After March 31st, travelers will be able to search, book, and cancel Hotel Service V2-sourced hotels from within the SAP Concur solutions mobile app.

What the User Sees

Content available through Hotel Service V2 will be available within the SAP Concur solutions mobile app on iPhone and Android devices.

Example:

Configuration for Professional and Standard Travel

No configuration is required. These updates are enabled automatically for all sites with content that is available through Hotel Service V2 Direct Connect, with the exception of Airbnb.

Sabre: Hotel - Content Services for Lodging Support

Information First Published

Information Last Modified

Feature Target Release Date

January 2020

March 16, 2020

March 2020

Any changes since the previous monthly release are highlighted in yellow in this release note.

Prof

Stan

Edition



X

X




GDS

Sabre Only

Direct Connect

Solution ID

Other

EMEA Data Center

Scan impact


UI impact

China Data Center


X

All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

In compliance with Sabre’s requirement to migrate from Sabre’s legacy hotel APIs, Concur Travel will be migrating to Sabre’s new Content Services for Lodging APIs (CSL) as of May 1, 2020.

These new services, while very similar, are not backward compatible with the legacy hotel services. For end-users, the transition will not affect the booking experience or their ability to confirm hotel reservations. For TMCs, Concur Travel has done everything it can to minimize any impact to current mid-office processes using cryptic host commands (i.e. HOT, HOD, HRD, HOX, and XI. – See Sabre SAN-15891) by using CSL to consume hotel content, while booking live hotel segments in the same structure as the legacy APIs. Concur Travel partners reserving offline full CSL hotel bookings through Sabre Red 360 can expect those reservations to appear on the user’s travel itinerary, however, Concur Travel will not have the ability to modify or cancel these bookings; they will be in a “read only” state.

As a general guideline, Concur Travel will continue to function very much the same in the future as it does today, but will use new services to support this functionality. Support for CSL aggregator content is not currently part of Concur Travel’s product direction. All hotel segments will be created in the legacy structure. Any offline hotel booking where a hotel segment was created in the CSL structure will be read only. Concur Travel will not allow any cancellation or modification of any CSL structured segments.

For TMCs, it is important to understand how the lack of backward compatibility is manifested and why it matters. Please refer to Sabre’s documentation on the limitations between CSL and the previous hotel services.

Travel Management Companies (TMCs) and 3rd party mid-office solutions should review this functionality (below) to determine if Concur Travel’s implementation of CSL will affect any of their processes or systems.

Functionality

Supported Yes/No

Shop GDS content via CSL

Yes

Sell hotel segments (legacy structure)

Yes

Sell hotel segments (CSL structure)

No

Shop aggregator content (Direct Connect)

Yes

Sell aggregator content (Direct Connect)

Yes

Shop aggregator content via CSL

No

Hotel Details Look-up

Yes

Read CSL hotel segments

Yes

Modify hotel segments (CSL structure)

No

Cancel hotel segments (CSL structure)

No

Cancel hotel segments – Offline Approval (CSL Structure) See FAQ below for additional information.

No


Users should see no difference when shopping and confirming a hotel reservation. They should also see no difference when attempting to change or cancel an existing reservation if it was originally booked in Concur Travel. If a hotel reservation is booked and confirmed outside of Concur Travel, a user’s ability to change or cancel that reservation may be limited.

TMC/Customer Benefit

All hotel bookings created within Concur Travel will use the same back-end structure as is used today. All mid-office processes that are run within Compleat should remain unaffected.

For hotel bookings made outside of Concur Travel, only those using the legacy API structure will be manageable within Concur Travel. If a booking was created with one of the CSL “create services” or Sabre Red 360, it will not be manageable within Concur Travel.


This feature is automatically enabled. There are no configuration steps.

FAQ

Q. Why can’t I cancel or change my offline hotel booking within Concur Travel?

A. All pre-CSL services create hotel bookings in a different back-end structure from the new CSL services. Older services aren’t able to make any changes to CSL structured bookings and CSL services can’t many any changes to any booking in the pre-CSL structure.

Q. If Concur Travel won’t be able to return hotel aggregator content through the new CSL services, where will I get aggregator content?

A. Aggregator content is still available via the Hotel Direct Connects.

For more information, refer to the Hotel Service Content Suppliers Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Starwood Loyalty Numbers No Longer Used




May 2020

n/a

2nd quarter of 2020


Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

X

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers

X



TSGs

Fact Sheets

Admin Guides

Other

Overview

After Marriott International bought Starwood Hotels in 2016, they retired Starwood’s loyalty program, Starwood Preferred Guest (SPG), and converted affected travelers to Marriott’s own loyalty program, now called BonVoy. However, old SPG numbers are still present in user profiles in Concur and continue to be added by some TMCs during the XML profile sync processes. This has the effect of creating errors in some scenarios when a user tries to book with Marriott.

Beginning in May 2020, SAP Concur solutions will remove old SPG loyalty numbers from users’ profiles and will no longer write new SPG loyalty numbers to user’s profiles. Any such numbers coming via the XML profile sync will be ignored and will not be returned via the Travel Profile 2.0 API.


Users will no longer get SPG-related errors when booking with Marriott.


This feature is enabled by default. There are no configuration steps.

MiscellaneousManage Holds and Purge Users Description Updated

Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

EMEA Data Center

Scan impact


UI impact

China Data Center


X

All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

The description of the Manage Holds & Purge Users data retention feature that appears on the Administration > Company > Data Retention page has been updated.

Before Update

After Update


This update provides more accurate information about where a user with the Data Retention Administrator role can find the Hold User, Remove Hold, and Purge User buttons.


There are no configuration or activation steps.

For more information, refer to the Shared: Data Retention Setup Guide for Professional edition, or the Shared: Data Retention Setup Guide for Standard Edition. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Modified Home Page Appears When Some Products and Services Are Unavailable

Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

EMEA Data Center

Scan impact


UI impact

China Data Center


X

All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

When a user signs into SAP Concur solutions, if some products or services are unavailable while other products and services are up and running, a modified version of the user’s Home page appears, providing access to the products and services that are up and running.

Prior to implementing this improvement, if a user attempted to sign in to SAP Concur solutions when one or more products or services was not available, a 503 (service unavailable) message appeared, the user’s Home page could not be accessed, and the user had to wait until all services and products were available before signing in to SAP Concur solutions.

The products and services that appear on a user’s Home page are specific to the user and they might differ from user to user.


This enhancement enables users to complete tasks that rely on the products and services that are up and running even when other products and services might be unavailable.

What the User Sees

When the user signs in, SAP Concur solutions determines which products and services are available to the user. If any products and services are unavailable, SAP Concur solutions presents the user with a modified Home page that includes tiles for each service.

Services that are up and running are signified by a green bar and checkmark at the top of the tile. Services that are not available are signified by a red bar and exclamation point at the top of the tile. In addition, a message displays indicating that one or more products or services are currently unavailable.

For users with access to Concur Open (open.concur.com), Concur Open uses a different process for determining the up and down time of products and services. As a result, it might take slightly longer for Concur Open to reflect the immediate availability of a product or service.


This enhancement is automatically available; there are no additional configuration or activation steps.

Old Sign In Experience No Longer Available

Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

EMEA Data Center

Scan impact


UI impact

China Data Center


X

All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

On October 31, 2019, SAP Concur solutions introduced a new experience for users signing into SAP Concur.

Since introducing the new sign-in experience, users have been able to choose between signing in through the new Sign In page or reverting to the old sign-in experience. Beginning with the May release, the old sign-in experience is no longer available.


The new sign-in experience provides better security and is faster and more convenient for users logging in to SAP Concur products and services. This change makes the sign-in experience uniform for all users.

What the User Sees

Beginning on October 31, 2019, users were incrementally given access to the new sign-in experience.

When a user opened the SAP Concur Sign In page, they saw the new Sign In page, and, at the top of the page, a Take me back to the old Sign In experience link.

When the user clicked the Take me back to the old Sign In experience link, they saw the legacy Sign In page.

Beginning with the May release, users no longer see the message at the top of the new Sign In page, and they cannot revert to the old experience.


There are no configuration steps. This change occurs automatically.

**Ongoing** Deprecation of HMAC Initiates Migration to SSO Self-Service




July 12, 2019

February 28, 2019

Phase I: July 2019

Phase II: July 2020


Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

EMEA Data Center

Scan impact


UI impact

China Data Center


X

All data centers



TSGs

Fact Sheets

Admin Guides

Other

Shared Planned Changes

Overview

SAP Concur solutions will soon begin the deprecation process of removing Hash-Based Message Authentication Code (HMAC) as an SSO option. The replacement service for HMAC is SAML SSO is a self-service method of setup whereby client admins have access within SAP Concur solutions to complete their SAML connections.

Clients currently using HMAC are encouraged to migrate to the SSO self-service tool as soon as it is released (targeted for Q2 2020). The new SSO self-service tool allows multiple portals (Identity Providers) to be added.

The HMAC deprecation includes two phases:

Phase I:

· Clients must have an Identity Provider (IdP) or a custom SAML 2.0 solution.

· Clients begin testing the new SSO self-service tool. (See below for more information.)

· Travel Management Companies (TMCs) prepare for onboarding new SAP Concur solutions clients using the new SSO self-service tool, which is targeted for release in Q2 2020.

· Once the SSO tool is available, customers will be notified via release notes about the official deprecation date of HMAC. As of the official deprecation date, no new clients can be onboarded using HMAC; new clients must be onboarded using the new SSO self-service tool.

· Existing clients using HMAC need to be migrated using the new SSO self-service tool.

Phase II:

· Travel Management Companies (TMCs) continue migrating existing SAP Concur solutions clients from the HMAC service to the new SSO self-service tool.

· Shut down the HMAC service after everyone has migrated from HMAC to the new SSO self-service tool. Phase II is targeted to end mid-year 2020.


This change provides better security and improved support for users logging in to SAP Concur products and services.

Important – Migration for TMCs

Travel Management Companies (TMCs) will be largely impacted and should begin testing SAML SSO now to prepare for migration to the new SSO self-service tool.

TMCs need to set up SAML SSO instead of HMAC for their new clients. Setting up SAML SSO now allows more time for TMCs to test the SSO self-service tool and train internal staff to assist clients.

To prepare for Phase I of the HMAC deprecation:

· TMCs first need to support SAML 2.0. TMCs need to contract for or develop their SAML 2.0 solution. TMCs need to have an Identity Provider (IdP).

· Once support for SAML 2.0 is complete, TMCs that need more information can open a case with SAP Concur support. TMCs do not need to use the online order form to request setup.

Important – Migration for Legacy HMAC Clients

Clients should begin testing SSO immediately to prepare for migration to the new SSO self-service tool.

To prepare for Phase I of the HMAC deprecation:

· Clients need to have an Identity Provider (IdP) or a custom SAML 2.0 solution.

· Clients can configure the SSO self-service tool as soon as it is released in Q2 2020.

More Information

For more information, refer to Authentication | **Planned Changes** Single Sign-On (SSO) Self-Service Option in the Shared Planned Changes release notes. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

**Ongoing** SAP Concur Legacy File Move Migration




March 6, 2020

--

Ongoing in 2020


Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

EMEA Data Center

Scan impact


UI impact

China Data Center


X

All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

This release note is intended for the technical staff responsible for file transmissions with SAP Concur solutions. For our customers and vendors participating in data exchange, SAP Concur solutions is maintaining our file transfer subsystem to provide greater security for those file transfers.

SAP Concur solutions will begin migrating entities that currently use a legacy process for moving files to a more efficient and secure file routing process that relies on APIs.

Clients whose entities are currently configured to use the legacy process will be migrated to the more efficient process sometime between now and the end of 2020. After they are migrated to the more efficient process, clients will see the following improvement:

· With the legacy process, clients had to wait for the file move schedule to run at a specified time. With the more efficient and secure API-based process, extracts and other outbound files from SAP Concur solutions will be available within the existing overnight processing period shortly after the files are created.

This announcement pertains to the following file transfer DNS endpoints:

· st.concursolutions.com


These changes provide greater security and efficiency for file transfers.


If assistance is required, please contact SAP Concur support.

For more information, refer to the Shared: File Transfer for Customers and Vendors User Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Retirement of Legacy Notifications for Profile Form of Payment, and Itinerary Changes

Prof

Stan

Edition

X

X






GDS

Direct Connect

Solution ID

Other

X

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

SAP Concur solutions continually reviews our products and services for compliance with security best practices. As part of a security improvement to our authentication infrastructure, the decision has been made to retire notifications for Profile, Form of Payment, and Itinerary for a user or a company because of their handling of OAuth tokens.

The decision to remove these notifications rather than refactor them to handle authentication differently was driven by both extremely low usage and a high error rate (unsuccessful delivery).

The notifications for Profile and FOP changes were disabled earlier in 2020. The notifications for Itinerary changes will be disabled in May or June 2020.


This change improves security for all clients.


No configuration is required.

Support for New Language (Thai)

Prof

Stan

Edition



X




GDS

Direct Connect

Solution ID

Other

EMEA Data Center

Scan impact


UI impact

China Data Center


X

All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

With this release, SAP Concur solutions now supports the following language:

· Thai


This change enables users to configure the SAP Concur solutions UI text to display in Thai.

What the User Sees

This language must be enabled in order to appear on the list. If the language is enabled, when a user opens the SAP Concur solutions Sign In page and then clicks to view the available languages list, Thai appears in the list.

Users Connecting to the US Data Center Are Redirected

Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

Beginning in May, users who connect to the US Data Center through www.concursolutions.com will be redirected to us1.concursolutions.com.

This change does not impact the Base URI (Instance URL) used in API calls to the SAP Concur solutions US Data Center.


This change makes the format of the URL for SAP Concur data centers consistent from one data center to another. For example, users connecting to the EMEA data center are redirected to eu1.concursolutions.com.


Users are automatically redirected. There are no configuration or activation steps.

Travel Operations / Technical EssentialsSouthwest Airlines Update




April 2020

April 17, 2020

May 2020


Prof

Stan

Edition



X

X




GDS

Worldspan & Apollo only

Direct Connect

Solution ID

Other

X

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Southwest via Travelport

Fact Sheets

Admin Guides

Other

Overview

Southwest Airlines is now a full participant for Apollo and Worldspan GDS. Flight schedules and fare content will be made available to US-based agencies who have obtained authorization from Southwest Airlines.

For more information about this change, refer to the Travelport Product Advisory, and/or the Southwest FAQs on MyTravelport.

Configuration for Professional or Standard TravelWorldspan Configurations

Today, travel configurations that use Worldspan as the primary GDS cannot provide Southwest content from Worldspan, so there are no related configuration settings to enable the GDS content.

If the Southwest Direct Connect is enabled for a Worldspan configuration, this will block GDS content from returning. Customers and TMCs should review this full release note for considerations relating to disabling the Direct Connect. SAP Concur teams are evaluating if further changes will be necessary in the future.

Apollo Configurations

Travel configurations that use Apollo as the primary GDS can provide limited Southwest content on Apollo but must first obtain a Certificate of Appointment from Southwest. Due to this requirement, Concur Travel has supported a special configuration option to ensure Southwest content would only be requested from Apollo when an agency partner has been authorized.

Since Southwest continues to require pre-authorization, SAP Concur teams expect this travel configuration option will remain in place but will evaluate if this is still necessary in the future.

To enable:

1. Click Administration > Travel (on the sub-menu) > Travel System Admin and access the desired client travel configuration.

Depending on your permissions, the page may appear immediately after you click Administration or Travel.

On the travel configuration page, locate the System configuration options section.

Check (enable) the APOLLO/GALILEO ONLY: Southwest COA filed and active on this PCC checkbox.

Save the travel configuration.

If a customer has previously used Direct Connect and will now be obtaining Southwest content from Apollo, the following travel configuration options should be reviewed and/or updated. In the Air Connectors section, Southwest Airlines subsection:

· Enable setting

· Search both the primary GDS and the Southwest direct connect setting

· Cost savings threshold setting

Known Limitations

The following limitations have been identified to date:

· The Post-Ticket Change feature prevents exchanges on Southwest bookings; Travelport has advised that this functionality has been temporarily suspended; this functionality will be made available in the future, but no dates have been provided at this time.

· Flights to airports in Mexico are not yet offered in Travelport; these will be available in the future.

· Flights to Nassau are not yet offered in Travelport; this is under investigation with Travelport.

FAQ

The following section of Frequently Asked Questions may be updated as more information becomes available. Please be sure to check for updates.

Q. If we are not a US-based agency, can we enable Southwest content in our Travelport GDS?

A. No. Southwest content will only be available for agencies based in the US.

Q. Will Travelport Southwest branded fares be available/supported in Concur Travel?

A. Yes, Concur’s branded fares functionality for Travelport will automatically support Southwest’s fare as long as they follow the established standard pricing methods.

Q. Will Early Bird check-in be supported in Worldspan/Apollo?

A. Southwest has advised that Early Bird check-in will be supported via Worldspan/Apollo in a later phase, but the exact date is not yet available.

Q. Will Southwest content be offered on other GDSs?

A. Yes, Southwest content will be available on Galileo and Amadeus in a later phase.

Q. If a customer has been using direct connect and wants to switch to GDS, can their travelers’ unused ticket credits be used for GDS bookings?

A. Unused credits (residual travel funds) from direct connect will not be lost but cannot be transferred to the GDS since those credits were created via direct settlement with Southwest. Miscellaneous charges orders (MCOs) and ARC settlement will be used in the GDS. The GDS does not recognize a Southwest-generated ticket credit. Existing unused funds will need to be used via Southwest direct channels. Funds created by a cancellation via the GDS will need to be used via the GDS. Customers with further questions regarding unused funds should reach out to their Southwest Account Manager.

Q. Is a different process required for discount codes for Southwest than there is for traditional GDS vendors?

A. The process required for discounts is changing from what Southwest uses today but should now match what’s being used for other airlines. Following the targeted May 1st launch, Southwest will start using tour codes in the GDS. Southwest Account Managers have reached out to existing customers with a discount to ensure a tour code is in place where applicable. Customers with questions about discounts should reach out to their Southwest Account Manager.

**TMC Preview** Amadeus: Support for Amadeus Ticket Changer (ATC)

Prof

Stan

Edition


X

X





GDS

Amadeus Only

Direct Connect

Solution ID

SS-18427

Other

X

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Post Ticket Change / Amadeus Ticket Changer (new TSG coming soon)

Fact Sheets

Admin Guides

Travel System Admin

Other

UPDATE: An issue with the display logic on the Itinerary View pages when completing an exchange has been identified. Currently, the total costs displayed at the bottom of the itinerary include the original ticket cost, the new ticket cost, and the change fees. This is due to incorrect ticket coupon status handling. SAP Concur teams are currently working to address this defect as soon as possible. Please watch this release note for further updates.

Overview

Historically, Concur Travel has offered post-ticket change capabilities for Sabre (via Sabre Automated Exchanges), Worldspan (via Rapid Reprice), and Apollo (via Worldspan cross-GDS Rapid Reprice).

With the March 2020 release, SAP Concur teams are pleased to announce support for exchange capabilities for Amadeus via Amadeus Ticket Changer (ATC) for Professional edition. ATC will be made available for Standard edition with the April 2020 release.


Amadeus customers will be able to make changes to their ticketed reservations online, eliminating the need to call their agency.

Agency Fulfillment Partner Benefit

Amadeus agency fulfillment partners can automate exchange processing for Concur Travel customers, saving time and travel consultant resources.

What the User Sees

The user opens their trip from My Trips. To change the trip, the user locates the desired Flight and clicks Change.

In the Change Flight window, users can change either segment of their flight. Concur Travel will automatically adjust any car or hotel reservations to match the days of the flight change. The user selects the updated day and time for the flight(s) they wish to change, and then clicks Search.

Concur Travel performs a search for the requested dates/times; the user then selects their desired flight(s) from the results.

Once the flight selection(s) is complete and the user clicks Get Price, updated cost information for the trip is displayed, including original airfare, new airfare, airfare difference, exchange fee, and the total cost of the exchange. To finalize the change, the user clicks Purchase New Flights.

At this point, the user can still maintain their original flights by clicking Cancel Flight Exchange.

An updated itinerary is displayed once the user clicks Purchase New Flights:


To configure:

1. In the company configuration (under Travel System Admin), choose “Concur Web” from the “Allow post-ticketing flight changes” dropdown:

In the agency configuration, (under Travel System Admin) complete the queuing configuration for “ticket change request queue” as demonstrated below:

For more information, refer to the Post Ticket Change / Amadeus Ticket Changer (ATC) Travel Service Guide. It will be available in the coming weeks. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Known Limitations

The following restrictions apply:

· ATC is not yet available for Standard edition; this will be made available with a future release

· Air France Abonnement fares are not yet supported; this will be made available with a future release

· The Ticket Change Attempts Travel report is not supported for Amadeus; there is no plan to update this report at this time

· The old and new Itineraries may only consist of a single carrier (multi- carrier bookings not supported)

· Not available on free tickets

· Only ARC/BSP accredited airlines are available through ATC

· Concur Travel does not support the exchange of unused tickets or credits on file; this limitation is due to Concur Travel’s inability to view the original electronic ticket shell if not issued in the same PNR

· Changes may only be made on live flight segments with no support for past date travel

· PNR’s with more than four segments or coupons may not be changed online

FAQ

Q. What is Amadeus Ticket Changer (ATC)?

A. ATC is a ticket re-pricing solution, which automatically researches old and new fares and rules, generating new, accurate pricing in seconds. The newly calculated price reflects appropriate rules, taxes, additional collections, refunds, penalties or administrative fees.

Q. How does ATC work?

A. ATC employs a pricing engine with a comprehensive “Fares and Pricing” database, offering 13 months of historical fare and rule data. It utilizes pricing construction based on historical, current, or a combination of historical and current fare and rule data.

Q. How can I look back at a previous ticket change?

A. Ticket changes with Concur Travel and ATC will cause historical fare quotes (TTHs) to be retained, with all the elements of the ticket change criteria; including old ticket booking date, place of issue, base tax and totals of old ticket.

Q. How many times can I change a ticket?

A. Once a ticket has been changed, it cannot be changed again.

Q. Will ATC work for international fights booked in Concur Travel?

A. ATC handles all itineraries both domestic and international conditionally if the original and re-priced itineraries.

Q. Which airlines are supported by ATC?

A. In Amadeus, enter FQN ATC/CXR and all ATC carrier participants will be listed.

Q. Can policy be applied to post ticket changes?

A. Yes; post-ticket change rules allow travel managers to use a subset of the standard Concur Travel rule violation options to help enforce corporate travel policy when users change their tickets.

Q. Can exchanges be made in Concur Travel & Expense if the original reservation was made by a traditional agent (offline booking)?

A. Yes, it can be used for offline bookings if the TST was stored at ticketing. There are no limitations on this feature, except limitations imposed by Amadeus.

**Ongoing** Apollo/Galileo: Migrate Legacy Web Services to Galileo Web Services




June 2019

—

TBD


Prof

Stan

Edition



X

X




GDS

Apollo and Galileo GDS Only

Direct Connect

Solution ID

Other

X

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

To retire legacy connectivity with Travelport, Concur Travel is migrating from the XML Select connectivity platform to the Galileo Web Services connectivity platform. This change benefits SAP Concur customers as follows:

· Allows better scalability and stability of Concur Travel’s Apollo/Galileo services

· Enables SAP Concur teams to remove legacy code used for connectivity to Apollo/Galileo, which simplifies internal operations

· May improve performance, since a more simplified connectivity approach will be used

· May improve stability

While this connectivity change should be seamless for end users, it does require an access-related change that will affect agency fulfillment partners (TMCs). With this change, Concur Travel will require the Host Access Profile (HAP) for the booking pseudo city code.

The HAP combines several types of identifiers into one "master" identification profile: the Pseudo City Code (PCC), Structured Data Identity, Host Sign On, Password, Host Identity, and additional identifiers for certain components. As such, the HAP identifies the customer to Galileo Web Services, provides permissions to specified services, and provides permissions and access to various GDS functions.

SAP Concur teams are working with Travelport to perform a mass update for existing customer configurations, but new customer implementations will require TMCs to obtain and configure the HAP in Concur Travel directly. The TMC Reseller Toolkit now provides updated implementation guidance for Apollo/Galileo agency partners.

As of February 2020, almost all European Data Center Apollo and Galileo customers have now been migrated to Galileo Web Services. With the March release, the HAP field in the Agency Configuration will become:

· Visible for all Apollo/Galileo Agency Configurations, regardless of datacenter

· A required field for Apollo and Galileo agency configurations in the EU datacenter (agency admins will not be able to save changes to an Agency Config without specifying HAP information)

With this change, SAP Concur teams are now focused on migrating US Data Center customers. Additional updates around this effort will be provided in this release note as they become available.


A new field exists in the Agency Configuration for the HAP information, as shown below:

FAQ

Q. What will happen if a TMC does not populate the HAP, if their Agency Configuration is one that does not successfully get populated during the mass update?

A. Today, Concur Travel will fall back to the legacy connectivity when no HAP is specified. SAP Concur representatives will reach out to affected TMCs to address missing HAPs before the legacy connectivity is retired. Ahead of that, the HAP field would be exposed in the Agency Configuration and would be a mandatory field for the purposes of saving any changes. Once the legacy connection has been retired, Apollo and Galileo will be managed similarly to Sabre and Amadeus, where the credential (HAP) will be required as part of the implementation process.

Q. How will TMCs be able to identify which of their configs do not have the HAP populated?

A. From a TMC login, the “View Travel Agencies” page shows the HAP info in the “SWS PCC” column so agencies can navigate to this page, sort by GDS, and look for missing HAPs.

Q. Will there be a way for agencies to validate their HAPs when adding them to Agency Configurations (similar to the Test Password feature for Sabre and Amadeus)?

A. This is being evaluated to see if it can be supported. Release notes will be updated once more information is available.

Q. Do we have a date as to when the HAP field will be mandatory in US datacenter Agency Configurations?

A. No, no date is available to share but a warning will be provided ahead of time via release notes.

**TMC Preview** Travelport Branded Fares – Full Support




June 2019

—

TBD


Prof

Stan

Edition



X

X




GDS

Apollo, Galileo, and Worldspan Only

Direct Connect

Solution ID

SS-24852, SS-15609, SS-19783, SS-25557, SS-23737, SS-18448

Other

X

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Branded Fares Travel Service Guide

Fact Sheets

Admin Guides

Other

UPDATE: SAP Concur solutions has resolved the previously identified issue with storing discount codes with brand modifiers for Apollo/Galileo customers. A small pilot has been in place for one week and no new issues have been reported. TMCs and customers are again welcome to request SAP Concur solutions enable the new functionality for testing and validation.

Overview

In 2017, SAP Concur solutions announced limited support for branded fares for all Apollo, Galileo, and Worldspan customers.

SAP Concur solutions has been in development, in partnership with Travelport, to deliver true branded fares support for all Travelport customers. Specifically, this development changes the way Concur Travel stores fares in GDS PNRs; fare stores will include brand modifier(s) for branded fare airlines. This new fare store functionality was made available via pilot starting the evening of February 24.

During the pilot/preview phase, the fare store changes only occur for simple and complex airlines as described in the Airlines Supported Using Concur Travel's Legacy Custom Solutions section of the Branded Fares Travel Service Guide. As part of this feature, SAP Concur solutions also requests additional branded fares (upsell fares) for itineraries. This functionality is being piloted in conjunction with the fare store changes.

Customers interested in participating in this pilot are encouraged to notify their agency fulfillment partner and/or their SAP Concur contact.

There will be several changes over the next few releases in support of moving to a general availability state with Travelport Branded Fares. In light of the pandemic impact, SAP Concur solutions is revising some dates to ensure our agency partners have enough time to validate these changes. These dates are tentative, in the event an agency partner requires additional time due to resourcing challenges. Please see the table below for details:

Date

Affected Travelport Core(s)

Description

March 2020 Release

Worldspan

Pilot expands to include “complex” branded fares airlines (as defined in Branded Fares Travel Service Guide)

May 2020 Release

(tentative)

Apollo/Galileo

Pilot expands to include brand modifiers for any fare returned from Travelport that includes them (remove “complex” airlines restriction)

May 18, 2020

Worldspan

Concur will remove the “complex” airlines restriction and will enable the full branded fares functionality for all Worldspan travel configurations by default

Shortly after the June 2020 release

(tentative)

Apollo/Galileo

Concur will enable the full branded fares functionality for all Apollo/Galileo travel configurations by default

For more information, refer to the Branded Fares Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

What the User Sees

When the upsell functionality is active, users will see a slight change in behavior.

In the following example, when the Exclude Unbundled Economy Fares (FXD) feature is enabled, the Basic Economy brand is not shown.

When Concur Travel shows a View Fares button, as seen here, this indicates that there are upsell options available for this itinerary:

Clicking the View Fares button will cause Concur Travel to request additional fares from Travelport:

Once those fares are obtained, Concur Travel shows all branded fares that are allowed by travel policy:

What the Agency Fulfillment Partner (TMC) Sees

Following are examples of the stored fares for each GDS.

Apollo

JX9NCG/OT QSBOT DQSBOT AG 49640150 07JUN

1.1CREED/THOMAS

1 KL1000T 25SEP LHRAMS HK1 630A 900A * WE E 1

2 KL1765T 25SEP AMSFRA HK1 950A 1100A * WE E 1

OPERATED BY KLM CITYHOPPER

3 HHL GI HK1 FRA 25SEP-26SEP 1NT 99407 HGI FRANKFURT AIRPO

1A01C8S -1/RG-EUR219.84/AGT49640150/G-VI4111111111111111EXP0930/

SI-NOPREF/NM-CREED THOMAS/CF-3127759517 *

4 KL1768T 26SEP FRAAMS HK1 215P 335P * TH E 2


5 KL1023T 26SEP AMSLHR HK1 515P 535P * TH E 2


*** PROFILE ASSOCIATIONS EXIST *** >*PA·

*** ADDITIONAL ITINERARY DATA EXISTS ***>*I·

FONE-DCAAS/703-837-6100

2 XXXR/703-837-6100

3 XXXB/703-837-6100

4 WAS703-837-6100-A

DLVR-P703-837-6100¤THOMAS CREED¤1919 GALLOWS RD¤FAIRFAX VIRGINIA

22002

ADRS-CONCUR¤1919 GALLOWS RD STE 800¤VIENNA VA Z/22182

FOP:-CK

TKTG-TAU/15SEP

*** LINEAR FARE DATA EXISTS *** >*LF·

ATFQ-OK/$B-*13H1*:BF0004/ET/TA13H1/CKL

FQ-GBP 284.00/USD 16.50GB/USD 131.90XT/USD 509.40 - 07JUN TFFGB

.TFFGB.TFFGB.TFFGB

GFAX-SSRADTK1VTOKL BY 15JUN19/0000Z OTHERWISE WILL BE XXLD

2 OSI1V-GI99407ARR25SEP CXL:CXL 3 DAYS PRIOR TO ARRIVAL

Galileo

NVZCJW/UT QSBOT V7OUT AG 99999992 07JUN

1.1HUBERT/JAMES

1. KL 1000 T 08OCT LHRAMS HK1 0630 0900 O* E TU 1

2. KL 1765 T 08OCT AMSFRA HK1 0950 1100 O* E TU 1


3. HHL HL HK1 FRA 08OCT-09OCT 1NT 99461 HILTON FRANKFURT AI

1A02CT4 -1/RG-EUR219.84/AGT99999992/G-VI4111111111111111EX

P0923/NM-HUBERT JAMES/CF-3121784590*

4. KL 1768 T 09OCT FRAAMS HK1 1415 1535 O* E WE 2


5. KL 1029 T 09OCT AMSLHR HK1 1655 1710 O* E WE 2


** CLIENT FILE REFERENCES EXIST ** >*CF·

** FILED FARE DATA EXISTS ** >*FF·

** SEAT DATA EXISTS ** >*SD·

** VENDOR LOCATOR DATA EXISTS ** >*VL·

** VENDOR REMARKS DATA EXISTS ** >*VR·

** SERVICE INFORMATION EXISTS ** >*SI·

*** ADDITIONAL ITINERARY DATA EXISTS ***>*I·

FONE-LONT/703 837 6100

2. LONB*703 837 6100

3. LONE*GALILEO//DEVTRAVEL.COM

4. LONA*442076297755

5. LONB*442075739334

6. LONF*442075739335

ADRS-JAMES HUBERT*209 MADISON ST*SUITE 400*ALEXANDRIA*P/22314

ADDA-CONCUR*SYGNUS CT*22-32 MARKET ST*MAIDENHEAD*P/SL68AD

FOP -VI4111111111111111/D0923

TKTG-TAU/SA28SEP

NOTE-

1. *S*/./MN UT 07JUN 1736Z

2. *H*HOTEL SPECIAL REQUEST INFO UT 07JUN 1736Z

3. *C*CAR SPECIAL REQUEST FREE FORMAT INFO UT 07JUN 1736Z

4. HT*PERSONAL CC 4111111111111111 0923CVV UT 07JUN 1736Z



7. H**CB/TRIPLOC/CQ-IL2-HPVR4-5GG UT 07JUN 1736Z

8. H**CB/FCN/LON KL X/AMS KL FRA 185.72TFFGB KL X/AMS KL LON 1

85.7 UT 07JUN 1736Z

2. *H*HOTEL SPECIAL REQUEST INFO UT 07JUN 1736Z

3. *C*CAR SPECIAL REQUEST FREE FORMAT INFO UT 07JUN 1736Z




7. H**CB/TRIPLOC/CQ-IL2-HPVR4-5GG UT 07JUN 1736Z

8. H**CB/FCN/LON KL X/AMS KL FRA 185.72TFFGB KL X/AMS KL LON 1

85.7 UT 07JUN 1736Z

9. H**CB/FCN/2TFFGB NUC371.44END ROE0.764586 UT 07JUN 1736Z

10. H**CB/FSC/BFQ/G-1G/C-KL/D-.38OO/R-0/P-ADT.1.1.1/S-1.2...38O

O/S- UT 07JUN 1736Z

11. H**CB/FSC3.4...38OO UT 07JUN 1736Z

12. H**CB/FARETYPE/ECONOMY FLEX UT 07JUN 1736Z

FQ1 - S1-2.4-5 07JUN19 UT/AG

>FQP1/-*38OO*:BF0004/CKL

P1 HUBERT/JAMES ADT X GBP 400.84

Worldspan

1P- 4FPUFQ

1.1TELLER/AMANDA*ADT

1 UA1041M 15AUG TH IAHIAD HK1 745A 1144A/O $ SK E

2 UA 249M 16AUG FR IADIAH HK1 505P 723P/O $ SK E

P- 1.YI9555-5555555-B

2.YI9703-837-6100-A

T- 1.T/

TKG FAX-AUTO PRICED FARE TYPE EX

*** FQ/TR ITEMS EXIST ***

FOP- 1.CCVI4111111111111111N0622

G- 1.SSRDOCSUAHK1/////@-----@/M//TELLER/AMANDA- 1.1

2.SSRPSPTYYHK1///@-----@/M- 1.1

3.SSRDOCSYYHK1/////@-----@/M//TELLER/AMANDA- 1.1

6.SSRADTK1PKK1 .TKT UA SEGS BY 01AUG19 TO AVOID AUTO CXL /EARLIER

7.SSRADTK1PKK1 .TICKETING MAY BE REQUIRED BY FARE RULE

M- 1.CB/TRIPLOC/CQ-YK7-HZWF5-2WF

**** ITEMS SUPPRESSED ****/U/EDT/S/DR

>*F

T- 1.T/

TKG FAX-AUTO PRICED FARE TYPE EX

TR- 1. 4P*FSR#FXD#TR#:BF0004#BO 1P/YI9/OT 31JUL 1957Z

TKG FAX-AUTO PRICED

FQ- FARE QUOTED 31JUL BY AGT-OT/YI9

* FARE SELECTED - SR

ADT HOU UA WAS534.03UA HOU534.03USD1068.06END UA

ZPIAHIAD XF IAH4.5IAD4.5

TX 80.10US 8.40ZP 11.20AY 9.00XF

BF-1068.06 TX-108.70 TTL-1176.76 MAA0AFEY/TV04

TOTAL BF-1068.06 TX-108.70 TTL-1176.76 USD


This feature will be available by default. There will be no configuration steps.

Pilot FAQ

Q. If there are problems, can the pilot/functionality be quickly reversed?

A. Yes; within minutes. Please work through your SAP Concur contact for this so that requests can be processed as soon as possible.

Q. Would a pilot for this feature be applied site-wide? By configuration? By rule class? By travelers?

A. It is a company-wide setting, but by GDS, so if we enable Worldspan for Acme Corporation for example, then any travel config using Worldspan under Acme’s Company ID would see the new functionality.

Q. How quickly could a pilot start?

A. For Worldspan customers, the pilot can be enabled quickly after the request is received.

Due to certain limitations with the legacy Apollo and Galileo connectivity, the new fare store process is only available via Galileo Web Services. When SAP Concur solutions receives a pilot request, Travelport will perform the necessary provisioning and SAP Concur solutions will then enable the pilot for the customer. This provisioning process generally takes 1-5 business days.

SAP Concur solutions requires the Company Name, Company ID, and GDS to be present in pilot enablement requests.

For more information on Galileo Web Services, refer to the **Ongoing** Apollo/Galileo: Migrate Legacy Web Services to Galileo Web Services release note earlier in this document.

Q. Can we pilot the upsell functionality and the fare store modifications separately?

A. No. The switch SAP Concur solutions uses to enable the upsell pilot also controls the fare store pilot.

Q. Does a site need to have the Complex Branded Fares feature enabled to participate in the pilot?

A. It is not a requirement, but sites that do not have this feature enabled will only see the new upsell experience for “simple” branded fares airlines, which represents significantly less branded fare content.

Q. Will Concur Travel store fares with brand modifiers for all fares?

A. Not initially. The pilot limits this functionality to non-lowest branded fares. Once SAP Concur solutions has received general acceptance from our TMC partners on the functionality, all limitations will be removed, and Concur Travel will store fares with brand modifiers in all cases where Travelport provides it.

Planned Changes

The items in this section are targeted for future releases. SAP Concur solutions reserves the right to postpone implementation of – or completely remove – any enhancement or change mentioned here.

IMPORTANT: These Planned Changes may not be all of the upcoming enhancements and modifications that affect this SAP Concur product or service. The Planned Changes that apply to multiple SAP Concur products and/or services are in a consolidated document. Please review the additional Planned Changes available in the Shared Planned Changes Release Notes. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Administration**Planned Changes** Approve Then Book User Permission




February 2020

—

TBD


Prof

Stan

Edition


X

X





GDS

Direct Connect

Solution ID

Other

X

EMEA Data Center

Scan impact

X


X

UI impact

China Data Center


All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

The Profile User permission is used in Concur Travel for two purposes. First, in a setup using only Concur Travel, or Concur Travel integrated with Concur Expense, or Concur Travel integrated with Concur Request and a Book then Approve workflow, it allows customers to assign this permission to users that should not have access to the Travel Wizard to book travel (yet), but should already have access to all Travel-related fields in their user profile to fill in (for example, preferences on seats and meals, frequent traveler numbers, etc.).

Also, this permission can be used with a setup where Concur Travel is integrated with Concur Request and an Approve then Book workflow. It can be used in this context to restrict user access to the Travel Wizard to book travel prior to receiving Request approval, while still enabling travel booking from an approved request.

To make a clear distinction between these two use cases, SAP Concur solutions plans to introduce a new Approve then Book permission user that will enable travel booking from an approved request.

In the future, users with only the Profile User permission will be unable to book travel from an approved request. No other changes to this permission are planned. The Profile User will still have access to all Travel-related fields in their Concur Travel user profile as before.

SAP Concur solutions plans to assign the new Approve then Book permission to all existing users with Request User and Profile User permissions but without the Travel Wizard User permission so that the planned code changes will have no impact on existing customers in a scenario with integrated Travel and Request and an Approve then Book workflow. Any user assigned to an Approve then Book workflow that has the Travel Wizard User permission assigned is not affected by this change, as this permission allows one to book travel from an approved request; the additional Approve then Book permission user is not required.


This change provides a clearer separation between users who are not able to book travel under any circumstance (the Profile User permission) from users who are only allowed to book travel from an approved request (the Approve then Book permission).

What the User Sees

No visible changes will display in the web application. Admin users with respective permissions will see the new Approve then Book permission on the User Permissions admin page.


SAP Concur solutions plans to bulk update all existing users in a setup with Concur Travel integrated with Concur Request and an Approve then Book workflow that have the Request User and Profile User permissions but not the Travel Wizard User permission, so that existing customers will not be affected by this change.

To assign the new Approve then Book permission

1. Go to Company > Company Admin > User Permissions.

Under Modify Permissions by, choose the applicable option (Users, Groups, Rule Classes).

Find the Approve then Book permission from the Available Permissions list.

Click the permission name and then click Add.

Click Save.

Configuration for Standard Travel

There are no configuration steps. Concur Standard Edition users will have the Travel Wizard User permission assigned by default, so they are not affected. The Profile User and the new Approve then Book permissions will also not be available for Concur Standard.

**Planned Changes** Retire Legacy Credit Card Feed




January 2020

—

July 2020


Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

X

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

The legacy Credit Card Feed is used by fewer than five Concur Travel clients to import credit card information. However, this method of transferring sensitive information does not reflect SAP Concur’s security best practices. Due to the small number of clients still using this feature, and given that there are more secure alternatives, we are deprecating the Credit Card Feed. Targeted for July 1, 2020, existing credit card feeds will no longer be operable.


Reducing the number of supported mechanisms for exchanging data allows SAP Concur solutions to focus on providing better security and ease-of-use for our clients.

Some alternatives for a more secure and supported way to import or update credit card information in Concur Travel include:

· For all clients, allow users to manually update credit card information via their User Profile Screen in the user interface.

· For Concur Expense & Travel clients, use the Employee Import > Record Type 650: Enhanced Card Account Import Format.

For more information, refer to the Employee Import Specification. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

· Concur Expense & Travel or Travel-only clients require set up and a ghost card for travel. This allows users to use a corporate card without revealing the card number to the user.

For more information on ghost card setup, refer to the Travel: Company Settings Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.



**Planned Changes** Retire Legacy HR Feed Editor




January 2020

—

July 2020


Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

X

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

The legacy HR Feed Editor is an outdated method for importing user information into Concur Travel and is used by less than five Travel-only clients. Due to the very small number of clients still using this feature, and given that there are superior alternatives, we are deprecating the HR Feed Editor. Targeted for July 1, 2020, feeds coming via the HR Feed Editor will no longer be operable. If you think you will be affected, please contact SAP Concur support or your TMC to identify a solution that’s best for you.

Some alternatives for a more secure and supported way to import or update employee information in Concur Travel include:

· Update your system to utilize the Concur Travel API.

For more information, refer to SAP Concur solutions’ API documentation, available at the SAP Developer Center. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

· For Expense-only customers, client administrators can follow SAP Concur solutions’ process to securely import employee information.

For more information, refer to the Shared: Employee Import Specification. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.


Reducing the number of supported mechanisms for exchanging data allows SAP Concur solutions to focus on providing better security and ease-of-use for our clients.



**Planned Changes** Retire Legacy Travel Assistant Feed




February 2020

—

July 2020


Prof

Stan

Edition



X

X




GDS

Direct Connect

Solution ID

Other

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Fact Sheets

Admin Guides

Other

Overview

The Legacy Travel Assistant Feed is an outdated method for importing user information into Concur Travel and is used by less than five Travel-only clients. Due to the very small number of clients still using this feature, we are deprecating the Travel Assistant Feed. Targeted for July 1, 2020, data coming via the Travel Assistant Feed will not be imported. If you think you are affected, please work with Support or your TMC to identify a solution that is best for you.


Reducing the number of supported mechanisms for exchanging data allows SAP Concur solutions to provide better security and improve ease-of-use for our customers.

Suggested Alternatives

In Concur Travel, users can be assigned the “Self-assigning Assistant” permission via User Permissions. This will allow these users to be able to designate themselves as an assistant for any traveler within their travel configuration. For more information on the Self-assigning Assistant permission, refer to the Travel Company Admin Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.


This change will occur automatically; no configuration is required.

Travel Operations / Technical Essentials**Planned Changes** HRS. Update Hotel Passive Segment




July 2019

—

TBD


Prof

Stan

Edition

On. Impacts end users who use this feature/vendor; no configuration/setup by agency/ admin; cannot be turned OFF (example. new icons or rate display, new Amtrak feature)

Available for use. No impact to end users unless/until configuration/setup by agency/admin (described below) (example. new rule, new Travelfusion airline)

X

X

Other. Refer to the release note below



GDS

All GDS

Direct Connect

Hotel Service v2. HRS

Solution ID

Other

X

EMEA Data Center

Scan impact

X


UI impact

China Data Center


All data centers



TSGs

Fact Sheets

Passive Segment

Admin Guides

Other

Overview

As part of its standardization effort, SAP Concur solutions will be updating the standard hotel passive format for all GDS.

TMC Benefit

Once SAP Concur solutions has migrated all hotel partners to the new hotel platform (HS2), agency fulfillment partners can program mid-office routines around one format for all non-GDS hotel content in Concur Travel.

Updated formatsAmadeus

Input

HU1AHK1AMS02SEP-03SEP//SI-DC HRS/V-RT/CF-129721598/RT-EUR137.28/H-IBIS STYLES AMSTERDAM AMSTEL/A-STADHOUDERSKADE 131/C-AMSTERDAM/S-NL/Z-1074 AW/P-31206738739/G-CAXXXXXXXXXXXX6219 EXP 1125/

Output

2 HTL 1A HK1 AMS 02SEP-03SEP//SI-DC HRS/V-RT/CF-129721598/RT-EUR137.28/H-IBIS STYLES AMSTERDAM AMSTEL/A-STADHOUDERSKADE 131/C-AMSTERDAM/S-NL/Z-1074 AW/P-31206738739/G-CAXXXXXXXXXXXX6219 EXP 1125/

Sabre

Input

0HHTYXGK1AMSIN24SEP-OUT25SEP/YX MONET GARDEN HOTEL/SINGLE/RG-227.06EUR/G/SI-¤VALKENBURGERSTRAAT 76¥AMSTERDAM NL 1011LZ¥FONE31202111418¤ SINGLE CONFIRMED¤HRS¤DIRECT CONNECT/CF-129693911

Output

1 HHT YX 24SEP T GK1 AMS/OUT25SEP/YX MONET GARDEN HOTEL/SINGLE/RG-227.06EUR/G/SI-¤VALKENBURGERSTRAAT 76¥AMSTERDAM NL 1011LZ¥FONE31202111418¤ SINGLE CONFIRMED¤HRS¤DIRECT CONNECT/CF-129693911-

Galileo

Input

0HTLRDMK1AMS01OCT-OUT02OCT/BC-I/P-58038/H-RADISSON BLU AMSTERDAM/W-RUSLAND 17\AMSTERDAM\NL\1012\31205208300/R-A1KCOR/CF-129722137/SI-DIRECT CONNEC\RT-243.71EUR

Output

1. HTL RD MK1 AMS 01OCT-OUT02OCT /H-RADISSON BLU AMSTERDAM/P-58

Date post:	07-Feb-2021
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

SAP Concur Training - Travel: May 2020 Release Notes · Web viewFQ-GBP 284.00/USD 16.50GB/USD...

Documents