SAP Knowledge Base Article - Public

3274802 - Employee Central - Job Information

Symptom

This is a collection of useful Knowledge Base Articles and information related to Job Information.

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

Environment

SFTipsNTricks.JPG Employee Central.png 

Reproducing the Issue

JOB INFORMATION COMPONENTS: 

Below is the current list of EC Job Info Components 

It is important to select the correct component for accurate categorization of Support Cases and added value. It would help reduced scope of effort, improves monitoring and assignment group mapping when creating case. 

Job Information – Imports (LOD-SF-EC-EDP-JOB) 

  • All Job Information Import related cases 

Job Information - Business Rules (LOD-SF-EC-JOB-RUL) 

  • Issues with Business Rules Triggered on Job Info 

Job Information - Object Associations and Field Criteria (LOD-SF-EC-JOB-OAS) 

  • Issues with Object Associations and field criteria on Job Info fields (Filtering issues) 

Job Information - Country Specific Configurations (LOD-SF-EC-JOB-CSF) 

  • Issue with Country Specific Field Configurations (CSF) 

Job Information – Forward Propagation (LOD-SF-EC-JOB-FWP) 

  • Forward Propagation Issues 

Job Information History or MSS UI + Workflow “In-flight updates” (LOD-SF-EC-JOB-UI) 

  • History UI display issues 

  • MSS UI display issues 

  • Workflow “In-flight updates’ display issues 

Job Information Events, Derivation & Employee Status (LOD-SF-EC-JOB-EVN) 

  • Event Reason Derivation issues 

  • Employee Status Inheritance Issues 

Job Information Picklists (LOD-SF-EC-JOB-PKL) 

  • Picklists not being respected 

  • Cascading picklist issues 

  • Option Ids being displayed 

Job Information – Off Cycle Event Batch (LOD-SF-EC-JOB-OFF) 

  • Off Cycle Event Batch cases updating Job Information 

Job Information Role Based Permissions (LOD-SF-EC-JOB-RBP) 

  • Role Based Permissions Cases for the Job Information and History UI including field level permissions 

Cause

FAQ INDEX

  • Implementation
  • Best Practices
  • Display Logic and Troubleshooting
  • Common Issues

Resolution

IMPLEMENTATION 

It is partially configurable in the Business Configuration UI (BCUI).  

It can be defined either globally, country specific, or person type specific. 

It is available in the Manager Self-Service scenario. 

Rule contexts, events, and field-level permissions are supported. 

  • For more Job information about some of the features and functions in Employee Central you may check on below : 

              Additional Information for Job Information | SAP Help Portal 

  • Expected Return Date 

  • Event Reason 

  • Job Code Propagation 

  • Position to Job Information Sync 

  • Notes and Attachments 

 

  • Job Information – Imports 

  • Configuration and Best Practices 

In import of Job Information, it’s important to prepare data for import such as Business Keys and Data Field. 

There are configurations/processes that’s by default is supported with Job Information Imports, as well as standard events. For detailed information please check Job Information Imports|SAP Help Portal 

With Centralized services there are several validations initiated for Import Employee Data page or APIs in different scenarios to ensure data consistency during import. It supports data import in Incremental Load mode and Full Purge mode. 

Job Information data imports on Centralized services benefits, behaviour changes from legacy imports and configuration requirements are explained here: 

  • How To's and Common Issues              

 

  • Job Information - Business Rules  

  • Configuration 

 These rules are for Job Information and Compensation only. These define the event reason              according to what change is done to an employee’s data, so that the system automatically selects the appropriate event reason. Depending on the event reason, the employee status is updated, if necessary. 

For details about setup of business rules for specific Job Information events please check here: Configuring Parameters for a Business Rule for Job Information |SAP Help Portal 

  •   Best Practices 

Use Cases: Business Rules |SAP Help Portal 

3195584 - Job information To Custom MDF Object OnSave Rule Behavior - Employee Central 

2906965 - Job information records creating without any change - Employee Central 
2951071 - B2005 EC: Resignation/Termination Date field in job information is not auto populating 

  • Configuration 

Here’s guide to understand the behaviour of FO/MO fields in Job Info with searchable fields. Also, if there’s a need to add more searchable text in Job Info FO fields for employees to easily identify what value of input can be found here:   

  • Best Practices 

 

  • Job Information - Country Specific Configurations 

  • Configuration 

To navigate to the Job Info country/region-specific content please refer here: 

 

  • Job Information - Forward Propagation 

  • Configuration and Best Practices 

  • Forward Propagation for Job Information is enabled by default in the UI (hard-coded) and cannot be disabled. 

  • Forward Propagation is currently available for Job Information AND Compensation Information (it is not designed to work for other elements such as Personal Info) 

  • This feature cannot be turned off for the Job Info UI's as it has been hard-coded. 

  • This feature can be enabled for Compensation Information UI via Admin Center > Company System and Logo Settings > Enable Forward Propagation for Compensation Information (Note: Not applicable for Imports) 

  • It works only when we Insert a new Job Information record through either Job History or Take Action (MSS UI). 

  • Forward Propagation does not occur when updating records through Job History > "Make Correction" nor when a record is Deleted via Job History. 

  • All records that are updated by the Forward Propagation logic now also have their "Last updated by" timestamp information updated to reflect that a change has been made to the record. Prior to b1608 the "Last modified by" timestamp did not get updated. 

  • Business rules are not triggered for the forward propagation modified time slices. 

Forward propagation was designed to carry the information to other records until it finds a different information 

If there is a change in a field, the propagation stops in order to assure nothing is overwritten. That is because system understands there is a reason that change was made for the employee on that date. 

 

  • Job information - History or MSS UI+Workflow 

  • Configuration 

Centralized services now support saving changes on the History UI of Job Information. 

The setting for this feature is Company System and Logo Settings >Enable Centralized Services to Save Changes on the History UI of Job Information. 

For Job Information History UI on Centralized service benefits, behavior changes from legacy History UI, and Configuration Requirement etc, please check below: 

  • How To’s 

 

  • Job Information - Events, Derivation & Employee Status 

  • Configuration and Best Practices 

When having difficulties in configuring the event reason derivation using business rules you may refer to this guide: Best practices setting up business rules for event reason derivation 

Before you configure the event reason derivation, we strongly recommend you to read the section 9 - Using MDF-Based Business Rules for Event-Reason and Workflow Derivation in our employee central master implementation guide and Blog:Event Reason Derivation XML Rules Change to Business Rules Within First Half 2021 Production Release - Innovation Alert 

  • Configuration and Common Issues 

Legacy Employee Central picklists have been migrated to MDF picklists. All picklists are now managed in the Picklist Center. 

For more information, refer to the Implementing Picklists |SAP Help Portal 

Off Cycle Event Batch is a native Employee Central feature that offers key automation capabilities to help you manage your employee data better. 

An Off Cycle Event Batch is a Metadata Framework (MDF) object that you can use to create an automated process for modifying the following employee data: 

  • Job Information 

  • Employment Details 

  • Employee Time 

  • Work Order Information (for Contingent Workers) 

For implementation, Additional Configurations and Use Cases, please refer to: 

 

  • Job Information - Role Based Permissions 

For all fields in jobInfo, the permissions are defined in the section "Employee Central Effective Dated Entities" within the Permission Role. 

When the fields are Country/Region-Specific, these permissions are defined with the initials from the Country in front of the field name. 

Country-Specific Fields in BCUI | SAP Help Portal 

Keywords

JOB INFORMATION , Expected Return Date, Event Reason , Job Code Propagation,  Data Model Field, Mandatory HRIS Fields for HRIS Elements , Import,  Business Rules, Object Associations , Country Specific Field Configurations (CSF), History UI display ,  MSS UI ,       Workflow “In-flight updates’, Event Reason Derivation ,  Employee Status Inheritance , Picklists , Cascading , Off Cycle Event Batch  , KBA , LOD-SF-EC-JOB , Job Information , LOD-SF-EC-JOB-PKL , Picklists , LOD-SF-EC-JOB-EVN , Events, Derivation & Employee Status , LOD-SF-EC-JOB-UI , History UI & MSS UI , LOD-SF-EC-JOB-FWP , Forward Propagation , LOD-SF-EC-JOB-CSF , Country Specific Configurations , LOD-SF-EC-JOB-RUL , Job Info Business Rules , LOD-SF-EC-JOB-OAS , Object Associations and Field Criteria , LOD-SF-EC-EDP-JOB , Job Information Imports , LOD-SF-EC-JOB-RBP , Job Information Role-Base Permissions , LOD-SF-EC-JOB-OFF , Off Cycle Event Batch , How To

Product

SAP SuccessFactors Employee Central all versions