Best Of
Re: 27 vs 26 bi-weekly paychecks in CY 2026
Hi - I don't recall ever doing anything special. I searched through MOSC and there were some documents mentioned (links are updated because the old links won't work anymore):
Benefits Administration Annual Amounts not Correct for 27 Pay Periods
EPY: Garnishment exemption amounts can be incorrect with 27/53 pay periods in year
EPY: Bi-Weekly Employees Compensation Reduced Due to 27 Payroll Periods
EPY: How do 27 or 53 Annual Pay Periods Effect the Tax Calculation for US Taxes
EPY: Setting Up 27 Pay Periods for Bi-weekly Pay Using PS_FREQUENCY_TBL
EPY: Garnishment Flat Amount Calculation Can Differ when 27 or 53 Pay Periods
Re: 27 vs 26 bi-weekly paychecks in CY 2026
Our agency went ahead and began testing payrolls, as we did not want employee pay to be reduced. The pay period 12/19/25-1/1/26 calculated gross the same amount in test, not reduced. We were thinking ours might be counting paycheck dates since we will have 27 pay periods but still only 26 paychecks. Our payroll staff also intends to run every payroll until they can get to 12/18/26-12/31/26…I believe they wanted to confirm insurance. We were thinking we were in situation (3) on the following article (included in Nicole's response above) and therefore might have had to plan to customize the PSPPYRUN COBOL:
Our staff is somewhere around May 2026 of their testing and has not yet reached the final pay period of 2026. We are optimistic since 12/19/25-1/1/26 looked okay.
Re: Standby database MRP problem WAIT_FOR_GAP
Yes, I understand now. Thanks I will try to fix the problem with unregister.
LunaTaxi
Re: Patch 38764390: SECURE 2.0 SECTION 603 ROTH CATCH-UP PATCH 2 - PEOPLECODE FOR ROTH THRESHOLD CHECKBO
Thank you very much for the information. We'll request to download all 5 patches.
Sheetal
Re: Patch 38764390: SECURE 2.0 SECTION 603 ROTH CATCH-UP PATCH 2 - PEOPLECODE FOR ROTH THRESHOLD CHECKBO
Hi Sheetal,
As stated in the initial announcement on this thread, PRP 38764390 was posted on December 19. It included patch 38750590.
Regards,
Joyce
Re: Subinventory Transfer Results in Negative Balances Not Allowed
Re: 38615240 Release Notes
Hi,
If you go to:
https://support.oracle.com/support/?kmContentId=10986173&page=sptemplate&sptemplate=km-article
(Payroll for North America Tax Updates - KA643)
Scroll down to:
HCM PRP Patchsets for Update Image 9.2.054
I was able to download this successfully.
Customization Insights in PeopleTools 8.62
PeopleSoft 8.62 introduces a great new way to reduce the cost of managing your PeopleSoft applications.
The new Customization Insights dashboards will provide a deeper understanding of how customizations impact you. Enabling Usage Monitor in your production system will allow you to identify unused customizations that might be candidates for removal as well as helping you to find expensive customizations in your system.
Read more about this great new feature from PeopleTools Strategy Director, Dan Iverson in this blog article.
Re: Resubmitting a Requisition in PO Canceled Status
Howdy,
I am not sure what PeopleSoft considers correct, other than creating a new requisition. I am not sure if you use the fluid req or not. We are still using ePro.
I think delivered, if you cancel a PO/line PeopleSoft also cancels the associated requisition lines. In ePro and in fluid, you can still undo- cancel.
Looks like you can also copy a canceled requisition.
We ended up customizing, if you undo-cancel or copy and also use auto-source, you end up sourcing to the same supplier again. Often, the supplier indicated there was a reason they could not provide what we ordered.
If we cancel a PO or PO line the associated requisition line(s) are set to RFQ required and the supplier removed. This appears in the buyer's req's to be sourced again and then they can figure out where to go next.
Idk if that helps at all.
Wendy 🌻
Re: Bug#35596820: Added the ability to enter AR direct journals using Microsoft Excel spreadsheet upload
The above knowledge base document is not working after the oracle support upgrade. Can you please check.