Job Profile or Position table

[rogue9]

For contingent worker to a proper worker scenario - being integrated from Sucessfactors, what would be the right way to drive employee experience for conversion scenarios: i.e from a consultant to an FTE?

Just using HR profile and user profile is not ideal because the system of record cannot send two records  if it does, would HR profile always be current data as of today - or does the job profile open up options to handle this better?

Cheers

[POOJA SINGH18]

Hi @rogue9 

Ideally, you should maintain a single employee profile that can handle both contingent workers and FTEs. In SuccessFactors, this can be achieved by using a single employee record with appropriate flags or attributes to indicate the worker's status (e.g., contingent, FTE). This way, you avoid the need for multiple records and can maintain a consistent history of the worker's journey within the organization.

HR Profile and User Profile:

• In ServiceNow, the HR Profile contains essential employee information, such as personal details, job information, and employment history. The User Profile is associated with an employee's account and contains access permissions and preferences.
• For a contingent worker to FTE conversion, you would need to update both the HR Profile and User Profile to reflect the new employment status and job details.
• You can use scripting and workflows to manage this data update process. Ensure that data is synchronized between these profiles to maintain data integrity.
  
  

  Effective Dating and Job Profiles:

  • ServiceNow supports effective dating, allowing you to track changes to employee data over time. When converting a contingent worker to an FTE, make sure to update the records with the appropriate effective date to capture when the change occurred.
  • Leveraging job profiles is essential in this scenario. Job profiles define job-specific information, such as roles, responsibilities, and qualifications. Ensure that the job profile for the FTE accurately reflects the new role.
    
    
    

    Hope it helps and please mark helpful if it solves the issue.

    Thanks,

    Pooja Singh

[JT8]

This is a great explanation Pooja!

I would recommend for the folks who use systems with different naming conventions to consider looking at the product documentation for the Jobs table (sn_hr_core_job) for storing things like worker job history. This will allow you to use the HR Profile as a current 'snapshot' of the user, including their current + primary job.

Note: I recommend working with your domain experts to make sure you understand their staffing model (e.g. position management) in order to determine an optimal approach.