3110424 - Job Information Fields are Accessible via API, Rules or Reports When not Configured in Succession Data Model/Business Configuration UI

A number of Job Information Fields are Accessible via API, Rules or Reports when not Configured in the Succession Data Model/Business Configuration UI.

These fields can be included in custom integrations or business rule configuration.

The full list of fields can be found below:

• eeo-class
• job-title
• job-code
• employee-type
• department
• division
• location
• change-reason
• change-reason-external
• manager
• hr-manager
• radford-jobcode
• notes
• seq-number
• expected-return-date
• manager-id

• SAP SuccessFactors Employee Central
• SAP SuccessFactors Integrations - OData / SFAPI

This issue occurred due to a defect, which meant API, Rules or Reports were not prevented from selecting these fields even though the fields were not configured in the Succession Data Model/Business Configuration UI.

A code correction was made in the 2H 2021 release to resolve this issue. This will be included in the Notable Fixes for the Production Release Information Update, A link will be updated here when published.

API, Rules or Reports will no longer be able to access these fields if they are not configured and enabled in the Succession Data Model/Business Configuration UI.

If you wish to use these fields in your instance they must be configured and enabled in the Succession Data Model/ Business Configuration UI.

To enable these fields this can be done via Manage Business Configuration UI.

How to Confirm if your instance is impacted:

If you are impacted by the above described issue, to confirm if your instance was using this field(s) when they are not enabled in your instance, please follow the below steps:

1. Navigate to  Manage Business Configuration, navigate to “jobInfo” hris element
2. Search for the impacted field for example "expected-return-date"
    a) If the field IS NOT list, then follow the steps "Enabling field(s) which ARE NOT Configured in Manage Business Configuration" below. 
    b) If the field IS listed, check the field "Enabled" setting of the field. If the field is set to Enabled =No, follow the steps "Enabling field(s) which ARE Configured in Manage Business Configuration" below. 
    c) If the field IS listed and is Enabled = Yes, your issue is not related to this code correction. Please reach out to the support team for further review. 

Enabling field(s) which ARE NOT Configured in Manage Business Configuration:

1. In Manage Business Configuration, navigate to “jobInfo” hris element
2. Add the desired field by selecting the hris field id from the “identifier” dropdown for example "expected-return-date"
3. In the “details” section, configure the field label and attributes as desired
4. Ensure the field is set to Enabled = Yes
5. Repeat steps 2 - 4 for all desired fields
6. Save Changes
7. Note: Technical information on the fields can be found in the following link:  
   Data Object Tables in Employee Central: Job Information

Enabling field(s) which ARE Configured in Manage Business Configuration:

1. In Manage Business Configuration, navigate to “jobInfo” hris element
2. Search for the desired for example "expected-return-date"
3. Click on the “details” section, configure the field label and attributes as desired
4. Change Enabled = NO to be Enabled = Yes
5. Repeat steps 2 - 4 for all desired fields
6. Save Changes
7. Note: Technical information on the fields can be found in the following link:  
   Data Object Tables in Employee Central: Job Information

Please Note:

If you wish for these fields to be visible on the Job Information UI, you must provided Permissions to these fields for end users to be able to view the fields. 

The following fields are depreciated and should not be used in your Job Information configuration:

• change-reason
  If you desire to use this fields, it is recommended to use a custom string instead.
• change-reason-external
  If you desire to use this fields, it is recommended to use a custom string instead.
• manager
  The standard "manager-id" field should be used instead of the "manager" field.
• hr-manager
  If you desire to use this fields, a custom string field can be used instead although recommend the use of Job Relationships to store this information. 

FAQs:

Q: Will I loose the data in the field when I enable it as directed above?
A: No data will be lost. Any data already in the database will still remain once the field is enabled. 

Q: If I have the same configuration in my Preview and Production Instance, do I also have to enable the field in the Production instance? 
A: Yes, this code correction is added in the 2H 2021 release, if the Production instance also does not have these field configured they should be enabled using the above methods prior to the Production Release.

Q: We recently implemented Leave of Absence but did not enable the "expected-return-date", should this field be enabled when using Leave of Absence? 
A: Yes, this field must be enabled when using Leave of Absence, further details can be found on the following page: Implementing Employee Central Core - Additional Information for Job Information : Expected Return Date

• 2984387- Job Information missing field in preview data model after 2H 2021 release affecting APIs and Reporting
• Data Object Tables in Employee Central: Job Information
• What's New Viewer: Deprecation of Job Information Data Model Fields - ECT-175639
• Setting Up and Using Business Configuration UI (BCUI): HRIS Elements and Fields in BCUI

ECT-153028, eeo-class, job-title, job-code, employee-type, department, division, location, change-reason, change-reason-external, manager, hr-manager, radford-jobcode, notes, seq-number, expected-return-date, manager-id, ECT-134794 , KBA , LOD-SF-EC-BCI , Manage Business Configuration (BCUI) & Data Models (XML) , LOD-SF-EC , Employee Central , LOD-SF-INT , Integrations , LOD-SF-EC-JOB , Job Information , Bug Filed