installation guide bpc 10

Installation GuideSAP BusinessObjects Planning and Consolidation 10.0version for SAP NetWeaver

Target Audience System Administrators Technical Consultants

CUSTOMERDocument version: 1.5 2013-01-30

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

Copyright 2013 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, 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.

DisclaimerSome 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 SAPs Support Services and may not be modified or altered in any way.

2/48 CUSTOMER 2013-01-30

Typographic Conventions

Example Description Angle brackets indicate that you replace these words or characters with appropriate

entries to make entries in the system, for example, Enter your .Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressionsExample Words or characters that you enter in the system exactly as they appear in the

documentationExample Textual cross-references to an internet address, for example, http://www.sap.com/example Quick links added to the internet address of a homepage to enable quick access to specific

content on the Web123456 Hyperlink to an SAP Note, for example, SAP Note 123456Example Words or characters quoted from the screen. These include field labels, screen titles,

push button labels, menu names, and menu options. Cross-references to other documentation or published works

Example Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database toolsEXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2013-01-30 CUSTOMER 3/48

Document History

The following table provides an overview of the most important document changes:Version Date Description1.0 2012-04-26 Accompanies the GA release of SAP BusinessObjects Planning and Consolidation

10, version for SAP NetWeaver1.1 2012-05-01 In Post-Installation [page 23], added the first step of activating SAP technical business

content.1.2 2012-05-02 In Post-Installation [page 23], added the second step of generating required

authorization profiles and performing user mass comparison. Also minor edits were made to Configure the ABAP Server Component [page 24] and Log On [page 28]

1.3 2012-06-29 Updates for support package 07.1.35 2012-07-18 Minor editorial changes to the topic HTTPS Settings ICF Procedure [page 28].1.4 2012-11-05 Removed SAP note 1574604 from the topic Other Important Notes [page 8], as this note

was applicable only to SP00 and upgrades to SP01.1.45 2012-11-20 Added more browser versions to the topic Client Prerequisites [page 14].1.5 2013-01-30 In Configure the ABAP Server Component [page 24], added /POA/ to the list of namespaces

you can make changeable.

4/48 CUSTOMER 2013-01-30

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Planning the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Planning the Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1.1 Installation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1.2 Server Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1.3 Server Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.1.4 Installing the Server Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1.5 Acquiring the Planning and Consolidation Installation Components and

Support Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2 Client Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3 Planning for Event & Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4 Optional: Planning for Content Lifecycle Management . . . . . . . . . . . . . . . . . . 15

Chapter 3 Installing Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1 Installing and Configuring SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2 Installing the Add-In POASBC ABAP Component . . . . . . . . . . . . . . . . . . . . . . 203.3 Installing the Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.4 Installing the EPM Add-In for Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . 203.5 Installing an ABAP Server Component Support Package . . . . . . . . . . . . . . . . . 203.6 Installing the SAP HANA Component for Planning and

Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.7 Installing Planning and Consolidation during the update of

NetWeaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.1 Activate Your SAP Technical Business Content . . . . . . . . . . . . . . . . . . . . . . . . 234.2 Generate Required Authorization Profiles and Perform User Mass

Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.3 Configure the ABAP Server Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2013-01-30 CUSTOMER 5/48

4.4 Ensure ICF Services are Activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.5 Log On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.6 HTTPS Settings ICF Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.7 Configure Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.8 Post-Installation: Optional Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . 294.8.1 Update the Persistence Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.8.2 Set Up a Job to Publish Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.8.3 Enable Virus Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.8.4 Configure Content Lifecycle Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.8.5 Enable BWA for a Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 5 Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.1 SMS for Planning and Consolidation Package Delivery . . . . . . . . . . . . . . . . . . 37

Chapter 6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 7 Connecting to Solution Manager Diagnostics . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 8 Security Considerations and Connection Issues . . . . . . . . . . . . . . . . . . . . 438.1 Checking for Open Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438.2 Adobe Flash Player Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438.3 Proxy Server and Firewall Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 9 Terminal Services or Citrix Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459.1 Terminal Services Home Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459.3 Installing Planning and Consolidation in a Terminal Services or Citrix Server

Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459.4 Creating a Shortcut to the Launch Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6/48 CUSTOMER 2013-01-30

1 Introduction

The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for system administrators and technical consultants. It contains everything you need to know about installing the Planning and Consolidation components.

New Installation Program Features in 10.0The application is built on top of the NetWeaver Flex Client Platform and provides the necessary user environment capabilities. It allows the implementation of a rich flex-based user interface with a consistent look and feel and a common flexible user interaction model. It provides prebuilt components for reuse across different applications as well as configuration capabilities through its Flex runtime. It uses standard RESTful connectivity to the ABAP backend, ensures consistent accessibility of the user interface, and provides client-side localization and logging capabilities.Planning and Consolidation now supports virtualized production environments as described in SAP Notes 1098847 and 1409608.Content Lifecycle ManagementContent Lifecycle Management (CLM) aims to support the management of application content. This is achieved by providing users with a consistent way to package, version-control, inspect, and import vendor content into their systems. It focuses on the capability to deliver content from vendors landscapes to customers landscapes.It is not intended to provide a means to transport content within a single landscape; this is already facilitated by the ABAP transport system.Event & NotificationThe event and notification function allows you to create and send messages to users through various channels. Users can select the preferred delivery channel through which they want to receive messages. This is configurable; an administrator has the ability to predefine a channel for all users.This function also allows you to scan all message attachments using a Virus Scanner Interface (VSI) available on the server.ContextContext allows business users to track data selection in their workspaces. The application can use the selected data to guide what to display to the user.It enables context-aware interaction in the workspace environment. Users can alter the display of data based on the selection of dimension members at the different levels within a workspace. The hierarchy of visual containers is used to scope and filter the selected context data. When the workspace is saved the selected context is saved with it.

1 Introduction

2013-01-30 CUSTOMER 7/48

1.1 SAP Notes for the InstallationRead the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as additions to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at the Internet address http://service.sap.com/notes.SAP Note Number Title Description1586088 Planning and Consolidation 10.0 for

NetWeaver Documentation Addendum

Contains information that does not appear in the application help of Planning and Consolidation 10.0, version for the SAP NetWeaver platform.

1744028 SAP Planning and Consolidation 10.0 SP09, version for the NetWeaver platform

This note contains installation information, enhancements, and resolved issues for SAP Planning and Consolidation 10.0 SP09, version for the SAP NetWeaver platform.





1660062 Planning and Consolidation 10.0 SP06 Central Note








1 Introduction1.1 SAP Notes for the Installation

8/48 CUSTOMER 2013-01-30

SAP Note Number Title Description1580564 Planning and Consolidation 10.0

SP02 Central NoteThis note contains installation information, enhancements, and resolved issues for SAP Planning and Consolidation 10.0 SP02, version for the SAP NetWeaver platform.



SAP Notes for POASBC Add-On InstallationYou must read the following SAP Note before you start the installation. This SAP Note contains the most recent information on the installation, as well as corrections to the installation documentation.SAP Note Number Title Description1511393 Release strategy for the ABAP add-on

POASBCThis note provides information about planning the installation and upgrade of ABAP add-on POASBC.

1568391 Installing POASBC 100_730 You want to install an add-on.1573237 Upgrade to NW 730 with POASBC

100_730This note contains information about upgrading with POASBC.

Other Important NotesSAP Note Number Title1575575 Add default formula when installing EnvironmentShell1578760 MDX: Error _MEMBER_GET_FULL_3 for external hierarchies1586265 New Master Data Deletion - Redundant table locks removed

1.2 Naming ConventionsIn this document, the following naming conventions apply.Variable Description Server name or IP address and port number of the Planning and Consolidation application

location. The drive where Planning and Consolidation is installed.

The default for this is C:\PC_NW.

1 Introduction1.2 Naming Conventions

2013-01-30 CUSTOMER 9/48

This page is left blank for documents that are printed on both sides.

2 Planning the Installation

This section describes the planning activities you must carry out before installing the software components required for Planning and Consolidation.

2.1 Planning the Server InstallationBefore installing the Planning and Consolidation server, complete the following planning activities.1. Make sure your hardware is appropriate for the server tiers. See Hardware Requirements [page 11].2. Verify that you have the required prerequisites installed on the server. If not, install them. See

Server Prerequisites [page 12] and Installing the Server Prerequisites [page 13].3. Download the Planning and Consolidation server components from SAP Service Marketplace. See

Acquiring the Planning and Consolidation and ABAP Server Components [page 13].

2.1.1 Installation ScenariosYou can install the ABAP server component in one of the following configurations: On an existing SAP NetWeaver AS ABAP system (that meets minimum prerequisites) On a completely new SAP NetWeaver AS ABAP system During an update from NetWeaver 7.3 to NetWeaver 7.3 Including Enhancement Package 1. For

more information about this scenario, see Installing Planning and Consolidation during the update of NetWeaver [page 22].

The supported SAP NetWeaver releases are: SAP NetWeaver AS ABAP 7.3 SAP NetWeaver AS ABAP 7.3 Including Enhancement Package 1 (as of Planning and Consolidation

10.0 SP07)

2.1.2 Server Hardware RequirementsProcedureBefore starting the Planning and Consolidation installation, make sure you follow the hardware requirements for the ABAP application server.The ABAP application server can run on any supported NetWeaver platform. For information about the requirements for this server, see the NetWeaver Master Guide and Installation Guide at https://service.sap.com/installnw73.

2 Planning the Installation2.1 Planning the Server Installation

2013-01-30 CUSTOMER 11/48

2.1.3 Server PrerequisitesYou must install the following requirements on the ABAP application server before installing the Planning and Consolidation server components:

For SAP NetWeaver 7.3 SAP NetWeaver 7.3 SP02

Application Server ABAP PI_BASIS 7.3 Application Server ABAP SAP ABA 7.3 Application Server ABAP SAP BASIS 7.3 Application Server ABAP SAP BW 7.3 Kernel (64-bit) and Unicode only

An operating system supported by SAP NetWeaver A database supported by SAP NetWeaver SAP NetWeaver Add-in POASBC ABAP component version POA_SBC_100_730For SAP NetWeaver 7.3 Including Enhancement Package 1 SAP NetWeaver 7.3 Including Enhancement Package 1

Application Server ABAP PI_BASIS 7.31 Application Server ABAP SAP ABA 7.31 Application Server ABAP SAP BASIS 7.31 Application Server ABAP SAP BW 7.31 Kernel (64-bit) and Unicode only

An operating system supported by SAP NetWeaver A database supported by SAP NetWeaver SAP NetWeaver Add-in POASBC ABAP component version POA_SBC_100_731

NOTEA list of the supported operating systems and database systems is also available in the Product Availability Matrix on SAP Service Marketplace at http://service.sap.com/pam. Search on Planning and Consolidation.For information on installing the prerequisite software, see Installing the Server Prerequisites [page 13].

SAP HANAIf you choose to use Planning and Consolidation with SAP HANA component HANABPC, you must run SAP NetWeaver 7.3 SP06 with its own HANA database revision 26 or higher.


12/48 CUSTOMER 2013-01-30

2.1.4 Installing the Server PrerequisitesFor information about installing SAP NetWeaver, the required software, and the supported databases for the ABAP application server, see https://service.sap.com/instguidesNW73.It is important that you refer to the following SAP Notes and apply the indicated corrections:SAP Note Number Title93042 Problems with SAPFTP1352953 DB6: Runtime error SYNTAX_ERROR in DBA Cockpit1537619 Changes to function group SROLETOOLSBPC1545834 MS Access 97: Incorrect version of Wdpsam97.exe1553052 OLE DB for OLAP: Transient queries in cube schema rowset1558149 OLE DB for OLAP: Error handling for cube rowset1561043 RSD1: Error adding navigation attribute for master data1560836 Class CL_ABAP_ZIP, Handle Leading 0x00000000 in ZIPs

2.1.5 Acquiring the Planning and Consolidation Installation Components and Support Packages

ProcedureYou must download the Planning and Consolidation 10.0 installation files and the required support packages.1. To download the installation files for Planning and Consolidation 10.0:

Go to http://service.sap.com/swdc Software Downloads Installations and Upgrades A - Z Index"B" SAP BPC FOR SAP NETWEAVER SBOP PC 10.0 FOR SAP NW Installation Downloads .

For SAP NetWeaver 7.3 the download object number is: 51040691 (Title: SAP Business Planning & Cons 10.0 NW ).

For SAP NetWeaver 7.3 Including Enhancement Package 1 the download object number is: 51043139 (Title: SBOP PC 10.0 FOR SAP NW 731).

NOTETo use SAP NetWeaver 7.3 Including Enhancement Package 1, the minimum required support package for Planning and Consolidation 10.0 is SP07.

2. To download support packages:Go to http://service.sap.com/swdc Software Downloads Support Packages and Patches A - Z Index

"B" SAP BPC FOR SAP NETWEAVER SBOP PC 10.0 FOR SAP NW Comprised Software Component Versions .Download the following : POA SBC 100_730 Support Packages Downloads . SAP EPM BPC ABAP 10.0 Support Packages Downloads .


2013-01-30 CUSTOMER 13/48

3. Click on a component you want to download and add the component to your Download Basket. Repeat this step for each component you want to download, using the links at the top of the page to locate other related components.

4. Download the components from the Download Basket using SAP Download Manager.

NOTEFor information about using the SAP Download Manager, go to https://service.sap.com/support and choose my Download Basket from the my Personalized Information pane.

2.2 Client PrerequisitesPlanning and Consolidation requires the following software for the Web client: A supported operating system. A list of supported operating systems available in the Product

Availability Matrix on SAP Service Marketplace at http://service.sap.com/pam. Search on Planning and Consolidation.

Microsoft Internet Explorer 7.0 or 8.0 As of support package 06: Microsoft Internet Explorer 9.0 32bit As of support package 07: Mozilla Firefox 8.0

To use the EPM Add-in in Mozilla Firefox, you must first install the EPM Plug-in for Firefox. Adobe Flash Player 10.2 or later For the EPM Add-in for Microsoft Office:

Microsoft Office 2007 or 2010 32-bitAs of support package 07 you can also use Microsoft Office 2003

Microsoft .NET Framework 3.5 SP1 Microsoft Web Services Enhancement 3.0 (WSE 3.0) Microsoft XML Parser 6.0 SP1NOTEFor more information about the installation prerequisites for the EPM Add-in, see the EPM Add-in for Microsoft Office Installation Guide.

2.3 Planning for Event & NotificationThe following tables hold the default configuration and can be configured through transaction SM30: /POA/D_ENDEFPREF: Master User Preferences for Default ValuesSample contents of the preference table are listed here:

2 Planning the Installation2.2 Client Prerequisites

14/48 CUSTOMER 2013-01-30

Item Description TypeCommunication Method Editable

Default Value

AUTOREFRESHENABLED Enable Auto-Refresh

Types Related to User/UI

Other Types Yes TRUE

AUTOREFRESHRATE Auto-Refresh Rate Types Related to User/UI

Other Types Yes 300

EMAIL E-Mail (external) Delivery Channel Type

Internet Mail Address

Yes TRUE

INBOX My Messages Delivery Channel Type

User (Receive via User Preferences: E-Mail, My Messages)

Yes TRUE

VSCAN VScan Attachments

Types Related to Back-End Services

Other Types No TRUE

VSI_PROFILE VSI Profile for scan Types Related to Back-End Services

Other Types No -

2.4 Optional: Planning for Content Lifecycle ManagementNOTEConfiguring Content Lifecycle Management (CLM) is not a mandatory part of the BPC NW 10.0 installation.

The following preparation and planning activities are required for Content Lifecycle Management.Preparing to Install Content Lifecycle ManagementFor more information about installing Content Lifecycle Management (CLM) as a standalone add-on, see SAP Service Marketplace at http://service.sap.com/securityguide SAP NetWeaver

SAP NetWeaver Security Guide Security Aspects for Lifecycle Management Security Issues in ABAP Software Maintenance Add-On Installation Tool (if CLM is being installed in standalone mode).See application-specific installation steps, which would include installation of CLM (if installation is being done together with application itself).If you are using Content Lifecycle Management in standalone mode, you can access the Customizing activities as follows:1. Run transaction SIMGH.2. Search for structure Content Lifecycle Management using F4 help.

You can add this structure as a favorite.3. Choose display mode.4. You can now maintain the Customizing activities.Identifying Managed Application SystemsIt is not necessary to identify all managed application systems during CLM installation as you can add extra application systems at a later stage and configure them for communication to CLM. However,

2 Planning the Installation2.4 Optional: Planning for Content Lifecycle Management

2013-01-30 CUSTOMER 15/48

identifying the application systems at this stage can provide a good overview of the overall landscape in the context of CLM and can help you to decide on existing systems that can be used for CLM installation.The systems for which content is to be managed must be technically capable of integrating with Content Lifecycle Management (CLM). Apart from the current application (with which CLM is shipped), it is possible to integrate with further applications.

RECOMMENDATIONWe recommend integrating Content Lifecycle Management with the following: Consolidation system for deploying content before deploying that content to the actual

production system.

Choosing Landscape ModelYou need to decide whether the integrated or standalone mode of the Content Lifecycle Management (CLM) system is more appropriate for your scenario.Refer to technical system landscape section in the master guide for the application.

CAUTIONTo enable communication between connected SAP systems it might be necessary to set up trust relationships between systems. When planning the installation of Content Lifecycle Management on an already existing application system instance alongside an existing application, security and performance considerations must be taken into account.

Identifying Roles and ActivitiesContent Lifecycle Management only delivers sample technical roles containing authorizations for various managed applications and with supported features for each managed application. The delivered roles are only for reference for a particular managed application; for more restrictions, you need to plan what roles can exist with regard to CLM and what CLM activities can users with these roles perform. Documentation of the CLM-based authorization objects and delivered technical roles is included in the Security Guide.

RECOMMENDATIONWe recommend to have the same users for both CLM and the application. The CLM authorization object can be assigned to users specific to the application via Netweaver ABAP user and role management.Authorization checks for application-specific objects and roles are part of the application itself. Since CLM interacts with these applications for content extraction and deployment; unauthorized access to content can only be prevented if the same user is used in both CLM and the application.

Ensuring Secure Connection for Files


16/48 CUSTOMER 2013-01-30

If you intend to create or import content packages with attachments/supporting files apart from application content, make sure that CLM is connected to a secured desktop. CLM uses local desktop for attachments/files upload and download within content packages. Make sure that CLM users have sufficient authorization to access local files.


2013-01-30 CUSTOMER 17/48

3 Installing Planning and Consolidation

The main steps for installing Planning and Consolidation are the following:1. Install and configure SAP NetWeaver see Installing and Configuring SAP NetWeaver [page 19].2. Install the add-in POASBC ABAP component see Installing the Add-In POASBC ABAP Component

[page 20].3. Install Planning and Consolidation and the ABAP add-on server component see Installing the Server

Components [page 20].4. Install the EPM Add-in for Microsoft Office see Installing the EPM Add-In for Microsoft Office [page

20].After the initial installation of Planning and Consolidation, see Installing an ABAP Server Component Support Package [page 20] for details of installing support packages.If you choose to use Planning and Consolidation with SAP HANA, download and install the add-in software component HANABPC. See Installing the SAP HANA Component for Planning and Consolidation [page 21].

NOTEYou can also install Planning and Consolidation as part of an update from NetWeaver 7.3 to NetWeaver 7.3 Including Enhancement Package 1. For more information, see Installing Planning and Consolidation during the update of NetWeaver [page 22].

3.1 Installing and Configuring SAP NetWeaverBased on your configuration, you can install Planning and Consolidation on an existing SAP NetWeaver technology platform, or you can install it on a new SAP NetWeaver platform. The Business Intelligence usage type is required.

ProcedureIf you are installing on a new SAP NetWeaver technology platform, you must first follow the steps outlined in the SAP NetWeaver installation documentation see https://service.sap.com/instguidesNW73.After you install SAP NetWeaver, configure it based on the guidelines in the SAP NetWeaver documentation. This means you must ensure all the post installation steps have been completed, including (but not limited to) setting up the Data Warehousing Workbench (RSA1) for normal use.

3 Installing Planning and Consolidation3.1 Installing and Configuring SAP NetWeaver

2013-01-30 CUSTOMER 19/48

3.2 Installing the Add-In POASBC ABAP ComponentCheck the system status dialog to ensure that there is not already a component with a name starting POASBC installed.Install the POASBC ABAP component using transaction SAINT.

3.3 Installing the Server ComponentsPrerequisites You have downloaded the server components from SAP Service Marketplace. See Acquiring the

Planning and Consolidation and ABAP Server Components [page 13]. You have read the topic System and Client Settings in SAP Library at http://help.sap.com/

saphelp_46c/helpdata/en/2e/d9530294f911d283d40000e829fbbd/frameset.htm for information about which client to use when installing SAP BusinessObjects Planning and Consolidation on SAP NetWeaver.

Make sure that Business Warehouse (BW) is activated and that Planning and Consolidation is activated in the same client as BW.

ProcedureTo install the server components, use the transaction SAINT.For information about using SAINT, see http://help.sap.com/saphelp_nw73/helpdata/EN/49/3e896728ab2222e10000000a42189d/frameset.htm.

3.4 Installing the EPM Add-In for Microsoft OfficeSAP BusinessObjects EPM Solutions, add-in for Microsoft Office provides business users the capability to analyze data from within supported SAP BusinessObjects EPM applications, using Microsoft Office tools: Excel, Word or PowerPoint. EPM Add-in for Microsoft Office creates the reports on and analyzes the data from Planning and Consolidation.You can connect to the EPM Add-in for Microsoft Office through the Planning and Consolidation web portal.For details of how to install and configure the EPM Add-in, see the EPM Add-in for Microsoft Office Installation Guide.

3.5 Installing an ABAP Server Component Support PackageYou can download and import support packages to update the ABAP add-on server component.

3 Installing Planning and Consolidation3.2 Installing the Add-In POASBC ABAP Component

20/48 CUSTOMER 2013-01-30

PrerequisitesThe RFC destination for transport must be properly configured before importing a support package. Perform the following steps to configure the destination:1. Run transaction SM59 to create the RFC destination and make sure the client, user and PW Status

are configured properly.2. Use Connection Test to verify the RFC destination. All of the connection tests should pass.3. Use Remote Logon to verify the RFC destination. This should logon to the system directly without

prompting for a password.4. Run transaction RSTPRFC to set the BW client and name of the destination.

ProcedureFollow the instructions in SAP Note 1582356 for downloading and importing add-on support packages.

3.6 Installing the SAP HANA Component for Planning and Consolidation

Follow these instructions to install the SAP HANA Component for Planning and Consolidation. This component accelerates report generation within Planning and Consolidation.

PrerequisitesYou have applied the following SAP Notes: 1680983 1658749 1566845 1654731Reports in Planning and Consolidation can be accelerated using the SAP HANA Component for Planning and Consolidation when they meet the following conditions: The storage type of the model is Periodic. The reports do not contain any members with formulas. A standard measure option in Planning and Consolidation is in use, such as Periodic, QTD, or YTD. Only one Planning and Consolidation cube exists under its corresponding SAP Business Warehouse

multi-provider.

Procedure1. Download the SAP HANA Component for Planning and Consolidation HANABPC from SAP

Service Marketplace.2. Install the component using transaction SAINT.3. Run the program BPC_HANA_MIGRATE_FROM_10 to migrate your version 10 environments.4. Set the IMG parameter ENABLE_ACCELERATOR to Y.

3 Installing Planning and Consolidation3.6 Installing the SAP HANA Component for Planning and Consolidation

2013-01-30 CUSTOMER 21/48

5. Turn on the shared memory hierarchy. See SAP Note 1657612 for more information.

3.7 Installing Planning and Consolidation during the update of NetWeaver

If you plan to update your SAP NetWeaver system from NetWeaver 7.3 to NetWeaver 7.3 Including Enhancement Package 1, you can include the Planning and Consolidation components in the update process. To do this, you must select Planning and Consolidation in the Select Add-on Products step in the Maintenance Optimizer (MOPZ). After that you use the Software Update Manager (SUM) tool to update your system.For more information, see SAP Note 1704901.For more information about the SUM tool, see Update Guide - Update of SAP Systems Using Software Update Manager that is available on the SAP Service Marketplace at: http://service.sap.com/sltoolset Software Logistics Toolset 1.0 SUM .

3 Installing Planning and Consolidation3.7 Installing Planning and Consolidation during the update of NetWeaver

22/48 CUSTOMER 2013-01-30

4 Post-Installation

The main steps after installing Planning and Consolidation are the following:1. Activate your SAP technical business content see Activate Your SAP Technical Business Content [page

23].2. Generate the required authorization profiles and perform a User Mass Comparison see Generate

Required Authorization Profiles and Perform User Mass Comparison [page 24].3. Configure the Planning and Consolidation ABAP add-on see Configure the ABAP Server Component

[page 24].4. Ensure that Internet Communication Framework services are activated see Ensure ICF Services are

Activated [page 27].5. Log on see Log On [page 28].6. Enable HTTPS for the ABAP server see HTTPS Settings ICF Procedure [page 28].7. Configure Single Sign-on see Configure Single Sign-on [page 28]8. Set up the SLD Data Supplier, which is the central directory of all of your system landscape

information. For more information, see Configuring the SLD Data Supplier in the Administrator's Guide.9. Optional configuration steps [page 29]:

1. Update the Persistence Service see Update the Persistence Service [page 29].2. Set up a job to publish messages see Set Up E-mail Job [page 31].3. Enable virus scanning see Enable Virus Scan [page 32].4. Configure Content Lifecycle Management see Post-Installation of Content Lifecycle Management

[page 32].

4.1 Activate Your SAP Technical Business ContentProcedure1. Go to transaction RSA1 and select BI Content.2. Choose Object Types.

Make sure Grouping is set to In Dataflow Before and Aftrwds and Collection Mode is set to Collect Automatically.

3. Expand the InfoObject type and double-click Select Objects.4. Filter the InfoObjects using the wildcard 0TCA*.5. Ensure that all of the objects are active.

If they are not active, activate them using the Install button.

4 Post-Installation4.1 Activate Your SAP Technical Business Content

2013-01-30 CUSTOMER 23/48

4.2 Generate Required Authorization Profiles and Perform User Mass Comparison

Procedure1. Go to transaction PFCG in SAP NetWeaver.2. Choose Utilities Mass generation .3. In Additional restrictions, use a wildcard to filter for roles containing *BPC* and *POA*.4. Choose All Roles and select Generate automatically.5. Execute the program.

Display the system log when the program finishes, if desired.6. Return to transaction PFCG in SAP NetWeaver.7. Choose Utilities Mass comparison .8. In Selection of roles, use a wildcard to filter for roles containing *BPC* and *POA*.9. Execute the program.

Display the system log when the program finishes, if desired.10. Close the PFCG transaction window.

4.3 Configure the ABAP Server ComponentYou must configure the ABAP server component after installing it.This procedure includes information about running the UJS_ACTIVATE_CONTENT program, which is how the default environment, EnvironmentShell, is created. It installs the EnvironmentShell environment by leveraging parts of the Planning and Consolidation transport framework. This program also supports the installation of many other table entries that are required in order for the system to work correctly, such as language settings, BW Business Content, and data manager instructions.

NOTEThe UJS_ACTIVATE_CONTENT program cannot be used to activate an existing environment migrated from 7.5 to 10.0.

The activation program loads only dimension members (master data) for EnvironmentShell; the program does load transaction data. The Clean option deletes BW objects of the environment and its entries in the Planning and Consolidation UJ* metadata tables. If you use the Clean option on EnvironmentShell, refer to SAP Note 1615644.

PrerequisitesThe ABAP server component has been installed.You have activated your SAP Business Content.

4 Post-Installation4.2 Generate Required Authorization Profiles and Perform User Mass Comparison

24/48 CUSTOMER 2013-01-30

CAUTIONSet the ABAP buffer size to at least 2 GB to minimize the risk of errors during the UJS_ACTIVATE_CONTENT step of the procedure. You can set the buffer size using the parameter abap/buffersize in the instance profile with transaction RZ10.After completing the step, you can change it back. After changing the parameter, you must restart the ABAP instance, for example, with the SAP Management Console.For more information about changing the buffer size, see SAP Note 1273283.

ProcedureThese steps are required for proper functioning of the Planning and Consolidation software.Logistic System for Planning and ConsolidationVerify that the BW client on which you are installing EnvironmentShell is modifiable using transaction SCC4. When it is set to "No changes allowed" an exception occurs during the installation.Apply Required SAP NotesIt is important that you refer to the following SAP Notes and apply the indicated corrections:SAP Note Number Title1572695 MDX: System-wide call of old parser implementation

Make Namespaces and Software Components ChangeableFor maximum flexibility, you can make the following namespaces and software components changeable: Namespaces:

/CPMB/ /1CPMB/ /B28/ /POA/ Customer Name Range General SAP Name Range

Software Components: CPMBPC HOME LOCAL

However, in a production environment, you may want to minimize the number of components that can be modified. If this is the case, you can set the following namespaces and software components to unchangeable: Namespaces:

/1CPMB/ Customer Name Range

4 Post-Installation4.3 Configure the ABAP Server Component

2013-01-30 CUSTOMER 25/48

General SAP Name Range /CPMB/ /B28/

Software Components: CPMBPC

Use the following procedure to set the components to Modifiable or Unmodifiable:1. Enter transaction SE06 and choose System Change Option.2. Make sure that the Planning and Consolidation Addon is set to Restricted Modifiability.3. Set the namespaces and software components to Modifiable.Import Client-Dependent ObjectsUsing transaction RSTPRFC, set up transports by creating the RFC destination for the After Import method. Save the password, then assign the BW client. For more information, see http://help.sap.com/saphelp_nw73/helpdata/en/45/b517e0ed2f52f5e10000000a1553f7/content.htm.If the transport fails, see SAP Note 1329561 for information.Run Connection Test on RFC Destination MDX PARSEREnter transaction SM59 and run a connection test on the RFC destination MDX PARSER.

NOTEIf this fails, apply SAP Note 1032461. After applying this note, you must restart the ABAP server.

Assign Authorization to Installation UserAssign the authorization SAP_BW_CONTENT_ADMIN to the user installing EnvironmentShell as the Planning and Consolidation system administration user to activate business content (such as default BW objects).We recommend that you also assign the SAP_ALL profile during the installation process of EnvironmentShell. You can remove the SAP_ALL profile after the installation.Create a Service UserThe service user that you create is used for BPC background processing.1. Create a service user, as follows: Enter transaction SU01, create a user with user type System (for

example, BPC_SERVICE).2. Assign the role SAP_BPC_SERVICE to this user.

NOTEIn the SAP_BPC_SERVICE role, for the authorization object /POA/A_BPT, verify that the value /POA/PSAPP is /POA/BPC/WEB (and not /POA/BPC/WEB).

Create and Asssign BPC RFC Destination1. Enter transaction SM59. Create an RFC destination to point to the client on which Planning and

Consolidation is installed and run. In the Logon & Security tab, enter the service user created above with the correct password.

4 Post-Installation4.3 Configure the ABAP Server Component

26/48 CUSTOMER 2013-01-30

2. Enter transaction SPRO. Choose SAP Reference IMG SAP Customizing Implementation Guide Planning and Consolidation Configuration Parameters Set Global Parameters . Choose New. In Field Name enter RFC_DESTINATION and press Enter . In Value enter the RFC destination created above, save the change and quit. Set the type of the RFC destination to Connection to ABAP System (type 3). Set the Communication Type to Unicode

Install EnvironmentShell1. Run the program UJS_ACTIVATE_CONTENT.2. In the Content Activation window, set the Environment ID to EnvironmentShell and the Content Version to 1.3. Choose the following options:

Update Language Activate BI Business Content Update Default DM Instructions Activate EnvironmentShell Update Default Formulas Table

4. Select Program Execute .5. Check the logs by selecting System Own Jobs .6. Select the job and display the spool.

NOTEThere can be an X_MESSAGE exception when running UJS_ACTIVATE_CONTENT to activate the environment EnvironmentShell. For details of how to resolve this issue, see SAP Note 1576929.

4.4 Ensure ICF Services are ActivatedPrerequisitesPOASBCThe software component, POASBC has been installed in your ABAP system.

ProcedureUse transaction SICF to verify that the following services are activated:

For Planning and Consolidation1. Verify that all services under /sap/EPM_BPC are activated.2. Verify that all services under /sap/poa are activated.3. Verify that all services under /sap/public/bc are activated.

For the EPM ConnectorVerify that the services under /sap/bw/xml/soap/xmla/ are activated.

4 Post-Installation4.4 Ensure ICF Services are Activated

2013-01-30 CUSTOMER 27/48

4.5 Log On1. Verify the HTTP port configured for your ABAP system using transaction SMICM.2. Log on with your user on the ABAP system.

Pattern: http://:/sap/bpc/webFor information about setting up users and assigning authorizations, see the Security guide.

4.6 HTTPS Settings ICF ProcedureProcedure1. Ensure that https is enabled for the ABAP server and that the port for https is configured.

To view the https port:1. Go to transaction SMICM.

This opens the Internet Communication Manager (ICM) Monitor.2. Choose Goto Services or press SHIFT + F1.3. If the https port is configured, you can view the port.

2. Test whether the Secure Sockets Layer (SSL) server certificate is installed correctly. To do so, run the URL https://:/sap/bc/bsp/sap/it00.Replace with the ABAP server's Fully Qualified Domain Name (FQDN) and with the port number you retrieved in transaction SMICM.If there is no certificate error, the SSL server certificate is installed correctly.

3. Go to transaction SICF. Choose SERVICE for the Hierarchy Type field and choose Execute (F8).Expand the tree view under Virtual Hosts /Services to display default_host sap poa fcp .

4. Switch the setting for each of the Flex Client Platform (FCP) services to https:1. Double-click fcprt service.2. Go to Error Pages Logon Errors .3. Choose Change or press CTRL + F1.4. Select System Logon.5. Choose Configuration.6. Select Define Service-Specific Settings.7. Choose Switch to HTTPS from the Protocol dropdown menu.8. Under SAP Implementation, choose any screen from the dropdown menu for SAP Theme.9. Execute steps 2 to 8 for each of the FCP services - core, container, fetcher and logger.

4.7 Configure Single Sign-OnYou must configure the server to support single sign-on (SSO). Follow the recommendations in SAP Notes 495911 and 817529 for configuring SSO and checking the configuration.

4 Post-Installation4.5 Log On

28/48 CUSTOMER 2013-01-30

For more details about possible SSO configurations, see Integration into Single Sign-On Environments in the Planning and Consolidation Security Guide and User Authentication and Single Sign-On in the SAP NetWeaver Security Guide. Security guides are available on SAP Service Marketplace at http://service.sap.com/securityguide.

4.8 Post-Installation: Optional Configuration StepsThe steps listed below are optional.1. Update the Persistence Service see Update the Persistence Service [page 29].2. Set up a job to publish messages see Set Up E-mail Job [page 31].3. Enable virus scanning see Enable Virus Scan [page 32].4. Configure Content Lifecycle Management see Post-Installation of Content Lifecycle Management [page

32].5. Enable BWA for a Model see Enable BWA for a Model [page 35]

4.8.1 Update the Persistence ServiceTransportable content with the persistence service can be added to a Customizing workbench request and transported to other systems. The ABAP backend provides a report, which starts an administrator UI. The administration UI displays the content tree of the specified partition. Within the content tree, you can select and add transportable resources to an ABAP Customizing transport request.

Prerequisites You need to have an ABAP server with the latest persistence service installed. You must have a client on this ABAP server configured to support Customizing requests. You need to have ABAP knowledge. You must have a user with unlimited authorizations for persistence service and transport tasks.Procedure1. Launch the transport UI for a given partition.

In this step, you specify the partition and see it as a content tree.1. Execute the report /POA/R_PST_TRS_CUST_CTN.2. Specify the partition you want to launch by entering the corresponding namespace and sub

namespace.Choose Execute.

2. Check details of resources in the content tree.If the partition already exists, you can see the resources highlighted in different colors according to the legend.

4 Post-Installation4.8 Post-Installation: Optional Configuration Steps

2013-01-30 CUSTOMER 29/48

Legend Entry

Properties Status Color Code Explanation Example

Sample Node Created

Created in the index table

Light blue background

You have created a resource with transportable content type. It is displayed in this status since it was created in the index tables, but has not been written to the transport tables. Selecting such a resource and choosing Add Selected synchronizes the resource and also writes it to the corresponding transport request.

Create a workspace within the SAP folder.

Sample Node Del From Idx

Deleted from the index table

Red A resource exists in the index and transport tables and is then deleted via the UI or the persistence service API, it is displayed in this status. Deleting via the UI removes it from the index tables, but not from the transport tables. Selecting such a resource and choosing Add Selected synchronizes the resource and removes it from the transport tables. This also adds a corresponding transport request entry.

Delete a workspace within the SAP folder, which was previously marked as in sync. Restart the transport Administration UI.

Sample Node Updated

Updated in the index table

Yellow A resource already exists in the index and transport tables, but an update has occurred via the UI and the version in the transport table is not up-to-date. Selecting such a resource and choosing Add Selected synchronizes the resource and updates the resource within the transport tables. This also adds it to the corresponding transport request.

Change the description of workspace within the SAP folder, which was previously marked as in sync. Restart the transport Administration UI.

Sample node Trp Upd Available

Transport update available

Blue An incoming transport request contains a resource; the transported tables have been updated accordingly, but the index tables have not. Choosing Import synchronizes all these resources regardless of your selection and adapts the information within the index tables. Note: An incoming import may result in deleting, updating, or creating the corresponding resource within the index tables.

Transport a resource to another system and launch the transport Administration UI there.

3. Synchronize between transparent and transport tables. To synchronize resources for which an update in the index tables is available, choose Select

Changed within the Export group.Choose Export Selected.The status only changes after re-executing the transport Administration UI.

To synchronize resources for which an update via transport is available, choose Select Changed within the Import selected group.Choose Import Selected.


30/48 CUSTOMER 2013-01-30

The status only changes after re-executing the transport Administration UI. Execute /POA/R_PST_TRS_CUST_CTN for the same partition again. These nodes are no

longer highlighted.4. Add resources to the Customizing request.

The Select All button allows you to select all transportable resources of the given partition at the same time.

If you want to select particular resources you need to click those resources. The Export Selected button adds all selected transportable resources to a Customizing transport

request.A defined set of transportable resources is added to a Customizing transport request. This request can be released and the content is transported into the corresponding target system.

4.8.2 Set Up a Job to Publish MessagesTo send a message in the prescribed format through a particular channel, you can call the REST methods of the event and notification function.To confirm the channel is active, you can check that the message is received by the user.You set up a job to publish messages.

Procedure1. Schedule the job.

1. Go to the SAP Connect administration screen by entering transaction code SCOT.2. Double-click Send Jobs in the left-hand navigation.3. Select the second icon (looks like a blank document), which displays a dropdown list.4. Select Schedule Job for INT.

2. Select the variant for the job.1. At this stage you can set the name of the job or use the default provided; you can also set the

period for the job - the minimum for this is 1 minute.2. Choose Continue.

NOTEDo not select the Start Immed. checkbox as this creates the job as a once off.

3. Define the background job.Set the job to start immediately by choosing Start condition.

4. Monitor the job.1. To monitor the job, go to transaction SM37.2. Enter the user for which you need to see job results and choose the execute icon.

You can see the jobs that have run for that user and the status of the process. Logs for each of the jobs can also be accessed by giving more details about the steps in the job.


2013-01-30 CUSTOMER 31/48

4.8.3 Enable Virus ScanningYou can scan message attachments for viruses using a Virus Scanner Interface (VSI) profile available on the server.

Procedure1. Go to transaction SM30 and maintain table /POA/D_ENDEFPREF.2. Set the VSCAN parameter in the preference table to TRUE.3. Set the virus scanner profile name in VSI_PROFILE.

Leaving it empty means the default profile registered on the system must be used for scanning. The user is forced to use the values set by the administrator if the system parameters are not marked as editable.

4.8.4 Configure Content Lifecycle ManagementPost-Installation of Content Lifecycle Management1. Set up communication destinations.2. Determine naming policy and global configurations.3. Configure system registry.4. Configure technical settings.5. Optional: Set up user mapping.Setting Up Communication DestinationsFor each system that has to be managed via CLM there should be at least one RFC destination set up.

NOTEIf it cannot be guaranteed that the same users are used throughout the landscape, it is also the point when users in the managed system and in the system hosting CLM can be mapped to each other. This can be done by configuring authentication of the created RFC Destinations (Logon & Security).

For more information about setting up RFC destinations, see SAP Help Portal at http://help.sap.com SAP NetWeaver .

CAUTIONWhen configuring the RFC destination, make sure that you set up authentication (logon and security). Ensure that the user is not asked for RFC connection logon details, as CLM lacks the capability to prompt users for RFC connection logon details during runtime.

Make a note of the destinations created as these are needed later on during the configuration process.Determining Naming Policy and Global Configurations


32/48 CUSTOMER 2013-01-30

To ensure that a globally unique identification is available for content managed by CLM, namespaces have to be configured within CLM. When application content is managed in CLM system; it receives specific identification based on values configured in this step.UseThere are three levels of unique names within CLM: Vendor namespace

NOTEVendor namespace is only necessary for the business process Providing Content. It is not necessary for the business process Consuming Content.

Authoring domains Repository identificationYou define these values in Customizing for Content Lifecycle Management under Define Global Settings and Define Authoring Domains.For more information about the namespace concept within CLM, see SAP Library documentation under Content Lifecycle Management Content Group .Procedure1. Specify CLM repository ID and vendor namespace that is globally unique for this instance of CLM.

NOTETo ensure the uniqueness of the chosen namespace, SAP operates a service that issues unique namespaces for use in SAP Service Marketplace. Vendors are free to use their own namespace identifier that can distinguish their content from others in CLM.RECOMMENDATIONWe recommend using an existing registered vendor namespace with SAP.

2. Identify at least one authoring domain that is going to be used with this instance of CLM.These settings are unique per CLM instance per CLM ABAP system and client combination. Therefore, in a landscape where CLM is installed in one system, but is used in multiple ABAP clients, each ABAP client holds client-specific values.

EXAMPLEYou can have Netweaver ABAP server D1X:1. Development client 100 has values: Vendor Namespace = XXX, Repository ID = DEV100,

Authoring Domain = O&G_USA2. Test client 200 has values: Vendor Namespace = XXX, Repository ID = QUA100, Authoring

Domain = O&G_USAYou can define the applications that communicate with CLM in Customizing for Content Lifecycle Management under Define Applications.Configuring System Registry


2013-01-30 CUSTOMER 33/48

The CLM system registry is used for maintaining a list of the managed systems along with their connectivity information. CLM must have an entry in the system registry for all the systems that are to be managed by CLM.You can configure new managed systems in Customizing for Content Lifecycle Management under Maintain System Registry (transaction SPRO).For more information, see Maintain System Registry documentation.During maintenance of system registry, you are asked to specify an existing authoring domain and an existing RFC destination whose values were set in above steps.CLM predelivers application-specific API groups containing APIs that are RFC functions modules residing in application system. When you configure system registry, you associate RFC destination to API groups and finally you use the system registry at runtime in your business scenarios for content extraction and deployment.

NOTEAfter settings have been made in Customizing, the transaction /POA/CLM_API_TESTER should be run to test the configured systems, APIs, and function modules before running CLM for actual extraction and deployment. This tool is only intended for developers and it accepts the system registry ID. The returned results display the format, signature, and RFC checks against a particular application system.

You can also maintain the system registry in transaction SE54. Choose Edit View Cluster and enter /POA/VC_CLM_SYS_REG.Configuring Technical Settings for Content Lifecycle ManagementCLM has the following technical settings that can be maintained: Deployment polling count how many times to check the deployment Deployment polling interval (minutes) how often to check the deployment Maximum extract chunk size (KB) Refresh (seconds) how often to refresh the content in the main view Comparison threshold (hours) if a content group you are comparing is older than the defined

threshold, you receive a warning messageTo change these settings, see Customizing for Content Lifecycle Management under Maintain Technical Settings (transaction SPRO).For more information, see the Maintain Technical Settings documentation.Based on the type of information architecture, the following steps must be performed to allow access to the Content Lifecycle Management (CLM) UI:NetWeaver Business ClientIf the NetWeaver Business Client is used as the information architecture, the following configuration steps must be performed:


34/48 CUSTOMER 2013-01-30

CLM delivers a role /POA/CLM_BPC_USER that you can either directly assign to CLM users or copy to any other role.Alternatively, you can configure your own role using transaction PFCG to provide access to the Web Dynpro application.1. In the Menu tab, create a new folder under Role Menu and provide a suitable name.2. Insert a Web Dynpro application: /POA/WD_CLM.3. Provide the following parameters: Parameter name = WDCONFIGURATIONID and parameter

value = /POA/WD_CLM_BPC.4. You can assign the authorizations for the authorization object /POA/CLMAC.

For more information about this authorization object, see the Security Guide.5. Assign the role to the required users.Users who have been assigned the appropriate role can access CLM. You can also use transaction NWBC to see the assigned roles in the NetWeaver Business Client.Standalone ABAP Web Dynpro URLYou can access the web URL pointing to the CLM Web Dynpro application /POA/WD_CLM with the configuration ID /POA/WD_CLM_BPC.You can retrieve this URL by running the Web Dynpro application, for example, through transaction SE80 in the SAP GUI.

RECOMMENDATIONWe recommend accessing CLM using the NetWeaver Business Client.

4.8.5 Enable BWA for a ModelIf you want to use the functionalities of Business Warehouse Analytics (BWA), you can enable it for a BPC model. For more information, see http://help.sap.com/saphelp_nw73/helpdata/en/4a/496262f3ec1c47e10000000a42189c/frameset.htm


2013-01-30 CUSTOMER 35/48

5 Tips

5.1 SMS for Planning and Consolidation Package DeliveryUse these instructions for SMS usage in the Planning and Consolidation installer and for patch publication.

PrerequisitesClient and SMS server are installed and configured.

Procedure1. Log on to the server on which SMS is installed.2. Create a folder for placing published packages.3. Create the folders SMSPACK and AP001 on D:\, where SMSPACK is the parent folder for publishing

packages with subfolders such as AP001, 002, and so on, for each package.4. Place the Planning and Consolidation setup files in D:\SMSPACK\AP001\.5. To publish the Planning and Consolidation setup files or to advertise them to the clients, create a

package for the setup file as follows:1. Open the SMS Admin console from Programs Systems Management Server SMS Administrator

console .2. Right-click on the packages folder, then select New Package .3. Enter the required data.4. On the General tab, click the data source and choose This package contains source files.5. Set the directory of the source files to the local drive D:\, then choose Apply/OK.

6. To run this package, create a program as follows:1. Expand the packages folder in the Admin console, right-click the programs, and select New

Program .2. Enter the Program Properties as required.

NOTEIf you have command line options for the setup, you can browse to choose the package and add the command line parameters next to it. If not, you can simply choose the setup file.You can use the After Running dropdown to configure the action once the package is installed.

5 Tips5.1 SMS for Planning and Consolidation Package Delivery

2013-01-30 CUSTOMER 37/48

On the Environment tab, you can choose how the package should run and whether the user must be logged in or not and with what rights. If the user does not have administrator rights, select Run with administrative rights and Allow users to interact with this program.

3. Choose Apply to save the settings, then choose OK.7. To notify client machines that a package is available, create an advertisement as follows:

1. Right-click on the Advertisements folder and choose New Advertisement .2. Provide a name and appropriate details, and choose the package and the program.3. Choose the systems to which the package is available.4. Indicate whether to advertise the package at a specific time or set a mandatory assignment by

choosing the yellow star button.The checkbox allows users to run the package installation independently, whenever convenient, from Control Panel or Add/Remove Programs.

5. On the Advanced tab, set the location from which you want to run the program, then choose Apply and OK.

8. Create a distribution point for this program as follows:1. Expand the packages folder in the Admin Console, expand the package you created, and right-

click the distribution point folder.2. Choose New Distribution point , and set the distribution point.3. Update this with the package you created by right-clicking on the distribution points folder,

selecting all tasks, and updating the distribution points.4. Choose Yes at the confirmation message.

9. Verify that the package is available on the client side.


38/48 CUSTOMER 2013-01-30

6 Troubleshooting

Client Installation IssuesBy default, the installation program runs a diagnostic program. Here are some potential error messages that display during the client installation: Visual Basic 6.0 SP5: Run-Time Redistribution Pack not installed

Download vbrun60sp5.exe, then run it. Visual C++ 6.0 Run-Time not installed

Download vc6redistsetup_enu.exe, then run it. OSoftDMClientTools.DMTools found in registry. Please refer to system administrator

before installationOpen the registry table, find the key OSoftDMClientTools.DMTool under HKEY_LOCAL_MACHINE\\SOFTWARE\\Classes and delete this key.

.NET Framework x.x is not installedInstall the relevant version of .NET Framework before continuing.

Other Potential IssuesThe ABAP service users can be locked as a result of the install. Check and unlock any locked ABAP service users after performing the install. To do so, perform transaction SU01, enter the service user ID (for example, BPC_SERVICE), and then press Ctrl+F5.

6 Troubleshooting

2013-01-30 CUSTOMER 39/48

7 Connecting to Solution Manager Diagnostics

The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems. This procedure provides the steps required to connect Planning and Consolidation to Solution Manager Diagnostics.

Procedure1. Install the Diagnostics Agent according to SAP Note 1234387 on all servers where Interface for the

Web and Application Servers are installed.NOTEInstallation files for Diagnostics Agent are available on the SAP Service Marketplace by navigating to Support Packages and Patches Entry by Application Group SAP Technology Components

SAP SOLUTION MANAGER SAP SOLUTION MANAGER 7.0 EHP 1 Entry by ComponentAgents for managed systems DIAGNOSTICS AGENT 7.11 .

Download an installation file based on one of the following system landscapes: Windows Server on IA32 32bit Windows Server on IA64 64bit Windows Server on x64 64bit

2. Set up your system for Diagnostics.Refer to End-to-End Root Cause Analysis System Landscape Setup Guide, which is available on Service Marketplace at https://service.sap.com/~sapidb/011000358700000074392009E, and follow the chapters that apply to Planning and Consolidation.

7 Connecting to Solution Manager Diagnostics

2013-01-30 CUSTOMER 41/48

8 Security Considerations and Connection Issues

Your client/server configuration is unique as it relates to security, so you may experience connection problems with SSL, proxy servers, or programs and settings that interact with these components. If you are having any issues related to connection, review the following recommendations and troubleshooting tips.

8.1 Checking for Open PortsYou must ensure that all required ports are open for inbound/outbound traffic. By default, Planning and Consolidation requires that Port 80 (used by http) is open.To test whether the required port is open, go to a command prompt and enter Telnet . For example, Telnet 43.118.18.36 80. If the system returns a blank command window, the port is open. If it returns a message stating that it cannot connect, the port is not open.

NOTEYou can use http://www.myserver.org/portsniff.asp to scan for the normal ports. It allows you to manually enter a port number to test.You can change the name of a port.

8.2 Adobe Flash Player IssuesThe Planning and Consolidation Flex Client uses the Adobe Flash player to generate the user interface. A limitation in the Adobe Flash player prevents the installation of the Planning and Consolidation Web server on some ports as the Flex Client cannot perform http calls on these ports.

FeaturesFrom Adobe Flash player 9.0.112.0, a security control blocks commonly reserved ports to prevent malicious activity. If a port number is specified at the end of a URL, such as http://www.adobe.com:80, the system checks the port against a list of commonly reserved ports. If the port is on this list, the network request is rejected and a security error event is generated.The Adobe Web site (http://www.adobe.com) has a Knowledge Base page, entitled URL requests to certain ports throw security errors in Adobe Flash Player 9.0.115.0 and higher, that lists the ports that Adobe Flash player considers to be reserved. You should not use the ports listed in this Knowledge Base page.

8 Security Considerations and Connection Issues8.1 Checking for Open Ports

2013-01-30 CUSTOMER 43/48

8.3 Proxy Server and Firewall IssuesFor questions about specific proxy servers, contact SAP Support.

General Considerations If you connect to the Internet through a firewall or proxy server, you need to add the IP address

of the Planning and Consolidation server as an exception. You can do this at the client level ( Internet Explorer Tools Internet Options Connections LAN Settings ) or at the server level.

Enabling content filtering on the proxy server or firewall may cause connection problems. If external users are having trouble connecting to the server, make sure the proxy server connects

using a fully qualified domain name. Fully qualified domain names typically resolve both internal and external IP addresses.

Each secure Planning and Consolidation server name must be identified on the proxy server. Proxy servers may or may not require authentication, which could conflict with Planning and

Consolidation authentication. Do not use authentication on the proxy server. The system synchronizes the user name and password on the remote server with the local user name and password.

NOTEFor more information about setting up an ISA proxy server, contact SAP Support to request a copy of Setting up ISA Proxy Server White Paper.

Internet Explorer Settings IssuesInternet Explorer settings must be set correctly to prevent errors and problems when you attempt to access the Planning and Consolidation server using the Connection Wizard. Change the settings by taking the following steps:1. From Internet Explorer, select Tools Internet Options .2. From the General tab, delete all temporary Internet files, cookies, and history.3. From the Security tab, set security to Default level for Internet and local intranet.4. From the Connections tab, choose the LAN settings button. If you select Use a proxy server for your LAN,

insert the IP address or fully qualified server name of the Planning and Consolidation server as an exception by choosing Advanced.

5. From the Advanced tab, choose Restore Defaults, Apply, then OK.

Microsoft Windows IssuesIf you have Windows XP SP2, disable the Microsoft Windows firewall.

Norton AntiVirus IssuesHaving Script Blocking enabled in Norton AntiVirus can cause some display and download issues.

8 Security Considerations and Connection Issues8.3 Proxy Server and Firewall Issues

44/48 CUSTOMER 2013-01-30

9 Terminal Services or Citrix Server

This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Services or Citrix Server deployment.

9.1 Terminal Services Home DirectoriesWe recommend using Terminal Server home directories rather than using the users profile directory. The profile directory downloads a minimal amount of information about the dimensions of the environment you are logging on to and may be as large as 2 MB per user. The profile directory is on the system drive and has limited space. By specifying a home directory, you can manage the disk space required.If you have a farm of servers, put the profile information in a common home directory rather than on each individual server, so that all users consistently use the current download of dimensions.

9.2 System RequirementsThe Citrix server should be one of the following systems: XenApp 5 Enterprise XenApp 5 PlatinumThe XenApp program must be installed on a Windows 2008 server.Only client virtualization is supported with XenApp 5 Enterprise and Platinum. For details, SAP Notes 1098847 and 1409608.The Terminal Services or Citrix Server computer requires the same client software as would be installed on the client server (see Client Prerequisites [page 14]).

9.3 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

PrerequisitesThe server installation files have been downloaded from SAP Service Marketplace and installed.

ProcedureThe following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or Citrix Server deployment:

9 Terminal Services or Citrix Server9.1 Terminal Services Home Directories

2013-01-30 CUSTOMER 45/48

1. Make sure the Terminal Services or Citrix Server machine has the system requirements installed.2. Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to

install on that server.3. At a command prompt, enter Change user/install.4. Open a browser and connect to the URL http:///sap/bpc/web.5. Log on to the Web site with the Planning and Consolidation administrative account.6. Click Install EPM Add-in for Microsoft Office to install the EPM Add-in.7. Go back to the command prompt and enter Change user/execute or Restart the server.8. For the Citrix Server, you must publish each client application. Take the following steps:

To publish the Planning and Consolidation Launch page: Iexplore.exe http(s)://-NetBIOS or FQDN/sap/bpc/web

To publish the EPM Add-in client: C:\Program Files\Microsoft Office\Office\Excel.exe

9.4 Creating a Shortcut to the Launch PageProcedureIf you use published desktops instead of published applications, the Planning and Consolidation desktop file (which is installed on the current users desktop) must be moved to the All Users/Desktop folder.

9 Terminal Services or Citrix Server9.4 Creating a Shortcut to the Launch Page

46/48 CUSTOMER 2013-01-30

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

Copyright 2013 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.

SAP BusinessObjects Planning and Consolidation 10.0Table of Contents1 Introduction1.1 SAP Notes for the Installation1.2 Naming Conventions

2 Planning the Installation2.1 Planning the Server Installation2.1.1 Installation Scenarios2.1.2 Server Hardware Requirements2.1.3 Server Prerequisites2.1.4 Installing the Server Prerequisites2.1.5 Acquiring the Planning and Consolidation Installation Components and Support Packages

2.2 Client Prerequisites2.3 Planning for Event & Notification2.4 Optional: Planning for Content Lifecycle Management

3 Installing Planning and Consolidation3.1 Installing and Configuring SAP NetWeaver3.2 Installing the Add-In POASBC ABAP Component3.3 Installing the Server Components3.4 Installing the EPM Add-In for Microsoft Office3.5 Installing an ABAP Server Component Support Package3.6 Installing the SAP HANA Component for Planning and Consolidation3.7 Installing Planning and Consolidation during the update of NetWeaver

4 Post-Installation4.1 Activate Your SAP Technical Business Content4.2 Generate Required Authorization Profiles and Perform User Mass Comparison4.3 Configure the ABAP Server Component4.4 Ensure ICF Services are Activated4.5 Log On4.6 HTTPS Settings ICF Procedure4.7 Configure Single Sign-On4.8 Post-Installation: Optional Configuration Steps4.8.1 Update the Persistence Service4.8.2 Set Up a Job to Publish Messages4.8.3 Enable Virus Scanning4.8.4 Configure Content Lifecycle Management4.8.5 Enable BWA for a Model


6 Troubleshooting7 Connecting to Solution Manager Diagnostics8 Security Considerations and Connection Issues8.1 Checking for Open Ports8.2 Adobe Flash Player Issues8.3 Proxy Server and Firewall Issues

9 Terminal Services or Citrix Server9.1 Terminal Services Home Directories9.2 System Requirements9.3 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment9.4 Creating a Shortcut to the Launch Page

Copyright and trademarks

installation guide bpc 10

Documents