Best Of

When drilling down from GL, View Transaction appears to do nothing

This is to share some info to potentially help someone else in the future. We have version 12.2.12 and the product is General Ledger.

In Inquiry > Account, select an account and click Show Journal Details then click Drilldown. The View Journal Entry Lines form appears in a browser window.

If you click View Transaction and it seems like nothing at all happens, the issue could be that pop ups are blocked so a message such as "frmservlet.jnlp could harm your device, do you want to keep it anyway" isn't being shown. Look on the URL address bar at the top of the screen and check for a small icon after the address. Hovering over the icon shows that pop ups have been blocked. Click on the icon and choose to allow pop ups from your EBS. Click on View Transaction again. This time, the message should be shown and the user can choose to Keep the file and then the java window will open and display the transaction.

This seemed like a useful addition since some searching found posts on how to respond to the message, how to make jnlp open automatically and so on, but not one for no message appearing at all.

J Reinhart

1

Re: Duplicate Supplier / Vendor Cleanup FSCM 9.2 Image 43 Tools 8.61

We have been through this exercise a few times over the years. I've seen a few things done.

Depending on if there are open transactions for the supplier (req's, PO's, contracts, items associated, Sourcing Events, RFQ's, etc.) we have requested that any open activity be closed so the vendor can be inactivated and any items where the supplier is listed as a priority be moved to the new or duplicate supplier.

I believe in those cases our AP group changes the vendor's name to do not use, use vendor xyz. At least then folks can see, if they try to use the supplier to use the supplier number we want to go forward with. I think this has been done for ages, regardless of the path forward.

Like this-

In other cases, I've seen where we make the supplier not open for ordering. This seems to allow active transactions to naturally clear up on their own, but new Req's or PO's can't be created. Although, this may take a while before that can happen. In this case, the items, if there are any should be moved to a different supplier.

There's been some conversation about allowing the supplier to be updated on the PO, but from a legal perspective, even if they are duplicates in your system that could get a little weird. We currently do not allow the supplier to be changed on a PO once it's been dispatched.

Although, there's been a case or two where we have made an exception and changed configuration to allow it- for that situation only and changed it back.

In some cases, new contracts have to be created using the supplier to move forward with. In others, it seems we have created a new contract version and changed the vendor for that version. That seems to mostly work. The idea is to make sure new req's or PO's created reference the appropriate contract.

In our situation, we also have to consider integrations to other systems. That always adds some spice to an already spicy situation. lol

Let us know if you have questions.

Happy to help! 🌶️

Wendy Jamison

2

Re: How to copy WBS, Activities, and Relationships from 3 separate projects into one project

From any existing project, you can go next to a WBS Root or lower and go to far left until the GEAR Icon appears, then click it and select ADD WBS from existing Project… then simply choose where it is and bring it in. Use details to select what all you carry in with addition.

Matthew Milliet

2

Re: Notifications when an SR is created in our group

Thank you @Margi-Oracle

Cindi Jacobsen

1

Re: Question on FAL (Fetch Archive log) on Data guard

Question1. The sequences (archived logs) needed (for both threads) to resolve the gaps were luckily still on Primary DB's FRA diskgroup.
So, at one point, I was thinking of copying out those archived logs from Primary to Standby manually.

But, isn't the FAL mechanism in dataguard supposed to automatically copy ('fetch') the archived logs from primary when real-time/synchronous redo apply fails for some reason ?

Answer:

Yes, that is true. Please check the RFS trace file from standby to check for the reason. I can see the below error message in the alert log. So there seems to be network issue.

Last contact from redo source occurred at 09/23/2025 22:07:24,

Question2.

My colleague did the following on the standby DB and then the MRP went from WAIT_FOR_GAP to APPLYING_LOG state and then the gaps were getting resolved and eventually the gaps for threads got resolved. CDB_05P mentioned below is the primary DB Unique name.

Answer:

Have you captured the status of remote destination at that point of time before you restart the transport processes. We may need that to check what was the status before the restart.

SethuKanthiah-Oracle

1

Re: Release management Introduction and step by step setup Documents

These documents are very informative and helpful. Thank you!

User_15AHV

1

Re: Savings Age Catch Up Extension Page-2 New Check Boxes

Hi,

The PeopleSoft Benefits development team had postponed the delivery of the Base Benefits and Benefits Administration Roth Age Catch-Up enhancement for SECURE 2.0 – Section 603. As of Friday, September 12, 2025, they were awaiting IRS guidance for the January 13, 2025, proposed regulations, 26 CFR Part 1 [REG-101268-24], regarding Catch-Up Contributions. On Monday, September 15, 2025, the Treasury and IRS published the final regulation regarding the new Roth catch-up rules and they are currently reviewing the 94-page final regulation.

The PeopleSoft Benefits team requires additional time to analyze and develop the follow-up changes to the internally developed catch-up contribution process in line with the new final regulation. A PeopleSoft Release Patchset (PRP) will be issued as soon as possible following the release of HCM Image 53, and prior to the target posting date for HCM Image 54, but no anticipated delivery date is available at this time.

Regards,

Joyce