Showing posts with label SAP BW. Show all posts
Showing posts with label SAP BW. Show all posts

Friday, April 11, 2008

How to Implement SAP BW Business Warehouse - Approaches to Simplify SAP BW Implementation

SAP BW is a winner SAP application as far as business decision support is concerned. Readers might remember my post of how implementing SAP R/3 is different from implementing SAP BW. Having decided to implement SAP BW, organizations are faced as to the apporach to take to implement BW. There are generally two categories here, companies which already have SAP R/3 implemeneted and want to implement SAP BW to leverage business decision making. On the other hand, there are orgzanizations which are looking at BW implementation parallely with R/3 implementation.

Whichever category your organization may be in, there are two implementation approaches. Here is a short description of each approach.

How to implement SAP BW Business Warehouse

Pilot Approach - In this appraoch, SAP BW is implemented for key business processes accross the enterprise. Processes which have the highest financial impact should be chosen as the pilot process. Once BW is successfully rolled out for the pilot processes with adequate testing, it can be duplicated for the other processes as well. the advantage of the pilot model to implement BW is that learnings from the pilot process implementation can be used in other BW implementations.

Big Bang Approach - The other not so recommended approach is to go for an all out implementation of SAP BW across all the business processes. So processes like order to cash, procure to pay, payroll, inventory, financials etc will all be covered in the implementation. The risk in this approach is unless planned properly, the big bang approach tends to fail. Further, this approach to SAP BW implementation requires an huge initial investment of resources as well as money.

SAP BW Tutorial Loading Data in InfoCube

These days, I have been doing a lot of exploring on the SAP Business Warehouse. I did some posts on SAP Infocubes and SAP BW basics earlier. Today, I am covering "How to Load Data into Infocube". Loading data in Infocube involves a series of steps. For the sake of convienence of the readers, below I have listed down the steps involved in loading data in infocube with a short description of each of the steps.

1. Creating a Source System - SAP Business Warehouse uses a protocal to find and extract data using the source system. BW can accept data from SAP R/3, BW solutions, Flat files and other third party tools.

2. Using Application Components - SAP BW uses application components to organize Infosources. Application components are arranged in a tree structure and are similar to infoareas in BW infocubes.

3. InfoSource for Data Characteristic - In SAP BW, extracting, transferring, transforming and loading data is a complex process. Infosources in addition to transfer rules are used in BW in the way in which the data loading happens.

4. InfoPackages to Load Characteristics data - A characteristic in SAP consists of master data, text and hierarchy. This master data can also be entered manually in BW. Infopackages are used in selecting, transfering and loading chracteristics datain BW.

5. Infosources and InfoPackage for transaction data - This final step involves creating an infosource for transactional data. At the time of creation of an infosource, one needs to select transaction data rather than master data. Once this is set up, infopackages can be used to upload the transaction data into BW. Infopackages simply specify how and when the data is loaded.

Certification SAP BW Questions and Answers

Continuing on my series of questions and answers on SAP BW certification, here is the question for today. The question below is one of the easier questions. Candidates who have prepared themselves for the BW certification exam will have absolutely no difficulty in answering the questions.

Q). What kind of data can be extracted and loaded with SAP BW?
This question has more than one answer.

a. Master data
b. Transaction data
c. Hierarchies
d. Attributes
e. None of the above

Answer: The correct answer to the question in a,b,c and d. Note that the question has multiple answers. Data that can be loaded into SAP Business Warehouse BW can be master data, transaction data, hierarchies and attributes.

Designing Data Model in SAP BW Implementation

SAP Business Warehouse implementation entails understanding the information needs of the organization and structuring the information in a format which is easy to read and comprehend by the management. The process mentioned above is implemented in SAP BW using the data model. So how does one go about defining and designing the data model in BW. The step by step process for transforming information needs of an enterprise into the data model are as under:

1. Key Performance Indicators KPIs - The first step is to analyze the various KPIs within the processes. This is done through interviews with the senior management and gathering key basic figures.

2. Business Subjects and related attributes - The second step is to find the characteristics which describe the KPIs. These attributes are important to map the KPIs into SAP BW. Similarly, business subjects as well as business entities should also be analyzed.

3. Assignment - The third step in the process of data model design is assigning the identified business subjects to the KPIs. This means generating different data views example time view.

4. Physical Model and Business Content Check - The last step consists of clustering key figures with similar structure. This forms the basis of the infocube. The logical model is then transformed in the physical model. The physical model is then checked against the business content. The business model also helps in building the logical model.

Designing User Roles and Authorizations in SAP BW Made Easy

Providing users authorizations in SAP BW is a hot question for organizations implementing SAP Business Warehouse BW. Ideally, desigining authorizations should always begin with designing user roles in BW. Due to the inherent structure of many organizations, user roles need to be defined at the same level of detail as individual users. Such a design for user access within SAP BW requires a lot of maintenance. As an alternative, organizations can create a few roles and assign as many users to it as required. Though this approach is maintenance friendly, any changes to user roles may have an adverse impact on other users.

The transaction code used to provide authorizations in SAP BW is RSSM. Though the T-Code PFCG Profile Generator can also be used to provide authorizations. Authorization administration is much easier through transaction RSSM in case reporting authorizations are required to be attached to user roles.

SAP-BW-Authorizations-Roles-Design-Business-Warehouse

The best practice approach in providing authorizations in SAP BW is to design authorizations based on SAP BW meta-data objects. Roles can be defined to restrict user access to a particular query or InfoCube. The key is to keep the authorizations design role centric rather than user centric. This is because with user roles in SAP BIW, additional features such as portal integration and user menu specification become possible which cannot be done using user based authorization. To help secure access in SAP BW, I would suggest that restricting user access to a particular reporting query or transaction based on user menus. Normally, users are not sophisticated enough to guess transactions. They only play with what appears in the user access menu in front of them.