We are considering Workday to replace our HRMS system, PeopleSoft version 9.1. Our DBAs are curious how the different database models might impact data conversion and our reporting model. Can you share some legacy wisdom on the major differences? --Database Dilemma from Atlanta, GA
Dear Database Dilemma:
It’s great that your DBAs are already looking at this and trying to get an understanding of how best to leverage the future state! Your IT Organization is probably very used to working with tables such as PS_JOB, PS_PERSONAL_DATA and managing the joins and SQL statements between these two. In addition, they are concerned about managing “Performance” and not allowing general end users to create reports on the fly for fear of taking down the system. These are issues that many of our legacy PeopleSoft clients faced.
You’ll see right away that the relational database model in PeopleSoft differs from Workday’s Object Management Model. Generally speaking, Workday’s OMS (Object Management System) takes the guesswork out of maintaining these legacy relational tables. It even helps streamline the data conversion effort. By delivering and managing data in Objects, the OMS takes responsibility for creating and managing these “Joins” between each of the data sources in the Object. The end result allows the user to utilize multiple data sources at one time to extract or import data; however, all the referential integrity and the concepts of inner/outer joins has already been managed for the users.
From a conversion perspective, all Workday clients are on a single code line which means they share the same Data Source structure and the referential integrity rules are already in place. This also means Workday’s conversion methods are significantly streamlined from legacy efforts. Because of these standardizations, the Workday platform essentially has half of the data conversion (import routines) already built for its clients. Your DBAs now just need to be concerned about the extraction of the data from PeopleSoft, worrying less about the import routines.
At the end of the day, the Workday platform reduces the inherent complexity and risk found in data conversion, integrations and deployment of reports to end users. There are many benefits to having “checks and balances” built into the system as delivered. They allow our customers to focus more on tasks supporting their business objectives rather than building redundant code or managing database reporting risks. Happy Workday deployment!
Have a migration-to-Workday question for Dear Collabie? Submit your request.