Enabling the Unified Job Requisition Data Model for Recruiting

Objectives

After completing this lesson, you will be able to:
  • Summarize the functionality of the Unified Data Model for SAP SuccessFactors Recruiting
  • Convert to Unified Data Model Generic Objects
  • Configure job location fields in a job requisition template
  • Rebuild the job requisition search index

Unified Data Model for SAP SuccessFactors Recruiting

The Unified Data Model introduces job location objects and standard marketing brand objects for Recruiting. These objects are Recruiting-specific and have been built to support Career Site Builder features.

The new Location Generic Object is an extension to the location data stored in the SAP SuccessFactors suite. Previously, the Location Foundation Object was used to store location data in the job requisition. However, because the Location Foundation Object was built for HRIS-specific features, certain limitations prohibited the location data from being fully used in recruiting-specific features and scenarios.

The Job Location Generic Object now provides customers with the ability to host recruiting-specific location data which can be fully localized and improve the candidate search experience in Career Site Builder. The Job Location object also fully supports multi-location posting.

Though not required, the Job Location Generic Object can be mapped to the Location Foundation Object if the Location foundation data is needed for transitioning/hiring of candidates. This provides full flexibility in the creation and maintenance of recruiting-specific location data.

When configuring the Job Requisition, is important to understand whether a customer will be using any of the Career Site Builder features (home page search features, the Google Maps component, job page layouts, and/or category pages) so that their environment is enabled with the Unified Data Model.

Overview of the Unified Data Model Location Objects

The following objects are standard and can be found in the Configure Object Definitions admin tool:

  • Marketing Brand Generic Object (GO) 

    A standard Marketing Brand Generic Object is available in Configure Object Definitions; however, the brand data must still be configured in Manage Career Site Builder.

    To help existing customers transition from the Brand field they are currently using (custom object, picklist, etc), a new Brand Migration job is available in Admin CenterScheduled Job Manager.

  • Job Location Generic Object (GO)

    The Job Location GO (JobLocation) offers much more flexibility in creating Career Site Builder- friendly data for various locations in different countries. This new location object provides structured location data on the job requisition to facilitate new Career Site Builder search features, including a card view of search results, faceted search by using the Google Map component, and posting a job to multiple locations for candidates to find on the career site.

    Example for a job location in New York, USA is displayed.

    Considerations include:

    • The Job Location object can be mapped to the Location Foundation Object (but it is not required).
    • The Job Location object uses the new Job Location Long Format to format the location address data correctly for each individual country.
    • This location object fully supports multi-location posting. 
    • The Job Location object hosts the following fields within the object definition:

      Job Location Object: Field Definition

      FieldComment
      Location Code 
      Location Name 
      FO LocationThe Location Foundation Object can be mapped directly to the Location Generic Object.
      Job Location Long FormatAn address format for the location information of a country/region displayed for the job requisition when a candidate searches for or opens the job requisition. Note that only one Job Location Long Format is allowed for a country/region. If no address format is created, a default format is displayed as the location information of a posted job. Thus, a Job Location Long Format enables address representation per country/region format standards. The Job Location Long Format address is displayed in multiple lines as part of the job requisition details.
      Address 1 
      Address 2 
      Address 3 
      Address 4 
      Subdivision/Neighborhood 
      City 
      Metropolitan Area 
      County/Region 
      State/ProvinceThe State/Province field is associated with the State/Province Generic Object to have a parent-child relationship between county and state.
      Flexible/Sales regionThis field could be used to host something other than Sales Region, if the customer does not need it.
      ZIP/Postal Code 
      Location Search SynonymsSimilar names of the locations to search for jobs.
      LatitudeCareer Site Builder uses Latitude and Longitude coordinates from the Google Map component to display pinned locations of the jobs on a map.
      LongitudeCareer Site Builder uses Latitude and Longitude coordinates from the Google Map component to display pinned locations of the jobs on a map.
      Override CoordinatesSet the value to Yes to manually provide coordinates to show a specific and accurate location of the posted job on the map.
      Override Latitude 
      Override Longitude 
      Effective Start Date 
  • Job Location Long Format (GO)Example for job location long format is displayed.

    The Job Location Long Format controls the address formatting of the Job Location data for each country. The Long Format is considered the formal/standard address. Only one format is allowed per country. If you do not configure this object for each country, it defaults to the following address formatting:

    Code Snippet
    1234
    [address1]<br/> [address2]<br/> [city],[state_name][postal_code]<br/> [country_name]<br/>

  • Job Location Short Format (GO)

    The Job Location Short Format offers full control over how location data is displayed within the job posting on the Career Site. Due to local requirements or business needs, some regions may require specific location data to be displayed in the job posting.

    The Job Location Short Format can be selected for the Job Location(s) in the Job Requisition, allowing users to control which format should be used to display location data in the job posting for the individual requisition.

    For example, the following fields can be utilized in the Job Location Short Format to help improve job searches:

    • Job location synonyms (for example: Manhattan, Financial District, Bronx for NYC)
    • Flexible sales region (for example: New Jersey, Delaware, Connecticut for NYC)
    • Metropolitan Area/Market 
    • Manual configuration of location Latitude/Longitude for the Google Maps component in Career Site Builder

    You also can select any of the following attributes to display them as part of the Job Location Short Format:

    • State/Province (The State/Province field is associated with the State/Province Generic Object to have a parent-child relationship between county and state.)
    • Flexible/Sales Region
    • ZIP/Postal Code
    • Location Search Synonyms (Similar names of the locations to search for jobs.)
    • Latitude
    • Longitude
    • Override Coordinates
    • Override Latitude
    • Override Longitude

    For example, when posting jobs in New York City (NYC), if you want to display the neighborhood, you can configure the Job Location Short Format as follows:

    Example for job location short format is displayed.

    This is how it would appear in Career Site Builder’s search results:

    Search Results for jobs is displayed.
  • State/Province Generic Object (GO)

    The State/Province object stores the ISO country codes and state codes associated with them are configured in the Recruiting_Country_States.text file.

    The existing state/province data is migrated to the State/Province Generic object using the State Province Go Migration Job.

Convert Existing Brand Data for the Unified Data Model

The brand migration job will help the system convert any of the following fields and its data to the standard Marketing Brand GO:

  • Picklists
  • Text
  • Object

High-Level Steps

  1. Navigate to Scheduled Job Manager
  2. Click the Job Scheduler tabCreate Job Request
  3. Slect the job type: Migrate Brand to Marketing Brand on Job Requisition
  4. Once the job has been completed, review the details in Monitor Job to ensure nothing has failed.

Create Job Location Formatting Data

Create the Location Long Format Data

For each country you are posting/advertising jobs in, you will need to create one Job Location Long Format. If you do not configure the long format for a country, it will default to the following format:

Code Snippet
12345
[address1]<br/> [address1]<br/> [city],[state_name]{postal_code]<br/> [country_name]<br/>

High-Level Steps

  1. Navigate to Configure Object Definitions using Action Search
  2. Create a new Job Location Long Format Generic Object
  3. Update the following attribute values for a specified job location in Manage DataJob Location Long Format:
    1. externalCode
    2. name
    3. country
  4. Add the respective address formatting fields as desired.

    Note

    If working with many countries, it is recommended to use Import/Export Data functionality to create the object data in bulk.

Create the Job Location Short Format Object

When creating Job Location Short Formats, you will want to consider what job location data is needed for job postings. For example, if you wish to improve the candidate’s search experience within Career Site Builder, it is helpful to include fields within the short format such as "Location Search Synonyms".

You can create as many short formats as desired, for different countries. You can configure the Job Location Short Format Object field on the Job Requisition, allowing recruiting users to select which short format they wish to use. Otherwise, you can use business rules to auto-populate this field if there is some standard that should be followed.

High-Level Steps

  1. Navigate to Manage Data using Action Search
  2. Select Create NewJob Location Short Format
  3. Add the desired attribute values to be displayed when the job is posted.
  4. Use separators (commas, spaces, hyphens, new lines, semicolons, pipes, underscores, slashes, and colons) to distinguish the field attributes when the location data is displayed in the job posting.

Convert Existing Location Data to Create Job Locations

To create Job Location data, there are a few data migration jobs that can be leveraged. Once the location data is migrated, you can begin building Recruiting-specific job locations.

State Province GO Migration Job

This will automatically convert the existing state/province data in the system to the State/Province GO.

High-Level Steps

  1. Navigate to Scheduled Job Manager
  2. Click the Job Scheduler tabCreate Job Request
  3. Select Job Type as "State Province GO Migration Job"
  4. Once the job has been completed, review the details in Monitor Job to ensure nothing has failed 

Export Location Details of the Posted Job Requisitions 

This job is considered a helper tool, facilitating in the creation of Job Location GO data. This job exports all the Location FO data of posted Job Requisitions while converting it into Job Location GO friendly formatting.

To maximize the use of this job, we recommend creating and posting a job requisition in all locations which you would like data created for (either by creating a test requisition and posting it to all locations or ensuring use of existing job requisitions that are posted).

High-Level Steps

  1. Navigate to Scheduled Job Manager
  2. Click the Job Scheduler tabCreate Job Request
  3. Select the Job Type as "Export Location Details of the Posted Job Requisitions to Create Job Location Generic Object Data".
  4. Once the job has been completed, view the details under Monitor Job and download the results.

    Note

    If you wish to create this data from the existing Location FO data, you may do so as well. You will need to first export all the Location FO data. Then, export the Job Location template from Import/Export Data. Complete the information within the Job Location .CSV as necessary to prepare for the next step.

Create Job Location GO Data

Lastly, the Job Location data must be created. If you are starting from the Export Location Details of Posted Job Requisitions file, you will need to review the data created and make any necessary changes to the location data. The following fields will auto-populate from the export job:

  • External Code
  • Location name
  • City
  • State/Province
  • Country
  • Postal/Zip Code
  • Effective Start Date
  • Status

The remaining fields that you wish to use for the Short Location Format, as well as the mapping to the Location FO, must be done manually (through the .CSV file, or through Manage Data tool after the import).

High-Level Steps

  1. Navigate to Import Export Data using Action Search
  2. Select the Import action
  3. Select the Job Location Generic Object and select the appropriate .CSV file. 
  4. Click Import
  5. To monitor the status of the job, you can use the View Results button once you have completed the import.

Job Location Fields in Job Requisition Template

The following object fields should be added to the Job Requisition template(s). Based on the requirements, these fields can be manually populated by the recruiting users or business rules can be leveraged to auto-populate the values as needed.

Note

Remember to permission the fields as necessary within the Job Requisition template(s).

sfstd_jobLocation_obj

Field Type = Object

Configure the sfstd_jobLocation_obj as the standard Field-ID and configure the Field Label (as desired) and use the following Object Type: JobLocation in the job requisition XML template. This field can be configured as a multi-select field, if necessary.

Field Definition

Code Snippet
123456789
<field-definition id="sfstd_jobLocation_obj " type="object" required="false" custom="false" object-type="JobLocation"> <field-label><![CDATA[Job Location]]></field-label> <field-label lang="en_US"><![CDATA[Job Location]]></field-label> <field-description><![CDATA[]]></field-description> <field-description lang="en_US"><![CDATA[Location data used for Career Site Builder]]></field- description> </field-definition>

sfstd_jobLocationShortFormat_obj

Field Type = Object

Configure the sfstd_jobLocationShortFormat_obj as the standard Field-ID and configure the Field Label (as desired) and Object Type as JobLocationShortFormat with Multiselect field set to False in a job requisition XML template.

Field Definition

Code Snippet
12345678
<field-definition id="sfstd_jobLocationShortFormat_obj " type="object" required="false" custom="false" object-type="JobLocationShortFormat"> <field-label><![CDATA[Location Formatting]]></field-label> <field-label lang="en_US"><![CDATA[Location Formatting]]></field-label> <field-description><![CDATA[]]></field-description> <field-description lang="en_US"><![CDATA[]]></field-description> </field-definition>

Job Requisition Search Index

Run the ReBuild Job Requisition Search Index job in Scheduled Job Manager to index the migrated data in the database before Career Site Builder consumes it. If you make changes to the job requisition, ensure to reindex it again to store the data.

Verify the Unifyconfiguration MDF Object to view the status of all the migration processes required to reindex the job requisitions available on your instance.

Check the Unifyconfiguration MDF Object to see the status of all migration processes needed to reindex the job requisitions in your instance.

When the instance is ready for the Unified Data Model switch to be enabled, you will see the object as depicted in Figure: UnifyConfiguration.

Log in to track your progress & complete quizzes