We recently completed our upgrade to JD Edwards 9.2.0 using the standard Oracle Upgrade Manager process. Everything went smoothly during the upgrade itself, but now we’re encountering critical issues with payroll processing.
When running payroll for the current period, the system throws errors indicating pay period mismatches. We’ve reviewed the fiscal date pattern configuration and verified our pay period tables (F0609 and F069116) appear intact. The strange part is that no customizations exist on our payroll calendar logic - this is completely standard Oracle functionality.
The error occurs specifically when trying to process bi-weekly payroll cycles. Monthly processing seems unaffected. Our payroll team is blocked and we need to process this week’s run. Has anyone experienced similar pay period alignment issues after upgrading to 9.2.0?
I dealt with this exact scenario last month during a client upgrade. The root cause stems from how the Oracle Upgrade Manager handles fiscal calendar data when migrating to 9.2.0, particularly for bi-weekly pay periods.
Since your upgrade followed the standard Oracle process and you’ve confirmed no customizations exist on payroll calendar logic, the issue is definitely in the pay period table alignment. Here’s the systematic fix:
First, verify your fiscal date pattern configuration in System Setup (P0008). Ensure the pattern type for payroll is set correctly and the base date aligns with your fiscal year start. Even though you reviewed this, double-check the pattern assignment specifically for the payroll business unit.
Next, address the overlapping dates in F0609 that you discovered via R07330. The upgrade process can introduce these overlaps when converting date boundaries. Create a backup of F0609, then systematically correct each bi-weekly period:
- Period end dates should be one day before the next period’s start date
- Verify no gaps exist between consecutive periods
- Ensure all 26 bi-weekly periods for the year are properly sequenced
For the immediate fix, you can manually update F0609 using SQL (backup first):
UPDATE F0609
SET PPEDTE = PPEDTE - 1
WHERE PPFRQ = 'BW'
AND PPEDTE IN (SELECT overlapping_dates FROM your_validation_query);
After correcting F0609, run these validation steps:
- Re-execute R07330 to confirm no overlaps remain
- Check F069116 constants match the corrected periods
- Test payroll processing in a non-production environment first
- Verify the fiscal calendar assignment in Payroll Constants hasn’t been altered
The reason monthly processing works fine is that monthly periods typically have more tolerance in date boundary handling and weren’t affected by the same migration logic. For future upgrades, I recommend running R07330 immediately post-upgrade as part of your validation checklist, before attempting any payroll processing. This proactive check would catch these alignment issues before they block operations.
Thanks for the suggestion. I checked UDC 00/FY and the fiscal year definitions look correct. All our fiscal years are properly defined with the right date ranges. The bi-weekly pay periods in F0609 also have the correct start and end dates. Could this be related to how the upgrade process migrated the calendar data?
Good catch! The R07330 report showed several bi-weekly periods with overlapping dates. The frequency codes in F069116 were correct, but somehow during the upgrade, a few periods in F0609 had their end dates extended by one day, causing the overlap with the next period’s start date.
I’ve seen this before on a 9.2.0 upgrade. Even though the pay period tables look correct, there’s often a mismatch in the date format between the old and new fiscal calendar structures. Check your UDC table 00/FY for any inconsistencies in the fiscal year definitions that might affect period calculations.