Study guide

6.5 Country-Specific Fields for Foundation Objects

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

6.5 Country-Specific Fields for Foundation Objects

Key Takeaways Explain This Topic AI

The CSF Corporate Data Model configures country-specific fields for legacy foundation objects, such as the corporate address format per country.

Country-specific configuration files use ISO 3166-1 alpha-3 country codes, for example PRT for Portugal.

The country assigned to a Legal Entity record determines which country-specific Legal Entity fields appear.

To add Legal Entity fields for a country without delivered fields, create a child MDF object with From Parent dating and a composite association.

The composite association uses Condition Field ID countryOfRegistration.code and the country's three-letter code as Condition Values.

Last updated: September 2026

6.5 Country-Specific Fields for Foundation Objects

Quick Answer: Foundation objects can show country-specific fields . For legacy (XML) objects , configure them in the CSF Corporate Data Model , for example the Corporate Address element per country. For the MDF Legal Entity , the record's country decides which country fields appear. If SAP delivers none for a country, add a child object linked by a composite association with Condition Field ID countryOfRegistration.code and the three-letter country code as the condition value.

The CSF Corporate Data Model

The CSF Corporate Data Model configures country-specific fields for legacy foundation objects . THR81's example is the business address of a Location . The United States and China show different address fields because the corporateAddress element is configured differently per country in the CSF Corporate Data Model.

Country-specific configuration files use the ISO 3166-1 alpha-3 three-letter codes, for example PRT for Portugal. If a country's code does not appear in the CSF Corporate Data Model, its country-specific fields have not been configured yet.

Worked Example: A Portuguese Corporate Address

Export the CSF Corporate Data Model from Import/Export Country/Region-Specific XML for Corporate Data Model in Admin Center or Provisioning.

Copy an existing country block, for example from the opening tag for DNK to its closing tag, and paste it before the GBR block.

Change the copied block's code to PRT and configure the corporateAddress fields:

  • Field Visibility Required Label
  • country both true Country
  • address1, address2, address3 both Address Line 1–3
  • city both City
  • state both State
  • zip-code both Postal Code

Import the CSF Corporate Data Model back in Admin Center or Provisioning.

Create the Lisbon location (PT_LIS) in Manage Organization, Pay and Job Structures and confirm that the business address section shows the configured fields.

Country-Specific Fields for MDF Foundation Objects

Legal Entity is the typical MDF foundation object with country-specific fields. Every new legal entity record in Manage Data must be assigned a country, and that country determines which country-specific fields become visible.

Some fields are pre-delivered. For example:

  • Country of registration Pre-delivered Legal Entity fields
  • United States Federal Reserve Bank, Fed Reserve Bank District, EEO Company Code
  • Germany Tax Unit, Social Accident Insurance, Social Accident Insurance Registration Number
  • Adding Country Fields Where None Are Delivered

For a country without delivered legal entity fields, the high-level steps are:

Create a child Legal Entity object to store the country-specific fields.

Create a composite association between the parent Legal Entity and the child.

In the association details, add the condition field countryOfRegistration.code and the condition values , the three-letter ISO code of the country. The child's fields then appear only for that country.

Worked Example: Legal Entity Fields for Portugal

Child object (Configure Object Definitions > Create New > Object Definition):

  • Setting Value
  • Code LegalEntityPRT
  • Effective Dating From Parent (marks it as a child object)
  • API Visibility Editable
  • Label Legal Entity Portugal

Fields externalCode (Auto Number, Not Visible), externalName (Not Visible), NIPC ( Corporate Tax Number ), NISS ( Social Security Number ), CAEcode ( CAE Code )

Association on Legal Entity (Take Action > Make Correction > Associations):

  • Attribute Value
  • Name toLegalEntityPRT
  • Multiplicity One to One
  • Destination Object Legal Entity Portugal
  • Type Composite
  • Label Portugal
  • Condition Field ID countryOfRegistration.code
  • Condition Values PRT

When prompted about warnings such as "visibility of searchable field is set to not visible", confirm with Yes. Then create Ace Portugal (ACE_Portugal) in Manage Data with country Portugal . The Portuguese fields (Corporate Tax Number, Social Security Number, CAE Code) appear only because Portugal was selected.

How Foundation CSF Connects to Employee CSF

The legal entity's country drives more than its own fields. THR81 notes that it controls the country-specific data available on the employee's Job Information, Employment Details, and Compensation Information . An employee of Ace Germany sees German Job Information fields (for example travel-distance once enabled), while a US employee sees US fields such as EEO data. This employee-side configuration lives in the CSF Succession Data Model (Section 7.3).

Comparing the Two Mechanisms

Legacy FO (for example Location) MDF FO (for example Legal Entity)

Where country fields are defined CSF Corporate Data Model (XML) Pre-delivered country fields, or child object plus composite association

What selects the country The country of the record, such as the address country The legal entity's country of registration

Tool to import or export Import/Export Country/Region-Specific XML for Corporate Data Model (Admin Center or Provisioning) Configure Object Definitions and Manage Data

Key setting A country code block such as PRT Condition Field ID countryOfRegistration.code with values such as PRT

Related: Translating Foundation Data

Country-specific fields are about which fields a country needs. Translating the names and descriptions of foundation records is a separate task. It uses the Translations icon in Manage Organization, Pay and Job Structures or the FoTranslation import for legacy objects, and the import template for MDF objects (Section 3.4).