SAP Knowledge Base Article - Public

2530704 - Validations Performed on Offer Detail Template Upload

Symptom

The import tool performs three categories of validations with respect to an offer detail template: Against all active job requisition, job application and other offer detail templates. Currently all validations performed against other templates will be shown only as a "Warning". This is to ensure backward compatibility.

Environment

Recruiting Management

Reproducing the Issue

2017-09-07 05_38_40-SAP.png

Cause

   System is validating the configuration of the newly uploaded template

Resolution

The list of validations performed includes the following:

1. Field Type Mismatch

  • Consider we have a field, "Country" that is defined as type "text" in the Offer Detail Template. However, the field is being referred from the Application XML where it is defined as type "picklist". This leads to a mismatch in types. This will make the offer field, "Country", to appear as text (showing the picklist id) in the offer screen.

 

2. Missing Fields

  • If the Offer Detail template is having some fields that refer to a job requisition template or job Application, and the field is not available in the referring template, this could lead to errors.

 

3. Check for mismatch in Required attribute values

  • Some fields might be defined as Required in the Offer Detail Template (required="true") while in the referring template it might be defined otherwise.

 

4. Validation of Standalone fields across multiple Offer Detail templates

  • This includes validation of one offer detail template against all the other active offer detail templates. Consider that we have two offer detail templates. Consider that we have two offer detail templates with each having a field "customPicklist4" of type picklist. Ideally, these fields should remain identicalin both the templates.
  • Having the same fields (type picklist) defined in the two templates with different labels would possibly cause issues especially while creating ad hoc reports. For instance, while creating an ad hoc report, it will take either of the labels, most probably the one that is defined first. However, the values will be populated for both the fields.

 

5. Check for unsupported fields

  • Only certain field IDs may be referenced from the Requisition or Application XML. There are some fields that are not supported in the offer detail template (for example, filter1 from Requisition).

See Also

2345268 - Offer Detail - Implementation Tips & Tricks from Support - Recruiting Management

Keywords

KBA , LOD-SF-RCM-APP , Applicants and Job Applications , How To

Product

SAP SuccessFactors HCM Suite 1511 ; SAP SuccessFactors HCM Suite 1602 ; SAP SuccessFactors HCM Suite 1605 ; SAP SuccessFactors HCM Suite 1608 ; SAP SuccessFactors HCM Suite 1611 ; SAP SuccessFactors HCM Suite 1702 ; SAP SuccessFactors HCM Suite 1705 ; SAP SuccessFactors HCM Suite 1708 ; SAP SuccessFactors HCM Suite 1711 ; SuccessFactors HCM Suite 1204 ; SuccessFactors HCM Suite 1207 ; SuccessFactors HCM Suite 1210 ; SuccessFactors HCM Suite 1302 ; SuccessFactors HCM Suite 1305 ; SuccessFactors HCM Suite 1308 ; SuccessFactors HCM Suite 1311 ; SuccessFactors HCM Suite 1402 ; SuccessFactors HCM Suite 1405 ; SuccessFactors HCM Suite 1408 ; SuccessFactors HCM Suite 1411 ; SuccessFactors HCM Suite 1502 ; SuccessFactors HCM Suite 1505 ; SuccessFactors HCM Suite 1508