Model Changes

With the August release, SAP Concur modified how employee information is filtered throughout the Cognos data model. Additional permissions were added to employee information in the data model to use both the BI Manager hierarchy filter and the Reporting hierarchy filter to filter employee information from the data model.

The modifications ensured clients could only view the employee information appropriate for the combination of their assigned Cognos user role, their assigned group(s) in the Reporting hierarchy and their BI Manager permissions, if applicable.

With the September release, we reverted the changes we made to the model filters in the August release, setting the filters back to their previous state where the data model uses only the BI Manager hierarchy to filter employee information from the model. This update was made on 13 September, 2019.

SAP Concur is committed to safeguarding employee information and ensuring only clients with the appropriate permissions can access employee information.

For more information about the Cognos user roles, the Reporting hierarchy and the BI Manager permissions, refer to the Analysis/Intelligence: Overview guide (English Only).

BACKGROUND INFORMATION

The changes to the data model in the August release had an unanticipated impact on all reports. The before and after states of how data is displayed in reports is as follows:

• Before the August change, if an employee changed organisational units in the company, the spend data associated with an employee remained with the associated organisational unit at the time the spend was incurred. For example, if an employee belonged to Department A and then moved to Department B, spend incurred while the employee was in department A remained visible to Department A. Any spend incurred once the employee moved to Department B was visible only to Department B.
• After the August filter change was implemented, when an employee changed departments, the spend associated with Department A was no longer visible to Department A, even though the data still existed in the database. Department B was able to see the spend associated with that department as long the employee was part of Department B, but once the employee changed departments, say to Department C, then spend associated with Department B, as well as Department A, was also no longer visible.

In effect, historical data spend was not visible in reports except for that data spend associated with the organisational unit to which the employee is currently assigned.

RERUNNING REPORTS

If you ran reports after the August release and before the 13 September, 2019 update, some of the reports may not have all the data in them due to the filter change. You may want to rerun any reports you ran during this period to ensure the most accuracy.

Other Changes

SAP Concur is in the process of enhancing the Standard Reports by Folder guide (English only). We are adding definitions of the report prompts and fields, and adding the expressions associated with the report fields for each report.

This is an ongoing project. Clients will see these guide updates as they become available.

EXAMPLES

Example of the new report prompt definition for the Itinerary Details report:

Record Locator: Used to search by the record locator assigned to the trip(s)

Example of the new field information for the Itinerary Details report:

This release note is intended for technical staff responsible for file transmissions with SAP Concur. For our customers and suppliers participating in data exchange through various secure file transfer protocols, SAP Concur is making changes that provide greater security for those file transfers.

SAP Concur will change the IP address for st-eu.concursolutions.com from 84.14.175.233 to 46.243.56.11 on 23 November, 2019 during the maintenance window in the region Europe, the Middle East and Africa (EMEA).

Clients whose file transfers protocols use the SAP Concur DNS endpoint (st-eu.concursolutions.com) to connect are not impacted by this change.

Clients who connect via IP address will need to connect to the SAP Concur DNS endpoint (st-eu.concursolutions.com) or the new IP address as of 23 November, 2019.

SAP Concur recommends connecting to DNS endpoint st-eu.concursolutions.com to avoid connection issues if the SAP Concur IP address changes.

This announcement pertains to the following file transfer DNS endpoint:

• st-eu.concursolutions.com

Business Purpose / Client Benefit: This change provides greater security for file transfers.

This feature is no longer targeted for the current release. This Release Note has been moved to the Shared Planned Changes Release Notes (English only).

This release note is intended for technical staff responsible for file transmissions with SAP Concur. For our customers and suppliers participating in data exchange through various secure file transfer protocols, SAP Concur made changes that provide greater security for those file transfers.

As of 8 AM PDT, 14 October, 2019, SAP Concur no longer supports the following unsecure SSH protocol algorithms/ciphers:

• (key exchange) diffie-hellman-group-exchange-sha1
• (encryption) aes128-cbc
• (encryption) aes192-cbc
• (encryption) aes256-cbc
• (message authentication code) hmac-md5
• (message authentication code) hmac-sha1-96
• (message authentication code) hmac-md5-96

This announcement pertains to the following file transfer DNS endpoints:

• st.concursolutions.com
• st-eu.concursolutions.com
• st-cge.concursolutions.com
• st-cge-dr.concursolutions.com
• vs.concursolutions.com
• vs.concurcdc.cn

If assistance is required, please contact SAP Concur support.

For more information, refer to the Shared: File Transfer for Customers and Vendors User Guide (English Only).

Business Purpose / Client Benefit: These changes provide greater security for file transfers.