Performance On PSA_ACCTGGL When Calling IU_PROCESSOR. A Huge Amount Of Undo Log Is Getting Generated.
(Doc ID 2346450.1)
Last updated on FEBRUARY 03, 2019
Applies to:PeopleSoft Enterprise FIN Project Costing - Version 9.2 to 9.2 [Release 9]
PeopleSoft Enterprise FIN Contracts - Version 9.2 to 9.2 [Release 9]
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
On : 9.2 version, Performance
Performance on PSA_ACCTGGL when calling IU_PROCESSOR
PSA_ACCTGGL calls IU_PROCESSOR when there are chartfields that are not in balance. We balance by Business Unit, CLASS_FLD and FUND_CODE. We use funds distribution to distribute costs to various activities, where those activities are tied to different chartfields and different billing contracts.
As a result, 1M inbound transactions can result in 4-5M FNDs and FDRs, and then when those are priced we get a resulting 2-3M BILs (not all activities are billable).
When we run PSA_ACCTGGL on Revenue, we have little to no issue with managing volumes. However, when we run PSA_ACCTGGL on Costs, and it goes to balance those costs on ps_psa_iu_ta15 and ps_psa_iu_ta25 (or appropriately obtained temp tables), the process ends up creating massive amounts of UNDO space as there is no commit. So in the case of 7M transactions that were being processed through PSA_ACCTGGL, the IU_PROCESSOR steps created a total of 355GB of undo space, which had an overall system performance issue.
PSA_ACCTGGL should not create lot of UNDO space which result in overall performance issues.
The issue can be reproduced at will with the following steps:
1. When running PSA_ACCTGGL for costs that causes IU_PROCESSOR to process data.
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