SAP Knowledge Base Article - Public

3427113 - Job Application field-permission Not Propert Working for Specific Custom Created Statuses - Recruiting Management

Symptom

Job Application Fields are not following the defined field-permission in certain custom created statuses.

For example: fieldID has been defined for all statuses in the Status Pipeline but only in the statusABC, the field is not following the field-permission.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP SuccessFactors Recruiting Management

Cause

The status under the field-permission has a typo and it's not following what has been set under Application Status Set base.

For example: In the Application Status Set base, the Status Name is "Phone Screen" but in the field-permission, it has been defined as "Phone screen", with a low capital letter.

 <field-permission type="write">
      <description><![CDATA[Description]]></description>
      <role-name><![CDATA[O]]></role-name>
      <role-name><![CDATA[R]]></role-name>
      <status><![CDATA[Phone screen]]></status>
      <field application-field-id="fieldID" />
</field-permission>

Note that blank spaces will also affect the configuration. If you have a Status Name " Phone Screen", with a blank space in the front, or in the back, the space must be respected as well in the field-permission.

Resolution

Review all affected fields and make sure to respect the specific Status Name given.

To access the Application Status Set base, you can refer to the following KBA under the section "How to edit a existing status": 2080952 - Applicant Status Configuration in SuccessFactors - Recruiting Management.

Keywords

field, missing, specific, status, application , KBA , LOD-SF-RCM , Recruiting Management , LOD-SF-RCM-APP , Applicants and Job Applications , Problem

Product

SAP SuccessFactors Recruiting all versions