Curious to know how other customers are doing employee record updates and mapping them for S3. For instance, if someone gets married. Change the martial status from single to married on the at a glance screen, save, and then effective date, but how are you mapping those changes over to S3 so benefits and payroll know it was a martial status change?
This is my understanding of "Updates": Shows up in the audit log under a business class of HCM (which from my understanding is a "catch all" business class). We needed some identfier over in S3 so payroll and benefits understood what was meaningful changes and what was not so meaningful changes, so we cross referenced the HCM business class to an action code in S3 called CHGMISC. However, just about anything a Generalist does to the employee record falls under this HCM business class: phone updates, address updates, manager code changes, work type updates, etc. So basically, this isn't helping our initial goal, and it's becoming a nightmare for our S3 folks because everything is being lumped into this HCM / CHGMISC bucket.
I have yet to find a way to note a reason for the change or anything because when doing updates... you just do the update and put in an effective date.
How are you handling these types of things?
