Employee Central - Data Models

Employee Central is global core HR solution and foundation for all of the other modules in the BizX Suites. 

EC provides support for any combination of business units, geos or cost centers to model and manage any workforce and as a pure cloud-based solution, provides access to near real-time updates from nearly any internet connection.

Corporate Data Model:

• Defines Foundation Objects
• Configures the relationships amongst Foundation Objects

Country Specific Corporate Data Model:

• Defines Foundation Object fields for a specific country
• If a country is not defined, then system will use the configuration from the corporate data model. 

Succession Data Model:

• Configures the fields that appear on the Employee’s Personal and Employment Information.

Country Specific Succession Data Model:

• Configures country specific fields that appear on the Employee’s Personal and Employment Information.
• Sets international standards like address format and national ID format
• If a country is not defined, then system will use the configuration from the succession data model.

HRIS Propagation Data Model:

• Defines how the system prepopulates data from the foundation tables into the employee record.

Workflow Rules Data Model: 

• It 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

Event Derivation Rules Data Model:

• It specifies what data changes should trigger a specific event reason
• It allows changes to be recorded and categorized

Employee Central Objects: 
 EC objects are classified in to the following three categories

• Foundation Objects
• Employee Data (HR Data) Objects
• MDF Objects or Generic Objects

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:

 

A Legal Entity cannot have a parent of the same type. A Division can belong to multiple Business Units and a Department can belong to multiple Divisions. In addition, both a Division and Department can have a parent of the same type, thus creating a hierarchy of these object types.

 We can compare the objects in this structure to SAP object types or fields:

Foundation Object	SAP ERP HCM equivalent
Legal Entity	Company Code
Business Unit	Business Area / Organizational Unit (Object type O)
Division	Organizational Unit (Object type O)
Department	Organizational Unit (Object type O)
Location	Personnel Area / Personnel Subarea
Cost Center	Cost Center (Object type K)

Associations between Foundation Objects (including Generic Objects)

Associations are relationships between objects that define the hierarchical relationship and filters for these objects. In essence, 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.