Posted by Jess Spaull, SAP SuccessFactors Consultant at Hula Partners, now GP Strategies
Welcome back! In my final installment of this three part series, I will cover the options available for Exporting data from Employee Central (EC) for the purposes of data validation.
The time to complete data validation can often be misjudged as it is a high time and resource consuming process. While business teams will be involved in validating the data, using an automated approach can add efficiencies to this process including the ability to test 100% of the migrated data immediately after the first test migration. Data validation determines the integrity of the migrated data through a process of comparing the migrated records in the destination system to the source system and is a checkpoint to ensure the data migrated is complete and usable.
Once the process of migrating data into Employee Central is complete, data validation testing can begin. But how will you get the data out of Employee Central? There are many reporting options available within SuccessFactors Employee Central that will not be covered in this blog. Instead, I will list the various methods that have worked for me in the past:
Located in the Admin Center:
o Export Users – use this to export the User Data File (UDF) and confirm all employees in scope to be migrated exist in EC with the correct status, either active or inactive.
o Import and Export data – select ‘export data’ as the action and export the data from any generic or custom object. The output will provide a direct dump of live data from the database of the object selected. The output will be in CSV format. There is no customizing these reports.
Located in the Report Center:
o Ad hoc Reports – use this to build your own reports to export live data from any standard object, like job information, personal information etc. The reports are quick and easy to build with options to merge data from more than one data set and/or from different domains if desired. The output can be saved in multiple formats such CSV, Excel and more.
o Advanced Reporting – existing in the Online Report Designer (ORD), this reporting tool is available for all EC customers and needs to be activated in your stance before use. It is an ODS (Operational Data Store) database which allows you to build queries and reports with any EC object – standard, generic, foundation and custom MDF objects. It may take longer to set up the reports initially as ORD requires skill training and sometimes performance can be unpredictable and poor.
Located in the Integration Center:
o My Integrations – make use of SAP’s built-in templates available from the Integration Catalog or create or own and then deploy and monitor these simple file-based integrations to your third party system via the Integration Center. These outbound files can be manually executed or scheduled using a variety of different trigger, source and destination types using different formats. Ideal if you want to send outbound files to a secure server location via SFTP or web services like REST or SOAP.
Using the SF API or ODATA APIs to extract data using an external system:
o Some of the ETL tools mentioned in part 2 of this blog series used to import data into Employee Central can also be used to export data out of Employee Central, like SAP Data Services. An automated reconciliation framework can be built in parallel with your migration framework to provide high-level migration results in a timely manner.
o The ODATA API can be used to extract data directly into Microsoft Excel or Google Sheets, making exporting data even easier. More information on how to do this can be found here.
Data validation is important and cannot be overlooked. The tools and resources available to you will aid in determining the best ways to extract data from Employee Central for your project. Feel free to reach out to me at email@example.com with any questions.
To read the first two installments of this series, please click here.
Share with us on social!
Hula Partners is now part of GP Strategies. To learn more, see here.