#hr software< payroll software | Explore Tumblr posts and blogs

dimac25305 · 5 years ago

Text

YOU’RE NOT THE BOSS OF ME – SAP/HCM battles KRONOS

With the sun due to set on the Production HCM (Human Capital Management) component of SuccessFactors SAP system, the company has been working with the global Human Resources team to build a user-friendly employee self-service portal to hopefully launch in August 2020.

The new Employee Central Hub is being designed and built with these system flaws in mind and we are not in the testing phase yet. The global team has had different experiences therefore, each country is designing workflows that best suits their needs. This is causing conflict in certain areas and not all processes translates the same way on the global stage. The new system is basically an intersection of human resources and information technology through HR software. This allows HR activities and processes to occur electronically and accommodate the many different aspects unique to each member of the team.

This might sound like a great idea given that we can now build a new shiny portal to make life easier for employees who need to make changes to their employee record on their own.

(Insert the sound of screeching brakes here)

Let’s back up a smidge. The current HCM system is so faulty that is thinks it’s the boss of KRONOS, which is the timekeeping system that is not compatible with anything known to man. The two systems hate each so much that it causes tremendous chaos and confusion for the end-user and too often creates payroll errors.

HCM is the ‘entry’ way to the employee record, however, extremely limited amount of information flows into KRONOS from HCM which means multiple layers of manual set up is required after the file feed from HCM over to KRONOS a day or so later. Here is an example of how persnickety KRONOS is. If an employee’s name is too long, it will only capture the person’s first letter of their first name resulting is so much havoc that a system analyst with high level access is the only person that can correct the issue by waving a magic wand on the back end of the system. The same way Mr. Scott, Chief Engineer of the Enterprise, is the only one who can put the engines back online so the warp drive will function allowing the starship to escape the neutral zone and avoid a war with the Romulans. (Remember, Romulans don’t take prisoners).

In escaping the neutral zone one might think the ship is out of danger. Yet, the Enterprise wanders into an Asteroid field. Now, the two systems engage in another battle of brawn. While the balance of power appears to be even and the employee record has been created in HCM and the manual set up allowing for specific levels of KRONOS access has been established, the employee needs to simply update their address, phone number, gets a promotion or any other type of change to their employee record which is first processed in HCM.

The next day, KRONOS, being the enemy from within, resets the access levels back to the employee’s original settings leaving them without access to either enter their work hours or for managers to have the ability to view and manage their teams time or a myriad of other issues. No notification is sent and not a clue is given that something is wrong. Anarchy ensues to a barrage of emails, Skype messages and phone calls of panicking staff begging the HRIS (Human Resources Information Systems) team to drop what they are doing and fix all these issues immediately.

I wish we had someone like Lt. Uhura to monitor all communications and only put through what was REALLY important.

Here’s the rub - this is an inconsistent system flaw in that not every change in HCM results in resetting KRONOS access levels. I think it depends on which way the wind is blowing that day.

Most days, the HRIS team can be flooded with emails on a daily basis to resolve the battle between HCM and KRONOS.

It may seem that KRONOS has the upper hand in the feud for attention, however, the information only flows one way – from HCM to KRONOS. Never from KRONOS back to HCM which means that anything set up in KRONOS will be wiped out 99% of the time a change is made in HCM.

If HCM had a voice ↓

One important goal for the global team to design is how to manage the workflow from HCM into KRONOS so that KRONOS doesn’t reset accrual profiles.

4 notes · View notes