Data Models In SuccessFactors Employee Central

Data Models:

 

 

Data models are used to set up as per the company's requirements.

We can define how a company's organizational structure is reflected in the system and what entries a user can make to set up company, person, and employment data.

We can add customer-specific fields and rename fields with the customer specific Labels.

Data Model is all about XML file. XML file contains objects and within the objects we can see different kind of fields.

In SAP SuccessFactors Employee Central (EC) we have 7 Data Models.

List of 7 Data Models:

👉Succession Data Model

👉Country Specific Succession Data Model

👉Corporate Data Model

👉Country Specific Corporate Data Model

👉HRIS Propagation Data Model

👉Event Derivation Rules Data Model &

👉Workflow Rules Data Model

These 7 data models data can access through the ESS and MSS Functionality.

What is ESS and MSS Functionalities?

ESS: Employee Self Service: is a web enabled tool used to update their own data by the employee itself. Allows employees to create, display, and change their own data in the company's intranet.

MSS: Managers Self Service: is a web enabled tool used for Managers to take report or update the data of subordinate. It is designed for the people who carry out management tasks.

For Example: Both Functionalities

ESS: Employee Self Service	MSS: Managers Self Service
Working Time Career and Job Employee Search Personal Data Benefits and Payment Travel Management Corporate Information Life, Work Events & Training Qualifications & Appraisals	Line managers Team leaders with project management tasks Department heads Tasks related to the personnel responsibility for their team Controlling tasks within their budgeting. Planning tasks Project management tasks & Staffing

The data type where users can access and cannot access will be defined in the Role Based Permissions (RBP).

Set the visibility of a field in the instance.

Define Custom labels and fields.

Define relationships among st Foundation Objects (FO).

Set the order of fields that appear in the instance.

Set a picklist for a field.

Define relationships between FO & Employee Files.

Set rules to trigger Events, Event Reasons, and workflows.

What is the purpose of the 7 Data Models?

The above 7 data models in the Employee Central play a critical role in configuration.

1 Corporate Data Model:

The Corporate Data Model (XML File) is the first data model to be configured for Employee Central. This Data Model (XML) helps to set up the Company's structure.

2.Country Specific Corporate Data Model:

This Data Model (XML) File helps to set up the foundation Object fields for a Specific country. If Country is not defined/System will use the configuration from the Corporate Data Model

This helps to define some foundation Objects like:

	Foundation Objects
Organization Structure	Job Structure	Pay Structure
Legal Entity (MDF) Business units (MDF) Division (MDF) Department (MDF) Location Location Group Geo Zone (MDF) Cost Center (MDF)	Job Function (MDF) Job Classification (MDF)	Pay Group Pay Range Pay Grade Pay Component Frequency (MDF)

 

If we observe the above screenshot under the category’s organization, Pay and Job we can see MDF objects. Earlier these MDF objects are a part of foundation Object but later they moved to MDF (Non-XML work).

3. Succession Data Model: (Represents to the HR Data)

The Succession Data Model controls the Employee Record. The Employee Record is divided in two main areas:

Employment

Personal Information

Employment: Employment information carry a record of the employee at work: For Example:  his/her Job information, Compensation Information etc.

Personal Information: Personal Information carry a record of the employee outside of work: For Example: Home Address, National ID, or Contact Information.

4. Country Specific Succession Data Model:

Sets International Standards like Address format and National ID Format.

Configure Country Specific Fields that appear on the Employee’s Personal and Employment Information

If a country is not defined, then system will use the configuration from the Succession Data Model.

5. Propagation Data Model:

In Corporate Data Model the foundation table values populate in the succession data model in Employment Information.

6. Events & Events Derivation Rules Data Model:

In SF we cannot create any custom events we have to use the standard events which are available. In SF there are 25 events which are pre-defined.

Event (Actions)	Event Reasons
Hire to Retire Promotions Transfers Increments Terminations	Why hiring an employee Business Expansion Replacement Death Retirement

 

For any custom events, SF provided to change the existing event label and we can use, but intent remains same.

Actions taken in the Employment Profile are based on the client requirement.

7. Workflow Rules Data Model:

Specifies what data changes should trigger a specific workflow. Workflow is a series of employees that review the workflow. You can configure the employees in a workflow via admin tools.

In SAP Terminology the workflows are called as Approvals. Workflow defines business rules and end number of approvals.

Organization Structure

In the standard-delivered configuration the organization structure is composed of the following MDF Objects (Migrated from Foundation to MDF):

👉Legal Entity

👉Business Unit

👉Division

👉Department

👉Cost Center

The diagram below illustrates the “top” 4 objects in the structure, with the standard-delivered Associations between objects:

Associations between Foundation Objects (including Generic Objects)

Associations are relationships between objects that define the hierarchical relationship and filters for these objects. They define the parent-child relationship and whether a child relationship must exist for a parent object. In addition, they are used to filter object lists. An Association must have a multiplicity defined, which is either One-to-One or One-to-Many:

👉One-to-One: Defines that the object can only be associated to one other object

👉One-to-Many: Defines that the object can be associated to multiple objects

In the diagram above we can see several associations. Departments are associated to Divisions, while Divisions are associated to Business Units, and Business Units are associated to Legal Entities. Business Units, Divisions, and Departments can have parents of the same type.

Data Model is an XML file and XML file is always modified based upon the guidance from DTD file. DTD is going to guide which xml tags we can add and cannot add. It gives the message whether is it appropriate or not.

Above screenshot gives the information on Data Model Vs DTD files available.

If we can observe the above screenshot, Country Specific Corporate data model and country specific succession data model both the data models are guided by one DTD.

Event Derivation Rules Data Model and Workflow rules data models, we don’t have specific DTD, but what we are going to have is, whatever we made the statement or modified xml is right or wrong validation or review will be happened by the reference DTD called rulesset.dt.