Study guide
7.4 HRIS Synchronization and Sync Mappings
SAP Certified - SAP SuccessFactors Employee Central Core and Position Management C_THR81
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: C_THR81 Exam and SAP SuccessFactors Platform Foundations
1.1 C_THR81 Exam Format, Logistics, and Preparation Plan 1.2 SAP SuccessFactors Suite, Platform Capabilities, and Employee Central Core 1.3 Instances, Provisioning, and Company Settings 1.4 Administrator Types, Super Admin Access, and Admin Center Navigation 1.5 Release Management, Upgrade Center, Release Center, and Consultant Resources
2 Chapter 2: Security, Proxy, and System Administration
2.1 Role-Based Permissions: Groups, Roles, and Target Populations 2.2 RBP Troubleshooting, Reports, and Governance Best Practices 2.3 Proxy Management, Company System and Logo Settings, and Platform Feature Settings 2.4 Admin Alerts, Check Tool, and System Access Settings 2.5 Scheduled Job Manager, Provisioning Job Scheduler, and Execution Manager
3 Chapter 3: User Experience Configuration
3.1 People Search, Action Search, Custom Navigation, Org Chart, and Built-In Support 3.2 Home Page Configuration and Mobile Settings 3.3 E-mail Notifications, Themes, and Company Logo 3.4 Text Replacement, Manage Languages, and Translations
4 Chapter 4: People Profile, Picklists, User Data, and the Metadata Framework
4.1 Latest People Profile, Categories, Cards, and Custom MDF Cards 4.2 Manage Business Configuration and Succession Data Model XML Fundamentals 4.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist 4.4 User Data File, Employee Import, and User Management Tools 4.5 Metadata Framework Enablement and Object Definition Settings 4.6 MDF Fields, Associations, Search, and Security
5 Chapter 5: Business Rules
5.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log 5.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects 5.3 Propagation Rules and Hire/Rehire Rules 5.4 Cross-Entity Rules, Rule Context, and Rule Design Practices
6 Chapter 6: Foundation Objects and Corporate Data Models
6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence 6.2 Foundation Objects: Organization, Pay, and Job Structures 6.3 Configuring Legacy and MDF Foundation Object Definitions 6.4 Foundation Object Associations and Field Criteria 6.5 Country-Specific Fields for Foundation Objects
7 Chapter 7: Employee Data Structures and Permissions
7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers 7.2 Configuring the Succession Data Model with BCUI and XML 7.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data 7.4 HRIS Synchronization and Sync Mappings 7.5 Employee Central Permissions for Administrators
8 Chapter 8: Employee Transactions and Data Maintenance
8.1 Hire, Rehire, Termination, and No-Show Transactions 8.2 Importing New Employees and Updating Employee Data by Import 8.3 Mass Data Management for Job Information, Job Relationships, and Positions 8.4 Employee and Manager Self-Service Permissions
9 Chapter 9: Workflows, Alerts, and Event Reasons
9.1 Workflow Configuration, Participants, Dynamic Roles, and Dynamic Groups 9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval 9.3 Employee Central Alerts and Notifications 9.4 Events, Event Reasons, and Event Reason Derivation 9.5 Workflow Derivation Rules and How They Work with Event Reason Derivation
10 Chapter 10: Optional Employee Central Configurations
10.1 Employee Central Quick Actions and Internal Job History 10.2 Custom Hire Templates, the Diagnostic Tool, and Joule in Employee Central
11 Chapter 11: Position Management Setup
11.1 Position Management Overview: Positions, Jobs, and the Leading Hierarchy 11.2 Enabling Position Management and Setting Role-Based Permissions 11.3 Navigating and Configuring the Position Organization Chart 11.4 Configuring the Position Object 11.5 Position Management Settings 11.6 Creating, Maintaining, Importing, and Mass-Changing Positions
12 Chapter 12: Position Management in the Employee Lifecycle
12.1 Position Fields in Job Information and Hiring Employees to Positions 12.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return 12.3 Manager Self-Service with My Team Positions and Quick Actions for Positions 12.4 Terminations with Position Management and Position Workflows
13 Chapter 13: Position Management Rules, Integrations, and Company Structure
13.1 Position Management Rule Scenarios and Rules for Position Data Entry 13.2 Synchronization Rules and Mass Change Runs for Positions 13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions 13.4 Integrating Position Management with Recruiting and Succession 13.5 Building the Company Structure Overview
7.4 HRIS Synchronization and Sync Mappings
Key Takeaways Explain This Topic AI
HRIS sync is a one-way synchronization of Employee Central data into the user data tables and Employee Profile used by talent modules.
Changes saved in the UI trigger synchronization automatically for current and past-dated records; imports and scheduled sync jobs also sync data.
Some mappings are hard-coded, such as jobInfo job-code to jobCode and emplStatus to status, and must not be configured again in the data model.
Custom sync mappings use the hris-sync-mappings section of the Succession Data Model or HRIS Sync Mappings in BCUI.
HRIS sync jobs are created in Scheduled Job Manager or Provisioning and can be one-time or recurring, incremental or full.
Last updated: September 2026
7.4 HRIS Synchronization and Sync Mappings
Quick Answer: HRIS synchronization is a one-way copy of Employee Central data into the user data tables and the Employee Profile . Talent modules such as Performance, Goals, Compensation, and Recruiting read those tables. Some field mappings are hard-coded , and you add custom mappings in the Succession Data Model or in BCUI's HRIS Sync Mappings . Sync happens automatically after UI saves and imports, and through Sync HRIS Data jobs.
Why HRIS Sync Exists
Employee Central is the core HR system and holds the most accurate, foundation-linked employee data. The Employee Profile is the platform for talent activities and needs a "mini-master" of core employee data to run them. Several areas still store data in legacy user tables . HRIS sync populates those tables with EC data , so employee data is accurate across the suite.
Without EC , talent processes rely on data imported with the User Data File (Section 4.4). That data feeds the standard Org Chart, dashboard and report filters, and the route maps for Performance and Compensation.
With EC , some talent modules still refer to the user data, but HRIS sync fills it automatically , so nobody uploads it manually.
Warning: to avoid inconsistencies between EC and the legacy tables, do not use the Basic Import or the UDF to update legacy tables directly. Changes from the UI or a scheduled UDF import can overwrite data coming from EC.
When HRIS Sync Is Triggered
Changes saved in the UI: sync starts automatically at the end of the update for current and past-dated records.
Imports of employee data.
Scheduled HRIS sync jobs , which periodically find EC changes and update the legacy tables. The automatic UI sync covers current and past-dated records, and SAP says the sync job itself should be configured to run on a schedule.
Jobs can be one-time or recurring and incremental or full .
Hard-Coded Sync Mappings
Some EC fields are synced to standard elements by default, based on hard-coded rules . You must not configure these in the Succession Data Model , because doing so can cause undesired results. The system also prevents duplicate mappings in the sync-mappings section, and BCUI validates against mapping hard-coded fields . Examples:
- HRIS element HRIS field Standard element
- employmentInfo start-date hireDate
- jobInfo emplStatus status
- jobInfo manager-id managerId
- jobInfo job-code jobCode
- jobInfo department department
- jobInfo division division
- jobInfo location location
jobRelationsInfo rel-user-id (using picklist external codes for HR manager, matrix manager, second manager, custom manager) the corresponding relationship
The complete list is in Implementing Employee Central Core .
Custom Sync Mappings
Custom mappings connect other EC fields, standard or custom, to standard elements , userInfo elements , or userInfo record key elements . HRIS sync considers these mappings when propagating EC data to the other products. For example, you can map Employment Details: Eligible for Stock to the standard element Customizable Field 9 .
In the Succession Data Model XML
Custom mappings go in a separate hris-sync-mappings section:
- identify the EC block with hris-element-ref refid="jobInfo"
- identify the EC field with hris-field-ref refid="business-unit"
- identify the Employee Profile field with standard-element-ref refid="custom01"
- update the XML and upload it to Provisioning <hris-sync-mappings>
- <hris-element-ref refid="jobInfo">
- <hris-mapping>
- <hris-field-ref refid="business-unit"/>
- <standard-element-ref refid="custom01"/>
- </hris-mapping>
- </hris-element-ref>
- </hris-sync-mappings>
Several hris-mapping sets can go inside one hris-element-ref, and several hris-element-ref sets inside hris-sync-mappings. The attribute entity-type is mandatory for mappings of address, email, phone, and global info , because it specifies which type (for example a business or personal e-mail). Check the external codes in the Picklist Center.
In BCUI
Go to Manage Business Configuration > HRIS Sync Mappings , choose + , select the HRIS Element ID , the Field ID , the Target Field Type , the Target Field ID , and the Entity Type where applicable, then save. All mappings appear on one screen, and a mapping also shows in the details of the mapped field. You can create a mapping in either place.
Worked Example: Standard Hours for Talent Reports
ACE wants Standard Weekly Hours to be reportable in Employee Profile reports:
BCUI > Employee Profile > Standard > custom07 : set the label, default label, and translations to Standard Hours .
BCUI > HRIS Sync Mappings > + : HRIS Element Job Information , Field Standard Weekly Hours , Target Field Type Standard Field , Target Field Standard Hours (custom07) .
Configure Latest People Profile > Talent Profile > Edit Employee Information > Content Configuration : add Standard Hours .
Test real-time sync by inserting a Job Information record effective today (event Data Change ) with new standard hours, then refresh the profile. The talent value matches.
Running HRIS Sync Jobs
HRIS sync jobs are created in Provisioning or in Scheduled Job Manager . THR81's recovery scenario: an intern uploaded the wrong Basic Import (UDF), so talent data no longer matches EC. The fix is a one-time job:
- Field Value
- Job Type Sync HRIS Data
- Sync Type Sync Changes Since the Last Successful HRIS Sync Job
- Occurrence One-Time
- Notifications For example, send e-mails when the job starts
Submit it, choose Run it Now on the Job Scheduler tab, and watch the Job Monitor . Completion depends on the queue.