Create Time Card Calculation Component Flow Retired
Use the Timecard category to create new timecard elements. You can no longer access the Create Time Card Calculation Components flow to upgrade standard elements to CIR time elements.
Elements previously upgraded to timecard calculation components through this process will continue to work but won't receive future enhancements. These upgraded elements have the following limitations:
- Full processing history is unavailable on the Earnings and Deductions page.
- Retroactive Overpayment and Recovery functionality isn't supported.
- Future enhancements to the timecard element template, including additional fields and functionality improvements, won't be available.
To maintain compatibility and take full advantage of these functionality, consider reimplementing the upgraded time elements by completing the following tasks:
1. Create replacement elements using the Timecard category.
2. Migrate applicable future timecards to use the replacement elements.
3. End-date eligibility for the upgraded elements after migration.
After you end-date eligibility, the upgraded elements remain available for retroactive processing. Retroactive changes entered on timecards will be detected and will trigger retropay calculations. The upgraded elements also remain available for selection on timecards, but they should no longer be used for new entries because doing so will generate a Load Timecard error.
- Reliable time-entry status tracking: Timecard elements retain key source attributes, such as Creator Type and Creator ID, to help identify where entries originated and track their payroll-processing status.
- Flexible support for time-based payments: Timecard elements support hours, days, and other units for regular and overtime pay, premiums, allowances, meals, on-call work, piecework, and similar scenarios.
- Less setup and maintenance: Creating a timecard element automatically generates the associated payroll elements, balances, formulas, and calculation components required for processing.
- Ongoing Oracle feature compatibility: Timecard elements use Oracle's supported template model, helping maintain compatibility with current and future Payroll and Redwood capabilities.
Steps to enable and configure
- Identify upgraded elements. The Create Time Card Calculation Component process creates an additional element with the CIR suffix. Search for these elements and identify the corresponding parent elements that need to be reimplemented.
- Create replacement elements using the Timecard category. See Create Time Card Elements for Time Entries and Create Time Card Elements for Global Payroll Time Entries.
- Export future timecards using HCM Extract.
- Identify and delete future timecards that use the upgraded elements. You can delete them in bulk using the Time Record Event Requests REST resource. See Time Record Event Requests REST Endpoints.
- Run the Load Timecard batch process to remove the deleted timecard entries from Payroll.
- Recreate the future timecards using the replacement Timecard-category elements. You can use the Time Record Event Requests REST resource. See Time Record Event Requests REST Endpoints.
- Run the Load Timecard batch process to transfer the recreated timecard entries to Payroll.
- End-date eligibility for the timecard elements with the CIR suffix, as identified in step 1. You can update eligibility in bulk using HDL. See Example of Updating Payroll Element Definitions.
You will need to review your incoming and outgoing integrations with third parties such as time management systems.
For the US, Oracle provides location time attributes that transfer to Payroll after final approval: ORA_HRX_US_EARN_STATE, ORA_HRX_US_EARN_COUNTY, and ORA_HRX_US_EARN_CITY. Those are different to the one used for upgraded elements. The following changes are needed:
- After creating new time elements (Step2 above), ensure to configure State, County, and City time card fields.
- Create a new Time Card Layout Set containing these fields
- Associate it with the Worker Time Entry Profile effective from the date the new elements are intended to be used.
For further information, refer to Configure US Location Override Fields in the Unified Time Entry Experience