SAP ABAP IMG Activity BW_PORTAL_UMAP (Maintain User Assignment in the Portal)
Hierarchy
SAP_BW (Software Component) SAP Business Warehouse
   BW (Application Component) SAP Business Information Warehouse
     RS (Package) BW: General Business Information Warehouse
IMG Activity
ID BW_PORTAL_UMAP Maintain User Assignment in the Portal  
Transaction Code S_BR8_35000026   (empty) 
Created on 20040311    
Customizing Attributes BW_PORTAL_UMAP   Maintain User Assignment in SAP EP 
Customizing Activity BW_PORTAL_UMAP   Maintain User Assignment in SAP EP 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BW_PORTAL_UMAP    

Use

In this activity, you assign a user in the BW system to a user in the portal.

User mapping depends on the logon method specified in Creating a BW System in the Portal . User mapping always has to be maintained with the UIDPW logon method. User mapping is not necessary with the SAPLOGONTICKET logon method .

Irrespective of the logon method you are using, user mapping is required with the Publishing in the Portal in the Web Application Designer scenario if the technical user name in the portal is not the same as the technical user name of the BW system.

User mapping was previously only used to link a user in the portal with a user in the BW system. Now user mapping is also used to link a user in the BW system with a user in the portal (inverse user mapping). Mapping therefore has to be unique in both directions. This makes it impossible for muliple users in the portal to be be mapped to the same user in the BW system.

BEx Information Broadcasting uses the bw_service user in the portal. You have to either create a bw_service user in the BW system or define user mapping for bw_service to another user in the BW system.

User bw_service is created automatically in the portal when the BW system is called in the portal. This happens for example when checking the setting for creating RFC destinations for the portal . The bw_service user cannot be created manually in the portal.

Requirements

Make sure that all users have at least read access to the BW system created in step 7. Start the iView System Administration -> System Configuration -> System Landscape. Navigate to the system you have created, open the context menu and choose Open -> Authorizations. Search by user, user group or role, add these and assign the Read authorization.

Standard settings

Activities

Complete the following steps to maintain user mapping in the portal:

  1. Log on to the portal.
  2. Start iView User Management -> User Mapping.
  3. Choose User from the dropdown box.
  4. Enter a user or choose Start for all users.
  5. Choose Start.
  6. Choose a user and choose Edit.
  7. Choose the system alias for the BW system (see Creating BW Systems in the Portal).
  8. Enter the technical user name in the BW system.
  9. Enter the password.
  10. Save your entries.

Overview

This activity is a step in report Maintain Settings for Integration to Portal (RSPOR_SETUP). This report supports you in maintaining settings for integrating BW and the portal. Alternatively, you can call the individual steps in transactions RSPOR_CUST01 to RSPOR_CUST13.

The necessary parameters are requested upon execution. The individual parameters are described in the documentation Overview: Integration into Portal.

Example

Business Attributes
ASAP Roadmap ID 262   Technical and Graphical Settings 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BW_PORTAL_UMAP 0 ARS0000021 Business Explorer 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object RSPOR_CUST12  
History
Last changed by/on SAP  20050720 
SAP Release Created in 400