FAMACR/APMACR EXTREMELY POOR PERFORMANCE AFTER APPLYING FA PATCHSET K

Question

제품 : FIN_FA
작성날짜 : 2005-11-28
FAMACR/APMACR EXTREMELY POOR PERFORMANCE AFTER APPLYING FA PATCHSET K
======================================================================
PURPOSE
FA_MASS_ADDITION시 Expensive sql로 성능저하 문제 발생
Explanation
Expensive sql statement while running the report is
update ap_invoice_distributions apid set assets_addition_flag='N'
where (((((assets_addition_flag='U' and assets_tracking_flag='N') and not
exists (select 1
from ap_ae_headers aeh
where ((aeh.accounting_event_id=apid.accounting_event_id
and aeh.set_of_books_id=apid.set_of_books_id) and aeh.gl_transfer_flag<>
'Y')))
and posted_flag='Y') and accounting_date<=to_date(:b0,'YYYY/MM/DD HH24:MI:
SS'))
and exists (select 1
from gl_code_combinations
where ((code_combination_id=apid.dist_code_combination_id and
chart_of_accounts_id=:b1)
and decode(upper(:b2),'SEGMENT1',segment1,'SEGMENT2',segment2,'SEGMENT3',
segment3,'SEGMENT4',
segment4,'SEGMENT5',segment5,'SEGMENT6',segment6,'SEGMENT7',segment7,'SEGMENT8',
segment8,'SEGMENT9',
segment9,'SEGMENT10',segment10,'SEGMENT11',segment11,'SEGMENT12',segment12,
'SEGMENT13',segment13,
'SEGMENT14',segment14,'SEGMENT15',segment15,'SEGMENT16',segment16,'SEGMENT17',
segment17,'SEGMENT18',
segment18,'SEGMENT19',segment19,'SEGMENT20',segment20,'SEGMENT21',segment21,
'SEGMENT22',segment22,
'SEGMENT23',segment23,'SEGMENT24',segment24,'SEGMENT25',segment25,'SEGMENT26',
segment26,'SEGMENT27',
segment27,'SEGMENT28',segment28,'SEGMENT29',segment29,'SEGMENT30',
segment30) in (select distinct asset_clearing_acct
from fa_category_books fcb ,fa_book_controls fac
where ((fac.book_type_code=:b3 and fac.book_class='CORPORATE')
and fcb.book_type_code=fac.book_type_code)
union
select distinct cip_clearing_acct
from fa_category_books fcb ,fa_book_controls fac
where (((fac.book_type_code=:b3 and fac.book_class='CORPORATE')
and fcb.book_type_code=fac.book_type_code) and cip_clearing_acct is not null ))
call count cpu elapsed disk query current
rows misses
Parse 1 0.03 0.03 4 7 0
0 1
Execute 1 5198.88 5241.95 258933 99354479 9946808
0 0
total 2 5198.91 5241.98 258937 99354486 9946808
0 1
cause: The Cause of this problem is still undetermined.
fix:
1. Apply Patch:2395191
자산화하기 위해서는 Invoice Distibution계정을 Asset Clearing 계정으로
입력하여야 하나 Account Type만 Asset이면 Track as asset이 Check되기 때문에 , 이 계정에 대한
Validation을 하는 과정에서 너무 많은 데이타로 인해 Performance문제가 생김
결산 시점의 문제가 발생시 문제의 Sql을 참고하여 , invoice distribution의 계정이 Asset Clearing계정이 아닌 계정은 미리 N:reject로 Update하여 대상을 줄일수 있음
Example
4406888.992
Reference Documents
249802.1

Answer 1