SAP Knowledge Base Article - Public

2305869 - Job Location Best Practices - Recruiting Marketing


This article explains the best practices about Job Locations for Recruiting Marketing jobs.


SucessFactors Recruiting Marketing (RMK) - All Versions

Reproducing the Issue



Location is an important part of promoting and marketing your jobs, and is critical to job searches.

The RMK platform requires each job to have a single or Multiple specific locations. Job seekers, search engines, aggregators, social media sites, and job boards all utilize location as a core component of their search.

A job with a single or Multiple, city-specific location is a key differentiator in promoting and marketing your jobs to potential candidates.

Jobs that do not contain this will display the location as it is listed in the applicant tracking system. This may cause the job to display incorrectly on a map, exclude the job from search results, and potentially not be distributed to search engines, job aggregators, and other distribution systems.

The preferred, standardized location format is for example:

  • Minneapolis, MN, 55111, US, - This is the strongly preferred format for United States jobs but also international jobs and allows for easy, functional mapping.

Some examples of poor location formats:

  • South Campus, Rochester, USA - "South Campus" is not a real location, it is instead the name of a corporate location. This cannot map, as there is no geographical location to map the "South Campus" to.
  • Dallas/Fort Worth, TX, US - This is two locations in one. RMK can only map to a single location, and it cannot "select" one of the two locations to map to.
  • Multiple Locations, Virtual - While this is helpful to a candidate to see that this job is located in Multiple Locations, we cannot map this to a single map point, and as a result, it will not work.
  • APAC-India-Technical Development Group - This location is not specific enough for us to map to.
  • Remote Office [MA, MN, WA, CA] – Regional - This is not a location for us to map to - it references a non-location "Remote Office", multiple states, and a broad regional area. For this case, the best would be to reach out to your Implementation Partner or SAP Professional Services to discuss on what would be the best option as it might depend on your business processes. What can be done is to use in the job requisition location the location of the office that requisition will be responding to.


For instances that uses RCM integrated to RMK: When using Legacy picklists, RCM does not send the ISO Code to RMK (e.g. US), it sends the picklist label (e.g. United States). For those cases, we recommend implementing the Multi-Location feature, otherwise you will need to use ISO codes on the picklist labels.

See Also

2652937 - Multi-location Job Posting Feature - Recruiting Management

2688516 - Multi-Location Job Posting – RCM and RMK integration

3086891 Hiring for Remote Positions: Leading Practices in SAP SuccessFactors Recruiting


Job Location, Map, Location format, Recruiting Marketing , KBA , LOD-SF-RMK , Recruiting Marketing , How To


SAP SuccessFactors Recruiting all versions