Kronos Import Guide

Workforce Timekeeper ™
Table Format Import

Programmer’s Guide
An administrator’s guide to importing data into the

Workforce Timekeeper database using SQL statements and
import tables.
Kronos Workforce Central Suite

Version 5
Document Part Number: 4703405-001

Document Revision: A
The information in this document is subject to change without notice and should not be construed as a commitment
by Kronos Incorporated. Kronos Incorporated assumes no responsibility for any errors that may appear in this
manual. This document or any part thereof may not be reproduced in any form without the written permission of
Kronos Incorporated. All rights reserved. Copyright 2005.
Altitude, Cambridge Clock, CardSaver, Datakeeper, Datakeeper Central, eForce, Gatekeeper, Gatekeeper Central,
Imagekeeper, Jobkeeper Central, Keep.Trac, Kronos, Kronos Touch ID, the Kronos logo, My Genies,
PeoplePlanner, PeoplePlanner & Design, Schedule Manager & Design, ShopTrac, ShopTrac Pro, StarComm,
StarPort, StarSaver, StarTimer, TeleTime, Timekeeper, Timekeeper Central, TimeMaker, Visionware, Workforce
Accruals, Workforce Central, Workforce Decisions, Workforce Express, Workforce Genie, and Workforce TeleTime
are registered trademarks of Kronos Incorporated or a related company. Altitude Dream, Altitude Pairing, Altitude
PBS, Comm.Mgr, CommLink, DKC/Datalink, FasTrack, HR and Payroll Answerforce, HyperFind, Improving the
Performance of People and Business, Kronos 4500, Kronos 4500 Touch ID, Kronos e-Central, KronosWorks, KVC
On Demand, Labor Plus, Momentum, Momentum Essentials, Momentum Online, Schedule Assistant, Smart
Scheduler, Smart View, StartLabor, Start Quality, Start WIP, Starter Series, Timekeeper Decisions, Timekeeper Web,
VisionPlus, Winstar Elite, WIP Plus, Workforce Activities, Workforce Attendance, Workforce Connect, Workforce
Employee, Workforce HR, Workforce Leave, Workforce Manager, Workforce MobileTime, Workforce Payroll,
Workforce Record Manager, Workforce Recruiter, Workforce Scheduler, Workforce Scheduler with Optimization,
Workforce Smart Scheduler, Workforce Tax Filing, Workforce Timekeeper, and Workforce View are trademarks of
Kronos Incorporated or a related company.
All other trademarks or registered trademarks used herein are the property of their respective owners and are used
for identification purposes only.
When using and applying the information generated by Kronos products, customers should ensure that they comply
with the applicable requirements of federal and state law, such as the Fair Labor Standards Act. Nothing in this
Guide shall be construed as an assurance or guaranty that Kronos products comply with any such laws.
Published by Kronos Incorporated

297 Billerica Road, Chelmsford, Massachusetts 01824-4119 USA
Phone: 978-250-9800, Fax: 978-367-5900
Kronos Incorporated Global Support: 1-800-394-HELP (1-800-394-4357)
For links to information about international subsidiaries of Kronos Incorporated, go to

http://www.kronos.com
Document Revision History
Document Revision Product Version Release Date

A Workforce Timekeeper 5.1 June 2005
Contents
About This Guide

Organization of this guide ............................................................................. 8
Workforce Timekeeper documents ................................................................ 9
Chapter 1: Technical Information About Table Import

About Table Import ..................................................................................... 14
Importing table-formatted data ............................................................. 14
Why run data imports ............................................................................ 15
Importing data with tables .................................................................... 16
Supported imports ....................................................................................... 18
Processing guidelines .................................................................................. 19
Required order of table processing ....................................................... 20
Standard import table columns .................................................................... 21
Request codes ........................................................................................ 21
Required values ..................................................................................... 21
Optional and ignored values ................................................................. 21
USERFIELD column ............................................................................ 22
Specifying column values ............................................................................ 23
Supported data types ............................................................................. 24
Data values ............................................................................................ 24
Data formats .......................................................................................... 25
Shorthand notation ................................................................................ 28
Value restrictions .................................................................................. 31
Table Import ID columns ............................................................................ 32
How SQL statement syntax differs between database types ....................... 33
Syntax for ending INSERT statements and import records .................. 33
Populating Import ID columns .............................................................. 34
Performance efficiencies ............................................................................. 36
Key terms ..................................................................................................... 37
Contents
Chapter 2: Import Table Descriptions and Examples

Accrual Dates Import ...................................................................................40
ACCRUALDATEIMPORT table .........................................................40
Column definitions ...............................................................................40
Required columns ..................................................................................42
Example: How to add or update an accrual date ...................................42
Accruals Import ............................................................................................44
ACCRUALIMPORT table ....................................................................44
Column definitions ................................................................................45
Accruals import examples .....................................................................47
Labor Level Entry Import ............................................................................53
LABLEVENTIMPORT table ................................................................53
Labor level entry import examples ........................................................57
Labor Level Sets Import ..............................................................................62
Labor Level Sets Import table ...............................................................62
Labor Level Set Labor Level Entries Import table ................................65
Specifying labor level entry names .......................................................66
Labor level sets import examples ..........................................................68
Pay Code Edits Import .................................................................................76
PAYCATEDITIMPORT table ..............................................................76
People Import .............................................................................................100
Person Import table ..............................................................................100
Person Date Import table .....................................................................120
Person Many Import ............................................................................126
Predefined data values .........................................................................130
Column population requirements for adding person types ..................130
Adding a person ...................................................................................130
Person Type 1: Workforce Timekeeper Employee ..............................132
Person Type 2: Workforce Employee ..................................................135
4 Kronos Incorporated
Contents
Person Type 3: Workforce Manager ................................................... 138

Person Type 4: Workforce Timekeeper Employee,
Workforce Employee, and Workforce Manager ....................... 140
Workforce Manager .................................................................. 142
Workforce Scheduler Employee ............................................... 145
Workforce Employee, Workforce Scheduler Employee ........... 147
Workforce Scheduler Employee, Workforce Manager ............. 149
Person Type 9: Workforce Timekeeper Employee, Workforce
Employee, Workforce Scheduler, Workforce Manager ............ 152
Scheduler Employee, Workforce Activities Employee ............ 154
Workforce Employee, Workforce Scheduler Employee,
Workforce Activities Employee ............................................... 157
Workforce Activities Employee,
Workforce Scheduler Employee, Workforce Manager ............. 159
Workforce Employee, Workforce Activities,
Workforce Scheduler, Workforce Manager .............................. 162
Person Type 14: Workforce Activities Employee,
Workforce Timekeeper Employee ............................................ 164
Workforce Activities Employee, Workforce Employee ........... 167
Workforce Activities Employee, Workforce Manager ............. 169
Workforce Activities Employee, Workforce Employee,
Workforce Manager .................................................................. 171
Updating a person ............................................................................... 174
People import examples ...................................................................... 180
Workforce Timekeeper Table Format Import Programmer’s Guide 5

Contents
Punch Import ..............................................................................................193

PUNCHIMPORT table ........................................................................193
Column definitions ..............................................................................194
Required columns ................................................................................198
Punch import examples .......................................................................198
Scheduled Pay Code Edits Import .............................................................207
SCHEDPCEIMPORT table .................................................................207
Required columns ................................................................................211
Scheduled pay code edit import examples ..........................................212
Schedule Import .........................................................................................220
SCHEDULEIMPORT table ................................................................220
Schedule import examples ...................................................................232
Appendix A: Required Columns for Request Codes
Appendix B: New Columns in Workforce Central 5.1

New Columns .............................................................................................286
Index
About This Guide
This guide describes Kronos® Workforce Central® import tables and provides
examples of Structured Query Language (SQL) statements that populate the
tables.
This preface contains the following section:
• “Organization of this guide” on page 8
• “Workforce Timekeeper documents” on page 9
About This Guide
Organization of this guide

This guide contains the following information:
• “Technical Information About Table Import” on page 13 provides key
concepts about the SQL-based import process and the structure of the import
tables.
• “Import Table Descriptions and Examples” on page 39 describes the tables
that you can use to bring external data into the tables in the Workforce Central
database. You can enter data into these tables using SQL INSERT statements.
• “Required Columns for Request Codes” on page 273 contains a list of the
required columns for each import table.
• “New Columns in Workforce Central 5.1” on page 285 contains a list of the
new columns for this release
Workforce Timekeeper documents

The following documentation is available to help you install, maintain, and use
the Workforce Timekeeper database and software:
• Workforce Central Planning for Installation provides an overview of the
Workforce Timekeeper architecture, outlines the system requirements,
explains how to install the product’s server and client components, and
includes licensing and upgrade requirements.
• Workforce Central System Administrator’s Guide provides an overview of the
system architecture, explains system administration tasks, and tells how to
work with logs and reports.
• Getting Started with Workforce Timekeeper—A Managers Guide for Power
Users summarizes the most common manager tasks, which include using
Workforce Genies, Timecards, Reports, and the People Editor.
• Getting Started with Workforce Timekeeper—A Guide for Managers
summarizes key product features for people who access employee time and
attendance information. The book also explains the various Workforce
Timekeeper components and the most common tasks that managers are likely
to perform with each component.
• Getting Started with Workforce Timekeeper—An Employee Guide for Power
Users explains some of the most common employee tasks, which include
using the Timecard and Time Stamp components, as well as viewing personal
schedules and reports.
• Getting Started with Workforce Timekeeper—A Guide for Employees explains
some of the most common employee tasks in Workforce Employee- HTML
Client, which includes using the Timecard, Time Stamp, and Quick Time
Stamp components, as well as viewing personal reports.
• Workforce Record Manager Installation Guide includes installation and
configuration instructions for Workforce Record Manager, the Setup Data
Manager, and the non-production databases and application servers that make
up the Workforce Record Manager environment.

About This Guide
• Workforce Record Manager User’s Guide primary use is for customers and
service personnel who use Workforce Record Manager and the Setup Data
Manager to copy data from one Workforce Central database to another. It
contains instructions for creating, running, and scheduling Workforce Record
Manager jobs and for administering the Workforce Record Manager
environment.
• Workforce Timekeeper Quick Reference to Schedule Groups explains major
changes to how schedule groups work in the current version of Workforce
Timekeeper, as opposed to how they worked in earlier versions.
• Workforce Central Process Manager Programmer’s Guide—Timekeeping and
Scheduling provides information on how to configure the Workforce
Timekeeper and Workforce Scheduler process templates.
• Workforce Central Process Manager/Messaging Database Tables Reference
Guide is an addendum to the Workforce Timekeeper Database Views
Reference Guide that specifically deals with Process Manager and Messaging
specific database tables.
• Workforce Central Process Manager Programmer’s Guide tells how to use
Process Manager to configure, implement, and maintain automated business
processes across an organization.
• Workforce Central System Administrator’s Guide—Timekeeping describes the
administrator’s activities, such as system configuration and setup, and
working with log reports, predefined data, and diagnostic tools.
• Workforce Timekeeper Database Tables Reference Guide contains details
about the Workforce Central database tables.
• Workforce Timekeeper Database Views Reference Guide provides information
and details about Views and how they are used as virtual tables in Workforce
Central.
• Workforce Central Database Administrator’s Guide explains how to maintain
the Oracle and SQL Server 2000 databases for Workforce Timekeeper. This
guide includes procedures for backing up databases, restoring and recovering
databases, adjusting performance, and using maintenance utilities.
• Workforce Timekeeper Table Format Import Programmer’s Guide provides
instructions and table data for Workforce Timekeeper Import tables.
• Workforce Central Import User’s Guide provides information about setting up

and running XML and table imports for labor management systems. It
describes the Transaction Assistant used to correct failed XML import data.
• Workforce Timekeeper XML Import Programmer’s Guide provides
information that specifically addresses XML import issues, and includes
descriptions of all of the tags, actions, and properties used by import
transactions.
• Workforce Timekeeper XML Export Programmer’s Guide addresses XML
export issues, and includes descriptions of all of the tags, actions, and
properties used by export transactions.
• Guide to Translating and Customizing Workforce Central provides
instructions for editing the browser-based graphical user interface, the Setup
applications user interface, and the associated browser-based Help files for
Workforce Timekeeper and Workforce Scheduler.
• Developer’s Toolkit documentation: Workforce Timekeeper includes an
Application Program Interface (API) that you can use to access certain
Workforce Timekeeper features from application programs. The Workforce
Central Developers Toolkit Programmer’s Guide includes annotated sample
programs that show how to use the API, and the Workforce Central
Developers Toolkit Reference Guide—Timekeeping provides detailed
information about each element of the API.
• Online Help for the Workforce Timekeeper system is installed automatically
with the product. To access online Help: click the Help link at the bottom of
the navigation bar, or click the Help icon in the component, or click the Help
button in a dialog box.
• Release notes provide additional information about Workforce Timekeeper,
including a list of new features, resolved issues, and late-breaking changes.

About This Guide
Chapter 1
Technical Information About Table Import
This chapter contains information that is of interest to a developer who is using

Table Import to import data into Workforce Central. It contains the following
sections:
• “About Table Import” on page 14
• “Supported imports” on page 18
• “Processing guidelines” on page 19
• “Standard import table columns” on page 21
• “Specifying column values” on page 23
• “Table Import ID columns” on page 32
• “How SQL statement syntax differs between database types” on page 33
• “Performance efficiencies” on page 36
• “Key terms” on page 37
Chapter 1 Technical Information About Table Import
About Table Import

The Table Import process enables you to move table-formatted data into the
Workforce Central database.
Note: Workforce Central v5.1 does not support file-type data, such as electronic
data interchange (EDI).
Importing table-formatted data

Table Import is used as a means of transferring data from an external data source
into the Workforce Central database. Table Import uses tables that have prescribed
structures that properly format and order the external data to be imported. An
import (either scheduled or manual) is used to transfer the table-formatted data
into the Workforce Central database. A batch consists of one or more tables that
are processed as a single unit.
When the batch import runs, Table Import validates all the data in a table to ensure
conformance with Workforce Central rules and constraints. Any record that fails
validation is not imported and remains in the import table. Error messages are
generated to explain why a record failed validation. You can view the error
messages using reports.
About Table Import
Why run data imports

When you import data from other business systems to the Workforce Central
database, you can re-use large volumes of data without having to re-enter it. For
example:
• Workforce Central startup—You can import data, such as employee data,
from an existing system to your new Workforce Central database, eliminating
the task of manually entering it into Workforce Central.
• Synchronize data from another source—You can share data from outside
data sources, such as payroll or human resources systems, with Workforce
Central, to ensure that all your business systems are working with the same
information. For example, as new data is added, changed, or deleted in
outside sources, the corresponding data will also be added, changed, or
deleted when imported to Workforce Central.
• Provide a single point of entry for database information—When you
import existing data into Workforce Central, you only have to enter data once.
Apart from saving a significant amount of time in not having to re-enter data,
you also avoid introducing errors into the Workforce Central database because
the data that you are importing is in use and has already been validated.
Accessing the Table Import workspace
You can access Table Import by browsing the Web from a remote client to the
Workforce Central server. To use Table Import:
• Navigate to Common Setup > Table Import.
• Set up and schedule imports or run them at your convenience.
You can then monitor the status of your scheduled batch import or on-the-fly
import by running the Statistics report. Review this report first to see if the results
of the import indicate a successful run in general. If the import ran for the
expected length of time and did not create an unusually large number of errors, it
is probably a successful run. The report lists the name and type of the import, the
total records that were successfully imported, total records that failed, the status at
the time the report was generated, and the duration.

Importing data with tables

You can import data in table format to the following databases:
• Oracle
• SQL Server
Importing data is a three-step process that requires you to export data from an
external database on an external system before you import data into the Workforce
Central database.
1. Extract data from an external application, such as a payroll or human
resources system. You may use a traditional export operation or you may have
an integration tool that supports transferring records from the external
database. See the documentation for the application that is the source of your
data for more information about this process.
2. Populate the import tables. You can do this using the following methods:
– Use Workforce Connect or another integration tool to output the data to
the import tables. Refer to the documentation for your integration tool for
more information.
– Use SQL INSERT instructions in an appropriate SQL editor for your
database. You can set up a third-party integration tool to create the
statements. For example, you can use SQL*Plus for Oracle databases,
Query Analyzer for SQL 2000 databases, and DB2 Command Center,
Command Line Processor, or command window for DB2 databases. Refer
to the vendor documentation for your application for more information.
The Insert statement does the following actions:
a. Defines the structure of the data by identifying each of the columns that is
to have a value.
b. Inserts values into the table import columns in the exact order in which
you defined the columns when you set up the structure. Use the examples
in “Import Table Descriptions and Examples” on page 39 as guidelines
for creating INSERT statements. Also refer to the documentation for your
relational database management system (RDBMS) for details about using
the Insert command.
About Table Import
3. Import the data from the import tables into the Workforce Central database.
You can import using a regularly scheduled batch import or run an
unscheduled import, selecting specific tables to include in the import. Refer to
the Workforce Timekeeper Import User’s Guide for more information about
these procedures.

Supported imports
Table Import supports the following types of imports:
Import Name Purpose

Accruals Add or modify employee accrual balances, such as
vacation or sick time.
Accrual Dates Add or modify employee-specific dates that affect accruals
for that employee.
Labor Level Entries Add or modify labor level entries. A combination of labor
level entries constitutes a labor account.
Labor Level Sets Add or modify labor level sets and the labor level entries
associated with a labor level set.
Pay Code Edits Add or subtract the specified number of hours or amount of
money associated with a pay code (including historical
adjustments) or a pay rule.
People Add or modify employee or user data.
Punch Add or delete employee punches.
Schedule Add or delete scheduled shifts for employees.
Scheduled Pay Code Add or delete scheduled pay code edits for employees.
Additional importable data, such as Workforce Scheduler and Workforce

Activities data and organizational map data, are available through XML import.
Refer to the Workforce Timekeeper XML Import Programmer’s Guide for details.
Processing guidelines
Processing guidelines
• Imported records are processed internally in a logical order using the
following assumptions:An employee must exist in the database before
importing the following data:
– Personal information, such as postal and e-mail address information,
telephone numbers, employment status, badge assignments, expected
hours, home account assignments, base wage, hire date, or a license
assignment
– Access assignments
– Punches, pay code edits, schedules, activities, or accruals
• A labor level set must exist before importing labor level entries to it.
• A pay rule must exist before importing pay code edits.
• A pay code, labor account, job hierarchy, or comment must exist before
referencing it.
• Tables that require an employee identification field process all the records for
a single employee together, regardless of which import table contains the
records.
• Changes made to data in a record during the import process affect how you
refer to the record later in the process. The processing order is determined
internally. The processing order is reflected in the descriptions, restrictions,
requirements, and optional values of individual tables and columns specified
in “Import Table Descriptions and Examples” on page 39.
Example
Employee J.D. Smith’s identification number was changed from 1234 to 4321 in
the Person Import table. In addition, J.D. Smith has import entries in the Punch
Import table. The new identification number is processed first. Therefore, all
imported punches that follow for J.D. Smith must use 4321 as the identification
number.

Required order of table processing

If you are setting up a batch import, set up the batch to process the tables in the
following order:
• Labor Level Entries
• Labor Level Sets
• People
• Accrual Dates
• Accruals
• Punches
• Pay Code Edits
• Scheduled Pay Code Edits
• Schedules
Standard import table columns
Standard import table columns

All import tables contain the following columns:
• Request code (REQ_CODE)—Specifies how to process the imported data.
• USERFIELD—Contains comments or notes.
Request codes
The Request Code (REQ_CODE) column specifies the import action. A request
code value is required for every import operation.
Table Import reads and processes data from the import tables according to the
value in the Request Code column. Request code values range from 1 to 41.
Required values
In addition to a request code, which is required for every import operation,
specific request codes require valid data in other columns of the table that you are
importing. An import process fails if a value is missing from a required column.
You can find information about the request codes and required columns in two
sections of the “Import Table Descriptions and Examples” on page 39.
• Read the complete table and column definitions for each table
• Refer to the numerical list of request codes.
Optional and ignored values

Columns that are not required are either optional or ignored:
• Optional column values can be null or contain data.
• Ignored columns contain data that is not applicable to the records that are
being imported. Loading a value into the column does not affect the import.

USERFIELD column
The USERFIELD column of each import table contains comments or notes about
an import entry. The value in this column can be any string value. This column is
optional; the values are not used in the import.
Information in the USERFIELD column might be used to indicate the date a
record was exported from a host application or the origin of the data. The
Workforce Central administrator might use this information if the import failed
for any reason.
Specifying column values

When you import the data into the database with SQL statements, ensure that the
values and formats that you intend to import into the database are valid for the
column. Workforce Central verifies that the values that you enter for the column
are valid. If the value being imported does not correspond to a value in the
database or to the value format, the import of the record fails.Example
The data for J.D. Smith in the People Import tables includes a column for the pay
rule with the value of “Weekly.” If the pay rule value of “Weekly” was never
created in Workforce Central, an error message is created that indicates the pay
rule does not exist; the entire record for J.D. Smith is not imported.
The “Columns, data types, and null contraints” sections for each import table
contain the following column details:
• Column names
• Data type for each column
• Null constraint for the column
• Comments
Not all columns include comments. However, if there is significant information
about using the column, the information is included as a comment. For some
columns, the information is explained further in the “Column Definition” section
that follows the column details.

Supported data types

Data that is imported to import tables must be either a character or integer format.
In the “Columns, Data Types, and Null Constraints” sections for each import
table, the following labels describe data types in the databases that Table Import
supports, as follows:
Data Type Oracle Term SQL Server Term DB2 Term

Integer Number(x) Int Int
Character VarChar2(x) VarChar(x) VarChar
Data values
Specify all import entry values, including those for date, time, and currency, as
character strings. The import process converts character strings to their
corresponding internal data types.
Data loaded into tables must match the format of the various Workforce Central
settings, depending on the specific data in question. Records that contain data that
is not formatted in accordance with the Workforce Central setting will not be
imported.
Selected data appears on the Workforce Central workspace are determined by
Configuration Applications settings. Other data formats are specified by the
application server used, as indicated under the System Configuration > System
Settings options. Local browser client show settings or Windows regional settings
should match these settings.
Refer to the Workforce Central System Administrator’s Guide for details.
In multiserver environments, one server per language is required. If the language
is English, French, or Spanish, you can make the selection during installation.
Specify other languages or locales under System Configuration > System
Settings. In an import, specify the server that has the correct localized settings for
the employment site in order to view the results in the correct language, times, and
amounts.
Data formats
The following sections describe the common formats and how you can expect to
view them.
Amounts and durations
Amounts and durations refer to the length of time. Format is shown with a colon
(:) separator or a decimal (.) separator. For example, six hours and 30 minutes can
be 6:30 or 6.5.
Amounts and duration type data should be formatted using the hours and minutes
that are specified during installation using the Setup Applications > Display
Profiles settings. Specify the Duration Display on the Edit Display Profile dialog
box.
Imports of amount and duration records should be formatted in the date format of
the application server that is used to process imports.
Entries in the import tables that do not correspond to this format generate errors
when the record is imported.
Currency
Currency includes currency units (dollar, pound, peso, and so on) and currency
format (symbol, number of decimal places, positive and negative entries).
The currency unit is set in Workforce Central System Configuration and stored in
the WFCSite.properties file. If no information is entered in these settings, the
currency setting is based on the country selected during the installation.
The currency unit is based on the language that you select at installation: the
American dollar for English, the Canadian dollar for French, and the Mexican
peso for Spanish. You can change the default setting for a currency by modifying
your system’s site-specific settings. See your Workforce Central System
Administrator’s Guide for details about modifying these settings.

Note: Only one currency unit is supported for a database. Although multiple
language servers can provide imported data to a database, only one currency is
supported in the database. Any modified currency settings should be configured
before you begin import operations.
The format of imported currency data should reflect the currency format that has
been defined in the application server regional settings. Entries in the Import table
that do not have this format generate errors when the record is imported.
Currency format can be adjusted for the currency unit. For example, if the
localized setting uses a period as the decimal separator, 10.25 represents $10.25,
and 1250.55 represents $1250.55 in American dollars. However, in Canadian
dollars, the amount appears as $1250,55 because the comma is the default
Canadian decimal separator.
The format for the currency symbol and separator corresponds to the selected
country and language. For example, if you specify CA (Canada) for the country
and en (English) for the language, the period is the separator. If you specify fr
(French), the comma is the separator.
You can import whole dollar amounts without using the currency symbol or decimal separator;
for example, you can import $25.00 as 25. Dates
When importing records that contain dates (for example, a punch import that
requires a date in the PDATE column), the date should be formatted in the date
format of the application server that is used to process the import.
Entries in the Import tables that do not use this format generate errors when the
record is imported.
You can set the date format in Workforce Central in the following location: System
Configuration > System Settings > Local Values tab. Labor accounts
Enter data for labor accounts in the same format as they appear in Workforce
Central. Separate each of the levels with a forward slash (/).
Example
The labor account format might be “Division/Department/Job” in Workforce
Central. For a seven-level labor account in the Workforce Central configuration,
specify the labor account in a format similar to the following:
Level1 / Level2 / Level3 / Level4 / Level5 / Level6 / Level7
Note: Table Import allows several shorthand notations for labor account entries.
Refer to the section “Shorthand Notation” in this chapter for details.
Time format
You can show time in 12-hour segments or 24-hour universal time, depending on
the format specified in Workforce Central Setup > Display Preferences >
Display Profiles.
When importing records that contain times (for example, a punch import that requires a time in
the PTIME column), the time must use the format on the application server that is used to
process the import. Entries in the Import tables that do not correspond to this format generate
errors when the record is imported.Time zones
Time entries associated with a punch should be formatted using the time based on
the time zone value specified for the employee unless an explicit time zone value
is provided with the punch.
When you are importing a person, the time zone is specified by entering the five-
digit ID number associated with the time zone or the exact name of the time zone.
See “Time Zone Definitions” in Appendix B of the Workforce Timekeeper
Database Tables Reference Guide.

Ad hoc labor level entries
The Workforce Central administrator can configure a system to allow the addition
of ad hoc labor level entries, which are new labor level accounts added when
punches are added during Punch Import. This method is an alternate way to add
labor level entries; however, using Workforce Central Setup is recommended.
Ad hoc labor level entries are permitted under the following conditions:
• The labor level entry must be associated with a labor level that permits the
entry of a new labor level entry. You can configure this in the Workforce
Central Setup.
• The labor level entry can be validated as a labor level entry. For example, the
entry meets the string length requirements or does not contain illegal
characters or both.
Additional data formats
Enter the names of labor level names, pay codes, pay rules, work rules, group
schedules, accrual profiles, accrual codes, accrual date names, and wage profiles
as they appear in the Workforce Central configuration. These names are case-
sensitive.
Shorthand notation
Shorthand notation simplifies the process of importing values. Use shorthand
notation with the following guidelines:
• New information must be entered into an import table in its entirety.
• Shorthand notation might not be allowed for a required field. Always review
the description in the Workforce Timekeeper Import Guide: Table Format
manual for restrictions.
You can use the following shorthand notations to update value entries in a table:
• @ (the “at” sign)—Can be used in the following import tables to retain the
currently stored value in a column for the record being updated: Accrual
Dates Import, Labor Level Entries Import, Labor Level Sets Import, and
People Import. Do not use the @ shorthand notation for labor accounts,
organizational jobs, or the primary organizational job.
Note: You can use the @ shorthand notation only for single-element column
values–not within multi-element values, such as labor accounts or Primary
labor accounts. However, you can use @ for the primary organizational job.
• # (the number sign)—Used in tables to indicate that the value should change
to null (a blank). Do not use the # shorthand notation for labor accounts,
organizational jobs, or the primary organizational job.
• @H (the “at” sign followed by uppercase H)—Used within labor account
data that you are updating to indicate that the entry for a specific labor level is
the same as the corresponding entry in the employee’s Primary labor account,
organizational jobs, or the primary organizational job. For example:
Change account: 101/201/301/401/501/601/701

To account: 101/201/302/401/501/601/701
Enter: @H/@H/302/@H/@H/@H/@H
You can use the @H shorthand notation in the following import tables: Pay
Code Edits Import, Punch Import, Scheduled Pay Code Edits Import, and
Schedule Import.
Note: You cannot use shorthand notations when you are entering a new
person using the Primary Labor Account column or the in the Person Date
Import table; however, you can use shorthand notations to update existing
people.
For example, the shorthand @/@/New Entry/@ or @H/@H/New Entry/@H

is invalid for a new labor level. However, the shorthand @H/@H//New Entry/
@H or //New Entry/ imports the data correctly.

• @P (the @ sign followed by uppercase P)—Used for the person’s existing

primary organizational job. You can substitute the @P, as follows in the
ORGPATHTXT column in the following tables:
– In People Import, when the person’s primary job has not changed. For
example, if the person’s complete organizational path is Organization/
Hospital A/OR/Scrubs/RN1, use @P to replace the person’s existing
primary organizational job. Do not use @P for individual locations or
jobs in the organizational path. For example, @P/Hospital B/@P/@P@P
is invalid.
– In Punch Import, Schedule Import, Scheduled Pay Code Edit Import,
punch, and Pay Code Edit Import to substitute for the person’s existing
primary job.
• Blanks—Use the blank to indicate that a labor level within a labor account,
including the primary labor account, is unchanged when you are importing a
transfer. In the following example, only the first and third labor level entries
are different:
Change account: 112/222/332/401/501/601/701

To account: 113/222/333/401/501/601/701
Enter: 113//333////
You can use the blank in the following import tables: Punch Import, Pay Code
Edits Import, Scheduled Pay Code Edits Import, Schedule Import, and Person
Date Import.
Value restrictions
Table Import generates error messages when values do not match the expected
data types and formats. To avoid data rejection, use the following guidelines:
• Provide values in the tables that match the format of the Windows Control
Panel regional settings on the Workforce Central Web server.
• Do not use the reserved words or symbols of your relational database
management system (RDBMS). You cannot import reserved words and
symbols into the fields of an import table.
For example, the ampersand (&) is a reserved symbol in the Oracle RDBMS,
so you cannot use an ampersand in the name of a work rule. Refer to the
documentation of your RDBMS for more information about reserved words
and symbols.

Table Import ID columns

Each import requires a unique value (Import ID) to identify an import record. In
most cases, this value is automatically generated by the database when a row is
inserted in the import table. The following table lists the import table names and
the name of the column in each table that holds the import ID:
Import ID
Import Type Table Name Column Name
Accrual Dates ACCRUALDATEIMPORT ACCRUALDATEIMPID
Accruals ACCRUALIMPORT ACCRUALIMPORTID
Labor Level Entries LABLEVENTIMPORT LLEVNTIMPID
Labor Level Sets LLSETIMPORT LLSETIMPORTID
Pay Code Edits PAYCATEDITIMPORT PAYCATEDITIMPID
People PERSONIMPORT PERSONIMPORTID
Punch PUNCHIMPORT PNCHIMPID
Scheduled Pay Code Edits SCHEDPCEIMPORT SCHEDPCEIMPID
Schedules SCHEDULEIMPORT SCHEDIMPID
For SQL Server and DB2, the value for the import ID column is automatically
generated by the database when a row is inserted in the import table. For Oracle
databases, you must specify a value in the SQL Insert statement. See “Populating
Import ID columns” on page 34.
Note: Imports encompassing multiple tables, such as the People Import and Labor
Level Sets Import, do not have Import ID column values automatically generated
by the database.
How SQL statement syntax differs between database types
How SQL statement syntax differs between database

types
How you enter SQL statements varies slightly, depending on which type of
database your system uses: SQL Server, Oracle, or DB2.
Syntax for ending INSERT statements and import records
Oracle and DB2
When writing SQL statements for Oracle and DB2 databases, you must do the
following actions:
• End each statement with a semicolon (;).
• Include a Commit; statement at the end of the set of INSERT instructions
that comprise an import record.
Example
Insert into PERSONIMPORT (PERSONIMPORTID, REQ_CODE,
PERSONTYPE, PERSONNUM, LASTNAME, PAYTRULE, USERFILELD)
Values (1,'1', '1', '8001', 'Jones', 'Support',
'Minimal Employee');
Insert into PERSONDATEIMPORT (PERSONIMPORTID,
RECORDTYPE, STARTDATE, ENDDATE, HOMELABORACCOUNT)
Values (1, '3', '3/29/2001', '', '101/201/301/401/501/
601/701');
Commit;

SQL server
The syntax for writing SQL statements for a SQL Server database is the same as
the syntax for Oracle and DB2 databases except for the following:
• Do not include the semicolons at the end of INSERT instructions.
• Do not include a Commit; statement at the end of the import record.
Populating Import ID columns

How you populate Import ID columns differs, depending on which type of
database your system uses: SQL Server, Oracle, or DB2. (For more information
about Import ID columns, see “Table Import ID columns” on page 32.)
Oracle database
Oracle Import ID columns require you to specify a valid sequence value as the
Import ID within a SQL Insert statement. The following table shows the values to
use for each import table:
Table Name Import ID Column Value

ACCRUALDATEIMPORT ACCRUALDATEIMPID NGP_ACCRUALDATEIMPORT.NEXTVAL
ACCRUALIMPORT ACCRUALIMPORTID NGP_ACCRUALIMPORT.NEXTVAL
LABLEVENTIMPORT LLEVNTIMPID NGP_LABLEVENTIMPORT.NEXTVAL
LLSETIMPORT LLSETIMPORTID NGP_LLSETIMPORT.NEXTVAL
PAYCATEDITIMPORT PAYCATEDITIMPID NGP_PAYCATEDITIMPORT.NEXTVAL
PERSONIMPORT PERSONIMPORTID NGP_PERSONIMPORT.NEXTVAL
PUNCHIMPORT PNCHIMPID NGP_PUNCHIMPORT.NEXTVAL
SCHEDPCEIMPORT SCHEDPCEIMPID NGP_SCHEDPCEIMPORT.NEXTVAL
SCHEDULEIMPORT SCHEDIMPID NGP_SCHEDULEIMPORT.NEXTVAL
How SQL statement syntax differs between database types
Example
Insert into SCHEDPCEIMPORT (SCHEDPCEIMPID, REQ_CODE,
EMPID, SDATE, STIME, AMOUNT, PAYCAT)
Values (NGP_SCHEDPCEIMPORT.NEXTVAL,'1', '4321', '9/5/
01', '3:00 PM', '3:00', 'Regular');
Commit;
SQL server or DB2 database
For all import types except Labor Level Sets Import and People Import, you do
not need to specify a value for Import ID columns on a SQL Server or DB2 UDB
database. When you run the SQL Insert command, it automatically generates an
incremental value for each table entry.
The following example is the same as the example presented for Oracle and DB2
databases, but presented using the syntax for SQL Server. The difference is that
the SCHEDPCEIMPID column is not included in the statement.
Example
Insert into SCHEDPCEIMPORT (REQ_CODE, EMPID, SDATE,
STIME, AMOUNT, PAYCAT)
Values ('1', '4321', '9/5/01', '3:00 PM', '3:00',
'Regular')
Note: When importing labor level sets or people (see “Import Table Descriptions
and Examples” on page 39), you must populate the Import ID column.

Performance efficiencies
You can manipulate import operations to improve performance in the following
ways:
• A unique user name, Import, and password is available for database
administrators or other users who log on to Workforce Central for the specific
purpose of importing data. The unique user name and password improves
performance and makes importing data faster because the system bypasses the
security privileges check associated with users who log on with a user name
and password that gives them access rights to other areas in Workforce
Central.
• Some tables require data to be regenerated for totalizations. The timing of the
totalization can affect the performance of the import. For this reason, you
might choose to stop the background processor from running during an import
and restart it after the import has completed. For example:
– If an accrual import, an accrual date import, or a pay code edit impacts an
employee’s data with a series of entries, such as an accrual date entry,
several punches, and a pay code edit, you can achieve better performance
by regenerating the totals after all entries have been imported.
– If an employee typically enters multiple punches per day, you can
increase the speed of the import by regenerating the totals after all
punches have been imported.
Key terms
Key terms
The table descriptions and examples in this guide use the following abbreviations
and terms. For more information about terms that are specific to Workforce
Central, see the online Help.
data type
A set of data with values having predefined characteristics. Examples of data
types are: integer, floating point unit number, character, string, and pointer. Each
database vendor may have a specific term for data that has the same
characteristics. For example, the terms Number, used by Oracle, and Int, used by
SQL Server and DB2, refer to integer data types. For more information about data
types that are supported in your database, see the documentation for your
relational database management system.
import record
A collection of data items arranged for processing. All elements of an import
record must validate for the import record to be imported. Otherwise, the
complete import record is not imported. Typically, an import record is a single
row of data in an import table; however, there are some exceptions, as follows:
• People Import—An import record consists of one row in the
PERSONIMPORT table, zero or more rows in the PERSONDATEIMPORT
table, and zero or more rows in the PERSONMANYIMPORT table.
• Labor Level Sets Import—An import record consists of one row in the
LLSETIMPORT table and zero or more rows in the LLSETLLEIMPORT
table.
• Schedule Import—When adding a shift, an import record consists of
multiple SCHEDULEIMPORT table rows.
not null constraint

A column constraint that determines whether that column can contain null values.
In this guide, the Null Constraint column in the Columns, Data Types, and Null
Constraints table uses “Null” to indicate that null values are allowed in that
column. “Not Null” indicates that a column is not a null constraint and null values
are not allowed within the column.

primary key
An attribute or a set of attributes that uniquely identify a specific instance of an
entity. It must have a non-null value for each instance of the entity, the value must
be unique for each instance of an entity, and the values must not change or
become null during the life of each entity instance. A badge number or a Social
Security number might be a primary key.
schema
Defines the tables, the columns in each table, and the relationships between the
columns and tables. The Workforce Central database can have several different
schemas, depending on which Kronos products are installed.
segment
A portion of a scheduled shift. The beginning or end of a segment is triggered by a
scheduled event such as a work rule transfer.
As an example of a scheduled segment, assume that an employee is scheduled to
work from 5:00 p.m. to 10:00 p.m. every Tuesday night. In addition, this
employee is scheduled to make a work rule transfer at 7:00 p.m. during these
shifts.
This employee’s shift contains two segments. One segment extends from
5:00 p.m. to 7:00 p.m. Another segment, associated with the work rule transfer,
extends from 7:00 p.m. to 10:00 p.m.
SQL
Structured Query Language (SQL) is a language used to define, query, modify,
and control the data in a relational database.
The table import process uses SQL statements to insert data into the import tables.
Chapter 1
Import Table Descriptions and Examples
Workforce Central uses import tables to hold the data that you want to merge into
the Workforce Central database. Your relational database management system, or
RDBMS, such as Oracle or SQL Server, dictates the record format required within
these tables. You import data from the import tables to the Workforce Central
database tables using Import.
This chapter describes the tables that you use to import employee data to the
database. The following information is provided for each import table:
• Table descriptions
• Table column names, data types, and data string lengths
• Null constraints
• Definitions for each column
• Required columns for request codes
• Examples of SQL INSERT instructions that insert data into the import table
Chapter 1 Import Table Descriptions and Examples
Accrual Dates Import
ACCRUALDATEIMPORT table
The Accrual Dates Import table enables import of employee accrual dates. An
accrual date is associated with an accrual event, such as vacation time earned or
sick leave taken.
You can perform the following import operations:
• Add accrual date entries
• Update accrual date entries
• Add or update accrual date entries
Columns, data types, and null contraints
Column Name Data Type Null Constraint Comments

ACCRUALDATEIMPID Integer Not null Automatically populated (except
for Oracle databases)
REQ_CODE Character(2) Not null See “Column definitions” on
page 40 for specific values.
EMPLOYEEID Character(15) Not Null
DATENAME Character(50) Not Null
ACCRUALDATE Character(10) Not Null
USERFIELD Character(50) Null
Column definitions
ACCRUALDATEIMPID
The Accrual Date Import ID column is the primary key of the

ACCRUALDATEIMPORT table. The Accrual Date Import ID column establishes
a unique sequence number for each entry that goes into the
ACCRUALDATEIMPORT table.
This column is always required when you insert an accrual date entry in an Oracle
database. A value for this column is automatically generated when you insert an
accrual date entry into a SQL Server or DB2 database.
REQ_CODE
The Request Code column indicates the action that you want to perform. This
column is always required.
Value Description
1 Add an accrual date entry.
2 Update an accrual date entry.
3 Add or update an accrual date entry.
EMPLOYEEID
The Employee ID column contains the ID number of the employee for whom the
accrual transaction is being imported. This column is always required.
DATENAME
The Date Name column contains the name of the date being imported for the
employee. The value in the DATENAME column must match the employee-
specific date name that already exists in the Workforce Central database. This
ACCRUALDATE
The Accrual Date column contains the date of the accrual date name being
imported. This column is always required.
USERFIELD
The Userfield column of each import table contains comments or notes about an
import entry. The value in this column can be any string value. This column is

Required columns
REQ_CODE 1, 2, 3
A REQ_CODE value is required for any import operation. The request codes 1, 2,
and 3 also require that the following columns have a value:
• ACCRUALDATEIMPID (Oracle only)
• EMPLOYEEID
• DATENAME
• ACCRUALDATE
Example: How to add or update an accrual date

The example in this section demonstrates how to add or update a new accrual date
entry in the ACCRUALDATEIMPORT table. To perform that function, enter the
SQL Insert command by following these guidelines:
1. Specify ACCRUALDATEIMPORT as the data’s destination table.
2. Identify all the columns that will be receiving data, in the order in which they
appear in the table.
Each table has columns that require you to specify a value. The
ACCRUALDATEIMPORT table requires you to specify values for new pay
code edits as follows:
– ACCRUALDATEIMPID
– REQ_CODE
– EMPLOYEEID
– DATENAME
– ACCRUALDATE
3. Specify the values to be placed in the columns that you identified.
4. Sample SQL Server statement
SQL Server database
The following example uses request code 3 to add or update an employee’s

accrual date:
Insert into ACCRUALDATEIMPORT (REQ_CODE, EMPLOYEEID,
DATENAME, ACCRUALDATE)
Values ('3', '4321', 'Date of joining health plan', '9/
15/99')
The following table shows the significance of each value that is used in this SQL
Insert statement:
Column Value Significance

REQ_CODE 3 Adds or updates an accrual data entry record.
EMPLOYEEID 4321 Identifies the employee’s ID number.
DATENAME Date of joining Identifies the name of the date.
health plan
ACCRUALDATE 9/15/99 Identifies the accrual date imported.
Oracle and DB2 databases
The SQL INSERT instructions for Oracle and DB2 databases resemble the
previous SQL Server database example except for the semicolon (;) needed at the
end of each statement and the ending commit statement (Commit;).
Oracle databases require that the ACCRUALDATEIMPID column and its value
be listed as the first column and value in the SQL Insert statement. The value is
NGP_ACCRUALDATEIMPORT.NEXTVAL.
Testing the statement
If the Insert statement runs successfully, verify that the record that adds the
accrual date to the database is included in the ACCRUALDATEIMPORT table.
To do this, issue a Select statement similar to the following command:
Select * from ACCRUALDATEIMPORT where EMPID = '4321'

Accruals Import
ACCRUALIMPORT table
The Accrual Import table enables the import of accrual information. An accrual
item might be vacation time or sick leave that was earned or taken. You can
perform the following import operations on a select set of accruals:
• Add an earned accrual amount for an employee
• Reset an employee’s accrual balances for an employee with an accrual profile
You cannot import the following accrual types. Instead, enter these accruals
directly.
• Transfer hours from a pool to a specific employee
• Transfer hours from or into a pool or group
• Suspend or reinstate accrual

ACCRUALIMPORTID Integer Not null Automatically populated
(except for Oracle databases)
REQ_CODE Character(2) Not null See “Column definitions” on
EMPLOYEEID Character(15) Not Null
ACCRUALCODE Character(50) Not Null
POSTINGDATE Character(10) Null Obsolete
POSTINGTIME Character(8) Null Obsolete
EFFECTIVEDATE Character(10) Null
AMOUNT Character(30) Not Null See “Column definitions” on
PROBATIONAMOUNT Character(15) Null
Accruals Import
Column definitions
ACCRUALIMPORTID
The Accrual Import ID column is the primary key for the ACCRUALIMPORT
table. The Accrual Import ID column establishes a unique sequence number for
each entry that goes into the ACCRUALIMPORT table. In a SQL Server or DB2
database, a value for this column is automatically generated when you insert an
accrual entry.
REQ_CODE
Value Description
16 Resets the employee’s accrual balance to the value in the AMOUNT column.
17 Adds an earned accrual amount, as either a positive or negative amount in the
AMOUNT column.
EMPLOYEEID
The Employee ID column contains the ID number of the employee for whom the
accrual transaction is being imported. This column is always required.
ACCRUALCODE
The Accrual Code column contains the accrual code associated with the accrual
transaction. The accrual code must be created in Workforce Timekeeper and
assigned to the employee before you can import data against it. This column is
required.

POSTINGDATE
The Posting Date column is obsolete. Data in this column is ignored.
POSTINGTIME
The Posting Time column is obsolete. Data in this column is ignored.
EFFECTIVEDATE
The Effective Date column contains the date and time that the accrual transaction
is effective. This column is required.
AMOUNT
The Amount column contains information that depends on the REQ_CODE

value.
REQ_CODE AMOUNT Value

16 The new accrual balance, in time or money
17 The amount earned, in time or money
This column is always required.
PROBATIONAMOUNT
The Probation amount column contains the amount of time in days in which
accrual balances are earned but cannot be taken or paid. This column is optional
when resetting an accrual balance. If you do not specify a value, the probation
amount defaults to zero days. This column is ignored when adding an earned
accrual amount.
Accruals Import
USERFIELD
Required columns
REQ_CODE 16, 17
Supply a value for the following columns when you reset an employee’s accrual
balance (17) or add an earned accrual amount (16):
• ACCRUALIMPORTID (Oracle only)
• REQ_CODE
• EMPLOYEEID
• ACCRUALCODE
• EFFECTIVEDATE
• AMOUNT
Accruals import examples

All the examples that follow use SQL that will insert rows into tables in a
Microsoft SQL Server database. As there are only minor differences between the
syntax of the supported databases, an exhaustive set of Oracle and DB2 database
examples is not provided.
For more information about differences in syntax, see “How SQL statement
syntax differs between database types” on page 33.

Example: How to reset an employee’s accrual balance
The example in this section demonstrates how to use the ACCRUALIMPORT

table to reset an employee’s accrual balance. To perform that function, enter the
SQL Insert command and follow these guidelines:
1. Specify ACCRUALIMPORT as the destination table for the data.
ACCRUALIMPORT table requires you to specify values for resetting an
employee’s accrual balance, as follows:
– ACCRUALIMPORTID
– REQ_CODE
– EMPLOYEEID
– ACCRUALCODE
– EFFECTIVEDATE
– AMOUNT
Sample SQL Server statement
SQL Server database
The following example uses request code 16 to reset the sick time accrual code for
employee 4321 to six hours effective on 8/8/00:
Insert into ACCRUALIMPORT (REQ_CODE, EMPLOYEEID,
ACCRUALCODE, EFFECTIVEDATE, AMOUNT)
Values ('16', '4321', 'Sick', '8/8/00', '6')
Accruals Import
Insert statement:

REQ_CODE 16 Resets an employee’s accrual balance.
ACCRUALCODE Sick Identifies the accrual code associated with
the accrual transaction.
EFFECTIVEDATE 8/8/00 Identifies the date and time that the accrual
transaction is effective.
AMOUNT 6 Identifies the amount of time associated
with the transaction.
Oracle databases require that the ACCRUALIMPORTID column and its value be
listed as the first column and value in the SQL Insert statement. The value is
NGP_ACCRUALIMPORT.NEXTVAL.
If the Insert statement runs successfully, verify that the record that resets the
accrual balance in the database is included in the ACCRUALIMPORT table. To
do this, issue a Select statement similar to the following command:
Select * from ACCRUALIMPORT where EMPLOYEEID = '4321'

Example: How to import an earned accrual amount
The example in this section demonstrates how to use the ACCRUALIMPORT

table to import an earned accrual amount. To perform that function, enter the SQL
Insert command and follow these guidelines:
1. Specify ACCRUALIMPORT as the destination table for the data.
ACCRUALIMPORT table requires you to specify values for adding an earned
accrual amount, as follows:
– ACCRUALIMPORTID
– REQ_CODE
– EMPLOYEEID
– ACCRUALCODE
– EFFECTIVEDATE
– AMOUNT
Accruals Import
SQL Server database
The following example uses request code 17 to add vacation time:

Insert INTO ACCRUALIMPORT (REQ_CODE, EMPLOYEEID,
ACCRUALCODE, EFFECTIVEDATE, AMOUNT)
VALUES ('17', '4321', 'Vacation', '1/1/00', '80')
Insert statement:

REQ_CODE 17 Enters an earned or taken accrual amount.
ACCRUALCODE Vacation Identifies the accrual code associated with the
accrual transaction.
EFFECTIVEDATE 1/1/00 Identifies the date and time that the accrual
transaction is effective.
AMOUNT 80 Identifies the amount of time associated with
the transaction.
For more information about the columns used in this example, see the previously
described section “Column definitions” on page 40.
Oracle databases require that the ACCRUALIMPORTID column and its value be
NGP_ACCRUALIMPORT.NEXTVAL.

If the Insert statement runs successfully, verify that the record that adds the new
earned accrual amount to the database is included in the ACCRUALIMPORT
table. To do this, issue a Select statement similar to the following command:
Select * from ACCRUALIMPORT where EMPLOYEEID = '4321'
Labor Level Entry Import
LABLEVENTIMPORT table
The Labor Level Entry Import table enables the import of labor level entries.
Labor levels are the categories that define an employer’s job and accounting (cost
center) structure. A labor level entry is a specific value within one of these
categories. Each labor level can contain one or more entries.
For example, the Region labor level might contain the entries 100 (Northeast),
101 (Southeast), and 102 (Midwest). Use this table to perform the following
import operations:
• Add labor levels
• Update labor levels
• Inactivate a labor level
• Reactivate a labor level


LLEVNTIMPID Integer Not Null
REQ_CODE Character(2) Not Null See “Column definitions” on page
54 for specific values.
NAME Character(50) Not Null
DESCRIPTION Character(250) Null
LLDEF Character(50) Not Null
NEWNAME Character(50) Null
Column definitions
LLEVNTIMPID
This column is the primary key for the LABLEVENTIMPORT table. The Labor
Level Entry Import ID column establishes a unique sequence number for each
entry that goes into the LABLEVENTIMPORT table.
REQ_CODE
The Request Code column indicates the operation that you want to perform. This
Value Description
1 Add a labor level entry
2 Update a labor level entry
3 Add or update labor level entries
4 Inactivate a labor level entry
5 Reactivate a labor level entry
NAME
The Name column identifies the name of the labor level entry upon which the
request code takes action. This column is always required.
Although the value in this column is alphanumeric, it is typically a number, not
text.
NAME works in conjunction with LLDEF, which identifies the labor level the
labor level entry is a member of. The text that describes the NAME is entered in
the DESCRIPTION column.
Example
The Precision Auto factory uses the labor account format with the following labor
levels:
/Company/Division/Department/Job
The employees perform a variety of work, so the “Job” labor level has multiple
entries that represent the jobs that are performed (assembly, welding, painting,
inspection). Each job has a different NAME, as follows:
Labor Level Entry NAME Corresponding DESCRIPTION

401 Assembly
402 Welding
403 Painting
404 Inspection
DESCRIPTION
The Description column contains text that describes the labor level entry value in
the NAME column. This column is ignored when you inactivate or reactivate a
labor level entry (5). It is optional for all other Request Codes. In the previous
example, the description contains the type of work performed.

LLDEF
The Labor Level Definition column identifies the labor level that is associated
with a labor level entry. This column is always required.
In the previous example, the labor account contained four labor levels:
/Company/Division/Department/Job
NEWNAME
The New Name column identifies the new name of an existing labor level entry.
This column is required only when you update a labor level entry (2).
If the labor level entry name is not changing, you can enter @ to indicate that the
labor level entry name should retain its original value.
USERFIELD
Required columns
REQ_CODE 1, 4, 5
Supply a value for the following columns when you add (1), inactivate (4), or
reactivate (5) a labor level entry:
• LLEVNTIMPID (Oracle only)
• REQ_CODE
• NAME
• LLDEF
REQ_CODE 2, 3
Supply a value for the following columns when you update (2, 3) a labor level
entry:
• LLEVNTIMPID (Oracle only)
• REQ_CODE
• NAME
• LLDEF
• NEWNAME
Labor level entry import examples

Example: How to add a labor level entry
The example in this section demonstrates how to add a new labor level entry in the
LABLEVENTIMPORT table. You can also use this format to inactivate or
reactivate a labor level entry. To perform that function, enter the SQL Insert
command by following these guidelines:
1. Specify LABLEVENTIMPORT as the destination table for the data.
LABLEVENTIMPORT table requires you to specify values for new labor
level entries as follows:
– LLEVNTIMPID (Oracle)

– REQ_CODE
– NAME
– LLDEF
Sample SQL Server statements
The following examples use request code 1 to add a labor level entry and identify
311 as its name:
Oracle database
Insert into LABLEVENTIMPORT (LLEVNTIMPID, REQ_CODE,

NAME, DESCRIPTION, LLDEF, USERFIELD)
Values (NGP_LABLEVENTIMPORT.NEXTVAL, '1', '311',
'Supervisor', 'Job', 'Cost Ctr from HR system');
Commit;
SQL Server database
Insert into LABLEVENTIMPORT (REQ_CODE, NAME,

DESCRIPTION, LLDEF, USERFIELD)
Values ('1', '311', 'Supervisor', 'Job', 'Cost Ctr from
HR system')
DB2 database

DESCRIPTION, LLDEF, USERFIELD)
Values ('1', '311', 'Supervisor', 'Job', 'Cost Ctr from
HR system');
Commit;
Insert statement:

LLEVNTIMPID NGP_LABLEVENTIMPORT. Establishes a unique sequence
NEXTVAL number for the entry in an
Oracle database.
REQ_CODE 1 Adds a labor level entry.
NAME 311 Names the labor level entry
upon which a request code
takes action.
DESCRIPTION Supervisor Describes the labor level entry.
LLDEF Job Defines the labor level.
USERFIELD Cost Ctr from HR system Stores user notes.
If the Insert statement runs successfully, verify that the information to add labor
level entry 311 to the database is included in the LABLEVENTIMPORT table. To
Select * from LABLEVENTIMPORT where NAME = '311'
Example: How to modify a labor level entry
The example in this section demonstrates how to modify a labor level entry in the
LABLEVENTIMPORT table. To perform that function, enter the SQL Insert
1. Specify LABLEVENTIMPORT as the destination table for the data.

LABLEVENTIMPORT table requires you to specify values for updated labor
level entries as follows:
– LLEVNTIMPID
– REQ_CODE
– NAME
– LLDEF
– NEWNAME
SQL Server database
The following example uses request code 2 to modify a labor level entry. It
changes the name identifier from 311 to 321.
DESCRIPTION, LLDEF, NEWNAME)
Values ('2', '311', '@', 'Job', '321')
Insert statement:

REQ_CODE 2 Updates a record.
NAME 311 Names the labor level entry upon which a request code
takes action.
DESCRIPTION @ Maintains the labor level entry description.
LLDEF Job Defines the labor level.
NEWNAME 321 Identifies the new name of the existing labor level entry.
Oracle databases require that the LLEVNTIMPID column and its value be listed
as the first column and value in the SQL Insert statement. The value is
NGP_LABLEVENTIMPORT.NEXTVAL.
Note: Any columns for which you do not supply a value are provided null values.
If one of these columns is a required column, the import will fail. If you are
performing an update and want an existing value to remain the same, specify @ as
the value of that column. The at (@) symbol instructs the Import process to retain
the column’s former value.
If the Insert statement runs successfully, verify that the information to update the
record for labor level entry 321 is included in the LABLEVENTIMPORT table.
Select * from LABLEVENTIMPORT where NEWNAME = '321'

Labor Level Sets Import

Labor Level Sets Import enables the import of labor level sets. A labor level set is
a named collection of labor level entries to which users can have access. As these
collections of accessible labor level entries are named, they can be assigned to
particular users to grant them access to particular labor accounts in their various
roles. Refer to the section “People Import” on page 100 to see the different roles
that a user can have that are determined by the assignment of a labor level set.
Use Labor level Sets Import for the following import operations:
• Add a labor level set
• Update a labor level set
• Add or update a labor level set
When you import a Labor Level Set, for column Type values 1 and 2, there must
be at least one entry in each level in the labor level set. For column Type value 3,
there must be at least one entry in the labor level set, which can be in any labor
level. For details, refer to TYPE in the following section, “Labor Level Sets
Import table” on page 62.
Labor Level Sets Import uses the following tables:
• LLSETIMPORT table contains all single instance attributes of a labor level
set. The name of the labor level set is an example.
• LLSETLLEIMPORT tables contains all multiple instance attributes of a labor
level set. The name of a labor level entry is an example.
Labor Level Sets Import table
LLSETIMPORT table
The Labor Level Sets Import table is a member table of Labor Level Sets Import
and contains all single instance attributes.

LLSETIMPORTID Integer Not Null
REQ_CODE Character(2) Not Null See “Column definitions” on
NAME Character(30) Not Null
DESCRIPTION Character(250) Null
TYPE Character(1) Null See “Column definitions” on
NEWNAME Character(30) Null
Column definitions
LLSETIMPORTID
The Labor Level Set Import ID column contains the unique identifier for the labor
level set. This column is always required for all databases (SQL Server, Oracle
and DB2); it is not automatically generated by the database.
REQ_CODE
The Request Code column specifies which operation to perform. This column is
always required. The Request Code has the following values:
Value Description
1 Add a labor level set
2 Update a labor level set
3 Add or update a labor level set

NAME
The Name column contains the name of the labor level set. This column is always
required.
DESCRIPTION
The Description column contains a brief summary of the labor level set. This
column is optional.
TYPE
The Type column identifies the type of the labor level set. This column is required
for an add (1, 3) operation. This column can have the following values:
Value Description
1 Indicates the entry of a labor level set that can be used in
any user role.
2 Indicates the entry of a labor level set that is used
exclusively for employee group labor level sets.
3 Indicates entry of a labor level set that is used exclusively
for labor level transfer sets.
For values 1 and 2, there must be at least one entry in each level in the labor level
set. For example, if the labor level set consists of seven labor levels, there must be
at least one entry in each level.
For value 3, there must be at least one entry in the labor level set, which can be in
any labor level. For example, if the labor level set consists of seven labor levels,
at least one of those seven must include at least one entry.
NEWNAME
The New Name column contains the name to replace the existing name of a labor
level set. This column is required for an update (2) of a labor level set. Use the
value @ to indicate that the existing name of the labor level set should be retained.
USERFIELD
Labor Level Set Labor Level Entries Import table

LLSETLLEIMPORT
The Labor Level Set Labor Level Entries Import table is a member table of Labor
Level Sets Import and contains all multiple instance attributes.

LLSETIMPORTID Integer Not Null
LLNAME Character(50) Not Null
LLENAME Character(50 Not Null See the section “Specifying labor
level entry names” on page 66 for
details.
LLEACTIONTYPE Character(1) Not Null See “Column definitions” on page
Column definitions
LLSETIMPORTID
The Labor Level Set Import ID column uniquely identifies the Labor Level Sets
Import record. Within the LLSETLLEIMPORT table, it is used to associate
LLSETLLEIMPORT table rows with the related row in the LLSETIMPORT
table. In others words, the Labor Level Set Import ID identifies the labor level set
that contains the labor level entries that are being imported. This column is always
required for all databases (SQL Server, Oracle, and DB2).

LLNAME
The Labor Level Name column contains the name of the labor level that the
associated labor level entry is a member of. This column is always required.
LLENAME
The Labor Level Entry Name column contains the name of the labor level entry.
This column is always required. Refer to the section “Specifying labor level entry
names” on page 66 for details.
LLEACTIONTYPE
The Labor Level Entry Action Type specifies the action to perform on the labor
level entry. This column is always required and has the following values:
Value Description
1 Add an entry
2 Delete an entry
Specifying labor level entry names

Users can specify labor level entry names to which they have access in the
following ways:
• As an explicit entry
• As a single character wildcard
• As a string wildcard
Explicit labor level entry names

An explicit labor level entry name is a labor level entry where all characters are
specified with explicit values and no wildcard. For example, a labor level entry of
401 is provided as 401.
If the specified labor level entry does not match an existing labor level entry
within the specified labor level, the entire labor level set will not be imported.
String wildcard labor level entry names

A string wildcard labor level entry name is a labor level entry where the string
wildcard asterisk symbol (*) is used. For example, a labor level entry of 4* means
that users assigned to the labor level set have access to any labor level entries that
start with a 4, followed by any series of one or more characters.
The following table shows some sample wildcard entries and the results on a
search of labor levels with the labor level entries of 400, 401, 410, 411, and 420:
Entry Result
4* 400, 401, 410, 411, 420
41* 410, 411
*0 400, 410, 420
*9 None
As shown in the last example, you can specify a labor level entry wildcard that
does not provide access to any existing labor level entries.
Single character wildcard labor level entry names

A single character wildcard labor level entry name is a labor level entry where the
single character wildcard symbol (?) is used. For example, a labor level entry of
4?0 means that users assigned to the labor level set have access to any labor level
entries that start with a 4 followed by any single character, followed by a 0.
The following table shows some sample wildcard entries and the results on a
search of labor levels with the labor level entries of 400, 401, 410, 411, and 420:
Entry Result
4?0 400, 410, 420
41? 410, 411
?0? 400, 401
43? None

As shown in the last example, you can specify a labor level entry wildcard that
provides no access to any existing labor level entries.
Labor level sets import examples

Example: Adding a new labor level set
The following example demonstrates the SQL for adding a new labor level set.
This labor level set encompasses six labor level entries over two labor levels.
To perform this function, enter the SQL statement by following these guidelines:
1. Specify the LLSETIMPORT table as the destination of the labor level set and
specify the LLSETLLEIMPORT tables as the destination for each of the six
labor level entries.
2. Identify all columns that will be receiving data, in the order in which they
appear in the tables.
3. Include a values statement whose values correspond to the columns in the
Insert statement.
The following example uses Request Code 1 to add a new labor level set and labor
level entries:
insert into LlsetImport (LlsetImportId, Req_Code, Name,
Description, type, NewName, UserField)
values (1, '1', 'Labor Level Set 1', 'Labor Level Set 1
description', '1', null, 'Add a new LLS')
insert into LlsetLleImport (LlsetImportId, LlName,
LleName, LleActionType) values (1, 'Item Number',
'601', '1')
'602', '1')
'603', '1')
'604', '1')
LleName, LleActionType) values (1, 'Work Order', '701',
'1')
'1')
The LLSETIMPORTID column values in each of these INSERT instructions.
They all have the same value, a value of 1. They could have any value as long as
the rows inserted into the LLSETLLEIMPORT table refer to the corresponding
row in the LLSETIMPORT table.
In addition, the row inserted into the LLSETIMPORT table must have a value for
LLSETIMPORTID that is unique. If a row is already stored in the
LLSETIMPORT table with the same value for LLSETIMPORTID, a primary key
constraint violation is reported when attempting to insert the row into the table.

For example:
Violation of PRIMARY KEY constraint 'PK_LLSETIMPORT'.
Cannot insert duplicate key in object 'LLSETIMPORT'.
The statement has been terminated.
Sample statements for Oracle and DB2
The following example demonstrates the SQL statement to insert the labor level
set and labor level entries into an Oracle or DB2 database:
description', '1', null, 'Add a new LLS');
'601', '1');
'602', '1');
'603', '1');
'604', '1');
'1');
'1');
Commit;
Example: Adding a labor level set with a labor level entry wildcard
The following example demonstrates the SQL Server statement for adding a new
labor level set using a labor level entry name wildcard.
The single character wildcard is used for labor level entries at the “Item Number”
labor level. Users assigned this labor level set are granted access to any three-
character labor level entry starting with 60.
The string wildcard is used for labor level entries at the “Work Order” labor level.
Users assigned this labor level set are granted access to any labor level entry
starting with 7.
SQL Server database

description', '1', null, 'Add a new LLS using
wildcard')
'60?', '1')
LleName, LleActionType) values (2, 'Work Order', '7*',
'1')
The LLSETIMPORTID column values in each of these INSERT instructions.
They all have a value of 2 to avoid a primary key constraint violation with the
entries made in the first example.

Example: Renaming an existing labor level set
The following example demonstrates the SQL for renaming an existing labor level
set. The labor level set name is changed from “Labor Level Set 2” to “Labor Level
Set 3.”
SQL Server database

NewName, UserField)
values (3, '2', 'Labor Level Set 2', 'Labor Level Set
3', 'Rename an LLS')
No inserts are made into the LLSETLLEIMPORT table because no data

associated with labor level entries within the labor level set have changed.
Example: Changing the description of a labor level set
The following example demonstrates the SQL for changing the description of an
existing labor level set. The description is changed to “Labor Level Set 3
description.”
SQL Server database

Description, NewName, UserField)
description', '@', 'Change LLS description')
The NEWNAME column is populated with an @ to retain the current labor level
set name.

Example: Adding labor level entries within a labor level set

The following example demonstrates the SQL for adding and deleting labor level
entries within a labor level of a labor level set. The labor level entry 622 is
deleted. The labor level entry 632 is added. Both of these labor level entries are
members of the “Item Number” labor level.
SQL Server database

NewName, UserField)
values (7, '2', 'Labor Level Set 3', '@', 'Add and
delete LLEs within an LLS')
'622', '2')
'632', '1')

Example: Deleting labor level entries from an existing labor level set
The following example demonstrates the SQL for deleting a labor level entry from
an existing labor level set. The labor level entry deleted is 611, which is a member
of the “Item Number” labor level.
SQL Server database

NewName, UserField)
values (6, '2', 'Labor Level Set 3', '@', 'Delete an
LLE from an LLS')
'611', '2')
The LLEACTIONTYPE column value is set to 2 to indicate removal of the labor
level entry from the labor level set.
• LLEVNTIMPID (Oracle)
• REQ_CODE
• NAME
Note: Any columns for which you do not supply a value are provided null values.
If one of these columns is a required column, the import will fail. If you are
performing an update and want an existing value to remain the same, specify @ as
the value of that column. The at (@) symbol instructs the Import process to retain
the column’s former value.
If the Insert statement runs successfully, verify that the information to update the
record for labor level entry 321 is included in the LABLEVENTIMPORT table.
Select * from LABLEVENTIMPORT where NEWNAME = '321

Pay Code Edits Import
PAYCATEDITIMPORT table
Use this table to import pay code edits. A pay code edit includes changes or
adjustments to an employee’s salary, hours, or totals.
You can perform the following import operations using either the employee ID
number or the employee badge number:
• Add or delete a pay code edit
• Add a comment to a pay code edit
• Add or delete a historical edit
• Add a comment to a historical edit
• Add or delete a totaled amount
• Add a comment to a totaled amount
• Add a pay code to scheduled hours or a historical edit
Column definitions

PAYCATEDITIMPID Integer Not Null Automatically populated
(except for Oracle databases)
REQ_CODE Character(2) Not Null See “Columns, data types, and
null contraints” on page 76 for
specific values.
EMPID Character(15) Not Null
EDITDATE Character(10) Not Null
PAYCAT Character(50) Null See “Column definitions” on

LABORACCT Character(356) Null See “Column definitions” on
AMOUNT Character(30) Not Null See “Column definitions” on
COMMENTTEXT Character (255) Null


WORKRULE Character(50) Null
OTYPE Character(1) Null See “Columns, data types, and
specific values.
PAID_SW Character(1) Null See “Columns, data types, and
specific values.
IMPACTSACCRUALS_SW Character(1) Null See “Columns, data types, and
specific values.
ADJ_APPLYDATE Character(10) Null
SCHEDAMTTYPEID Character(1) Null
ORGPATHTXT Character(1000) Null
PAID_SW Character(1) Null See “Columns, data types, and
specific values.
IMPACTSACCRUALS_SW Character(1) Null See “Columns, data types, and
specific values.
ADJ_APPLYDATE Character(10) Null
SCHEDAMTTYPEID Character(1) Null
PAYCATEDITIMPID
The Pay Code Edit Import ID is the primary key for the table. This column
establishes a unique sequence number for each entry that goes into the
PAYCATEDITIMPORT table.
This column is always required in an Oracle database. A value for this column is
automatically generated when you insert a row in a SQL Server or DB2 database.
REQ_CODE
Value Description
6 Add a pay code edit using the employee ID number.
7 Add a pay code edit using the employee badge number.
8 Delete a pay code edit using the employee ID number.
9 Delete a pay code edit using the employee badge number.
27 Add a comment to a pay code edit using the employee ID number.
28 Add a comment to a pay code edit using the employee badge number.
29 Add a historical edit using the employee ID number.
30 Add a historical edit using the employee badge number.
31 Delete a historical edit using the employee ID number.
32 Delete a historical edit using the employee badge number.
33 Add a comment to a historical edit using the employee ID number.
34 Add a comment to a historical edit using the employee badge number.
35 Add a totaled amount using employee ID number.
36 Add a totaled amount using the employee badge number.
37 Delete a totaled amount using the employee ID number.
38 Delete a totaled amount using the employee badge number.
39 Add a comment to a totaled amount using the employee ID number.
40 Add a comment to a totaled amount using the employee badge number.

EMPID
The Employee ID column contains the employee ID or badge number. This

column is required with the following values:
REQ_CODE Value EMPID Value

6, 8, 27, 29, 31, 33, 35, 37, or 39 Contains the employee ID number.
7, 9, 28, 30, 32, 34, 36, 38, or 40 Contains the employee badge number.
EDITDATE
The Edit Date column contains the date on which the current pay code edit
becomes effective. This column is always required.
PAYCAT
The Pay Code column identifies the name of the pay code that is being applied to
an amount associated with a pay code or to a historical amount. This column is
always required importing a pay code edit or a historical edit. It is ignored when
importing a totaled amount. REQ_CODE Values 1 and 27 are required.
A pay code holds one of the following units:
• The hours accumulated during a pay period. A pay code that holds hours can
contain worked hours (such as regular, overtime, or second shift) or unworked
hours (such as vacation, sick, or personal).
• Money earned by employees during a pay period.
For example, to allocate hours for J.D. Smith, who worked 8 regular and 4
overtime hours for a total of 12 hours, create two pay code edit entries:
– An entry with 8 regular hours
– An entry with 4 overtime hours
LABORACCT
The Labor Account column contains the name of the labor account of the
employee whose pay code amount or totaled amount is being edited. This column
is optional when adding a pay code edit, historical edit, or totaled amount. The
column is required when the pay code edit, historical edit, or totaled amount being
deleted or commented contained an explicit LABORACCT value. You can leave
this column blank if the pay code amount or totaled amount applies to the
employee’s primary account.
Enter data for labor accounts in the same format as they appear in the Workforce
Central database. If you have a seven-level labor account, specify a value for each
labor level, using the following format:
101/202/303/404/504/603/702
You can leave blank any labor levels that are not changing; for example, you can
enter the value 101//303////, indicating that only the first and third labor level
entries are different.
If any of the labor levels should stay the same as the employee’s primary labor
account, you can enter @H for those labor levels instead of entering the labor
entry names.
AMOUNT
The Amount column contains the value associated with the corresponding pay
code amount or totaled amount. This column is required for all request codes.
Enter the value as follows:
• If the PAYCAT column holds money, specify an amount of money.
• If the PAYCAT column holds time, specify a duration of time.
• If this is a totaled amount (the PAYCAT column is blank), specify a duration
of time.

COMMENTTEXT
The Comment Text column contains a text string that is attached to the pay code
amount or totaled amount. This column is required when you add a comment (27,
28, 39, 40). It is optional when adding a pay code edit, historical edit, or totaled
amount. It is ignored when deleting a pay code edit, historical edit, or totaled
amount.
The string in this column must exactly match an applicable comment that already
exists in the Workforce Central database and must apply for this category. The
string matching is case-sensitive.
A comment entered as part of a historical amount is not used as part of the criteria
when an import delete is issued for the same historical amount.
USERFIELD
WORKRULE
The Work Rule column contains the work rule to which the amount is being
applied. This column is optional when adding a totaled amount. If the column is
left blank, it will use the employee’s default work rule.
OTYPE
The Override Type column contains the override type value, if any, that is being
applied when adding a totaled amount. This column is ignored when adding a
comment to a totaled amount. This column is always ignored for pay code edits
and historical edits.
Value Description
0 No new shift override
1 New shift override
PAID_SW
The Paid Indicator column determines whether the historical amount (either time
or money) is tracked and included in the employee’s totals. This column is
optional when adding a historical edit.
Value Description
0 The default value. The amount supplied is tracked, but is not included in
the employee’s totals for the current pay period.
1 The amount supplied is tracked and included in the employee’s totals for
the current pay period.
IMPACTSACCRUALS_SW
The Impacts Accruals Indicator column determines whether the accrual balances
should be adjusted based on the historical amount.
Value Description
0 The default value. The employee’s accrual balances should not be
adjusted based upon the historical amount entered.
1 The employee’s accrual balances should be adjusted based upon the
historical amount entered.

ADJ_APPLYDATE
The Adjustment Apply Date column contains the date to which the historical edit
is applied. This column is required for all operations on historical edits. It is
always ignored for the pay code edits and totaled amounts.
The date supplied must be within a locked pay period.
SCHEDAMTTYPEID
The Scheduled Amount Type ID column determines whether or not the Pay Code
Edit amount needs to be calculated. If the column is calculated, the value is based
on the number of hours that the employee is scheduled to work that day and
whether the amount is a full day or half day amount. This column is ignored for
historical pay code edits and totaled ammounts.
If you do not specify a value for this column, the value specified in the Amount
column is used to calculate the scheduled amount. If you specify a value of 1 or 2
in this column, the value specified in the Amount column must be 0 or an error
message appears.
Value Description
1 Calculates the amount as a full-day scheduled amount.
2 Calculates the amount as a half-day scheduled amount.
ORGPATHTXT
The Organizational Path Text column contains the name of the organizational job
path of the employee whose pay code amount or totaled amount is being edited.
The column is required when the pay code edits, historical edit, or totaled amount
being deleted or commented contained an explicit ORGPATHTXT value.
The column is optional when you add a pay code, historical edit, or totaled
amount. You can leave this column blank if the punch applies to the employee's
primary organizational job.
Enter data for ORGPATHTXT in the same format as it appears in the database.
The ORGPATHTXT string matching is case-sensitive on a Workforce Central
server that connects to an Oracle database.
Use the shorthand notation @P to substitute for the person’s existing primary
organizational job.
Required columns
REQ_CODE
6, 7, 8, 9
Supply a value for the following columns when you import amounts associated
with a pay code:
• PAYCATEDITIMPID (Oracle only)
• REQ_CODE
• EMPID
• EDITDATE
• PAYCAT
• AMOUNT
REQ_CODE
27, 28
Supply a value for the following columns when you add a comment to amounts
associated with a pay code:
• REQ_CODE
• EMPID
• EDITDATE
• PAYCAT
• AMOUNT
• COMMENTTEXT

REQ_CODE
29, 30, 31, 32
Supply a value for the following columns when you import historical amount
data:
• REQ_CODE
• EMPID
• EDITDATE
• PAYCAT
• AMOUNT
• ADJ_APPLYDATE
REQ_CODE
33, 34
Supply a value for the following columns when you add a comment to historical
amount data:
• REQ_CODE
• EMPID
• EDITDATE
• PAYCAT
• AMOUNT
• ADJ_APPLYDATE
• COMMENTTEXT
REQ_CODE
35, 36, 37, 38
Supply a value for the following columns when you import totaled amount data:
• REQ_CODE
• EMPID
• EDITDATE
• AMOUNT
REQ_CODE
39, 40
Supply a value for the following columns when you add a comment to a totaled
amount:
• REQ_CODE
• EMPID
• EDITDATE
• AMOUNT
• COMMENTTEXT
Pay code edits import examples

Example: How to add an amount associated with a pay code edit
The example in this section demonstrates how to add a new pay code edit entry in
the PAYCATEDITIMPORT table. To perform that function, enter the SQL Insert
1. Specify PAYCATEDITIMPORT as the destination table for the data.
PAYCATEDITIMPORT table requires you to specify values for new pay code
edits as follows:
– PAYCATEDITIMPID
– REQ_CODE
– EMPID
– EDITDATE
– PAYCAT
– AMOUNT
SQL Server database
The following example uses request code 6 to add a pay code edit for an
employee:
Insert into PAYCATEDITIMPORT (REQ_CODE, EMPID,
EDITDATE, PAYCAT, AMOUNT)
Values ('6', '4321', '9/5/00', 'Regular', '10:00')
Insert statement:

REQ_CODE 6 Adds a pay code edit using the employee’s ID number.
EMPID 4321 Identifies the employee.
EDITDATE 9/5/00 Identifies the date of the edit.
PAYCAT Regular Identifies the pay code.
AMOUNT 10:00 Identifies the number of hours of the edit.
Oracle databases require that the PAYCATEDITIMPID column and its value be
NGP_PAYCATEDITIMPORT.NEXTVAL.
If the Insert statement runs successfully, verify that the record to add the new pay
code edit to the database is included in the PAYCATEDITIMPORT table.
Select * from PAYCATEDITIMPORT where EMPID = '4321’
Example: How to add a totaled amount
The example in this section demonstrates how to add a new totaled amount in the
PAYCATEDITIMPORT table. To perform that function, enter the SQL Insert

edits as follows:
– PAYCATEDITIMPID (Oracle only)
– REQ_CODE
– EMPID
– EDITDATE
– AMOUNT
SQL Server database
The following example uses request code 35 to add an amount using the
employee’s ID number:
EDITDATE, AMOUNT)
Values ('35', '4321', '9/6/00', '8:00')
Insert statement:

REQ_CODE 6 Adds a totaled amount using the employee’s ID number.
AMOUNT 8:00 Identifies the amount of time applied to the default pay
rule.
Select * from PAYCATEDITIMPORT where EMPID = '4321'
Example: How to add a scheduled pay code amount
The example in this section demonstrates how to add a pay code amount using
scheduled amounts. To perform that function, enter the SQL Insert command by
following these guidelines.
– Each table has columns that require you to specify a value. The
PAYCATEDITIMPORT table requires you to specify values as follows:
– REQ_CODE
– EMPID
– EDITDATE
– PAYCAT
– AMOUNT
– SCHEDAMTTYPEID

SQL Server database
The following example uses request code 6 to add a scheduled pay code amount
using the employee’s scheduled amount type ID number:
EDITDATE, PAYCAT, AMOUNT, SCHEDAMTTYPEID)
Values ('6', '4321', '9/6/00', 'Regular', '0','1')
Insert statement:

REQ_CODE 6 Adds a pay code edit using the employee’s
ID number.
AMOUNT 0 Identifies the amount that needs to be
calculated, which must be zero if when
SCHEDAMTTYPEID is used to calculate
the amount.
SCHEDAMTTYPEID 1 Calculates the scheduled amount as a full
day scheduled amount.
Example: How to add a comment to a pay code amount or totaled amount
The example in this section demonstrates how to add a comment to a pay code
amount or totaled amount in the PAYCATEDITIMPORT table. To perform that
function, enter the SQL Insert command by following these guidelines:
and totaled amounts as follows:
– PAYCATEDITIMPID
– REQ_CODE
– EMPID
– EDITDATE
– PAYCAT (not required when adding a totaled amount)
– AMOUNT
– COMMENTTEXT
SQL Server database
Adding a Comment to an Existing Entry

You can add a comment to an existing pay code amount or totaled amount in a
table by using the employee’s ID number or the employee’s badge number:
EDITDATE, PAYCAT, AMOUNT, COMMENTTEXT)
Values ('27', '4321', '9/5/00', 'Regular', '10:00',
'Needs Review')

Insert statement:

REQ_CODE 27 Adds a comment using the employee’s ID
number.
COMMENTTEXT Needs Review Contains the text of the comment. The text in
this column must match an applicable
comment in Workforce Timekeeper and apply
for this category.
Adding a Comment When You Add a Pay Code amount or Totaled amount
You can also add a comment when adding a pay code amount or totaled amount.
EDITDATE, PAYCAT, AMOUNT, COMMENTTEXT)
Values ('6', '4321', '9/4/00', 'Sick', '8:00', 'Needs
Review')
The following table shows the significance of each value that is used.

REQ_CODE 6 Adds a pay code edit using the employee’s ID
number.
PAYCAT Sick Identifies the pay code.
this column must match an applicable
comment in Workforce Timekeeper and apply
for this category.


If the Insert statement runs successfully, verify that the record to add the comment
to the pay code edit in the database is included in the PAYCATEDITIMPORT
Example: How to add an historical edit

The example in this section demonstrates how to add a historical edit entry in the
edits as follows:
– REQ_CODE
– EMPID
– EDITDATE
– PAYCAT
– AMOUNT
– ADJ_APPLYDATE

SQL Server database
The following example uses request code 29 to add a historical edit for an
employee:
Insert into PAYCATEDITIMPORT (REQ_CODE, EMPID,EDITDATE,
PAYCAT, AMOUNT, ADJ_APPLYDATE)
Values ('29', '4321', '9/7/00','On-Call', '4:00', ‘9/7/
99’)
Insert statement:

REQ_CODE 29 Adds a historical edit using the employee’s ID
number.
PAYCAT On-Call Identifies the pay code to which the
adjustment is applied.
AMOUNT 4:00 Identifies the amount of the adjustment.
ADJ_APPLYDATE 9/7/99 Identifies the date of the adjustment.
Example: How to delete a pay code edit
The example in this section demonstrates how to delete a pay code edit in the
PAYCATEDITIMPORT table requires you to specify values for pay code edit
deletions as follows:
– PAYCATEDITIMPID
– REQ_CODE
– EMPID
– EDITDATE
– PAYCAT
– AMOUNT
3. Specify a value for each column that you identified.

SQL Server database
The following example uses request code 8 to delete a pay code edit. This import
deletes the pay code edit added in the last example.
EDITDATE, PAYCAT, AMOUNT)
VALUES ('8', '43', '9/5/00', 'Regular', '10:00')
Insert statement:

REQ_CODE 8 Deletes a pay code edit using the employee’s ID
number.
If the Insert statement runs successfully, verify that the record to delete the pay
code entry from the database is included in the PAYCATEDITIMPORT table. To

People Import
People Import enables the import of employee and user demographic information.
Examples of the data are names, addresses, phone numbers, and logon names and
passwords.
Use People Import for the following import operations:
• Add a person. Refer to the section “Predefined data values” on page 130 for
details about the columns to populate.
• Update a person. Refer to the section “Updating a person” on page 174 for
details about the columns to populate.
• Add or update a person.
• Delete a person.
People Import uses the following tables:

• PERSONIMPORT table contains all single instance attributes associated with
a person. A person’s surname is an example.
• PERSONDATEIMPORT table contains attributes that might have multiple
instances of effective date entries. A primary labor account assignment is an
example. Workforce Central supports an unlimited number of consecutive
primary labor account assignments to a person that have effective dates.
• PERSONMANYIMPORT table contains all additional multiple instance
attributes. An example is a phone number. Workforce Central supports the
entry of up to three phone numbers per person.
Person Import table
PERSONIMPORT
The Person Import table contains single instance data.

People Import
Columns, data types, and null constraints
Null
Column Name Data Type Constraint Comments
PERSONIMPORTID Integer Not null
REQ_CODE Character(2) Not null See “Column Definitions” for
specific values.
PERSONTYPE Character(2) Not null See “Column Definitions” for
specific values.
PERSONNUM Character(15) Not null See “Column Definitions” for
specific values.
NEWPERSONTYPE Character(2) Null See “Column Definitions” for
specific values.
NEWPERSONNUM Character(15) Null
FIRSTNAME Character(30) Null
MIDNAME Character(1) Null
LASTNAME Character(30) Null
SHORTNAME Character(20) Null Defaults to first 20 characters of
FIRSTNAME.
HIREDATE Character(10) Null Defaults to the date imported.
MANAGERNAME Character(64) Null
BIRTHDATE Character(10) Null
TIMEZONE Character(30) Null
PAYRULE Character(50) Null
WAGERATE Character(15) Null Defaults to 0.
WAGEPROFILE Character(50) Null
ACCRUALPROFILE Character(50) Null
FUNCACCESSPROF Character(50) Null Predefined data values are available
to populate this column. See
“Predefined data values” on page
130.

Null
DISPLAYPROFILE Character(30) Null Predefined data values are available
130.
FTEPERCENTAGE Character(15) Null See “Column Definitions” for the
relationships with other FTE columns
and possible errors.
FTEEXPECTEDHOURS Character(15) Null See “Column Definitions” for the
FTEHOURS Character(15) Null See “Column Definitions” for the
EXPDAILYHOURS Character(5) Null Entries cannot contain colons.
EXPWEEKLYHOURS Character(6) Null
EXPPAYPERIODHOURS Character(6) Null
DEVICEGROUP Character(50) Null
LOGONNAME Character(70) Null
LOGONPROFILE Character(50) Null
PASSWORD Character(30) Null Do not use an encrypted value.
PASSWORDCHANGE Character(1) Null See “Column Definitions” for range
of values.
TRANSFERIN Character(1) Null
EMPGROUPLLSET Character(30) Null Predefined data values are available
130.
MGRXFERLLSET Character(30) Null Predefined data values are available
to populate this column. See “Column
definitions” on page 40.

People Import
Null
EMPXFERLLSET Character(30) Null Predefined data values are available
to populate this column. See the
section, “Predefined data values” on
page 130
EMPPAYCODEDAP Character(30) Null Predefined data values are available
130.
EMPWORKRULEDAP Character(30) Null Predefined data values are available
130.
MGRPAYCODEDAP Character(30) Null Predefined data values are available
130.
MGRWORKRULEDAP Character(30) Null Predefined data values are available
130.
MGRREPORTDAP Character(30) Null Predefined data values are available
130.
TIMEENTRYMETHOD Character(1) Null See the column definitions for
specific values.
WORKERTYPE Character(50) Null
SCHEDGROUPPROFILE Character(50) Null Predefined data values are available
130.

Null
SHIFTTMPLPROFILE Character(50) Null Predefined data values are available
130.
PATTERNTMPLPROFILE Character(50) Null Predefined data values are available
130.
SENIORITYDATE Character(10) Null
Column definitions
PERSONIMPORTID
The Person Import ID uniquely identifies the People Import record. It is used to
associate any related rows in the PERSONDATEIMPORT and
PERSONMANYIMPORT tables. It is also included in the Import Error Report to
allow the user to relate error messages to a particular People Import record.
This column always requires a value. Unlike many Import tables, its value is not
automatically generated by the database.
REQ_CODE
The Request Code column indicates the action to be performed on the People
Import record. A value for this column is always required.
Value Description
1 Add a new person.
2 Update a person. Use if your data source allows you to export only changes
to a person.
3 Add or update a person. Use if your data source only allows you to export
all information about a person when importing.

People Import
Value Description
4 Delete an existing person from the database. This action permanently
deletes all the person’s information from the database. Once you delete a
person using this method, you must reimport the information to restore the
person.
PERSONTYPE
The Person Type identifies the type of person being imported and is used for
license assignments. Use PERSONTYPE to:
• Assign a license to a new person
• Add a license to an existing person
• Supersede NEWPERSONTYPE for new people only
Do not use PERSONTYPE to downgrade or remove a license. Use
NEWPERSONTYPE.
A value for this column is always required. Shorthand notation of @ is allowed.
Possible values are:
Value Description
0 Employee without any license type, such as a terminated employee.
1 Workforce Timekeeper Employee
2 Workforce Employee and Workforce Timekeeper Employee
3 Workforce Manager
4 Workforce Timekeeper Employee, Workforce Employee, and Workforce
Manager
5 Workforce Timekeeper Employee and Workforce Manager
6 Workforce Timekeeper Employee and Workforce Scheduler Employee
Scheduler Employee
8 Workforce Timekeeper Employee, Workforce Scheduler Employee, and
Workforce Manager

Value Description
9 Workforce Timekeeper Employee, Workforce Employee, Workforce
Scheduler Employee, and Workforce Manager
Workforce Activities Employee
Scheduler Employee, and Workforce Activities Employee
12 Workforce Timekeeper Employee, Workforce Activities Employee, Workforce
13 Workforce Timekeeper Employee, Workforce Activities Employee, Workforce
Employee, Workforce Scheduler Employee, and Workforce Manager
14 Workforce Activities Employee and Workforce Timekeeper Employee
15 Workforce Timekeeper Employee, Workforce Activities Employee, and
Workforce Employee
Workforce Manager
17 Workforce Timekeeper Employee, Workforce Activities Employee,Workforce
Employee, and Workforce Manager
NEWPERSONTYPE
The New Person type column indicates the value of the license type to which the
person has been switched. Use NEWPERSONTYPE to:
• Upgrades a existing person's license
• Downgrade an existing person's license
• Remove an existing person's license
• Maintain the existing person's license type if the value is @
• Supersede PERSONTYPE for all existing people

People Import
The column value is required when a person license type changes. Choose from
the following values:
Value Description
0 No licenses applied to this employee
1 Workforce Timekeeper Employee
3 Workforce Manager
Manager
5 Workforce Timekeeper Employee and Workforce Manager
6 Workforce Timekeeper Employee and Workforce Scheduler Employee
Scheduler Employee
Workforce Manager
Workforce Activities Employee
12 Workforce Timekeeper Employee, Workforce Activities Employee,
Workforce Scheduler Employee, and Workforce Manager
Workforce Employee, Workforce Scheduler Employee, and Workforce
Manager
14 Workforce Activities Employee and Workforce Timekeeper Employee
Workforce Employee
Workforce Manager

Value Description
Workforce Employee, and Workforce Manager
If you do not specify a value, the existing value from PERSONTYPE is used as
the NEWPERSONTYPE value.
PERSONNUM
The Person Number contains the person’s identification number. A value for this
column is always required. Non-numeric values are permitted.
NEWPERSONNUM
The New Person Number column contains the person’s new identification
number. A value for this column is always required when you are updating a
person’s record. A value of @ retains the current person’s identification in the
updated record.
FIRSTNAME
The First Name column contains the person’s first name. A value for the column
is always optional.
MIDNAME
The Middle Name column contains the person’s middle initial. A value for this
column is always optional.

People Import
LASTNAME
The Last Name column contains the person’s last name. A value for this column is
required for adding a new person (1, 3). When updating a person, do not use
“Null” or similar placeholder to indicate that the person’s last name is not
changing. Use shorthand notation of @ as a placeholder. Using a value such as
Null inserts the string Null as the last name instead of maintaining the actual
name.
SHORTNAME
The Short Name column contains the name by which the person wants to be
known. A value for this column is optional. If you do not provide a value, the
person’s short name defaults to the first 20 characters of the person’s first name.
HIREDATE
The Hire Date column contains the date on which the person was hired. A value
for this column is optional. If you provide a value, the value must be later than the
birth date. If you do not provide a value, the person’s hire date defaults to the date
the person’s record is imported.
MANAGERNAME
The Manager Name column contains the name of the person’s manager. A value
for this column is always optional. If you provide a value, specify the manager’s
name as follows: last name, comma, space, first name, space, middle initial. For
example: Smith, John B.
BIRTHDATE
The Birth Date column contains the person’s date of birth. A value for this column
is optional.

TIMEZONE
The Time Zone column contains either the ID, a five-digit value that describes
how the local time for a region relates to Greenwich mean time (GMT), or the
exact name of the time zone in which the person works. A value for this column is
required when a value is also specified for the DEVICEGROUP column. If you
do not specify a value, the default time zone is used.
Refer to Appendix B “Time Zone Definitions” in the Workforce Timekeeper
Database Tables Reference Guide for a complete list of all time zone codes and
names.
PAYRULE
The Pay Rule column contains the name of the pay rule that is assigned to the
employee. A pay rule defines the set of business standards by which persons are
paid and determines how the person’s time is processed and categorized.
WAGERATE
The Wage Rate column contains the person’s wage rate, which is the monetary
rate at which the person is paid. A value for this column is optional. If you do not
provide a value, the person’s wage rate defaults to zero.
WAGEPROFILE
The Wage Profile column contains the name of the person’s wage profile. A value
for this column is optional.
ACCRUALPROFILE
The Accrual Profile column contains the name of the person’s accrual profile.
Accrual profiles are based on your company’s accrual rules and policies that apply
to similar groups of employees. The rules determine how employees accrue their
time or money, or both. When an employee uses accrued time or money, specified
amounts are deducted from the balance. When an employee receives or earns time
or money, specified amounts are credited to the balances. A value for this column
is optional.

People Import
FUNCACCESSPROF
The Function Access Profile column contains the name of the person’s function
access profile. The function access profile determines the components that users
can access and the types of functions that users can perform, based on their
assigned roles.
For example, access profiles for Managers can include permission to edit
schedules and timecards. The same profile can be assigned to a group of similar
users, such as managers in the same department. The system administrator creates
the access profiles in Setup. Refer to the Workforce Central System
Administrator’s Guide for an explanation of the roles.
Import provides predefined data values, for example, IS, Payroll Manager, Time
Stamp Employee, Workforce Employee, and Default. Refer to “Predefined data
values” on page 130. If you do not specify a value, the value is set to Default.
DISPLAYPROFILE
The Display Profile column contains the name of the person’s display profile. The
display profile identifies the information that is displayed to a user; for example,
which Workforce Genie appears as a Genie selection on the navigation bar or how
time is displayed in the interface.
Default and Super User Preferences are predefined values. Refer to “Predefined
data values” on page 130. If you do not specify a value, the value is set to Default.
FTEPERCENTAGE
The Full Time Equivalency Percentage column specifies the ratio of the expected
hours worked by the employee to the expected hours worked for a full-time
employee. The value is used to determine the rate at which benefits accrue for the
employee. The value is treated as a percentage and must have an integer value
between 1 and 100. An error is reported if an integer value for
FTEPERCENTAGE is less than 1 and greater than 100.
Do not specify a value for Full Time Equivalency Percentage if you have provided
values for the FTEEXPECTEDHOURS column and the FTEHOURS column. An
error is reported if you specify values for all three columns.

FTEEXPECTEDHOURS
The Full Time Equivalency Expected Hours column contains the number of hours
that the full-time employee is expected to work and is used in conjunction with the
value provided in the FTEHOURS column to determine the rate at which benefits
accrue for the employee.
Do not specify a value for Full Time Equivalency Expected Hours if you have
provided a value for the FTEPERCENTAGE column. An error is reported if you
specify a value for all three, the FTEPERCENTAGE, FTEEXPECTEDHOURS,
and FTEHOURS columns. An error is also reported if the full Time Equivalency
Expected Hours value is greater than the value of the FTEHOURS column.
FTEHOURS
The Full Time Equivalency Hours column contains the number of hours that a
full-time employee works and is used in conjunction with the value provided in
the FTEXPECTEDHOURS column to determine the rate at which benefits accrue
for the employee.
The Full Time Equivalency Hours value defaults to 40 if you do not specify a
value.
Note: If you specify a value for FTEPERCENTAGE, do not specify a value for
FTEEXPECTEDHOURS or FTEHOURS. If you specify a value for
FTEEXPECTEDHOURS and FTEHOURS, do not specify a value for
FTEPERCENTAGE.

People Import
EXPDAILYHOURS
The Expected Daily Hours column contains the number of hours that the
employee is expected to work each day. The value can be an integer amount or a
decimal amount, such as 8, 8.0 or 8.5. Do not use colons, for example, 8:00 to
separate hours and minutes.
EXPWEEKLYHOURS
The Expected Weekly Hours column contains the number of hours that the
employee is expected to work each week. The value can be an integer amount or a
decimal amount.
EXPPAYPERIODHOURS
The Expected Pay Period Hours column contains the number of hours that the
employee is expected to work each pay period. The value can be an integer
amount or a decimal amount.
DEVICEGROUP
The Device Group column contains the name of the group of devices that the
employee is authorized to use.
LOGONNAME
The Logon Name column contains the user name that allows the user to access
Workforce Central. A unique logon name is required; no two users can have the
same logon name.
If your system uses an external method of authorization, such as the Windows NT
or Lightweight Directory Access Protocol (LDAP) username, the logon name
must match.

LOGONPROFILE
The Logon Profile column contains the name of the user’s logon profile. The
logon profile provides rules for password behavior or provides rules for automatic
logout and lockout behavior.
Default and Super Access are predeinfed values. Refer to “Predefined data
values” on page 130. If you do not specify a value, the value is set to Default.
PASSWORD
The Password column contains the user’s password. A value is required if

LOGONNAME contains a value. The value of the password should not be
encrypted.
PASSWORDCHANGE
The Password Change column contains a value indicating whether the user must
change the password the next time that the user logs on. The column can have one
of the following values:
Value Description
0 No password change is required.
1 Password change is required at the next logon.
TRANSFERIN
The Transfer In column indicates whether the user can view data for employees
who have transferred into work labor accounts that match the primary accounts to
which the user has access. The column can have the following values:
Value Description
0 Cannot see transfer ins
1 Can see transfer ins

People Import
EMPGROUPLLSET
The Employee Group Labor Level Set column contains the name of the labor
level set that applies to the user who has the role of a Workforce Manager. The
labor level set identifies the set of primary labor accounts to which the user has
access in this role.
Import provides the predefined data values of Empty Profile and All Labor
Accounts. Refer to “Predefined data values” on page 130. When a new person
with a Workforce Manager license is added, the default of Empty Profile is used if
no other value is specified.
MGRXFERLLSET
The Manager Transfer Labor Level Set column contains the name of the labor
level that applies to users in their role as a Workforce Manager. The labor level
transfer set identifies the set of labor level transfer entries to which the user can
transfer people in this role.
with a Workforce Manager license is added, the default of Empty Profile is used if
no other value is specified.
EMPXFERLLSET
The Employee Transfer Labor Level Set column contains the name of the labor
level set that applies to the user who has a role as a Workforce Employee. The
labor level transfer set identifies the set of labor level transfer entries to which the
use can transfer. The Employee Transfer Labor Level Set value default is the
Empty Profile if a value is not provided.
with a Workforce Employee license is added, the default of Empty Profile is used
if no other value is specified.

EMPPAYCODEDAP
The Employee Pay Code Data Access Profile column contains the name of the
pay code data access profile that applies to the users in their role as a Workforce
Employee. The labor level transfer set identifies the set of labor level transfer
entries to which the use can transfer. The Employee Transfer Labor Level Set
value default is the Empty Profile if a value is not provided.
Import provides the predefined data values of Empty Profile and All Pay Codes.
Refer to “Predefined data values” on page 130. When a new person with a
Workforce Employee license is added, the default of Empty Profile is used if no
other value is specified.
EMPWORKRULEDAP
The Employee Work Rule Data Access Profile column contains the name of the
work rule data access profile that applies to the user who has a role as a Workforce
Employee. The labor level transfer set identifies the set of labor level transfer
entries to which the use can transfer. The Employee Transfer Labor Level Set
value default is the Empty Profile if a value is not provided.
Import provides the predefined data values of Empty Profile and All Work Rules.
Workforce Employee license is added, the default of Empty Profile is used if no
MGRPAYCODEDAP
The Manager Pay Code Data Access Profile column contains the name of the pay
code data access profile that applies to users in their role as a suite manager. This
access profile identifies those pay codes that the user can select.
Import provides the predefined data values of Empty Profile and All Pay Codes.
Workforce Manager license is added, the default of Empty Profile is used if no

People Import
MGRWORKRULEDAP
The Manager Work Rule Data Access Profile column contains the name of the
work rule data access profile that applies to the user who has a role as a Workforce
Manager. This access profile identifies those work rules that the user can select.
Import provides the predefined data values of Empty Profile and All Work Rules.
MGRREPORTDAP
The Manager Report Data Access Profile column contains the name of the report
data access profile that applies to the user who has a role as a Workforce Manager.
This access profile identifies those reports the user can generate or view.
Import provides the predefined data values of Empty Profile and All Reports.
TIMEENTRYMETHOD
The Time Entry Method column indicates the method that the person uses for
entering their time. The column can have one of the following values:
Value Description
1 Timestamp
2 Timestamp and Hourly View
3 Hourly View
4 Project View

Enter a value in this column if you are importing any of following person types:
Value Description
Manager
Scheduler Employee
Activities Employee, Workforce Scheduler Employee, and Workforce
Manager
Workforce Employee
USERFIELD
The User Field column of each import table contains comments or notes about an
WORKERTYPE
The Worker Type column contains the name of the worker type that applies to a
Workforce Timekeeper Employee. This column is optional.

People Import
SCHEDGROUPPROFILE
The Schedule Group Profile column contains the name of a Workforce Manager’s
schedule group profile. This schedule group profile identifies those schedule
groups that the person can select.
Import provides the predefined data values of Empty Profile and All Group
Schedules. Refer to “Predefined data values” on page 130.
SHIFTTMPLPROFILE
The Shift Template Profile column contains the name of a Workforce Manager’s
shift template profile. This shift template profile identifies those shift templates
that the person can select.
Import provides the predefined data values of Empty Profile and All Shift Codes.
Refer to “Predefined data values” on page 130.
PATTERNTMPLPROFILE
The Pattern Template Profile column contains the name of a Workforce Manager’s
schedule pattern template profile. This pattern template profile identifies those
pattern templates that the user can select.
Import provides the predefined data values of Empty Profile and All Schedule
Patterns. Refer to “Predefined data values” on page 130.
SENIORITYDATE
The Seniority Date column contains the seniority date of a Workforce Timekeeper
Employee. This is relevant to users who use a schedule job list, in which each job
has a seniority date associated with it. This column is optional.

Person Date Import table
PERSONDATEIMPORT
The Person Date Import table contains data that may have multiple instances.

PERSONIMPORTID Integer Not Null
RECORDTYPE Character(2) Not Null See “Column Definitions” for
specific values.
STARTDATE Character(10) Null Defaults to the date imported.
STARTTIME Character(8) Null See “Column Definitions” for
exceptions to Null constraint.
ENDDATE Character(10) Null Defaults to January 1, 3000
ENDTIME Character(8) Null See “Column Definitions” for
HOMELABORACCOUNT Character(356) Null See “Column Definitions” for
GROUPSCHEDULE Character(30) Null See “Column Definitions” for
EMPLOYEESTATUS Character(1) Null See “Column Definitions” for
BADGENUMBER Character(15) Null See “Column Definitions” for
USERSTATUS Character(1) Null See “Column Definitions” for
ORGPATHTXT Character(1000) Null See “Column Definitions” for

People Import
Column Definitions
PERSONIMPORTID
The Person Import ID column uniquely identifies the People Import record.
Within the PERSONDATEIMPORT table, it is used to associate
PERSONDATEIMPORT table rows with the related row in the
PERSONIMPORT table.
RECORDTYPE
The Record Type column contains a value that identifies the type of effective date
record that is being imported. A value for this column is always required. The
column can have the following values:
Value Description
1 Employee badge assignment record
2 Employee status record
3 Primary labor account record and organizational path text
4 Group schedule assignment record (creates a group schedule if one does
not exist.)
5 User status record
6 Existing group schedule assignment record (if a group schedule does not
exist, an error message appears.)
STARTDATE
The Start Date column contains the effective date of the record. A value for this
column is optional. If you do not provide a value, the effective date defaults to the
date of the import.

STARTTIME
The Start Time column contains the effective time of the record. A value for this
column is optional. If you do not provide a value, the effective time defaults to
midnight.
Note: This column can only be used with BADGENUMBER imports. It is

ignored for all other operations.
ENDDATE
The End Date column contains the expiration date of the record. Providing a value
for this column is optional. If you do not provide a value, the expiration date
defaults to the latest possible date, which is January 1, 3000.
ENDTIME
The End Time column contains the expiration time of the record. The value or this
column is optional. If you do not provide a value, the effective time defaults to
midnight.
Note: This column can only be used with BADGENUMBER imports. It is

HOMELABORACCOUNT
The Primary Labor Account column contains the name of the employee’s primary
labor account. This value for this column is required only when the value of
record type is 3, which indicates the entry of the employee’s primary labor
account name.
The following is an example of a primary account name that you enter in this
column (depending on how labor levels and accounts are defined in your system):
112/222/332/401/501/601/701. You can use shorthand for the primary labor
account in any labor account entry if you are also importing an organizational path.
If the Record Type indicates the entry of a different type of record, the value in
this column is ignored.

People Import
GROUPSCHEDULE
The Group Schedule column contains the name of the group schedule to which the
employee is assigned. Provide a value for this column only when the value of the
record type is 4 or 6, which indicate the entry of a group schedule assignment.
If the record type value indicates the entry of a different type of record, the value
in this column is ignored.
Use the value # to remove the group schedule name. Using a record type of 4 or 6
with a value of # for the group schedule removes all the schedule groups that are
assigned to an employee during a specified time.
EMPLOYEESTATUS
The Employee Status column contains a value that indicates the employee status.
The column can have the following values:
Value Description
0 Not applicable
1 Active
2 Inactive
3 Terminated
Provide a value for this column only when the value of the record type is 2, which
indicates an entry of employee status. If the record type value indicates the entry
of a different type of record, the value in this column is ignored.
Note: You must specify a valid EMPLOYEESTATUS value if the person is

licensed as a Workforce Timekeeper Employee. If you do not specify a valid value
and the person is licensed, the person is not assigned a license after import. If you
do not specify a value and the person is not licensed, the employee status is set to
Not Applicable.

BADGENUMBER
The Badge Number column contains an employee badge number that is assigned
to the employee. Provide a value for this column only when the value of record
type is 1, which indicates the entry of a badge number assignment. If the record
type value indicates the entry of a different type of record, the value in this column
is ignored.
The system can be configured to allow multiple badges for employees. Specify
whether to allow multiple badge assignments in System Configuration > System
Settings > Global Values > global.BadgeAssignment.allowsOverlap = Yes.
If an employee is assigned multiple badge numbers, each badge number and
associated information is imported in separate import statements. Refer to
“Example: Updating an employee with multiple badge assignments” on page 185.
To remove the badge assignment for the employee, use the # symbol for this
column value. The correct process for removing excess badge numbers is to
remove all existing badge numbers. Reassign the valid number that you want to
keep. Refer to “Example: Deleting multiple badge assignments” on page 187.
USERSTATUS
The User Status column contains a value indicating the status of the user. The
column can have the following values:
Value Description
0 Not applicable
1 Active
2 Inactive
3 Terminated
Provide a value for this column only when the value of record type is 5, which
indicates the entry of a user status. If the record type value indicates the entry of a
different type of record, the value in this column is ignored.

People Import
You must specify a valid value if the person is licensed as a Workforce Employee
or a Workforce Manager. If you do not specify a valid value and the person is
licensed, the person is not assigned a license after import. If you do not specify a
value and the person is not licensed as a Workforce Employee or a Workforce
Manager, the user status is set to Not Applicable.
ORGPATHTXT
The Organizational Path Text column contains the primary job information.
Provide a value for this column only when the value of record type is 3, which
indicates the entry of the employee's primary labor account name and primary
organizational job path text. This column is only required to import a Workforce
Scheduler Employee.
Use @P to substitute for the complete organizational job path when the person’s
primary organizational job does not change.
Note: The labor level entries within a labor account cannot overlap with the
organization-derived account. For example, in the labor account: 101//////
701, the entry 101 overlaps with Organization in the organization-derived
account Organization/Hospitals/Hosp A/Floor 1/ER/RN2.
The combining of an imported labor account and an organizational job path-

derived account must result in a fully qualified labor account. For example, the
labor account /////// and organization-derived account Organization/
Hospitals/Hosp A/Floor 1/ER/RN2 cannot result in a fully qualified
labor account, because the organization-derived account has only six labor level
entries, not seven level entries.

Person Many Import
PERSONMANYIMPORT table
The Person Many Import table contains data that may have multiple instances
where you want to store all instances in the database.

PERSONIMPORTID Integer Not null
RECORDTYPE Character(2) Not null See “Column Definitions” for
specific values.
PHONENUMBERTYPE Character(30) Null See “Column Definitions” for
PHONENUMBER Character(35) Null See “Column Definitions” for
CUSTOMSTRINGTYPE Character(30) Null
CUSTOMSTRING Character(80) Null
STREETADDRESSTYPE Character(30) Null Reserved for future use.
STREETADDRESS Character(100) Null
CITY Character(25) Null
STATE Character(25) Null
POSTALCODE Character(25) Null
COUNTRY Character(25) Null
EMAILADDRESSTYPE Character(30) Null Reserved for future use.
EMAILADDRESS Character(50) Null

People Import
PERSONIMPORTID
The Person Import ID column uniquely identifies the People Import record.
Within the PERSONMANYIMPORT table, it is used to associate
PERSONMANYIMPORT table rows with the related row in the
PERSONIMPORT table.
RECORDTYPE
The Record Type column contains a value that identifies the type of
PERSONMANYIMPORT table record that is being imported. This column is
always required. The column can have the following values:
Value Description
1 Custom string
2 E-mail address
3 Postal address
4 Telephone number
Note: When the value for Record Type is 4, you must specify a value for both the
Phone Number Type and the Phone Number columns.
PHONENUMBERTYPE
The Phone Number Type column contains the name of the customer-defined label
for the different phone number types; for example: home, work, or cellular. You
can enter a maximum of three phone numbers for a person. Provide a value for
this column only when the value of record type is 4, which indicates the entry of a
telephone number. If the record type value indicates the entry of a different type of
record, the value in this column is ignored.

PHONENUMBER
The Phone Number column contains the telephone number. Provide a value for
this column only when the value of record type is 4, which indicates the entry of a
telephone number. If the record type value indicates the entry of a different type of
CUSTOMSTRINGTYPE
The Custom String Type column contains the name of the customer-defined label
for the different custom string types; for example: seniority number, mother’s
maiden name, or Social Security Number. You can enter a maximum of ten
custom strings for a person. Provide a value for this column only when the value
of record type indicates the entry of a custom string. If the record type value
indicates entry of a different type of record, the value in the column is ignored.
CUSTOMSTRING
The Custom String column contains the text of the custom string. Provide a value
for this column only when the value of record type indicates the entry of a custom
string. If the record type value indicates the entry of a different type of record, the
value in this column is ignored.
STREETADDRESSTYPE
The Street Address Type column is reserved for future use.
STREETADDRESS
The Street Address column contains the numerical and street name portion of the
person’s address. Provide a value for this column only when the value of record
type indicates the entry of a postal address. If the record type value indicates the
entry of a different type of record, the value in this column is ignored.

People Import
CITY
The City column contains the city or town portion of the person’s address. Provide
a value for this column only when the value of record type indicates the entry of a
postal address. If the record type value indicates the entry of a different type of
STATE
The State column contains the state or province of the person’s address. Provide a
value for this column only when the value of record type indicates the entry of a
POSTALCODE
The Postal Code contains the postal code portion of the person’s address. Provide
COUNTRY
The Country column contains the country portion of the person’s address. Provide
EMAILADDRESSTYPE
This column is reserved for future use.

EMAILADDRESS
The E-mail Address column contains the employee’s electronic mail address.
Provide a value for this column only when the value of record type indicates the
entry of an e-mail address. If the record type value indicates the entry of a
different type of record, the value in this column is ignored. Only one e-mail
address is allowed.
Predefined data values

Use the predefined data value as it appears in your system. For more information
about predefined data values, refer to the Workforce Central System
Administrator’s Guide.
Column population requirements for adding person types

The person types you can add are listed in the definitions of PERSONTYPE and
NEWPERSONTYPE on pages 1-68 through 1-70. The tables in the “Columns to
Populate” sections later in this chapter list the column population requirements for
adding a person for each of the different person types.
Adding a person
When you are adding a person, a People Import record will have populated
columns in the PERSONIMPORT table, the PERSONDATEIMPORT table, and
potentially, in the PERSONMANYIMPORT table.

People Import
For example, one person type that can be added is a Workforce Timekeeper
Employee, whose values must be populated as follows:
Table Column Notes

PERSONIMPORT PERSONIMPORTID Automatically populated when a row is
inserted
PERSONIMPORT REQ_CODE Can have a value of 1 (add a person) or 3 (add
or update a person)
PERSONIMPORT PERSONTYPE Must have a value of 1 (a Workforce
Timekeeper Employee)
PERSONIMPORT PERSONNUM Must not match the value of PERSONNUM
for any other person entered in Workforce
Timekeeper
PERSONIMPORT LASTNAME As entered
PERSONIMPORT PAYRULE Must match the name of a pay rule already
entered in Workforce Timekeeper
PERSONDATEIMPORT PERSONIMPORTID Must have the same value as the
PERSONIMPORTID in the
PERSONIMPORT table
PERSONDATEIMPORT RECORDTYPE Must have a value of 3 (a primary labor
account)
PERSONDATEIMPORT HOMELABORACCOUNT Must match the name of a labor account
already entered in Workforce Timekeeper
Additional columns may be populated as applicable. If there is a validation error

with any populated column or if a required field is not populated, the entire People
Import record is rejected and will remain in the respective import tables.
For example, if you specify a pay rule name that does not match the name of a pay
rule that is already entered in the database, the defective PERSONIMPORT table
row will remain in the PERSONIMPORT table and the related rows in the
PERSONDATEIMPORT table and PERSONMANYIMPORT table will remain in
their respective tables.

Person Type 1: Workforce Timekeeper Employee

Populate the following People Import columns to add a Workforce Timekeeper
Employee:
Table Column Required/Optional/Ignored

PERSONIMPORT PERSONIMPORTID Required
PERSONIMPORT REQ_CODE Required
PERSONIMPORT PERSONTYPE Required
PERSONIMPORT PERSONNUM Required
PERSONIMPORT NEWPERSONNUM Ignored
PERSONIMPORT FIRSTNAME Optional
PERSONIMPORT MIDNAME Optional
PERSONIMPORT LASTNAME Required
PERSONIMPORT SHORTNAME Optional
PERSONIMPORT HIREDATE Optional
PERSONIMPORT MANAGERNAME Optional
PERSONIMPORT BIRTHDATE Optional
PERSONIMPORT TIMEZONE Optional
PERSONIMPORT PAYRULE Required
PERSONIMPORT WAGERATE Optional
PERSONIMPORT WAGEPROFILE Optional
PERSONIMPORT ACCRUALPROFILE Optional
PERSONIMPORT FUNCACCESSPROF Ignored
PERSONIMPORT DISPLAYPROFILE Ignored
PERSONIMPORT FTEPERCENTAGE Optional
PERSONIMPORT FTEEXPECTEDHOURS Optional
PERSONIMPORT FTEHOURS Optional
PERSONIMPORT EXPDAILYHOURS Optional
PERSONIMPORT EXPWEEKLYHOURS Optional
PERSONIMPORT EXPPAYPERIODHOURS Optional
PERSONIMPORT DEVICEGROUP Optional
PERSONIMPORT LOGONNAME Ignored
PERSONIMPORT LOGONPROFILE Ignored
PERSONIMPORT PASSWORD Ignored
PERSONIMPORT PASSWORDCHANGE Ignored
PERSONIMPORT TRANSFERIN Ignored
PERSONIMPORT EMPGROUPLLSET Ignored
PERSONIMPORT MGRXFERLLSET Ignored
PERSONIMPORT EMPXFERLLSET Ignored

People Import

PERSONIMPORT EMPPAYCODEDAP Ignored
PERSONIMPORT EMPWORKRULEDAP Ignored
PERSONIMPORT MGRPAYCODEDAP Ignored
PERSONIMPORT MGRWORKRULEDAP Ignored
PERSONIMPORT MGRREPORTDAP Ignored
PERSONIMPORT TIMEENTRYMETHOD Ignored
PERSONIMPORT USERFIELD Ignored
PERSONIMPORT WORKERTYPE Optional
PERSONIMPORT SCHEDGROUPPROFILE Ignored
PERSONIMPORT SHIFTTMPLPROFILE Ignored
PERSONIMPORT PATTERNTMPLPROFILE Ignored
PERSONIMPORT SENIORITYDATE Optional
PERSONDATEIMPORT PERSONIMPORTID Required. Separate
PERSONDATEIMPORT table
rows must be populated for each
primary labor account
assignment, group schedule
assignment, employee status
entry, and badge number
assignment as the value of the
RECORDTYPE column
designates which type of record
appears in a given
PERSONDATEIMPORT table
row.
PERSONDATEIMPORT RECORDTYPE Required
PERSONDATEIMPORT ORGPATHTXT Optional
PERSONDATEIMPORT STARTDATE Optional
PERSONDATEIMPORT STARTTIME Optional for
BADGEASSIGNMENT only
PERSONDATEIMPORT ENDDATE Optional
PERSONDATEIMPORT ENDTIME Optional for
PERSONDATEIMPORT HOMELABORACCOUNT Required
PERSONDATEIMPORT GROUPSCHEDULE Optional
PERSONDATEIMPORT EMPLOYEESTATUS Optional
PERSONDATEIMPORT BADGENUMBER Optional
PERSONDATEIMPORT USERSTATUS Ignored


PERSONMANYIMPORT PERSONIMPORTID Required if a record is provided
in the
PERSONMANYIMPORT
table. Separate
custom string entry, phone
number entry, street address
entry, and postal address entry
as the value of the
RECORDTYPE column
designates which type of record
appears in a given
row.
PERSONMANYIMPORT RECORDTYPE Required if a record is provided
in the
PERSONMANYIMPORT
table.
PERSONMANYIMPORT PHONENUMBERTYPE Required if a phone number is
provided.
PERSONMANYIMPORT PHONENUMBER Required if a phone number
type is provided.
PERSONMANYIMPORT CUSTOMSTRINGTYPE Required if a custom string is
provided.
PERSONMANYIMPORT CUSTOMSTRING Required if a custom string type
is provided.
PERSONMANYIMPORT STREETADDRESSTYPE Reserved for future use.
PERSONMANYIMPORT STREETADDRESS Optional
PERSONMANYIMPORT CITY Optional
PERSONMANYIMPORT STATE Optional
PERSONMANYIMPORT POSTALCODE Optional
PERSONMANYIMPORT COUNTRY Optional
PERSONMANYIMPORT EMAILADDRESSTYPE Reserved for future use.
PERSONMANYIMPORT EMAILADDRESS Optional

People Import
Person Type 2: Workforce Employee

Populate the following People Import columns to add a Workforce Employee:

PERSONIMPORT MANAGERRNAME Optional
PERSONIMPORT FUNCACCESSPROF Optional
PERSONIMPORT DISPLAYPROFILE Optional
PERSONIMPORT LOGONNAME Required
PERSONIMPORT LOGONPROFILE Optional
PERSONIMPORT PASSWORD Required
PERSONIMPORT PASSWORDCHANGE Optional
PERSONIMPORT EMPXFERLLSET Optional
PERSONIMPORT EMPPAYCODEDAP Optional


PERSONIMPORT EMPWORKRULEDAP Optional
PERSONIMPORT TIMEENTRYMETHOD Optional
PERSONDATEIMPORT PERSONIMPORTID Required. PERSONDATEIMPORT
table rows must be populated for
each primary labor account
assignment, group schedule
assignment, employee status entry,
badge number assignment, and user
status entry as the value of the
RECORDTYPE column designates
which type of record appears in a
given PERSINDATEIMPORT table
row.
PERSONDATEIMPORT USERSTATUS Optional
PERSONMANYIMPORT PERSONIMPORTID Required if a record in the
PERSONIMPORT table is
provided.

People Import

PERSONMANYIMPORT RECORDTYPE Required if a record in the
PERSONMANYIMPORT table is
provided. Separate
custom string, e-mail address, postal
address, and telephone number, as
the value of the RECORDTYPE
column designates which type of
record appears in a given
row.
provided.
PERSONMANYIMPORT PHONENUMBER Required if a phone number type is
provided.
provided.
PERSONMANYIMPORT CUSTOMSTRING Required if a custom string type is
provided.
PERSONMANYIMPORT STREETADDRESSTYPE Reserved for future use
PERSONMANYIMPORT EMAILADDRESSTYPE Reserved for future use

Person Type 3: Workforce Manager

Populate the following People Import columns to add a Workforce Manager

PERSONIMPORT PAYRULE Ignored
PERSONIMPORT WAGERATE Ignored
PERSONIMPORT WAGEPROFILE Ignored
PERSONIMPORT ACCRUALPROFILE Ignored
PERSONIMPORT FTEPERCENTAGE Ignored
PERSONIMPORT FTEEXPECTEDHOURS Ignored
PERSONIMPORT FTEHOURS Ignored
PERSONIMPORT EXPDAILYHOURS Ignored
PERSONIMPORT EXPWEEKLYHOURS Ignored
PERSONIMPORT EXPPAYPERIODHOURS Ignored
PERSONIMPORT DEVICEGROUP Ignored
PERSONIMPORT TRANSFERIN Optional
PERSONIMPORT EMPGROUPLLSET Optional
PERSONIMPORT MGRXFERLLSET Optional

People Import

PERSONIMPORT MGRPAYCODEDAP Optional
PERSONIMPORT MGRWORKRULEDAP Optional
PERSONIMPORT MGRREPORTDAP Optional
PERSONIMPORT WORKERTYPE Ignored
PERSONIMPORT SCHEDGROUPPROFILE Optional
PERSONIMPORT SHIFTTMPLPROFILE Optional
PERSONIMPORT PATTERNTMPLPROFILE Optional
PERSONIMPORT SENIORITYDATE Ignored
PERSONDATEIMPORT PERSONIMPORTID Required
PERSONDATEIMPORT GROUPSCHEDULE Ignored
PERSONDATEIMPORT EMPLOYEESTATUS Ignored
PERSONDATEIMPORT BADGENUMBER Ignored
provided.
provided. Populate separate table rows in
the PERSONMANYIMPORT column
for each custom string, phone number,
street address, or postal address entry as
the value of RECORDTYPE indicates
which record type appears in a given
PERSONMANYIMPORT table row.
PERSONMANYIMPORT PHONENUMBERTYPE Required if a phone number is provided.
provided.
PERSONMANYIMPORT CUSTOMSTRINGTYPE Required if a custom string is provided.
provided.



Populate the following People Import columns to add a person who is a
Workforce Timekeeper Employee, a Workforce Employee, and a Workforce
Manager:

People Import

BADGEASSIGNMENT only.


provided.
provided.
provided.
provided.
provided.
provided.

Manager
Populate the following People Import column to add a person who is a Workforce
Timekeeper Employee and a Workforce Manager:


People Import



PERSONDATEIMPORT STARTTIME Optional for BADGEASSIGNMENT
only.
PERSONDATEIMPORT ENDTIME Optional for BADGEASSIGNMENT
only.
provided.
provided.
provided.
provided.
provided.
provided.

People Import

Scheduler Employee
Populate the following People Import columns to add person who is a Workforce
Timekeeper Employee and a Workforce Scheduler Employee:

PERSONIMPORT LOGONNAME Ignored
PERSONIMPORT LOGONPROFILE Ignored
PERSONIMPORT PASSWORD Ignored
PERSONIMPORT PASSWORDCHANGE Ignored


PERSONDATEIMPORT ORGPATHTXT Required
provided.
provided.
provided.
provided.

People Import

provided.
provided.

Employee, Workforce Scheduler Employee
Workforce Timekeeper Employee, a Workforce Employee, and a Workforce
Scheduler Employee:




People Import

provided.
provided.
provided.
provided.
provided.
provided.

Scheduler Employee, Workforce Manager
Workforce Timekeeper Employee, a Workforce Scheduler Employee, and a
Workforce Manager




People Import

provided.
provided.
provided.
provided.
provided.
provided.



Employee, Workforce Scheduler, Workforce Manager
Workforce Timekeeper Employee, a Workforce Employee, a Workforce
Scheduler Employee, and a Workforce Manager


People Import

only.
only.
provided.


provided.
provided.
provided.
provided.
provided.

Scheduler Employee, Workforce Activities Employee
Employee, a Workforce Scheduler Employee, and a Workforce Activities
Employee


People Import



only.
only.
provided.
provided.
provided.
provided.
provided.
provided.

People Import

Employee, Workforce Scheduler Employee, Workforce Activities
Employee
Employee, a Workforce Employee, a Workforce Scheduler Employee, and a
Workforce Activities Employee.



only.
only.
provided.
provided.
provided.

People Import

provided.
provided.
provided.

Activities Employee, Workforce Scheduler Employee, Workforce
Manager
Employee, a Workforce Activities Employee, a Workforce Scheduler Employee,
and a Workforce Manager



only.

People Import

only.
provided.
provided.
provided.
provided.
provided.
provided.


Employee, Workforce Activities, Workforce Scheduler, Workforce
Manager
Workforce Timekeeper Employee, a Workforce Employee, a Workforce Activities
Employee, a Workforce Scheduler Employee, and a Workforce Manager


People Import

only.
only.
provided.
provided.
provided.


provided.
provided.
provided.
Person Type 14: Workforce Activities Employee, Workforce

Timekeeper Employee
Workforce Activities Employee and a Workforce Timekeeper Employee


People Import

only.
only.


provided.
provided.
provided.
provided.
provided.
provided.

People Import

Activities Employee, Workforce Employee
Workforce Timekeeper Employee, a Workforce Activities Employee, and a
Workforce Employee.



only.
only.
provided.
provided.
provided.
provided.

People Import

provided.
provided.

Activities Employee, Workforce Manager
Workforce Timekeeper Employee, a Workforce Activities Employee, and a
Workforce Manager



only.
only.

People Import

provided.
provided.
provided.
provided.
provided.
provided.

Activities Employee, Workforce Employee, Workforce Manager
Workforce Timekeeper Employee, a Workforce Activities Employee, a Workforce
Employee and a Workforce Manager




People Import

only.
only.
provided.
provided.
provided.
provided.
provided.
provided.


Updating a person
When updating a person to Workforce Timekeeper, a People Import record will
have populated columns in the PERSONIMPORT Table, potentially, in the
PERSONDATEIMPORT Table, and in the PERSONMANYIMPORT Table.
For example, in the following table, a person’s record needs to be updated to
change their pay rule assignment. The person needs to have values populated for
the following columns. The person type cannot be a Workforce Manager Type 3,
because this type does not have a pay rule assignment.
Table Column Notes

PERSONIMPORT PERSONIMPORTID Automatically populated when a row is
inserted.
PERSONIMPORT REQ_CODE Can have a value of “2” (Update a person)
or “3” (Add or update a person).
PERSONIMPORT PERSONTYPE Can be any person type except Workforce
Manager (Type 3).
PERSONIMPORT PERSONNUM Must match the value of PERSONNUM
for a person entered in Workforce
Timekeeper.
PERSONIMPORT NEWPERSONNUM Must populate with an @ (retains the
current person number value).
Alternatively, can also be populated with
the same value that is used to populate the
PERSONNUM.
PERSONIMPORT PAYRULE Populated with the name of the new pay
rule assignment. This value must match the
name of a pay rule already entered in
Workforce Timekeeper.

People Import
Additional columns may be populated as applicable. If there is a validation error

with any populated column or a required field is not populated, the entire People
Import record is rejected and will remain in the respective import tables.
For example, if you specify a pay rule name that does not match the name of a pay
rule already entered in Workforce Timekeeper, the row in the PERSONIMPORT
Table will remain in the PERSONIMPORT Table, and the related row(s) in the
PERSONDATEIMPORT Table and PERSONMANYIMPORT Table will remain
in their respective tables.
Licensing Using PERSONTYPE and NEWPERSONTYPE
PERSONTYPE only examples
New Person: Assign the license defined in PERSONTYPE.

Current PERSONTYPE = NULL, Current License = None
Resulting
PT NPT PERSONTYPE Resulting Licenses
1 Null/Not included 1 Workforce Timekeeper Employee
2 Null/Not included 2 Workforce Timekeeper Employee and
Workforce Employee
3 Null/Not included 3 Workforce Manager
4 Null/Not included 4 Workforce Timekeeper Employee,
Workforce Employee, and Workforce
Manager
Workforce Manager
Existing Person: Add the license defined in PERSONTYPE if not already

assigned. If already assigned, do nothing.
Note: Adding a license may result in a change to the PERSONTYPE value

because of the additive quality of PERSONTYPE.

Current PERSONTYPE = 1, Current License = Workforce Timekeeper Employee
Resulting
1 Null/Not included 1 (no change) Workforce Timekeeper Employee
Workforce Employee
Workforce Manager
Manager
Workforce Manager

and Workforce Employee
Resulting
1 Null/Not included 2 (no change) Workforce Timekeeper Employee and
Workforce Employee
Workforce Employee
Manager
Manager
Manager

People Import
Current PERSONTYPE = 3, Current License = Workforce Manager
Resulting
Workforce Manager
Manager
3 Null/Not included 3 (no change) Workforce Manager
Manager
Workforce Manager
Current PERSONTYPE = 4, Current License = Workforce Timekeeper Employee,

Resulting
Manager
Manager
Manager
4 Null/Not included 4 (no change) Workforce Timekeeper Employee,
Manager
Manager


and Workforce Manager
Resulting
Workforce Manager
Manager
Workforce Manager
Manager
Workforce Manager
PERSONTYPE and NEWPERSONTYPE examples
New Person: Assign the license defined in PERSONTYPE. Ignore the license
defined in NEWPERSONTYPE. This allows for an add/update situation
(PERSONIMPORT REQ_CODE=3) so that the person can be added if not in the
system or updated if the person is in the system.
Current PERSONTYPE = NULL, Current License = None
Resulting
PT NPT* PERSONTYPE Resulting Licenses
1 1 1 Workforce Timekeeper Employee
2 1 2 Workforce Timekeeper Employee and
Workforce Employee
3 1 3 Workforce Manager

People Import
Resulting
PT NPT* PERSONTYPE Resulting Licenses
4 1 4 Workforce Timekeeper Employee,
Manager
Workforce Manager
* NEWPERSONTYPE can be any number from 0-5 or @. The result should be

the PERSONTYPE value because NEWPERSONTYPE is ignored.
Existing Person:
• Remove the existing license assignment and reassign the license in the
NEWPERSONTYPE. This can be an upgrade or a downgrade. Ignore the
value in PERSONTYPE.
• Remove the existing license assignment if the NEWPERSONTYPE value is
0. Ignore the value in PERSONTYPE.
• Maintain the existing license assignment if the NEWPERSONTYPE value is
@. Ignore the value in PERSONTYPE.
Current PERSONTYPE = 3, Current License = Workforce Manager
Resulting
PT* NPT PERSONTYPE Resulting Licenses
1 0 0 None
1 1 1 Workforce Timekeeper Employee
Workforce Employee
1 3 3 Workforce Manager
1 4 4 Workforce Timekeeper Employee, Workforce
Workforce Manager
1 @ 3 (no change) Workforce Manager

* PERSONTYPE can be any number from 0-5 or @. The result should be the
NEWPERSONTYPE value because PERSONTYPE is ignored.
People import examples

Example: Adding a Workforce Timekeeper Employee with minimal data
The example in this section demonstrates how to add a Workforce Timekeeper

Employee. The employee has a person number, a last name, a pay rule
assignment, and a primary labor account. The primary labor account assignment
takes effect on March 29, 2002 and does not have an expiration date.
All these examples use SQL that will insert rows into tables in a Microsoft SQL
Server database. The syntax for Oracle databases is slightly different. To perform
this function, enter the SQL commands for the PERSONIMPORT and
PERSONDATEIMPORT tables as follows:
1. Specify PERSONIMPORT as the destination for the employee personal data.
2. Specify PERSONDATEIMPORT for the effective data information.
Supply a value for the following PERSONIMPORT columns:
– REQ_CODE
– PERSONTYPE
– PERSONNUM
– LASTNAME
– PAYRULE
– USERFIELD

People Import
Supply a value for the following PERSONDATEIMPORT columns:

– PERSONDATEIMPORTID
– RECORDTYPE
– STARTDATE
– ENDDATE
– HOMELABORACCOUNT
4. Specify the value to be placed in the columns that you identify in the SQL
statement.
SQL Server database
The following example uses Request code 1 to add an employee:

PERSONTYPE, PERSONNUM, LASTNAME, PAYRULE, USERFIELD
Values (1, '1', '1', '8001', 'Jones', 'Support',
'Minimal Employee')
Values (1, '3', '3/29/2002', '', '101/201/301/401/501/
601/701')
Note: The PERSONIMPORTID column value in the second insert statement must
match the PERSONIMPORTID column value provided in the first insert
statement to insert a row in the database.
The SQL INSERT instructions for Oracle and DB2 databases are similar to the
previous SQL Server database example. The only differences are the semicolons
that are used at the end of each statement and the trailing commit statement.


PERSONTYPE, PERSONNUM, LASTNAME, PAYTRULE, USERFILELD)
Values (1, '3', '3/29/2002', '', '101/201/301/401/501/
601/701');
Commit;
Example: Adding a Workforce Timekeeper Employee with complex data
The SQL statements that follow demonstrate an import for adding a Workforce
Timekeeper Employee with complex data. This person has the majority of
columns populated. Note the following conditions:
• Multiple rows are inserted into the PERSONDATEIMPORT and
PERSONMANYIMPORT tables.
• The use of effective-dated columns to enable creation of two consecutive
primary labor account assignments.
This example uses SQL statements that will insert rows into tables in a Microsoft
SQL Server database. The syntax for Oracle databases is slightly different. To
perform this function, enter the SQL commands for the PERSONIMPORT, the
PERSONDATEIMPORT table, and the PERSONMANYIMPORT tables and
follow these guidelines.
1. Specify PERSONIMPORT as the destination for the employee personal data.
2. Specify PERSONDATEIMPORT for the effective date information.
3. Specify PERSONMANYIMPORT for demographic data, such as employee
address.

People Import

– PERSONIMPORTID
– REQ_CODE
– PERSONTYPE
– PERSONNUM
– FIRSTNAME
– MIDNAME
– SHORTNAME
– HIREDATE
– MANAGERNAME
– BIRTHDATE
– TIMEZONE
– PAYRULE
– WAGERATE
– WAGEPROFILE
– ACCRUALPROFILE
– FTEPERCENTAGE
– FTEEXPECTEDHOURS
– FTEHOURS
– DEVICEGROUP
Supply a value for the following PERSONDATEIMPORT columns in the
appropriate SQL statements. This example requires eight statements, one for
each record type.
– PERSONIMPORTID
– RECORDTYPE
– STARTDATE
– ENDDATE

– BADGENUMBER
– EMPLOYEESTATUS
– HOMELABORACCOUNT
– PHONENUMBERTYPE
– PHONENUMBER
– CUSTOMSTRINGTYPE
– CUSTOMSTRING
– STREETADDRESS
– CITY
– STATE
– POSTALCODE
– COUNTRY
– EMAILADDRESS
The following example uses Request Code 1:
PERSONTYPE, PERSONNUM, FIRSTNAME, MIDNAME, LASTNAME,
SHORTNAME, HIREDATE, MANAGERNAME, BIRTHDATE, TIMEZONE,
PAYRULE, WAGERATE, WAGEPROFILE, ACCRUALPROFILE,
FTEPERCENTAGE, FTEEXPECTEDHOURS, FTEHOURS,
DEVICEGROUP)
Values (‘2’, '1', '1', '8003', 'Alicia', 'A', 'Smith',
'Allie', '03/01/2002', null,
'05/21/1965', 'Eastern', 'Support', '50', null, 'VAC,
PRL, SK Full Time', null, '40', '40', null)
RECORDTYPE, STARTDATE, ENDDATE, BADGENUMBER)
Values (2, '1', '3/01/2002', null, '987654321')
RECORDTYPE, STARTDATE, ENDDATE, EMPLOYEESTATUS)
Values (2, '2', '3/01/2002', null, '1')
Insert into PERSONDATEIMPORT (PERSONDATEIMPORTID,

People Import
Values (2, '3', '3/01/2002', '3/05/2002', '101/201/301/

401/501/601/701')
Values (2, '3', '3/06/2002', null, '101/203/305/401/
501/601/701')
Insert into PERSONMANYIMPORT (PERSONIMPORTID,
RECORDTYPE, PHONENUMBERTYPE, PHONENUMBER)
Values (2, '4', 'Phone 1', '555-321-9999')
RECORDTYPE, CUSTOMSTRINGTYPE, CUSTOMSTRING)
Values (2, '1', 'Only Custom Data Field', 'Here is my
work custom string')
RECORDTYPE, STREETADDRESS, CITY, STATE, POSTALCODE,
COUNTRY
Values (2, '3', ‘297 Billerica Road, 'Chelmsford',
'MA', '01824', 'USA')
RECORDTYPE, EMAILADDRESS)
Values (2, '2', 'asmith@Kronos.com')
Refer to the previous example of an Oracle statement in the section Example:
Adding a Workforce Timekeeper Employee with minimal data to create the SQL
statement for this example.
Example: Updating an employee with multiple badge assignments
1. When you add an employee with multiple badge numbers, first add the
employee information. Specify PERSONIMPORT as the destination for the
employee personal data.
2. Specify PERSONDATEIMPORT for the badge assignment information.


– REQ_CODE
– PERSONTYPE
– PERSONNUM
– LASTNAME
– PAYRULE
– NEWPERSONNUM
– USERFIELD
Supply a value for the following PERSONDATEIMPORT columns:
– PERSONDATEIMPORTID
– RECORDTYPE
– BADGENUMBER
– STARTDATE
– STARTTIME
– ENDDATE
4. Specify the value to be placed in the columns that you identify in the SQL
statement.
The following example uses Request Code 2 to import another badge assignment
for an existing person:
PERSONTYPE, PERSONNUM, LASTNAME, PAYRULE, NEWPERSONNUM,
USERFIELD
Values (1, '2', '1', '8001', 'Jones', 'Support', '@',
'Multiple badges')
RECORDTYPE, BADGENUMBER, STARTDATE, STARTTIME, ENDDATE,
Values (1, '1', '1234','2/08/2002', '12:00:00', '10/31/
2002')
The following statement adds the next badge assignment in a subsequent import:

People Import

RECORDTYPE, BADGENUMBER, STARTDATE, STARTTIME, ENDDATE
Values (1, '1', '9876','10/01/2002', '12:00:00', '10/
14/2002')
Example: Deleting multiple badge assignments
In this example, all but one badge assignment is being deleted. First, remove all
badges from the person. Import the badge that remains valid.
PERSONTYPE, PERSONNUM, LASTNAME, PAYRULE, NEWPERSONUM,
USERFIELD
Values (1, '2', '1', '8001', 'Jones', 'Support', '@',
'One badge')
RECORDTYPE, BADGENUMBER, STARTDATE, STARTTIME, ENDDATE,
Values (1, '1', '#','10/15/2002', '4:00:00', '10/31/
2002')
The following statement adds the valid badge assignment in a subsequent import:
Values (1, '1', '9876','10/15/2002', '12:00:00', '12/
15/2002')
Example: Changing the primary labor account assignment of a Workforce

Timekeeper Employee
When you add a person to the database, you know when the assignment becomes
effective, but may not know when the assignment will end. To indicate this, in the
Insert statement for the PERSONDATEIMPORT table, you set the ENDDATE to
NULL.
Values (621, '3', '8/01/2002', null, '101/202/301/401/
501/601/701')

Use either of the following ways to change the primary labor account assignment:
• Include two INSERT instructions for the PERSONDATEIMPORT table, one
to end the current primary labor account assignment, and another to begin the
new assignment.
• Include one Insert statement that contains the start date for the new primary
labor account assignment, and implies the end date of the current account
assignment, based on the start date.
The following examples show each method.
Using Request Code 2 (Update) and two INSERT instructions
The following SQL statements use two INSERT instructions to populate the
PERSONDATEIMPORT table to change a person’s primary labor account
assignment. Note the following information about this example:
• The REQ_CODE column value is set to 2 to indicate an update of an existing
person.
• The first insert into the PERSONDATEIMPORT table provides an explicit
ENDDATE column value for the existing primary labor account assignment,
that is the assignment to primary labor account 101/201/301/401/501/601/701
ends on 7/31/2002.
• The second insert into the PERSONDATEIMPORT Table provides an open-
ended assignment to the primary labor account, 101/202/301/401/501/601/
701 starting on 8/1/2002.
PERSONTYPE, PERSONNUM, NEWPERSONNUM, USERFIELD)
Values (621, '2', '1', '8620', '@', 'Update Person
8620')
Values (621, '3', '1/02/2002', '7/31/2002', '101/201/
301/401/501/601/701')

People Import
Values (621, '3', '8/01/2002', null, '101/202/301/401/

501/601/701')
The following SQL statements use one Insert statement to populate the
PERSONDATEIMPORT table to end the current primary labor account
assignment and begin the new assignment.
As in the previous example, the statement used to populate the
PERSONDATEIMPORT table provides an open-ended assignment to the primary
labor account, 101/202/301/401/501/601/701 starting on 8/1/2002. However, in
this example, the end date of 7/31/2002 for account 101/201/301/401/501/601/
701 is automatically derived from the start date contained in the single Insert
statement.
PERSONTYPE, PERSONNUM, NEWPERSONNUM, USERFIELD)
Values (621, '2', '1', '8620', '@', 'Update person
8620')
values (621, '3', '8/1/2002', null, '101/202/301/401/
501/601/701')
Using Request Code 3 (Add or Update)
The following examples use the Add or Update request code to add a person and
update her primary labor account assignment. (Except for the request code
indication, the statements needed to add a new person are the same as the
statements needed with request code 2.) You must use request code 3 if your data
source only allows you to export all information about a person, not just changes
to that person. Using this request code causes a complete and ever-growing
history of the person to be contained in the SQL statements.
Example 1
Note the following information about this example:
• The REQ_CODE column value is set to 3 to indicate an Add or Update
operation.

• The NEWPERSONNUM column value is set to @ to indicate an update of

the record of person 8621.
• The first insert into the PERSONDATEIMPORT table provides an explicit
ENDDATE column value for the existing primary labor account assignment
(the assignment to account 101/201/301/401/501/601/701 ends on 7/31/
2002).
• The second insert into the PERSONDATEIMPORT Table provides a start
date of 8/1/2002 for the assignment to labor account 101/202/301/401/501/
601/701. It does not specify an end date.
The following are the example INSERT instructions:
Insert into personimport (personimportid, req_code,
persontype, personnum, newpersonnum, firstname,
midname, lastname, shortname, hiredate, managername,
birthdate, timezone, payrule, wagerate, wageprofile,
accrualprofile, ftepercentage, fteexpectedhours,
ftehours, expdailyhours, expweeklyhours,
exppayperiodhours, devicegroup)
Values (622, '3', '1', '8621', '@', 'Helen', 'J',
'Importico', 'Helen', '01/02/2002', null, '04/03/1963',
'Eastern', 'Support', '50', null, 'VAC, PRL, SK Full
Time', null, '40', '40', '8', '40', '80', null)
Insert into persondateimport (personimportid,
recordtype, startdate, enddate, homelaboraccount)
Values (622, '3', '1/02/2002', '7/31/2002', '101/201/
301/401/501/601/701')
Values (622, '3', '8/1/2002', null, '101/202/301/401/
501/601/701')

People Import
Example 2
In the following example, no explicit ENDDATE column value is provided for
any primary labor account assignment. Instead, the value for this column is
derived from the STARTDATE column value of any subsequent primary labor
account assignment. Therefore, the assignment to account 101/201/301/401/501/
601/701 has an end date of 7/31/2002, derived from the start date of 8/1/2002
for the subsequent primary labor account assignment.
Insert into personimport (personimportid, req_code,
persontype, personnum, newpersonnum, firstname,
midname, lastname, shortname, hiredate, managername,
birthdate, timezone, payrule, wagerate, wageprofile,
accrualprofile, ftepercentage, fteexpectedhours,
ftehours, expdailyhours, expweeklyhours,
exppayperiodhours, devicegroup)
Values (623, '3', '1', '8621', '@', 'Helen', 'J',
'Importico', 'Helen', '01/02/2002', null, '04/03/1963',
'Eastern', 'Support', '50', null, 'VAC, PRL, SK Full
Time', null, '40', '40','8', '40', '80', null)
Values (623, '3', '1/02/2002', null, '101/201/301/401/
501/601/701')
Values (623, '3', '8/1/2002', null, '101/202/301/401/
501/601/701'
If the Insert statement runs successfully, verify that the record to add the person is
included in the PERSONIMPORT table. To do this, issue a Select statement
similar to the following command:
Select * from PERSONIMPORT where PERSONNUM = '8621'
Example 3
In this example, an employee with multiple Person Types (Type 4) is terminated.
The person’s identification is retained in the updated record.

Insert into PERSONIMPORT (PERSONIMPORTID,

REQ_CODE,PERSONTYPE,PERSONNUM,NEWPERSONNUM,
NEWPERSONTYPE)
Values (231,'2', '4', '76534', '@', '0')
Example 4
In this example, a person with multiple Person Types (Type 5) is changed to
Type 1.
PERSONTYPE, PERSONNUM, NEWPERSONNUM,NEWPERSONTYPE)
Values (231,'2', '5', '76534', '@', '1')
In Examples 3 and 4, changing the existing employee’s Person Type automatically
changes the Employee Status and User Account Status.
Using Request Code 4 (Delete a Person)
The following example uses the Delete Person request code to delete a person:
PERSONNUM, PERSONTYPE)
Values (2, '4', '1001', '1')
Once you delete a person using this method, you must reimport the information to
restore the person. Refer to “Example: Adding a Workforce Timekeeper
Employee with minimal data.”

Punch Import
Punch Import
PUNCHIMPORT table
The Punch Import table enables the import of employee punch information. A
punch is an entry into the employee’s time sheet. You can perform the following
import operations for punches using either an employee ID number or an
employee badge number:
• Add a punch
• Delete a punch
• Clear a punch work rule transfer
• Add a comment to a punch

PNCHIMPID Integer Not Null Automatically populated
REQ_CODE Character(2) Not Null See “Column definitions” on page
PDATE Character(10) Not Null
PTIME Character(8) Not Null
LABORACCT Character(356) Null See “Column definitions” on page
TIMEZONE Character(30) Null
COMMENTTEXT Character (255) Null

Column definitions
PNCHIMPID
The Punch Import ID column establishes a unique sequence number for each
entry that goes into the PUNCHIMPORT table. This column is required when
inserting a Punch Import entry in an Oracle database. A value for this column is
automatically generated when you insert a Punch Import entry in a SQL Server or
DB2 database.
REQ_CODE
REQ_CODE Value Description

6 Add a punch using the employee’s ID number.
7 Add a punch using the employee’s badge number.
8 Delete a punch using the employee’s ID number.
9 Delete a punch using the employee’s badge number.
18 Clear a work rule using the employee’s ID number. This removes
a work rule transfer that is already in place.
19 Clear a work rule using the employee’s badge number. This
removes a work rule transfer that is already in place.
27 Add a comment using the employee’s ID number.
28 Add a comment using the employee’s badge number.

Punch Import
EMPID
The Employee Identification column identifies the employee by an identification

number or badge number. This column is always required:
REQ_CODE Value EMPID Value

6, 8, 18, or 27 Contains the employee’s ID number.
7, 9, 19, or 28 Contains the employee’s badge number.
PDATE
The Punch Date column contains one of the following entries:

• The date of the punch that is being added or deleted
• The date of the punch for which you are adding a comment
• The date of the punch for which the work rule is being cleared
If you are clearing a work rule transfer, use a different combined PDATE and
PTIME than was used for the work rule transfer. If you erroneously put in a work
rule transfer, to clear it, delete the punch.
PTIME
The Punch Time column contains one of the following:

• The time of the punch that is being added or deleted
• The time of the punch for which you are adding a comment
• The time of the punch for which the work rule is being cleared
If you add a punch with a work rule other than the employee’s default work rule,
the work rule behaves as a “transfer” work rule. Therefore, to change the work
rule, delete the punch. Add the punch again with the new work rule.

WORKRULE
The Work Rule column contains the work rule associated with the punch. Work
rules apply a different set of pay rules to the employee’s time. The application of
these rules determines how employee hours are calculated. The value in this
column is populated only when a work rule other than the employee’s usual work
rule is applied to the punch that is being added. For all other operations, any value
in the column is ignored.
LABORACCT
The Labor Account column contains the name of the labor account of the
employee whose punch is being imported. This column is optional when you add
a punch. You can leave this column blank if the punch applies to the employee’s
primary account. For all other operations, any value in this column is ignored.
Enter data for labor accounts in the same format as they were configured. If you
have a seven-level labor account configured, specify a value for each labor level,
using the following format:
101/202/303/404/504/603/702.
You may leave blank any labor levels that are not changing; for example, you can
entries are different. If any of the labor levels should stay the same as the
employee’s primary labor account, you can enter @H for those labor levels
instead of entering the labor entry names. For more information about how to
indicate labor accounts, see the Workforce Central Import User’s Guide .
If your system is set up to allow you to create new labor level entries when you
add punches (“ad hoc” labor level entries), you can create those new entries when
specifying the labor account. For more information about ad hoc labor level
entries, see the Workforce Central Import User’s Guide .
TIMEZONE
The Time Zone column identifies the time zone being applied to the punch. Add
either the name of the time zone or use the five-digit TIMEZONE as the value in
this column.

Punch Import
This column is optional if you are adding a punch. However, for punches that
were added with a TIMEZONE value, the column is required for all delete, clear,
or comment operations.
All time zone ID numbers are listed in Appendix B “Time Zone Definitions” in
the Workforce Timekeeper Database Tables Reference Guide.
COMMENTTEXT
The Comment Text column contains a comment string that is attached to the
punch being added or edited. This column is required only when you add a
comment to a punch (27, 28). It is optional when adding a punch (6, 7). It is
You can use this column to provide details about the punch. The string in this
column must match exactly an applicable comment that already exists in the
database. The string matching is case-sensitive.
USERFIELD
ORGPATHTXT
The Organizational Path Text column contains the primary organizational job
information of the employee whose punch is being imported. This column is
optional. You can leave this column blank if the punch applies to the employee's
primary organizational job.
organizational job.

Required columns
REQ_CODE
6, 7, 8, 9, 18, 19
Supply a value for each of the following columns when you add punches (6, 7),
delete punches (8, 9) punches, or clear a work rule (18, 19):
• PNCHIMPID (Oracle only)
• REQ_CODE
• EMPID
• PDATE
• PTIME
REQ_CODE
27, 28
Supply a value for each of the following columns when you add a comment to a
punch (27, 28).
• PNCHIMPID (Oracle only)
• REQ_CODE
• EMPID
• PDATE
• PTIME
• COMMENTTEXT
Punch import examples


Punch Import
Example: How to add a punch
The example in this section demonstrates how to add a new punch in the
PUNCHIMPORT table. To perform that function, enter the SQL Insert command
by following these guidelines.
1. Specify PUNCHIMPORT as the destination table for the data.
PUNCHIMPORT table requires you to specify values for new punches as
follows:
– PNCHIMPID
– REQ_CODE
– EMPID
– PDATE
– PTIME
SQL Server database
The following example uses request code 6 to add a punch:

Insert into PUNCHIMPORT (REQ_CODE, EMPID, PDATE, PTIME)
VALUES ('6', '4321', '9/7/00', '1:12 PM')

Insert statement:

REQ_CODE 6 Adds a punch using the employee’s ID number.
PDATE 9/7/00 Identifies the date of the punch.
PTIME 1:12 PM Identifies the time of the punch.
Oracle databases require that the PNCHIMPID column and its value be listed as
the first column and value in the SQL Insert statement. The value is
NGP_PUNCHIMPORT.NEXTVAL.
If the Insert statement runs successfully, verify that the record to add the new
punch to the database is included in the PUNCHIMPORT table.
Select * from PUNCHIMPORT where EMPID = '4321'
Example: How to delete a punch
The example in this section demonstrates how to delete a punch by using the
PUNCHIMPORT table. To perform that function, enter the SQL Insert command
by following these guidelines:

Punch Import
– Each table has columns that require you to specify a value. The
PUNCHIMPORT table requires you to specify values for deleted punches
as follows:
– PNCHIMPID
– REQ_CODE
– EMPID
– PDATE
– PTIME
SQL Server database
The following example uses request code 9 to delete a punch:

Values ('8', '5678', '9/7/00', '1:12 PM')
Insert statement:

REQ_CODE 9 Deletes a punch, using the employee’s badge
number.
PDATE 9/7/00 Identifies the date of the punch to be deleted.
PTIME 1:12 PM Identifies the time of the punch to be deleted.



If the Insert statement runs successfully, verify that the record to delete the punch
from the database is included in the PUNCHIMPORT table. To do this, issue a
Select statement similar to the following command:
Example: How to clear a work rule

The example in this section demonstrates how to clear a work rule by using the
PUNCHIMPORT table. Clearing a work rule allows you to remove or stop a work
rule transfer that is already in place. To perform that function, enter the SQL Insert
PUNCHIMPORT table requires you to specify values for cleared work rules
as follows:
– PNCHIMPID
– REQ_CODE
– EMPID
– PDATE
– PTIME

Punch Import
SQL Server database
The following example uses request code 18 to clear a work rule for an employee:
Values ('18', '4321', '9/7/00', '1:12 PM')
Insert statement:

REQ_CODE 18 Clears a work rule using the employee’s ID number.
If the Insert statement runs successfully, verify that the record to clear the work
rule is included in the PUNCHIMPORT table. To do this, issue a Select statement

Example: How to add a comment to a punch
The example in this section demonstrates how to add a comment to a new punch
or an existing punch in the PUNCHIMPORT table. To perform that function, enter
the SQL Insert command by following these guidelines:
PUNCHIMPORT table requires you to specify values for a punch with a
comment as follows:
– PNCHIMPID
– REQ_CODE
– EMPID
– PDATE
– PTIME
– COMMENTTEXT
SQL Server database

Adding a Comment When You Add a Punch
You can add a comment when you add the punch.
Insert into PUNCHIMPORT (REQ_CODE, EMPID, PDATE, PTIME,
COMMENTTEXT)
VALUES ('6', '4321', '9/8/00', '1:12 PM', 'Early, by
request')

Punch Import
Insert statement:

REQ_CODE 6 Adds a punch using the employee’s ID number.
COMMENTTEXT Early, by Contains the text of the comment. The text in this
request column must match an applicable comment in
the database and apply for this category.
Adding a Comment to an Existing Punch

You can add a comment to an existing punch using the employee’s ID number or
the employee’s badge number.
Insert into PUNCHIMPORT (REQ_CODE, EMPID, PDATE, PTIME,
COMMENTTEXT)
VALUES ('27', '4321', '9/8/00', '1:12 PM', 'Needs
Review')
Insert statement:

REQ_CODE 27 Adds a comment to an existing punch using
the employee’s ID number.
COMMENTTEXT Needs Review Contains the text of the comment. The text
in this column must match an applicable
comment in the database and apply for this
category.

If the Insert statement runs successfully, verify that the record with the comment
is included in the PUNCHIMPORT table. To do this, issue a Select statement

Scheduled Pay Code Edits Import
SCHEDPCEIMPORT table
The Scheduled Pay Code Edits Import table enables the import of employee
schedule pay code edit information from an external system. Scheduled pay code
edits are used when it is known in advance that employees will be entering a
different pay code, such as training or company shutdown periods.
You can perform the following import operations:
• Add a scheduled pay code edit for an employee
• Delete a scheduled pay code edit
• Add a comment to a schedule pay code edit

SCHEDPCEIMPID Integer Not null Automatically populated
REQ_CODE Character(2) Not null See “Column definitions” on page
EMPID Character(15) Not null
SDATE Character(15) Not null
STIME Character(15) Null See “Column definitions” on page
AMOUNT Character(15) Null See “Column definitions” on page
PAYCAT Character(50) Null See “Column definitions” on page
COMMENTTEXT Character(255) Null See “Column definitions” on page

Column definitions
SCHEDPCEIMPID
The Schedule Pay Code Edit Import ID column sets a unique sequence number for
each entry that goes into the SCHEDPCEIMPORT table.
This column is required when inserting a schedule pay code edit entry in an
Oracle database. A value for this column is automatically generated when you
insert a schedule pay code edit entry in a SQL Server or DB2 database.
REQ_CODE
The Request Code column indicates the action you want to perform. This column
is always required.
Value Description
1 Add a scheduled pay code edit.
10 Delete a scheduled pay code edit.
27 Add a comment using the employee’s ID number.
EMPID
The Employee ID column contains the ID number of the employee who is being
affected by the scheduled pay code edits. This column is always required.
SDATE
The SDATE (Start Date) column contains the date of the scheduled pay code edit.
STIME
The STIME (Start Time) column contains the start time of the scheduled pay code
edit. This column is always required.

AMOUNT
The Amount column contains the amount of the pay code edit. The amount can be
either time (formatted as hh:mm) or money, whichever is appropriate to the
associated pay code (which you indicate in the PAYCAT column). This column is
always required.
PAYCAT
The PAYCAT (Pay Code) column contains the pay code that is associated with the
pay code edit. REQ_CODE Values 1 and 27 are required.
LABORACCT
The LABORACCT (Labor Account) column contains the labor account that is
associated with the pay code. Note the following information:
• If the scheduled pay code edit applies to the employee’s primary account,
leave this column blank.
• If the scheduled pay code edit applies to a labor account other than the
employee’s primary account, you must enter a value.
• If you are adding a comment to a scheduled pay code edit that had an explicit
value for LABORACCT when it was imported, you must enter that value.
• When you are deleting a scheduled pay code edit, this column is ignored.
Leave the column blank.
REQ_CODE Value Value Requirement

1 Optional
10 Ignored
27 Required when the scheduled pay code edit being commented
already contains a value for the labor account column

have a seven-level labor account configured, specify a value for each labor level,
using the format shown in the following example:
101/202/303/404/504/603/702.
You do not have to enter values for any labor levels that are not changing. For
example, you can enter 101//303////, indicating that only the first and third labor
level entries are different.
entry names.
For more information about indicating labor accounts, see the Workforce
Timekeeper Import User Guide.
COMMENTTEXT
The Comment Text column contains a comment string that is attached to the
scheduled pay code edit. The string in this column must match exactly an
applicable comment that already exists in the database and apply for this category.
The string matching is case-sensitive. This column is required according to the
Request Code, as follows:

1 Optional
10 Ignored
27 Required
USERFIELD
The User Field column contains comments or notes about an import entry.

ORGPATHTXT
The Organizational Path Text column contains the organizational job path of the
employee whose scheduled pay code edit is being imported.
The column is required if the scheduled pay code edit applies to an organizational
job other than the employee's primary organizational job.
The column is optional when you add a scheduled pay code edit. You can leave
this column blank if the scheduled pay code edit applies to the employee's primary
organizational job. This column is ignored when you are deleting a scheduled pay
code edit.
If you adding a comment to a scheduled pay code edit that had an explicit value
for ORGPATHTXT when it was imported, you must enter that value.
organizational job.
Required columns
REQ_CODE 1
Supply a value for each of the following columns when you add a scheduled pay
code edit:
• SCHEDPCEIMPID (Oracle only)
• REQ_CODE
• EMPID
• SDATE
• STIME
• AMOUNT
• PAYCAT

REQ_CODE 10
Supply a value for each of the following columns when you delete scheduled pay
code edits:
• REQ_CODE
• EMPID
• SDATE
• STIME
• AMOUNT
• PAYCAT
REQ_CODE 27
Supply a value for each of the following columns when you add a comment to a
scheduled pay code edit:
• REQ_CODE
• EMPID
• SDATE
• STIME
• AMOUNT
• PAYCAT
• COMMENTTEXT
Scheduled pay code edit import examples

All allthe examples that follow use SQL that will insert rows into tables in a

Example: How to add a scheduled pay code edit
The example in this section demonstrates how to use the SCHEDULEIMPORT

table to import a scheduled pay code edit. To perform that function, enter the SQL
1. Specify SCHEDPCEIMPORT as the destination table for the data.
SCHEDPCEIMPORT table requires you to specify values for adding
scheduled pay code edits, as follows:
– SCHEDPCEIMPID (Oracle only)
– REQ_CODE
– EMPID
– SDATE
– STIME
– AMOUNT
– PAYCAT
SQL Server database
The following example uses request code 1 to add a scheduled pay code edit for
an employee:
Values ('1', '4321', '9/5/01', '3:00 PM', '3:00',
'Regular')

Insert statement:

REQ_CODE 1 Adds a new record.
SDATE 9/5/01 Identifies the date that the edit should occur.
STIME 3:00 PM Identifies the start time of the edit.
AMOUNT 3:00 Identifies the number of hours of the pay code edit.
PAYCAT Regular Identifies the name of the pay code.
Oracle databases require that the SCHEDPCEIMPID column and its value be
NGP_SCHEDPCEIMPORT.NEXTVAL.
If the Insert statement runs successfully, verify that the record that adds the new
scheduled pay code edit to the database is included in the SCHEDPCEIMPORT
Select * from SCHEDPCEIMPORT where EMPLOYEEID = '4321'
Example: How to add a comment to a scheduled pay code edit
The examples in this section demonstrate how to use the SCHEDULEIMPORT

table to add a comment to a scheduled pay code edit import. To perform that
function, enter the SQL Insert command and follow these guidelines:

SCHEDPCEIMPORT table requires you to specify values for adding scheduled
pay code edits, as follows:
– REQ_CODE
– EMPID
– SDATE
– STIME
– AMOUNT
– PAYCAT
– COMMENTTEXT
SQL Server database
Adding a Comment When You Add a New Record

You can include a comment in a scheduled pay code edit when you add a new
record. The following example uses request code 1 to add a new scheduled pay
code edit with the comment ‘Needs Review’:
STIME, AMOUNT, PAYCAT, COMMENTTEXT)
Values ('1', '4321', '9/7/01', '3:00 PM', '3:00',
'Regular', 'Needs Review')

Insert statement:

REQ_CODE 1 Adds a new record.
SDATE 9/7/01 Identifies the start date of the pay code edit.
STIME 3:00 PM Identifies the start time of the pay code edit.
AMOUNT 3:00 Identifies the number of hours associated with
the pay code edit.
this column must match an applicable comment
created in the database and apply for this
category.
Adding a Comment to an Existing Entry

You can add a comment by employee ID to an existing scheduled pay code edit
entry. The following example uses request code 27 to add the comment
‘Approved’:
STIME, AMOUNT, PAYCAT, COMMENTTEXT)
Values ('27', '4321', '9/5/00', '3:00 PM', '3:00',
'Regular', 'Approved')
Insert statement:

REQ_CODE 27 Adds a comment by employee’s ID number.
SDATE 9/5/00 Identifies the start date of the pay code edit.


AMOUNT 3:00 Identifies the number of hours associated with the
pay code edit.
COMMENTTEXT Approved Contains the text of the comment. The text in this
column must match an applicable comment
created in the database and apply for this category.
For more information about the columns used in these examples, see the
previously described section “Column definitions” on page 208.
If the Insert statement runs successfully, verify that the record that adds the
comment to the database is included in the SCHEDPCEIMPORT table.
Select * from SCHEDPCEIMPORT where EMPLOYEEID = '4321'
Example: How to delete a scheduled pay code edit
The example in this section demonstrates how to use the SCHEDPCEIMPORT

table to delete a specific scheduled pay code edit. To perform that function, enter
the SQL Insert command and follow these guidelines:

SCHEDPCEIMPORT table requires you to specify values for deleting a
scheduled pay code edit, as follows:
– REQ_CODE
– EMPID
– SDATE
– STIME
– AMOUNT
– PAYCAT
SQL Server database
The following example uses request code 10 to delete a scheduled pay code edit
for an employee:
Values ('10', '4321', '9/7/01', '3:00 PM', '3:00',
'Regular')
Insert statement:

REQ_CODE 10 Deletes scheduled pay code edits that begin on the given
date.


SDATE 9/7/01 Specifies the date of the pay code edits to be deleted.
AMOUNT 3:00 Identifies the number of hours associated with the pay
code edit.
If the Insert statement runs successfully, verify that the record that deletes the
scheduled pay code edit from the database is included in the
SCHEDPCEIMPORT table. To do this, issue a Select statement similar to the
following command:
Select * from SCHEDPCEIMPORT where EMPID = '4321'

Schedule Import
SCHEDULEIMPORT table
The SCHEDULEIMPORT table enables the import of employee schedule
information. Schedules includes dates and times of shifts, breaks, and off days.
You can perform the following import operations for a specified employee:
• Delete all schedule shifts, pay codes, and off days that begin on a specified
date
• Add a new shift
• Insert a break in a shift
• Insert a transfer in a shift
• End a shift
• Add a new full or partial off day (a day that a person is not available to work)
• Delete all schedule shifts and off days that begin on a specified date
• Add a new off shift (a shift for an off day on which a person is available to
work, if necessary
• Add a comment for an off day, a shift, or an off shift

Schedule Import

SCHEDIMPID Integer Not null Automatically populated
REQ_CODE Character(2) Not null See “Column definitions” on page
SDATE Character(15) Null
STIME Character(15) Null See “Column definitions” on page
DURATION Character(15) Null
COMMENTTEXT Character(255) Null See “Column definitions” on page
Column definitions
SCHEDIMPID
The Schedule Import ID column is the primary key for the SCHEDULEIMPORT
table. This column establishes a unique sequence number for each entry that goes
into the SCHEDULEIMPORT table.
This column is required when you insert a Schedule Import entry into an Oracle
database. This column value is automatically generated when a Schedule Import
entry is inserted in a SQL Server database.

REQ_CODE
column is always required:
REQ_CODE
Value Description
10 Delete all scheduled shifts, pay codes, and off days that begin on
the specified date.
11 Begin importing a new shift.
12 Insert a break in a shift.
13 Insert a transfer in a shift.
14 End a shift.
15 Import a new off day.
16 Delete all scheduled shifts and off days that begin on the
specified date.
17 Add a comment for an off day.
21 Add a comment for a shift
41 Add an off shift (a shift for an off day on which a person is
available to work, if necessary).
42 Add a comment for an off shift
If you use a duration amount with request code 13 to insert a transfer within a
shift, the duration amount is ignored. The transfer begins at the start time that you
specify and extends to the end of the shift.
If you do not want the duration amount to be ignored:
1. Use request code 11 to define a shift with a duration that extends to the end of
the transfer period.
2. Use request code 13 to start the transfer at the desired time with no duration
amount, and request code 14 to end the shift import.
3. Use request code 11 to define another shift that starts at the end of the transfer
period and with a duration that stretches to the end of the overall shift.
4. Use request code 14 to end the second shift import.

Schedule Import
EMPID
The Employee ID column contains the ID number of the employee who is being
affected by the schedule imports and deletions. This column is always required.
SDATE
The Start Date column contains information that depends on the value in the
REQ_CODE column, as follows:
REQ_CODE Value SDATE Value

10 The start date of the shift, pay code, or off day being deleted
11 The start date of the shift being imported
12 The start date of the break being imported
13 The start date of the transfer being imported
15 The start date of the off day being imported
16 The start date of the shift or off day being deleted
17 The date of the off day
21 The date that the comment was added to the shift
41 The start date of the off shift being imported
42 The date of the off shift
This column is required when you delete all scheduled shifts (10), import a shift
(11), insert a break (12), insert a transfer (13), import an off day (15), or import a
shift comment (21), or import an off shift (41).

STIME
The Start Time column contains information that depends on the value in the
REQ_CODE Value STIME Value

11 The start time of the shift being imported
12 The start time of the break being imported
13 The start time of the transfer being imported
15 The start time of the off day being imported
17 The date of the off day
41 The start time of the off shift being imported
42 The date of the off shift
This column is required whenever you import a shift (11), insert a break in a shift
(12), insert a transfer in a shift (13), import a shift commnet (21), or import an off
shift (41). It is optional when importing an off day (15). If you do not specify a
value, the off day start time defaults to the start of the day.
Note: An error is reported if an STIME column value is specified without a

corresponding DURATION column value.
DURATION
The Duration column contains information that depends on the value in the
REQ_CODE Value DURATION Value

11 The elapsed time of the shift being imported, in hours and minutes
(hh:mm)

Schedule Import
REQ_CODE Value DURATION Value

12 The elapsed time of the break being imported, in hours and minutes
(hh:mm)
15 If importing a partial off day, the duration of the off time, in hours
and minutes (hh:mm)
17 The elapsed time of the off day that contains the comment
41 The elapsed time of the off shift being imported, in hours and
minutes (hh:mm)
42 The elapsed time of the off shift that contains the commnet
This column is required when you import a shift (11), insert a break in a shift (12),
import a shift comment (21), or import an off shift (41). It is optional when
importing an off day (15). If you do not specify a value, the off day duration
defaults to the duration of a day.
Note: An error is reported if a duration column value is specified without a

corresponding STIME column value.
LABORACCT
The Labor account column indicates the labor account to which the employee is
transferring. This column is optional when adding a shift (11), inserting a transfer
within a shift (13), or adding an off shift (41). When adding a shift (11), this
column can be left blank if the shift being added applies to the employee’s
primary labor account.
When inserting a transfer within a shift (13) or adding an off shift (41), you must
specify a value for the LABORACCT, WORKRULE column, or the
ORGPATHTXT column.
You must specify a value for LABORACCT when you are adding or updating a
comment to an off day (17), to a shift (21), or to an off shift (42) if the off day,
shift, or off shift already contains a LABORACCT value.
The LABORACCT column is ignored for all other Schedule Import operations.

have a seven-level labor account in the configured, specify a value for each labor
level, using the following format:
101/202/303/404/504/603/702
You can leave blank any labor levels that are not changing in a labor account
transfer when you are beginning a new shift or inserting a transfer in a shift.
For example, if J.D. Smith is transferring
From account: 101/202/303/404/504/603/702
To account: 102/202/304/404/504/603/702
entries are different.
entry names.
For more information about how to indicate labor accounts, see the Workforce
Timekeeper Import User Guide.
WORKRULE
The Work Rule column indicates the work rule that is being applied to the
employee’s schedule. Work rules apply a different set of pay rules to the
employee’s time. The application of these rules determine how employee hours
are calculated.
You must specify a value for the WORKRULE column when you are adding or
updating a comment to an off day (17), to a shift (21), or to an off shift (42), if that
shift, off day or off shift already contains a WORKRULE value.
When adding a shift, you can leave this column blank if the shift being added
applies to the employee’s usual work rule. When inserting a transfer within a shift
or adding an off shift, you must specify a value for the WORKRULE column, the
LABORACCT column, or the ORGPATHTXT column. The work rule column is
ignored for all other Schedule Import operations.

Schedule Import
USERFIELD
ORGPATHTXT
The Organizational Path Text column contains the organizational job path to
which the employee is transferring.
You must specify a value for ORGPATHTXT when you are addding or updating a
comment to an off day (17), to a shift (21), or to an off shift (42) if that shift, off
day, or off shift already contains an ORGPATHTXT value.
This column is optional when you import a shift (11), insert a transfer (13), import
an off day (15), or import an off shift (41). When adding a shift (11), this column
can be left blank if the shift being added applies to the employee's primary
organizational job.
When inserting a transfer within a shift (13) or adding an off shift (41), you must
specify a value for LABORACCT column, the WORKRULE column, or
ORGPATHTXT column.
server that connects to an Oracle database. Use the shorthand notation @P to
substitute for the person’s existing primary organizational job.
COMMENTTEXT
The Comment Text column contains a comment string that is attached to the shift,
not the shift segments. The string in this column must match exactly a comment
that already exists in the database and belong to the schedule category. The string
matching is case-sensitive.

The column is required according the Request Code, as follows:

11 Optional
12 Ignored
13 Ignored
14 Ignored
15 Optional
17 Required
21 Required
42 Required
Required columns
REQ_CODE 10
Supply a value for each of the following columns whenever you delete all
scheduled shifts, pay codes, and off days that begin on a date:
• SCHEDIMPID (Oracle only)
• REQ_CODE
• EMPID
• SDATE
REQ_CODE 11
Supply a value for each of the following columns whenever you begin importing a
shift:
• REQ_CODE

Schedule Import
• EMPID
• SDATE
• STIME
• DURATION
REQ_CODE 12
Supply a value for each of the following columns when you insert a break in a
shift:
• REQ_CODE
• EMPID
• SDATE
• STIME
• DURATION
REQ_CODE 13
Supply a value for each of the following columns to insert a transfer in a shift:
• REQ_CODE
• EMPID
• SDATE
• STIME
You must supply a value for the LABORACCT column, the WORKRULE
column, the ORGPATHTXT column, or any combination.
Note: REQ_CODE value 13, Insert a transfer in a shift, ignores the duration of the
inserted shift.

REQ_CODE 14
Supply a value for each of the following columns to end a shift:

• REQ_CODE
• EMPID
REQ_CODE 15
Supply a value for each of the following columns to import an off day:
• REQ_CODE
• EMPID
• SDATE
REQ_CODE 16
Supply a value for each of the following columns whenever you delete all
scheduled shifts and off days that begin on a date:
• REQ_CODE
• EMPID
• SDATE
REQ_CODE 17
Supply a value for the following column whenever you add a comment for an off
day:
• COMMENTTEXT
• REQ_CODE

Schedule Import
• EMPID
• LABORACCT
• WORKRULE
Supply a value for LABORACCT, WORKRULE, or ORGPATHTXT if the off
day that had a comment added already contains a value for them:
REQ_CODE 21
Supply a value for the following column whenever you add a comment for a shift:
• COMMENTTEXT
• REQ_CODE
• EMPID
• SDATE
• STIME
• DURATION
Supply a value for the LABORACCT, WORKRULE, or ORGPATHTXT if the
shift that had a comment added already contains a value for them.
REQ_CODE 41
Supply a value for the following columns to import an off shift (shift for an off
day on which a person is available to work, if necessary):
• REQ_CODE
• EMPID
• SDATE
• STIME
• DURATION

You must supply a value for the LABORACCT column, the WORKRULE
column, the ORGPATHTXT column, or any combination.
REQ_CODE 42
Supply a value for the following column whenever you add a comment for an off
shift:
• COMMENTTEXT
• REQ_CODE
• EMPID
• SDATE
• STIME
• DURATION
Supply a value for the following columns if the shift that had a comment added
already contains a value for them:
• LABORACCT
• WORKRULE
• ORGPATHTXT
Schedule import examples
Example: How to Delete Scheduled Shifts

table to delete one of an employee’s scheduled shifts that begin on a specific day.
To perform that function, issue the SQL Insert command, and follow these
guidelines:
1. Specify SCHEDULEIMPORT as the destination table for the data.

Schedule Import
appear in the table. The SCHEDULEIMPORT table requires you to specify
values for deleting scheduled shifts, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
SQL Server database
The following example uses request code 10 to delete all the schedule’s contents
(shifts or off day) for an employee on a given date:
Insert into SCHEDULEIMPORT (REQ_CODE, EMPID, SDATE)
Values ('10', '4321', '9/7/00')
Insert statement:

REQ_CODE 10 Deletes the scheduled shift(s) or off day that
begins on the given date.
SDATE 9/7/00 Identifies the date for which the scheduled
events should be deleted.

Oracle databases require that the SCHEDIMPID column and its value be listed as
NGP_SCHEDULEIMPORT.NEXTVAL.
If the Insert statement runs successfully, verify that the record that deletes the
scheduled shifts from the database is included in the SCHEDULEIMPORT table.
Select * from SCHEDULEIMPORT where EMPID = '4321'
Note: When you delete schedules using the SCHEDULEIMPORT table, you
delete all schedules that belong to the specified employee and that start on the
specified date.
Adding a scheduled shift
SCHEDULEIMPORT differs from the other import tables. In the other import
tables, only one SQL Insert statement is required to add an entry. In the
SCHEDULEIMPORT table, several statements are required to add a single shift.
You must add each distinct element of the shift separately, in separate INSERT
instructions. A final Insert statement denotes the end of the shift definition.
When you import a shift, the shift starts automatically in the employee’s default
labor account and work rule. If you want the shift to begin in a different labor
account or work rule, follow the instructions provided in “Example: How to add a
scheduled shift with a transfer” on page 241. Enter the labor account or work rule
as you would for a transfer, but schedule this “transfer” to occur at the same time
that the shift begins.
Example: How to add a scheduled shift
The example in this section demonstrates how to add a scheduled shift using the
SCHEDULEIMPORT table. To perform that function, you must enter two SQL
Insert commands.

Schedule Import
First Insert command

SCHEDULEIMPORT table requires you to specify values for adding shifts, as
follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION
Second Insert command

SCHEDULEIMPORT table requires you to specify values for completing
scheduled shifts, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID

SQL Server database
You can add a scheduled shift for an employee. The following example uses two
INSERT instructions:
• The first SQL statement uses request code 11 to add a scheduled shift for an
employee.
• The second SQL statement uses request code 14 to indicate the end of the
shift import for an employee.
Insert into SCHEDULEIMPORT (REQ_CODE, EMPID, SDATE,
STIME, DURATION)
Values ('11', '4321', '9/7/00', '7:00 AM', '8:30')
Insert into SCHEDULEIMPORT (REQ_CODE, EMPID)
Values ('14', '4321')
The following tables show the significance of each value that is used in this SQL
Insert statement:

REQ_CODE 11 Adds a shift.
SDATE 9/7/00 Identifies the starting date of the scheduled shift.
STIME 7:00 AM Identifies the starting time of the scheduled shift.
DURATION 8:30 Contains the length of the shift.

REQ_CODE 14 Indicates that there are no additional elements of the shift
to be imported.

Schedule Import
If the INSERT instructions run successfully, verify that the records that add the
scheduled shift to the database and that signify the end of the shift import are
included in the SCHEDULEIMPORT table. To do this, issue a Select statement
Example: How to add a scheduled shiftt with a break

table to import a scheduled shift containing a break. To perform that function, you
must enter three SQL Insert commands.
SCHEDULEIMPORT table requires you to specify values for adding
– SCHEDIMPID
– REQ_CODE
– EMPID

– SDATE
– STIME
– DURATION
SCHEDULEIMPORT table requires you to specify values for adding a break,
as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION
Third Insert command
SCHEDULEIMPORT table requires you to specify values for completing
– SCHEDIMPID
– REQ_CODE
– EMPID

Schedule Import
SQL Server database
You can add a scheduled shift with a break. The following example uses three
• The first SQL statement uses request code 11 to add a scheduled shift for an
employee.
• The second SQL statement uses request code 12 to add a break for the
employee.
• The third SQL statement uses request code 14 to indicate the end of the shift
import.
STIME, DURATION)
Values ('11', '4321', '9/8/00', '7:00 AM', '8:30')
STIME, DURATION)
Values ('12', '4321', '9/8/00', '12:00 PM', '0:30')
Values ('14', '4321')
Insert statement:

SDATE 9/8/00 Identifies the starting date of the scheduled shift.
STIME 7:00 AM Identifies the starting time of the scheduled shift.


REQ_CODE 12 Adds a break.
SDATE 9/8/00 Identifies the starting date of the break.
STIME 12:00 PM Identifies the starting time of the break.
DURATION 0:30 Contains the length of the break.
REQ_CODE 14 Indicates that there are no additional elements of the
shift to be imported.

If the INSERT instructions run successfully, verify that the records that add the
scheduled shift and break information to the database and that signify the end of
shift import are included in the SCHEDULEIMPORT table. To do this, issue a
Select statement similar to the following:

Schedule Import
Example: How to add a scheduled shift with a transfer

table to import a scheduled shift containing a labor account or work rule transfer
that begins after the start of the shift. To perform that function, you must enter
three SQL Insert commands.
appear in the table. You must specify the following values when adding
scheduled shifts:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION
SCHEDULEIMPORT table requires you to specify values for adding a labor
account or a work rule transfer, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME

– You must supply a value for either the LABORACCT column, the
WORKRULE column, or both.
SCHEDULEIMPORT table requires you to specify values for completing a
scheduled shift, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
SQL Server database
Importing a Shift Containing a Labor Account Transfer

You can import a scheduled shift containing a labor account transfer. The
following example uses three INSERT instructions:
• The first SQL statement in the following example uses request code 11 to
import a scheduled shift for an employee.
• The second SQL statement uses request code 13 to import a labor account
transfer. This transfer lasts until the end of the shift since no other transfers
were imported.
• The third SQL statement uses request code 14 to indicate the end of the
imported shift for the employee.

Schedule Import

STIME, DURATION)
Values ('11', '4321', '9/5/00', '7:00 AM', '8:30')
STIME, LABORACCT)
Values ('13', '4321', '9/5/00', '8:00 AM', '102//304///
/')
Values ('14', '4321')
The following tables show the significance of the values used in each SQL Insert
statement:

SDATE 9/5/00 Identifies the starting date of the shift.
STIME 7:00 AM Identifies the starting time of the shift.

REQ_CODE 13 Adds a labor account transfer.
LABORACCT 102//304//// Defines the labor account.

REQ_CODE 14 Indicates the end of the import command.

Importing a Shift Containing a Work Rule Transfer

You can import a scheduled shift containing a work rule transfer. The following
example uses three INSERT instructions:
• The first SQL statement uses request code 11 to import a scheduled shift for
an employee.
• The second statement uses request code 13 to import a transfer into a work
rule.
• The third statement uses request code 14 to end the import instructions.
STIME, DURATION)
Values ('11', '4321', '9/7/00', '7:00 AM', '8:30')
STIME, WORKRULE)
Values ('13', '4321', '9/7/00', '8:00 AM', 'On-Call')
Values ('14', '4321')
Insert statement:


REQ_CODE 13 Adds a work rule transfer.

Schedule Import

WORKRULE On-Call Defines the work rule.

REQ_CODE 14 Indicates that there are no additional elements of
the shift to be imported.
Importing a Shift with a Labor Account and Work Rule Transfer

You can import a scheduled shift containing a labor account transfer combined
with a work rule transfer.
Note: In this example, you do not have to use a separate Insert statement for the
start of the shift, and add individual INSERT instructions for the labor account
transfer and the work rule transfer. The activity is taking place from the start of the
shift.

STIME, DURATION, LABORACCT, WORKRULE)
Values ('11', '4321', '9/7/00', '7:00 AM', '8:30',
'103/201/301////', 'On-Call')
Values ('14', '4321')
Insert statement:



DURATION 8:30 Provides the length of the shift.
LABORACCT 103/201/301//// Identifies the labor account being billed.
WORKRULE On-Call Contains the work rule.

REQ_CODE 14 Indicates that there are no additional elements of the shift
to be imported.
If the Insert statement runs successfully, verify that the records that add the
scheduled shift and transfer information to the database, and that signify the end
of the shift import are in the SCHEDULEIMPORT table. To do this, issue a Select
statement similar to the following command:

Schedule Import
Example: How to add a scheduled shift with several transfers and abreak
table to import a scheduled shift containing three transfers and a break. To
perform that function, you must enter six SQL Insert commands. In this example,
the employee makes two transfers in the morning, takes a half-hour lunch break at
noon, and makes another transfer in the afternoon.
values for adding scheduled shifts, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION

values for adding a labor account, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– LABORACCT


values for adding a work rule, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– WORKRULE
Fourth Insert command

values for adding a break, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION

Schedule Import
Fifth Insert command

values for adding both a labor account and a work rule transfer, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– LABORACCT
– WORKRULE
Sixth Insert command

values for completing scheduled shifts, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID

SQL Server database
You can import a scheduled shift containing several transfers and a break. The
following example uses six INSERT instructions:
an employee.
• The second statement uses request code 13 to import a transfer to a labor
account.
• The third SQL statement uses request code 13 to import a transfer to a work
rule.
• The fourth SQL statement uses request code 12 to import a break.
• The fifth SQL statement uses request code 13 to import both a labor account
transfer and a work rule transfer.
• The sixth SQL statement uses request code 14 to indicate the end of the
schedule import for the employee.

STIME, DURATION)
Values ('11', '4321', '8/29/00', '7:00 AM', '8:30')
STIME, LABORACCT)
Values ('13', '4321', '8/29/00', '8:00 AM', '102//304//
//')
STIME, WORKRULE)
Values ('13', '4321', '8/29/00', '9:00 AM', 'On-Call')
STIME, DURATION)
Values ('12', '4321', '8/29/00', '12:00 PM', '0:30')

Schedule Import

STIME, LABORACCT, WORKRULE)
Values ('13', '4321', '8/29/00', '2:00 PM', '102/202/
303/404/504/603/702', 'Callback')
Values ('14', '4321')
Insert statement:


REQ_CODE 13 Adds a labor account transfer.
SDATE 8/29/00 Identifies the date of the transfer.
STIME 8:00 AM Identifies the time of the transfer.
LABORACCT 102//304/ Defines the new labor account.
///

REQ_CODE 13 Adds a work rule transfer.
STIME 9:00 AM Identifies the time of the transfer.
WORKRULE On-Call Defines the new work rule.


STIME 12:00 PM Identifies the time of the transfer.
DURATION 0:30 Defines the length of the break.

REQ_CODE 13 Adds a labor account transfer and a work rule transfer.
STIME 2:00 PM Identifies the time of the transfer.
LABORACCT 102/202/ Defines the new labor account.
303/404/
504/603/
702
WORKRULE Callback Defines the new work rule.


Schedule Import
scheduled shift, transfer, and break information to the database and that signify the
end of the shift import are included in the SCHEDULEIMPORT table. To do this,
issue a Select statement similar to the following command:
Select * from SCHEULEIMPORT where EMPID = '4321'
Example: How to add a scheduled shift that crosses the day divide
You can use the SCHEDULEIMPORT table to import a scheduled shift that
crosses the day divide. When you import a break or a transfer, however, the date
you specify is the date on which the break or transfer begins, not the date on
which the shift begins.
To add this function, you must enter three SQL Insert commands.
– Identify all the columns that will be receiving data, in the order in which
they appear in the table. The SCHEDULEIMPORT table requires you to
specify values for adding scheduled shifts, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION


values for adding a break, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION

– SCHEDIMPID
– REQ_CODE
– EMPID

Schedule Import
SQL Server database
You can add a break within a shift that begins on one date and ends on the next.
The following example uses three INSERT instructions:
an employee.
• The second SQL statement uses request code 12 to import a scheduled break.
• The third SQL statement uses request code 14 to indicate the end of shift
import for the employee.
STIME, DURATION)
Values ('11', '4321', '9/11/00', '10:00 PM', '8:30')
STIME, DURATION)
Values ('12', '4321', '9/12/00', '12:30 AM', '1:00')
Values ('14', '4321')
Insert statement:

STIME 10:00 PM Identifies the starting time of the shift.
DURATION 8:30 Defines the length of the shift.



SDATE 9/12/00 Identifies the date of the break.
STIME 12:30 AM Identifies the time of the break.
DURATION 1:00 Defines the length of the break.

REQ_CODE 14 Indicates that there are no additional
elements of the shift to be imported.
scheduled shift and break information to the database and that signify the end of
the shift import are included in the SCHEDULEIMPORT table. To do this, issue a

Schedule Import
Example: How to add two scheduled shifts for the same day
Assume that you want to use the SCHEDULEIMPORT table to import two
scheduled shifts for the same employee and for the same day. To perform that
function, you must enter four SQL Insert commands.
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION

– SCHEDIMPID
– REQ_CODE
– EMPID


– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION
Fourth Insert command

– SCHEDIMPID
– REQ_CODE
– EMPID
SQL Server database

You can add two separate scheduled shifts for employee 4321. Each scheduled
shift requires a statement with request code 11 to import the shift and another with
request code 14 to indicate the end of the import. The following example uses four
• The first SQL statement uses request code 11 to define the first shift.

Schedule Import
shift import for the employee.
• The third SQL statement uses request code 11 to define the second shift.
• The fourth SQL statement uses request code 14 to indicate the end of the shift
import for the employee.
STIME, DURATION)
Values ('11', '4321', '9/13/00', '6:00 AM', '5:00')
Values ('14', '4321')
STIME, DURATION)
Values ('11', '4321', '9/13/00', '5:00 PM', '5:00')
Values ('14', '4321')
Insert statement:




STIME 5:00 PM Identifies the starting time of the shift.

If the Insert statement runs successfully, verify that the records that add the new
shifts to the database and that signify the end of the shift imports are included in
the SCHEDULEIMPORT table. To do this, issue a Select statement similar to the
following command:

Schedule Import
Example: How to add full and partial days off

table to add an off day for an employee. To perform that function, enter the SQL
values for adding an off day, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME (partial off day only)
– DURATION (partial off day only)
– USERFIELD
SQL Server database
The following example uses request code 15 to schedule a full day off for an
employee:
Insert into SCHEDULEIMPORT (REQ_CODE, EMPID, SDATE)
Values ('15', '4321', '9/14/00')
Insert statement:

REQ_CODE 15 Adds a day off.


SDATE 9/14/00 Identifies the date of the day off.
The following example uses request code 15 to schedule a partial off day for an
employee:
STIME, DURATION, USERFIELD)
Values ('15', '4321', '9/14/00', '4:00 PM', '04:00',
'PARTIAL OFF DAY')
Insert statement:

REQ_CODE 15 Adds a day off.
SDATE 9/14/00 Identifies the date of the day off.
STIME 4:00 PM Identifies the start time of the off period.
DURATION 04:00 Identifies the length of the off period (4 hours)
USERFIELD Partial off day Identifies the nature of the information being imported.

Schedule Import
If the Insert statement runs successfully, verify that the record that adds the off day
to the database is included in the SCHEDULEIMPORT table. To do this, issue a
Example: How to add an off shift

table to add an off shift for an employee. An off shift is a shift for an off day on
which a person is available to work, if necessary. To perform that function, enter
the SQL Insert command and follow these guidelines:
values for adding an off shift, as follows:
– SCHEDIMPID
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION
– Supply a value for one or both of the following columns: LABORACCT,
WORKRULE

Sample SQL statement
SQL Server database
The following example uses request code 41 to schedule an off shift for an
employee:
STIME, DURATION, LABORACCT, WORKRULE)
Values ('41', '4321', '1/14/02', '7:00 AM', '8:30',
'102//304////', 'Callback')
Insert statement:

REQ_CODE 41 Adds an off shift.
SDATE 1/14/02 Identifies the date of the off shift.
STIME 7:00 AM Specifies the start of the off shift.
DURATION 8:30 Defines the length of the off shift.
LABORACCT 102//304//// Defines the transfer labor account.
WORKRULE Callback Defines the transfer work rule.

Schedule Import
If the Insert statement runs successfully, verify that the record that adds the off day
to the database is included in the SCHEDULEIMPORT table. To do this, issue a

SQL Server database
The following example uses Request code 1 to add an employee:

PERSONTYPE, PERSONNUM, LASTNAME, PAYRULE, USERFIELD
Values (1, '1', '1', '8001', 'Jones', 'Support',
'Minimal Employee')
Values (1, '3', '978654321','02/08/2002',
'08:00:00','10/31/2002'
Note: The PERSONIMPORTID column value in the second insert statement must
match the PERSONIMPORTID column value provided in the first insert
statement to insert a row in the database.
The SQL INSERT instructions for Oracle and DB2 databases are similar to the
previous SQL Server database example. The only differences are the semicolons
that are used at the end of each statement and the trailing commit statement.
PERSONTYPE, PERSONNUM, LASTNAME, PAYTRULE, USERFIELD)
Insert into PERSONDATEMPORT
(PERSONIMPORTID,RECORDTYPE,STARTDATE,ENDATE,
HOMELABORACCOUNT)
Values (1, '3', '3/29/2002'/'', '101/201/301/401/501/
601/701');
Commit;

Schedule Import
Example: How to add a shift with a comment

table to add a comment to a shift. To perform that function, enter the SQL Insert
command and follow these guidelines:
– Identify all the columns that will be receiving data, in the order in which
they appear in the table. The SCHEDULEIMPORT table requires you to
specify values for adding a shift, as follows:
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION
– LABORACCT
– COMMENTEXT
– USERFIELD
SQL Server database
The following example uses request code 21 to add a comment to a shift. This
action requires two insert statements.


STIME, DURATION, LABORACCT, COMMENTEXT, USERFIELD)
Values ('21', '8', '04/22/2004', '8:00 AM', '8:00', '///
401/503//703', 'union meeting', ‘full day’)
Values (‘14,’ ‘8’)
The following tables show the significance of each value that is used in the SQL
Insert statement for REQ_CODE 21:

REQ_CODE 21 Adds an off shift.
SDATE 04/22/2004 Identifies the date of the off shift.
STIME 8:00 AM Specifies the start of the off shift.
DURATION 8:00 Defines the length of the off shift.
LABORACCT ///401/503//703 Defines the transfer labor account.
COMMENTEXT forgot to punch Contains the comment information
USERFIELD full day Contains addtional information about the
shift or comment
The following tables show the significance of each value that is used in the SQL
Insert statement for REQ_CODE 14:

REQ_CODE 14 Indicates that there are no additional
elements of the shift to be imported.

Schedule Import
Example: How to update the the information about a commented shift

table to update a comment. To perform that function, enter the SQL Insert
commands and follow these guidelines:
values for adding a shift, as follows:
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION
– LABORACCT
– COMMENTEXT
– USERFIELD
– WORKRULE
SQL Server database
The first example uses request codes11, 12, 13, and 14 to import a shift with a
comment. This action requires four insert statements.

• The second statment used request code 12 to update the shift information.
• The third statement uses request code 13 to update the labor accoutn and
workrule for the shift.
Values ('11', '8', '04/22/2004', '8:00 AM', '8:00', '
///401/503//703', 'union meeting', ‘full day’)
STIME, DURATION)
Values (‘12,’ ‘8’, '04/22/2004','1:30 PM', '0:30', )
Values (‘13,’ ‘8’, '04/22/2004','2:30 AM',102/204/307//
501//701’, Administration’ )
Values (‘14’, ‘8’)
Example: How to update the comment on a shift

table to update a comment. To perform that function, enter the SQL Insert
commands and follow these guidelines:

Schedule Import
values for adding a shift, as follows:
– REQ_CODE
– EMPID
– SDATE
– STIME
– DURATION
– LABORACCT
– COMMENTEXT
– USERFIELD
– WORKRULE
SQL Server database
The following example uses request codes 12, 13, 14, and 21 to update the
comment. All other existing infomration about the shift must also be updated.
This action requires four insert statements.
Information about the shift exists and needs to be re-imported
• The second statment used request code 12 to update the shift information.
• The third statement uses request code 13 to update the labor accoutn and
workrule for the shift.


Values ('21', '8', '04/22/2004', '8:00 AM', '8:00', '
///401/503//703', 'union meeting', ‘full day’)
STIME, DURATION)
Values (‘12,’ ‘8’, '04/22/2004','1:30 PM', '0:30', )
Values (‘13,’ ‘8’, '04/22/2004','2:30 AM',102/204/307//
501//701’, Administration’ )
Values (‘14’, ‘8’)
The following tables show the significance of each value that are used in the SQL
Insert statements:

Appendix A
Required Columns for Request Codes
The Import function reads entries from the import tables and performs operations
on those entries as determined by the value in the request code (REQ_CODE)
column of the import entry.
This appendix contains the following information about request code:
• A numerical list and brief description
• The tables in which the request code is valid
• Other required columns from each table that are required for a successful
import using the request code
REQ_COD
E Description Applies to these Tables Required Columns
1 Add a new ACCRUALDATEIMPORT ACCRUALDATEIMPID (Oracle only)
record. EMPLOYEEID
DATENAME
ACCRUALDATE
Add a labor LABLEVENTIMPORT NAME
level entry. LLDEF
Add a new PERSONDATEIMPORT Required columns vary depending on the
person. PERSONMANY type of person you are adding. See
“People Import” on page 100.
Add a new PERSONIMPORT PERSONNUM
person HIREDATE
PAYRULE
Appendix A Required Columns for Request Codes
REQ_COD
Add a scheduled SCHEDPCEIMPORT SCHEDPECEIMPID (Oracle only)
pay code edit. EMPID
SDATE
STIME
AMOUNT
PAYCAT
2 Update a record. ACCRUALDATEIMPORT ACCRUALDATEIMPID (Oracle only)
EMPLOYEEID
DATENAME
ACCRUALDATE
Update a labor LABLEVENTIMPORT LLEVNTIMPID (Oracle only)
level entry. NAME
LLDEF
NEWNAME
Update a person. PERSONDATEIMPORT Required columns vary depending on the
Use if your data PERSONMANY type of person you are updating. See
source only “People Import” on page 100.
allows you to
export all
information
about a person
when importing.
Update a person. PERSONIMPORT PERSONNUM
Use if your data NEWPERSONNUM (for new person
source allows entry)
you to export
HIREDATE
only changes to
a person. PAYRULE

REQ_COD
3 Add a record if ACCRUALDATEIMPORT ACCRUALDATEIMPID (Oracle only)
one does not EMPLOYEEID
exist; update a
DATENAME
record if one
exists. ACCRUALDATE
Add or update a LABLEVENTIMPORT LLEVNTIMPID (Oracle only)
labor level entry. NAME
LLDEF
NEWNAME
Add or update a PERSONDATEIMPORT Required columns vary depending on the
person. PERSONMANY type of person you are adding or
updating. See “People Import” on page
100.
Add or update a PERSONIMPORT PERSONNUM
person. Use if NEWPERSONNUM (for new person
your data source entry)
only allows you
HIREDATE
to export all
information PAYRULE
about a person
when importing.
4 Inactivate LABLEVENTIMPORT LLEVNTIMPID (Oracle only)
NAME
LLDEF
Delete PERSONIMPORT PERSONIMPORTID
PERSONNUM
PERSONTYPE
5 Reactivate. LABLEVENTIMPORT LLEVNTIMPID (Oracle only)
NAME
LLDEF

REQ_COD
6 Add either a PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle)
punch or an EMPID
amount
EDITDATE
associated with
a pay code using PAYCAT
the employee’s AMOUNT
ID number.
Add a punch PUNCHIMPORT PNCHIMPID (Oracle)
using the EMPID
employee’s ID
PDATE
number.
PTIME
7 Add either a PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
punch or an EMPID
amount
EDITDATE
associated with
badge number.
Add a punch PUNCHIMPORT PNCHIMPID (Oracle only)
using the EMPID
employee’s
PDATE
badge number.
PTIME
8 Delete either a PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
punch or an EMPID
amount
EDITDATE
associated with
ID number.

REQ_COD
Delete a punch PUNCHIMPORT PNCHIMPID (Oracle only)
using the EMPID
employee’s ID
PDATE
number.
PTIME
9 Delete either a PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
punch or an EMPID
amount
EDITDATE
associated with
badge number.
Delete a punch PUNCHIMPORT PNCHIMPID (Oracle only)
using the EMPID
employee’s
PDATE
badge number.
PTIME
10 Delete SCHEDULEIMPORT SCHEDIMPID (Oracle only)
scheduled shifts EMPID
or scheduled off
SDATE
days that begin
on the specified
date.
Delete
scheduled pay
code edits that
begin on the
specified date.
11 Add a new shift, SCHEDULEIMPORT SCHEDIMPID (Oracle only)
or replace an EMPID
existing shift or
SDATE
off day.
STIME
DURATION

REQ_COD
12 Add a break. PAYCATEDITIMPORT
Insert a break in SCHEDULEIMPORT SCHEDIMPID (Oracle only)
a shift. EMPID
SDATE
STIME
DURATION
13 Add a labor SCHEDULEIMPORT SCHEDIMPID (Oracle only)
account transfer, EMPID
a work rule
SDATE
transfer, or both.
STIME
LABORACCT
WORKRULE
14 Indicate that SCHEDULEIMPORT SCHEDIMPID (Oracle only)
there are no EMPID
additional
elements of the
shift to be
imported.
15 Add an off day. SCHEDULEIMPORT SCHEDIMPID (Oracle only)
EMPID
SDATE
16 Reset an ACCRUALIMPORT ACCRUALIMPORTID (Oracle only)
employee’s EMPLOYEEID
accrual balance.
ACCRUALCODE
17 Enter an earned ACCRUALIMPORT ACCRUALIMPORTID (Oracle only)

or taken accrual EMPLOYEEID
amount.
ACCRUALCODE

REQ_COD
17 Add a comment SCHEDULEIMPORT COMMENTTXT
for an off day. SCHEDIMPID (Oracle only)
EMPID
SDATE
STIME
DURATION
LABORACCT (on add or update)
USERFIELD
ORGPATHTXT (on add or update)
WORKRULE (on add or update)
18 Clear a work PUNCHIMPORT PNCHIMPID (Oracle only)
rule using the EMPID
employee’s ID
PDATE
number.
PTIME
19 Clear a work PUNCHIMPORT PNCHIMPID (Oracle only)
rule using the EMPID
employee’s
PDATE
badge number.
PTIME
20 This request
code is reserved.

REQ_COD
for a shift SCHEDIMPID (Oracle only)
EMPID
SDATE
STIME
DURATION
USERFIELD
22 Obsolete N/A N/A
23 Obsolete N/A N/A
25 Obsolete N/A N/A
26 Obsolete N/A N/A
27 Add a comment PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
by employee ID. EMPID
EDITDATE
PAYCAT
AMOUNT
COMMENTTEXT
Add a comment PUNCHIMPORT PNCHIMPID (Oracle only)
using the EMPID
employee’s ID
PDATE
number
PTIME
COMMENTTEXT

REQ_COD
Add a comment SCHEDPCEIMPORT SCHEDULEPCEIMPID (Oracle only)
using the EMPID
employee’s ID
SDATE
number.
STIME
AMOUNT
PAYCAT
COMMENTTEXT
using the EMPID
employee’s
EDITDATE
badge number.
PAYCAT
AMOUNT
COMMENTTEXT
Add a comment PUNCHIMPORT PNCHIMPID (Oracle)
using the EMPID
employee’s
PDATE
badge number.
PTIME
COMMENTTEXT
29 Add a historical PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
amount using EMPID
the employee’s
EDITDATE
ID number.
PAYCAT
AMOUNT
ADJ_APPLYDATE

REQ_COD
amount using EMPID
the employee’s
EDITDATE
badge number.
PAYCAT
AMOUNT
ADJ_APPLYDATE
31 Delete a PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
historical EMPID
amount using
EDITDATE
the employee’s
ID number. PAYCAT
AMOUNT
ADJ_APPLYDATE
32 Delete a PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
historical EMPID
amount using
EDITDATE
the employee’s
badge number. PAYCAT
AMOUNT
ADJ_APPLYDATE
comment using EMPID
the employee’s
EDITDATE
ID number.
PAYCAT
AMOUNT
ADJ_APPLYDATE
COMMENTTEXT

REQ_COD
comment using EMPID
the employee’s
EDITDATE
badge number.
PAYCAT
AMOUNT
ADJ_APPLYDATE
COMMENTTEXT
35 Add a totaled PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
amount using EMPID
the employee’s
EDITDATE
ID number.
AMOUNT
36 Add a totaled PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
amount using EMPID
the employee’s
EDITDATE
badge number.
AMOUNT
37 Delete a totaled PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
amount using EMPID
the employee’s
EDITDATE
ID number.
AMOUNT
38 Delete a totaled PAYCATEDITIMPORT PAYCATEDITIMPID (Oracle only)
amount using EMPID
the employee’s
EDITDATE
badge number.
AMOUNT
to a totaled EMPID
amount using
EDITDATE
the employee’s
ID number. AMOUNT
COMMENTTEXT

REQ_COD
to a totaled EMPID
amount using
EDITDATE
the employee’s
badge number. AMOUNT
COMMENTTEXT
41 Add an off shift SCHEDULEIMPORT SCHEDIMPID (Oracle only)
EMPID
SDATE
STIME
DURATION
LABORACCT and/or WORKRULE
for an off shift SCHEDIMPID (Oracle only)
EMPID
SDATE
STIME
DURATION
USERFIELD

Appendix A
New Columns in
Workforce Central 5.1
This appendix contains a list of the new columns that were added to the import
tables for Workforce Central 5.1 features.
Appendix A New Columns in Workforce Central 5.1
New Columns
PERSONIMPORT table:
• WORKERTYPE
• SCHEDGROUPPROFILE
• SHIFTTMPLPROFILE
• PATTERNTMPLPROFILE
• SENIORITYDATE
PERSONDATEIMPORT table:
• ORGPATHTXT
PUNCHIMPORT table:
• ORGPATHTXT
SCHEDULEIMPORT table:
• ORGPATHTXT
• COMMENTTEXT
SCHEDPCEIMPORT table:
• ORGPATHTXT
PAYCATEDITIMPORT table:
• ORGPATHTXT

Index
Symbols labor level set with wild card 71

off shift 263 to ??
)syntax, SQL for different database types 33
punches 199 to 200
@ (at sign) 61, 75
scheduled amounts 91 to 92
scheduled pay code edit 213 to 214
A scheduled shift 234 to 237
accrual dates scheduled shift with break 237 to 240
adding 42 to 43 scheduled shift with transfer 241 to 246
accrual dates import scheduled shift with transfers and break 247
column definitions 40 to 41 to 253
purpose 40 shift to cross day divide 253 to 256
accruals import totaled amount 89 to 91
column definitions 45 to 47 two shifts to same day 257 to 260
examples 48 to 52 Workforce Timekeeper Employee 180 to 187
purpose 44 amount associated with a pay code edit,
required columns 47 adding 88 to ??
ad hoc labor levels 28 amounts, format 25
adding (examples)
accrual dates 42 to 43 C
amount associated with a pay code edit 88 to
changing (examples)
??
description of labor level set 72
comment to a pay code edit 93 to 95
Workforce Timekeeper Employee 187 to 192
comment to a punch 204 to 206
clearing a work rule 202 to 203
comment to a scheduled pay code edit 214 to
column definitions
??
accrual dates import 40 to 41
days off 260
accruals import 45 to 47
earned accrual amount 50 to 52
labor level entry import 54 to 56
entries to a labor level set 73
labor level set labor level entries import 65 to
historical adjustment 95 to 97
66
labor level entry 57 to 59
labor level sets import 63 to 65
labor level set 68 to 70
pay code edits import 78 to 84
Index
person date import 121 to 125 pay code edit 97 to 99

person import 104 to 119 punches 200 to 202
person many import 127 to 130 scheduled pay code edit 217 to 219
punch import 193, 194 to 197 scheduled shift 232 to 234
schedule import 221 to 228 durations, format 25
schedule import table 67
scheduled pay code edits 208 to 210, ?? to E
228 earned accrual amount, adding 50 to 52
column values entries in a labor level set, adding 73
amounts and durations 25 entries in a labor level set, deleting 74
currency 25 errors
data type and format 24 format 25
date 26 populating tables for People imports 131
ignored 21 reserved symbols 31
labor accounts 27 updating a person 180
optional 21 value restrictions 31
required 21 examples
restrictions 31 adding
specifying valid values 23 accrual date 42 to 43
time zone 27 comment to a pay code edit 93 to 95
comment associated with a punch comments to a punch 204 to 206
adding 204 to 206 comments to a scheduled pay code
comment associated with scheduled pay code edit edit 214 to ??
adding 214 to ?? days off 260
currency formats 25 earned accrual amount 50 to 52
entries to a labor level set 73
D historical adjustment 95 to 97
data formats 24 labor level entry 57 to 59
case-sensitivity 28 labor level set 68 to 70
currency 25 labor level set with wildcard 71
pay codes 28 off shift 263 to ??
profiles 28 punches 199 to 200
data type, defined 37 scheduled amount 91 to 92
database scheduled pay code edit 213 to 214
importing data to 16 scheduled shift with break 237 to 240
date formats 26 scheduled shift with transfer 241 to 246
day divide in scheduled shift 253 scheduled shift with transfers and
days off, adding 260 break 247 to 253
deleting (examples) scheduled shifts 234 to 237
entries from a labor level set 74 shift to cross day divide 253 to 256

Index
shift with a labor account and a work rule adding a person type 131
transfer 245 ID columns 32
shift with a labor account transfer 242 procedure 16
shift with a work rule transfer 244 tables
totaled amount 89 to 91 ACCRUALDATEIMPORT 40 to 42
two shifts to same day 257 to 260 ACCRUALIMPORT 44 to 47
Workforce Timekeeper Employee 180 to ID columns 32
187 LABLEVENTIMPORT 53 to 57
changing LLSETIMPORT 62 to 65
description of a labor level set 72 LLSETLLEIMPORT 65 to 66
labor level entry 59 to 61 PAYCATEDITIMPORT 76 to 87
Workforce Timekeeper Employee 187 to PERSONDATEIMPORT 120 to 125
192 PERSONIMPORT 100 to 119
clearing work rules 202 to 203 PERSONMANYIMPORT 126 to 130
deleting processing order 19
entries from a labor level set 74 PUNCHIMPORT 193 to 198
pay code edit 97 to 99 SCHEDPCEIMPORT 207 to 212
punches 200 to 202 SCHEDULEIMPORT 220 to 232
scheduled pay code edits 217 to 219 uses 15
scheduled shifts 232 to 234 import ID columns
renaming labor level sets 72 Oracle database 35
resetting employee’s accrual balance 48 to 49 import ID values, not generated
automatically 34
F import record, defined 37
format
amounts 25 L
dates 26 labor accounts, format 27
durations 25 labor level entry import
labor accounts. 27 column definitions 54 to 56
examples 57 to 61
G purpose 53
guidelines for record processing 19 required columns 56
labor level entry, adding 57 to 59
H labor level set
adding 68 to 70
historical adjustment, adding 95 to 97 renaming 72
labor level set labor level entries import
I column definitions 65 to 66
ID columns (import) 32 labor level set with wild card
import adding 71

Index
labor level sets import purpose 100

column definitions 63 to 65 Workforce Manager 140, 142
examples 68 to 75 Workforce Timekeeper Employee 135
member tables 62 person date import
purpose 62 column definitions 121 to 125
data types 120
M purpose 100
matching existing values person import
when updating a person 180 column definitions 104 to 119
modifying data types 101
labor level entry (example) 59 to 61 purpose 100
multiple person types types of persons 130
columns required to add 142, 145, 147, 149, person many import
152, 154, 157, 159, 162, 164, 167, 169 column definitions 127 to 130
multi-server environments 25 data types 126
purpose 100
N values populated for adding a Workforce
Timekeeper Employee 130
not null constraint, defined 37 punch import
null constraint, defined 38 column definitions 193, 194 to 197
null values purpose 193
as default value 75 required columns 198
retaining current value 75 punches
adding 199 to 200
O deleting 200 to 202
off shift, adding 263 to ??
order of processed data 19 R
record format for database server 39
P record processing guidelines 19
pay code edit, deleting 97 to 99 renaming labor level sets with wild card 72
pay code edits import request codes 21
column definitions 78 to 84 required columns
examples 88 to 99 accrual dates import 42
purpose 76 accruals import 47
required columns 85, ?? to 87 labor level entry import 56
people import pay code edits import 85, ?? to 87
examples 180 to 192 people import, multiple person types 142,
member tables 100 145, 147, 149, 152, 154, 157, 159, 162,
multiple person types 142, 145, 147, 149, 164, 167, 169
152, 154, 157, 159, 162, 164, 167, 169 people import, Workforce Manager 140, 142

Index
people import, Workforce Timekeeper specifying labor level entries

Employee 135 explicit character 66
punch import table 198 single character wildcard 67
schedule import table 228 to 232 string wildcards 67
scheduled pay code edits 211 to 212 SQL
to add Workforce Timekeeper Employee 135 defined 38
required values 21 how syntax differs for database types 33, ??
resetting an employee’s accrual balance, to 35
example 48 to 49 statements, guidelines 16
Structured Query Language. See SQL
S syntax, SQL for different datatabase types ?? to
schedule import 35
column definitions 221 to 228
examples 232 to ?? T
purpose 220 tables
required columns 228 to 232 ACCRUALDATEIMPORT 40 to 42
scheduled pay code edit ACCRUALIMPORT 44 to 47
adding 213 to 214 ID columns 32
column definitions 208 to 210, ?? to 228 LABLEVENTIMPORT 53 to 57
deleting 217 to 219 LLSETIMPORT 62 to 65
scheduled pay code edits LLSETLLEIMPORT 65 to 66
purpose 207 PAYCATEDITIMPORT 76 to 87
required columns 211 to 212 PERSONDATEIMPORT 120 to 125
scheduled shift PERSONIMPORT 100 to 119
adding 234 to 237 PERSONMANYIMPORT 126 to 130
deleting 232 to 234 processing order 19
scheduled shift with break, adding 237 to 240 PUNCHIMPORT 193 to 198
scheduled shift with transfer, adding 241 to 246 SCHEDPCEIMPORT 207 to 212
scheduled shift with transfers and break, SCHEDULEIMPORT 220 to 232
adding 247 to 253 totaled amount, adding 89 to 91
schema, defined 38 totalizing, optimum timing 36
segment, defined 38 two shifts to same day
shift to cross day divide, adding 253 to 256 adding 257 to 260
shorthand notation
# 29 U
@ 29 updating a person 174
@H 29 userfield column 22
currently stored values 29
labor level data 29, 122 V
null values 29

Index
validation of data 15
value restrictions
data input errors 31
values (column)
amounts and durations 25
currency 25
data type and format 24
date 26
ignored 21
labor accounts 27
optional 21
required 21
restrictions 31
specifying valid values 23
time zone 27
W
wild cards
using for labor level entries 67
work rules, clearing 202 to 203
Workforce Manager
columns required to add 140, 142
Workforce Timekeeper Employee
adding 180 to 187
changing 187 to 192
columns required to add 135

Kronos Import Guide

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Kronos Import Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Workforce Timekeeper ™

Table Format Import

An administrator’s guide to importing data into the

Kronos Workforce Central Suite

Document Part Number: 4703405-001

Published by Kronos Incorporated

For links to information about international subsidiaries of Kronos Incorporated, go to

Document Revision History

Document Revision Product Version Release Date

About This Guide

Chapter 1: Technical Information About Table Import

Chapter 2: Import Table Descriptions and Examples

Person Type 3: Workforce Manager ................................................... 138

Workforce Timekeeper Table Format Import Programmer’s Guide 5

Punch Import ..............................................................................................193

Appendix A: Required Columns for Request Codes

Appendix B: New Columns in Workforce Central 5.1

Organization of this guide

Workforce Timekeeper documents

Workforce Timekeeper Table Format Import Programmer’s Guide 9

• Workforce Central Import User’s Guide provides information about setting up

Workforce Timekeeper Table Format Import Programmer’s Guide 11

This chapter contains information that is of interest to a developer who is using

About Table Import

Importing table-formatted data

Why run data imports

Workforce Timekeeper Table Format Import Programmer’s Guide 15

Importing data with tables

Workforce Timekeeper Table Format Import Programmer’s Guide 17

Import Name Purpose

Additional importable data, such as Workforce Scheduler and Workforce

Workforce Timekeeper Table Format Import Programmer’s Guide 19

Required order of table processing

Standard import table columns

Optional and ignored values

Workforce Timekeeper Table Format Import Programmer’s Guide 21

Specifying column values

Workforce Timekeeper Table Format Import Programmer’s Guide 23

Supported data types

Data Type Oracle Term SQL Server Term DB2 Term

Amounts and durations

Workforce Timekeeper Table Format Import Programmer’s Guide 25

Workforce Timekeeper Table Format Import Programmer’s Guide 27

Ad hoc labor level entries

Additional data formats

Change account: 101/201/301/401/501/601/701

For example, the shorthand @/@/New Entry/@ or @H/@H/New Entry/@H

Workforce Timekeeper Table Format Import Programmer’s Guide 29

• @P (the @ sign followed by uppercase P)—Used for the person’s existing

Change account: 112/222/332/401/501/601/701

Workforce Timekeeper Table Format Import Programmer’s Guide 31

Table Import ID columns

How SQL statement syntax differs between database

Syntax for ending INSERT statements and import records

Oracle and DB2

Workforce Timekeeper Table Format Import Programmer’s Guide 33

Populating Import ID columns

Table Name Import ID Column Value

SQL server or DB2 database

Workforce Timekeeper Table Format Import Programmer’s Guide 35

not null constraint

Workforce Timekeeper Table Format Import Programmer’s Guide 37