Once the System Connection has been successfully configured, the first data integration to activate and run is Cost Object Replication. It is done first for two reasons:
- If the customer is going to use Employee Replication, the Cost Objects must exist before that process runs to ensure each user profile can be assigned to the proper Cost Object.
- If the customer is not going to use Cost Object Replication, the Cost Objects must exist before the first expense report to be transmitted via Financial Integration is created.
Customers can choose to integrate a variety of Cost Objects. Each Cost Object can be set up to run with different filters and on a different schedule.

Running Cost Object Replication will populate and maintain the items in the SAP Integration Hierarchy list. You can manually add test values to this list for testing the Concur UI, but those test values should be removed once Cost Object Replication is enabled.
Process
Now, let's take a moment to practice the process of setting up and running Cost Object Replication. SAP Concur will help the customer set up and run the integration, but they are responsible for ongoing use of the tools.











