Leila Fielding
Why I picked it
Oracle switched off the Create Time Card Calculation Component process in 26D. Elements it upgraded (ending in CIR) keep working, but won't get future enhancements, and have limits: no full processing history on the Earnings and Deductions page, and no retroactive overpayment and recovery.
Where it helps
A payroll team finds its elements ending in CIR, recreates them in the Timecard category, and moves future timecards across before end-dating the old elements.
What to do now
- Find your upgraded elements. Search for elements ending in CIR, and note the parent element each one came from.
- Create replacement elements in the Timecard category. Oracle says this automatically creates the payroll elements, balances, formulas and calculation components they need.
- Move future timecards across. Export them with HCM Extract, delete the ones using upgraded elements through the Time Record Event Requests REST resource and run Load Timecard, then recreate them with the new elements and run Load Timecard again.
- Then end-date eligibility for the CIR elements. You can do this in bulk with HDL. Oracle says the old elements still appear on timecards afterwards, but using them for new entries causes a Load Timecard error, so tell timecard users.
- US payroll: set up the State, County and City time card fields, a new Time Card Layout Set, and the Worker Time Entry Profile from the date the new elements start.
- Review integrations with third-party time systems that send or receive these elements.
Watch out: Oracle hasn't set a deadline. Don't end-date the old elements until future timecards have moved across, and check integrations with third-party time systems.
Last reviewed November 2026