3441736 - How Seek Location is handled by Recruiting Posting?

Since January 2024 and the migration of Jobstreet job boards and JobsDB job boards into various Seek job board, the location fields of Seek Job boards has changed.

SAP Successfactors Recruiting Posting

Seek requested SAP to stop using a static picklist about locations and start using their API to retrieve location. In order to do that, Recruiting Posting is using its own location fields (City, Postal Code and Country) to make the call to Seek API and fetch the Location Id to Seek API and send it on the feed. 

Please note that if the location is invalid/wrong, incorrect, (e.g. the city field of Recruiting Posting is not filled with an actual city) the Seek API can return the location ID with blank (Null) value and this will prevent the job to be posted on the job board. It is therefore important to correctly filled the location field when posting to Seek. Otherwise, the posting will appear in Invalid Field status or with an incorrect location on Seek interface.

Important : There is an exception for Seek HK, as it is linked only to Hong Kong city, therefore Seek requires that city field must be filled with the Hong Kong district and postal code should be filled with "000", "0000", "00000". This will ensure to retrieve correctly the location id from Seek API otherwise a blank (Null) value will be fetched and the job will not be posted.

Note : If you are getting an "Invalid Fields" error and you are not able to download the logs from the Job Status Table, it must be because your Location field data hasn't been recognized by Seek API. In such cases please refer to the above solution in order to solve your issue.

3412054 - JobStreet and JobsDB Joboards Unified with SEEK Job Board - Recruiting Posting

Seek, Location, Recruiting Posting, RPO, invalid field , KBA , LOD-SF-RPO-JOB , Job Offer not to be found/ to be removed to Job Boards , How To