SAP Knowledge Base Article - Public

2302876 - Top Reasons why a job is not appearing on jobs page - Recruiting Marketing

Symptom

This article presents an overview of the most common causes why a job is not appearing in the Recruiting Marketing site.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental

Environment

SAP SuccessFactors Recruiting Marketing (RMK)

Resolution

1. Job post type

For Recruiting Management customers: Ensure that the job is posted externally, and not internally, expired or private.

You can check this by going to the Job Requisition > Job Postings > and checking if the job is posted in the Corporate Posting. If it is only posted in Intranet, Internal or External Private Posting, it will not appear in RMK.

posting date.PNG

2. Job is posted

For all customers: Ensure that the job is live and posted in the Applicant Tracking System.

You can check this by searching for the job in the Applicant Tracking System job site, or by checking the apply URL.

 

3. Changes in the Applicant Tracking System

For all customers: if you made any change in your Applicant Tracking System that may have caused this and you didn’t informed us about this change, please open a support incident with us informing what changes were made. The changes in the Applicant Tracking System should be informed and aligned with our Professional Services team, so they can adjust any configuration or setting in our end to accommodate the changes.

 

4. Recruiting Marketing Job Field Mapping

For Real Time Job Sync customers: the mapping between the Recruiting Management and Recruiting Marketing fields can be incomplete or wrong.

Please refer to the following Knowledge Base Article for further details: 2292809

 

5. The RMK required fields are not populated

For all customers : RMK requires the following fields to be populated in RCM for the jobs to be imported into RMK. These fields are : External Description (Remember that if you are using Job Profile, the description is replaced by Job Profile), External Title and location information (Country and City for all jobs and State data for US jobs)

Please refer to the following Knowledge Base Article for further details: 2292809

 

6. Real Time Job Sync backend configuration

For Real Time Job Sync customers: there can be a misconfiguration for the feature. In this case, please open a support incident with us, and we will double check the configuration for you.

Please mention the following internal Knowledge Base Article for details: 2292841

 

7. User that is owner for the full feed job

For Real Time Job Sync customers: the user that was used to create the full feed job in our backed must be always active. While configuring Real Time Job Sync, we need to create a full feed job in our end that will automatically run every day to collect and update the jobs. This full feed job has a user owner, in case that this user is set to inactive in the system, the full feed job will fail. For this reason, we always recommend to set an admin user as owner of this job, as this admin user will probably not be inactivated from the system.

8. job size exceeds maximum allowed of 100000 bytes per job

To ensure jobs are not over the limit, the requisition must be cleaned up. Embedded graphics must be removed from the job description. The other primary culprit is editing the requisition in Word and pasting the content into RCM without following the process for cleaning up the word content which may contain unsupported formatting.

The best way is to use notepad to create the description and paste the content into the editor.

Please refer to the following Knowledge Base Article for further details: 2512171.

9. Expected time using Job Collection 

For Job Collection/Kapow customers: Please note that the job will take 24 hours to appear on Recruiting Marketing. The daily job that runs every night needs to run to collect and post the job from the Applicant Tracking System to Recruiting Marketing.

 

10. Posting Notes

For Job Collection/Kapow customers: The job must have the Posting Notes in the job description.

Note this does not apply to Odata Api Job collection where Posting Notes are not required.

Please refer to the following Knowledge Base Article for further details: 2207663

 

11. Incorrect Posting Notes

For Job Collection/Kapow customers: The job have posting notes, but it is still not appearing on the Applicant Tracking System? Please double check if the Posting Notes are configured correctly. They should have the same number of segments and the same segments.

Please refer to the following Knowledge Base Article for further details: 2207663

 

12. Job Collection backend configuration

For Job Collection/Kapow customers: If steps 1, 2, 5 and 6 are correct, please open a support incident with us and we will check the internal configuration.

13. The rules may need to be adjusted

All strategy pages are created based on rules. These rules define the fields/keywords/title/etc. that the jobs must contain in order to display on that page.

For example, usually the rules are created based on the department/job category field, so the rule can say that all jobs where the department field is “sales” will appear on the "Sales" strategy page.

If a job is not appearing on a strategy page, a possible reason might be that the rule does not contain the expected values for that job, so the rules have to be reviewed.

Please refer to the following Knowledge Base Article for further details: 2305898.

Keywords

Top Reasons, Job not posted, Real Time Job Sync, Job Collection, Kapow, job missing in RMK, missing jobs, Could not open app. Try again later   , KBA , LOD-SF-RMK , Recruiting Marketing , How To

Product

SAP SuccessFactors Recruiting all versions