3231299 - The wrong user is getting populated in the Operator field when creating a new Job Requisition

When leaving the Operator fields empty on the Job Requisition creation page, the system allows the Job Requisition Originator to proceed and does not validate the required Operator fields. In the Job Requisition details page, a "random" user has been inserted as the Hiring Manager and Recruiter Operator by the system. 

SAP SuccessFactors Recruiting Management

1. Go to Recruiting
2. Job Requisitions
3. Click on "Create New"
4. In the Job Requisition creation page, enter the Job Req Title, but leave the Operator fields empty
5. Click on Next
6. There is no validation message and the system allows you to proceed
7. In the Job Requisition details page, a "random" user has been inserted as the Hiring Manager and Recruiter Operator by the system

There is an active user in the UDF file with "null" (or "Null") as User ID and the system enters this user as the Operator in the Job Requisition details page. 

When the Operator field is empty, the system reads it as null value which gets converted to "null" string, therefore the backend is skipping the validations for it.

As best practice, there should be no active user in the UDF file with User ID as "null". As a workaround, you might want to make the user inactive and purge it from the system. You would first need to reassign all the assigned tasks and functions to another active user with a valid User ID. 

Regarding the skipping validation of the system, this has been identified as a defect and will be fixed with the b2211 release (Preview: October 28th, 2022 - Production: December 9th, 2022). 

3231398 - Job Requisition Creation page: missing system validation for Required Operator Fields

Operator, Wrong, User, WEF-29764 , KBA , LOD-SF-RCM-JOB , Job Postings & Requisitions , Problem