2718804 - How the “Department”, “Location” and "Division” fields will behave once transferred to an object field from enum - Recruiting Management

How the "Department", "Location" and "Division"  fields will behave once these fields are updated to an object field from enum.

SAP SuccessFactors Recruiting Management

1. In the requisition template Department, Division and Location are configured as an enum field. 
2. Add a new object type fields having field id  “department_obj”, “location_obj ” and ”division_obj”. 
3. Upload the requisition template and save. 

Old and new requisition will contain two fields one is “enum” and the other is an object. Customer can hide the old fields by controlling the permission in the requisition template. However we don’t have any option to copy the old “enum” values into the newly created “object” field.

Once the object fields are configured there will be two Location, Department and Division fields in the filter and display option on the Job Requisition Overview page. It is not possible to merge both of these fields into the one but you can hide the standard enum fields using the setting "Disable Department, Division, and Location filter options on Job Requisition Tab" in Manage Recruiting Settings in the Admin Center.

There will also be two of each value in "Internal and External Career Search Settings" in the Admin Center. Using Location as an example, the enum field will be labeled "Location" while the object field will be labeled "Location(Foundation Object)". It is not possible to merge these filters on the job search page into one, but you can disable the enum filters from this page and enable the object filters.

You can use Report Center or Integration Center to generate report on these fields.

Object, field, department, division, location, transferred, enum, template, behavior, change, migrate

, KBA , csg_q , LOD-SF-RCM-JOB , Job Postings & Requisitions , How To

SAP SuccessFactors Recruiting all versions