Epicor® HCM 5.

Link Module Implementation Guide

 Epicor® HCM 5.9

Link Module Implementation Guide

Epicor Software Corporation

Notices
This manual is furnished under a license agreement with Epicor® Software Corporation. The
manual was prepared to assist operators of Epicor Software Corporation’s Epicor HCM
product and may not be used for any other purpose without Epicor’s written permission. The
material contained herein is supplied without representation or warranty of any kind, is sub-
ject to change without notice, and does not represent a commitment by Epicor. Companies,
names, and/or data used in screens and sample output are fictitious unless otherwise noted.
Epicor assumes no responsibility and shall have no liability of any kind from the supply or use
of this manual or the material it contains. In an Epicor HCM-hosted or subscription envir-
onment, some Epicor HCM software functionality may not be available.
U.S. Government Restricted Rights. This software and its documentation are "Commercial
Items," as that term is defined at 48 C.F.R. §2.101, consisting of "Commercial Computer
Software" and "Commercial Computer Software Documentation," as such terms are used in
48 C.F.R. §12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R.
§12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable, the Commercial
Computer Software and Commercial Computer Software Documentation are being
licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those
rights as are granted to all other end users pursuant to the terms and conditions herein.
Unpublished rights are reserved under the copyright laws of the United States.
Manufacturer is Epicor Software Corporation, 10955 Westmoor Drive, Suite 100, West-
minster, Colorado 80021.
www.epicor.com
Epicor HCM is a registered trademark of Epicor Software Corporation.
Windows Server 2012 and Windows 7 are registered trademarks of Microsoft Corporation.
SQL Server is a trademark of Microsoft Corporation.
All other trademarks are the property of their respective owners.
Copyright © 1999-2014, Epicor Software Corporation. All rights reserved.
Printed in the U.S.A.
EHCM-590LKI-1122014
Contacting Epicor Software Corporation
General Information
Epicor provides a variety of human resource software products and support services. You
can contact us at Epicor or find out more information about additional software products or
services using any of the following methods:
Epicor Software Corporation
10955 Westmoor Drive, Suite 100
Westminster, CO 80021
(800) 334-5660 (General Information)
www.epicor.com

Epicor HCM Product Support and Education Services

Epicor HCM users with a current maintenance agreement have access to telephone hotline
support. When you call the Product Support and Education (PSE) hotline, a qualified PSE
representative works with you to diagnose and correct your problem. Contact a Epicor HCM
PSE representative using the following methods:

Telephone: (800) 424-6749

E-mail: [email protected]

Please have the following information at hand before you contact a PSE representative:
l Your customer number.
l A listing of any Epicor HCM modules or service packs that you have installed.
l A clear summary of the problem. Identify it specifically, especially in doc-
umentation that your organization can use later. Write down each step you
took when you found the problem (take screen prints, if possible).
l Any specific error messages you encountered.
Table of Contents
About This Guide vii

Who Should Read This Guide viii

Where to Look for More Information ix
Epicor HCM Online Help ix
Field Level Help ix
Microsoft Windows Online Help ix
Internet Explorer Online Help ix
How This Guide is Organized x
Conventions Used in This Guide xi
Introduction to Link 1

An Overview of the Module 2

Common Uses for Link 2
Basics of a Link Data Transfer 3
Export and Import Templates 3
File Formats 3
Data Transformations 4
Export Methods 4
When Link Runs 4
License the Software 5

Prepare to Activate the License 6

Determine Your Licensing Status 6
Locate Your License Key 6
Steps to License Your Software 7
7
Implement the Module 9

Plan implementation 10
Link Implementation Life Cycle 10
Planning 10
Development 11
Testing 11
Delivery for Testing 12
User Acceptance Testing 12
 Go Live and Beyond 13
Integration Setup 14
Link Terms 14
Configure Link Export Task 15
Export Master Tab 15
Export Master Subtab 16
Parameters Subtab 17
Rollup Code Subtab 18
File Subtab 19
Record Subtab 19
Field Subtab 21
Data Grouping Subtab 23
Data Sorting Subtab 24
Export Group Tab 24
Schedule Subtab 25
Tables Tab 26
Test the Integration 28
Invalid Carrier Feed Data 28
Run Link Export Task 29
Configure Link Import 31
Import Master 31
Import Group 32
Import Source 33
Import Date 33
Import Field 34
Import Field Translations 34
Import Schedule 34
About This Guide

Thank you for choosing the Epicor HCM Link module, which will expand the
capabilities of you Epicor HCM software. This guide will help you understand
how link is set up, how it functions, how to license your software, how you
might be part of the implementation process, and how to maintain Link inter-
faces.
Epicor HCM Link is a data transfer module that allows you to export data
from Epicor HCM to other workforce-related systems.
For more information about your Epicor HCM software, refer to online help
within Epicor HCM.

Concepts covered in this preface include:

Who Should Read This Guide viii

Where to Look for More Information ix
How This Guide is Organized x
Conventions Used in This Guide xi

- vii -
Preface

Who Should Read This Guide

This guide is for those individuals in your organization working with Epicor
HCM Professional Services to set up a data transfer interface using the Epi-
cor HCM Link module. There may be many people in your organization that
need to be involved to assist in setting up the Link interface; however, this
guide will address the main contact for this project within your organization as
the one responsible for completing the tasks. This guide uses "you" and
"your" to refer to the person in your organization who is responsible for the
project.
You must have system administrator permissions to license the Epicor HCM
Link module and use the Link tasks. Please read this guide to become famil-
iar with basic concepts and to understand how the Link module interacts with
your Epicor HCM software.

IMPORTANT: Use this guide only if you have received task-spe-

cific training from a Professional Services consultant. This guide is
to be used to complete tasks as assigned by Professional Services.
Even advanced users should not attempt an integration setup
without the aid of Professional Services.

- viii -
 About This Guide

Where to Look for More Information

There are several online help systems where you can find information and
documentation relating to Epicor HCM. This section describes the different
online sources available to assist you in using Epicor HCM and related soft-
ware.

Epicor HCM Online Help

Epicor HCM has an extensive online help facility to assist you when you need
help. You can access online help in Epicor HCM by clicking the Help button
that is in the product. If you are in a task when invoking help, the help topic for
the task that you are viewing appears.
Each procedural help topic in the Epicor HCM online help provides sys-
tematic instructions that guide a user through completing a task. Once the
online help is open, you can navigate to other areas in the help system. You
can search for other procedures through the Contents, Index or by using the
built-in Search functionality.

Field Level Help

While Epicor HCM is very intuitive to use, there may be certain fields in a task
that are more difficult to work with or remember their purpose. Epicor HCM
has a Field Level Help system, where some key fields have been singled out
for quick access to information. Anywhere you see a question mark icon
you can click it to display an informational box. The information presented is
intended to assist you in completing that field and therefore to finish the task.
If you need further assistance, the full online help system is always available.

Microsoft Windows Online Help

For more information about Microsoft Windows, choose Help and Support
from the Start menu.

Internet Explorer Online Help

Use Microsoft Internet Explorer Help for assistance with issues specific to
Internet Explorer. To view Microsoft Internet Explorer Help, from the Menu
bar click Help > Internet Explorer Help or press F1 on your keyboard.

- ix -
Preface

How This Guide is Organized

The following table describes the sections contained in this guide:
Chapter Contains
About This Guide Description of this guide.
Chapter 1: Intro- Introductory information about the Link module.
duction to Link
Chapter 2: License Instructions on how to license the Link module.
the Software
Chapter 3: Imple- Information about planning for the implementation, set up files to
ment the Module transfer, and an overview of the link tasks.

-x-
 About This Guide

Conventions Used in This Guide

As you use this guide, you'll notice that some text appears in bold or italic let-
tering. These conventions have meaning and help you learn and use Epicor
HCM. You'll see the following conventions in this guide.

Convention Description
bold Used for box labels including check boxes, drop-down list items, tab names,
menu labels, and any literal text that you must type exactly as presented.
Especially important to use for boxes where the label has multiple words or is
a sentence. Also may be used for dialog box titles.
italic Any variable text you replace with specific text, such as the current date or
the name of a file, appears in italics.
Navigational When you are instructed to select an item, this instruction typically means to
Terminology click the item to highlight it (as in a list). When you’re instructed to choose or
click an item, these actions execute a command (as when choosing or click-
ing the OK button). Double-click means to quickly press and release the left
mouse button twice. Press refers only to keys on the keyboard. Enter means
to type the text as indicated and take the appropriate action to move on to the
next step. For example, “Enter the employee’s hire date” means to type the
date in the box and then to press the Tab key to move to the next box.

- xi -
 Chapter 1

Introduction to Link

Welcome to the Epicor HCM Link module.

This chapter provides an overview of the Link module, common uses for a
Link integration, and basics of a Link integration.

Concepts covered in this chapter include:

An Overview of the Module 2

Basics of a Link Data Transfer 3

Epicor HCM | 1
Chapter: 1

An Overview of the Module

Epicor HCM Link is a data transfer module that allows you to export data
from Epicor HCM to other workforce-related systems or import data into Epi-
cor HCM from an external system file. The ability to electronically transfer
data from provides the following benefits:
n It relieves you of the burden of entering the same person data in two
different systems (for example, Epicor HCM and your payroll sys-
tem).
n It ensures that both systems involved in the data transfer contain the
same data, thus increasing the overall quality of data in your organ-
ization.
n It allows the single point of entry approach many organizations utilize
to push HR maintained employee information out to multiple internal
systems and external vendors.

Common Uses for Link

Common systems and vendors that Epicor HCM Link can accommodate are
as follows:
n Payroll System
n Financial System
n Timekeeping System
n Learning Management System
n Benefit Carriers
n Internally Developed Databases

2 | Epicor Software Corporation

 Introduction to Link

Basics of a Link Data Transfer

Link consists of multiple tasks and steps that are used to configure an inter-
face for an export file or an import file. As you begin to explore Link notice that
the basic structure of a Link export is a template. You can use Link con-
figuration tools to define the export file details and determine when link runs
the export file.

Export and Import Templates

An Epicor HCM Link template defines the type of integration, the type of data
that can be handled in the file transfer, and determines how the integration
operates. The data definition is separated into the following:
n The data records and fields to be exported or imported.
n The people whose data is used for the export or import file.

A template contains a definition of the type of data that is sent in an export file
or imported into HCM. One or more files contain the records and fields data
as specified by the template. The type of records and fields that are used in a
template can vary greatly between different templates. For example, a
payroll export template may have deduction information in the export, and a
benefit carrier export template may contain dependent eligibility information.
The export template specifies the people in your HCM system whose data is
being exported. For example, your payroll import template may include only a
group of individuals being paid by that payroll (not international employees or
dependents), and your benefic carrier export template would include only
employees enrolled in the benefits that carrier provides. Within each tem-
plate, you can assign people into unique groups and work with those groups
independently of each other.
An export template built for a payroll system can export a comma delimited
ASCII file that might be similar to the following:

Employee Number, First Name, Last Names, Home Area

Code, Home Phone
1234,Joe,Smith,212,555-1234
5678,Sally,Jones,212,555-5678
9012,Mark,Jefferson,212,555-9012
3456,Jessica,Madison,212,555-3456

File Formats
Each template allows data export in the following two primary file formats:
ASCII Delimited and ASCII Fixed Length. There are also situations where
Epicor HCM Link can be modified to allow the export of data in other formats,
such as XML.

Epicor HCM | 3
Chapter: 1

Additionally, an Epicor HCM Link export template can be configured to send

person data via a web service. This type of template is only relevant for sys-
tems or vendors that provide that type of data transmission capability.

Data Transformations

Epicor HCM Link can be configured to transform your data using formulas to
match the expectations of the receiving system or vendor. For example, if you
store employee salary information in Epicor HCM as an annual amount, you
can use a formula to export that data in a pay period amount.
Another common transformation is a basic translation of a data element. For
example, if you store a department code in Epicor HCM as “AB100”, you can
translate that code to “1200” during the export process. The opposite can be
set up for importing data for use in Epicor HCM. Data transformations allow
you to have Epicor HCM set up to meet your data needs, yet have that same
data converted for an export file or import file that enables you to work with
data in the form required by external systems and vendors.

Export Methods
In Epicor HCM Link, you can define the method of exporting data for each
export template. The most common option for many types of interfaces is to
transfer only relevant changed data. To accomplish this, Epicor compares
the data as of the date you are processing with the data in the previous
export. The comparison process then removes any data elements or even
entire person records from the resulting export file if no changes were
present, thus resulting in a file that contains only changed data.
The other option is to transfer all data for all people in the export. With this
method a full data dump is performed of all the data elements and people
data defined in the export template.

When Link Runs

Epicor HCM Link provides two methods to process an export: scheduled and
manual.
When you run the integration manually, it gives you the most flexibility, allow-
ing you to run the process using different dates or groups of people. It also
provides immediate access to review the audit report and any relevant errors
reports.
With the scheduled processing method you configure the export template to
process the export file on a standard schedule. This method is most com-
monly employed in situations where an export template has been suc-
cessfully operating for a period of time.

4 | Epicor Software Corporation

 Chapter 2

License the Software

This chapter describes the tasks necessary to complete the licensing of the
Epicor HCM Link module.

NOTE: If you are an Epicor-hosted client, you can ignore this

chapter and proceed with Chapter 3 to begin your Epicor HCM Link
module implementation.

Concepts covered in this chapter include:

Prepare to Activate the License 6

Steps to License Your Software 7

Epicor HCM | 5
Chapter: 2

Prepare to Activate the License

To have access to and use the Epicor HCM Link module, you need to activ-
ate the license in your system. Licensing your system ensures that your
organization receives the base product and module functionality, for the allot-
ted number of users that you purchased.

Determine Your Licensing Status

The status of the licensing of your Link module depends on whether you pur-
chased the module at the same time you purchased your Epicor HCM soft-
ware or if you purchased the module as an upgrade after an initial purchase
of Epicor HCM.
n Module purchased at same time as Epicor HCM – When you
licensed Epicor HCM you, at the same time, licensed the Epicor HCM
Link module when you licensed your system. You can ignore this sec-
tion and skip ahead to Chapter 3.
n Module purchased as an upgrade, after the initial purchase of
Epicor HCM – Complete the procedures in this chapter to license
the Epicor HCM Link module.

Locate Your License Key

Make sure that you have received and located your upgrade and module soft-
ware package from Epicor, which includes upgrade CD.
Epicor sends your Link module license key via email. Have the license key
available before you continue.

6 | Epicor Software Corporation

 License the Software

Steps to License Your Software

When the upgrade process is finished, complete the following steps to
license the Link module:
1. Log on to your Epicor HCM software as a Super Admin and click Util-
ities Licensing Display Licensing Information. The Current
Licensing information section appears, as shown in Figure 2-1..

Figure 2-1: The Current Licensing information section

2. Click Change. Epicor HCM displays the Enter License Key window.
3. Enter your license key and click Submit.
4. Verify that all information regarding the number of users and Epicor
HCM modules for which you are licensed is correct.

Epicor HCM | 7
 Chapter 3

Implement the Module

Now that the Link module is licensed, you are ready to begin implementing
the Link module. Implementation of the module will require planning, con-
figuration, setup of codes, and testing before you can transmit a file.

Concepts covered in this chapter are:

Plan implementation 10
Integration Setup 14
Test the Integration 28
Run Link Export Task 29
Configure Link Import 31

Epicor HCM | 9
Chapter: 3

Plan implementation
During the Link module implementation process, you will work together with
Epicor Professional Services team from start to finish. Your participation in
each and every phase is vital to the success of the project. You will be
involved in planning, data gathering, communicating business needs, and
testing of the interface. Depending on the type of interface being developed,
you should have representatives from several different functional areas to be
key members of the team. In some cases, it may be realistic to have people
from Payroll, Benefits, Human Resources and IT departments that can con-
tribute to the success of the Link implementation.
Epicor has, as part of the Professional Services team, a group that spe-
cializes in interface development. Throughout this document, the Pro-
fessional Services Interface Developer will be referred to as PSID.
Depending on the scope of a development request, there could be one
developer or several. One will be assigned as the owner of all your interfaces.

Link Implementation Life Cycle

Epicor follows a full Software Development Life Cycle (SDLC) when imple-
menting an interface.

Planning

The project begins when the contact person from your organization submits a
request for an interface with your Epicor project manager or after the creation
of a project’s scope. A PSID is then assigned to work on your interface.
One of the most important steps during the initiation phase is obtaining the
specifications regarding the interface and providing it to the PSID for ana-
lysis. File and field specifications can come from many sources. If the pur-
pose of the interface is to connect to another system such as a payroll
system, you should be able to contact the payroll vendor for file requirements.
The same should apply to any benefit carrier exports. You should check with
the vendor first to make sure that their system can import a file and then
request the specifications for importing the desired data. If the interface recip-
ient system is one of your organizations internal systems such as Active Dir-
ectory, you should look to your IT staff to obtain the specifications from their
IT staff. The PSID reviews the specifications to get an understanding of the
development that is required.
The PSID gathers knowledge about the specific business area of the inter-
face, formalizes requirements, and prepares an interface specifications doc-
ument for the interface. The PSID prepares the functional specifications,
prepares work plans, cost estimates and schedules for the various items that
will be delivered. There will be a kickoff call by Professional Services to intro-
duce all parties involved, to the overall work plan, and the work schedule.
After the kickoff call, the PSID schedules a mapping meeting. For the

10 | Epicor Software Corporation

 Implement the Module

mapping, it is the vendor’s responsibility to review the mapping document for

general file layout. It is your responsibility to define from where the contents
are to be derived. Epicor is not responsible for determining the data from your
Epicor HCM system that you want sent in the export file.

Development

The development stage starts when the PSID begins designing the interface.
The design stage takes, as its initial input, the requirements identified in the
approved requirements document. For each requirement, a set of one or
more design elements will be created. Design elements describe the
required interface features in detail.
Implementation of the design by the PSID consists of two parts: Con-
figuration and Development of specialized code. Link is used to build and con-
figure the structure of the integration.Epicor HCM contains some base
templates that are used as a starting point for certain integrations. When
working with the Epicor HCM Link Configuration task, the PSID performs the
following:
n Creates an Export Master or Import Master record, with an ID and a
descriptive name.
n Uses the Export Master or Import Master to configure the integration.
n Develops specialized coding in C#, as necessary. The PSID builds
the more complicated requirements defined in the interface spe-
cifications document.

Once the integration has been applied to your live database, testing can
begin.

Testing

Development testing consists of testing the interface and making adjust-

ments that are needed. The PSID will create a test plan detailing scenarios
that mimic real occurrences. This testing is performed in the development
environment at Epicor. These tests are designed to answer the following
basic questions:
n Is data coming through the file?
n Are amounts coming through the file?
n Are code conversions working?
n Are data deletions being identified properly?

For exports, once development testing has successfully been completed, a

full or baseline file will be produced and delivered to both the client and the
vendor. The file needs to be analyzed by the vendor for structure and by the
client for accuracy of the data contents. Import data is verified against an

Epicor HCM | 11
Chapter: 3

HCM test system. During development testing, the PSID will make any
necessary adjustment that may come as a result of the testing.

Delivery for Testing

Once the integration setup has passed structural analysis and you have
reviewed the contents of the file, the PSID will work with you to deploy the
integration to use your live Epicor HCM data. Your PSID will then schedule a
time to train you and your staff on the functionality of Link and how to run the
interface. With the interface deployed on your Epicor HCM system with real
data, you test the file for accuracy. A full file is created upon delivery that you
are responsible for reviewing the accuracy of the contents.
A Link integration can also be delivered if you operate a hosted Epicor HCM
system. Your PSID will coordinate with Epicor’s Network Services team to
deploy the integration to your production software. Whether your Epicor
HCM system is hosted by Epicor or your organization houses your software,
you are responsible for the testing the integration that is developed for your
organization.

User Acceptance Testing

User Acceptance Testing (UAT) is designed to expose unforeseen issues

with the integration as the tests are conducted on your Epicor HCM system
and delivered as a test file to the recipient system (for exports).
Your PSID, in most instances, creates and configures the integration in their
Epicor environment. Every effort is made to deliver to you a working integ-
ration; however, unknown environment factors can affect the way the integ-
ration behaves. It is important to have you test the integration on your
working environment.
UAT starts with you creating a test plan detailing scenarios that mimic real
occurrences, adding, changing, and deleting data from Epicor HCM. Using
your test plan you test the integration on your Epicor HCM system. After your
testing, contact the vendor to notify them you want to send a test file and then
send the file to the vendor according to their instructions. You might be provid-
ing the test file to your appropriate staff, if an internal system is the intended
recipient of the file. The vendor (or your staff) analyzes the file and reports
back to you errors in the file that do not adhere to their requirements.
You will work with your PSID to address the issues and functional concerns
that arise during UAT. After making required alterations to the interface, the
PSID will test the changes in Epicor’s environment. Then the PSID will sched-
ule and deliver the changes to your Epicor HCM system. You, again, proceed
through UAT on your Epicor HCM system.

12 | Epicor Software Corporation

 Implement the Module

Go Live and Beyond

Following your sign-off on the UAT, your export integration is ready to inter-
face with the recipient system and feed live data. Continue to monitor the file
transfers, errors in transmissions, and notifications from the vendor of
changes to their system that may affect your file. During the lifetime of the
interface, situations may arise that require a change to the integration setup.
Additional data may be requested to be included in the file. Data issues may
also result in changes to the integration. It is important to remember that the
interface is a data processing routine. Your specific data needs may change
over time and maintaining the integration or setting up a new integration will
be required. You can always contract with Professional Services for addi-
tional interface work on a fee basis.

Epicor HCM | 13
Chapter: 3

Integration Setup
When setting up an export integration to interface between Epicor HCM and
a receiving system or a file that you will import into Epicor HCM from an
external system, Professional Services does the majority of the configuration.
You may be given specific assignments to assist in completing the integ-
ration. To set up the integration, Professional Services mainly uses the Con-
figure Link Export task or the Configure Link Import task. After the
integration is configured and delivered, you may be asked to complete some
specific assignments using the Link configuration task. You will also be
involved in testing and running the export or import.

IMPORTANT: Setup of an integration is very complex. You should

never attempt it unless you have received task-specific training
from Professional Services. Even advanced users should not
attempt an Integration setup without the aid of Professional Ser-
vices. Only an administrator has access to and can use the Con-
figure Link task.

Link Terms
Before getting started, familiarize yourself with the following terms:
n Export Master or Import Master – An Export Master or Import
Master is a set of definitions that create a specific type of export or
import to or from an external system (for example, a payroll system
such as ADP). Each Export Master or Import Master may be accom-
panied by template that contains the settings to use that define the file
layouts, validation rules, and other parameters. Each Export Master
and Import Master is referred to by a unique ID code.
n Template – A template is the framework of tables that defines the
type of Export Master or Import Master and the configuration that can
be done for the integration. These tables consist of the Export
Master, Parameters, Rollup Codes, File, Record, Field tables. For
imports these tables consist of the Import Master, Import Group,
Import Source, Import Date, Import Field, Import Field Translations,
and Import Schedule. The configuration of these tables is done
through the Link configuration tasks. Most of this configuration is
done by Professional Services when you contract with them to build
an integration for you. You may be given some specific configuration
to complete by Professional Services to support the integration. Two
areas that you typically may be asked to modify are the Parameters
and Rollup Code subtabs.

14 | Epicor Software Corporation

 Implement the Module

n Export Group or Import Group – An integration group is a subset

of the people in your Epicor HCM database, from which you determ-
ine relates to the integration data. Each Epicor HCM Link integration
will use at least one group. You can set up as many different groups
as necessary.

Configure Link Export Task

The Configure Link Export task is used to create an Export Master, and set
up the associated template framework. You will also define the export data
details, and the export functionality using the task.

Navigation Path
Find this task on the Utilities tab:
Data Integration Development Tools Link Configure Link Export

The following are the three main tabs in the task:

n Export Master
n Export Group
n Tables

There are many subtabs in the task. The Export Master tab is the default start-
ing view.

Export Master Tab

When you access the Configure Link task, the Export Master subtab on
the Export Master tab is the default view. The Export Master tab is used to
create and configure the export integration. On the Export Master tab, the fol-
lowing subtabs are available:
n Export Master
n Parameters
n Rollup Code
n File
n Records
n Fields

Epicor HCM | 15
Chapter: 3

n Data Grouping
n Data Sorting

Export Master Subtab

The Export Master subtab is used to create a specific type of export, such as
ADP or 834 Benefit Carrier. The Export ID and Description is seen in the
left pane and, therefore, should be descriptive of the type of export or the
vendor (for example, Payroll or ADP). In most cases, Professional Services
will create the Export Master, after discussions with you. After the Export
Master has been delivered to you, Professional Services may ask you to edit
the settings.
To edit an Export Master, proceed as follows:
1. On the Export Master subtab, from the left pane, select the appro-
priate Export Master name for which you will edit the settings.
2. Edit the following fields, as needed:
Name Description
Delimiter A delimiter is a character used to terminate
segments, separate data elements or sub-ele-
ments, and serve as an element value repe-
tition separator in a delimited file. Common
characters that might be entered in this field
are * (asterisk), : (colon), ~ (tilde), ^ (caret), or
, (comma). A SQL notation can also be used
and a tab delimiter (\t) can be used.
Delete Character A character that denotes a deleted field in the
file.
Fixed Length Select the check box to use a fixed length file
format, instead of a delimited file format.
Make sure this check box is cleared if you are
exporting a delimited file.
Send All Data Select the check box to export all data
records, regardless of whether the records
have changed.
Rollup Benefit Codes Select the check box to consolidate selected
benefits deductions into a single payroll rollup
code for the export file. Refer to the section
on the Rollup Code subtab for further details.
Rollup codes for benefit carrier export files
are handled differently than for payroll export
files, so this option would not be appropriate.
Delete Work Tables at Finish Clear the check box to retain the data in the
work tables after the export run is complete.
End Date Previous Export Group Select this check box if you want to auto-

16 | Epicor Software Corporation

 Implement the Module

Name Description
matically end date the previous export group.
Maximum Number of Export The number of export logs for this Export ID
Logs to Keep that are stored in Epicor HCM.
Export Type The Export type determines how the export
will run. Select from Manual or Triggered.
Selecting Triggered enables the Triggers sec-
tion, which allows you to configure automatic
exports based on specific database events.
Template Type Select the appropriate file from the list to act
as the link template for the Export Master
record.
Data Object column and the If Triggered is selected from the Export
Type column Type list, then use the Triggers section to
select one or more values in the Data Object
column and corresponding values in the Type
column to configure automatic exports based
on the selected events.
3. Click Submit to finish the task.

Parameters Subtab

The Parameters subtab is used to define conditions for the export operation,
the export interaction with a receiving system, and other types of conditions
that may be required by the type of export or by the vendor receiving the
export file. This could include setting the export to pass a user name and pass-
word, triggers for such actions as to run export reports, and values for data
fields or a web service URL. The parameters that are set up are unique to the
export type or to the receiving vendor and the parameter values are unique to
the receiving vendor or your Epicor HCM setup. Based on the type of export,
the supplied vendor documentation, and in collaboration with you, the PSID
will determine the parameters to set up and the values to assign. In some
cases, you will have to change values after the integration is delivered to you,
when instructed to do so by the PSID.
The following are the only two fields available for a parameter setup:
Field Description
Name The Name provides the description of the parameter.
Value The Value is the appropriate data entry that corresponds with
the parameter type. For example, if the parameter Name is
Password, then the Value would be the actual password that is
needed to process the export.

When specific parameter values are provided by Professional Services for

you to change, proceed as follows:

Epicor HCM | 17
Chapter: 3

1. On the Parameters subtab, from the left pane, select the parameter
to change.
2. In the Value field, enter the value that you have been instructed to
enter by Professional Services.
3. Repeat the previous steps for other parameter changes or click Sub-
mit to finish the task.

Rollup Code Subtab

The Rollup Code subtab is used to consolidate deductions for selected

benefits into a single code to be used in the export file. The typical use for rol-
lup codes is payroll deductions for benefits. With rollup codes you can export
just one payroll deduction code for an employee record instead of several sep-
arate codes for each of the employee's benefit plan options. For example,
you may want to roll up dental, medical, and vision plans into one health insur-
ance payroll deduction code.
For export files of health benefits enrollments to a benefit carrier the rollup
codes are used slightly differently. Instead of the rollup code being a payroll
deduction code, the code is a benefit plan type code that is specified by the
benefit carrier, which is used for enrollment or maintenance in a benefit plan.
The benefits that you select for the rollup code correspond to the benefit car-
rier benefit plan type code.
You will work with your PSID to determine the codes and requirements the
receiving system has, and which are the benefits to consolidate into the
codes. The contact person for the receiving system can provide to you the
codes for their system. In most cases, your PSID will complete this section;
however, they may provide the codes and associated benefits for you to com-
plete.
Under the direction of and with data provided by Professional Services, use
the Rollup Code subtab as follows to add a new rollup code or edit an existing
code:
1. Click the New button to create a rollup code or click a rollup code from
the left pane to edit.
2. In the Code field, enter the value for the code that is sent in the export
file and is used by the receiving system.
3. In Description, enter a word or phrase that describes the deduction
rollup code. In most cases, this information is not sent in the export
file.
4. Select benefit options from the Available Items column, and then
click the Add Selected Items arrow button to move them to the
Selected Items column.
5. Click Submit to finish the task.

18 | Epicor Software Corporation

 Implement the Module

File Subtab

The File subtab is used to enter location and name of the export file that is
produced as the end result of the export process. The location of the file
should be accessible to Epicor HCM and the HCM administrators and in the
same IIS Application Pool as Epicor HCM. Professional Services will assist
you in determining a suitable location for the export file.
Specify the file location and name as follows:
1. In File Description, enter a word or phrase to describe the export
file.
2. In the Path to output file field, enter the path to the location that the
generated export file will reside. Enter a full path on the IIS Server or
domain location that includes the drive letter and ends with a back-
slash (\), for example, C:\TEMP\.

Previous export files at the same location, with the same name, are
deleted when a new export file is generated.
3. Enter the name and format of the output file in the Output file name
box.

NOTE: Special coding can build the file names with the
export group or the date.
For example, if you are using the ADP template, Employee
data is PR$GROUP$EMP.csv. When you generate the
export, Epicor HCM Link automatically replaces $GROUP$
in the output file name with the export group established on
the Export Master subtab. Ask your PSID to set up this
code, if this is something that you need.

4. Select the Use Text Qualifier check box to specify a qualifier within
the export file.
5. In the Text Qualifier box, enter the qualifier used for the export file
data.
6. Click Submit to finish the task.

Record Subtab

Records and fields set up the structure for the export file data detail. The
Record subtab is used to create and define the records that the export file
contains. Each export file can have multiple record configurations within it.
Using the Record and Field subtabs to set up the export file data can be com-
plex. Your PSID will use these subtabs extensively when developing your
export integration. In most cases, you will not be asked to create records or
configure records. The records and fields that the PSID set up are based on

Epicor HCM | 19
Chapter: 3

the type of export and the unique requirements of the receiving system.
When your integration is delivered it will contain several records with multiple
associated fields.
Each record that is created is found in the left pane and is identified by the
Sequence and the Description.
The following describe the fields of a record on the Record subtab:
Field Description
Sequence A number representing the order in which this record type
appears in a file. For example, if your file includes a header
record and an employee data record in your export file, enter
1 for the header record and 2 for the data record. You can
have gaps in numbers, but lower numbers still appear before
greater numbers (1000 appears before 2000).
Description A word or phrase describing the record.
Work Table This is the name of the database table to populate with work
data during the export execution. This name must be distinct
for each record type within the export type, as Epicor HCM
selects the data for each record type during the export and
adds it to this table.
Warehouse Table This is the name of the database table that Epicor HCM pop-
ulates with the data from the previous export run during the
export execution.
The data in the warehouse table is used to calculate dif-
ferences between the current and previous exports, and is
compared to the data in the work table. This name must be
distinct for each record type within the export type, and must
be different from the work table name.
Always Send The Always Send check box indicates to always include the
record in the export file, even if the data has not changed
since the last export. This check box is typically selected for
header and trailer records.

Note: If the Send All Data check box is selected on the

Export Master subtab, it is the equivalent to having the
Always Send check box selected on every record.
Single Record The Single Record check box indicates that the record type
is not dependent upon person data, and only one instance of
the record is written to the export file. This check box is used
for all header and trailer records.
Non Person Record Selec- This check box is used to include non-person data, such as
tion data from a code table, in an export. Data is not restricted
based on the people for the export group.
Send Full Record On Any This check box indicates that a full record is processed when
Change any change in the data is made.
Source Based Person This check box is used to include data from the source table,

20 | Epicor Software Corporation

 Implement the Module

Field Description
Selection based on the person identifier.

Field Subtab

The Field subtab is used in conjunction with the Record subtab. Each record
is associated with one or more fields. The Field subtab is used to create and
define the fields that the export file contains. Each field definition specifies the
details of the field within that record type, such as field name, data type, and
the field's position in the export file. In most cases, you will not be asked to cre-
ate fields or configure fields. The records and fields that the PSID set up are
based on the type of export and the unique requirements of the receiving sys-
tem. When your integration is delivered it will contain several records with
multiple associated fields.
Each field that is created is found in the left pane and is identified by the
Sequence and the Description.
The following describe the fields on the Field subtab:
Field Description
Export Field Name A descriptive word or phrase for the field.
No Delete Selecting the check box specifies that an empty field in the cur-
rent export file should not delete previously sent data for the
field. If the field had data in the last export file, the data should
not be deleted when the current export file has the field as
empty.
Always Send Select the check box to always to send data for the field.
Do Not Compare Select the check box so the field does not go through the com-
pare process, and will not initiate a change to be sent in the
file.
Data Type From the list, specify the type of data as Fixed-Length
string, Variable-Length string, or Numeric.
Start Position The starting location for the field data in the export file.
Length The length of the data allowed in the export file for the field.
Use a single value for fixed-length string and variable-length
string data types. For numeric data types, use the format
(d,p), where d is the total number of digits and p is the number
of places to the right of the decimal.

For example, 13,2 indicates a 13-character field length with

the decimal point two positions from the right.
Justification This setting is only applicable for fixed-length fields. From the
list, select Left or Right. Epicor HCM defaults to Left jus-
tification if this field is blank.
Fill Char Enter a character to use to fill remaining space where the data
did not use all of the fixed-length space. Epicor HCM defaults

Epicor HCM | 21
Chapter: 3

Field Description
to a space if you leave this field blank.
Key Field Designates this field to indicate to generate a new record each
time the code changes in the export file.
Exclude from Export The check box indicates that this field exists in the work table
solely for calculation purposes and should not be sent to the
actual export file.
Convert Codes The check box is used to indicate the field needs to be con-
verted based on the entries made during code conversion
setup.
Rollup Benefit Codes The check box is used indicate that the values selected for this
field are compared against the configured benefit rollup
codes. The contribution values for benefits are used for the
corresponding rollup code.
For example, data for several company-specific benefit plans
may be sent to the benefit provider as a single export record,
with the contribution amounts summed for the benefits with
the same rollup code.
Encrypted Data Flag Select the Encrypted Data Flag check box to indicate that
data in this field is encrypted in the database and must be,
therefore, decrypted for export.

For example, data for national IDs are stored encrypted, but
on export this data should be sent decrypted. This check box
specifies that values from the database should be decrypted
for export.
Source Table Select the name of the table that provided the data for the spe-
cified field from the Source Table list.
Select Calculated to indicate that you want a specified field to
be calculated based on other fields in the work table, rather
than pulling data directly from the original database.
Source Field Enter the name of the Epicor HCM source field in the Source
Field box. You can only enter actual field names from the
source tables.
Source Value Enter the Transact SQL expressions for calculating field val-
ues, if necessary, in the Source Value box. The length of an
expression is limited to 2,000 characters.
Invalid/Valid Data Rule Enter a SQL clause of up to 2,000 characters that defines the
data validation rule in the Invalid/Valid Data Rule box.
Defines Valid Data Select the Defines Valid Data check box if the validation rule
defines the set of valid data. The Invalid/Valid Data rule
defines invalid data; however, you can select this check box if
you want this rule to do the opposite, that is, to define valid
data. Data that does not match the validation rule is con-
sidered invalid.
Validation Error Message The text in this field displays in the Data Error report run,

22 | Epicor Software Corporation

 Implement the Module

Field Description
which is found on the Link Export run page. This message
provides users with a descriptive message and potential solu-
tion for data errors. Standard integrations already have val-
idation messages added.
Associated Fields Select one or more of the available associated fields from the
Available Items column and click the arrow button to
move them to the Selected Items column.
Associated fields are fields that are dependent upon one
another. Specifically, Epicor HCM exports the data in an asso-
ciated field when the data in the primary field changes, even if
the data in the associated field did not change. You typically
set up associated fields for paired fields.

For example, a deduction amount must always be sent with a

deduction code. If the deduction amount (primary field)
changes, Epicor HCM should also export the deduction code
(associated field)
Populate Codes This option is not often used or appropriate for many integ-
ration configurations. The PSID will determine if this option
can be used to populate codes.
Code Conversion Enter the corresponding code from your destination system in
the Convert To box.
Code conversions let you map values between Epicor HCM
and the external system. For example, if your payroll system is
set up for a one-character status code, you would map the
status code of "LOA" to the payroll system code of "L."

Data Grouping Subtab

Use the Data Grouping subtab to create a set of records to group together in
the export file, rather than have the records listed sequentially. Multiple data
record groups can be created, which you can use to define parent and child
data group relationships.
Data groups that you create are listed in the left pane, with each group iden-
tified by the Description name that you assigned.
The following describe the fields on the Data Grouping subtab:
Field Description
Description A word or phrase describing the group of records. This description appears in
the left pane. Multiple groups can be created for the export file and appear in
the left pane.
Parent When multiple groups are created for the export file, you can designate the
Grouping parent group for this group. This creates a parent/child group relationship.
Record Select at least 2 records that have at least one field in common. The common

Epicor HCM | 23
Chapter: 3

Field Description
fields are used to group the data.
Data Set the order that the records appear in the group.
Grouping
Sequence
Grouping The common fields from the selected records are listed in the Available Fields
Fields box. To group the field data for the records move the field from Available
Fields to Selected Fields.

Data Sorting Subtab

Use the Data Sorting subtab to define the sort order for the specific records in
the export file or data groups. To sort an entire file with multiple records, you
create a data group, and then sort the records for the data group.
The following describe the fields on the Data Sorting subtab:
Record Sorting Fields Description
Record Select the record that contains the field by which to sort.
Sort by Select the field by which to sort.
Sort Order Select the sort order.

Data Group Sorting Fields Description

Data Grouping Select the data group that contains the fields by which to sort.
Sort by Select the field by which to sort.
Sort Order Select the sort order.

Export Group Tab

Export Groups are a subset of persons chosen to have their information
exported from Epicor HCM Link into a designated external system. Rather
than including all persons in every export, you choose which group to export.
A separate set of Export Groups is defined by each Export Master. In most
cases, you will be assigned the task of creating the group to include in the
export.
Create an Export Group as follows:
1. With the appropriate Export Master for the integration selected, click
the Export Group tab.
2. Enter a name for the group in the Group box.
3. Enter a description of the group in the Description box.
4. Select the Bank Deposit Edit Disabled check box to restrict
employees from updating direct deposit information during the

24 | Epicor Software Corporation

 Implement the Module

export. If your Epicor HCM system is licensed for the Employee Con-
nect module, selecting this check box restricts employees from chan-
ging their direct deposit information through Employee Connect
during your export. Once your export is complete, clear this check box
to enable employees to update their direct deposit information.

NOTE: It is not required that you disable direct deposit modi-

fications in Employee Connect during your export; how-
ever, any changes made to direct deposit information
during the export will not be picked up by the export.
Changes will be included in the next payroll export.

4. Select the Check Row Security to Run check box to restrict the
ability to manually run this export to only those users with appropriate
row security permissions.
5. In Archive Path, enter the path to the location that previously gen-
erated export files will reside. After a new export file is generated, the
old export file is automatically moved to the archive location. Enter a
full path on the IIS Server or domain location that includes the drive
letter and ends with a backslash (\), for example, C:\TEMP\.
4. To enable row security rules to be used for a scheduled export, com-
plete the following:

n Select the Process Rules on Export check box.

NOTE: Triggered exports process row secur-

ity rules during the nightly run.

n Select one or more of the available row security rules

from the Available Items column and click the arrow
button to move it to the Selected Items column.

7. Click to continue to the next subtab or click Submit to finish the

task.

Schedule Subtab

Use the Schedule subtab to set up regularly scheduled times for the Link
export to run. Consult with your PSD to determine if a scheduled export is
appropriate for the export type.

IMPORTANT: At least one manual export must be run prior to turn-

ing on scheduling.

Epicor HCM | 25
Chapter: 3

Set up the schedule for an export as follows:

1. In Schedule Name, enter a word or phrase description for the export
schedule.
2. In Start Date, enter a date for the exports to begin.
3. In End Date, enter a date for the export to end, if applicable.
4. Select the Enabled check box if you want to immediately enable this
schedule.
5. Epicor HCM automatically marks the Current box Yes if the start
date is on or before the current date, and the end date is later than the
current date (or if there is no end date for this record).
6. From the Occurs list, select the frequency with which this schedule
will run .

NOTE: Other boxes appear depending on if your selection

was Daily, Weekly, or Monthly. Fill in these boxes accord-
ingly.

7. In the Recurs Every field, enter a numeric value. The value you
enter here is used in conjunction with your selection in the Occurs
list.

For example, if you selected Daily and entered the number 5, then
Epicor HCM schedules the export to run every five days.

8. From the Run Time list, select or enter the time you’d like this export
to run.
9. Click Submit to finish the task.

Tables Tab
The Tables tab is used to define the database entities that Epicor HCM uses
in creating exports. The PSD will work with you to determine the necessary
tables for your exports and will set up this tab as part of your integration deliv-
ery.
The PSD will use the following fields to configure the table setup:
Field Description
Name The database object – a table or a view.
Sequence A numeric value designating the sort order that the tables
appear in the left pane. The secondary sort order is alpha-
betical.
Sequence (Criteria) The order in which the criteria statements are processed for the

26 | Epicor Software Corporation

 Implement the Module

Field Description
table.
Criteria A SQL statement to further define how the table data is used.

Epicor HCM | 27
Chapter: 3

Test the Integration

After the integration is configured and delivered to you by Professional Ser-
vices, you will work with Professional Services to ensure that the integration
performs as required. As part of the testing, you can run the Invalid Carrier
Feed Data report. You can run the report at any time after your integration is
delivered to verify the data in your Epicor HCM system is set up properly for
the export to function correctly. It is recommended that you always run the
report and correct any error listed on the report, before you process an export
through Link.

NOTE: Data validation errors do not prevent the export process

from completing; however, the data that is sent will be incomplete
or incorrect if the errors are not fixed prior to export.
Functional errors, such as invalid columns, malformed SQL state-
ments, will cause the export process to fail and must be resolved to
export successfully. This report does not identify functional errors.

Invalid Carrier Feed Data

The Invalid Carrier Feed Data report tests that your Epicor HCM system is
optimally set up to transmit data that is correct and complete. There are two
ways to access the report:
n Through the Run Link Export task.
n Through the Reports tab.

Run the report through the Reports tab as follows:

1. On the Reports tab, navigate to Benefits Invalid Carrier Feed
Data.
The report is produced and identifies data issues or setup issues that
could prevent a successful export.
2. Save the report and, if there are errors on the report, provide the
report to Professional Services.
3. Work with Professional Services to address items on the report prior
to running the export.

28 | Epicor Software Corporation

 Implement the Module

Run Link Export Task

Use the Run Link Export task to manually process an export file from Epi-
cor HCM to an external data system. The first time you use the Run Link
Export task, a full file is created that includes all of the data for all of the per-
sons included in the interface. After the initial file is committed, subsequent
files can be built as full file or changes only.
Whenever the interface is run, it does not change/affect data in the main
tables. Even if the export with which you are working is set up as a scheduled
export, you will still use the Run Link Export task during testing of the integ-
ration.

Navigation Path
Find this task on the Utilities tab.
Process Link Interfaces Link Run Link Export

Run the export as follows:

1. From the Export Master list, select a template.
2. From the Export Group list, select a group.
3. Click the Invalid Data Carrier Feed Report link.

NOTE: If the report reveals any errors, stop this procedure,

correct the data that caused the errors, and then return to
the Run Link Export procedure.
Data validation errors do not prevent the export process
from completing; however, the data that is sent will be
incomplete or incorrect if the errors are not fixed prior to
export.
Functional errors, such as invalid columns, malformed SQL
statements, will cause the export process to fail and must
be resolved to export successfully. This report does not
identify functional errors.

5. In Export Start Date, enter the beginning date of the information to

export.
6. In Export End Date, enter the last date that the information is used
for the export file data.
7. In Export Payroll Date, enter the date of the payroll.

NOTE: This field displays for payroll exports, but does not
appear for other export types.

Epicor HCM | 29
Chapter: 3

5. Select the Full Export check box to create a full export file.
6. Click Run Export. Epicor HCM runs the export process.
7. View the Link Export status box to determine if there are functional
errors in the export that prevent it from completing.

NOTE: If there are errors, return to the Link Configuration

task to correct the functional error.

5. If there are no errors, click Commit Export.

Within the Run Link Export task you can view past exports by selecting val-
ues from the Number of past Export Logs to show and Sort Order lists.

30 | Epicor Software Corporation

 Implement the Module

Configure Link Import

Use the Configure Link Import task to set up import parameters that will trans-
fer data to Epicor® HCM from an external system. Import Masters are a set of
definitions that create a specific type of export for the external system from
which you import data (for example, a payroll system). Each Import Master is
referred to by a unique Import ID code. Import Masters and
After you finish this configuration, you can use the Run Link Import task to pro-
cess the import to Epicor HCM.

IMPORTANT: This task is for advanced Epicor HCM users only.

Use it only if you have received task-specific training from an Epicor
Professional Services Consultant.

Navigation Path
Find this task on the Utilities tab.
Link Data Integration Development Tools Configure Link Import.
The following seven tabs can be used to configure an import from the integ-
ration template that was loaded:

Import Master
The Import Master tab displays the Import Master subtab by default.
Use this subtab to set up definitions that create a specific type of export for an
external system, such as ADP.
1. Click New to create a new Import Master, or select an existing Import
Master from the section list on the left side of the screen to modify it.
2. In Code, enter a unique value.
3. In Description, if languages are enabled, place your cursor in the
field or click the pencil icon to enter or edit a code description.
Otherwise, just type in the Description box. After clicking , the
Multi-Language Edit window appears. Enter information as follows:
a. Select the row for the Language you want to enter or edit the
description.
b. Click the Value field in that row.
c. Type your description in the appropriate language.
d. Click Update to complete your changes.
4. From the Import Type list, select the appropriate type of import.

Epicor HCM | 31
Chapter: 3

5. Select the Import is associated to a specific vendor setup check

box to designate the import setup for a specific vendor.

NOTE: When the check box is selected, the Payroll Vendor

list box appears. Payroll vendors from which to select are
created using the Payroll Vendor Setup task on the Setup
tab.

6. From the Payroll Vendor list, select the appropriate vendor.

7. From the Import Report Entity list, select the type of report entities
you are using for this Import Master.
8. From the Import Processing Class list, select the type of pro-
cessing template to use for this Import Master.
9. Click to continue to the next tab. Click Submit to finish the task.

Import Group
Import groups are a subset of persons you choose to have their information
imported from a designated external system into Epicor HCM through the
Link import utility. Rather than including all persons in every import, you
choose which group to import. An Import Master designates a single import
group to use, and you designate the vendor payroll companys to use for the
group.
Create the import group as follows.
1. Click New to create a new import group.
2. In Code, enter a name for the group.
3. In Description, if languages are enabled, place your cursor in the
field or click the pencil icon to enter or edit a code description.
Otherwise, just type in the Description box. After clicking , the
Multi-Language Edit window appears. Enter information as follows:
a. Select the row for the Language you want to enter or edit the
description.
b. Click the Value field in that row.
c. Type your description in the appropriate language.
d. Click Update to complete your changes.
4. Select the Inactive check box if you no longer use this code but you
want to continue to track it for historical purposes.
5. In the Payroll Vendor Company Selection section, select from the
Available Payroll Companies and move to the Selected Payroll

32 | Epicor Software Corporation

 Implement the Module

Companies box.
6. Click to continue to the next tab. Click Submit to finish the task.

Import Source
Use the Import Source tab to enter information about the actual import file
that is used to populate information within Epicor HCM. As part of an integ-
ration template
1. Select a file. Or, click New to create new import file information.
2. In Description, enter a value to describe the file.
3. Select the Inactive check box if you no longer use this code but you
want to continue to track it for historical purposes.
4. In Default Import Path, enter the path to the location of the import
file. Enter a full path that includes the drive letter and ends with the file
name and file type extension.
5. In File Archive Path, enter the path for your archives.
6. Select the Delimited Flag check box to specify a delimiter within the
import file.
When the check box is selected, the File Delimiter box appears.
7. In the File Delimiter box, enter the delimiter used for the import file
data.
8. Select the File uses text qualifier check box to specify a qualifier
within the import file.
9. In the Text Qualifier box, enter the qualifier used for the import file
data.
10. In Number of header Rows, enter the number of header tows that
the import file will contain.
11. Click to continue to the next tab. Click Submit to finish the task.

Import Date
Use the Import Date tab to describe the import date for the file. This descrip-
tion becomes available on the Run Link Import task, when setting up a
manual import.
1. Select from the list in the left panel. Or, click New to create a new
import date description.
2. In Description, enter a value to describe the import date.
3. Select the Inactive check box if you no longer use this code but you

Epicor HCM | 33
Chapter: 3

want to continue to track it for historical purposes.

4. Click to continue to the next tab. Click Submit to finish the task.

Import Field
Use the Import Field tab to define the various types of fields that the import
file contains. Each field definition specifies the details of one field within
import source type, such as field name, data type, and the field's position in
the export file.
1. Select a field. Or click New to create a new field.
2. In Import Field Name, enter the name of the field in the import file.
3. In Data Type, select Datetime, Numeric or String,.
4. In Start Position, enter the order in which the specified field to
appears in the import file record.
5. In Length, enter the length of the field.
6. Click to continue to the next tab. Click Submit to finish the task.

Import Field Translations

Use the Import Field Translations tab to identify the import field value and the
value it translates into for Epicor HCM.
1. Select an import field from the left pane.
2. In the Import Field Translations grid, click New to create a new trans-
lation for the field.
3. In Source Value, enter the field value from the import file.
4. In Translation Value, enter a value for the HCM translation.
5. Click to continue to the next subtab. Click Submit to finish the
task.

Import Schedule
Use the Schedule tab to set up regularly scheduled times for the Link import
to run.

IMPORTANT: At least one manual import must be run prior to turn-

ing on scheduling.

1. Select the Import Group from the list in the data bar.
2. Select a schedule. Or click New to create a new schedule.
3. In Schedule Name, enter a unique identifier for the schedule.
4. In Start Date, enter the date to begin this schedule.

34 | Epicor Software Corporation

 Implement the Module

5. In End Date, enter the date to end this schedule, if applicable.

6. Select the Enabled check box if you want to immediately enable this
schedule.
7. The Epicor HCM application automatically marks the Current box
Yes if the start date is on or before the current date, and the end date
is later than the current date (or if there is no end date for this record).
8. Select the Commit After Process check box if you want to commit
the data after import.
9. In Notification Email Address, enter an email address that
receives notification of the import. Select the Enabled check box to
allow this notification.
10. In Occurs, select the frequency with which this schedule will run.
Note: Other boxes will appear depending on if your selection was
Daily, Weekly, or Monthly. Fill in these boxes accordingly.
11. In Recurs Every, enter a numeric value. The value you enter here is
used in conjunction with your selection in the Occurs list.
For example, if you selected Daily and entered the number 5, and
then Epicor HCM schedules the export to run every five days.
12. In Run Time, select the time of day for this schedule to run.
13. Click Submit to finish the task.

Epicor HCM | 35