3 Steps for Creating Efficient Update Rules
- by John Kurgan, Independent SAP BI Professional, JK Global Consulting, Inc.
- November 1, 2006
With a little ABAP code, optimize your data loads with efficient update rules.
Update rules connect InfoSources to data targets. They allow you to filter, transform, aggregate, and integrate the data passing through them.
In the BW world, tables often occupy much of developers’ time, as they analyze dimensional design, key fields versus data fields, compounding keys, and line-item dimensions, just to name a few. But what about all those generated programs that connect all the tables and dramatically affect data loads? These programs — update rules and transfer rules — are often swept under the rug and given less attention with little consideration to performance as long as they function properly.
With some BW knowledge and a few lines of code, I can show you how to create efficient update rules that optimize your loads using only limited ABAP code. Using these tricks, you can create update rules that perform optimally. This can increase the chances of meeting service-level agreements (SLAs) and allow greater windows of time for other activities, such as information broadcasting, aggregate rollups, index rebuilding, statistics updates, and InfoCube compressions.
Though I am not an ABAP expert, I know that a few bad lines of code can cripple the way that a data warehouse loads. Having acquired a few tips from experienced coders, I’ll show you that creating great update rules is now possible for everyone.
First, I’ll discuss the DATA_PACKAGE internal table and global declarations, and then I’ll show you how to put this knowledge to use with three steps to help you create optimized update rules. I’ll also point you in the direction of the best resources available on the topic of update rules in the sidebar, “Related Tips in Other Resources.”
Would you like to see this full item?