Baan IVc4 SP5, NT 4, Oracle 8.05
We are having serious performance problems with calculate commissions. It runs for about 22 - 25 hours every month. The setup is complex, with between three and five people getting commission on any sales order line, depending on the customer & item.

I did some testing on test server and found out that it was taking
about 15 minutes to calc for 100 sales orders (900 so lines).

So I enabled the 'display refresh = 180' and number of servers = 2 performance boosters, but that did not make a difference on the
run time.

When it is calculating, you can look at the task manager, and see the oracle 80 process sitting @ 100 % (of one processor).

Has anyone else had performance problems with calculate commissions ?
Suggestions on my next steps ?

John

John,

We are having serious performance problems with calculate commissions. It runs for about 22 - 25 hours every month. The setup is complex, with between three and five people getting commission on any sales order line, depending on the customer & item.

This is one of the problem sessions in Baan. When you have a complex commission structure and you probably have a large number of sales order lines, the data volume involved results in large tables which causes query performance problems. Several of our customers have had mods done to this session to improve the commission calc process, or have offloaded the process to another program.

There is not a simple answer to this one. Sorry.

I would check on the support web site because I believe there are some performance related patches for this session. I do not know if they were already included in SP5.

So I enabled the 'display refresh = 180' and number of servers = 2 performance boosters, but that did not make a difference on the

The display performance boosters will have little impact on a batch session like this one when running on a local LAN and if the process is spinning on an Oracle query issue.

I do not recall how the program uses multiple bshells. Many of the performance boosters were fixed in c4 and did not work in c2. Most of my customers were c2 or c4 soI do not know with c3.

When it is calculating, you can look at the task manager, and see the oracle 80 process sitting @ 100 % (of one processor).

This is the key fact -- you probably have a query that is taking a long time to resolve. If you send me an email I can direct you to a tool that may help you to diagnose the individual query issue. I suspect that you have an indexing/table size related issue that is manifest with some poor queries or optimization (wrong hint, etc.) -- two problems working in conjunction to cause your performance issue.

I wish I had a simple answer for you on this one, but unfortunately, sometimes Baan queries are sub-optimal when run against large or complex datasets.

-- Jim