Travel: November 2020 Release Notes - Concur Training



SAP Concur Release NotesConcur TravelConcur Professional/Premium and Concur StandardMonthAudienceRelease Date: November 14, 2020Update #1: Friday, November 13, 4:00 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 _Toc56175275 \h 1Authorized Support Contacts PAGEREF _Toc56175276 \h 1Online Scheduling for SAP Concur Support PAGEREF _Toc56175277 \h 1Hotel PAGEREF _Toc56175278 \h 4Amadeus Hotel Passive Segment Changes PAGEREF _Toc56175279 \h 4Custom Hotel Sourcing – Provider Controlled Sort (Rate Level) PAGEREF _Toc56175280 \h 5Profile PAGEREF _Toc56175281 \h 7Canadian Personal Protection Program Number in CTE PAGEREF _Toc56175282 \h 7Cell Phone Number Validation in Profile Page UI PAGEREF _Toc56175283 \h 9Miscellaneous PAGEREF _Toc56175284 \h 12End of Support for Insecure Protocols and Ciphers in F5 Client SSL Profiles for VIPs PAGEREF _Toc56175285 \h 12Malicious Domains Alert PAGEREF _Toc56175286 \h 13Single Sign-On (SSO) Self-Service Option PAGEREF _Toc56175287 \h 15Support for Two SSH Transfer Ciphers Removed from File Transfer for Customers and Vendors PAGEREF _Toc56175288 \h 19**Ongoing** Deprecation of Director SAML Service and Migration to SAML v2 PAGEREF _Toc56175289 \h 21**Ongoing** Deprecation of HMAC Initiates Migration to SSO Self-Service PAGEREF _Toc56175290 \h 23**Ongoing** SAP Concur Legacy File Move Migration PAGEREF _Toc56175291 \h 26UI Label Enhancements - Updating Country and Countries Labels PAGEREF _Toc56175292 \h 27Planned Changes PAGEREF _Toc56175293 \h 29Flight PAGEREF _Toc56175294 \h 29**Planned?Changes** AirPlus A.I.D.A. Feature Retirement in Concur Travel PAGEREF _Toc56175295 \h 29**Planned Changes** CIBT – Retirement of Legacy Integration PAGEREF _Toc56175296 \h 31**Planned Changes** Next Generation AA AirPass Program PAGEREF _Toc56175297 \h 36Profile PAGEREF _Toc56175298 \h 47**Planned Changes** Retiring Legacy Travel Profile?1.0 API / Profile Endpoint PAGEREF _Toc56175299 \h 47**Planned Changes** Travel Config Parameter in Travel Profile 2.0 API PAGEREF _Toc56175300 \h 48Client Notifications PAGEREF _Toc56175301 \h 50Browser Certifications and Supported Configurations PAGEREF _Toc56175302 \h 50Monthly Browser Certifications and Supported Configurations PAGEREF _Toc56175303 \h 50Subprocessors PAGEREF _Toc56175304 \h 50SAP Concur Non-Affiliated Subprocessors PAGEREF _Toc56175305 \h 50Additional Release Notes and Other Technical Documentation PAGEREF _Toc56175306 \h 51Online Help – Admins PAGEREF _Toc56175307 \h 51SAP Concur Support Portal – Selected Users PAGEREF _Toc56175308 \h 52Legal 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 NotesAuthorized Support Contacts Online Scheduling for SAP Concur SupportProfStan 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 GuidesOtherOverviewSAP Concur Support has implemented an online scheduling feature that allows Authorized Support Contacts (ASCs) to schedule a meeting with a Support Engineer. User/Customer BenefitOnline scheduling makes it easier for Authorized Support Contacts (ASCs) to schedule a meeting with an SAP Concur Support Engineer.What the ASCs SeesASCs will see a new scheduling link option in their case update notification emails.An ASC can click on the link and schedule a meeting with a Support Engineer. The scheduling page will show the availability of a Support Engineer and allow the ASC to select a date and time.Configuration for Professional and Standard TravelThe feature is automatically available; there are no configuration or activation steps.For more information, refer to the Online Schedule for SAP Concur Support fact sheet. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.HotelAmadeus Hotel Passive Segment 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 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 SheetsPassive_Segments_FSAdmin GuidesOtherOverviewWith the November release, SAP Concur solutions will modify the template it uses to create passive segments in Amadeus for hotels. Consistent with existing practice, we will continue to create passive segments for hotels. However, after the November release, we will remove the Credit Card Guarantee field from the passive segments. By doing so, we will ensure that Form of Payment (credit card) information is not transmitted. User/Customer BenefitSAP Concur solutions is taking this step to avoid any possibility of compromising the security of PCI payment card information.Configuration for Professional and Standard TravelThis feature is enabled by default. There are no configuration steps.Custom Hotel Sourcing – Provider Controlled Sort (Rate Level)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 belowDoes not apply to this editionSource / Solution SuggestionGDSDirect ConnectAll CHS Direct ConnectSolution IDOtherXEMEA Data Center Scan impactXNorth America Data Center XUI impactChina Data Center File finishing impactAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherOverviewWith this update, we have allowed Custom Hotel Sourcing Providers to override the sort order for rates for Desktop users. This feature is not available to Mobile users.User/Customer BenefitCustomers will have the benefit of displaying rates in the order specified by the providers who are participating in the Custom Hotel Sourcing program.What the User SeesOn the Hotel search results page, when users select a hotel property, they will see the available rates for that hotel property. Users will have the ability to view rates in the order specified by the Custom Hotel Sourcing vendor partners, instead of sorting from low to high. The price displayed next to the hotel name is the lead price. The lead price will be taken into consideration for the display of property level sorting, including Price sort. e.g. Price – Low to High. Configuration for Professional TravelBy agreement between SAP Concur solutions, the client, and the Custom Hotel Sourcing provider, Concur Travel will enable the provider to control the sort order of hotel search results and rates.ProfileCanadian Personal Protection Program Number in CTE ProfStan? ? 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 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 GuidesOtherOverviewOn November 5, 2020, in support of the Canadian Passenger Protect Program (PPP) mandate, Sabre is making enhancements to allow two DOCO/R SSRs per passenger, one for a U.S. Redress Number and one for a Canadian Travel Number. Prior to this date, only one DOCO/R SSR was retained per?passenger.?A Canadian Travel Number will begin with the letters “CAN”. Any DOCO/R that is entered with a document number starting?with characters other than “CAN” will be assumed to be a U.S. Redress Number.?At this time, no other countries use DOCO/R.?CTE SupportA user can only have one number at a time within their Concur Travel profile, either a USA Redress Number OR a Canadian Travel Number. Within CTE, travelers should enter their Canadian Travel Number into the Redress Number field of the TSA Secure Flight section of their Profile UI page. A Canadian Travel Number, when entered into Redress Number field, will be written into the DOCO/R SSR in the PNR for all GDSs, not just Sabre. The Redress DOCO is always handled in the same manner across all GDS’s. The Amadeus and Travelport profile templates can be setup to handle CA PPP in a similar manner.Clients or TMCs should use existing communication options to let users know that the Redress Field is the correct field for the Canadian Travel Number. In the future, SAP Concur solutions will expand the Profile UI to include a dedicated field for the Canadian Travel Number, however, there is no targeted date for this change.For more information on the Passenger Protect Program, please visit: BenefitThis enhancement allows CTE to support travelers using a Canadian Traveler Number.What the User SeesConfiguration for Professional and Standard TravelThis feature is enabled by default. There are no configuration steps.Cell Phone Number Validation in Profile Page UI ProfStan? ? 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 ConnectSolution IDOtherEMEA Data Center Scan impactNorth America Data Center XUI impactChina Data Center File finishing impactXAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsFact SheetsAdmin GuidesOtherOverviewPreviously, when users added or updated their mobile phone numbers on the User Profile page, they may have seen different entry validations, depending on how their page was configured. In the Mobile Phone Number field of the Concur Mobile Devices section, they may have seen strict validation rules applied where only dashes, spaces and digits were allowed. In the Mobile Phone field of the Contact Information section, however, no validation rules were applied (any character was allowed). This sometimes resulted in duplicate entries and/or other data-related issues when an attempt was made to remove or edit the user’s mobile number.Strict Validation of Mobile Number:Any Character Allowed in Mobile Number:With this change, SAP Concur solutions applies consistent validations to the Mobile Phone field of the Concur Mobile Devices section and the Mobile Phone field of the Contact Information section, limiting the allowed characters to dashes (-), spaces, and digits. This reduces the likelihood of duplicate entries and provides a consistent user experience. This modification does NOT affect other phone number-related fields, such as Home Phone, Work Phone etc. User/Customer BenefitThis enhancement ensures consistent UI behavior and fewer bugs associated with mobile phone numbers.What the User SeesWith the November release, users who have made an entry in the Mobile Phone field of the Contact Information section may see an error when they try to save their profile information. This occurs if their new or existing mobile phone number includes characters other than dashes, spaces and digits. Users will need to correct their mobile phone entry and click Save.In the Concur Mobile Devices section, there is no change in behavior.Configuration for Professional and Standard TravelThis feature is enabled by default. There are no configuration steps.MiscellaneousEnd of Support for Insecure Protocols and Ciphers in F5 Client SSL Profiles for VIPs 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 the SAP Concur continued commitment to maintaining secure authentication.OverviewIn early October, the SAP Concur networking team noted that their configuration of the Content Delivery System had been blocking the protocols in the list that follows for some time.As such, the notice to customers that we would be making a change to our F5 Client SSL profile was superfluous, as those aspects of the existing profile were not actually available. SAP Concur did make changes to the F5 Client SSL profile on October 7 as well, in the interest of maintaining a strong security profile.This means that there was no new effect for customers, as the following protocols had already previously been blocked:SSL v2SSL v3TLS v1.0TLS v1.13DES cipher suiteUser/Customer BenefitThis update provides ongoing security for our products and services.Configuration for Professional and Standard TravelThere are no configuration or activation steps.Malicious Domains AlertProfStan 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 GuidesOtherOverviewPlease refer to the following table for a list of potential malicious domains. This list is not exhaustive and is meant as an initial warning about the existence of possible fraudulent sites that use some false derivative of the SAP Concur solutions brand within the domain name.Malicious concur.concur.concur.concur.concur.concur.concur.isconcur.concur.concur.concur.techconcur.concur.concur.concur.concur.concur.skconcur.concur.concur.storeconcur.bzconcur.concur.azconcur.What Should Customers Do?Customers should avoid these domains in the context of working with SAP Concur solutions. While some domains may be registered, it is recommended to err on the side of caution.User/Customer BenefitThis alert provides ongoing security for our products and services.Configuration for Professional and Standard TravelThere are no configuration or activation steps.For more information about web domains, refer to the Concur Travel & Expense Supported Configurations document. To locate, refer to the Additional Release Notes and Other Technical Documentation section in these release notes.Single Sign-On (SSO) Self-Service OptionProfStan 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 the SAP Concur continued commitment to maintaining secure authentication.OverviewWith the November release, SAP Concur is adding a Single Sign-On (SSO) self-service tool to SAP Concur products. This new tool enables clients to set up SSO for their organization without assistance from SAP Concur support. SSO is currently supported for Concur Expense, Concur Invoice, Concur Request, and Concur Travel.SSO enables users to access multiple applications using one set of login credentials. Currently, SAP Concur has two methods for signing in: Username and passwordSSO with Identity Provider (IdP) credentials, such as a user's login credentials for their organizationThe new SSO self-service tool will eventually replace the existing SSO configuration process, enabling clients to implement SSO at their organization. The existing SSO configuration process and the new SSO Self-Service tool will both be available until everyone has migrated to the new SSO Self-Service tool.Currently, SSO can be configured using the Security Keys page.The new SSO self-service tool will include the following features:A self-service option for setting up SSO at your organization; this new feature is automatically available to all clientsThe new SAP Concur SAML v2 SSO (SAML v2) service which complies with SAML 2.0 and is a current industry standardEncrypted SAML assertion to address privacy and security concernsEnforcement of SSO at the company level (the ability to select SSO as optional is also available)The ability to upload multiple Identity Provider (IdP) metadataThe ability to download SAP Concur Service Provider metadataSupported IdPs include any IdP that can send SAP Concur standard SAML 2.0 SAML assertions, such as: ADFS, Azure AD, Okta, Ping, G Suite, Sitemaster, Centrify, OneLogin, and VMWare Workplace One.User/Customer BenefitThis feature will provide new SAP Concur clients with a self-service option for setting up SSO. It will also provide an option for existing SSO clients who must eventually migrate to the new SAML v2 service to manage SSO for their users.Important – Migration for Legacy SSO CustomersLegacy SSO clients will be able to use the SSO self-service tool to migrate to the new SAML v2 service. Company admins will configure the feature and connect to the new SSO service on the Manage Single Sign-On page.The new SAML v2 service is independent of existing SSO services. Setting up a new SSO connection on SAML v2 does not interrupt existing SSO connections. Existing clients can remain legacy SSO clients while migrating to the new SAML v2 service.What the Admin SeesA user with the required permissions will see a new Authentication Admin list item when they click Administration > Company. The items in the Administration and Company lists vary depending on which SAP Concur products your company uses and which edition your company uses. Professional Edition ExampleStandard Edition ExampleTravel Only ExampleAfter clicking Authentication Admin, the Authentication Administration page appears.The new SSO self-service tool is accessed by clicking the Manage Single Sign-On link on the Authentication Admin page.Configuration for Professional and Standard TravelThis feature is automatically available to users with the required permissions.For more information about migrating to SAML v2, refer 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.Support for Two SSH Transfer Ciphers Removed from File Transfer for Customers and VendorsProfStan 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 technical staff responsible for file transmissions with SAP Concur solutions. For our customers and vendors participating in data exchange through various secure file transfer protocols, we are making changes that provide greater security for those file transfers. On October 13, 2020, support for the following SSH transfer ciphers was removed for file transfers:3des-cbcblowfish-cbcThis announcement pertains to the following file transfer DNS endpoints:st.st-eu.While these ciphers were not listed in our supported cipher list, they were not blocked until October 13, 2020. This change does not affect supported ciphers for PGP encryption.User/Customer BenefitThese changes provide greater security for file transfers.Configuration for Professional and Standard TravelThese changes occurred automatically. If you have been using one of the unsupported ciphers, you must move to a supported cipher in order to restore service.For a list of the supported SSH transfer ciphers, 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.**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. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.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, 2019November 13, 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). With the November release, targeted for November 14, SAP Concur will provide a Single Sign-On self-service option that enables 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 Single Sign-On self-service option 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.Configuration for Professional and Standard TravelMigration 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 choose to use the Single Sign-On self-service option. The Single Sign-On self-service option is targeted for release with the SAP Concur November release.For more information, refer to the Single Sign-On (SSO) Self-Service Option release note in this document and to the Shared: Single Sign-On Overview and the Shared: Single Sign-On 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.UI Label Enhancements - Updating Country and Countries LabelsProfStan? ? 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 GuidesOtherOverviewInstances of Country or Countries in the user interface are being updated to Country/Region and Countries/Regions, respectively.User/Customer BenefitThis change provides a better global user experience.What the User SeesExample: "Filter by Country" now reads "Filter by Country/Region":Configuration for Professional and Standard TravelThe feature is automatically available; there are no additional configuration or activation steps.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** AirPlus A.I.D.A. Feature Retirement in Concur TravelInformation?First Published?Information Last Modified?Feature Target Release Date?November 2020n/aFebruary 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 IDOtherXEMEA Data Center Scan impactXNorth America Data Center UI impactChina Data Center File finishing impactAll data centersProfile/Profile API/3rd Party XML Sync ImpactAffected DocumentationTSGsVirtual Payment – AirPlus AIDA, AirPlus Company Account, Form of PaymentFact SheetsAdmin GuidesTravel System AdminOtherOverviewWe are continually examining our solutions and portfolio to provide the most value to our customers. Due to low usage and changes coming to the program, we are retiring the current AirPlus A.I.D.A. feature in Concur Travel. Retirement of the AirPlus A.I.D.A. feature is currently targeted for the February 2021 release.Our vision for virtual payments includes working to expand the Conferma Pay integration to help make it easier to procure and issue virtual cards across Concur Travel programs. By investing in the Conferma Pay integration, we can support customers who want to increase adoption on virtual cards or even move to a complete virtual card program.Concur Travel will continue to support the AirPlus company ghost card and associated TAMARA credit card feed. These features are not affected by the retirement of A.I.D.A.For more information, refer to the AirPlus Travel Service Guide, Virtual Payment – AirPlus A.I.D.A. Travel Service Guide and Form of Payment Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.Retirement PlanWith the targeted February 2021 release, the AirPlus A.I.D.A. travel configuration setting will be disabled for all customers, removing the ability to create a virtual MasterCard (MC) when the AirPlus ghost card is not accepted by a supplier. No new virtual cards will be issued after the retirement date, but virtual MasterCards issued prior to this date will still be honored and valid.AirPlus A.I.D.A. AlternativesCustomers using the AirPlus A.I.D.A. program today should review their payment settings to determine how payments should be handled when the AirPlus ghost card is required and the supplier does not accept AirPlus. Customers that are interested in a virtual payment program should review the Virtual Payment – Conferma Pay TSG for how AirPlus virtual cards can still be supported for GDS hotel content.For more information, refer to the Virtual Payment – Conferma Pay Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.Configuration for Professional and Standard TravelThere are no configuration steps required for this feature retirement.**Planned Changes** CIBT – Retirement of Legacy Integration?Information?First Published?Information Last Modified?Feature Target Release Date?February 2020?October?13, 2020?April 2021?Any?changes since the previous monthly release?are highlighted?in yellow?in this release note.?ProfStan 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 ConnectCIBTSolution 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 GuidesOtherOverviewIn February 2020, SAP Concur and CIBT launched a new integration method through the Concur App Center, where the new CIBT app is available since then. The legacy integration method with CIBT is still supported during a transition period but SAP Concur will eventually retire the Legacy Batch File protocol integration method. The original retirement date announced with the release notes in February 2020 was November 2020. To give our customers and business partners more time for the transition and ease a little the impact that the Covid-19 pandemic may have had on some organizations, SAP Concur decided to extend the transition period. The retirement is planned for the second half of 2021. More details will be provided closer to the retirement date.If you are still using the legacy integration method, please refer to the CIBT Travel Service Guide for instructions on how to activate the integration via the App Center. Benefits of the new integration method: the CIBT service is available for additional countries. Travelers whose profiles are associated to a Concur Travel configuration based in Denmark, Finland, Ireland, Norway or Sweden can now benefit from CIBTs visa services.For more information on the new CIBT Integration and how to set it up, refer to the CIBT Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes. User/Customer BenefitCIBT has integrated with SAP Concur’s Itinerary API and Travel Profile API and has released an App Center Connector to facilitate the continuous, real-time flow of itineraries to better serve clients and travelers. CIBT will be able to support clients and travelers in more countries and with a more stable, scalable integration. The new integration method also reduces configuration effort for admin users in Concur Travel.What the User SeesThere is no visible indication to the traveler at the time of booking that the feature is enabled or if action is required. Concur Travel automatically engages with CIBT in the background to begin the traveler experience. As to end user experience, there are no changes compared to the old integration method. Samples of the emails received from CIBT after booking an international trip can be found in the CIBT Travel Service Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes. With the planned retirement of the legacy integration method, existing configuration settings on the Concur Travel admin UI will be removed. This includes: In the Professional Edition, on the Travel Configuration page the check box Send Profile/Travel Data to CIBT. In the Professional Edition, the Manage CIBT Configuration admin page.In the Standard Edition, the Visa / Passport Services tab on page/setup step Discounts and Travel Content.Configuration for Professional and Standard TravelTo apply for the new integration method via App Center:Go to the App Center and select the CIBT App.Click Connect.If the Connect button is not available, your user does not have Admin privileges in Concur Travel. Contact your company administrator for assistance.Review and opt-in to the following elements in the displayed overlay:Concur App Center End-User Terms & ConditionsShared InformationCompany Authorization to Link ServicesOpt-in is required only once. If you enabled other App Center partners previously and accepted the electronic Company Authorization to Link Services, you may not be required to opt-in again.Fill in the activation form in an overlay hosted by CIBT where CIBT will collect:Admin First Name, Last Name, & EmailCompany/Business NameCountryIf existing CIBT client, the CIBT account code for activationIf you would like to activate CIBT for multiple countries / Travel configurations in Concur, please use the “add another company entity” option towards the bottom of the activation form to add further countries.At submission, an email will be sent to ConcurClientConnect@. The information in the previous step is collected via the Activation Form and will be sent through email to CIBT.CIBT will activate the client in the CIBT database system for Visa Alert. Only for customers that used the legacy integration method so far: CIBT will turn this integration method off from their end in favor of the new integration via Concur’s App Center. **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 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. User/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 Travel.use traditional GDS ticketing processes, instead of requiring ticketing by American Airlines directly.require the use of a dedicated UATP card for ticket fulfillment.For additional details 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 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 displayed to help new AirPass users understand when AirPass fares should be used for their business travel.Policy ApplicationSince the new AirPass program uses its own filed fares, users can now see accurate policy violation indicators, as they relate to the AirPass fares. With the legacy AirPass program, since the AirPass fare was a Concur-calculated amount and shared a line in the fares display with a non-AirPass fare, the policy was only applied to the non-AirPass fare.Legacy Shopping DisplayNote the shared fare display. It is not clear that these are two separate fares (non-AirPass and AirPass) and policy violation indicators are in fact referring to the non-AirPass fares.Review and Reserve PageAn AirPass fare indicator is shown in the Review Price Summary section. The user can select a credit card at this point, but it is not intended for use in AirPass fare ticketing. Agency fulfillment partners must ticket AirPass fares using the UATP card issued to the customer for this purpose. The credit card selected here is intended for other non-AirPass charges, such as agency transaction fees or other incidentals.Itinerary ViewAll Itinerary view pages (Travel Details, Trip Confirmation, etc.) will denote AirPass flights with the AirPass icon.Configuration for Professional TravelUpdate Concur Travel ConfigurationTo configure for AirPass: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.In the Wizard Options section of the travel configuration page, locate the new AA AirPass Configuration section. Check the Enable New AA AirPass option and save changes.Quick Help is provided for the new section, as well as the setting itself.Add AirPass Code to Air Discount AdministrationTo add the AirPass code: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.In the Company-Specific Configuration section of the left menu, click Manage Corporate Discounts.Select the desired company and click Choose.Select the desired company travel configuration and click Choose.Add or edit a discount for American Airlines as shown below:Quick Help is provided for this setting as well.Assign User AccessTo book an American Airlines AirPass reservation, the user must first have an American Airlines loyalty program loaded into their profile and then be enabled to use AirPass. There are two ways for users to be assigned access to AirPass: Via the Import Data administrative tool: The user general information import template includes a Travel Preferences tab. On that tab there are three AAirPass columns. The Has AAirpass column can be used to assign AAirPass access to individual users.Although the AAirpass Start Date and AAirpass End Date columns are present on the import template, they are not supported for the new AirPass feature.Via User Administration: when viewing a user profile that is associated to a travel configuration that has AAirPass enabled, administrators will see an editable AAirPass field in the profile.Once access has been assigned, the user will see the customary AA AirPass indicator in their profile.Known 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/AYesPost-ticket changes (exchanges) are not supported. Traveler/arranger must cancel and rebook.YesYesProfile**Planned Changes** Retiring Legacy Travel Profile?1.0 API / 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 API/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 API/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 API/Loyalty, refer to specific SAP?Concur Developer Center documentation at more information on Travel Profile 2.0 API, 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.**Planned Changes** Travel Config Parameter in Travel Profile 2.0 API Information First PublishedInformation Last ModifiedFeature Target Release DateNovember 2020n/aDecember 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 GuidesOtherOverviewSAP Concur solutions is adding an optional parameter into the Travel Profile 2.0 (TP2.0) API / Get Summary endpoint that allows callers to retrieve users associated with one or more Travel Configurations. Before this change, TP2.0 API callers would retrieve all users associated with their App. With this change, TP2.0 API callers will be able to optionally provide one or more TravelConfig IDs as a parameter into their GET call to filter the user profiles to those in the associated TravelConfigs. An example call might look like this:GET /api/travelprofile/v2.0/summary?LastModifiedDate=2015-01-01T01:00:00&travelConfigs=100,200,3000For more information, please refer to the SAP Concur Developer Center, which will be updated to include this new, optional parameter in December. User/Customer BenefitThis enhancement will enable Travel Profile 2.0 callers to filter the set of user profiles to a smaller set, potentially reducing the amount of time, bandwidth, and resources need to sync profiles with CTE.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