Incorrectly Able To Post Budget Journals and Budget Transfers On Project Activity at "Summary" Level; Should Only be Able to Post on Project Activity at "Detail" Level
(Doc ID 2938707.1)
Last updated on MARCH 30, 2023
Applies to:
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
Incorrectly able to post Budget Journals and Budget Transfer Journals with project Activity at "summary" level instead only correctly posting with project Activity at "detail" level.
No validation in place once line already has "summary" level project Activity. Validation only occurs when click on the dropdown of the project Activity field in the online page.
STEPS:
A.Project Costing> Activity Definitions> Project Activities, identify project Activity at summary and detail levels – e.g. for Project 12345678
--view Activity at summary level: 0001 and 0002
--then under Activity at summary level 0001, view Activity at detail levels 0002, 0003, 0004, 0005, 0007
B.Enter Budget Transfer via Commitment Control> Budget Journals> Enter Budget Transfer
1.Enter first line
Account: 123456
Fund: ####
Dept: ######
Authority: #####
PC Business Unit: XXXXX
Project id: 12345678
Activity id: 0001
2.Then add a line and it copies the same exact information.
3.In added line with project id 12345678, retain Activity 0001 (summary level) and credit amount to balance it out.
4.Then Save the journal. Send journal for approval and once approved execute Post. The journal gets successfully edited and posted.
C.Enter Budget Journal via Commitment Control> Budget Journals> Enter Budget Journal
1.Enter first line
Account: 123456
Fund: ####
Dept: ######
Authority: #####
PC Business Unit: XXXXX
Project id: 12345678
Activity id: 0001
2.Then add a line and it copies the same exact information.
3.In added line with project id 12345678, retain Activity 0001 (summary level) and credit amount to balance it out.
4.Then Save the journal. Send journal for approval and once approved execute Post. The journal gets successfully edited and posted.
Test Conclusion:
No validation in place once line already has "summary" level project Activity, e.g. 0001.
Validation only occurs once click the project Activity field dropdown.
On budget transfer journal line, chartfields tab, see that since the Activity field contains "summary" level Activity 0001, it then gets the error msg "No matching values were found".
When click on the dropdown for the Activity field, it shows 5 detail values - 0002, 0003, 0004, 0005, 0007 - thus, validating that "summary" level Activity 0001 is invalid.
Thus, users are able to enter invalid project Activity at summary level instead of correct project Activity at detail level, since budget journal entry and budget journal transfer pages are not validating the project Activity field unless the user clicks on the dropdown for the field.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |