Best practices for Time Off Calendar imports
Importing Time Off Calendars is supported – but we do not recommend to import Time Account Details (or changing these manually) as these get created by calendar runs. E.g. Do not import accruals as these have associated a periodID number to allow for recalculations and it is risky to manually make changes such as this as it will lead to inconsistency of Time Off data. If you need to adjust balances or earned days please avail of the Manual Adjustment posting type, which is supported in the import process, or make these changes via Interim Account Update calendar run.
When importing calendars always use status READY TO RUN (if you want to start them manually via UI) or status SCHEDULED (with a run date to trigger an automated run on a certain day). Do not use RUNNING, START or WAITING FOR OTHERS. By using status RUNNING you run the risk that calendars of the same time account type get executed at the same time and this might overlap postings in the time account details, as for START or “WAITING FOR OTHERS” these are more internal statuses to make avoid that calendars run in parallel.
If there are several calendars scheduled, the system determines the execution order automatically
- Calendars of different time account types get ran in parallel.
- Calendars for the same time account type have to run one by one.
When importing different types of calendars, of different time account types, please always follow this order:
- Account Creation
- Accrual Creation
- Entitlement Creation
- Interim Account Update
- Period End Processing
This way you ensure that e.g. when running accruals all your accounts have been created already.
Please share your experience using the tool and provide us with your feedback and I will be happy
Thanks & Regards,
SAP HCM& SuccessFactors Consultant&Corporate Trainer