Financial Report Performance Issues

don_schoen

Member
List

We are experiencing poor performance with our custom financial reports using
Xe. They use the row functionality. The chart of accounts is rather large,
about 315,000 accounts, the majority of which are profit and loss accounts.
The consolidated income statement (about 12 columns, one for each company,
and about 20 rows) takes about 30-45 minutes to process on the AS400.
Should this be considered unusually poor performance, or do other customers
experience the same durations for similar reports?

Thanks in advance for any input.

Don Schoen
B7333 AS/400 ES model 720 w/ 2 gig of memory
 
I have experienced this problem before specifically with row reports and we
narrowed it down to the type of join in the Business View that is
automatically attached to Financial Row reports.

Try change the join on the BSVW and see if it helps. Generally the row
reports do take longer to process though.

Peter J Fourie



From: don_schoen <[email protected]>
Reply-To: [email protected]
To: [email protected]
Subject: Financial Report Performance Issues
Date: Tue, 23 Oct 2001 11:44:03 -0700 (PDT)

List

We are experiencing poor performance with our custom financial reports using
Xe. They use the row functionality. The chart of accounts is rather large,
about 315,000 accounts, the majority of which are profit and loss accounts.
The consolidated income statement (about 12 columns, one for each company,
and about 20 rows) takes about 30-45 minutes to process on the AS400.
Should this be considered unusually poor performance, or do other customers
experience the same durations for similar reports?

Thanks in advance for any input.

Don Schoen
B7333 AS/400 ES model 720 w/ 2 gig of memory




--------------------------
 
Peter,

we have a similar issue with 706,544 account in f0901 and the performance are terrible !

What have you exactly change in the join of the financial business view?

Christian Audet


Implementing B7333 (Xe) SP14.1, SQL
(Support B732, B7331 and B7332)
 
I would not consider this as excessive. After all the row functionality can
give rise to a very complex report, 20 rows can be the equivalent in
complexity as 20 separate reports, on that basis 2 minutes a report is quite
good! Depending on how you define your columns there is an added level of
complexity.



OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development
 
You may want to change the jde.ini file in the Lock Manager section to
Requested Service = *none. It took us from 20 hours for a repost to 1 hour.

Libbi Fletcher
HoMedics, Inc.
M.I.S. Department
248-863-3001 ext. 1281
[email protected]
 
Type 0501-002 into the search box on the knowledge garden with the
document that lists about four major causes of excessive row spec report
processing time and their solutions. The document is titled: "Performance
Alert-Financial Row Report Performance".

Durbin
 
Back
Top