PUBLIC

SAP Integration with Concur Solutions

Best Practice Document – System Copies and RFC
Destination

Proposal
TABLE OF CONTENTS

ABOUT THIS DOCUMENT/DISCLAIMER ....................................................................................................... 3

USE CASE 1 – COPY FROM PRODUCTION SYSTEM TO TEST:................................................................. 4

1. What should be done before copying a productive system? ................................................................. 4

2. What should be done in the new system copy? ...................................................................................... 4
3. What can happen if you just do a copy without taking care about Concur? ........................................ 5
4. Dump in class CL_CTE_FND_OAUTH_SECSTORE after System Copy ................................................ 6
USE CASE 2 – COPY PRODUCTION TO NEW PRODUCTION SYSTEM AND DELETE OLD
PRODUCTION SYSTEM .................................................................................................................................. 7

1. What should be done before copying a productive system? ................................................................. 7

2. What should you do in the old system? ................................................................................................... 7
3. Dump in class CL_CTE_FND_OAUTH_SECSTORE after System Copy ............................................... 7

www.sap.com/contactsap

© 2019 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.

The information contained herein may be changed without prior notice. 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 or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP 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, and they should not be relied upon in making purchasing decisions.

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. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/copyright for additional trademark information and notices.
ABOUT THIS DOCUMENT/DISCLAIMER

In this document you can find some useful information about settings you should review, check or adapt after
a system copy has been made.

DISCLAIMER: This document is designed to show a potential option how to ensure data consistency after a
system copy when using SAP Integration with SAP Concur Solutions. This is not a final solution. The contents
of this document, and SAP’s strategy and possible future developments, products, and/or platforms directions
and functionality are all subject to change and may be changed by SAP 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 assumes no responsibility for errors or omissions in this document, except if such damages were caused
by SAP’s intentional 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.

3
USE CASE 1 – COPY FROM PRODUCTION SYSTEM TO TEST:

Customers often copy their productive SAP systems to keep their test system landscape up to date or to do
special tests. They often do not know or are not aware that such system copies could heavily damage or
destroy their Concur integration in the productive SAP system.

Depending on the customer’s copy processes it can happen that RFC destination entries are copied as well.

A customer may find a working connection in CTE_SETUP of his newly copied SAP system although a new
connection hasn’t been created yet. An entry in CTE_SETUP can also exist without copying the RFC
destination (e.g. if CTE tables have been copied.)

1. What should be done before copying a productive system?

Keep in mind: please stop all automatic import jobs before creating a copy of your PROD system to avoid
importing productive data into a test system. You may reschedule them as soon as copied system is
maintained properly.

2. What should be done in the new system copy?

In your new system copy please proceed by applying the following steps:

1. If you have forgotten to stop the automatic batch jobs, you should do this in your system copy
immediately. To do this you can for example re-run the FIN Posting Wizard for the particular connection
and in the Automatic Import step, choose the “Manual Import” radio button.

2. Change LOGSYS entry (source system ID) in table T000

(most probably this is still containing the source system ID of your productive system). Replace this
value by the logical system ID of your test system. If you need to change logical system names in the
system that results from the copy, change the logical system names as described in SAP Notes 103228
and 544509.

3. Empty PARTNER_SYSTEM_DETAIL_ID in Table CTE_C_CONNECTION (not necessary if you have

installed SP12 on ECC or SP09 on S/4HANA onPremise)

4. Delete existing system connection in CTE_SETUP, after changing your LOGSYS entry

a. You may need to delete integration activities (e.g. cost objects, etc. first)

4
5. To proceed tests with your new system you can now create a new connection:

a. Run through the System Setup Wizard and maintain all data (incl. client credentials for all new
connections after SP09 ECC and SP06 S/4HANA on Premise)

b. Run through the Financial Posting Wizard and maintain the correct logical system in the Filter
Definition step (Relevance Filter)

c. If Payroll integration is in use: please also run through your Payroll Wizard and maintain the correct
logical system in the Filter Definition step (Relevance Filter)

3. What can happen if you just do a copy without taking care about Concur?

1. If you have not stopped the automatic batch jobs for the export and import your system will exchange
data with Concur.

In the worst-case productive expense reports are fetched and successfully posted by the wrong system.
Those will never arrive in the production system again and show up as successfully posted with the
corresponding Financial Document information from the copy system in the Concur audit trail. Most of the
times our customers are wondering about this Financial information, which can’t be found in the
productive SAP system. In the worst case the system copies have been deleted in the meanwhile and
there is no evidence of the Financial information at all anymore.

ACTION: immediately stop the automatic batch processing in the system copy

RESOLUTION: you must post the expense reports posted in the wrong Financial system manually in the
production system.

As an alternative you can ask your Employees to copy the affected expense reports in the Concur system
and resubmit them. Disadvantage: Duplicate Expense Reports exist in Concur.

5
2. If you just delete the Concur connection in the copied system without removing LOGSYS and/or
PARTNER_SYSTEMDETAIL_ID you most probably have removed the mapping service entries. As an
effect no expense report can be fetched in the production anymore.

RESOLUTION: recreate the system connection again in the copied system. After that you need also to
recreate the financial and payroll wizard data. Now you should start with the steps described under point
two “What should I do in the new system copy?” and finally you can delete the connection in the copied
system.

As an alternative do the following steps in your production system:

1) Transaction SE16: table CTE_C_CONNECTION - remove field content of field PARTNER
SYSTEM DETAIL ID (it looks like fe0a45da-5030-4a29-8e6f-5b77fbe23241)
2) Go through the system setup wizard with all valid credentials
3) Reset the filter value in the Financial Posting wizard

4. Dump in class CL_CTE_FND_OAUTH_SECSTORE after System Copy

It might occur that after a system copy an entry is missing in the table “RSECACHK” for the Concur (CTE)
application. In this case, please make sure that you add an entry in table "RSECACHK" analogous to the
one depicted below (the value of CHSUM will be different in your case):

6
USE CASE 2 – COPY PRODUCTION TO NEW PRODUCTION SYSTEM AND DELETE OLD
PRODUCTION SYSTEM

1. What should be done before copying a productive system?

Keep in mind: please stop all automatic import jobs before creating a copy of your PROD system to avoid
importing productive data into a test system. You may reschedule them as soon as copied system is
maintained properly.

2. What should you do in the old system?

In your old system please proceed by applying the following steps:

1. If you have forgotten to stop the automatic batch jobs. You should do this in your system copy
immediately. To do this you can for example re-run the FIN Posting Wizard for the particular connection
and in the Automatic Import step, choose the “Manual Import” radio button.

2. Empty PARTNER_SYSTEM_DETAIL_ID in Table CTE_C_CONNECTION (not necessary if you have

installed SP12 on ECC or SP09 on S/4HANA on Premise

3. Delete existing system connection in CTE_SETUP, after changing your LOGSYS entry

a. You may need to delete integration activities (e.g. cost objects, etc. first)

3. Dump in class CL_CTE_FND_OAUTH_SECSTORE after System Copy

It might occur that after a system copy an entry is missing in the table “RSECACHK” for the Concur (CTE)
application. In this case, please make sure that you add an entry in table "RSECACHK" analogous to the
one depicted below (the value of CHSUM will be different in your case):

7
8