SAP Knowledge Base Article - Public

3103944 - Prevention of Special Record Creation in Job History ECT-130989 - 2H 2021

Symptom

In the 2H 2021 Release an new enhancement ECT-130989: prevents the creation of records with certain events via the Job Information History UI.

Environment

SAP SuccessFactors Employee Central

Cause

  • Creation of records with below listed events is no longer possible via the Job Information History.
  • Also, when editing existing records to change the event, these events cannot be selected any more.
  • There are dedicated UI transactions for these events where the status of the employee, along with their Employment/Termination Details, will be updated correctly.
    Please note some of these Event are feature specific and can only be used if the relevant feature is enabled and configured in your instance. 
  • These Events will not be selectable via Take Action > Change Job Information, as only Events associated to Employee Status = No Selection can be selected via Take Action > Change Job Information. 
  • Such changes can still be done using the full purge import.
  • This change has been implemented to avoid data inconsistency across EC Objects

List of prevented events:

  • Hire (H)

  • Termination (26)

  • Rehire (R)

  • Leave of Absence (10)

  • Return to Work (23)

  • No Show (NS)

  • Add Global Assignment (GA)

  • Away on Global Assignment (AGA)

  • Obsolete (OGA)

  • Back from Global Assignment (BGA)

  • End Global Assignment (EGA)

  • Start Pension Payout (SPP)

  • End Pension Payout (EPP)

  • Discard Pension Payout (OPP)

  • Surviving Spouse Start (SSS)

  • Surviving Spouse End (ESS)

  • Work Order End (ECWK)

  • Add Higher Duty/Temp Assignment (HD)

  • End Higher Duty/Temp Assignment (END_HD)

  • Obsolete Higher Duty/Temporary Assignment (OHD)

Please Note: 

  • These Events are restricted based on their External Code, the label may differ in your instance but if the External Code matches those Events will be restricted. 
  • This change is only with regards to creation of new records via Job History > Insert New Record.
  • This means that you will no longer be able to create a new record via History > Insert New Record with one of the Listed Events.
  • When trying to create a new record via History > Insert New Record you will no longer see these Events for selection in the Events Drop Down.
  • This will not prevent you from editing or updating and existing record which has one of these Events. Please note however when editing/updating an existing record you will no longer be able to change the Event to one of the above Events. 

Please Note - Update for Leave of Absence Events (10 & 22):

Based on customer feedback that the Legacy Leave of Absence.   Legacy Leave of Absence has not be supported since the introduction of PP3 and instead “Time Off" and "Enable Time Off for Leave of Absence only" features should be used: 2560416 - Employee Central: Legacy Leave of Absence FAQ (v12 Revolution UI only)

As the implementation of “Time Off" and "Enable Time Off for Leave of Absence only" features may take sometime. To allow continued use of the system, from the b2111p1 patch (1 Dec Preview and 3 Dec Production) LOA events will be accessible from Job History in the following circumstance:

    • When Time Management is not enabled in an instance, on inserting a new record via Job Info History UI, you'll be able to select the Events 'Start Leave of Absence' or 'Return from Work'
    • When  Time Management is enabled in an instance, on inserting a new record via Job Info History UI, you'll be not be able to select the Events 'Start Leave of Absence' or 'Return from Work'.

  • Please Note:
    From the 1H 2022 release these two Events will once again be prevented from being created via Job History. The same prevention will apply to the creation of LOA records via job information import / API upsert, regardless of whether Time Off or Time Off for LOA Only is enabled.
    This means if you are currently using Legacy Leave of Absence you must have completed a migration/implementation to either "Time Off for Leave of Absence Only" or full Time Off feature prior to the 1H 2022 Release. 
    Please review the following links for the required details:
    •  2560416 - Employee Central: Legacy Leave of Absence FAQ (v12 Revolution UI only).
    • Refer KBA for steps on how to enable "Manage Leave of Absence" Option from Take Action, once you have enabled and configured Time Off: 2558149 - Time Off: How to start a Time Off Leave of Absence from Take Action (v12 and PP3 UI)
    • Refer Implementation Guide section on Time Off for Leave of Absence Only
    • Other relevant KBAs on Time Off For Leave of Absence: 2577804 - Migration to Time Off for Leave of Absence FAQ
  • Workaround While Implementing “Time Off" and "Enable Time Off for Leave of Absence only" (not available after 2H b2211 release):

As the implementation of “Time Off" and "Enable Time Off for Leave of Absence only" features may take some time. To allow continued use of the system, you can create  Legacy Leave of Absence Records via Job History if you disable “Enable Centralized Services to Save Changes on the History UI of Job Information” via Company System and Logo Settings.

Please Note: “Enable Centralized Services to Save Changes on the History UI of Job Information” will be universally enabled as of the 2H 2022 Release and as of then this workaround will no longer be available. The implementation of “Time Off" and "Enable Time Off for Leave of Absence only" MUST be completed before the 2H 2022 Release to ensure you daily activities are not impacted.

FAQ:

Q: I can still see some of these Events in Job History?
A: If you have configured on of the above Events with an incorrect External Code (not the external code listed in parentisies by each Event) then this external code will still be visible in Job Histroy. 
    Please note this would be considered a configuration issue as each Event has a required External Code. 
    The list of External Codes can be seen in:
     - The Event Picklist which can be downloaded in the Master Picklist File from SAP Software Download Center 
     - In the following KBA: 2617429 - Event Reason Availability and Configuration in Employee Central

Q: If we selected the wrong Event Reason can we still Edit one of these Records via Job History, for example we selected the wrong Termination Event Reason? 
A: Yes, you will still be able to edit records with these Events via Job History. You will also be able to adjust the Event Reason selected, for example Change the Termination Event Reason selected to a different Termination Event Reason.
    You can also change the Event of a Record but not to one of the Listed Event Reasons.

Q: We have been Rehiring a user by inserting a Rehire record via Job History. How do we do this now? 
A: This change was made to prevent certain records from being created via Job History which should not be created via JOb History but via a dedicated UI or Import. 
    In this case a user should be Rehired via a HIRE/Rehire UI or via a Job History Import. Users in your system should be rehired via one of these methods.

Q. I cannot see the Leave of Absence Option from Take Action Menu?
A: Please review the above note "Update for Leave of Absence Events (10 & 22)"

Q. Our Event Reason Derivation Business Rules are overwriting these Events when editing a record. What can we do to stop this. 
A: The issue you are facing with regards to the Event Reasons getting overwritten due to Event Reason Derivation business rules is caused by the configuration of said business rules.
     As per the requirement of Business Rules for Event Reason Derivation must:

  •     Check if the event reason field's value is null before setting it through the business rule. This avoids overwriting the event reason accidentally.

    This is documented in the following section of the handbook: 
    Implementing Employee Central Core: Event Reason Derivation Business Rules 
    As per your current configuration this is not implemented in your rules, do not check if event reason is equal to null.
    In order to prevent this issue from occurring, your Event Reason Derivation business rules need to be corrected.
    For records that need updating until this is done, they must be corrected via Import.

Feature Specific Event Links:

Leave of Absence Events:

No Show:

Global Assignment:

Pension Payout:

Contingent Worker:

High Duty:

See Also

Keywords

ECT-130989, job history, events, event reason, event reasons, b2111, 2111, 2H 2021, Hire, Termination, Rehire, Leave of Absence, LOA, Return to Work, No Show, Add Global Assignment, Away on Global Assignment, Obsolete, Back from Global Assignment, End Global Assignment, End Global Assignment, Start Pension Payout, End Pension Payout, Discard Pension Payout, Surviving Spouse Start, Surviving Spouse End, Work Order End, Add Higher Duty/Temp Assignment, End Higher Duty/Temp Assignment, Obsolete Higher Duty/Temporary Assignment, ECWK, INC1256312, ECT-186330, PTCH-37450, ECT-192014   , KBA , LOD-SF-EC-JOB-UI , History UI & MSS UI , LOD-SF-EC-JOB , Job Information , Product Enhancement

Product

SAP SuccessFactors Employee Central all versions