JobLocation Migration: Seamless Transition to Unif...

svishwas · ‎2025 May 02

We are excited to introduce capabilities in SAP SuccessFactors Recruiting that simplifies the adoption of the JobLocation object on the job requisition. The JobLocation Migration Admin Tool allows admins to map and migrate legacy location data on job requisitions to the new Job Location object. We have also introduced a new business rule function to achieve the migration using business rules.

Why this enhancement matters:

With the Unified Data Model (UDM), the JobLocation object provides a structured way to manage job locations across requisitions, enhancing reporting, filtering, and search-ability for candidates. However, many customers have historically stored location data in custom or legacy fields on job requisitions, making it challenging to transition to the new model.

This enhancement solves this challenge by providing a structured, automated, and admin-friendly approach to migrating location data, making it easier to enable the Unified Data Model (UDM) and optimize your career site built with Career Site Builder

Note: If you are a customer using Career Site Builder for building your public career sites, this enhancement will help you transition easily to UDM. If you are a customer who is not yet using the Career Site Builder capabilities, this enhancement will still help you prepare your data to transition to CSB and UDM. The JobLocation object also acts as a standard way to represent Job Location data in your system. So regardless of your configuration, using the Migration tool helps you maintain and use job Location data in an efficient way

How the Migration works:

We offer two approaches for transitioning to the JobLocation object, providing flexibility based on customer needs:

1. JobLocation Migration Tool (Admin UI) – “Admin Center/ Set Up Job Location Mapping and Initiate Migration”

This tool provides an Admin Page where system administrators can:

Review and/or configure mappings between job location fields on the job requisition and the JobLocation object for relevant Job Requisition templates.

If you are a customer already using Recruiting Marketing for career sites, we default the mapping from Admin Center. Review and update the mapping as necessary
Map Country, State, City, ZIP/PostalCode fields; Mapping ‘Country’ field is mandatory

Run the JobLocation migration on all open requisitions.
Choose whether to migrate location data for closed job requisitions.
Execute a migration to mass-migrate legacy location data on job requisitions created from mapped templates. A scheduled job runs the migration logic.
Review and validate results using the ‘Scheduled Job Manager’ in Admin Center. Additionally, you can generate reports (People Analytics or Ad Hoc reports) on job requisitions and their JobLocation data to validate the migration.

NOTE: Access to the admin page can be controlled using an RBP Permission.

2. Business Rule Function: get Job Location ()

Use the new rule function "get Job Location ()" within Job Requisition business rules to facilitate the migration of Job Location data.

Use business rules to update JobLocation for newly created job requisitions after the mass migration process to all new job requisitions use the structured JobLocation format moving forward. Business rules can also be applied to update job requisitions individually or in groups based on specific criteria.

Review and/or configure mappings between legacy location fields and the JobLocation object for relevant Job Requisition templates.
- If you are a customer already using Recruiting Marketing for career sites, we default the mapping from Admin Center. Review and update the mapping as necessary.
For mapped templates, configure the rule function within a business rule to set the JobLocation object field on the job requisition.
- When the business rule runs as an OnChange or OnSave rule, it fetches and assigns the relevant JobLocation to the JobLocation field based on the mapping and job location data on the requisition.

Supported Data Type Combinations:

As a customer, you may have used standard requisition fields, custom fields, or a mix of different field types to store job location data on job requisitions. The Job Location Migration process supports various field types to ensure that most location data can be automatically migrated. However, if your data does not align with the supported field types listed below, the migration may result in incomplete or incorrect data on the requisition.

The following job requisition field/field-types are supported for migration:

Derived fields

Country

StateProvince

Text/Picklist fields

City

PostalCode

Facility

Filter fields 1-15

Mfields 1-15

ENUM fields

Department

Location

Division

Standard Object fields

Location_Obj (single select and multi select)

LEGAL_ENTITY_OBJ

BUSINESS_UNIT_OBJ

DEPARTMENT_OBJ

DIVISION_OBJ

COST_CENTER_OBJ

Position_obj (single select and multi select. Only primary value will be migrated)

Custom fields

text

picklist

ENUM

Object

NOTE:

For multiselect picklists and objects (except location_obj), only the primary value is considered during migration.
If location_obj contains multiple values, all values are considered in the migration process.

To ensure a smooth migration, avoid selecting Boolean fields in the mapping tool, as they are not supported in the migration process.

JobLocation migration process using the Admin page:

When you initiate migration from the admin page, a scheduled job runs and makes the following changes for each mapped template:

For each mapped template, the system automatically adds and assigns permissions to the standard JobLocation field if it is not already present.
For every Open and Closed requisition, based on the user's selected criteria and mapping:
The system retrieves data from the mapped fields in the job requisition.
It searches the Job Location object for an existing location with attributes that exactly match the requisition data.
If a matching JobLocation is found, it is assigned to the standard JobLocation field on the requisition.
If no match is found, a new JobLocation is created with the relevant attributes and assigned to the requisition.

Note: When migrating JobLocation data using the business rule function, a new JobLocation object is not created. If no matching JobLocation is found, the requisition will not be assigned a JobLocation.

Reviewing results of migration:

When you trigger the migration using the Admin tool, you can check the results of the scheduled job at “Admin Center -> Scheduled Job Manager” under Job type = “Migrate Job Location Data for Job Requisitions”.

monitor job.jpg

Job Details also contains an excel file attachment that prints out results of migration for each Job Requisition that is being processed. Admin users triggering the job will receive an email with Job run details:

Furthermore, you can use table or story reports to generate a report on Job Locations assigned to a Job requisition.

Example of table report:

report real.jpg

JobLocation migration example scenarios:

Consider that the job requisition has the following field types in the example scenario:

City – Standard text field

State/Province – Standard derived field

Country – Standard derived field

Pin/Zip Code – Standard text field

Scenario	If existing job location data on the Job Requisition is..	And the following fields from the requisition template are mapped for the template in the admin page….	And, the jobLocation object available in your instance is	Then, the jobLocation that is assigned to the requisition is….	More details	How can you avoid errors
All criteria satisfied					Based on the fields mapped and existing data on the job requisition, an exactly matching JobLocation was found and assigned to the requisition.	N/A
Relevant fields are not mapped				Using admin tool: Since an exactly matching jobLocation object is not available in the instance, a new jobLocation will be created and assigned to the requisition. Using business rule: Since an exactly matching JobLocation object is not available, no value will be assigned to the job requisition	Zip/PostalCode field is not mapped in the mapping tool. Hence the tool tries to find a JobLocation which does not contain a value for Zip/PostalCode. Since it could not be found, a new matching jobLocation is created	By mapping all relevant fields, that contain data on the job requisition. In this case, Zip/PostalCode
Relevant values are not maintained on the job requisition				Using Admin tool: Since an exactly matching JobLocation object is not available in the instance, a new JobLocation will be created and assigned to the requisition Using business rule: Since an exactly matching JobLocation object is not available, no value will be assigned to the job requisition	Although the ‘State’ field is mapped on the Admin tool, the requisition does not contain a value for ‘State’. Thus, a new matching JobLocation is created and assigned.	Not having value for ‘State’ on a job requisition, is a valid use case. If you are only using business rules for data migration, ensure jobLocation object which contains only Country-City-Zip/PostalCode, is available in the instance.
Job requisition does not contain ‘Country’ value				NULL	Although relevant fields are mapped in the admin page, the Job Requisition does not contain a value for ‘Country’. Hence migration will not be processed	Ensure every job requisition has value selected for ‘Country’ field
‘Country/Region’ is not mapped on the admin page				NULL	Country field is not mapped on the admin page. Hence the migration will not be processed	Ensure that the ‘Country/Region’ field is mapped for every template, which needs a data migration

For more details, review our Product Documentation here:

Preparing Recruiting Data for the Unified Data Model

GetJoblocation() rule function

SAP SuccessFactors Recruiting