This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
These materials may not be reproduced in any format without the express written permission of ADP, LLC.
The ADP logo, ADP , and IN THE BUSINESS OF YOUR SUCCESS are registered trademarks of ADP, LLC. All other trademarks and service marks are the property of their respective owners.
Minimize distractions. Return promptly from breaks. Participate. Ask any question that comes to mind. Make mistakes. This is a safe environment. Put your phone on mute during the presentation.
This course has been designed to provide you with the knowledge and hands on experience required to be comfortable using the Importing Data for ADP Workforce Now®.
This course prepares you to update data in ADP Workforce Now® after your ADP Implementation team has completed the initial importing process (referred to as the data conversion process).
It describes the available methods for updating data, including importing in batch, focusing on employee and paydata.
Upon completion of this module, you will be able to:
Describe the importing process at a high level Identify the available data update methods Identify the types of data that can be imported Explain the purpose of a Baseline Report Describe how to validate imported data Describe how to send notifications when a data import is
During your implementation, the Data Conversion team worked with you to map your employee data to the Workforce Now database. During this process, they ensured that all Validation tables were updated either:
The Data Conversion/Implementation team uses the same process identified in the Data Import Process of this course. The same methodology is used for either an initial import, or updates to the data after the bulk of the data is set up.
There are several methods available for maintaining data in ADP Workforce Now®. The following table describes all of the data update methods, as well as how to access them in the system:
Use This Data Update Method: When You Need to: By Accessing:
Importing Upload multiple types of data with different values
Process > Utilities > Import
Mass changeEnter the same field value for a group of employees
Process > HR > Mass Change
Manual data entry Change information for one employee at a time
Data import is a process that loads data from a source file into your ADP Workforce Now database. Because it eliminates the need to enter data manually, importing provides an easy way to transfer large amounts of data from another source or to make multiple corrections.
Importing is useful when you need to upload multiple types of data with different values. If you need to update the same field value for a group of employees, the Mass Change feature is the more suitable option.
A baseline report is a snapshot of your data in its current state prior to the import. You can refer to this report to confirm that your data updated as expected. Running the baseline report represents the third stage of the data import process.
Depending on which type of information you are importing, you can run a standard report or create and run a custom report.
A baseline report is only required if you are updating existing records. It is not required if you are adding records.
Upon completion of this module, you will be able to:
Prepare the data import file Prepare employee import files Prepare paydata import files Identify the other types of import files Use the Import Reference Guides to help you prepare data
Preparing for data import involves determining the type of data that you need to import, deciding on the most appropriate data update method based on the volume of data to be imported, preparing the data import file, running the baseline report, and setting your import preferences if notification when the importing process is finished is required.
Some import files will require the Change Effective On field to be included in the data import file header. Effective dating means that ADP Workforce Now holds multiple records:
Historical
Current
Future
Refer to the Handout Manual for additional details.
Requirements differ depending on the type of data that you are importing.
Each import file consists of a header that specifies the data to be imported.
Headers for each data type differ depending on the importing task, and the data that is important to your organization.
The best practice for creating import files is to specify the header information in a Microsoft Excel spreadsheet, which is much easier to read than a comma-separated values (CSV) file in Notepad.
Once you are sure that the headers in the import file are correct, then save the file to CSV format.
Include all required fields Ensure that all field headings are correct Ensure that fields are in the correct sequence Ensure that all data values are valid Save the file using the correct filenaming convention Save the file in the correct format
To import employee data, users require Practitioner access to Workforce Now. You can use the employee import file to both change and delete employee data. You can use importing to update both current year, and year end data. The way you set up the employee import file determines whether current year or year-end data is imported.
When you import employee data, the requirements for the data import file vary depending on the following factors:
If the import is for new hires
If the import involves changes to existing employee data
If you are setting up new entries in the Validation Tables in Workforce Now, such as awards, memberships, license and certifications
You must include Position ID in order for the records to be properly indexed.
Note: If you are importing additional positions for employees, you must also include the Associate ID field.
Ensure that all field headings are correct
Each field heading must match the requirements specified in the Importing Employee Data guide.
Ensure that fields are in the correct sequence
Your employee data import file must use one of the following sequences:• Position ID must be the first field.• If required, Associate ID must be the first field, and
Position ID must be the second field.
All other fields you are importing may be listed to the right in any sequence.
Ensure that all data values are valid
Ensure that you enter and format the data correctly. For example, enter Social Security numbers as nine digits with or without dashes and without spaces.
Save the file using the correct filenaming convention
You may use almost any filenaming convention for employee data import files. Restrictions are listed in the Importing Employee Data guide.
Note: If you want to import records from multiple company codes within the same file or positions that are not associated with a company code, you must use the filenaming convention EMP____.CSV.
Save the file in the correct format Save the file as a CSV or TXT file.
Only Practitioners with the correct access permission to the paydata import function can import paydata. Access to importing paydata is controlled by your profile memberships and access permissions. These are set up for you by your company administrator. You can import both current year and year-end paydata.
You must include Position ID, Payment and Description. If Position ID is not included, then Company Code and File Number must be the first two fields. Additional fields are required and vary depending on the type of paydata you are importing. These requirements are specified in the Importing Paydata guide.
Ensure that all field headings are correct
Each field heading must match the requirements specified in the Importing Paydata guide.
Ensure that fields are in the correct sequence
Your paydata import file must use the following sequence:
Position ID
Note: If Position ID is not used, then Co Code, Description, File # and the other fields.
Co Code must be the first field - not required if Position ID is used.
Description must be the second field - not required if Position ID is used.
File # must be the third field.
The other fields you are importing are listed to the right.
Ensure that all data values are valid
Ensure that you enter and format the data correctly. For example, enter file numbers with no more than nine digits.
Save the file using the correct filenaming convention
Use the filenaming convention EPIccccAA.CSV, where "cccc" represents the company code.
Save the file in the correct format Save the file as a CSV file.
Validation tables contain the data that make up the selection lists for many of the fields in ADP's Workforce Now. For example, the Department table contains the codes displayed in the Home Department field on the Position page, and the Temporary Department column on the Paydata Entry Batch page.
Most of the validation tables for your company are set up by ADP during the initial import process. After the initial setup, you may need to add more entries, or records, to a validation table.
There are two options available for updating Validation Table data: Through the Workforce Now menu – Setup > Tools >
Typical Time & Attendance data are things like schedules or major changes to Labour Charge fields. For example, if you have a complete reorganization, an import field can be used to import employee level Labour Charge fields.
The Import Reference Guides contain useful information on how to structure your import file for the various import types. The best practice for preparing an import file is to use the corresponding import guide while you are creating the data import file.
For more detailed information about preparing your data import files, refer to the following ADP Workforce Now guides on the Support Center:
Importing Applicant Data Importing Employee Data Importing Paydata Importing Validation Table Data Importing and Exporting Time and Attendance Data
Prepare the data import file Prepare employee import files Prepare paydata import files Identify the other types of import files Use the Import Reference Guides to help you prepare data
Options for Structuring a Paydata Import File (continued)
If you were to combine both of these payment types in a single paydata import file, you would need to leave the field for Earnings Value blank for Bonus Pay, and leave the field for Earnings Amount blank for Vacation Pay, as shown in the following graphic:
Always refer to the Importing Paydata Guide for information on the fields required in the import file header.
After the import, you verify that the data imported as expected. You may also need to troubleshoot any errors or warnings that occurred. Verifying data is the final stage of the data import process.
Errors and warnings are generated when data is incomplete or invalid. If errors occurred, the import file status will display as Completed with Errors. The following example shows this status: