ADP G2 Spreadsheet Loader Data Entry: End-User Guide
ADP G2 Spreadsheet Loader Data Entry: End-User Guide
Author: GV Product
Date: 2012-02-25
Document Reference GV00002671
Version 3.3
Confidentiality
The information contained in this document is privileged and confidential, and remains
the intellectual property of Automatic Data Processing, Inc. and/or its affiliates ("ADP
Group"). This document must not be reproduced, stored in a retrieval system, or
transmitted in any form by means electronic, mechanical, optical, photocopying,
recording or otherwise, without the prior consent of the ADP Group. This document must
be kept strictly confidential at all times. It must not be disclosed to any person without
the prior written consent of the ADP Group.
The ADP Logo and GlobalView® are registered trademarks of ADP, Inc.
Code-Signing Certificate
ADP’s GlobalView solution is built on SAP’s Human Capital Management (HCM) platform. In
SAP, data is stored in ‘Infotypes’ - or groups of related fields. For example, the ‘Personal Data’
Infotype may contain fields such as ‘Title’, ‘First Name’, ‘Last Name’, ‘Date of Birth’, etc. While
each Infotype contains default fields, some of which are mandatory, other fields can be added
or removed to meet the specific requirements of different clients and those of the GlobalView
system.
Determination of which Infotypes and related fields are required for each client implementation
is made during the blueprinting phase of the project.
Batch Data Load – Client HR and payroll systems are programmed to send data through the
G2 Gateway automatically via Batch Data Load. This form of data transfer is known as ‘machine
to machine’ and generally accounts for the majority of data transferred from client to
GlobalView.
Spreadsheet Load - Any data that is required for GlobalView that is not saved in the client’s
legacy system or cannot be transferred by batch data load for any reason is to be provided
manually using the Spreadsheet Loader (SSL) program. This form of data transfer is known as
‘human to machine’.
In most cases, customers will need to use a combination of these methods in order to provide
all the data that is required for GlobalView®.
Use the SSL Generator program to generate a Workbook specific to this configuration
containing only the data that has to be provided manually. This Workbook is client-
specific with each country configuration requiring a separate file.
Customise the country-level Field Help in the generated Workbook to ensure that
specific organisational requirements are met and then use this file as a ‘template’ by
copying it for data entry (this step is not mandatory but is highly recommended as it will
make this already useful help tool even more powerful).
Enter some personal information, such as the data entry person’s details and processing
date (this information is used to facilitate problem resolution should errors occur).
Create the Upload File for import into the GlobalView system (this step involves a
second validation process).
During the implementation phase, the upload file is sent to the designated ADP Data
Loader for loading and testing.
For Processing Services (PS) clients, the client’s designated users upload the file directly
to the GlobalView system.
For Managed Services (MS) clients, the upload file is sent to the designated ADP Payroll
Administrator for loading into the GlobalView system.
Overview The Overview Screen contains details about the data file, such as the
received and processed dates, logical file name, record count and Create
Upload File button (more details are provided on Page).
P0000 … These tabs correspond to the records selected during the Workbook
generation process (as described in the ‘ADP G2 SSL Workbook Generator
End User Guide’).
CCRMD &
MGRLK Other Master Data record types such as cost centres, manager link.
NHIRE Combines record types for easy data entry for New Hires.
Reference If the Field Help option is selected during the Workbook generation process, a
Reference Worksheet is generated containing values extracted from the
system configuration. This help is in the form of drop-down menus listing
possible values. It is configured at the country level and usually requires
further customisation by the end-user.
The types of records that can be uploaded using the Workbook are Personnel Administration
(PA) records (HR/Payroll Infotypes, Other Master Data, Time Events, etc) and Organisational
Management (OM) records. Generally speaking, organisations configured for GlobalView
Payroll services will utilize PA records, while those configured for HR and payroll will also
utilise the Workbook for OM records.
When data is prepared for uploading to GlobalView, each data item must:
Be formatted correctly.
Where a Last Name field is mandatory, the field can’t be empty and it cannot
contain numerical data.
Optional fields may also need to be of a particular format if they are to contain a value, for
example fields containing a dollar amount or a time value.
The next sections will work through the steps involved in entering data in the Overview Sheet
and the individual Worksheets.
1. Client Info
These values are populated as a result of the Workbook generation process and
cannot be changed here. If any details are incorrect, re-generate the Workbook with
the correct values (refer to the ‘ADP G2 SSL Workbook Generator End User Guide’).
2. Client Contact
Enter the operator’s name, phone number, email address and ADP contact person.
3. Program Control
Test Run is usually not required. If it is checked, a test upload file is created when the
Create Upload File button is clicked. These test files can’t be loaded into the system
and are used for testing purposes.
‘Operation’ provides the ability to send records for deletion from the GlobalView
system by entry of word delete
4. Period
Date Received - Enter the date the Workbook is received (this could be the same as
the date the Workbook is generated).
Logical Filename - Enter a name that describes the content and file creation date, e.g.
myname_july_11_upload_1. The logical filename is meta-data, or information
about the file, and must be a unique identifier.
5. Authorization
This step is generally not required. Please contact ADP if prompted for authorization,
otherwise leave blank.
6. Transaction Overview
Once all the data has been entered in the Workbook and validated on a worksheet by
worksheet basis, this button creates the Upload File that is then uploaded to the
GlobalView system.
As the pre-existing Field Help entries are general in nature, it is important to know how to tailor
the entries in the Reference Worksheet to the particular requirements of your organisation. In
some cases this will be by deleting default entries, or in other cases by adding entries or columns
to the workbook.
Click OK.
3. Select Row.
Reference Merge
The SP4 edition of Spreadsheet Loader provides the ability to import Help Field values
from another Workbook. New versions of the Workbook will be generated as further G2
configuration is completed during the implementation process; Reference Merge allows
custom values developed in the end-user workbook to be copied from one version of the
Workbook to the next version.
Add Column
Clicking Add Column will display
a window which allows for entry
of all of the column details,
including:
Before/After Field:
Fieldname
(=technical field name)
Description
The Edit button allows you to edit existing columns. Delete will simply delete a selected column.
The usual method for selecting records for deletion will be by first, downloading them,
using the Download method described above, checking and updating the details, and then
sending records for deletion.
CCRMD DELETE
Note that Cost Centre Master Data cannot be deleted by using G2 and SSL. If
necessary, use transaction KS14 Delete Cost Centres
HROBJ = HR Objects
For a Payroll Only customer (e.g. SAP HR is not configured) the values that can be loaded
using HR Objects are Position, Job and Org Unit. This is to provide basic HR information for the
purposes of payroll.
The Manager Link Table [MLT] is a table showing employee’s manager details for the purposes
of leave approvals and related functions. MLT is a flat file that is used instead of the standard
SAP Organisational Structure for the purposes of workflow and MSS reporting as the SAP
structure contains many details not required by GlobalView.
NHIRE is used to enter employee details for persons joining the Client Organisation. New Hire
has certain minimum data requirements, specifically:
Infotypes 0000, 0001 and 0002 must be supplied with no data errors and if there are any
secondary infotypes associated with IT 0002 these must also be supplied.
Infotype 0041 with Actual Hire Date must be supplied in the Date Type ‘01’.
NHIRE in the Spreadsheet Loader groups all of the mandatory fields from these infotypes into
the NHIRE worksheet.
Time Events are used to upload time-clock data and related information. Not all GlobalView
clients will be configured for time-clock data. See G2 Extension for PD clock times
inbound transfer for details.
For Organisational Management infotypes, the procedures for entering and validating data are in all
other respects exactly the same as for PA infotypes.
Worksheet Headings
Deletion of Non-required
Worksheets
Data is entered in the main body of the Worksheet, commencing at left and
tabbing through the data fields.
Cells outlined in red are mandatory fields and cannot be left blank.
Optional fields are not outlined in red and may or may not contain entries.
Field Tips
To reveal a tip for a required value,
position the cursor over the Technical
Name of the column in Row 3. A tip will
appear as a pop-up box.
Fig 20: Field Tips
Tips are indicated by the red triangle at
top right of the Technical Name cell.
Field Help
As seen previously, fields for which there
are standard entries will generally have a
Lookup List. When the cursor is placed in
Fig 21: Field Help
these fields, the prompt at right will
appear in the Status Bar.
Data Validation
Save File
The Create Upload File process
commences with a Save File dialog box.
Fig 29:Save File
File Created
If the file is created with no errors, the
following dialog box appears.
Next Steps
After completing data entry, validating each Worksheet and generating the Upload File, data
is ready for import into the GlobalView system via the G2 Spreadsheet Loader program.
Clients without access to the Spreadsheet Loader program (this includes most clients at the
point of initial data load and all Managed Services clients) will then send the Upload File to
ADP via SecureMail.
Clients with access to the Spreadsheet Loader program who are able to manage their own
data upload to GlobalView (this includes Processing Services clients) should read the next
document in this series - ADP G2 Spreadsheet Loader End User Guide.
Related Documentation
There are things that may occur at any time, such as expense claims or overtime pay. A
person may have any number of expense claims or overtime claims.
Accordingly, some types of data are subject to time constraints. If time constraints are not
taken into account when data is entered in the Workbook, it may result in validation errors in
the upload file. Frequently, this is because contradictory information has been entered, eg. a
annual leave date and sick leave date entered for the same day.
The following explanation will help to illustrate the types of time constraints that need to be
taken into account when entering periodic data. Generally speaking, each Infotype is subject
to a Time Constraint which can be found in the Time Constraint Report in the G2 application.
(For more information about the Time Constraint Report, refer to the ‘APD G2 SSL Reporting
End User Guide’.)
Further Examples
Employee is taking leave of absence from July until March of the following year.
Infotype 0001 Personnel Details will continue to exist throughout leave of absence.
An entry has been made for Annual Leave for an employee for a particular range of
dates.
A Medical Certificate is received for the employee for a day within this range.
A Sick Day is recorded for this day, creating an error – because Sick Day and Annual
Leave day cannot overlap.
Employee has submitted expense claims twice for the same claim.
Because records with Time Constraint Type 3 can overlap, the entries can be run
without causing an error.
Each employee is required to have one ‘main bank’ (time constraint 1: no gaps, no
overlap).
‘Other Bank’ record is under time constraint 3 (record is optional and can exist more
than once).
If bank details and direct deposit amount to ‘Other Bank’ is entered more than once
then duplication will occur and the direct deposit will be made more than once.
If the incorrect Excel Macro Security level is set, you may see the following error message when
opening the Workbook. (See instructions below for Excel 2007 and higher.)
1. Go to Tools>Options>Security.
Click OK.
Click OK.
Cell Format:
It is a good idea to keep a
backup workbook,
which will allow you to
view what format the
cells should be.
A backup workbook is
simply a blank copy of the
workbook with no data
entered.
4. Click OK.
1. Enable Macro security and ensure Trust Access to VBA Project model is enabled.
2. Remove any older versions of Office.
3. Install custom OWC to reinstall Web Spreadsheet component removed from Office
2007 onwards.
Macro Security
1. Choose Excel Options
1. Enable Macro security and ensure Trust Access to VBA Project model is enabled.
2. Remove any older versions of Office.
3. Install custom OWC to reinstall Web Spreadsheet component removed from Office
2007 onwards.
Macro Security
1. Choose More Commands
When multiple versions of Office are loaded especially with Project 2003 and earlier, the
Object references in the workbook to point to the wrong version of Excel. This causes the
macro code to fail with an error that the command being run doesn’t exist. To correct
this remove all versions of Office and Project. Run the Free EUSing Registry, reinstall the
2010 version of Office and then run the Custom OWC install program. When running
EuSing, scan and then repair any errors found.
http://www.eusing.com/free_registry_cleaner/registry_cleaner.htm
The screenshot below shows the error message displayed with workbook reference
errors.
There are two GL worksheets. The first is for GL Account Central Maintenance
(Infotype GLCLM - Transaction FS00) and the second GL Account Company Code (IT
GLCCD - Transaction FSS0)
The GL Account Company Code is used to send GL Code and Company Code information.
Internal Work Orders function has been provided to enable clients to write wage and
salary payments against Cost Centre numbers. Input fields are:
Please ensure that entries conform with the Template Standard Z100
Accordingly, a new record type has been created, TCUR, along with a new Segment
/ADPGV/ZXADPTCURR with following fields
TCURR – To Currency
GDATU - effective Date (in YYYYMMDD format
UKURS - Exchange rate
Apart from update via G2 this table can be maintained via transaction
ZADP_M99_TCURMNT.
User Notes