Travel: September 2020 Release Notes



SAP Concur Release NotesConcur TravelConcur Professional/Premium and Concur StandardMonthAudienceRelease Date: September 19, 2020Update #1: Friday, September 25, 3:30 PM PTSAP 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 TOC \o "1-3" \h \z \u Release Notes PAGEREF _Toc51939479 \h 1Flight PAGEREF _Toc51939480 \h 1American Airlines Fare Changes PAGEREF _Toc51939481 \h 1Delta Air Lines and GDS Seat Assignments PAGEREF _Toc51939482 \h 2Southwest in Sabre PAGEREF _Toc51939483 \h 3Southwest Ticket Credit Expiry Date Update PAGEREF _Toc51939484 \h 4Profile PAGEREF _Toc51939485 \h 5Travel Profile 2.0 API, Active Arrangers Only PAGEREF _Toc51939486 \h 5Miscellaneous PAGEREF _Toc51939487 \h 6**Ongoing** Deprecation of Director SAML Service and Migration to SAML v2 PAGEREF _Toc51939488 \h 6**Ongoing** Deprecation of HMAC Initiates Migration to SSO Self-Service PAGEREF _Toc51939489 \h 8**Ongoing** SAP Concur Legacy File Move Migration PAGEREF _Toc51939490 \h 11Planned Changes PAGEREF _Toc51939491 \h 13Flight PAGEREF _Toc51939492 \h 13**Planned Changes** Next Generation AA AirPass Program PAGEREF _Toc51939493 \h 13Profile PAGEREF _Toc51939494 \h 17**Planned Changes** Retiring Legacy Travel Profile?1.0 / Profile Endpoint PAGEREF _Toc51939495 \h 17Client Notifications PAGEREF _Toc51939496 \h 19Browser Certifications and Supported Configurations PAGEREF _Toc51939497 \h 19Monthly Browser Certifications and Supported Configurations PAGEREF _Toc51939498 \h 19Subprocessors PAGEREF _Toc51939499 \h 19SAP Concur Non-Affiliated Subprocessors PAGEREF _Toc51939500 \h 19Additional Release Notes and Other Technical Documentation PAGEREF _Toc51939501 \h 20Online Help – Admins PAGEREF _Toc51939502 \h 20SAP Concur Support Portal – Selected Users PAGEREF _Toc51939503 \h 21Legal DisclaimerThe 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.Release NotesFlightAmerican Airlines Fare ChangesProfStan? ? EditionOn: 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)XXOther: Refer to the release note belowDoes not apply to this editionSource / Solution SuggestionGDSAll GDSDirect ConnectSolution IDOtherXEMEA Data Center Scan impactXNorth America Data Center UI impactChina Data Center File finishing impactAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherOverviewEffective September 1, 2020, American Airlines has made a change to how fare classes are utilized, specifically related to B class fares. Traditionally, B class was reserved for the basic economy fares; after this change, B class can now represent non-Basic economy fares as well.There is no expected impact in Concur Travel as a result of this change. The change affected by American Airlines is generally managed in the GDS; Concur Travel relies more on the brand assignment for each fare that is provided by the GDS instead of the fare class. Concur Travel still relies on fare class assignment information for the flex faring display and for cabin designation, but neither area is affected by these changes. Specifically, American Airlines is not a flex faring airline, and the fare class changes do not change cabin designation. Given the current environment of low travel, this is a good opportunity for travel administrators to evaluate any View More Fares configurations or rule settings that may have relied on fare classes/booking codes, which are no longer necessary.Delta Air Lines and GDS Seat AssignmentsProfStan? ? EditionOn: 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)XXOther: Refer to the release note belowDoes not apply to this editionSource / Solution SuggestionGDSAll GDSDirect ConnectSolution IDOtherXEMEA Data Center Scan impactXNorth America Data Center UI impactChina Data Center File finishing impactAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherOverviewDelta Air Lines has made some changes in their internal systems to follow social distancing guidelines by “dynamically” blocking center seats between individual travelers. To support blocking seats in the GDSs effectively, the generic seat request function needed to be disabled. Specifically, the generic aisle/window seat request made by Concur Travel during the initial booking no longer functions for any GDS. These changes do not impact dedicated seat requests available at the end of the booking workflow, where the user may still choose a specific seat successfully.The generic seat request functionality is expected to remain disabled through Jan 6, 2021 as part of Delta’s dynamic seat blocking policy; customers should monitor release notes for additional updates as they become available.Southwest in SabreProfStan? ? EditionOn: 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)XXOther: Refer to the release note belowDoes not apply to this editionSource / Solution SuggestionGDSSabre GDSDirect ConnectSolution IDOtherXEMEA Data Center Scan impactXNorth America Data Center UI impactChina Data Center File finishing impactAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherOverviewAs reported by the press in July, Southwest will no longer participate in the Basic Booking Request (BBR) distribution model with Sabre at the end of 2020. Concur Travel will continue to display Southwest schedules for Sabre after December 31, 2020. Reservations made for January travel and beyond, however, return an unconfirmed (UC) status. To ensure uninterrupted access to Southwest content via Concur Travel, customers may need to consider alternative content strategies for Southwest.The Southwest Direct Connect remains available for use in Concur Travel today. While the hope is that Sabre and Southwest reach a new arrangement that will continue to allow Southwest content to be available in Sabre, Concur Travel currently supports Southwest content via Travelport (Apollo, Worldspan and Galileo). It is expected that this content will be supported in Amadeus, once available. Southwest Ticket Credit Expiry Date UpdateProfStan? ? EditionXXOn: 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 belowDoes not apply to this editionSource / Solution SuggestionGDSDirect ConnectSouthwestSolution IDOtherXEMEA Data Center Scan impactXNorth America Data Center UI impactChina Data Center File finishing impactAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherOverviewBecause of the COVID-19 epidemic, Southwest Airlines has extended the validity of the unused ticket credits. Concur Travel follows these changes and ensures that the travelers do not lose their ticket credits. In September 2020, the expiry date of all impacted Southwest ticket credits stored in Concur Travel was updated to ensure that the ticket credit expiry dates reflect to what was communicated by the airline.For more information, refer to for Professional and Standard TravelThis feature is enabled by default. There are no configuration steps.ProfileTravel Profile 2.0 API, Active Arrangers OnlyProfStan? ? EditionOn: 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)XXOther: Refer to the release note belowDoes not apply to this editionSource / Solution SuggestionGDSDirect ConnectSolution IDOtherXEMEA Data Center Scan impactXNorth America Data Center UI impactChina Data Center File finishing impactAll data centersXProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherOverviewPreviously, when using the Travel Profile 2.0 API to retrieve a user’s Travel Arranger, both active and inactive Arrangers were returned for that user. With this change, the Travel Profile 2.0 API now returns only active Travel Arrangers.For more information, refer to the SAP Concur Developer Center, Travel Profile Resource. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.User/Customer BenefitBy returning only the minimum amount of data required to arrange travel, SAP?Concur solutions can reduce the amount of data exposed online. Configuration for Professional and Standard TravelThis feature is enabled by default. There are no configuration steps.Miscellaneous**Ongoing** Deprecation of Director SAML Service and Migration to SAML v2Information First PublishedInformation Last ModifiedFeature Target Release DateJuly 10, 2020--July – December 2020Any changes since the previous monthly release are highlighted in yellow in this release note.ProfStan EditionOn: 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)XXOther: Refer to the release note belowDoes not apply to this editionSource / Solution SuggestionGDSDirect ConnectSolution IDOtherEMEA Data Center Scan impactNorth America Data Center UI impactChina Data Center File finishing impactXAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherThese changes are part of our continued commitment to maintaining secure authentication.OverviewSupport for the Director SAML service is being deprecated. Travel Management Companies (TMCs) and SAP Concur personnel will soon begin assisting customers who currently use Director SAML to migrate to SAP Concur SAML v2 SSO (SAML v2). Clients currently using Director SAML are encouraged to migrate to SAML V2 as soon as possible.Deprecation of support for the Director SAML service is dependent on the following requirements:SAP Concur technicians and TMCs assist existing SAP Concur clients to migrate from the Director SAML service to SAML V2.All clients that currently rely on the Director SAML service have migrated from Director SAML to SAML V2.Migration from Director SAML to SAML V2 requires the following general steps:The client identifies an admin to act as the SSO admin and assigns the proper permission/role. The SSO admin coordinates with their SAP Concur technician to obtain the SAP Concur SP metadata. The SSO admin configures the SSO settings at the IdP based on information from SP metadata. The SSO admin retrieves IdP metadata from the IdP and delivers the metadata to the SAP Concur technician. The SSO admin adds a few testing users and tests the new SSO connection. With successful testing, the company rolls out SSO to their SAP Concur users. For more detailed information about migrating to SAML v2, refer to the SSO Service: Overview Guide and the Shared: SSO Management Setup Guide.User/Customer BenefitThis change provides better security and improved support for users logging in to SAP Concur products and services.Configuration for Professional and Standard TravelMigration for TMCsTMCs will be significantly impacted by this change and should begin testing now to prepare for migration to SAML V2.TMCs must set up SAML v2 instead of Director SAML for their new clients. Setting up SAML v2 now allows more time for TMCs to test the new configuration and train internal staff to assist clients.To prepare for the deprecation of Director SAML:TMCs must support SAML 2.0 compliant SSO. TMCs must contract for, or develop, their SAML 2.0-compliant solution. TMCs must have an Identity Provider (IdP).Once support for SAML 2.0-compliant SSO is established, 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.Migration for Legacy Director SAML ClientsClients should begin testing SAML v2 immediately to prepare for migration.To prepare for the deprecation of Director SAML:Clients must have an Identity Provider (IdP) or a custom SAML 2.0-compliant solution.Clients must coordinate with an SAP Concur technician to complete migration to SAML v2.For more information, refer to the HYPERLINK "" SSO Service: Overview Guide and the Shared: SSO Management Setup Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.**Ongoing** Deprecation of HMAC Initiates Migration to SSO Self-ServiceInformation First PublishedInformation Last ModifiedFeature Target Release DateJuly 12, 2019July 17, 2020Phase I: July 2020Phase II: July 2021Any changes since the previous monthly release are highlighted in yellow in this release note.ProfStan EditionOn: 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)XXOther: Refer to the release note belowDoes not apply to this editionSource / Solution SuggestionGDSDirect ConnectSolution IDOtherEMEA Data Center Scan impactNorth America Data Center UI impactChina Data Center File finishing impactXAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherThese changes are part of our continued commitment to maintaining secure authentication.OverviewSAP Concur support for Hash-Based Message Authentication Code (HMAC) is being deprecated. Travel Management Companies (TMCs) and SAP Concur personnel are currently assisting customers who use HMAC to migrate to SAP Concur SAML v2 SSO (SAML v2). In Q3 of 2020, SAP Concur plans to provide a self-service tool that will enable client admins to setup their SAML v2 connections without involving an SAP Concur support representative.SAML v2 supports the use of multiple identity providers (IdPs).The HMAC deprecation includes two phases:Phase I:Clients must have an identity provider (IdP) or a custom SAML 2.0-compliant solution.Clients begin testing authentication using SAML v2. TMCs prepare to onboard new SAP Concur clients to SAML v2.Once the SSO self-service 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 to SAML v2.Existing clients using HMAC must migrate to SAML v2.Phase II:TMCs have migrated all existing SAP Concur clients from the HMAC service to SAML v2.The HMAC service is deprecated. Phase II is targeted to end mid-year in 2021.User/Customer BenefitThis change provides better security and improved support for users logging in to SAP Concur products and services.Migration for TMCsTMCs will be significantly impacted and should begin testing now to prepare for migration to SAML v2.TMCs must set up SAML v2 instead of HMAC for their new clients. Setting up SAML v2 now allows more time for TMCs to test SAML v2 and to train internal staff to assist clients.To prepare for Phase I of the HMAC deprecation:TMCs must support SAML 2.0 compliant SSO. TMCs must contract for or develop their SAML 2.0 compliant solution. TMCs must have an Identity Provider (IdP).Once support for SAML 2.0 compliant SSO is established, 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.Migration for Legacy HMAC ClientsClients should begin testing SAML v2 immediately to prepare for migration.To prepare for Phase I of the HMAC deprecation:Clients must have an Identity Provider (IdP) or a custom SAML 2.0 compliant solution.Clients can coordinate with SAP Concur support now to complete migration to SAML v2.When it is released, clients can configure the SSO self-service tool. The self-service tool is targeted for release in Q3 of 2020.For more information, refer to Authentication | **Planned Changes** Single Sign-On (SSO) Self-Service Option in the Shared Planned Changes release notes and to the SSO Service: Overview Guide and the Shared: SSO Management Setup Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.**Ongoing** SAP Concur Legacy File Move MigrationInformation First PublishedInformation Last ModifiedFeature Target Release DateMarch 6, 2020--Ongoing in 2020Any changes since the previous monthly release are highlighted in yellow in this release note.ProfStan EditionOn: 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)XXOther: Refer to the release note belowDoes not apply to this editionSource / Solution SuggestionGDSDirect ConnectSolution IDOtherEMEA Data Center Scan impactNorth America Data Center UI impactChina Data Center File finishing impactXAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherOverviewThis release note is intended for the technical staff responsible for file migrations 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.User/Customer BenefitThese changes provide greater security and efficiency for file transfers.Configuration for Professional and Standard TravelIf 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.Planned ChangesThe 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.Flight**Planned Changes** Next Generation AA AirPass ProgramInformation First PublishedInformation Last ModifiedFeature Target Release DateAugust 2020September 20204th quarter of 2020Any changes since the previous monthly release are highlighted in yellow in this release note.ProfStan? ? EditionOn: 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)XAvailable 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 belowXDoes not apply to this editionSource / Solution SuggestionGDSSabre onlyDirect ConnectSolution IDOtherXEMEA Data Center XScan impactXNorth America Data Center XUI impactChina Data Center File finishing impactAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsAmerican Airlines AirPass Travel Service GuideFact SheetsAdmin GuidesOtherOverviewFor companies that participate in the American Airlines AirPass program, Concur Travel will soon have the ability to support American Airlines’ next generation AirPass program. This program allows travelers to purchase unrestricted airfares at a pre-paid fixed rate. AirPass utilizes full-fare inventory, offering last-seat availability and flexibility, and is tied to a traveler's AAdvantage membership number. The following options will be made available in Concur Travel:AAnytime?: Members who make their travel arrangements at the last minute can enjoy last-seat availability by booking in unrestricted First (F), Business (J), or Coach (Y); one-way or round-trip without change fees.Instant Upgrade Fares (UP Fare): If an UP fare is available in the market, it can be booked using AirPass. All fare rules must still be followed.AA AirPass travel is valid on flights marketed by American Airlines. Additional details will be added to this release note as they become available. Feedback about the new feature or its limitations should be directed to your Concur Travel representative to ensure further consideration.For more information on the AA AirPass program, visit the American Airlines AirPass website. Customer BenefitThere are several differences between the new and legacy AirPass programs, but these differences are generally operational in nature. These changes allow Concur Travel to offer a more streamlined booking and fulfillment experience for AirPass fares. The new AirPass program will:use GDS filed fares, which incorporate the burn rates that traditionally required special faring logic in Concur Traveluse traditional GDS ticketing processes, instead of requiring ticketing by American Airlines directlyrequire the use of a dedicated UATP card for ticket fulfillmentFor additional detail on the legacy AirPass program, refer to the American Airlines AirPass Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes. The guide also contains additional links to American Airlines sites which provide more information about the program. What the User SeesSearch ResultsAirPass results will be returned if the user has been assigned access and they have an American Airlines loyalty number in their Concur Travel profile. AirPass fares will be denoted by the AirPass logo and, since these fares will be filed in GDS like other fares, they will no longer “share” a fare button with a non-AirPass fare. When searching in a market where AirPass fares are applicable, users will see an AirPass indicator on the collapsed view of a flight option. Upon clicking the View Fares button, the standard branded fares are displayed, as well as the AirPass fares. A tooltip will be available to help new AirPass users understand when AirPass fares should be used for their business travel.New DisplayLegacy DisplayKnown LimitationsThe following table describes the limitations for the new AirPass functionality in Concur Travel. Information regarding whether the limitation exists in either or both features is provided for clarity.DescriptionLegacy Feature Limitation?New Feature Limitation?Supported for Sabre GDS onlyYesYesNot supported with third-party meeting integrationYesYesPlanAAhead? fares (H class, 7-day advance purchase) not supportedNoYesTransmission of the UATP card will not be supported. Initial agency fulfillment partner feedback has indicated that this payment method needs to be managed by the agency to ensure non-AirPass forms of payment are still present for car and hotel reservations which cannot be charged to the UATP card.N/AYesProfile**Planned Changes** Retiring Legacy Travel Profile?1.0 / Profile EndpointInformation First PublishedInformation Last ModifiedFeature Target Release DateSeptember 2020-December 2020Any changes since the previous monthly release are highlighted in yellow in this release note.ProfStan? ? EditionOn: 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)XXOther: Refer to the release note belowDoes not apply to this editionSource / Solution SuggestionGDSDirect ConnectSolution IDOtherXEMEA Data Center Scan impactXNorth America Data Center UI impactChina Data Center File finishing impactAll data centersXProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherOverviewThe current supported version of the Travel Profile API is version 2.0. However, there are still clients and partners who continue to call the Travel Profile 1.0/Profile endpoint to get user profiles. This old endpoint will be fully deprecated with the December 2020 release; users must switch to Travel Profile 2.0 API before this date.The Travel Profile 1.0/Loyalty endpoint will continue to operate for partners using it to read or write frequent flier and other loyalty program numbers. For more information on Travel Profile 1.0/Loyalty, refer to specific SAP?Concur Developer Center documentation at more information on Travel Profile 2.0, refer to specific SAP Concur Developer Center documentation at User/Customer BenefitBy reducing the number of supported mechanisms for exchanging profile data, SAP?Concur solutions is able to focus on providing better security, ease-of-use, and additional functionality for those we support.Configuration for Professional and Standard TravelThis feature is enabled by default. There are no configuration steps.Client NotificationsBrowser Certifications and Supported ConfigurationsMonthly Browser Certifications and Supported ConfigurationsThe SAP Concur Release Notes – Monthly Browser Certifications document lists current and planned browser certifications. The document is available with the other SAP Concur monthly release notes.The Concur Travel & Expense Supported Configurations – Client Version guide is available with the setup guides, user guides, and other technical documentation.For information about accessing all release notes, browser certifications, setup guides, user guides, other technical documentation, and supported configurations, refer to the Additional Release Notes and Other Technical Documentation section in this document.SubprocessorsSAP Concur Non-Affiliated SubprocessorsThe list of non-affiliated subprocessors is available here: SAP Concur list of SubprocessorsIf you have questions or comments, please reach out to: Privacy-Request@ Additional Release Notes and Other Technical DocumentationOnline Help – AdminsAny user with any "admin" role can access release notes, setup guides, user guides, admin summaries, monthly browser certifications, supported configurations, and other resources via online Help.SAP Concur Support Portal – Selected UsersAccess release notes, webinars, and other technical documentation on the SAP Concur support portal.If you have the proper permissions, the Contact Support appears on the Help menu. Click to access the SAP Concur support portal, then click Resources. Click Release/Tech Info for release notes, technical documents, etc. Click Webinars for recorded and live webinars.? 2020 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or 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’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or 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. 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. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download