Sr No

2
3
4

5
 Activities
Following SSL certificates are installed

DigiCert Global Root CA

GeoTrust RSA CA 2018

Middleware: If you opt to use middleware, enter the Middleware Host, Path Prefix, User and Password and/or SSL Certificate.
Connection to Concur cloud should use TLS (transport layer security) 1.2 or higher
Integration Add ons
CTE_FND 100
CTE_FIN 100
Integration set up - T code CTE_SETUP
Integration set up with Concur
RFC destination
Concur host (e.g. www.concursolutions.com)
Port details
Language details
Wizard - Cost objects (for exporting cost centers)
Wizard - Setting up the posting import (for posting import from Concur system)
POC system
Status Remarks

14/9- Installation done on premise. For AWS port needs to be opened. Kamal to
Yes follow up with Andrew
14/9- Installation done on premise. For AWS port needs to be opened. Kamal to
Yes follow up with Andrew
NA TGB will be using direct method and no middleware will be involved.
Yes 14/9 - Murali confirmed that TGBL uses TLS 1.2

Yes 14/9 - Add Ons added in both POC on premise and AWS system
Yes 14/9 - Add Ons added in both POC on premise and AWS system
 Role

SAP_CTE_BASE: Concur Integration Setup and Replication Monitor

SAP_CTE_FINANCE: Concur Financial Integration

 Usage

The purpose of this role is to prepare your SAP system for the integration with Concur and to monitor the data expor

With this role you are authorized to take care of the integration in the areas of financial posting and cost object expo

The Concur integration is available for the following SAP products:

SAP ECC 6.0 and higher

keep in mind that only uni-code system are supported.
Non-unicode system will receive UTF-8 errors during communication. A possible solution for customer having non
system could be to use function module SCP_REPLACE_STRANGE_CHARS for conversions.