1.

With Manage Business Configuration, enable the attachment-id field in Biographical

Information. Set the field to be labeled as Biographical Attachment and configured as editable.
a. Go to Manage Business Configuration.
b. Select the hris-element personInfo.
c. At the bottom of the field list, select the field identifier drop-down list.
d. Select attachment-id.
e. Add the label, Biographical Attachment.
f. Set Enabled to Yes.
g. Select Details and check if visibility is set to Edit.
h. Select Done, then save the element.
i. If you are prompted to confirm other changes made to the data model by BCUI, select
Yes.

2. Verify the field has been added to the Biographical Information block in the Employee File.
a. Search for Marcus Hoff and go to Personal Information → Biographical Information.
b. Select Edit(pencil icon). Verify that the new field exists.
c. Select Cancel.

Generic Object to the Succession Data Model

Often customers want to use a Generic Object to function like the Employee Central predefined
Foundation Objects. These Generic Objects can be created, configured, and then used in the
Employee File as custom fields in the hris-elements. They can use associations to filter valid values for
the Generic Object Record.

How to Assign a Generic Object to a Custom Field in Succession Data Model

1. Go to Manage Business Configuration, and select the relevant HRIS Element.

2. Create a new custom string field and complete the Label, Section (if required), and Enabled
fields.
3. Open the Details of the field, and update the following fields:
a. Type of Reference Object: Foundation Object.
b. Reference Object: the ID of the Generic Object.
4. If your Generic Object uses association filtering, configure the appropriate values in the field
criteria.
5. Save your changes.
6. Assign any required role-based permissions for the new custom field.

Exercise: Assign a generic object to the Succession Data Model

Business Example

Business Example: ACE would like to add a field in Job Information to reference the company’s
parking records. At the same time, they would also like it to be filtered based on the employee’s
location.
If you completed the prior exercise on creating a custom Garage Generic Object, you can use the
Garage object instead of the Parking object. The same process could be used to assign it to the
Succession Data Model.

Determining the Destination Field Value and Source Field name is covered in the topic on
Creating Associations.

Steps
 1. Verify that Parking records already exist and are assigned to a location.
a. Go to Manage Data.
b. Change the search field to Parking.
c. Review the two records that exist. Note the assigned location(s) for each record.
2. Locate the ID of the Parking Generic Object to be used on the employee file.
a. Go to Configure Object Definition → Object Definition → Parking .
b. Locate the Code field of the object. Determine the value. The value is required in a
later step and will be case-sensitive when used.
c. Locate the association to Location Wrapper. Determine the Name. The value is
required in a later step and will be case-sensitive when used.
3. Enable custom-string4 and assign the parking GO in Job Information using BCUI.

Parking Field

a. Go to Business Configuration UI.

b. Go to Job Information element, add a custom string field. Follow the properties in the
table titled Parking Field.
c. Save the element.
d. If prompted to confirm other changes made to the data model by BCUI, choose Yes.
4. Permission the newly enabled field for parking to the Administrator Role.
a. Go to Manage Permission Roles → System Admin → Permission → Employee Central
Effective Dated Entities → Job Information .
b. Select ALL of the permissions for the Parking Field.
c. SelectDone → Save Changes .
d. Log out and log back in.
5. Test the association in employee records.
a. Go to Marcus Hoff’s profile and then go to Job Information → Edit .
b. Select Edit.
c. Select today’s date for the Start Date.
d. Change location to Arlington, Virginia.
e. Verify that you can see the associated parking record (Amidi Parking) in the Parking
field.
f. Cancel the changes.
Configuring the Succession Data Model XML

Succession Data Model XML

As valuable as the Business Configuration UI is to configure HRIS elements for Succession and
Country Specific Succession Data Models, the use of XML still has some advantages over BCUI.
These include:
● Using XML makes it easier to make simultaneous changes to a variety of global and country-
specific fields, while BCUI will often get an error
● Back-up versioning is available for every data model upload, while changes in BCUI cannot be
undone

Learn to configure the XML attributes in the interaction.

Succession Data Model XML

Any newly enabled fields in the data models or BCUI must be permissioned using Role Based
Permissions for any role to access it. In the sample configuration for ACE, the field Preferred Name
has permission at all levels: View Current, History, Edit/Insert, Correct, and Delete.

Exporting the Succession Data Model in the Admin Center

Before you start with any configuration using the Succession Data Model XML, be sure to download
the latest XML version. Files can be downloaded directly from the Admin Center. All previous versions
can be exported directly from the Export Succession Data Model tool. You can restore the data model
to a specific version from the list. The list of versions only stores up to 100 previous versions.
Supplemental Resources for this Lesson

Here are some additional resources you can explore relevant to this lesson (access requires S-ID):
● https://help.sap.com/viewer/b14dd15ca58f43e0856184a740a4b212/latest/en-US
● https://help.sap.com/viewer/213711b5e5a847e2a20dfdd465346252/latest/en-US
● https://help.sap.com/viewer/b05b0831c7a540739a2d19f01fbeadff/latest/en-US

Exercise: Configure the Succession Data Model using XML

Business Example

Ace Corp wants to make changes to the Job Information block in the Employee Files. They want
to enable and update the label of the Supervisor Level field. They also want to include a custom
field to store Additional Job Details.

If you need to create a custom field (string, date, and so on), you can reference the XML examples in
the Implementing Employee Central Core guide. If your custom field label does not appear correctly,
you can add a line for English US: <label xml:lang="en-US">Additional Job Details </label>.

Steps
1. Export the Succession Data Model.
a. Go to Export Succession Data Model using Action Search.
b. Select Export Succession Data Model.
c. Save the file with your other data models, rename the file to match the other files, and
increment the version number on your file.
2. Open the Succession Data Model.
a. Open the file in your XML editor.
b. (Optional) If you use an XML editor that validates versus a DTD, update row 4 to a
value of "sf-form.dtd".
3. Enable the Supervisor Level field and update the label to Management Level.
a. Go to HRIS Element → jobInfo .
b. Go to hris-field → supervisor-level .
c. Change the visibility to "both".
d. Change the label: Supervisor Level → Management Level.
e. If necessary, to change the en-US label, go toSupervisor Level → Management Level.
4. Create a custom field to store the Additional Job Details. Utilize custom-string8 hris-field.
a. Go to HRIS Element → jobInfo .
b. Add the following code block AFTER the closing tag of supervisor-level (</hris-
element>) and BEFORE the opening tag of is-cross-border-worker (<hris-field id="is-
cross-border-worker" visibility="both">):

<hris-field id="custom-string8" visibility="both">

<label>Additional Job Details</label>
</hris-field>

c. (Optional) Validate your XML if supported by your XML editor.

d. Save a new version of your data model.
5. (Optional) If you completed the Manage Succession Data Model with Manage Business
Configuration (BCUI) exercise, verify the change to personInfo exists in the exported data file.
a. Search for personInfo to locate the hris-element.
b. Scroll down to locate the hris-field attachment-id.
c. Verify the field has the label (Biographical Attachment) and is set to editable (visibility
= "both").
6. Upload the updated version of the Succession Data Model in Provisioning.
a. Log in to Provisioning.
 b. Go to Succession Management → Import/Export Data Model .
c. Browse for the file in the local drive and enter a description/comment for the new
version.
d. Select Submit.
7. Permission the fields that you enabled in the previous steps.
a. Log in to your instance.
b. Go to Manage Permission Roles → System Admin → Permission → Employee Central
Effective Date Entities → Job Information.
c. Find Additional Job Details and select all checkboxes.
d. Repeat prior steps for Management Level.
e. Select Done and Save Changes.
8. Test your changes.
a. Log in to your instance.
b. Go to Marcus Hoff → Employment Information .
c. Ensure that you can see your two changes:
■ Management Level
■ Additional Job Details

Configuring the country and region specific fields for

Succession Data Model

Country specific fields (CSF) Succession Data Model

The CSF Succession Data Model allows you to configure fields relevant to a specific country. For
example, you can format home address fields differently for each country or add custom fields for
selected countries. In the figure, Country Specific Fields (CSF) Succession Data Model, you can see
the Personal Address block for two countries. On the left is a block for the United States, and on the
right is a block for the Philippines. The different fields are made possible by the CSF Succession Data
Model.
The HRIS elements that support country-specific configuration are as follows:
● Global Information (globalInfo)
● Addresses (homeAddress)
● National ID Information (nationalIdCard)
● Job Information (jobInfo)
● Compensation Information (compInfo)
● Employment Information (employmentInfo)
The standard Country-Specific Succession Data Model used for implementation provides
preconfigured country-specific fields for more than 100 countries.

National ID in the CSF Succession Data Model

The National ID format group is preconfigured for countries in the standard Country Specific
Succession Data Model. The configuration in the data model dictates the behavior of the fields in the
user interface.
● Country Id: determines the country-relevant format and fields that will be displayed in the
system
● Format Id: indicates the national ID type for the country
● Regular expression: determines the acceptable data format

In the figure, National ID in the CSF Succession Data Model, you can see that the acceptable format
required for Social Security Number in the United States: three digits, a dash, two digits, a dash, and
four digits. This is different from the acceptable format for the French INSEE.

Home address in the CSF Succession Data Model

The Home address element is also preconfigured in the standard CSF Succession Data Model. In the
figure, Home Address in the CSF Succession Data Model, you can see the standard configuration for
the United Kingdom and Canada. The county field in GBR is set for picklist, COUNTY_GBR, while the
state field in CAN is set to display values from PROVINCE_CAN picklist.

Global information in the CSF Succession Data Model

Global information (globalInfo) is predelivered for most countries in the standard Country Specific
Succession Data Model. When configured, the fields in the Global Information element appear in the
same People Profile block as that of Personal Information (personalInfo).

In the sample configuration for ACE in the figure, you can see the globalInfo HRIS element for the
United States. The Ethnic Group and Veteran status fields are visible and have associated picklists.
Exercise: Configure global information in the CSF Succession Data
Model

Business Example

The Ace Corporation has expanded operations into Germany. They need to add two additional fields
to Germany's Global Info.

Consider which data model you will use. In the data model, which element do you configure? If you
create a custom field, how do you make it visible in the instance?

This exercise requires you to have completed Prepare the Data Models exercise.

Steps

1. Create custom fields to store Ethnicity and Religion for employees in Germany. These will be
displayed in the Global Information area of the Personal Information block.

a. Go to Manage Business Configuration.

b. Select the hris-element globalInfo.
c. Expand globalInfo with the triangle symbol.
d. Select globalInfo_DEU.
e. At the bottom of the field list, select the field identifier drop-down list.
f. Select custom-string1.
g. Add the label Ethnicity.
h. Set Enabled to Yes.
i. Select Details and check if visibility is set to Edit.
j. Repeat the steps to enable custom-string3 according to the table.
k. Save the element.
2. Permission the newly enabled fields for the System Admin to have full permissions.
a. Go to Manage Permission Roles.
b. Select System Admin.
c. Select Permissions → Employee Central Effective Dated Entities → Personal
Information
d. Find Ethnicity and Religion and select all the checkboxes.

The permission will be in the format "DEU—field name". For example DEU-Ethnicity.

e. Select Done → Save Changes .

Validate