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

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:

1. BCUI > globalInfo, expand it with the triangle, and select globalInfo_DEU.
2. Add custom-string1 labeled Ethnicity and custom-string3 labeled Religion, each with Enabled = Yes and Visibility = Edit in Details. Save.
3. In Manage Permission Roles, grant the fields under Employee Central Effective Dated Entities > Personal Information. Country-specific permissions are named like DEU-Ethnicity.
4. 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

1. BCUI > jobInfo. First confirm that travel-distance is not enabled in the base jobInfo element.
2. Expand jobInfo, select jobInfo_DEU, add travel-distance labeled Travel Distance, with Enabled = Yes and Visibility = Edit. Save and confirm.
3. Grant DEU-Travel Distance under Employee Central Effective Dated Entities > Job Information.
4. A German employee (Ace Germany) sees the field. A US employee does not.

Worked Example: Employment Details for the USA and France

1. BCUI > employmentInfo, expand it, and choose Configure New Country/Region. Pick the country (for example United States, USA) and save.
2. 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.
3. 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).
4. 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