Scribd
Upload
21 views6 pages

Partial Imports

The document outlines various data import methods in Employee Central, including Partial Imports for updating specific fields without overwriting others, and the ability to delete employee data through Incremental Load. It also describes the Manage Mass Changes tool for applying simultaneous job information updates to multiple employees, and the Business Configuration User Interface (BCUI) for managing the Succession Data Model. Additionally, it covers the configuration of person types and dynamic group filters within BCUI.

Uploaded by

fati
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
21 views6 pages

Partial Imports

The document outlines various data import methods in Employee Central, including Partial Imports for updating specific fields without overwriting others, and the ability to delete employee data through Incremental Load. It also describes the Manage Mass Changes tool for applying simultaneous job information updates to multiple employees, and the Business Configuration User Interface (BCUI) for managing the Succession Data Model. Additionally, it covers the configuration of person types and dynamic group filters within BCUI.

Uploaded by

fati
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Partial imports

Update Specific Fields via Import

So far, you've learned about two importing modes, Full Purge and Incremental Load. When you want
to update specific fields but retain others selectively, you can use Partial Imports. A Partial Import is an
incremental import that uses &&NO_OVERWRITE&& against fields you do not want to update.
Fields for the business keys and fields marked with &&NO_OVERWRITE&& will NOT be changed.
While importing data, if the system encounters a field without any value, the system will add either
&&NO_OVERWRITE&&, or null value depending on whether the entity supports partial import or not.

Unsupported Entities for Partial Imports

If you want to perform a Partial Import while importing data in Incremental Load mode, you cannot
update information for these objects:
● Address
● Work Permit Info
● Job relationships
● Dynamic Role
● Workflow

Delete Employee Data via Import

Employee data can be deleted in Incremental Load by choosing an operation type between DELETE
and DELIMIT. The operation type depends on the entity you are importing. Use DELETE for
Compensation Information, Job History, and Personal Information. Use DELIMIT for other entities.

Applying mass changes to job information in Admin


Centre

Mass changes
In Employee Central, the Manage Mass Changes tool allows an administrator to simultaneously apply
changes to Job Information or Job Relationships to multiple employees. Examples of mass changes
include changing office locations, corporate restructuring, or assigning a new manager to a group of
employees as part of an organizational change. For example, if you need to assign a new HR
representative to Carla Grant’s sales department, use the Manage Mass Changes tool to make the
process more efficient.

How To Set Up a Mass Change

Go to Manage Mass Changes . The steps for setting up a mass change job are as follows:
1. Provide a name for the job.
2. Create a group for the impacted employees. The interface and criteria are similar to that of the
role-based permission group.
3. Enter the Effective date of the change.
4. Select whether the change is for Job Information or Job Relationship.
5. Choose the appropriate field from the Job Information or Job Relationship.
6. Enter the value for the field.
7. Select the appropriate Event Reason (applies to Job Information only).
8. Select Save and Initiate to run the job. Alternatively, use Save if you do not want to execute
the job immediately.

Configuring the Succession Data Model with business


configuration

Succession Data Model

The XML data models defining Employee Data configuration are Succession Data Model and CSF
Succession Data Model. In the Succession Data Model figure, you can see the different elements
included in the Succession Data Model. In this lesson, you will learn how to configure the HRIS
elements of the Succession Data Model using the Business Configuration User Interface.

Management of the Business Configuration tool

Manage Business Configuration Tool

The Business Configuration UI (BCUI) allows consultants and administrators to update the Succession
Data Model and Country Specific Succession Data Model without XML intervention. The Succession
and Country-Specific Succession Data Models must be uploaded initially during implementation before
the BCUI can be used.

BCUI does not have an undo feature, nor does it create a backup version of the data models when
changes are made.

Using Manage Business Configuration Tool


Configurations in BCUI:
1. Employee Central: Here, you’ll find the HRIS elements and country-specific elements included
in the Data Models.
2. Employee Profile: Here, you’ll find standard elements and userInfo elements that are used for
the talent modules.
3. Set the label and Default label of the HRIS element.
4. Enable or disable the element.
5. Assign business rules to the element.
6. Set the field label.
7. Enable or disable the field.
Field details are used to set field attributes such as field type, required, etc.

Person Types in BCUI


The Person Type in BCUI allows you to define a set of fields specific to a group of persons, like a
contingent worker. Administrators can define person types for both global and country-specific HRIS
elements.

For a person type, you can configure these attributes:


● Enabled
● Mandatory
● Visibility

When a person type is created, all the HRIS fields specific to the Person Type get copied from the
base element. Person Type is only supported for HRIS elements.

You cannot add a field that is not in the base element.

You can only add the Person Type in BCUI. Person Type added in BCUI will not have any
corresponding entry in the data model, and you cannot configure the Person Type by editing the XML.

With BCUI, you can add different Person Types for other blocks. Not all Person Types are supported
in all elements. Some Person Types are only enabled in the BCUI when their respective modules are
enabled in Provisioning. The following Person Types might be available in your instance, depending
on configuration:
● Employee
● Dependent (Dependents Management required)
● Student (SAP SuccessFactors Learning module required)
● Candidate (SAP SuccessFactors Recruiting module required)
● Onboardee
● Contingent Worker

For more detailed information, including a matrix of supported person types and elements, review the
Setting Up and Using Business Configuration UI documentation in the SAP Help Portal.

How to Add Dynamic Group Filters


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 like to add
Employee Central Fields to the People Pool category. To create a new dg-filter, follow these steps:
1. Go to Manage Business Configuration UI using Action Search.
2. Go to Filters → Dynamic Group Filters → DG Filters.
3. Select Details in the first row.
4. Select the HRIS Element that you would like to reference.
5. Select Details and the HRIS Field that you want to use as a category. Make sure the HRIS
field is enabled and visible.
6. Select Save. You may need to log out and log back in before the field is visible in the People
Pool category.

Exercise: Manage Succession Data Model with Manage Business Configuration (BCUI)

Business Example

ACE would like to be able to start an attachment within the Biographical Information block on the

You might also like