Skip to Content

Why should you use Business Rules (Table Based Logic) instead of Script Logic in the SAP BPC?

NOTE: BPC 10 Microsoft Platform shows different behavior due to design change so if you are using it, please read below URL.

Recently I had a chance to visit a customer site. They said they had a performance issue with currency conversion. I found that they were using script logic for currency conversion so I converted thier script logic to business rule. The performance improved more than 10 times even though new business rule processed more records. Please check below graph.

As you can see, it took under 150 seconds to convert 1.14 million records.


Then you may ask a question why the performance is SO MUCH different.

The answer is… ‘Business rule is the logic module that is based on the stored procedure of data base server but script logic is based on the component of application server’.

Script logic reads data from the Database server and calculates it. After it finishes calculations, Logic components will post result data through BPC sending engine.

Most of customer has multi server environment so Application server and Database server is separated physically. It means script logic will make communication traffic between Application server and database server. Usually it doesn’t matter when data size is small but like this customer case, if logic creates a lot of records, it will make a performance issue. In addition, sending engine performance also will be affected its amount of data.

In conclusion, we should use business rule when logic needs to process a lot of data. Of course business rule can’t handle all cases but if we use it properly, we can get best result.

I attached two scripts for comparing.





Note: Please refer below URL. You can find a document how to convert currency using business rule.

You must be Logged on to comment or reply to a post.