SAP BOBJ Planning & Consolidation (BPC), version for Netweaver How-To Guide How To... Use the BPC_NW Mass User Management Tool Applicable Releases: SAP BusinessObjects Planning & Consolidation 7.0, version for NetWeaver SAP BusinessObjects Planning & Consolidation 7.5, version for NetWeaver Version 1.0 August 2010
SAP BOBJ Planning & Consolidation (BPC), version for Netweaver How-To Guide Copyright 2010 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, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, 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. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way.
SAP BOBJ Planning & Consolidation (BPC), version for Netweaver How-To Guide Document History Document Version Description 1.00 First official release of this guide
SAP BOBJ Planning & Consolidation (BPC), version for Netweaver How-To Guide Typographic Conventions Type Style Example Text Example text Example text Example text <Example text> EXAMPLE TEXT Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Emphasized words or phrases in body text, graphic titles, and table titles File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER. Icons Icon Description Caution Note or Important Example Recommendation or Tip
SAP BOBJ Planning & Consolidation (BPC), version for Netweaver How-To Guide Table of Contents 1. Business Scenario... 1 2. Background Information... 1 3. Prerequisites... 1 4. Step-by-Step Procedure... 2 4.1 Exporting Users... 3 4.2 Importing Users... 4 4.3 Exporting Teams... 6 4.4 Importing Teams... 7 4.5 Exporting Team Assignments... 9 4.6 Importing Team Assignments... 11 4.7 Exporting Task Profiles... 16 4.8 Importing Task Profiles... 18 4.9 Exporting Member Access Profiles... 24 4.10 Importing Member Access Profiles... 26 4.11 Exporting Task Profile Assignments... 32 4.12 Importing Task Profile Assignments... 33 4.13 Exporting Member Access Profile Assignments... 38 4.14 Importing Member Access Profile Assignments... 40 5. Appendix... 46
1. Business Scenario In this guide, we will explore how to use a custom program to do mass maintenance of the SAP BusinessObjects Planning & Consolidation 7.0 and 7.5, version for NetWeaver (hence forward referred to as BPC_NW) security objects. These objects include users, teams, team assignments, task profiles, member access profiles, task profile assignments, and finally, member access profile assignments. This custom program uses the BPC_NW user management APIs, the same APIs used by the BPC_NW Admin Console, to correctly create or update the associated security objects. This program simply provides an interface which the user can use to upload files containing all of the relevant data in which the security objects can be created from. 2. Background Information Most BPC_NW security objects are not transportable using the BPC_NW Transport Framework. In some cases, it can be really cumbersome to re-create these objects throughout the landscape. This custom program allows the user to export as well as import all BPC_NW security objects. The export/import functions use comma, tab, or pipe delimited text files as the data transfer medium. Example files have been supplied with this guide. While the user can simply create files from scratch and upload them into the system, the real power of this program is that it allows the user to export these security objects from an AppSet, and then import them into another AppSet in the same system, or in a remote system, essentially transporting these objects across the landscape without using the BPC_NW transports framework. 3. Prerequisites Required/recommended expertise or prior knowledge SAP BusinessObjects Planning and Consolidation 7.0, version for SAP NetWeaver. SAP BusinessObjects Planning and Consolidation 7.5, version for SAP NetWeaver, Access to SAP NetWeaver transaction codes: SE38 Additional Documentation RKT Online Knowledge Product http://service.sap.com/rkt On the left hand side, navigate to SAP Ramp-Up Knowledge Transfer -> SAP BusinessObjects EPM Solutions -> SAP BO PC 7.5, version for SAP NetWeaver Other EPM How-To Guides http://wiki.sdn.sap.com/wiki/display/bpx/enterprise+performance+management+%28ep M%29+How-to+Guides August 2010 1
4. Step-by-Step Procedure This How-To guide contains transport request files, K900321.EPM and R900321.EPM. This transport request contains all the NetWeaver objects that are required to complete this How-To Guide. Programs ZUJE_MASS_USER_MGMT BPC_NW Mass User Management Tool As the process of importing a transport request is not covered here, it is suggested that you seek assistance from your basis administrator in order to have this transport request imported into your system. Note: These objects must be imported into your system before continuing any further. To begin using the tool, log on to the backend NetWeaver system via SAPgui, and run the ZUJE_MASS_USER_MGMT program from transaction code SE38, by entering the program name and clicking the Execute button. August 2010 2
4.1 Exporting Users 1. From the initial screen, select the appropriate radio button for Export Data. 2. Next, enter the name of the AppSet which contains the data which is to be exported. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the export file. Finally, select the delimiter value for the file. Comma, pipe, and tab delimiters are supported. 3. Next, select the appropriate radio button for Export Users. 4. Finally, click the Execute button to start the export process. August 2010 3
5. The output file is then generated. 4.2 Importing Users 1. From the initial screen, select the appropriate radio button for Import Data. 2. Next, enter the name of the AppSet where you want to create the users. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the import file. Finally, select the delimiter value for the file. Note: The file must contain the following structure in a comma delimited format: USER_ID FULLNAME EMAIL User ID Full Name of User Email Address of User The file structure is exactly the same as what is generated by the export function. An example file might look like the following: COMX_ALL\BROWNJ,Jane Brown,jane.brown@companyx.com COMX_ALL\SMITHJ,Joe Smith,joe.smith@companyx.com August 2010 4
Note: It is very important that the values in the FULLNAME column do not contain any commas if the delimiter is set to Comma. This will cause issues when parsing the data. We suggest using a different delimiter if your user s full name contains commas. 3. Select the appropriate radio button for Import Users. 4. To start the process, click the Execute button from the application toolbar. 5. The new users are then created for the AppSet and a message screen is displayed. This screen will show all associated success and failure messages. August 2010 5
... How To Use the BPC Mass User Management Tool 6. The new users can now be seen from the BPC_NW Admin Client. 4.3 Exporting Teams 1. From the initial screen, select the appropriate radio button for Export Data. 2. Next, enter the name of the AppSet which contains the data which is to be exported. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the export file. Finally, specify the delimiter. August 2010 6
3. Next, select the appropriate radio button for Export Teams. 4. Finally, click the Execute button to start the export process. 5. The output file is then generated. 4.4 Importing Teams 1. From the initial screen, select the appropriate radio button for Import Data. August 2010 7
2. Next, enter the name of the AppSet where you want to create the users. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the import file. Finally, specify the file delimiter. Note: The file must contain the following structure in a comma delimited format: TEAM_ID DESCRIPTION Team ID Description of the Team The file structure is exactly the same as what is generated by the export function. An example file might look like the following: ADMINTEAM,Administration Team ACCTEAM,Accounting Team 3. Select the appropriate radio button for Import Teams. 4. To start the process, click the Execute button from the application toolbar. August 2010 8
5. The new users are then created for the AppSet and a message screen is displayed. This screen will show all associated success and failure messages. 6. The new teams can now be seen from the BPC_NW Admin Client. 4.5 Exporting Team Assignments 1. From the initial screen, select the appropriate radio button for Export Data. August 2010 9
... How To Use the BPC Mass User Management Tool 2. Next, enter the name of the AppSet which contains the data which is to be exported. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the export file. Finally, specify the delimiter. 3. Next, select the appropriate radio button for Export Team Assignments. 4. Finally, click the Execute button to start the export process. 5. The output file is then generated. August 2010 10
4.6 Importing Team Assignments 1. From the initial screen, select the appropriate radio button for Import Data. 2. Next, enter the name of the AppSet where you want to create the users. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the import file. Finally, specify the delimiter. Note: The file must contain the following structure in a comma delimited format: USER_ID TEAM_ID TEAM_LEADER User ID Team ID Flag User ID as Team Leader(Optional) The file structure is exactly the same as what is generated by the export function. An example file might look like the following: COMX_ALL\SMITHJ,ADMINTEAM,X COMX_ALL\BROWNJ,ACCTEAM, August 2010 11
3. Select the appropriate radio button for Import Team Assignments. 4. To start the process, click the Execute button from the application toolbar. 5. The new team user assignments are then updated for the AppSet and a message screen is displayed. This screen will show all associated success and failure messages. August 2010 12
6. The new team assignments can now be seen from the BPC_NW Admin Client. First click on one of the teams. 7. From the action pane, click on Modify Team. August 2010 13
8. In the following dialog, click Next. August 2010 14
9. In the following dialog, you can see that the user has been assigned to the team correctly. If the user had been flagged as a Team Leader, the checkbox next to the user ID would be checked as well. August 2010 15
4.7 Exporting Task Profiles 1. From the initial screen, select the appropriate radio button for Export Data. 2. Next, enter the name of the AppSet which contains the data which is to be exported. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the export file. Finally, specify the delimiter. 3. Next, select the appropriate radio button for Export Task Profiles. 4. Finally, click the Execute button to start the export process. August 2010 16
5. The output file is then generated. August 2010 17
4.8 Importing Task Profiles 1. From the initial screen, select the appropriate radio button for Import Data. 2. Next, enter the name of the AppSet where you want to create the users. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the import file. Finally, specify the delimiter. Note: The file must contain the following structure in a comma delimited format. Since there are multiple sets of data associated with task profiles, the use of record level identifiers is leveraged here. Below are the record identifiers and their descriptions. Record Identifiers H K R T U Defines the header level data record Defines the Tasks assigned to the Task Profile Defines the Roles assigned to the Task Profile Defines the Teams assigned to the Task Profile(Optional) Defines the Users assigned to the Task Profile(Optional) H Record Structure PROFILE_ID DESCRIPTION Task Profile ID Task Profile Description K Record Structure PROFILE_ID Task Profile ID TASK_ID Task ID ( TASK_IDs found in tables UJE_TASK and UJE_TASKT ) August 2010 18
R Record Structure PROFILE_ID ROLE_ID Task Profile ID Role ID ( ROLE_IDs found in tables UJE_ROLE and UJE_ROLET T Record Structure PROFILE_ID TEAM_ID Task Profile ID Team ID U Record Structure PROFILE_ID USER_ID Task Profile ID User ID The file structure is exactly the same as what is generated by the export function. An example file might look like the following: H,COMX_ADMIN,CompanyX Administrator Task K,COMX_ADMIN,P0003 K,COMX_ADMIN,P0006 K,COMX_ADMIN,P0008 K,COMX_ADMIN,P0011 K,COMX_ADMIN,P0012 K,COMX_ADMIN,P0021 K,COMX_ADMIN,P0022 K,COMX_ADMIN,P0024 K,COMX_ADMIN,P0025 K,COMX_ADMIN,P0027 K,COMX_ADMIN,P0028 K,COMX_ADMIN,P0043 K,COMX_ADMIN,P0055 K,COMX_ADMIN,P0056 K,COMX_ADMIN,P0057 K,COMX_ADMIN,P0067 K,COMX_ADMIN,P0068 R,COMX_ADMIN,R02 R,COMX_ADMIN,R03 T,COMX_ADMIN,ADMINTEAM U,COMX_ADMIN,COMX_ALL\SMITHJ H,CC_MGR,CompanyX Cost Center Manager Task August 2010 19
K,CC_MGR,P0003 K,CC_MGR,P0006 K,CC_MGR,P0008 K,CC_MGR,P0056 K,CC_MGR,P0057 R,CC_MGR,R04 T,CC_MGR,ACCTEAM U,CC_MGR,COMX_ALL\BROWNJ 3. Select the appropriate radio button for Import Task Profiles. 4. To start the process, click the Execute button from the application toolbar. 5. The new task profiles are then created for the AppSet and a message screen is displayed. This screen will show all associated success and failure messages. August 2010 20
6. The new task profiles can now be seen from the BPC_NW Admin Client. First click on one of the new task profiles. 7. From the action pane, click Modify Task Profile. August 2010 21
8. In this dialog, you can see that the new task profile has been created with the associated description, as well as the assigned roles. Click Next. August 2010 22
9. In this dialog, you can see the assigned tasks. Click Next. August 2010 23
10. In this dialog, the assigned teams and users are displayed. 4.9 Exporting Member Access Profiles 1. From the initial screen, select the appropriate radio button for Export Data. August 2010 24
2. Next, enter the name of the AppSet which contains the data which is to be exported. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the export file. Finally, specify the delimiter. 3. Next, select the appropriate radio button for Export Member Access Profiles. 4. Finally, click the Execute button to start the export process. August 2010 25
5. The output file is then generated. 4.10 Importing Member Access Profiles 1. From the initial screen, select the appropriate radio button for Import Data. August 2010 26
2. Next, enter the name of the AppSet where you want to create the users. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the import file. Finally, specify the delimiter. Note: The file must contain the following structure in a comma delimited format. Since there are multiple sets of data associated with member access profiles, the use of record level identifiers is leveraged here. Below are the record identifiers and their descriptions. Record Identifiers H M T U Defines the header level data record Defines the Members assigned to the Member Access Profile Defines the Teams assigned to the Member Access (Optional) Defines the Users assigned to the Member Access (Optional) H Record Structure PROFILE_ID DESCRIPTION Member Access Profile ID Member Access Profile Description M Record Structure PROFILE_ID DIMENSION APPLICATION_ID MEMBER READ/WRITE Member Access Profile ID Dimension Application ID Assigned Member( Can contain [ALL]) Read and/or Write Access(R=Read, W=Write, D=Deny) T Record Structure PROFILE_ID TEAM_ID Member Access Profile ID Team ID U Record Structure PROFILE_ID USER_ID Member Access Profile ID User ID August 2010 27
The file structure is exactly the same as what is generated by the export function. An example file might look like the following: H,COMX_ADMIN_MAP,CompanyX Administrator MAP M,COMX_ADMIN_MAP,CATEGORY,PLANNING,[ALL],W M,COMX_ADMIN_MAP,P_CC,PLANNING,[ALL],W M,COMX_ADMIN_MAP,CATEGORY,RATE,[ALL],W M,COMX_ADMIN_MAP,R_ENTITY,RATE,[ALL],W U,COMX_ADMIN_MAP,COMX_ALL\SMITHJ T,COMX_ADMIN_MAP,ADMINTEAM H,CC_MGR_MAP,Cost Center Manager MAP M,CC_MGR_MAP,CATEGORY,PLANNING,ACTUAL,W M,CC_MGR_MAP,P_CC,PLANNING,Canada,W M,CC_MGR_MAP,P_CC,PLANNING,US,W M,CC_MGR_MAP,CATEGORY,RATE,[ALL],W M,CC_MGR_MAP,R_ENTITY,RATE,[ALL],W U,CC_MGR_MAP,COMX_ALL\BROWNJ T,CC_MGR_MAP,ACCTEAM 3. Select the appropriate radio button for Import Member Access Profiles. 4. To start the process, click the Execute button from the application toolbar. August 2010 28
5. The new member access profiles are then created for the AppSet and a message screen is displayed. This screen will show all associated success and failure messages. 6. The new member access profiles can now be seen from the BPC_NW Admin Client. First click on one of the new member access profiles. 7. From the action pane, click on Modify member access profile. August 2010 29
8. In this dialog, you can see that the new member access profile has been created with the associated description. Click Next. August 2010 30
9. In this dialog, you can see the associated members for this profile. Click Next. 10. In this dialog, the assigned teams and users are displayed. August 2010 31
4.11 Exporting Task Profile Assignments 1. From the initial screen, select the appropriate radio button for Export Data. 2. Next, enter the name of the AppSet which contains the data which is to be exported. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the export file. Finally, specify the delimiter. 3. Next, select the appropriate radio button for Export Task Profile Assignments. 4. Finally, click the Execute button to start the export process. August 2010 32
5. The output file is then generated. 4.12 Importing Task Profile Assignments 1. From the initial screen, select the appropriate radio button for Import Data. 2. Next, enter the name of the AppSet where you want to create the users. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the import file. Finally, specify the delimiter. Note: The file must contain the following structure in a comma delimited format. Since there are multiple sets of data associated with task profile assignments, the use of record level identifiers is leveraged here. You can assign both a user and a team to task profiles. Below are the record identifiers and their descriptions. Record Identifiers T U Defines the Teams assigned to the Task Profile(Optional) Defines the Users assigned to the Task Profile(Optional) August 2010 33
T Record Structure PROFILE_ID TEAM_ID Task Profile ID Team ID U Record Structure PROFILE_ID USER_ID Task Profile ID User ID The file structure is exactly the same as what is generated by the export function. An example file might look like the following: T,COMX_ADMIN,ADMINTEAM U,CC_MGR,COMX_ALL\BROWNJ 3. Select the appropriate radio button for Import Task Profile Assignments. 4. To start the process, click the Execute button from the application toolbar. August 2010 34
5. The new task profile assignments are then updated for the AppSet and a message screen is displayed. This screen will show all associated success and failure messages. 6. The new task profile assignments can now be seen from the BPC_NW Admin Client. First click on one of the task profiles. 7. From the action pane, click Modify Task Profile. August 2010 35
8. Click Next. 9. Click Next. August 2010 36
10. In this dialog, the assigned teams displayed. August 2010 37
11. Change the View By: drop down box to Users. Notice the user has been assigned to the task profile as well. 4.13 Exporting Member Access Profile Assignments 1. From the initial screen, select the appropriate radio button for Export Data. August 2010 38
2. Next, enter the name of the AppSet which contains the data which is to be exported. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the export file. Finally, specify the delimiter. 3. Next, select the appropriate radio button for Export Member Access Profile Assignments. 4. Finally, click the Execute button to start the export process. 5. The output file is then generated. August 2010 39
4.14 Importing Member Access Profile Assignments 1. From the initial screen, select the appropriate radio button for Import Data. 2. Next, enter the name of the AppSet where you want to create the users. In this guide, the APSHELL_HTG AppSet will be used for all examples. Also, enter the file path and file name for the import file. Finally, specify the delimiter. Note: The file must contain the following structure in a comma delimited format. Since there are multiple sets of data associated with member access profile assignments, the use of record level identifiers is leveraged here. You can assign both a user and a team to member access profiles. Below are the record identifiers and their descriptions. Record Identifiers T U Defines the Teams assigned to the Member Access Profile(Optional) Defines the Users assigned to the Member Access Profile(Optional) T Record Structure PROFILE_ID TEAM_ID Member Access Profile ID Team ID U Record Structure PROFILE_ID USER_ID Member Access Profile ID User ID August 2010 40
The file structure is exactly the same as what is generated by the export function. An example file might look like the following: U,CC_MGR_MAP,COMX_ALL\BROWNJ T,CC_MGR_MAP,ACCTEAM U,COMX_ADMIN,COMX_ALL\SMITHJ T,COMX_ADMIN,ADMINTEAM 3. Select the appropriate radio button for Import Member Access Profile Assignments. 4. To start the process, click the Execute button from the application toolbar. 5. The new member access profile assignments are then updated for the AppSet and a message screen is displayed. This screen will show all associated success and failure messages. August 2010 41
6. The new member access profile assignments can now be seen from the BPC_NW Admin Client. First click on one of the member access profiles. 7. From the action pane, click Modify member access profile. August 2010 42
8. Click Next. August 2010 43
9. Click Next. 10. In this dialog, the assigned teams displayed. August 2010 44
... How To Use the BPC Mass User Management Tool 11. Change the View By: drop down box to Users. Notice the user has been assigned to the task profile as well. August 2010 45
5. Appendix August 2010 46
www.sdn.sap.com/irj/sdn/howtoguides