3476633 - Unified Data Model - New and existing Location objects

What are the new location Generic Objects available since release 2H2023?
Why should these be used when Unified Data Model is enabled?
Which locations objects should be leveraged for location posting in Recruiting?
Which fields should be populated in the new Job Location objects?
What happens to the previously used EC Location Foundation Object and data?
Should the RMK field mapping be changed once UDM is enabled?

SAP SuccessFactors Recruiting

What are the new location Generic Objects available since release 2H2023?
With the advent of the Unified Data Model, new Job Location Generic Objects were created to cater for the job location needs of Recruiting.
These objects are : Job location, Job Location Long Format, Job Location Short Format

Job location
This new standard field (sfstd_jobLocation_obj) should be added to the templates to be selected in the requisitions for the location data to be consumed by UDM.
The object should be populated with the locations which will be used for job posting in Recruiting.

Job Location Long Format
An address format for the location information setup per country/region. This address is displayed in multiple lines as part of the job requisition details.
There can only be one per country.

Job Location Short Format
This represents a short address format suitable for placement in the search result sets beneath the job title on the career site.
Note that the job location short format isn’t associated with a country, and you can create many Job Location Short Format addresses to visualize them on the job cards.

Why should these GOs be used when Unified Data Model is enabled?
The main features offered by UDM rely on the structured location data contained in the new location objects. Some examples are:
> Address section card view of search results leverages Job Location Short Format
> The Integrated Google map relies on the address coordinates (latitude and longitude) for job placement 
UDM does not consume FO location data for these features so the New Location Objects must be configured for this information to come through.  

Which locations objects should be leveraged for location posting in Recruiting?
If UDM is implemented then the new Location objects should be used.
If UDM is not implemented then the existing Location Foundation Object can continue to be used as before.

Which fields should be populated in the new Job Location objects?
The new location objects provide more location information than previously possible. It is up to the customer how much data they want to include but of course, the more the better as this then means more options to play with on the CSB side and better search options for potential candidates.
One should keep in mind the following though:
Map Coordinates (latitude and longitude) are automatically calculated based on the provided data so the more data the more accurate the location.
At the moment the Integrated Google map requires a street address for job placing.
As to required fields these are marked as such with the usual star.

What happens to the previously used EC Location Foundation Objects and the data they contain once UDM is enabled?
Enabling UDM does not in itself have any effect on the FO location object data.
For the purposes of Location posting in Recruiting, once the new GOs are configured and used in the requisitions, the old FO location data becomes redundant since the new GOs can contain the same data (City, Country, State and Postcode) plus much more.
The FOs should continue to be used in parallel for other processes than job location posting.

Should the RMK field mapping be changed once UDM is enabled?
UDM does not use the RMK field mapping. The data is retrieved via an API from RCM directly. The mapping is only relevant if leveraging Advanced Analytics and/or RMK feeds as these still use the current integration and job sync.
For the consistency of location data across the Career Site, job distribution and Advanced Analytics ensure you map the Job Location Generic Object to City, Country/Region, State, and Pincode/Zip Code fields.

UDM, Unify , KBA , LOD-SF-RCM-JOB , Job Postings & Requisitions , LOD-SF-RMK-INT , Int with RCM, Data Mapping, AwLi, Multilocation posting , How To