Job Classification Change - Synch to Position

[bkelley62]

Hello -- we have encountered situations where updating a job classification does synch to the position(s).  This behavior seemed to have started after one of the recent upgrades.  So the question to the community is: why are the positions are not syncing when job classifications are updated?  

I read in another community post that there is no standard trigger from Job Classification to Position.  

If you've had this same issue, what solution did you come up with so that job classification would syncing to the position information?

Thank you -- BK

[JaninaHornig]

Hi 🙂 Could you provide some more details on what exact changes you are making to the Job Classification - I assume you are updating Job Classification objects in Manage Data, is that correct? Could you share an example?

[bkelley62]

Hello -- we are actually updating employee records through an employee data import/export process.  The HR team is exporting a data template for a group of employees and making adjustments in job classification, postion, pay grade, pay range, etc.  They are using six different templates to update the data.  Once the data is updated and imported back into SuccessFactors, they are wanting all the data to synch to the respective portlets -- compensation, job information, job classification.  My understanding is that it would take a custom integration for that to happen.

[JaninaHornig]

Thank you for clarifying this! So, if you are updating employees' Job Information records through the "Import Employee Data" transaction in EC, these changes (if effective today) will show in the Job Information/Organizational Information/Position Information EC portlets in the profile once the import job has completed successfully. There is no sync required for that, as you are updating the same entity that you are viewing in the profile (if my understanding of your scenario is correct). This applies to a Compensation Information import as well - changes will be visible in the Compensation Information portlet if effective today - if effective in the future, they will show only when the effective date of the imported changes arrives. Job Classification isn't a standard profile portlet, so I am not sure what the configuration in your instance is. In case your leading HR system is an external system and that's where the changes are made, then they will need to be synced into EC through an integration job. Are you in the implementation phase or is this in Production?

[bkelley62]

Hello - this is in our production system and we're using Employee Central as our primary HR system. I'm looking at an example HR sent where you can see the pay grade change in Manage Data > Job Classifcation but the EC Job Information still shows the old paygrade. The import changed the pay grade in Job Classifcation to a P11 but Job Information in EC on the employee sill shows P10.

[JaninaHornig]

Ah I see. For this particular example, I don't think there is a process that syncs this information. Job Information stores a reference (object ID) to the employee's job classification, but any field changes in the Job Classification object will not have an impact on Job Info.

[JaninaHornig]

Sorry, my response posted too soon. If you have an onSave rule in Job Info that sets the pay grade field (i.e. Set Job Information.Pay Grade.Value to be equal to Job Information.Job Classification.Pay Grade") then this will happen when you save changes to an employee's Job Information, but not when you save the Job Classification object. Can you reach out to whoever configured your instance and set up the Job Information data model and the business rules?

[bkelley62]

Thank you for the information. I'm going to run this by our EC consultant and check our OnSave rules.

[JaninaHornig]

Yes, that'll be the best thing to do 🙂

[vanessilva]

Hello! Hope you are fine. In this scenario which is the best practice when we are updating Job Classification objects in Manage Data and needs Position update as well.