SAP BI 7.0 Initial Customization Process

IBM Americas Advanced Technical Support
IBM SAP Technical Brief
SAP Business Intelligence 7.0 Initial Customization Process
Damir Rubic IBM SAP & Oracle Solutions Advanced Technical Support
Version: 1.0 Date: 24 February 2009
2009 International Business Machines, Inc.
IBM Americas Advanced Technical Support ACKNOWLEDGEMENTS ........................................................................................................................ 4 1. DISCLAIMERS ...................................................................................................................................... 4 COPYRIGHTS ....................................................................................................................................... 4 FEEDBACK .......................................................................................................................................... 4 VERSION UPDATES.............................................................................................................................. 4 SAP BI BASIS POST-INSTALLATION STEPS ............................................................................. 6 1.1. 1.2. 1.3. 1.4. 1.5. 1.6. 1.7. 1.8. 1.9. 1.10. 1.11. 1.12. 2. 2.1. 2.2. 2.3. 2.4. 2.5. Configuring the Transport Management System ....................................................................... 6 SAP License Key Installation ..................................................................................................... 8 IBM DB2 License Key Installation ............................................................................................ 9 SAP User Definition................................................................................................................. 10 SAP System Time setup ............................................................................................................ 11 Installation of the latest SAP kernel patch ............................................................................... 12 Installation of the latest SAP ABAP patches (Hotpacks) ......................................................... 14 Importing the SAP BI Content ................................................................................................. 16 Definition of the Logical system .............................................................................................. 18 Definition of the Production client .......................................................................................... 20 Client Copy .............................................................................................................................. 22 SAP Documentation Installation.............................................................................................. 23 BI Technical Content Activation .............................................................................................. 24 Data Cube Activation ............................................................................................................... 26 Data Cube Load ....................................................................................................................... 28 Sample Query Definition.......................................................................................................... 29 Query Execution....................................................................................................................... 30
INTRODUCTION........................................................................................................................................ 5
SAP BI CUSTOMIZATION STEPS................................................................................................ 24
APPENDIX A: RELATED PUBLICATIONS ........................................................................................ 32
2009 International Business Machines, Inc. Page 2
IBM Americas Advanced Technical Support Figures: Figure 1 - Transaction STMS (1) ................................................................................................................... 6 Figure 2 - Transaction STMS (2) ................................................................................................................... 7 Figure 3 - Transaction STMS (3) ................................................................................................................... 7 Figure 4 Transaction SLICENSE................................................................................................................ 8 Figure 5 Executing DB2LICM Command .................................................................................................. 9 Figure 6 User Definition Using Transaction SU01 (1) ............................................................................. 10 Figure 7 User Definition Using Transaction SU01 (2) ............................................................................. 10 Figure 8 User Definition Using Transaction SU01 (3) ............................................................................. 10 Figure 9 - System Time Setup Using Transaction STZAC ......................................................................... 11 Figure 10 JSPM Execution Dialog steps (1) .......................................................................................... 12 Figure 11 JSPM Execution Dialog Steps (2) ......................................................................................... 13 Figure 12 JSPM Execution Dialog Steps (3) ......................................................................................... 13 Figure 13 Transaction SPAM Basic Dialog........................................................................................... 15 Figure 14 Transaction SPAM Queue Definition ................................................................................... 15 Figure 15 Transaction SPAM Queue Import Confirmation .................................................................. 15 Figure 16 Transaction SAINT Queue Import Definition (1) ................................................................. 16 Figure 17 Transaction SAINT Queue Import Definition (2) ................................................................. 17 Figure 18 Transaction SAINT Password Request ................................................................................. 17 Figure 19 Transaction SM31 Logical Systems Table ............................................................................ 18 Figure 20 Transaction SM31 Creating New Logical System ................................................................ 18 Figure 21 New Transport Request Created ............................................................................................... 19 Figure 22 Transaction SE09 Transport Request Release ....................................................................... 19 Figure 23 Transaction SM31 Client Table Input ................................................................................... 20 Figure 24 Transaction SM31 Client T000 Content................................................................................ 20 Figure 25 - New Client Input Parameters .................................................................................................... 21 Figure 26 - Client Copy using Transaction SCCL ....................................................................................... 22 Figure 27 - Transaction SR13 - Documentation Installation ....................................................................... 23 Figure 28 - Transaction SR13 - Workbench Request .................................................................................. 23 Figure 29 Transaction RSA1 Initial Execution ...................................................................................... 24 Figure 30 - BI_TCO_ACTIVATION Batch Job ......................................................................................... 24 Figure 31 - Transaction RSTCO_ADMIN .................................................................................................. 25 Figure 32 - Transaction SM37 ..................................................................................................................... 25 Figure 33 - Data Warehousing Workbench Cube Activation ................................................................... 26 Figure 34 - Data Warehousing Workbench Cube Data Model Display ................................................... 27 Figure 35 - Data Warehousing Workbench Cube Data Model Display ................................................... 27 Figure 36 - Program CUBE_SAMPLE_CREATE Execution ..................................................................... 28 Figure 37 - Query Definition in Query Designer ......................................................................................... 29 Figure 38 - Query Output BEx Analyzer General View........................................................................... 30 Figure 39 - Query Output BEx Web Analyzer Data Presentation ............................................................ 31
Acknowledgements
Thank you to Jim Dilley and Mark Gordon for all their help regarding this and many other SAP & IBM Power Systems related subjects.
Disclaimers
IBM has not formally reviewed this paper. While effort has been made to verify the information, this paper may contain errors. IBM makes no warranties or representations with respect to the content hereof and specifically disclaim any implied warranties of merchantability or fitness for any particular purpose. IBM assumes no responsibility for any errors that may appear in this document. The information contained in this document is subject to change without any notice. IBM reserves the right to make any such changes without obligation to notify any person of such revision or changes. IBM makes no commitment to keep the information contained herein up to date.
Copyrights
RS/6000, IBM Power Systems, and AIX are copyrights of IBM Corporation. DB2 is a copyright of IBM Corporation. SAP R/3, SAP BI 7.0 and NW2004s are the copyrights of SAP Corporation.
Feedback
Please send comments or suggestions for changes to drubic@us.ibm.com.
Version Updates
Version 1.0 - initial version
Introduction
This paper is intended for IBM pSeries customers, IBM Technical Sales Specialists and IBM & SAP consultants who would like to know more about the steps required for the initial customization of SAP BI based systems. This process is one of the most fundamental SAP BI related implementation procedures and can be used in many different scenarios (SAP BI Demo installations, SAP BI POC related activities etc.). This paper starts with the assumption that the initial SAP system installation is performed following the steps provided by the SAP install guides for the respective installation type. The process described in this document utilized SAP Netweaver 7.0 (2004s) SR3. The database of choice was IBM DB2 v9.5 FP2 and the operating system used was SUSE Linux Enterprise Server 10 SP2. The first group of the steps is related to the SAP Basis configuration required for the proper definition and utilization of the actual BI features delivered by SAP. The process begins with the initial definition of the SAP Transport Management System. It continues with the description of the license key installation, both for SAP and DB2. After the users were defined, SAP system time was corrected. Next step is the extensive installation process of the required binary executable patches and ABAP Support Packages that are prerequisite for the successful installation of the BI Content. The Final Basis customization step is the definition of the client and the logical system that will contain the data used for the testing of the SAP BI functionality. Installation of the SAP documentation is the optional, but is a much recommended process. The group of customization steps outlined in this document will prepare the system for the BI Business Content initialization, continuing with the definition of the sample BI cubes, initial data load process and the definition of the several sample queries. This document can be expanded in many different SAP BI related directions. Additional information is available in the Appendix A of the paper, including a number of references to address the questions that may come up from reading this document.
1. SAP BI Basis Post-Installation Steps

Before the initial SAP BI customization process is started, the following procedures should be successfully executed: Basic Installation Planning/Preparation SAP Software Installation Basic administrative post-installation steps that are part of the SAP Installation Guide (Chapter 5)
1.1.
Configuring the Transport Management System
Change and Transport System (CTS) is a tool that organizes development projects in ABAP Workbench and in Customizing, and then transports the changes between the SAP systems in the system landscape. Before working with the Transport Management System (TMS), it must be configured in all SAP Systems in the system landscape. Login to the SAP system using client 000, UID: SAP*/password. (password is a master password defined during the installation of the SAP system). Execute transaction STMS and follow the dialog prompts.
Figure 1 - Transaction STMS (1)
1.2.
SAP License Key Installation
To use SAP software legally and in accordance with contractual stipulations, SAP Systems can only be operated with a license key granted by SAP. When installing the SAP System, a temporary license is automatically installed that allows the operation of the system for four weeks (as of the date of installation). Before the temporary license expires, a permanent license key must be obtained from SAP. After receiving the license key from SAP, install and manage the keys using transaction SLICENSE.
Figure 4 Transaction SLICENSE
1.3.
IBM DB2 License Key Installation
The management of licenses for DB2 Universal Database (DB2 UDB) products is done primarily through the License Center within the Control Center of the online interface to the product. Use the License Center to check license information, statistics, registered users, and current users for each of the installed products. When the Control Center cannot be used, the db2licm Licensed Management Tool command performs basic license functions. This command allows adding, removing, listing, and modifying licenses and policies installed on the local system. The presented SAP OSS note provides specific steps for the installation of the DB2 licenses under the SAP application suite. Note 816773 - DB6: Installing an SAP OEM license
Figure 5 Executing DB2LICM Command
1.4.
SAP User Definition
Different activities that are part of this customization process require a user definition that is not delivered with the standard SAP content load. SAP transaction SU01 is used for this specific task. Included figures provide a description of how to create a new user in both pre-defined clients: 000 and 001.
Figure 6 User Definition Using Transaction SU01 (1)
The user type defined was dialog and the SAP profiles used during the definition of this user were: SAP_ALL and SAP_NEW.
1.5.
SAP System Time setup
The SAP System uses the local date, local time and time zone settings of the operating system. If the SAP system time is not properly synchronized with the OS system time, a different set of the anomalies can occur in the SAP system. The time zone difference between different clients can be found using the report tzonecheck. Execute this report in SE38 and check the time zone for the selected client. The time zones can also be checked using the transaction STZAC. Login to each of the clients and execute the transaction STZAC to display the time zone. The time zones can also be changed in this transaction. But to do so the client should be first made modifiable.
Figure 9 - System Time Setup Using Transaction STZAC
Additionally, check for time inconsistencies between the SAP kernel and database by executing the report RSDBTIME in SE38. For additional information, see the following SAP OSS notes: Note 198411 - Current data and information about time zones Note 481835 - Analyzing the time zone settings
The customization steps explained in the next two chapters are not mandatory for the successful activation and utilization of SAP BI content. However, these two chapters are included because of the stability that the implementation of the latest SAP ABAP and Java patches kernel updates brings to the rest of the customization steps. At the time this document was written, two different versions of BI content were available for implementation. Each of them required different set of the ABAP Support Packages prerequisites. These details will be explained in the chapter 1.7. For ABAP Support Packages, Support Package Manager is used, while the Java Support Package Manager is provided for the application of the Java Support Packages. 2009 International Business Machines, Inc. Page 11
1.6.
Installation of the latest SAP kernel patch
Java Support Package Manager (JSPM) is used to apply support packages on deployed software components by automatically detecting SAP software components that have been modified. Once started, JSPM connects to the SDM server, which performs additional validation of the support packages and software components for deployment. JSPM detects SAP software components that have been modified and allows support packages to be applied to them. Before JSPM utility is used, necessary support packages must be downloaded from the SAP Service Marketplace. To start the JSPM utility on the Unix/Linux operating system, execute the following steps: In the file system, go to the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM directory. Depending on the system, the name of the central instance has the following syntax: o For a standalone system JC<xx> o For an add-on system DVEBMGS<xx>, where xx is the number of the central instance. To start JSPM, run the go script file. Enter the password for the SDM, choose Log On and follow the dialog steps until the update is finished. The procedure controls the execution of the update and is fully automatic. Examples of the dialog steps are presented in the following three figures (1-10 to 1-12).
Figure 10 JSPM Execution Dialog steps (1)
Figure 11 JSPM Execution Dialog Steps (2)
Figure 12 JSPM Execution Dialog Steps (3)
1.7.
Installation of the latest SAP ABAP patches (Hotpacks)
Support Package Manager is the tool used to import the Support Packages into the system, whether they are from the SAP Support Portal or from Collection CDs. This tool is implemented in the transaction SPAM. Before transaction SPAM is called for the first time, several prerequisites are required: Change and Transport System is configured correctly. There is enough space available in the transport directory (UNIX: /usr/sap/trans). There are relevant authorizations for Support Package Manager. Logged on in client 000, user DDIC. Use the latest version of Support Package Manager. Version 33 was latest version available at the time of this publication
During the execution, the tool goes through the several different activities: Loading Support Packages Defining a Queue Importing a Queue Adjusting Modifications (if necessary) Checking Logs Confirming the Queue
Since SPAM/SAINT version 32, the SAP maintenance certificate must be obtained for the proper SAP Support Package import. These maintenance requests can be requested manually or downloaded and automatically distributed using the SAP Solution Manager. The BI Contents (BI_CONT_7.03 and BI_CONT_7.04) installed for this papers specific scenario has a set of Support Packages that they require for successful implementation. These prerequisites are explained in detail in the following OSS notes: Note 916834 - BI_CONT 7.03: Installation and upgrade information Note 1172899 - BI_CONT 7.04: Information about installation and upgrade
These will be explained in more details steps in the next chapter.
IBM Americas Advanced Technical Support The following figures provide a basic overview of the steps included during the execution of the SPAM tool:
Figure 13 Transaction SPAM Basic Dialog
Figure 14 Transaction SPAM Queue Definition
Figure 15 Transaction SPAM Queue Import Confirmation
1.8.
Importing the SAP BI Content
SAP Add-On Installation Tool (transaction SAINT) was developed to enable users to install and upgrade add-ons directly from their standard SAP system. This is the tool used to load the SAP BI Content. Access to the operating system or restarting the system is not required. Prior to installation, numerous import conditions are checked to ensure that only the add-ons that fit the available SAP system can be installed. For this papers specific scenario, BI_CONT_7.04 was used. The successful data load required the following set of prerequisites, all together included in the Service Pack 17 (SP17): SAP_BASIS SAP_ABA SAP_BW PI_BASIS Or PI_BASIS 700 Support Package 17 700 Support Package 17 700 Support Package 19 2005_1_700 Support Package 17 2006_1_700 Support Package 07
Once the data load prerequisites were fulfilled, the following set of the steps were executed: BI_CONT_7.04 and BI_CONT_7.04_SP1 packages downloaded and properly unpacked into the /usr/sap/trans/EPS/in directory Logon as DDIC in 000, call transaction SAINT and choose the BI Content for the load
Figure 16 Transaction SAINT Queue Import Definition (1)
BI_CONT_7.04_SP1 must be installed together with the basic package
Figure 17 Transaction SAINT Queue Import Definition (2)
before the content load starts, provide the proper installation password
Figure 18 Transaction SAINT Password Request
once the final package list is presented and confirmed, the BI content load starts
1.9.
Definition of the Logical system
During the definition of the new client required for the later steps, a new SAP logical system is created. The SAP logical system is an entity used to identify an individual client in a system, for ALE communication between SAP systems. To create a new logical system, table V_TBDLS must be maintained using transaction SM31. This is done in the client 000.
Figure 19 Transaction SM31 Logical Systems Table
By pressing the Maintain button, the content of the table V_TBDLS is presented. In the next dialog step, select New Entries and add the necessary content to the first line in the table. Once the content is saved, the new transport request is generated. The name syntax is {SID}CLNT{Client No.}.
Figure 20 Transaction SM31 Creating New Logical System
Figure 21 New Transport Request Created
Before the definition of the logical system is properly finished, the just generated transport request must be released using transaction SE09.
Figure 22 Transaction SE09 Transport Request Release
Once this is confirmed, the new SAP logical system has been created.
1.10.
Definition of the Production client
SAP Client is an independent self-contained business entity in the SAP system that has its own set of tables and master records. Before the imported BI Content can be activated, the client used for testing must be properly configured. All SAP System clients are maintained in the table T000. To maintain the table, transaction SM31 is again used.
Figure 23 Transaction SM31 Client Table Input
Figure 24 Transaction SM31 Client T000 Content
Pressing the New Entries button triggers the process that will create the new client used for the target copy of client 001.
IBM Americas Advanced Technical Support The next dialog screen presents the input parameters that are required for the proper definition (including just created new logical system).
Figure 25 - New Client Input Parameters
For the demo purposes, option Changes without automatic recording under Changes and Transports for Client-Specific Objects was selected. In the production environment, option Automatic recording of changes has to be chosen. Once the parameters are checked, confirmed and saved, the new client is created. This client (100) will simulate the BI production client that will be used for the BI content activation, customization and testing.
1.11.
Client Copy
Before starting with the customization of the BI environment, copy the content of client 001. To avoid minor anomalies during the initial logon to the new client, several changes are required in the SAP default instance profile (DEFAULT.PFL) set login/system_client=100 set login/no_automatic_user_sapstar = 0
The second element is explained in more details in the SAP OSS Note: Note 550894 - CC-ADMIN: Setting up a new client
To avoid the termination of the program RS_CLIENT_COPY_BW, apply the solution from the following SAP OSS Note: Note 316923 - Termination of program RS_CLIENT_COPY_BW
To activate the changes, the system has to be restarted. Login to the new client 100 with SAP* and password PASS. Initiate client copy process using the transaction SCCL using the source client 000 and copy profile SAP_UCSV.
Figure 26 - Client Copy using Transaction SCCL
Once the client copy process is successfully finished, proceed to Chapter 2 where the BI customization process is explained.
1.12.
SAP Documentation Installation
Installation of online SAP documentation is not a mandatory process, but is highly recommended. It is initiated by using the transaction SR13. Figure 1-25 provides the input information used for initialization of the online help directly from the SAPGui.
Figure 27 - Transaction SR13 - Documentation Installation
Once the input is saved, the new workbench request is generated. SE09 should be used to release the transport request before continuing to the next step.
Figure 28 - Transaction SR13 - Workbench Request
2. SAP BI Customization Steps

This chapter provides information about the configuration steps that are specific to the SAP BI content loaded previously. It will explain the initial BI content activation that presents a base for data cube definition. Once the data cubes are properly defined they can be loaded with sample data. Then test queries will be defined to access the data inside the cubes using the basic BI analysis tool called BEx Analyzer. After confirming that the queries are properly defined and executed, continue with the configuration process that will link the Enterprise Portal presentation services with the part of the ABAP stack providing BI functionality. This will allow presentation of the BI queries using Web and Java technology, providing additional data mining and presentation functionality.
2.1.
BI Technical Content Activation
Once the client copy process is successfully finished, re-logon to the same client 100 using the custom pre-defined user. The BI technical content activation process is automatically triggered after the transaction RSA1 is called for the first time. This transaction is responsible for the start of the BI_TCO_ACTIVATION batch job that will run in the background and can be monitored using transaction SM37.
Figure 29 Transaction RSA1 Initial Execution
Figure 30 - BI_TCO_ACTIVATION Batch Job
IBM Americas Advanced Technical Support When the Data Warehousing Workbench screen appears every further activity should be postponed until there is final confirmation that the BI technical content is properly activated.
Figure 31 - Transaction RSTCO_ADMIN
To confirm the success of the activation process, the transaction RSTCO_ADMIN can be used. Additionally, the previously mentioned SM37 can be used to confirm the status of the BI_TCO_ACTIVATION job.
Figure 32 - Transaction SM37
2.2.
Data Cube Activation
Data Warehousing Workbench (DWB) is the central tool for performing tasks in the data warehousing process. It provides data modeling functions as well as functions for controlling, monitoring, and maintaining all the processes in SAP NetWeaver BI that are related to the procurement, retention, and processing of data. BI Content is shipped in the delivery version (D version). Before working with BI Content objects, copy them from the delivery version (D version) to the active version (A version). This requires activation of the BI Content. Collect the delivered BI Content in the function area BI Content of the Data Warehousing Workbench and copy it to the active version. This ensures that all additional required objects are automatically included, as is the sequence of activation. Collection Mode chosen was Collect Automatically. Then choose whether to copy, match, or not install the BI Content objects.
Figure 33 - Data Warehousing Workbench Cube Activation
Once the cube is activated, it will appear in the Modeling tab of the Data Warehousing Workbench. Moving the cube using the drag and drop function will provide several different options for the proper data model activation. The Simulate Installation function is usable if it is not known whether all the information objects are ready for activation for this specific cube. If all the prerequisites are available, installation will be activated using the one of the last three options presented in Figure 1-33.
Figure 34 - Data Warehousing Workbench Cube Data Model Display
Figure 35 - Data Warehousing Workbench Cube Data Model Display
IBM Americas Advanced Technical Support Occasionally, the activation process of the cube will fail. If that occurs, the output of the process will provide detail information about the failure point. Several transactions are available for help in this specific situation including RSTCO_ADMIN, RSRV etc... One of the transactions of major importance is the RSD1. It is used for InfoObject maintenance. The problem that occurs very often during the activation of the cubes is that an InfoObject required by the cube is not active. RSD1 is used to initiate the manual activation of the object. This activation procedure can be initiated in a several different ways that are clearly presented in the Figure 1-35.
2.3.
Data Cube Load
Once the required cubes are properly activated, SAP provides a sample program for the data cube load. The program is called CUBE_SAMPLE_CREATE. For the proper activation and execution of the sample program, transaction SE38 is used. Figure 1-36 provides an overview of the input fields in the program CUBE_SAMPLE_CREATE, InfoCube Name and the Number of Data Records to be Generated that the program will load into the sample cube.
Figure 36 - Program CUBE_SAMPLE_CREATE Execution
2.4.
Sample Query Definition
At this point the necessary elements used for the definition of the test query are ready. SAP provides a tool that is part of the SAPGUI (frontend) package called BEx Query Designer. This analyzes the dataset of the BI system by defining queries for InfoProviders. Selecting and combining InfoObjects (characteristics and key figures) or reusable query elements (such as structures) determines how to navigate through and evaluate the data in the selected InfoProvider. Starting the tool and logging on to the system will provide a view on the cubes that are currently active in the system. The following steps describe how to define the test query: From history, or from all available InfoProviders under InfoAreas, select the InfoProvider to base the query. The available objects for the InfoProvider selected are displayed as a directory tree in the InfoProvider screen area. Make the selections for the filter of the query. From the directory tree of the InfoProvider, select the characteristics or the key figure on which the query is to be based. Specify which characteristics, key figures, or structures are to be made available for navigating through the query data. Using drag and drop, drag the corresponding directories of the characteristics in the InfoProvider tree to the directories Rows, Columns, or Free Characteristics in the Rows/Columns screen area, or drag the structure directories into the rows or columns. When the query is created, check the query definition by choosing Query Check in the menu bar. Save the query. Enter a Technical Name and a Description for the query.
Figure 37 - Query Definition in Query Designer
2.5.
Query Execution
The BEx Analyzer is the Business Explorer analytical, reporting, and design tool embedded in Microsoft Excel. The BEx Analyzer can analyze and plan with selected InfoProvider data by using the context menu or drag and drop to navigate within queries created in the BEx Query Designer. Design the interfaces for queries by inserting design items (controls) such as analysis grids, dropdown boxes, and buttons into the Excel workbook. This transforms the workbook into a query application. BEx Analyzers functionality is divided into two modes, each with a dedicated toolbar and menu path: Analysis mode for executing OLAP analyses on queries Design mode for designing the interface for query applications
In the following example, BEx was used in the analysis mode. Figure 38 and 39 present a basic overview of the BEx tool, presenting the general view of the results and the associated spreadsheet chart.
Figure 38 - Query Output BEx Analyzer General View
Additional SAP BI functionality can be explored and utilized if the BEx Web Analyzer is used. That is a standalone, convenient Web application for data analysis which can call using a URL or as an iView on the portal. In the Web Analyzer, open a data provider (query, query view, InfoProvider, or external data source) and use ad hoc analysis to create views of BI data, called query views, which then can be used as data providers for other BI applications. Results of ad hoc analysis can be distributed and saved as required. The configuration process is explained in the following OSS notes: Note 917950 SAP Netweaver 2004s: Setting Up BEx Web Note 937697 Usage of SAP Netweaver BI Diagnostics & Support Desk Tool
IBM Americas Advanced Technical Support A sample query result presented in the browser using the BEx Web communication can be seen in the Figure 39.
Figure 39 - Query Output BEx Web Analyzer Data Presentation
Appendix A: Related Publications

The publications listed in this section are recommended for a more detailed discussion of the topics covered in this white paper. 1. Publications Accessing a DB2 Data Warehouse using DB connect in SAP BI 7.0, Mark Gordon (IBM) http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101181 Tuning SAP R/3 with Oracle on pSeries, Mark Gordon (IBM) http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100377 SAP J2EE Engine Architecture and Tuning Guide, Damir Rubic (IBM) http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101180
2. Ressources SAP Help Portal: http://help.sap.com/ IBM System p and AIX Information Center http://publib.boulder.ibm.com/infocenter/pseries/index.jsp (AIX 5L) http://publib.boulder.ibm.com/infocenter/systems/scope/aix/index.jsp (AIX 6.1) DB2 Information Center: http://publib.boulder.ibm.com/infocenter/db2luw/v8//index.jsp (V8) http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp (V9.1)

SAP BI 7.0 Initial Customization Process

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SAP BI 7.0 Initial Customization Process

Încărcat de

Drepturi de autor:

Formate disponibile

IBM Americas Advanced Technical Support

IBM SAP Technical Brief

SAP Business Intelligence 7.0 Initial Customization Process

Version: 1.0 Date: 24 February 2009

2009 International Business Machines, Inc.

SAP BI CUSTOMIZATION STEPS................................................................................................ 24

APPENDIX A: RELATED PUBLICATIONS ........................................................................................ 32

2009 International Business Machines, Inc. Page 2

2009 International Business Machines, Inc. Page 3

IBM Americas Advanced Technical Support

2009 International Business Machines, Inc. Page 4

IBM Americas Advanced Technical Support

2009 International Business Machines, Inc. Page 5

IBM Americas Advanced Technical Support

1. SAP BI Basis Post-Installation Steps

Configuring the Transport Management System

Figure 1 - Transaction STMS (1)

2009 International Business Machines, Inc. Page 6

IBM Americas Advanced Technical Support

Figure 2 - Transaction STMS (2)

Figure 3 - Transaction STMS (3)

2009 International Business Machines, Inc. Page 7

IBM Americas Advanced Technical Support

SAP License Key Installation

Figure 4 Transaction SLICENSE

2009 International Business Machines, Inc. Page 8

IBM Americas Advanced Technical Support

IBM DB2 License Key Installation

Figure 5 Executing DB2LICM Command

2009 International Business Machines, Inc. Page 9

IBM Americas Advanced Technical Support

SAP User Definition

Figure 6 User Definition Using Transaction SU01 (1)

Figure 7 User Definition Using Transaction SU01 (2)

Figure 8 User Definition Using Transaction SU01 (3)

2009 International Business Machines, Inc. Page 10

IBM Americas Advanced Technical Support

SAP System Time setup

Figure 9 - System Time Setup Using Transaction STZAC

IBM Americas Advanced Technical Support

Installation of the latest SAP kernel patch

Figure 10 JSPM Execution Dialog steps (1)

2009 International Business Machines, Inc. Page 12

IBM Americas Advanced Technical Support

Figure 11 JSPM Execution Dialog Steps (2)

Figure 12 JSPM Execution Dialog Steps (3)

2009 International Business Machines, Inc. Page 13

IBM Americas Advanced Technical Support

Installation of the latest SAP ABAP patches (Hotpacks)

These will be explained in more details steps in the next chapter.

2009 International Business Machines, Inc. Page 14

Figure 13 Transaction SPAM Basic Dialog

Figure 14 Transaction SPAM Queue Definition

Figure 15 Transaction SPAM Queue Import Confirmation

2009 International Business Machines, Inc. Page 15

IBM Americas Advanced Technical Support

Importing the SAP BI Content

Figure 16 Transaction SAINT Queue Import Definition (1)

BI_CONT_7.04_SP1 must be installed together with the basic package

2009 International Business Machines, Inc. Page 16

IBM Americas Advanced Technical Support

Figure 17 Transaction SAINT Queue Import Definition (2)

Figure 18 Transaction SAINT Password Request

2009 International Business Machines, Inc. Page 17