Introducing Employee Data

The Succession and Country-Specific Succession Data Models must be uploaded initially during implementation before the BCUI can be used.

The following permissions are required to use the Manage Business Configuration tool:

• Manage Business Configuration
• Metadata Framework

The Business Configuration UI has several sections. For managing HR data structure, most of the configurations will likely be in the Employee Central→HRIS Elements section. Refer to the image below and its description to know more about each section:

1. Employee Central: Here, you’ll find the HRIS elements and country-specific elements included in the Data Models. HRIS elements are reflected as blocks in People Profile.
2. Employee Profile: Here, you’ll find standard elements and userInfo elements that are used for the talent modules.
3. Filters: Here, you can create a dynamic group filter that can be used as criteria for creation permission groups.
4. Take Action: This is where you can initiate the edit mode.
5. Set the Label and Default label of the HRIS element.
6. Enable or disable the element.
7. Set the field label.
8. Enable/disable or set other field properties.
9. Assign business rules to the element.

The Employee Central section displays all standard person and employment data structure.

The system has built-in validations and warns users when certain actions are not allowed. You can also use the Check Tool to validate and identify configuration issues in BCUI and take corrective action.

BCUI doesn’t have an undo feature. Changes made via Business Configuration UI update the Succession and Country-Specific Succession Data Model. At the same time, importing the data models triggers the Synchronize Business Configuration job.

As an administrator, you can manage and monitor the Synchronize Business Configuration job using the Scheduled Job Manager in the Admin Center.

For more information related to Business Configuration, please check out the related Implementing and Managing Business Configuration guide in the SAP Help Portal: http://help.sap.com/cloud4hr

Several SAP SuccessFactors applications utilize User Data Tables from the Employee Profile section instead of the HRIS Elements of Employee Central. As Employee Central is the core HR system of record for SAP SuccessFactors, it is vital to ensure employee data used by other talent solutions are accurate and consistent with the data stored in Employee Central.

Human Resource Information System (HRIS) Sync is the data synchronization from Employee Central to User Data Tables. HRIS Sync is a one-way (unidirectional) sync of EC data to populate the talent data to support the other modules of SAP SuccessFactors. Several HRIS fields are, by design, hard-coded to synchronize to standard user data fields.

Using the BCUI, you can define additional HRIS Sync mappings for standard elements, user info elements, and user info record key elements. With these mappings, you can establish a relationship between these elements and HRIS fields. You can define mappings for both standard and custom HRIS fields.

The HRIS Sync Mappings section in Business Configuration UI allows you to add/edit and delete field mappings. Any changes made to this section will reflect in the HRIS field mapping at the element level.

To learn more about HRIS Sync Mappings, visit the Configure Employee Central Core course.

Business Configuration UI allows you to add new filters that can be used when defining permission groups. The Dynamic Group Filter (DG-Filter) in BCUI makes it a lot easier when you want to add Employee Central fields to the standard criteria used for creating permission groups.

Here are the high-level steps for adding a DG-filter:

1. Go to Filters→Dynamic Group Filters→DG Filters.
2. Select Details.
3. Select the HRIS element that you would like to reference.
4. Select Details and the HRIS field that you want to use as a category. Make sure the HRIS field is enabled and visible.
5. Select Save. You may need to log out and log back in before the field is visible as a category in Manage Permission Groups.

The National ID Card (nationalIdCard) is a non-effective-dated HRIS element that stores country-specific identification. The National ID element allows for the tracking of changes over time. The valid-from, valid-to, and record-id fields can be used so that multiple National ID records can be stored for a person, each with it's own time period.

The Addresses (homeAddress) is an effective-dated HRIS element that stores country-specific address information.

Personal (personalInfo) stores basic demographic information, and Global Information (globalInfo) stores country-specific demographic data. Although configured separately as HRIS elements, it is displayed in the same block. Both are effective-dated.

Person Information (personInfo) is also a non-effective-dated HRIS element that stores biographical information.

Work Permit (workPermitInfo) is a non-effective-dated HRIS element that stores work eligibility documents such as passports or visa information.

Email (emailInfo), Phone (phoneInfo), and Social Accounts (imInfo) are non-effective-dated HRIS elements that store contact details. Although configured separately, it is displayed in the same block.

Emergency Contacts (emergencyContactPrimary) is a non-effective-dated HRIS element that stores emergency contact details.

Dependents (personRelationshipInfo) is an effective-dated HRIS element that stores dependent information.

Job Information (jobInfo) is an effective-dated HRIS element that stores job-related information. Job Info supports country-specific fields. Although configured in a single HRIS element, this is displayed in two blocks: Job Information and Organization Information.

Job Relationships (jobRelationsInfo) is an effective-dated HRIS element that stores other hierarchical and non-hierarchical job relationships of employees.

Employment Details (employmentInfo) is a non-effective-dated HRIS element that stores hiring and termination data. This element supports country-specific fields.

Compensation Information (compInfo) is an effective-dated HRIS element that stores compensation-related data. It supports country-specific field configuration. Pay Component Recurring (payComponentRecurring) stores recurring pay components assigned to employees. Although configured separately, both are displayed in the same block.

Non-Recurring Pay Component (payComponentNonrecurring) is a non-effective dated HRIS element that stores one-time or spot payments.