2428809 - Job Requisition Validation Against Status Name in Status Permissions - Recruiting Management

When working with Job Requisition templates in Provisioning and in Manage Templates in Admin Center, the following error message appears when importing the Job Requisition XML template or modifying it through Manage Templates:

• In Provisioning:

• In Manage Templates Tool:

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

To edit the templates through Manage Templates:

1. Go to Admin Center;
2. Click on Recruiting > Manage Templates;
3. Select "Job Requisition;
4. Select the template you want to modify.

To edit the templates via Provisioning:

1. Go to section "Managing Recruiting";
2. Click on "Import/Update/Export Job Requisition Template";
3. Download the template you want to modify;
4. Make the changes through an XML editor;
5. Upload the template back into the instance.

In the past, if the "Enable Multi Stage Application" feature is enabled in Provisioning, the application field permissions have to be maintained under the <application-status-config> section of the Job Requisition template. The application field permissions have to be linked to statuses of the Application Status Set that is linked with the Job Requisition template. When uploading a Job Requisition template, the status names were not validated by the system although wrongly typed status names could cause system errors.

In Multi Stage Application there isn't validation against the name of the status in the permissions. So, for example, if the status name in the pipeline is called "InvitedToApply", and in the XML the permission has the following line:

<status><![CDATA[Invited To Apply]]></status>

The name is not matching (because of typo, or spaces, or capital letters...). And this is generating mistakes on permissions. The status name must be exactly the same on both sides: in the XML and in the Applicant Status Set.

Currently, the following validation check has been introduced: if the customer uploads a Job Requisition template via Provisioning, the system will check the names of the statuses that are linked with the field permissions under the <application-status-config> section. A wrongly typed status name will result in an appropriate error message. The status names have to match exactly the status names of the Application Status Set. The Application Status Set can be viewed and maintained via Admin Center > Edit Applicant Status Configuration.

With Multi Stage Application you can permission view/edit of fields based on status. In the job requisition XML you can define a status name. If this status name is not identical to the status name defined in Admin Center (Recruiting > Edit Applicant Status Configuration) then you run into issues. To avoid these issues, a validation tool has been developed to inform users that there is a mismatch between the status name in the requisition XML and in Applicant Status Configuration.

These validations will show for the following:

• When uploading job requisition XML in Provisioning
• When working with Manage Templates Tool in Admin Center (Admin Center > Manage Templates)

To solve these issues, you'd need to change the Status Name under the <application-status-config> section of the Job Requisition template.

To do that, you have two options:

• Contact your partner to do the changes in the XML;
• Select the correct status through Manage Templates.

Not a Valid Status in Application, CheckJobReqAppStatus, Recruiting Management, RCM , KBA , LOD-SF-RCM-JOB , Job Postings & Requisitions , Problem