3561608 - "Context.Current User" in Recruiting Rules Always Returns Null - Recruiting Management

• "Context.Current User" returns a null value in Recruiting rules.
• How to fetch a user's Employee Central information (job info, employment info, etc.) in Recruiting module via Business Rules?

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

SAP SuccessFactors Recruiting Management

1. Use "Context.Current User" to retrieve the user's EC information.
2. A null value is returned.

"Context.CurrentUser" was never supported in Recruiting business rules.

This function exists in old business rules that were created using the 'Basic' scenario. It has been removed from the new scenario rules creation process. 

It is recommended to select a Recruiting scenario to create a new business rule. The old 'Basic' scenario includes unsupported options, such as "Context.CurrentUser".

Please note that there is no direct rule function to select the current login user's Employee Central information within Recruiting business rules.

To retrieve and map a user's Employee Central information to a field in Recruiting, use Job Requisition Operator Fields instead. This is feasible only when the user is assigned to the job requisition as an Operator, such as a Recruiter or Hiring Manager. Operator Team fields are not supported.

Job Requisition Operator Fields are available from the following entities:

• Job Requisition Template
• Offer Detail Template  (if defined in the template)
• Job Requisition (All)  (accessible in Job Application template rules)
• Offer Approval (All)  (accessible in Job Application template rules)
  
  

Sample use case - Automatically populate Job Requisition fields with the job information of the Hiring Manager:

RCM, business rule, EC info, job info, default job req value, Context, INC9657764  , KBA , LOD-SF-RCM-RUL , Recruiting Rule Issues with MDF Platform , LOD-SF-RCM-JOB , Job Postings & Requisitions , Problem