Keep ABAP Routines in Sync for Global SAP NetWeaver BW 7.0 Implementations

  • by Soumya Mishra, Managing Consultant, IBM Corporation
  • July 27, 2010
Discover effective practices and methodologies to consider when designing and implementing start and end routines in transformations, customer exits for query variables and DataSources, and routines in data transfer processes in SAP NetWeaver BW 7.0. These methodologies and practices can help reduce the risks of keeping the data model in sync during implementation.
Key Concept
In a transformation, a start routine contains the input and output parameters for the routine. Run at the beginning, the start routine performs preliminary calculations and stores the results in a table. End routines also contain input and output parameters, but the system uses end routines after the transformation is complete. You can use end routines to delete unnecessary data or to perform data checks.

ABAP routines help you meet requirements during SAP NetWeaver BW implementations that the standard functionalities of SAP NetWeaver BW cannot meet. In global implementations, these ABAP routines can be used in each country rollout, especially for the country-specific objects.

In multiple country rollouts, it is typical to design and copy a global data model for each country rollout. It can become challenging to keep the subsequent changes to the global data model in sync across all the rolled-out countries. For example, a section of ABAP code used in the start and end routines of the transformation is common across many transformations. Any changes made to that routine for a specific transformation must also be changed for all the transformations.

My team and I have identified an approach in which you can design and implement ABAP routines that keep the data model in sync during implementation across countries, ensuring the production support path and development path are independent of each other during implementation. This more practical method can be used to design start and end routines in transformations, customer exit variable routines for BEx, routines for DTP filters, and customer exits for SAP ERP Central Component (SAP ECC) DataSources.

With this process, function modules are applied to reduce the overall maintenance efforts in large-scale, global SAP NetWeaver BW 7.0 implementations. You can also make post-implementation changes in the function module and the changes are automatically reflected in all the transformations using that function module.


Soumya Mishra

Soumya Mishra is a senior BI practitioner with a total of eight years of experience in the SAP BI space. He has been continuously focused on developing business enabling analytic strategies and solutions. He has extensive enterprise analytics assessment knowledge and has successfully played a key role in delivering large-scale finance transformation solutions that deliver actionable information and insight to users, giving them the ability to make informed decisions. He has deep knowledge of BI, and SAP ECC FI/CO configuration, as well as experience with implementations in several Fortune 500 companies in the consumer products and financial services industries. He is a certified SAP BI solution consultant with deep experience in development and integration of BI strategy; process redesign with information systems; and project planning and implementations with strong communication, organizational, and project management skills. You can view his LinkedIn profile at

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.