Best Of
Re: Asking about installing Solaris 11.4 security patch without SRU upgrade
Hi,
There isn’t a supported “security-only” update stream that lets you apply just security fixes while staying on the same SRU level. Most security fixes arrive as part of an SRU (and sometimes require other dependency updates), so applying security fixes typically advances you to a newer SRU.
Thank you!
Regards
Saravanan
Re: Expense Payment Holds
Hi @Evelyn ,
Hope all is well.
Welcome to the PeopleSoft Financials Community and thank you for posting your question!
There is no way on these pages, you can find the user id who had put the hold. There is no audit for these pages.
On the Expense payment page, the back end record has the last updated date time field but not the user.
I hope the information provided has clarified all your doubts. Should you have additional related questions, do not hesitate letting us know. On the contrary, if all your queries, and doubts have been successfully addressed, please mark this reply with a YES on the question listed at the bottom of the post ('Did this answer the question?'). Only the user who created the initial question can perform this action. This will enable other Community Users to quickly identify the solution suggested, and see that this post has been successfully answered.
Thanks,
Rajani
Expense Payment Holds
Is there a way to find out which user put an expense report payment on hold from either the Expense Report Payments page or the Pay Cycle Details page?
We are on PeopleTools 8.61.17 Image 54.
Re: how to fix error message "accounting distribution for the prepaid is not valid."
Actually, error message is because of the Combo Error. Please advise how to fix that..
Re: DBSAT report error Error: Java version 17 or later is required.
some of them
should work
https://www.oracle.com/de/java/technologies/downloads/
Re: PeopleSoft Receivables - Adjusting a closed item
@JulietC ,
Juliet,
We'd love to see something similar — a way to post an adjustment of some sort to a closed item, resulting in reopening the item. We see this with payments - where we discover later on that a payment was posted to an incorrect item — and correcting that across fiscal years can be incredibly difficult and convoluted, especially when using commitment control as well. From unreconciling, opening prior periods, unposting, entering new deposits, reapplying, reposting, and addressing commitment control exceptions due to prior period closures, ensuring transactions go to current accounting periods, reposting, and re-reconciling). Whereas ultimately, we want to "reopen" a closed item with a "correction". I was working on exactly this type of issue just today!
We need to maintain as much traceability and auditability back to the Grants, Project Costing and Contract as possible, as it has impacts on reporting for Federal Draws, LC_ID / LOC_DOC_ID reporting, grant reporting, CMIA reporting and so forth.
Seems there may be two use-cases:
- For Open Items — How to make an adjustment to previous activity without having to unpost all subsequent activity
- For Closed Items - How to make an adjustment that can reopen the item, without having to unpost a payment / maintenance action.
@Gail-Oracle / @Georgeta Moraru - Oracle-Oracle —> are there any ideas in the idea space related to this sort of functionality already?
@Richa_Dubey123-Oracle —> Is this something you could perhaps add to a future Focus Group meeting to discuss how customers are doing this today, and whether there is a greater need for this type of functionality? I'd be happy to speak to it in the Focus Group if you'd like. Seems it would tie in with the NSF discussion too.
Robert
Re: PeopleSoft Receivables - Adjusting a closed item
Hello,
Reversal in AR is performed by unposting the transaction. This behavior is expected under the current design and correctly updates both the customer balance and the related accounting entries.
Regards,
Oracle Support
PeopleSoft Receivables - Adjusting a closed item
We have a number of situations where we need to reverse an older transaction.
We are aware of the unpost process but have issues where, for example, there are too many subsequent transactions and unposting is too complicated/involves too many other records OR where a subsequent transaction is a direct debit payment and is not suitable for adjusting as the direct debit group is too large.
Example - a payment was received and applied OA to an account, this was then matched to a new invoice via the automatching process, a direct debit them collected the remaining balance of the item. At a later date it became clear that the OA should not have been applied to this account. To keep an audit trail we would like to remove the matching and the OA payment from the item but we cannot do this due to the subsequent direct debit (this group needs to be unposted first).
Is there anyway to make this sort of adjustment to a closed item WITHOUT having to unpost all subsequent maintenance transactions first?
JulietC