1 / 20

Interface Development

Interface Development. Day 2. Where We Are, Where We’re Going…. Technical Workshop. Learning Objectives. Identify the scope of interfaces Identify GF interface requirements Describe GF interface processing Locate and apply sources for interface design documentation

tavita
Download Presentation

Interface Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interface Development Day 2

  2. Where We Are, Where We’re Going… Technical Workshop

  3. 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

  4. Overview of Interfaces

  5. 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

  6. Interface Technologies • SSH • Unicode • XML • EDI/Flat files

  7. Global HR Repository Interface

  8. Interfacing To/From Local Systems: High-Level Overview GLOBAL HR REPOSITORY Local IN Local OUT (3) EMPLOYEE INFO HUMAN RESOURCE SYSTEMS (2) ORGS TO LOCAL LOCAL SYSTEMS Interface TIME & EXPENSE SYSTEMS (5) TIME/EXPENSE (4) ENGAGEMENTS TO LOCAL AP VENDOR VOUCHER (6) EDI INBOUND BANK INFORMATION (7) BANK INFORMATION PAYROLL LOCAL BANK COMMUNICATIONS SOLUTIONS LOCAL BANK (7) BANK INFORMATION (8) BATCH & JET UPLOADS FIXED ASSETS* PAYROLL TO IMPREST PURCHASING CHECK PRINTING SYSTEMS CURRENCY PROVIDER DB *Currently under discussion and subject to change

  9. Global HR Repository Interface Topics • Overview of Global HR Repository • Glossary of terms • Business design requirements • Interface transmissions • GHR interface files

  10. 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 Overview – Global HR Repository

  11. 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

  12. 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.

  13. 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

  14. 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 Glossary of Terms • GLL Summary:

  15. 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.

  16. 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

  17. Employee Data Process Flow Diagram Local Systems Local Systems Local Systems Local Systems Employee Data Flow Diagram Daily EMS & AP Employee Data Feed Weekly Stdhrs Employee Data Feed Org Structure and Rank Errors and Warnings Local GNs Global Interface Staging Errors and Warnings Errors and Warnings Local GNs Loading Program Global HR Repository Org Structure Std Hours Feed AP Feed EMS Feed GF

  18. Employee Data Process Flow • Local HR • Global Interface Staging • Global HR Repository

  19. 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

  20. Fourteen files are created by the Orgs to Local Process: Industry File Org Crosswalk File Translate Values File Reporting Attributes File Source to Account Service Codes VAT Codes Orgs to Local Systems Business Purpose – Components • Closed BU File • Ranks File • Orgs File • Countries File • States File • Currencies File • Calendar File

More Related