Symptom
Primary configuration for GO/FO fields in Job Requisitions.
Environment
SAP SuccessFactors Recruiting Management
Resolution
Please reached out to Partners or Professional Services to configure these fields in the job requisition template.
How to configure GO/FO fields in the Job requisition template?
Job Requisition
The Job Requisition was enhanced to support fields of type GO/FO (both standard and custom). Six new standard GO/FO fields were also introduced. They are:
- legalEntity_obj
- businessUnit_obj
- division_obj
- department_obj
- costCenter_obj
- location_obj
Job Requisition template
The GO/FO fields can be defined in the Job Requisition template as follows
<field-definition id="department_obj" type = "object" object-type="Department" required="false" custom="false">
- id --> Is the name of the standard GO/FO field. It is case sensitive.
- type --> If defined will always have the value "object". This tag is optional for six standard GO/FO fields.
- object-type --> Will be the Objects code of the GO/FO (Found in configure Object Definition). Defining a wrong GO/FO to the standard field will not be supported. Eg, the standard field Department_obj should be of type Department. No other type will be allowed.
- custom (OPTIONAL) --> If defined it should always be FALSE.
The Job Requisition template would be enhanced to support GO/FO fields as both standard and custom fields. The GO/FO should be ACTIVE. Field id is case sensitive on the template
Standard GO/FO Fields
For standard fields the naming convention would be to use the name of GO along with the suffix "_obj". A standard field Division on the template would be defined as follows
<field-definition id="department_obj"type = "object" object-type="Department" required="false" custom="false">
- id --> Is the name of the standard field. It is case sensitive.
- type --> If defined will always have the value "object". This tag is optional for the 6 standard fields
- object-type --> Will be the Objects code (Found in configure Object Definition). Defining a wrong GO/FO to the standard field will not be supported. Eg, the standard field Department_obj should be of type Department. No other type will be allowed.
- custom (OPTIONAL) --> If defined it should always be FALSE.
Custom GO/FO Fields
For custom fields there are no naming conventions. A custom field can be defined as follows
<field-definition id="custom_dept" type = "object" object-type="Department" required="false" custom="true">
- field-definition id --> Is the name of the custom field. It is case sensitive.
- type --> will always have the value "object"
- object-type --> Will be the Objects code of an ACTIVE GO/FO (Found in configure Object Definition). This can be either a standard (GO/FO) or custom (GO/FO) object. Defining a non existent GO/FO will not be supported to the standard field will not be supported. INACTIVE objects will not be supported.
- custom (OPTIONAL) --> If defined it should be true in this case.
Note: If the same custom field has been defined in different job requisition templates with different types or object-types, a WARNING message is shown to the user while saving the template.
Keywords
CheckJobReqFOGOCustomFields, GO/FO fields, FO/GO, HR Master data, GO/FO fields in Job requisition, Generic Objects, Foundation Objects , KBA , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem