Create iView for SAP Tcode

The steps for creation of iview for a transaction are pretty self explanatory. I will copy the screens below. Hopefully these have enough information to get you going.

We start with deciding on the name and component id for the iView

Portal - Create iView for Transaction
Portal - Create iView for Transaction

Next we choose the gui type of the transaction. Full functionality for some transaction might not be available for some of these options.

Portal - Create iView for Transaction 2
Portal - Create iView for Transaction 2

Now we specify the transaction for which the iView is created. Understandable this is the linchpin of the entire process.

Portal - Create iView for Transaction 3
Portal - Create iView for Transaction 3

This is the confirmation screen of the process showing the data entered till now. Clicking the finish button will create the iView in the PCD

Portal - Create iView for Transaction 4
Portal - Create iView for Transaction 4

Once created we can open the iView in the explorer to display and further maintain its properties. The iView can now be incorporated in worksets and roles.

Portal - iView for Transaction - Final
Portal - iView for Transaction - Final

Create iView

In this post, we will go over the steps involved in creating an iView from scratch. The detailed description of what all options you have when creating an iView are out of scope for this discussion as typically a security administrator is not likely to be asked to create iViews for a productive system. However, like most other posts on this blog there is enough information to get you started and help you understand what all options are available for a portal developer.

The first step while creating new content (iview/workset/role/page) for Portal is to decide the folder in the PCD where your custom development is going to be stored. On right clicking on the appropriate directory you get the option of creating new content. We chose the option of creating a new iview.

Portal - Create iView
Portal - Create iView

The create iview screen gives you a few options – Create iview from template or for a java webdynpro or for an ABAP webdynpro. Each of these options will have their own configuration options.

Portal - Create iView 2
Portal - Create iView 2

In our case we chose the option of creating an iview from an iview template. This in turn opens up a new page with lots more options. For example iview templates are available for BEX queries, SAP transactions, etc.

Portal - Create iView from template
Portal - Create iView from template

In the next post we go through the individual steps for creating an iview based on a SAP transaction

Portal Roles

Security for Enterprise Portal is based on Portal Roles. Portal Roles are created in the Portal Content Studio and are meant to structure the content displayed to a user on the Portal. Portal Roles are assigned to users through the identity management component of the portal just like UME roles. Multiple Portal roles can be assigned to a user which will impact the display of the enterprise portal for him. We look at structure one of the standard portal roles below

Portal Role - Content Admin
Portal Role - Content Admin

Content in a Portal Role is organized in a hierarchy of folders as shown above as worksets, iViews and pages. The folders in a portal role are called worksets. Worksets can be used across many portal roles. Also there can be multiple worksets under a workset. The lowest level of content are iViews. The screen above gives an example of Portal role in the PCD and the role structure showing both worksets and iviews. Also the same role “Content_Admin” is also assigned to my user id in the system. The top level navigation showing the different tabs like Content Administration > Portal Content> Multiple Property Replacement gives an idea of how a role looks when assigned to a user.

The behaviour of the role or workset can be changed by modifying the property editor settings shown on the far right. Also important is the permissions that can be modified in the property editor settings. An example of the permissions that can be set on the property editor for Content Admin role is copied below.

Portal Role - Content Admin - Permissions
Portal Role - Content Admin - Permissions

Enterprise Portal

SAP Enterprise Portal (EP) as a component can only be installed on AS Java. Till now our discussion on AS Java security has exclusively dealt with security using the User Management Engine. We have talked about UME users, roles and groups. However, in addition to UME roles, we can also create roles for Enterprise Portal. Before we start our deep dive into security for the enterprise portal lets take a brief tour of the Enterprise Portal solution.

To a large extent the Enterprise Portal to support display of content on the various corporate intranets (portals) of SAP customers. Thus the security framework for EP is also geared towards display of static or dynamic content rather than on granular security. To look. To get an idea about the look and feel of the Enterprise Portal just log in to the SAP Service Marketplace which is also built on EP.

Enterprise Portal - Look & Feel
Enterprise Portal - Look & Feel

To create content for Enterprise Portal, you need access to the Portal Content Studio shown below. You would also need access to the content_admin portal role.

EP - Portal Content Studio
EP - Portal Content Studio

Most of the Employee Self Service, Manager Self Service Applications are based on the Enterprise Portal. In addition, EP developers also can create portal applications for displaying BI dashboards, BW reports, webviews for SAP transactions and just simple static pages.

Most clients have a dedicated portal team instead of having security develop applications for portal. But I still feel that having some knowledge of portal is always helpful. Portal development normally starts by accessing the Portal Content Studio through the Portal Content Directory (PCD). Double clicking any content – iViews, Worksets, Roles opens the content in the right hand window for modification.