Your SAP Resource  »  Publications  »  SAP Experts  »  BI Expert Online

Log In  |  Help

BI Expert

SAP BI/BW/BusinessObjects
concepts, technology, and
best practices

Part of the
SAP Experts
knowledgebase

Subscribe/Renew Now

Browse by Category  |  Advanced Search »

Go

Home

Knowledgebase Overview

Article Index  |  PDF

Free Sample Article

Frequently Asked Questions

Downloads

Webinars

BI 2011 Conference

SAP Insider Event Calendar

SAP Experts Knowledgebases

About Us

Contact Us

Knowledgebase  »  Volume 8 (2010)  »  Update 7

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

by Soumya Mishra, Sr. Consultant, Deloitte Consulting LLP (July 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.

Categories: ABAP, BEx, Data Management

BI, BW, IT

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.

 

Would you like to see the full version of this article?

If you are an electronic license holder to BI Expert, please click here to log in.

If you would like information about becoming an electronic license holder — and having 24/7 unrestricted access to all articles and content in the BI Expert online knowledgebase — click here to see the available subscription options.

Or call 1-781-751-8799 to speak directly with a subscription and licensing specialist about customized access for you and your team.

Isn't your SAP implementation worth world-class information support?

Copyright © 2010 Wellesley Information Services. All rights reserved. Email: customer.service@bi-expertonline.com.
BI Expert, 20 Carematrix Drive, Dedham, MA 02026, USA.
Sales and Customer Service: 1-781-751-8799
SAP and the SAP logo are trademarks or registered trademarks of SAP AG in Germany and several other countries.