Symptom
One Event Reason Initial Conversion Data Load (DATACONV) is made inactive with effective start date from 15.11.2019. But when they used this event reason in data upload template with effective date of 01.04.2020, data uploaded was successful with this inactive Event Reason.
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 Employee Central
Reproducing the Issue
1. Make status of an Event Reason inactive from Manage Organization, pay and job structures tool.
2. Perform import using this inactive Event Reason.
3. Import is successful.
Resolution
This is current system behavior and will occur on imports which do not use Centralized Services.
To confirm which element supports Centralized Services please review the following link:
Managing Mass Changes in Employee Central: Centralized Services for Employee Data Imports
For elements which do not use Centralized Services yet, the below workarounds can be used:
- To delete the event reason.
- If event reason cannot be deleted then make correction in Effective as of date of event-reason to future date so that it cannot be used while importing till then for example '12/12/2099'.
Keywords
Inactive Event Reason in Import, ECT-139130 , KBA , LOD-SF-EC-FOO , Foundation Objects (Organisation, Pay and Job Structures) , Problem