MARCH 2004
Day 2
Interface
Developme
nt
Where We Are, Where We’re
Going…
Technical Workshop
Monday
Welcome
Overview
Tuesday
and
GS/LIS (Cont.)
Wednesday
Interface
Development
Thursday
Friday
Interface
Testing (Cont.)
Local Testing
Technical
Migration
Implementation
Next Steps
Technical
Introduction
Global T&E
Datafeeds
Conversion
Testing
Technical
Deployment
Overview
Conversion
Development
Interface
Testing
Break-out
Discussion
Groups
GS/LIS
Technical Workshop
2
Learning Objectives
Identify the scope of interfaces
Identify GF interface requirements
Describe GF interface processing
Locate and apply sources for interface design
documentation
 Complete a local practice interface usage profile
 Update system diagram




Technical Workshop
3
Overview of Interfaces
Technical Workshop
4
Datafeeds vs. Interfaces
Datafeeds are not the same as Interfaces
 Interfaces





Used by Local Systems for Validations
Have Business Rules built into them
Have Critical Interdependencies between them
Are about the Present and Future
Code block is not shifted
 Datafeeds
 Designed primarily to support out of scope downstream
applications
 Code block is shifted on data sourced from Engagement Reporting
and Datamart
 On cycle close, data is as of the cycle close until the batch process
is complete
Technical Workshop
5
Interface Technologies




SSH
Unicode
XML
EDI/Flat files
Technical Workshop
6
Global HR Repository Interface
Technical Workshop
7
Interfacing To/From Local
Systems: High-Level Overview
GLOBAL HR
REPOSITORY
Local IN
HUMAN RESOURCE SYSTEMS
Local OUT
(3) EMPLOYEE INFO
(2) ORGS TO LOCAL
TIME & EXPENSE SYSTEMS
(5) TIME/EXPENSE
Interface
AP VENDOR VOUCHER
INBOUND BANK INFORMATION
(4) ENGAGEMENTS TO LOCAL
LOCAL SYSTEMS
(6) EDI
(7) BANK INFORMATION
PAYROLL
FIXED ASSETS*
LOCAL BANK
COMMUNICATIONS
SOLUTIONS
(8) BATCH & JET UPLOADS
PAYROLL TO IMPREST
PURCHASING
CHECK PRINTING
SYSTEMS
*Currently under discussion and
subject to change
CURRENCY PROVIDER
DB
Technical Workshop
8
LOCAL
BANK
Global HR Repository Interface
Topics
 Overview of Global HR Repository
 Glossary of terms
 Business design requirements
 Interface transmissions
 GHR interface files
Technical Workshop
9
Overview – Global HR
Repository
Global Interface
Staging (GIS)
Country 1
Country 2
Organization Structure and
List of Global Values
Country n
GF
•Global HR List of Values
•Error Files
•GPN Crosswalk Files
Global HR
Repository
Other
Applications
Global
Directory
Technical Workshop
10
Overview – Global HR
Repository
 Employee HR data is needed in GF to:
 Provide information needed for financial calculations in
EMS
 Validate time submissions
 Support expense reimbursements
 Provide standard hours to support revenue
calculations and utilization reporting
Technical Workshop
11
Glossary of Terms
 Local Personnel Number (LN)
Assigned by the member firm
Unique within the member firm
May be used to build GN
Global HR Repository sends this ID back along with GN
and GUI to each managerial country.
Technical Workshop
12
Glossary of Terms
 Global Unique Identifier (GUI)
 Unique global identifier that will follow the person
across all managerial countries
 Each managerial country will be given a range of
numbers for assigning GUI
 Managerial country must verify existence of GUI for
personnel hired from other E&Y firms to ensure
uniqueness
Technical Workshop
13
Glossary of Terms
 GLL Summary:
Identifier
Generated by
Used in
Used as unique
identifier in
LPN
Local country
Local country
systems, GHR
Local country
systems
GN
GHR
GHR, GF
GF
GUI
Local country
GHR, GF
GHR
Technical Workshop
14
Business Design
Requirements
 The local systems will
send XML files containing
required and optional
data elements for GF,
Global Directory, and
Global HR.
 All inbound files are to
conform to GIS
standards.
Technical Workshop
15
GHR Interface Summary
 Global HR Repository:
 Stores employee data for all member firms
 Is the main source of HR data for global applications
 Uses the employee identifiers GPN, LPN, and GUI
 Employee HR data is needed in GF to:




Provide information needed for financial calculations in EMS
Validate time submissions
Support expense reimbursements
Provide standard hours to support revenue calculations and
utilization reporting
Technical Workshop
16
Employee Data Process Flow
Diagram
Local
Systems
Employee Data
Flow Diagram
Local
GNs
Local
Systems
Local
Systems
Daily
EMS & AP
Employee
Data Feed
Weekly
Org
Structure Stdhrs
and Rank Employee
Data Feed
Local
Systems
Errors
and
Warnings
Global Interface
Staging
Local
GNs
Loading Program
Global HR
Repository
Org
Structure
EMS
Feed
Std Hours
Feed
GF
Technical Workshop
17
AP
Feed
Errors
and
Warnings
Errors
and
Warnings
Employee Data Process Flow
 Local HR
 Global Interface Staging
 Global HR Repository
Technical Workshop
18
Global HR Repository
Dependencies
 Initial steps during GF technical migration:
 Local practice has fully integrated GHR and has been
receiving employee crosswalk files
 Local practice configuration and conversion data
resides in GF
 Local practice receives Orgs to Local interface
 Local practice locally assigns employees to valid orgs
 GHR sets local practice to “In GF”
 Local practice submits new employee org assignments
to GHR
 GHR communicates employee org info to GF
Technical Workshop
19
Orgs to Local Systems
Business Purpose –
Components
 Fourteen files are created by the Orgs to Local Process:







Closed BU File
Ranks File
Orgs File
Countries File
States File
Currencies File
Calendar File







Technical Workshop
20
Industry File
Org Crosswalk File
Translate Values File
Reporting Attributes File
Source to Account
Service Codes
VAT Codes