3300769 - Behaviour of read-only location object as filter, token and in reports when Job Requisition is created via HCM

When a Job requisition is created via HCM and the location field is read-only, the location no longer appears as filter on career site, does not resolve as a token and also appears blank in reports

SAP SuccessFactors Recruiting Management

1. Create Job Requisition via HCM
2. Job requisition is passed to RCM and the location is pre-populated
3. Post job and see that the location does not appear as filter, does not resolve as a token in emails and is blank in reports

When creating the Job Req using SAP HCM (using SFAPI calls) and saving the record from the SF Recruiting UI, it's expected behaviour of UI not to save the Read-only fields in SF database. Hence these values are showing blank in all other places e.g. Report, Token resolution & Career Site filter. Please note that it works fine with OData API. 

In order to resolve this issue, you would need to switch to OData API. If not, the only workaround is to grant write permission to the location object so that you can update it manually and it will then resolve as a filter, token and will appear in reports.

Field Behavior for Job Requisition Trigger Integration

integrations, triggers, HCM, HXM, job req, requisition, objects, read-only, read only, readable, writeable, filters, not resolving, no data, not visible, disappear, disappears, removed, hidden, internal and external career search settings, foundation object , KBA , LOD-SF-RCM-INT , Integration Center & Intelligent Services , LOD-SF-RCM-JOB , Job Postings & Requisitions , LOD-SF-RCM-API , Webservices & APIs , How To