Tip

A business case for integrating SAP BI and XI, part one

This weblog is in response to several forum posts that question the necessity of integrating SAP XI and SAP BI. In this series, we'll discuss what's really needed and whether we can surpass that. We'll also look at the benefits of such an integration.

In part one, we'll discuss the business driver and present the business case for a hypothetical organization that needs a new system to store employee data.

Most of the time when a business asks to use BI open hub architecture and extraction mechanisms instead of SAP XI, it's because of the extra costs and budget involved in using XI. We'll propose potential solution approaches for the business case that leverage SAP XI and open hub architecture and we'll look at extraction mechanisms of SAP BI that do not use SAP XI. We draw out a comparison matrix that concludes the recommended approach.

Business drivers

Let's say that with an organization mission of "Global Business Processes," all of the subsidiaries of Org A plan to replace and merge most of their back office solutions into SAP. IT landscape is the most critical factor; hence, we propose a solution approach, in the form of a Global Employee Database (GED) business case, that can help the business to reap maximum benefits.

Business case description

GED is a legacy system that the subsidiaries of Org A use for storing employee data. The IS team needs to update the data each month after it collects the changed records from the HR

    Requires Free Membership to View

and payroll departments. Each subsidiary provides the delta files in either Excel or fixed width formats, which the IS team then reconciles and loads into the GED. The IS team sends these files to three external business partners on a monthly basis. First, it uses export routines for each of the business partners; then the files are password protected, zipped and sent out via email. One partner receives a text file, but the other two receive spreadsheets.

Sometimes the IS team is unable to send the files on time because of problems that might occur in data loading or data reconciliation.

The IS team also sometimes uses GED to search the employee information for internal purposes. GED is also used annually to collate diversity information from all of the businesses as of March 31st. This is to provide an overall company profile for input to the annual report. During this operation, the IS team has to manually pull the data from GED and use lookups and pivot tables to produce the info required (Crystal Reports are not working). On an ad hoc basis, business partners may request a complete dump; in this case, the IS team needs to pull up the employee data from the GED manually and send it to the business partners.

This is the current landscape in the organization:

Drawbacks

  1. Manual intervention by the IS team affects the businesses' ability to perform key activities.
  2. The approach consumes time and effort by the IS team for collating the employee data, loading the data into the GED and sending to the business partner. It can hamper the IS team's ability to carry out critical day-to-day activities.
  3. Manual processes are more error-prone and effort-intrinsic.
  4. No mechanism is available to slice and dice across the data to come up with KPI'S.
  5. The IS team is unable to monitor and track business across various subsidiaries.
  6. After requesting the complete employee information data, business partners have to wait for the IS team to pull the large volume of data and reconcile and send it.
  7. No automated mechanism is available to notify in the event of failure of data loading.
  8. The process is human-dependent and prone to loss of information when a person leaves the organization.

To overcome the drawbacks, I propose a solution approach that helps the IS team to carry out their work smoothly and to make business-critical solutions.

In the next article in this series, I will discuss the solution and recommend an approach to achieve the business case presented here.

A business case for integrating SAP BI and XI, part 2


This content is reposted from the SAP Developer Network.
Copyright 2006, SAP Developer Network

SAP Developer Network (SDN) is an active online community where ABAP, Java, .NET, and other cutting-edge technologies converge to form a resource and collaboration channel for SAP developers, consultants, integrators, and business analysts. SDN hosts a technical library, expert blogs, exclusive downloads and code samples, an extensive eLearning catalog, and active, moderated discussion forums. SDN membership is free.

Want to read more from this author? Click here to read Sravya Talanki's weblog. Click here to read more about SAP Exchange Infrastructure (XI) on SDN.



This was first published in December 2006

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.