cancel
Showing results for 
Search instead for 
Did you mean: 

Large segmented chart of accounts

Former Member
0 Kudos

Hi Experts,

I am working on a site which has a large number (around 24000) of GL accounts due to account segmentation and as a result, a number of functions are very slow, for example, opening the budget scenario definition screen takes around 5 minutes.

I have upgraded the database to 8.8, PL12 on a test server, which has increased the performance slightly, but it is still takes about 3 minutes to open the budget scenario definition screen.

That screen is just one example, anything to do with the accounts is slow, even opening the General Ledger report selection screen

I have proved that it is the number of accounts in a test system by deleting all accounts that have never had any postings in jdt1 which halved the total number of accounts, and increased the system performance dramatically

Has anyone come across this performancee problem bofore?

Edited by: Arran Bishop on Sep 8, 2010 8:34 AM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

For such amount of GL Accounts, performance is definitely an issue. It is better clear up all the unused accounts. The worst case scenario world be to recreate couple of them in the future from thousands account deleted. It worths a try.

Thanks,

Gordon

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Arran,

I had a customer with over 18K GLs. There were a couple of screens that may have been slow to open but not what you are experiencing. We did go thru the CoA to delete some GLs that would never be used which may have helped, but what they liked more was it was easier to go thru the GLs than having all original 18K.

Heather

former_member186095
Active Contributor
0 Kudos

Hi Bisshop,

Just to share that we have a customer of SBO that have 100 branches. They choose to use branches database rather than using segmentation account. We suggest both solution i.e. using segmented account to reflect the branch or branches database. So, the HQ is only a consolidation db.

We assume that if one branch have 300 accounts, the total accounts will be 30,000. It will decrease the performance unless the customer invests high spec server e.g. quad core server with minimum of 16 GB memories and 500 gb harddisk. You may choose sun server.

The customer has chosen to invest the server that can accomodate 100 branches. So, there are 100 branches and 1 hq databases in one server only.

JimM