You are on page 1of 17

BI Portal Design for End Users

Applies to:
Business Intelligence, Enterprise Portal. For more information, visit the Business Intelligence homepage.

Summary
This article provides a step by step procedure for setting up the portal roles for BI reports in the portal and also describes how to set up the portal display for end users based on their backend BI authorizations. Author: Somesh Athikinasetti

Company: Sauer-Danfoss Created on: 6 May 2009

Author Bio
Somesh is a SAP Certified Associate,certified Senior BI Analyst and has more than 8 years of experience in SAP. His core competency is Business Intelligence (BI) and also worked on ABAP, Java and web technologies. He has worked on various type of projects viz. full cycle implementations, Global Rollouts, Ugrades, Application Support and Enhancements. He is currently working with Sauer-Danfoss.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

BI Portal Design for End Users

Table of Contents
BI 7.0 Portal Design............................................................................................................................................3 BI Portal Set up ...............................................................................................................................................3
Option I: Create New BI Portal Roles...........................................................................................................................3 Option II: Role Upload from BI to Portal .....................................................................................................................13

Related Content................................................................................................................................................16 Copyright...........................................................................................................................................................17

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 2

BI Portal Design for End Users

BI 7.0 Portal Design


This paper discusses how to set up Business Intelligence (BI) Reports in Portal for end users after the technical and function upgrade to BI 7.0 is done. Different organizations will implement BI security in different ways. They implement the security at different levels based on their business requirements. In this paper, we assume that the BI Security in 3.X version is maintained at the folder level. In BIW 3.X we access the BI reports through role menu (folders) as per the screen-shot below:

If we take, for example from the above screen-shot, there is a backend role for BI Finance Folder and separate backend role for BI Procurement folder. So for each folder, we maintain a backend role in the BI system. Whenever any finance user requests BI access, we provide them with appropriate roles for example in this case, role BI Finance folder. When we upgrade from BIW 3.5 to BI 7.0, then all the BI reports will be displayed in the Portal. There is no separate portal concept like BI Portal or Enterprise Portal. There is only one Enterprise Portal (EP) and for BI 7.0 it is mandatory to use Enterprise Portal to run BI 7.0 reports to avail all the new 7.0 features. BI Portal Set up Portal Roles: There are two ways to set up portal roles for BI. First option, create new corresponding portal role to each backend role in the BI system. Second option, use the role upload tool to upload the backend roles from the BI system into Portal and clean up the naming convention accordingly. Option I: Create New BI Portal Roles 1. Create one corresponding new portal role for each backend role. 1.1) Login to BI Portal. Go to tab Content Administration and Portal Content. Create a folder BI Roles. Right click on the BI Roles folder and click on new and click on Role.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 3

BI Portal Design for End Users

1.2)

Enter the Role name, Role id and the prefix and click next. In the next screen click Finish. The use of prefix is mainly used for security purpose. All the portal content development within this prefix com.bp can be controlled easily if the prefix is used for the portal development. For example, a corresponding portal role for BI Procurement Folder is being created below. So, here our role name is BI Procurement Folder.

1.3) 1.4)

Create all the corresponding roles for all the BI backend roles. Procurement Role with name Procurement is created now.

2. Create Portal work set under the new portal role. 2.1) Go to tab Content Administration and Portal Content. Create a folder BI Work sets. Right click on the BI Work sets folder and click on new and click on work set.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 4

BI Portal Design for End Users

2.2)

Enter the work set name, work set id and prefix. Click Next and click Finish. In the same way, create all the required work sets.

3) 3.1)

Create Pages/iViews Go to tab Content Administration and Portal Content. Create a folder BI Pages/iViews. Right click on the BI Pages/iViews folder and click on new and click on Page/iView.

3.2)

Steps for creating iView.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 5

BI Portal Design for End Users

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 6

BI Portal Design for End Users

3.3) 3.4)

Click Finish. Steps for creating Portal Page.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 7

BI Portal Design for End Users

3.5) 3.6)

Click Finish. Right click on the iView Cost Development Report and Add iView to Page delta link.

3.7)

In this example, in BIW 3.5 version, I have the BI Procurement Folder for procurement users and under this folder, I have sub folders such as Payables and Spend Analysis Reports, Quality Management Reports, Supplier Delivery Performance Reports and Vendor Master Reports. The BI reports are present under these sub folders like below.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 8

BI Portal Design for End Users

3.8) 3.9)

3.10) 4) 4.1)

As a first step, create a new portal role called BI Procurement Folder as described in step number 1. Then, create the following 5 work sets as described in step number 2 in the BI Portal : i) Procurement ii) Payables and Spend Analysis Reports iii) Quality Management Reports iv) Supplier Delivery Performance Reports v) Vendor Master Reports Once Portal work sets are created, create iView for each report as described in step number 3.2. Steps to set up the Portal Layout for end users. Open the required role, in this case, Procurement Role as below.

4.2)

Scroll to the Work set Procurement on the left and right click on the work set and add work set to the procurement role.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 9

BI Portal Design for End Users

4.3)

Now, select the work set Procurement and scroll to the work set Payables and Spend Analysis Reports on the left hand side and right click and add work set to the work set as shown below.

4.4)

Repeat step 4.3 again three time for adding all other work sets to Procurement role as below.

4.5)

Select the Procurement work set below the procurement role and right click and click on properties.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 10

BI Portal Design for End Users

4.6)

Select the property Entry point to Yes.

4.7)

Now, select the work set Payables and Spend Analysis Reports and scroll to the iView Cost Development Report iView on the left hand side and add the iView to the work set. In the below screen-shot it is showing as Add iView to Role and not to the work set because the work set Payables and Spend Analysis Reports is already present in the role Procurement. So , the context menu will always show Add iView to Role instead of showing Add iView to Work set.

4.8) 4.9)

Repeat step 4.7 to add all the iViews to the corresponding work sets. Also, iViews can be added to Pages and then Pages can also be assigned to Roles. Now assign the procurement role to the procurement user as shown

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 11

BI Portal Design for End Users

4.10)

The display of the BI Reports will be as shown below. BIW 3.5

BI 7.0

When clicked on the Cost Development Report on the left, the report will be displayed on the right side in the portal display area.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 12

BI Portal Design for End Users

Option II: Role Upload from BI to Portal SAP Help for the role upload is below: http://help.sap.com/saphelp_nw70/helpdata/en/7b/135540e4c79354e10000000a155106/frameset.ht m Navigate to System Administration Transport Role upload as seen below:

Select the target backend SAP system. In this example, the N4SCLNT001 system is used.

The Object Type field allows selection of a variety of objects. Because a role upload is desired, Roles is chosen.

Enter the desired role name or partial role name in the Search for ID field.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 13

BI Portal Design for End Users

Initially, the BI role PORT_MIG_ROLE_A is entered. Click on the Search pushbutton and then select the checkbox adjacent to the desired role as seen below.

Click the Add pushbutton to add the selected role to the List of Objects for Upload. The object should appear in the bottom section. Click the Next pushbutton to continue to the Upload Settings area.

The Settings for Role Upload have several parameters, which may be set. Upload user mapping Assigned users from backend system are assigned to the portal role. This only is relevant for role upload to roles. User mapping is not supported in role upload to work sets. Upload included services When set, included transactions in the ABAP role are uploaded and created as iViews. Select first folder level as entry point Sets the folder as an entry point, which corresponds to a toplevel tab in the portal. Convert roles to work sets Converts to the roles to work sets, which can then be added to a role. The General Upload Settings allow one to overwrite existing content. This option is typically used on subsequent role uploads.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 14

BI Portal Design for End Users

Click the Start Upload pushbutton to begin the role upload process. A status screen appears with updated information.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 15

BI Portal Design for End Users

Related Content
http://help.sap.com/saphelp_nw70/helpdata/en/7b/135540e4c79354e10000000a155106/frameset.htm For more information, visit the Business Intelligence homepage.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 16

BI Portal Design for End Users

Copyright
Copyright 2009 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. 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.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 17