Overview
If Employee Replication is intended to be used, it should be configured and implemented after Cost Object Replication is successfully configured and all applicable Cost Objects have been exported to SAP Concur. This will help to ensure the successful completion of the Employee Replication process.
Going forward, customers should be instructed to make sure that their Cost Object Replication schedule takes place prior to their Employee Replication schedule. This will ensure that any employee impacting changes to the Cost Object list occur prior to the Employee Replication updates.
For example, if Cost Object Replication is set to run every day at 7 p.m. local time, Employee Replication should be set to run every day after 7 p.m. local time, perhaps at 7:30 or 8 p.m.
Many customers opt not to implement Employee Replication. There are a variety of reasons for this, but the main ones are:
- Some customers may not use SAP as their HR system, therefore, SAP is not the best system of record to be used to maintain user data in SAP Concur.
- Employee Replication does not support any of the supplemental data imports available in the CSV import, such as credit card assignment imports (650 record) and setting Authorized Approver limits (700, 720, and 750 records). Furthermore, combining Employee Replication with the CSV import is not supported.
API Documentation
Employee Replication uses the User API provided by SAP Concur to create user profiles. The Get User Response Schema table lists the fields available for Employee Replication.
Select the LEARN MORE button to review the documentation.

Running Employee Replication will populate and maintain the customer's list of users in SAP Concur. As with all methods for automating user profile maintenance, customers are encouraged to choose only one method and stick to just that method going forward.
Note
Employee Replication is not supported in SAP S/4HANA Cloud.
Some Things to Remember
- Employee Replication creates and maintains user profiles within the SAP Concur system on a set schedule. All updates to employee data is done in the SAP system and those changes are pushed to SAP Concur.
- Be sure the customer knows that Employee Replication uses the combination of Employee ID and Login ID to determine if it should create a new user or update an existing user. Changing a user's Employee ID or Login ID in SAP can have a negative impact on the data in SAP Concur.
- Like all forms of automated user maintenance, customers should be informed that when using Employee Replication, manually creating and updating user profiles in SAP Concur is not recommended and should only be done with extreme caution.
Process
Now, let's take a moment to review the process of setting up and running Employee Replication. You will help the customer set up and run the integration, but they are responsible for the ongoing use of the tools.














