Study guide

7.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data

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.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data

Key Takeaways Explain This Topic AI

HRIS elements with country-specific support are globalInfo, homeAddress, nationalIdCard, jobInfo, compInfo, and employmentInfo.

The standard CSF Succession Data Model provides preconfigured country-specific fields for more than 100 countries.

National ID validation uses the country ID, a format ID for the card type, and a regular expression for the accepted format.

The employee's legal entity determines the country-specific fields in Job Information, Compensation Information, and Employment Details.

A country-specific field reused across countries in jobInfo, employmentInfo, compInfo, or nationalIdCard may differ only in its label.

Last updated: September 2026

7.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data

Quick Answer: The CSF Succession Data Model adds country-specific fields and formats to six HRIS elements: globalInfo, homeAddress, nationalIdCard, jobInfo, compInfo, and employmentInfo . The standard model covers 100+ countries . For job, employment, and compensation data, the employee's legal entity decides which country's fields appear. Country-specific personal fields live in globalInfo , shown inside the Personal Information card.

  • Which Elements Support Country-Specific Fields
  • Global Information (globalInfo)
  • Addresses (homeAddress)
  • National ID Information (nationalIdCard)
  • Job Information (jobInfo)
  • Compensation Information (compInfo)
  • Employment Information (employmentInfo)

The standard CSF Succession Data Model provides preconfigured country-specific fields for more than 100 countries . For example, the Personal Address block looks different for the United States and the Philippines.

National ID

The national ID format group is preconfigured for many countries. The data model settings drive the UI:

  • Country Id: which country's formats and fields are displayed
  • Format Id: the national ID type for the country
  • Regular expression: the accepted data format

For a US Social Security Number, the accepted format is three digits, a dash, two digits, a dash, and four digits . France's INSEE number uses a different format.

National IDs can also be tracked over time . The fields valid-from , valid-to , and record-id allow several national ID records per person, each with its own period. The Allowlist Configuration Detail for National ID with Validity Period (in Manage Data) defines how multiple records are handled. The allowlist must be defined before storing multiple records of any card type.

Home Address

The home address element is preconfigured per country. In the standard model, the county field for GBR uses the picklist COUNTY_GBR , and the state field for CAN uses PROVINCE_CAN .

Global Information

globalInfo is pre-delivered for most countries. Its fields appear in the same People Profile block as Personal Information . In SAP's sample configuration, the US globalInfo shows Ethnic Group and Veteran Status with picklists. Country-specific gender values are also set up in globalInfo (Section 4.3).

Worked Example: Germany

ACE adds Ethnicity and Religion for Germany:

BCUI > globalInfo , expand it with the triangle, and select globalInfo_DEU .

Add custom-string1 labeled Ethnicity and custom-string3 labeled Religion , each with Enabled = Yes and Visibility = Edit in Details. Save.

In Manage Permission Roles , grant the fields under Employee Central Effective Dated Entities > Personal Information . Country-specific permissions are named like DEU-Ethnicity .

Check a German employee's Personal Information (View All > Show empty fields) for Ethnicity (Germany) and Religion (Germany) .

Job Information, Employment Details, and Compensation

jobInfo is pre-delivered for most countries. The legal entity determines the country-specific fields in Job Information : an ACE USA employee gets US fields such as the EEO fields. compInfo and employmentInfo can also hold country fields, but the standard CSF model delivers none . The employee's legal entity decides which country applies.

Reuse rule: for jobInfo, employmentInfo, compInfo, and nationalIdCard , if you reuse a country-specific field across several countries, you may change only the label . Visibility, required, and the other attributes must stay the same.

Worked Example: Travel Distance for Germany

BCUI > jobInfo . First confirm that travel-distance is not enabled in the base jobInfo element .

Expand jobInfo, select jobInfo_DEU , add travel-distance labeled Travel Distance , with Enabled = Yes and Visibility = Edit . Save and confirm.

Grant DEU-Travel Distance under Employee Central Effective Dated Entities > Job Information .

A German employee (Ace Germany) sees the field. A US employee does not.

Worked Example: Employment Details for the USA and France

BCUI > employmentInfo , expand it, and choose Configure New Country/Region . Pick the country (for example United States, USA) and save.

Choose Take Action > Make Correction on employmentInfo_USA and set Enabled = Yes . SAP notes it is very common to forget to enable a newly created CSF element. You may need to refresh before the country shows as active.

Add the fields: for the USA, Probation Waived (custom-string1, picklist yesNo) and End of Probation (custom-date1). For France, Hiring Initiative (custom-string2) and Previous Service From (custom-date2).

Grant permissions, then verify: US and French employees see their fields, and a German employee sees neither.

Configuring CSF in XML Instead

The same changes can be made in the CSF Succession Data Model XML (validated against country-specific-fields.dtd ). Country blocks use ISO 3166-1 alpha-3 codes such as USA, DEU, and FRA. XML suits bulk changes across many countries (Section 7.2). SAP notes there are many country details and exceptions and points to the Employee Central Country-Specific Implementation Handbook for current specifics.

Troubleshooting Country-Specific Fields

Symptom Likely cause

New country fields never appear The CSF element was not set to Enabled = Yes , or the field lacks an RBP permission

Fields appear for the wrong employees The employee's legal entity belongs to another country; CSF follows the legal entity

Save error when reusing a field across countries Attributes other than the label differ between countries

Several national IDs of one type cannot be stored The allowlist for national IDs with validity periods is not configured