3774227 - Timezone Defaults to UTC in USERS_SYSINFO for Onboarding Users - HRIS Sync Required - Onboarding

• For users hired via Onboarding, the timezone in backend table USERS_SYSINFO is maintained as UTC
• The correct timezone (for example, US/Eastern) is stored in EMP_JOB_INFO_T
• The discrepancy persists even after completion of onboarding and hiring steps
• UDF export reflects the timezone as UTC for such users

SAP SuccessFactors Onboarding

1. Initiate a new hire through Onboarding.
2. During the Review New Hire Data (NHDR) step, ensure the Location field is populated (with business rule deriving timezone).
3. Complete the onboarding process and proceed beyond the start date.
4. Validate backend tables:
   • EMP_JOB_INFO_T → Timezone reflects correct value
   • USERS_SYSINFO → Timezone is maintained as UTC
5. Once the candidate is hired, download UDF export and observe timezone is shown as UTC.

• This is an expected system behavior.
• During onboarding, the user record is created at an early stage where timezone information is not yet available. As a result, the system assigns the default timezone (UTC) in USERS_SYSINFO.
• Once the onboarding process progresses and job information is updated (for example, via location-based business rules), the correct timezone is stored in EMP_JOB_INFO_T.
• However, the timezone field is not automatically synchronized from Job Information to USERS_SYSINFO, as it is not part of the standard HRIS Sync configuration.

To ensure the timezone is consistently updated in USERS_SYSINFO, it is required to configure and validate HRIS Sync for the timezone field.

1. Configure HRIS Sync Mapping

• Navigate to: Admin Center → Manage Business Configuration → HRIS Sync Mappings
• Create or maintain mapping as follows:
  • Source HRIS Element: Job Information (jobInfo)
  • Source Field: Timezone (timezone)
  • Target Field Type: Standard Field
  • Target Field: Time Zone (timeZone)
• Save the configuration

2. Understand HRIS Sync Behavior

• For UI-triggered changes (e.g., saving Job Information), HRIS Sync is triggered automatically in real time

3. Validate Data Consistency

• Ensure the timezone value is correctly stored in Job Information (EMP_JOB_INFO_T)
• Verify that the same value is updated in USERS_SYSINFO after HRIS Sync execution

4. Verify Prerequisites

• Ensure the Job Information record is active and effective
• Confirm the timezone field is properly populated and saved
• Verify required permissions are in place to read Job Information data
• Ensure the Location Foundation Object is configured with the correct timezone value, as the timezone in Job Information is typically derived from the location via business rules

Note: Timezone is not a hard-coded HRIS Sync field and must be explicitly configured

• 2080587 - How to Sync Correct Timezone to Public Profile in Employee Central
• 2080065 - What is a Full HRIS Sync? - Employee Central
• 3634254 - Time zone field in Employee Profile not updated automatically during hire - SuccessFactors Employee Central
• 2079939 - Public profile displays the employee’s local time incorrectly
• Fields Hard-Coded for Syncing (HRIS Sync)
• 3119552 – Deprecation of Job Information Data Model Fields

onboarding, manage pending hires, timezone, utc, eastern, users_sysinfo, udf, employee profile, job information, hris sync, timezone mapping, new hire data review, location rule, emp_job_info, ec mph , KBA , LOD-SF-OBX-EC , Integration EC - MPH, Hire , Problem