My Oracle Support Banner

E1:07/07Y/77/77Y: Year-End Rollover (Payroll Month & Calendar Month ) Frequently Asked Questions (Doc ID 1916609.1)

Last updated on MAY 26, 2022

Applies to:

JD Edwards EnterpriseOne US Payroll - Version 9.2 and later
JD Edwards EnterpriseOne Australia/New Zealand Payroll - Version 9.2 and later
JD Edwards EnterpriseOne Canadian Payroll - Version 9.2 and later
Information in this document applies to any platform.


This document provides frequently asked questions regarding Year-End Rollover (Payroll/Calendar Month).


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Question 1:  Why is the R07390B Calendar Month Rollover not calculating the rollover amounts/balances?
 Question 2:  What Year End Rollover business functions and/or UBEs need to be mapped to run the process on a local machine?
 Question 3:  Why would a blank report be created when running the year-end rollover?
 Question 4:  Why is the rollover process not updating the F06146 when run in Final Update mode?
 Question 5: Can the calendar month final rollover process be run twice?
 Question 6: Why is the rollover process updating the F06146 with unexpected results?
 Question 7: Should the Year End ESU be installed before running the year rollover?
 Question 8: When running the year end rollover (P07390) for PTO accrual we are also getting F06146 record for PTO taken created. How do we suppress this?
 Question 9: We ran the Payroll Month (R07390A) program but should have run the Calendar Month (R07390B) program to rollover our vacation and sick PDBAs.  We were also a week early.   The Calendar Month rollover didn't need to be run until next week when we process the 12/30 and 12/31 work dates.  What is the impact?  How will this affect our 2020 PDBA balances?  
If needed, how can we go about correcting the issue?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.