EC Time Management Q4 2017 Features
time again to write some words on the new EC Time features. But first let me step back a bit and take a look at our time management solution in total. Cause myself and development teams are always busy with the current development release, thinking and working in 3 months release cycles. When the actual release is shipped to customers we are already working on the successor release. We are so deep in the release by release wheel that we often tend to forget what we have achieved so far in general. So, let me take this last opportunity in 2017 to step back a bit and look on our product rather from a birds perspective.
Time off started in 2012. In the beginning I don´t think many would have expected that it becomes such a flexible, comprehensive time account accrual machinery with all kinds of variation of daily, weekly, monthly, yearly accruals based on whatever parameters as it is nowadays. With a user interface that still is outstanding compared with others in its usability and attractiveness. With an intense and pre-build EC Payroll integration that covers many localization topics. With lots of business rule functions that cater for nearly all constellations.
Then time sheet and time valuation – that was started in late 2014. Only 3 years ago! Having a look on what is in the time valuation engine overall I am really proud of being part of this team. Valuation running real time, lots of flexible time valuation operations, overtime calculation, break deduction, pay type generation possibilities, working time accounts, time collectors, input validation rules and and and – all coming with a really cool user interface.
Looking on the last 4 releases of 2017 there are great enhancements as well. To name only a few: time sheet input validations, mobile time sheet, time account snapshot and balance replication to SAP Payroll, Time Account process simulator, time admin workbench enhancements, mass approval, time collectors, error messages in time sheet upon evaluated times, lots of localization features for time off, nearly a ton of new business rule functions and even new time valuation types.These are only the big ones, there are also lots of useful minor features. Check my past blogs to get an overview on what we have delivered this year. Hence, we again brought our EC Time solution many steps forward this year and I am already looking forward to 2018 where we will continue and step into a complete new topic to round up our solution portfolio by targeting the long missing clock in / out integration.
Lets have a look on customer numbers.
Where does EC Time stand at the moment in terms of customer numbers? Tremendous increase compared this year with the previous. We get next to 600 EC Time customers, thereoff more than 120 using Time Sheet and Time Valuation. Looking only on time sheet – this is an increase of 1000% within one year! Really impressive. Okay, last year we had only 10 customers and this makes the percentual increase so huge ;-). But for me it could be always like this. And it shows that customers are using what we provide and that we are heading into the right direction. That we can help customers running their business. And it shows the trend. Listening to consultants, partners and customers I can predict that this rise is going to continue next year.
When I meet with customers or got deep dive customer phone calls that are still an SAP ERP Time customer I often get the question when we will be at that level. When we will cover same than RPTIME programm with it lots of schemas and personell rules. And I always tend to say: you don´t want us to be there again. Yes, schemas and personell rules are flexible. But at the same time languaros. No innovation possible. No fast delivery possible. No implementation at low cost possible. Not an easy task to maintan for customers. Hence, no, we don´t want to be at SAP ERP Time level. Cloud is different. You need to think simpler. You have choosen a cloud solution amongst others to operate it at reduced costs than an onprem solution. You have choosen a cloud solution to manage it simpler, streamline processes, benefit from fast innovations and enhancements. This is different than onprem solution. We cannot provide all the configuration options SAP ERP Time Valuation provides. Where it takes years to implement it for customers. Where tiny specialities could be configured even only for a handfull of employees- but at a massive implementation and maintenance cost. When there would be a check of the implemented SAP ERP Time valuation schemas at customers side – how much in it is actually still needed? How many personell rules are outdated but no one knows? And how many experts are still out there who understand each and any rule in customers schemas ad hoc? SAP ERP Time valuation is a massive and strong configuration beast – with lots of hunger in terms of maintenance cost. We don´t want to be a copy of this. Rather we want deliver best practice business solutions for many of the business processes supported by SAP ERP Time – but not in the same configuration depth. In some areas we provide already more flexibility and easiness of configuration. Take our business rules or time valuation rules for example that can be understood by everyone. It is not a quasi-coding language that has to be studied like the personell rules and schemas of SAP ERP Time known only by a few (and less getting) experts. Everyone can now configure EC time valuation. And, most important, the time calculation engine runs real time. Employee records time data and it gets evaluated immediately. Not overnight like in SAP onprem Time. Always at any time accurate data available.
Customers can benefit from a more streamlined, cost saving solution that offers best practices. And this is what we do and plan to do further. Not rebuilding the old.
Now coming to the facts. What is in the box of the Q4 2017 release?
First we did a lots for data privacy and data protection. EU based consultants / customers know that next year the new GDPR (General Data Protection Regulation) comes true. This deals a lot with erasing of personell data when it is not needed for the business anymore, read access log on sensitive data, information reports on what data is stored for an employee and so on. To support customers on this issue we did a lot of developments in Successfactors and of course in EC Time.
But apart from this topic we provide again new functional enhancements in the Time area as well. Let me give you an overview before going into the details:
- New Time Sheet Amendment Process
- Time Collector Overview Page
- Time Configuration Search Tool
- Configuration Option to post working time account postings on approval
- Time Sheet Generate Job enhancements
- Role based permissions for time account balance display in termination
Lets go a bit more into details.
New Time Sheet Amendment Process
This is a step towards a more solid and “round” time sheet life cylce. As we started with time sheet and time valuation in 2014 we designed the time sheet for the limited use case of positive time recording. Hourly employees that get paid for the hours they worked and recorded in the time sheet. When a time sheet is approved and the employee adapts it afterwards (a so called amendment) but this amended time sheet was declined by the approver, we reverted the time sheet back to the last approved one. This was necessary to ensure that an employee gets paid in the next payroll run. However, this led to the result that all amendments where removed – the employee had to re-enter them. This was done because not that many amendments happen for positive time hourly recorders. Then we enhanced the time sheet for negative time (see my excursus on the difference methods below). Due to the inner logic of time sheet generate jobs each time recording of a negative time recorder is a kind of amendment. When a negative time recorder has however lots of time data recorded and the time sheet was rejected, the time sheet reverted back to the generated times based on the workschedule -which was quite cumbersome for the employee cause he had to re-do all his time recordings – even when he has recorded only allowances or on call times for example.
This has now changed. A new status approval status has been introduced into the time sheet life cycle, called, “declined”, and a time sheet with this status still contains all previously recorded data. Nothing is reverted back automatically. Employees can adapt the records that where the cause of approval decline and submit the time sheet again without having to re-enter all the other time records entered as an amendment (or for negative time recorders: deviations from the workschedule).
Here is a screenshot of the new approval status:
Based on the new status the system can send notifications to employees informing them that the time sheet has been rejected.
So, rejected amended time sheets of positive time recorders keep their data so that employees can adapt it and re-submit. As well as rejected time sheets for negative time recorder. Now, the promised excursus. When you already now the difference of the commonly used time recording methods, you can skip following part:
Excursus: Negative and positive time recording, Absence only and overtime only – what is this all about?
In time management in general there are lots of different ways of time recording. However, not that many conceptual ways of time recording, or time recording philosophy exists. I am not quite sure if the terms for the time recording methods have been introduced by SAP. I rather think that other time management systems got same terminology to describe specific ways of time recording. But I learnt only on the concepts when I attended the SAP HR306 time management course lots of years ago. Lets have a look on this different methods:
Quite easy: this is when employees record only absences like vacation, illness, jury duty. They enter records when they are not performing work or are not busy for the employer. You use this when you want to track absence entitlements (like vacation), document absences like sickness, need to send this absence records to a payroll system (unpaid absences for example to cut the salary) or simply want to provide a team absence calendar for your employees.
This employees usually are salaried paid employees.
This is covered with our Time Off solution in Employee Central.
Positive time recording
Employees need to record ALL their time data. Attendance time and absence times. The attendance time recording part can be done due to multiple reasons: the most simple one is for hourly paid employees. When they don´t record attendance times they are not paid – cause no system can calculate the hours for base pay. But even many salaried employees need to record their working time. Be it for compliance reasons, for documenation purpose, overtime calculation purpose or cause they have got a working time account where all recorded times per day are compared with the planned time and the delta is posted daily to a time account.
Now we come to the rather tricky method:
Negative time recording
Negative time recorder can be salaried (most often) or hourly paid. They don´t need to record their working time. They have got a workschedule assigned and as long as they don´t record any deviations from the workschedule, the system assumes the employee has worked according to his plan. This can mean that the time valuation calculates premiums for shift work (early / late shift premium) or for Sunday work without having the employee to record any working time. Each day the planned time of the employee is converted automatically to recorded time and time valuation gets triggered. If the employee has a shift on Sunday, time valuation calculates automatically Sunday premium.
The only thing the employee needs to record are deviations from the work schedule. Deviations are: absences (vacation, sickness…) or when the employee has worked longer (overtime), on a different day, or at a different time for example. So, each deviations from the workschedule need to be recorded. They get intermingled with the work schedule times.
And last but not least:
This method applies for all employees that only need to record those times that are in excess of their working time (plus absences when needed). These need to be salaried employees (or nobody would work for this employer ;-)). Planned times of the work schedule do not play any role here (even not to find out if the recorded time was overtime or not).
Our time sheet solution in Employee Central covers positive time, negative time and overtime only (and of course you can record absences in the time sheet as well).
Hope this helps a bit to gain a common understanding on the different time recording methods.
Now back to the Q4 features:
Time Collector Overview Page
In Q3 2017 release we shipped our “time collectors”. Please check my blog for the previous release on this (don´t let the length of the blog discourage you. The collectors are a bit a complicated topic). You find in the time admin workbench now a new tab called “time collectors” that shows nicely per employee the accumulated collector values for daily, weekly or monthly collectors, the last posting value and last posting date. You can apply filter in this UI to get an overview on only those collectors you are interested in. It looks like this:
Time admins can now easily track the progress and the balance of specific collectors per employee.
They can detect for example when an employee has worked too much late shifts in a month, has performed more than 4 on call times in the last 2 months, has worked more than 200 hours per month and so on.
Time Configuration Search Tool
Time Management can be complex and variable. Lots of workschedules, different time profiles, time valuation rules, time accounts and so on.
We try constantly to make implementation and maintenance of the configuration easier. We have provided in the past releases the time valuation trace that gives you details on the applied time valution rules and results, we have provided the time account accrual simulator that simulates the time account accrual giving you the chance to review and adapt the accrual rule when the result is not what you want to get and there is also the time configuration check tool that checks all configuration for an employee and gives you error messages / warnings when there are inconsistencies or errors in the configuration.
And now we provide another piece that facilitates system maintenance: the time configuration search tool. This tool allows to search for configuration objects that are directly or indirectly assigned to employees. You can get a list of employees that have got a specific time account, work schedule, holiday calendar, time type, time type profile, time recording profile for example. This tool is quite useful and we will enhance it further in future and incorporate for example even time valuation rules and time type groups.
Here are two screenshots that show the search for employees with a specific workschedule and public holiday calendar:
Search tool with search for employees with time profile “CLT – Standard”:
Search tool with search for employees with public holiday calendar “Holiday Calendar (DEU)”:
Configuration option to post working time account postings on approval
This new feature is a rather small one, albeit important one. Working time accounts are a kind of enhancement of the time off in lieu accounts and we shipped them some releases ago. Upon each time recording the daily sum of attendance and absences hours (depending on your configuration) are taken and compared with the planned working time of the day. If less hours are recorded the delta is posted as a minus booking to the working time account, if more hours are recorded the delta is posted as a positive value. This is a kind of “flexible working time” where overtime is not paid for each day that an employee works longer, but rather balanced out in the future course. The employee can accumulate additional day offs by working longer on some days (of course specific rules can be applied that an employee does not record more than 10hours per day or more than 50 per week for example) or he can leave earlier on friday when he has worked longer on other days.
Up to this release the working time account difference was posted regardless if the time sheet was approved or unapproved. Immediately upon time recording the working time account was filled. This allows for example an employee to work on Monday two hours longer and leave on Friday two hours earlier even when he submits his time sheet only on Friday and approval did not take place. Based on customer feedback we provided now the same configuration option as for time off in lieu accounts: you can configure if you want to have an instant working time account posting – or only a posting after the time sheet approval.
Here is a time sheet with a working time account:
Time Sheet Generate Job enhancements
Although we got a real-time time valuation running there are nevertheless some jobs necessary that run in the background.
There is for example a job that generates for negative time recorders daily the planned working time as actual hours worked. Or that submits time sheets for negative time recorders automatically at the end of the week (cause you don´t want to have the negative time recorders need to submit their time sheets although they have none deviations recorded, but worked exactly according to the workschedule.) Or when working time accounts are configured and employee has not recorded any times for yesterday time valuation needs to run nevertheless, detect this and post a working time difference. And there are a couple of other reasons why some time sheet jobs need to run in the background.
Now there might be in rare constellations the situation that the time sheet generate jobs can´t be finished and no time sheets are generated. We have now put mechanisms into place that detect this constellations and re-runs the job automatically. Hence this caters for data quality and less manual steps for customers to review the job logs and re-run the jobs manually.
In addition you can now start the time valuation manually for one or many employees and trigger an instant recalculation. This might be the case when you change time evaluation configuration for the past and you want to re-evaluate specific employees. You need to create a recalculation event via manage data and set the flag “start on save”. You can either choose an employee or a time recording profile (and then all employees with this time recording profile are recalculated).
In the screenshot above you see a second new feature: trigger of a recalculation event for a specific public holiday calendar.
This was done for customers in China (and some other countries). In these countries there are ad hoc announced public holidays. This public holidays are announced in the course of the year and for the actual year. Changes in public holiday calendars when they have already been assigned to employees in the job information did so far not trigger a recalculation event. Hence absences that that was recorded on such a day have not been re-evaluated. To overcome this you had to assign a new public holiday calendar with the newly announced public holidays in it to the employees. This triggerd a recalculation cause it was a new assignment in the job information. But to change the job information was regarded as a cumbersome process by customers. Hence we enhanced our solution: you can now adapt an already assigned public holiday, create a recalculation event and absences, time accounts and time sheets are recalculated and you don´t need to assign a new public holiday calendar anymore.
Role based permissions for time account payout balance display in termination
Some customers don´t want to show in the termination portlet the time account balance as of termination date. You can now configure with this new permission if the balance is shown or not in the termination process.
And we provided again three new business rule functions for time off that deliver:
– Job information string field value on key date
– Job information numeric field value on key date
– number of working days or hours for a period
So, that´s it. This were the Q4 features in EC Time.
Then a glimpse on next year: What´s up to come? I am happy to announce that we finally started to get into the topic of clock in / out terminal integration. For the ERP folks: this will be a cloud equivalent for the HR PDC interface (or for those of the early days: CC1 interface). We gonna work on this in the course of next year and I´ll keep you posted in my blogs on the progression of it. Goal is to provide a proper punch in / out or clock in / out interface, we do the pair formation and all the rest of business standard processes that needs to be build around this topic.
Best wishes for all your EC Time implementations. Feedback is welcome.
If we dont get to that level of SAP time off functionality, one feature I would really like to see is the availability of standard reports and time domain to add calculated fields: e.g.
Time off results by worker, by country, by location, how much has been accrued, how much has been used,
Liability reports on how much the organization owes for each org by cost center, by country
usually liability reports are done in payroll systems. Cause you need the monetary valuation of the vacations. But the time data is needed for this, of course. We provided exactly for this use case our Time Account Snapshot API. This gives you the balances at a given date and stores it in an API. In addition there is a pre-build integration for EC Payroll that integrates the time account snapshot results to the IT0015. This can be used for liabilty reporting via Payroll. For Australia there have for example payroll schema adaptations be done in order to move the leave liability report from IT2006 to read the IT0015.
Furthermore we are currently working on an integration to IT2006 for specific countries.
For your second question: There is a standard report available (called Time account snapshot, too, but is different from the API ;-)) that should give you exactly the time data you need:
Accrual value, deduction, overall balance.
I attach a screenshot.
We are trying to consume the TimeAccountSnapshot API in HCI to fetch the time data. But we aren't able to see it in the list. Not even in the Integration center.
We have set the API visibility as Read Only and performed the metadata refresh as well.
Is it hidden by design? How can we get to see the API in Integration Center or HCI/Boomi.
I just learnt that the API is not white listed for public usage, only for internal EC Payroll customers. Which is a surprise to me as well. We will white list it so that it can be used. I try to get it done in 1808 - but this will be difficult due to the close development end for that release. If not we plan it for the 1811 release.
Is there anything related to time account is that Time account will be valid until certain date or week from the date of time account creation. Right now I guess the validity is one year and we can extend to certain month or week by Monthly booking offset.
Let me elucidate further with an example.
If we create a Time off in Lieu time account which will valid only for 2 months from the date of time account created.
Eg. If an employee gets a time account for Time Off in Lieu created on 2nd Jan. Then this account will be valid until 2nd March. After that, the time account will get closed automatically.
This will be helpful if you are giving a comp off to an employee who worked on weekends or public holiday. But this Comp Off will be valid only for 2 months and if the employee does not utilize his Comp off within 2 months then this Time account will be closed automatically.
why should this not be possible? We are very flexible regarding time accounts and you just need a bit creativity ;-).
But first: is this really the requirement to limit a time account to 2 months? I know those customer requirements that say: each performed overtime must be compensated within 2 months. But not the full time account as such. Hence each overtime time account posting would need to have a counter that invalidates it after 2 months but the compensation account overall still exists. I had often heard this kind of requirement as a consultant but I dare to say that there is no time solution out there that can do this. SAP onporem can´t do this neither. You would need to evaluate each day if a time account posting crosses the 2month threshold. Cause you would not create for each overtime performed on a weekend a dedicated time account. You would post all overtime into 1 time account - but each posting should have only the deduction period of 2 months. And what when the employee gets ill for 4 weeks inbetween and there was not the chance to for compensating? When you start asking this kind of questions to customers they usually agree that this makes not much sense. And besides - no employee would be prepared to work overtime anymore when those hours are just set to zero. Rather there is a quaterly set to zero of the overtime account then. Each employee knows this rule, it is easy to understand and it is a transparent regulation. No one would be prepared to work overtime anymore when he could not utilize the comp off. Imagine you work 5 weekends within 2 months - got 5 different compensation accounts each with a different end date. This is completly intransparent for the employee and he would not know when to compensate which performed overtime.
But if really the requirement is to have 1 time account only for a limited period, here is what you need to do:
Assign the Comp off account to the time profil with validity day/month offset 2/3. The account gets then created with validity start date 02. March for example. End date is end of year (for yearly accounts).
You then perform an interim time account update with an interim time account update rule that limits the validity date to a certain date (here you can choose 02. June then). You need to select for the update run the toil account and a period that contains the 2. March.
When you really want to close the accounts you run another interim time account update afterwards that closes this accounts.
Wow - I would suggest that you don't understand how agreement/award interpretation works in some countries if you think the ERP time valuation function shouldn't be replicated.
We all appreciate that a simplified Cloud solution has its place with some customers but for others, a Hybrid solution is the best answer.
We all need SAP's sales strategy to recognise this and stop trying to sell customers solutions that they're disappointed in.
Also it does not take years to implement ERP time/payroll - only if Accenture etc are doing the implementations and milking the customers - the rest of us do it in 1-6months for a full solution.
I'm loving a lot of the SF features but there is a big gap between the sales hype and reality of delivery for existing ERP customers.
This blog has been really helping for knowing what's coming - thanks.
Thanks for the detailed updates on EC Time...we work with many SAP on-premise and now net new mid to smaller sized customers that are looking for this kind of simplified Time functionality. That said, you mention some 2018 items that I saw on the official roadmap document you linked to.
Is there anything you can confirm regarding a simple 'soft clock-in/out' capture type of app or functionality that is in the works? This would go a long way in helping to shore up the positioning of EC Time functionality to all customers, specifically those in the Retail/blue collar/high turnover hourly worker environment. Even if it were to only support start/stop time capture without Cost Center allocation it would be great...anything you can confirm (or deny) on this functionality?
thanks for the comments.
Clock in / out will be the major big topic for us in 2018, indeed we started working on it already. It won´t be only a "soft clock-in-out", we target to deliver an full fledged feature comparable with SAP onprem Time clock in / out features. With dynamic break deduction, flextime bandwidth, core times, manual time punch correction with approval workflow, error and alert messages and so on. Of course, as you know, this is a big topic. We build and ship in an incremental way hence it will take it´s time to have all this pieces build. But depending on the customer requirements -that are very variable regarding this topic- it might be that some customers can use this earlier than others. So, stay tuned in my blogs and release updates to be informed on which piece we ship when.
Hope this helps
Awesome Blog, well written and informative blog. You can Visit www.idcubesystems.com
Can we get a target date for the first release of a simple 'soft clock'. We have people deciding on solutions that are using that as a big criteria.
unfortunately not: Product Management is not allowed to give such kind of target dates. There are too many things that can interfere and delay a shipment and then we get in trouble with customers who rely on the dates we gave.
A "soft clock" won´t help neither - cause what does it help when the data is send to EC Time - but lots of processes that come with clock in / out are not working as customer expects? Workflow for forgotten punches, alerts and notification, more enhanced break handling....
We are already working on the clock in / out integration and accompanying business processes. But this is a big topic. I can only tell for sure that we won´t be able to ship anything before end of year. Maybe this helps for the decision.
And please don´t take the statement in a way that there is a guarantee that something is shipped regarding clock in / out end of year. There is no guarantee.
Excellent content ! May I ask if the followings will be in the pipe-line ?
Thank you and regards,
for 1): trouble shoot for 1 employee was actually not the use case we had in mind. It was rather intended to provide a kind of test environment when time accounts and accruals are set up. We don´t have currently planned to include inactive employees here.
for 2): you can´t run it for a single employee. But the calendar run is clever enough to see that when you choose a time account and 10.000 employees have already this time account but only 1 not, than only this 1 employee is processed and not all 10000. However I have heard it from other customers as well that it would be fine to select a single employee. When we have done most of our bread and butter things we can focus on these fine tuning requirements.
I'm trying to regenerate the absence calculation because i have added new holidays to my holiday calendars. I'm following what you said about "Time management recalculation event" but my job is not triggered and nothing is recalculated.
Can you advice please?
Please describe which steps you performed.
This is what i did in the Recalculation event.
But i don't see anything happing when i save.
change the field target type from "user" to "public holiday calendar".
Cause you don´t want to recalculate single employees, but all employees who got this public holiday calendar - this is much more efficient and it will work 😉
And choose the public holiday calendar you have adapted in the target ID field.
Where can we found the Configuration Option to post working time account postings on approval? For the moment i'm only able to have the system directly putting the hours in the time account, the manager is getting the approval but hours are already posted before the approval is done?? and even if manager declines the hours are staying in the time account?
This would be a big help!
Possible. It is a setting in the time profile.
See attached screenshot.
Default is "No", means approval is not regarded (just like in SAP ERP - and there was no configuration option at all to change this ;-)).
Upon rejecting the balance stays, this is true, but as soon as the time sheet gets opened again the recalculation is triggered and the balance is reverted back.
Thanks Volker, that helped 🙂