Factors to consider when deciding to move off SAP BEx

Column

Factors to consider when deciding to move off SAP BEx

David Fox

Aside from the end of life for a release, deciding whether to move off SAP BEx comes down to an evaluation of feature/function, user adoption and integration. Unfortunately, the last item -- integration -- is often overlooked because of the sizzle factor of some of the tools on the market.

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

For more on moving from SAP BEx to BOBJ
SAP: Don't rush from SAP BEx to BusinessObjects

Consider more than end of support in move from BEx to BOBJ

Should you stick with SAP NetWeaver BW?

SAP NetWeaver BW BEx continues to shine in areas such as multi-currency support, multi-language support, and use of flexible hierarchy relationships, and as a robust calculation engine and dynamic OLAP engine. While extremely powerful, these capabilities are overshadowed by the instantly impressive Web 2.0 flash-based tools available.

That notion is changing, however, and changing quickly. Pioneer -- the combination of the two flagship products SAP BusinessObjects Voyager and SAP NetWeaver BEx Analyzer -- will be made available in ramp-up in 2010. Soon, customers will be able to have a consistent user interface across desktop client and Web versions of the product. This will have a tremendous positive impact on end-user satisfaction and user adoption rates.

With an increase in end-user adoption rates, the velocity of information delivery will increase, which will be accompanied by an increase in ROI. Furthermore, this increase in consumption will result in additional needs for increased access to external data. The increased adoption and use of the front-end tools will drive the need to expand the underlying data warehouse, as well as increase self-service functions and automation initiatives. Customers will find the information value chains becoming more efficient as the tool integration matures. Taking a view from the BI Maturity Model developed by Wayne Eckerson of The Data Warehousing Institute, the integration will have a significant impact on helping customers transition from a state of actionable information to decision automation.

When you think of benefits, it comes down to removing the barriers to user adoption and increasing ROI. Getting to BW 7.2, which SAP has now rolled into the NetWeaver BW 7.3 release, and Pioneer will eliminate the last remaining barrier to attaining full user adoption. As users become attuned to the robust and consistent user interface, the focus will shift to additional information needs and a continued increase in the velocity of the information value chain -- driving automation.

David Fox is the principal BI architect for Claricent Inc., an SAP consulting firm that specializes in NetWeaver BI, and now in NetWeaver and BusinessObjects integration. Fox has more than 10 years of experience in NetWeaver BI.


Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.