SAP Knowledge Base Article - Public

3300689 - Take Rule Behavior when Multiple Leave records are in the Import File


Example : You have a same take rule on 2 different LOA Time types which is configured to trigger an Error if the Employee status changes to Unpaid (U) or Paid Leave (P) which would happen if the Employee is on a LOA.

  • When you try to run an LOA Import with these 2 Time types for the same EE, the expectation is that AFTER the first row Import is done / executed, the Employee will go into U or P status and the take rule will execute for the secord record on the Import file - Thereby triggering an Error Message
  • However, this is not happening. The Take rule is evaluated to false as per rule trace, it is not identifying the status change due to 1st LOA record in the file .
  • Both the LOA records are being Imported successfully without any Error messages.


  • SAP SuccessFactors HXM Suite
  • SAP SuccessFactors Employee Central


This is an Expected Behavior


  • The status change which will potentially be triggered by the new LOA is NOT considered in the take rule. So, for the provided take rule to trigger on a single LOA import, the user already has to be in status U or P before the new LOA record(s) file is being Imported.
  • The validations are run for all LOAs "in the batch" in parallel before the job info is changed.
  • As the minimal batch size is 20, the aforementioned use case will not have the Take Rule Triggered.
  • You either need to use separate imports with only one LOA per file or you need to run a bigger import and split the LOAs of the same employee in different batches (e.g., first entry and 21st entry).


SF, EC, Success factors, Employee Central, Multiple EmployeeTime, Time off , KBA , LOD-SF-EC-TIM-RUL , TAT Rules, Validation & Take rules , LOD-SF-EC-MDF , MDF & EC2MDF Migration , LOD-SF-MDF-IMP , Import and Export Issues , Problem


SAP SuccessFactors HXM Core all versions