Clarification on PUM Enhancement bugs 26102256, 27530289 and 26075668
(Doc ID 2504534.1)
Last updated on JANUARY 08, 2020
Applies to:PeopleSoft Enterprise FIN Grants - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
On : 9.2 version, Functionality
PUM enhancement questions
Please provide responses to the questions regarding PUM enhancement bugs
Bug ID 26102256: Enhanced the Grants Facilities and Administration feature to prevent costs from being processed based on certain conditions, such a pre-award spending and overspending. This is achieved by assigning a specific status and being able to place the transaction on hold. This feature is in response to OMB Uniform Guidance CFR200.
Question: What is the impact of placing a transaction on hold? Where/what does it impact downstream?
Bug ID 27530289: Enhanced the F&A process feature so that the accounting date on new system generated F&A transactions are brought forward from the original source cost transaction. In addition, the effective dated revenue offsets are based on the accounting date from the source cost transaction, rather than the current date. This provides a consistent use of effective dating for the standard F&A process and the retroactive F&A process, using the accounting date on the transaction.
Question: Is there demo data in Image 30 that we can validate this enhancement?
Bug ID 26075668: Added the Modify End Dates feature to provide an efficient method of updating end dates in Grants, Contracts, and Project Costing. This feature adds a one-page utility to update the award end date, related contract lines, associated projects and activities, as well as funding and award modification dates.
Question: Is Commitment Control also included? Will the End Date also update Commitment Control using this page?
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