Redwood Time & Labor — Planning Your Move
Everyone is talking Redwood for Oracle SaaS solutions, but let’s focus on Time & Labor (OTL). OTL stands out as one of the select modules that influences both Human Capital Management (HCM) and Enterprise Resource Planning (ERP). It serves a dual purpose: tracking time for payroll purposes and allocating costs within the Project Portfolio Management (PPM) module.
With the upcoming Release 24D, the transition to Redwood Timecards becomes compulsory, signalling the end of support for Responsive Timecards. What does this entail? Post 24D, no bug fixes will be issued for Responsive Timecards. Moreover, should you submit a Service Request (SR) to Oracle concerning a Responsive Timecard, the recommended resolution will be to switch to Redwood. Considering that Release 24D is on the horizon, less than six months away, it’s crucial to start planning your migration immediately.
As you start on the transition to Redwood, there are several key factors to consider. Security takes precedence; employees must possess edit rights to submit timecards, a shift from the current Responsive system. Similarly, managers will need edit rights to approve timecards directly within the interface.
Furthermore, please be aware of the following updates: 1)The Timecard Template now supersedes the ‘Copy Other’ feature found in Responsive timecards. 2) There is no support for daily details. 3) The Cost Override Layout is not supported. 4) Calculated Time has a new look (refer to the above screenshot). 5) For customising the sequence of timecard fields, the new unified layout is required.
So what are the benefits of the Unified Layout? It’s much simpler to configure, there is only one layout for reported time, calculated time, entry, edit and view. The guided process has been streamlined, so there are just three steps — display properties; timecard fields and time totals. The timecard attributes can be configured by role — Worker, Line Manager and Time & Labor Manager. Additionally, it is possible to filter the data sources by role.
What do you need to consider before you turn on the Unified Layout? The great news is that the delivered time entry layout components will continue to work! There is no need to set them up again. From a security role perspective, Time & Labor Administrators can edit existing non-unified layouts, but they cannot create new ones. The unified layout can include a combination of non-unified and unified timecard fields. If you have dependent timecard fields on a non-unified layout, they must be switched to independent timecard fields when moving to the unified layouts. Finally, if you need to be able to control the order of the timecard fields on a Redwood timecard, you must use the unified layout.
Oracle is set to introduce new features in the 23C and 24D updates. However, all essential functionalities required for transitioning to Redwood Time Cards are currently accessible. It’s advisable to activate Oracle Search and configure the necessary profile options for OTL within a separate pod for thorough testing. Familiarising yourself with the system through hands-on experience is vital for devising a realistic deployment schedule for Production before the 24D release.
Learn more about how Version 1 can help you maximise your Oracle Cloud instances here.
About the author:
Kate Mead is an Oracle-certified HCM Consultant and Solution Architect at Version 1 with 14 years of experience in Oracle HR and Payroll systems, including 7 years with Oracle HCM Cloud. She has worked across implementation projects and managed services, has a sound knowledge of UK Payroll legislation and — before becoming a consultant — was an HR Manager.
If you have any questions or would like more information on how Version 1 can help you realise the full potential of your Oracle Cloud instances, please contact her at kate.mead@version1.com
Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines
