[On Behalf of Customer] - Need better approach on performance issue - FSPCCURR
Hi All
We have performance issue with FSPCCURR and other processes such as Jrnl edit. One of the reasons could be the RT_RATE_TBL which has row count of 6,998,742. We are thinking to copy it to a separate table and truncate all the rows before 1/1/2013 in RT_RATE_TBL. We did this to LEDGER and LEDGER_BUDG per oracle support. My questions are:
1. Is the right way or you have other recommendations?
2. What is the impact to GL and Subledgers if we delete the previous year rates? I did some random testing and seems ok to bring up old records.
We have performance issue with FSPCCURR and other processes such as Jrnl edit. One of the reasons could be the RT_RATE_TBL which has row count of 6,998,742. We are thinking to copy it to a separate table and truncate all the rows before 1/1/2013 in RT_RATE_TBL. We did this to LEDGER and LEDGER_BUDG per oracle support. My questions are:
1. Is the right way or you have other recommendations?
2. What is the impact to GL and Subledgers if we delete the previous year rates? I did some random testing and seems ok to bring up old records.
0