Sie sind auf Seite 1von 11

How-to Guide SAP NetWeaver 2004s

How To Add a BI Report to a Portal Page

Version 1.00 October 2006 Applicable Releases: SAP NetWeaver 2004s

Copyright 2006 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C , World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP,, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data

contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings (Code) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

1 Scenario
You have developed Web Templates using the Web Application Designer. Now you want to offer these Web Templates to your end users via the Enterprise Portal. This How-to guide describes how to add these Web Templates to your Enterprise Portal Content.

2 Introduction
The solution presented here is based on SAP NetWeaver 2004s. The How-to guide describes only the steps that are necessary, if you create the BI iViews directly in the Enterprise Portal. You could also publish the Web Templates from the Web Application Designer as iViews into the Portal Content directory.


3 The Step By Step Solution

1. As the first step you have to navigate to the right Portal Content folder, where you want to add the BI report as Portal iView.

3a Recognize Prefix (here:

2. Then you have to create a new iView using the context menu: New iView


3. Now you see the iView Wizard. In the first step you have to choose iView template create an iView from an existing iView template as source type.

4. In the next step you have to choose the iView template BEx Web Application iView.


5. Then you have to provide an ID (technical name of the Portal Content iView), a description, the iView ID Prefix and the master language of the iView.

9a Titel in Tray of iView 9b ID in Portal 10 put in Prefix XY 11 Master Language


6. Then you have to choose the version of the BEx Web Application. If you created the Web Template using the Web Application Designer based on SAP BW 2.x/3.x, you have to choose the appropriate option. If you have created the Web Template using the new Web Application Designer based on SAP NetWeaver 2004s, you have to choose the option SAP NetWeaver BI 7.x

13 Choose BW 2.x/3.x or SAP NW BI 7.x



7. In the next step you have to type in a prefix (depending on the version of the BEx Web Application) and the technical name of the Web Template. If you have used the SAP BW 2.x/3.x Web Application Designer version you have to use the prefix TEMPLATE_ID=. If you have used the Web Application Designer based on SAP NetWeaver BI 7.x, you have to use the prefix TEMPLATE= (e.g. TEMPLATE=MYTEMPLATE_ID).

15 Put in WebTemplateID with Prefix


8. In the last wizard step you can check your entries, you have made before. You can also set the flag Open for editing, when wizard completes. Then you can directly work on the BI iView to do some further adjustments.

17 Check your entries and this flag



9. After pressing the Finish-button in the iView wizard the iView properties show up. There you can select the property category Appearance Size. For the property Height Type you should select Automatic in order to avoid scroll bars on the portal page later on. Save your settings and close your BI iView

21 19 20

10. In the next step you want to add your newly created BI iView to a page. Therefore you have to first navigate to the page you want to add the new iView (or you can create a new page). Then you have to open the page via the context menu Open Object

22 Right Mouse click to open Page


11. To add the iView to the page you have to navigate again to the newly created iView. Via context menu you can add now the iView to the page: Right-mouse click on the iView Add iView to page Deltalink. Afterwards you save the page.

24 Save

23 Right Mouse click

12. Finally you can do a preview to have a look at your new BI iView that is integrated into the portal page. Depending on the result you can adjust the page layout.
25 Preview

13. As a result you will see the BI iView on your portal page.


4 Appendix
1. Before you can create a BI iView in the Enterprise Portal, the system connection and the alias of the BI system has to be defined. This can be done in the System Administration of the Portal System Configuration System Landscape

1 2

2. Also the user mapping to the BI system has to be maintained (in order to use single-sign on). This can be done in the user administration Identity Management

1 2 3

If you work with the Web Application Designer you can also directly publish the Web Templates as iViews in the Portal Content. For further information, have a look in the online documentation.