Installation Guide for SAP Business Planning and

Installation Guide CUSTOMER

2017-08-25

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaver

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 SAP Notes for the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Planning the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 Planning the Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Installation Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Server Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Server Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Installing the Server Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Acquiring the Planning and Consolidation Installation Components and Support Packages. . . . . . . . 10

2.3 Client Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.4 Planning for Event & Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.5 Optional: Planning for Content Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Installing Business Planning and Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Installing and Configuring SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 Installing the Add-On POASBC ABAP Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.4 Installing the Server Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.5 Installing the EPM Add-In for Microsoft Office. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.6 Installing an ABAP Server Component Support Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.7 Installing the SAP HANA Component for Business Planning and Consolidation. . . . . . . . . . . . . . . . . . . 173.8 Installing Business Planning and Consolidation during the update of NetWeaver. . . . . . . . . . . . . . . . . . 18

4 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.2 Activate Your SAP Business Warehouse Technical Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.3 Generate Required Authorization Profiles and Perform User Mass Comparison. . . . . . . . . . . . . . . . . . 204.4 Configure the ABAP Server Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.5 Ensure ICF Services are Active. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.6 Log On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.7 HTTPS Settings ICF Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.8 Configure Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.9 Post-Installation: Optional Configuration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2 C U S T O M E R


Content

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Update the Persistence Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Set Up a Job to Publish Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Enable Virus Scanning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Configure Content Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Enable BWA for a Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

5 Tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.1 SMS for Planning and Consolidation Package Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

6 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

7 Connecting to Solution Manager Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

8 Security Considerations and Connection Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398.2 Checking for Open Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398.3 Adobe Flash Player Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398.4 Proxy Server and Firewall Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

9 Virtualization Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverContent C U S T O M E R 3

1 Introduction

1.1 Introduction

The SAP Business 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.0

The 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 Management

Content 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 & Notification

The 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.

Context

Context 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.

4 C U S T O M E R


Introduction

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/1098847


1.2 SAP Notes for the Installation

Read 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 and the issues resolved in the release. Make sure that you have the up-to-date version of each SAP Note, which you can find by clicking on the SAP Note numbers below or by searching on SAP Service Marketplace at http://support.sap.com/notes .

Table 1:

SAP Note Number Title

1586088 Documentation Addendum

* Contains information that does not yet appear in the application help

2062798 Support Package 16 Central Note
















SAP Notes for POASBC Add-On Installation

You 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.

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverIntroduction C U S T O M E R 5

http://help.sap.com/disclaimer?site=http://support.sap.com/notes


















Table 2:

SAP Note Number Title Description

1511393 Release strategy for the ABAP add-on POASBC

This 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_730

This note contains information about upgrading with POASBC.

Other Important Notes

Table 3:


1575575 Add default formula when installing EnvironmentShell

1578760 MDX: Error _MEMBER_GET_FULL_3 for external hierarchies

1586265 New Master Data Deletion - Redundant table locks removed

1.3 Naming Conventions

In this document, the following naming conventions apply.

Table 4:

Variable Description

<PC_server:port> Server name or IP address and port number of the Planning and Consolidation application location.

<drive> The drive where Planning and Consolidation is installed.

The default for this is C:\PC_NW.

6 C U S T O M E R


Introduction







2 Planning the Installation

2.1 Introduction

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

2.2 Planning the Server Installation

2.2.1 Introduction

Before 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 8].2. Verify that you have the required prerequisites installed on the server. If not, install them. See Server

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

the Planning and Consolidation and ABAP Server Components [page 10].

2.2.2 Installation Scenarios

You 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 18].

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)● SAP NetWeaver AS ABAP 7.4

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverPlanning the Installation C U S T O M E R 7

2.2.3 Server Hardware Requirements

Before 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.2.4 Server Prerequisites

You must install the following requirements on the ABAP application server before installing the Business 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-on POASBC ABAP component – version POA_SBC_100_730

For 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


8 C U S T O M E R


Planning the Installation

http://help.sap.com/disclaimer?site=https://service.sap.com/installnw73

http://help.sap.com/disclaimer?site=https://service.sap.com/installnw73

For SAP NetWeaver 7.4

● SAP NetWeaver 7.4○ Application Server ABAP – PI_BASIS 7.40○ Application Server ABAP – SAP ABA 7.40○ Application Server ABAP – SAP BASIS 7.40○ Application Server ABAP – SAP BW 7.40○ Kernel (64-bit) and Unicode only


SAP HANA

If you choose to use Business Planning and Consolidation with SAP HANA component HANABPC, you must run SAP NetWeaver 7.3 SP06 or higher including 7.4 SPX with HANA Revision 26 or higher.

HANA revision 96 or higher is required to use nodes of multiple hierarchies in the same report or input schedule.

More Information

A list of the supported operating systems and database systems is also available in the Product Availability Matrix on SAP Service Marketplace at http://support.sap.com/pam . Search on Planning and Consolidation.

For information on installing the prerequisite software, see Installing the Server Prerequisites [page 9].

2.2.5 Installing the Server Prerequisites

For 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:

Table 5:


93042 Problems with SAPFTP

1352953 DB6: Runtime error SYNTAX_ERROR in DBA Cockpit

1537619 Changes to function group SROLETOOLSBPC


http://help.sap.com/disclaimer?site=http://support.sap.com/pam

http://help.sap.com/disclaimer?site=https://service.sap.com/instguidesNW73


1545834 MS Access 97: Incorrect version of Wdpsam97.exe

1553052 OLE DB for OLAP: Transient queries in cube schema rowset

1558149 OLE DB for OLAP: Error handling for cube rowset

1561043 RSD1: Error adding navigation attribute for master data

1560836 Class CL_ABAP_ZIP, Handle Leading 0x00000000 in ZIPs

2.2.6 Acquiring the Planning and Consolidation Installation Components and Support Packages

You 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://support.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.

○ For SAP NetWeaver 7.4 the download object number is: 51043139 (Title: SBOP PC 10.0 FOR SAP NW 731).

NoteTo use SAP NetWeaver 7.4, the minimum required support package for Planning and Consolidation 10.0 is SP10.

2. To download support packages:Go to http://support.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 Entry by Component .For SAP NetWeaver 7.3, download the following:

○ Bus. Plan.and Cons. ABAP POA SBC 100_730 Support Packages Downloads <required support package> .

○ Bus. Plan.and Cons. ABAP SAP EPM BPC ABAP 10.0 Support Packages Downloads <required support package> .

10 C U S T O M E R



http://help.sap.com/disclaimer?site=http://support.sap.com/swdc

http://help.sap.com/disclaimer?site=http://support.sap.com/swdc

For SAP NetWeaver 7.3 Including Enhancement package 1 or for SAP NetWeaver 7.4, download the following:

○ Bus. Plan.and Cons. ABAP 7.31 POA SBC 100_730 Support Packages Downloads <required support package> .

○ Bus. Plan.and Cons. ABAP 7.31 SAP EPM BPC ABAP 10.0 Support Packages Downloads<required support package> .

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.

Note

For information about using the SAP Download Manager, go to http://service.sap.com/support and choose Software Downloads Download Manager .

2.3 Client Prerequisites

Planning 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://support.sap.com/pam . Search on Planning and Consolidation.

● Microsoft Internet Explorer 7.0 or 8.0 32–bitAs of support package 04: Microsoft Internet Explorer 9.0 32–bitAs of support package 09: Microsoft Internet Explorer 8.0 64–bit and 9.0 64–bitAs of support package 10: Microsoft Internet Explorer 10.0As of support package 16: Microsoft Internet Explorer 11.0 in compatibility view or enterprise modeAs of support package 18: Microsoft Internet Explorer 11.0

● As of support package 07: Mozilla Firefox 8.0As of support package 08: Mozilla Firefox 9.0 to 14.0As of support package 08: Mozilla Firefox 15.0 to 19.0To 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 09: Microsoft Office 2010 64–bitAs of support package 10: Microsoft Office 2013

○ Microsoft .NET Framework 3.5 SP1○ Microsoft Web Services Enhancement 3.0 (WSE 3.0)○ Microsoft XML Parser 6.0 SP1

NoteFor more information about the installation prerequisites for the EPM Add-in, see the EPM Add-in for Microsoft Office Installation Guide.


http://help.sap.com/disclaimer?site=http://service.sap.com/support

http://help.sap.com/disclaimer?site=http://support.sap.com/pam

2.4 Planning for Event & Notification

Use

The following tables hold the default configuration and can be configured through transaction SM30:

● /POA/D_ENDEFPREF: Master User Preferences for Default Values

Sample contents of the preference table are listed here:

Table 6:

Item Description Type Communication 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.5 Optional: Planning for Content Lifecycle Management

Use

NoteConfiguring 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 Management

12 C U S T O M E R



For 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 <Release Version> 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 Systems

It 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, 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 Model

You 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 Activities

Content 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.


http://help.sap.com/disclaimer?site=http://service.sap.com/securityguide

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

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.

14 C U S T O M E R



3 Installing Business Planning and Consolidation

3.1 Introduction

The main steps for installing Business Planning and Consolidation are the following:

1. Install and configure SAP NetWeaver – see Installing and Configuring SAP NetWeaver [page 15].2. Install the add-on POASBC ABAP component – see Installing the Add-On POASBC ABAP Component [page

16].3. Install Business Planning and Consolidation and the ABAP add-on server component – see Installing the

Server Components [page 16].4. Install the EPM Add-in for Microsoft Office – see Installing the EPM Add-In for Microsoft Office [page 17].

After the initial installation of Business Planning and Consolidation, see Installing an ABAP Server Component Support Package [page 17] for details of installing support packages.

If you choose to use Business Planning and Consolidation with SAP HANA, download and install the add-in software component HANABPC. See Installing the SAP HANA Component for Business Planning and Consolidation [page 17].

NoteYou can also install Business 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 Business Planning and Consolidation during the update of NetWeaver [page 18].

3.2 Installing and Configuring SAP NetWeaver

Use

Based on your configuration, you can install Business 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.

Procedure

If 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 .

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverInstalling Business Planning and Consolidation C U S T O M E R 15

http://help.sap.com/disclaimer?site=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.

Business Planning and Consolidation requires that you are able to do at least the following with SAP NetWeaver Business Warehouse:

● Create and activate an InfoObject of type Characteristic● Maintain master data and the hierarchy for Characteristic● Create and activate the InfoCube● Transport InfoObjects and InfoCubes

To perform the actions listed above, you must first activate SAP Business Warehouse Technical Content, about which you can find more information in Activate Your SAP Technical Business Content [page 19]. You must also run transaction RSTPRFC to set up a user and an RFC destination for Business Warehouse after import processing

3.3 Installing the Add-On POASBC ABAP Component

Use

Check 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.4 Installing the Server Components

Prerequisites

● You have downloaded the server components from SAP Service Marketplace. See Acquiring the Planning and Consolidation and ABAP Server Components [page 10].

● 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 Business 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.

Procedure

To install the server components, use the transaction SAINT.

16 C U S T O M E R


Installing Business Planning and Consolidation

http://help.sap.com/disclaimer?site=http://help.sap.com/saphelp_46c/helpdata/en/2e/d9530294f911d283d40000e829fbbd/frameset.htm

http://help.sap.com/disclaimer?site=http://help.sap.com/saphelp_46c/helpdata/en/2e/d9530294f911d283d40000e829fbbd/frameset.htm

For information about using SAINT, see http://help.sap.com/saphelp_nw73/helpdata/EN/49/3e896728ab2222e10000000a42189d/frameset.htm .

3.5 Installing the EPM Add-In for Microsoft Office

SAP EPM Solutions, add-in for Microsoft Office provides business users the capability to analyze data from within supported SAP 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.6 Installing an ABAP Server Component Support Package

Use

You can download and import support packages to update the ABAP add-on server components.

Procedure

Download the support packages from SAP Service Marketplace, and install them using transaction SPAM. For details, refer to SAP Notes 1582356 and 1694454 .

3.7 Installing the SAP HANA Component for Business Planning and Consolidation

Use

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

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverInstalling Business Planning and Consolidation C U S T O M E R 17

http://help.sap.com/disclaimer?site=http://help.sap.com/saphelp_nw73/helpdata/EN/49/3e896728ab2222e10000000a42189d/frameset.htm

http://help.sap.com/disclaimer?site=http://help.sap.com/saphelp_nw73/helpdata/EN/49/3e896728ab2222e10000000a42189d/frameset.htm



Prerequisites

You have applied the following SAP Notes:

● 1680983● 1658749● 1566845● 1654731

Reports in Business Planning and Consolidation can be accelerated using the SAP HANA Component for Business 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 Business Planning and Consolidation is in use, such as Periodic, QTD, or YTD.● Only one Business Planning and Consolidation cube exists under its corresponding SAP Business Warehouse

multi-provider.

Procedure

1. Download the SAP HANA Component for Business 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.5. Turn on the shared memory hierarchy. See SAP Note 1657612 for more information.

3.8 Installing Business 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 Business 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, 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 <version> that is available on the SAP Service Marketplace at: http://service.sap.com/sltoolset

Software Logistics Toolset 1.0 SUM .

18 C U S T O M E R


Installing Business Planning and Consolidation







http://help.sap.com/disclaimer?site=http://service.sap.com/sltoolset

4 Post-Installation

4.1 Introduction

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 19].

2. Generate the required authorization profiles and perform a User Mass Comparison – see Generate Required Authorization Profiles and Perform User Mass Comparison [page 20].

3. Configure the Planning and Consolidation ABAP add-on – see Configure the ABAP Server Component [page 20].

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

5. Log on – see Log On [page 25].6. Enable HTTPS for the ABAP server – see HTTPS Settings ICF Procedure [page 25].7. Configure Single Sign-on — see Configure Single Sign-on [page 26]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 26]:

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

31].

4.2 Activate Your SAP Business Warehouse Technical Content

Use

This is part of the Business Warehouse setup. If it has already been completed, skip this section; otherwise complete it now.

Procedure

1. Go to transaction RSA1 and select BI Content.

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverPost-Installation C U S T O M E R 19

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.3 Generate Required Authorization Profiles and Perform User Mass Comparison

1. 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.4 Configure the ABAP Server Component

Use

You 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 Business Planning and Consolidation transport framework. This program also supports the installation of many other Business Planning and Consolidation objects that are required 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.

20 C U S T O M E R


Post-Installation

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 Business Planning and Consolidation UJ* metadata tables. If you use the Clean option on EnvironmentShell, refer to SAP Note 1615644 .

Prerequisites

The ABAP server component has been installed.

You have completed your SAP Business Warehouse setup especially the installation of Business Warehouse Technical Content, about which you can find more information in Activate Your SAP Business Warehouse Technical Content [page 19]. You can install Business Warehouse Technical Content with transaction RSTCO_ADMIN or RSA1.

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 .

Procedure

These steps are required for proper functioning of the Planning and Consolidation software.

Logistic System for Planning and Consolidation

Verify 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 Notes

It is important that you refer to the following SAP Notes and apply the indicated corrections:

Table 7:


1572695 MDX: System-wide call of old parser implementation

Make Namespaces and Software Components Changeable





For 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:○ HOME○ LOCAL

Use the following procedure to set the components to Modifiable:

1. Enter transaction SE06 and choose System Change Option.2. Set the namespaces and software components to Modifiable.

However, when you do not want any changes in a production environment except those made from importing transport requests, you can set System Change Option to Unmodifiable. This automatically sets all namespaces and components to Unmodifiable as well.

Import Client-Dependent Objects

Using 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 the topic “Authorization Profile for Background Users” in the SAP NetWeaver 7.3 > SAP NW Business Warehouse > Data Warehouse Management application help at http://help.sap.com/saphelp_nw73/helpdata/en/4a/27b47181661d10e10000000a42189b/content.htm .

If the transport fails, see SAP Note 1329651 for information.

Run Connection Test on RFC Destination MDX PARSER

Enter transaction SM59 and run a connection test on the RFC destination MDX PARSER.

Note

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

Assign Authorization to Installation User

Assign 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 User

The service user that you create is used by Business Planning and Consolidation to complete tasks that require different authorizations than you would assign to a normal user.

1. Create a service user as follows:1. Enter transaction SU01.

22 C U S T O M E R


Post-Installation

http://help.sap.com/disclaimer?site=http://help.sap.com/saphelp_nw73/helpdata/en/4a/27b47181661d10e10000000a42189b/content.htm

http://help.sap.com/disclaimer?site=http://help.sap.com/saphelp_nw73/helpdata/en/4a/27b47181661d10e10000000a42189b/content.htm



2. Create a user with the User Type dialog. For example, you may name the user BPC_SERVICE.3. Assign the profile SAP_ALL to this user.

2. Make the following adjustment:1. Log on to the system with this service user.2. Start transaction PFCG to display a role such as SAP_BPC_SERVICE.

3. Navigate to Utilities Settings and switch on the option Automatic User Master Adjustment when Saving Role.

4. Log off this service user from the system.3. 3. Alter the user as follows:

1. Use transaction SU01 to change the user type of the service user to System.2. Remove all of the profiles and roles of this user.3. Assign the role SAP_BPC_SERVICE or a role that is exactly the same as SAP_BPC_SERVICE to it.

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 Assign a Business Planning and Consolidation RFC Destination

1. Enter transaction SM59. Create an RFC destination to point to the client on which Business Planning and Consolidation is installed and run. In the Logon & Security tab, enter the service user created above with the correct password.

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 EnvironmentShell

1. 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 .



Assign Authorization for After-Import Processing

Business Planning and Consolidation after-import processing uses the same RFC destination and user as BW after-import processing. Therefore, use transaction RSTPRFC to find out the user that has already been created, and assign role SAP_BPC_SERVICE to it.

Also, create a role with authorization object /POA/A_BPT and value for fields as shown below:

● /POA/ACDTP: *● /POA/AUTHT: X● /POA/CNTTP: *● /POA/PSACT: *● /POA/PSAPP: *● /POA/RESTP: *● /POA/SUBNS: *

Assign this role to the user.

4.5 Ensure ICF Services are Active

Prerequisites

POASBC

The software component, POASBC has been installed in your ABAP system.

Procedure

Use transaction SICF to verify that the following services have been activated:

For Business Planning and Consolidation

1. Verify that all services under /sap/EPM_BPC are active.2. Verify that all services under /sap/poa are active.3. Verify that all services under /sap/public/bc are active.

For the EPM Connector

Verify that the services under /sap/bw/xml/soap/xmla/ are active.

24 C U S T O M E R


Post-Installation

4.6 Log On

Use

1. Log on with your user on the ABAP system.Pattern: http://<host>:<port>/sap/bpc/webFor information about setting up users and assigning authorizations, see the Security guide.

2. Verify the HTTP port configured for your ABAP system using transaction SMICM.

4.7 HTTPS Settings ICF Procedure

Procedure

1. Ensure that https is enabled for ABAP server and that 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 https port is configured, you can view the port for https.

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

3. Go to SICF transaction. Choose SERVICE for 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 icon or press CTRL + F1.4. Select System Logon radio button.5. Choose Configuration.6. Select Define Service-Specific Settings radio button.7. Choose Switch to HTTPS from Protocol dropdown menu.8. Under SAP Implementation, choose any screen from the dropdown menu for SAP Theme.9. Execute steps b) to h) for each of the FCP services - core, container, fetcher and logger.


4.8 Configure Single Sign-On

You 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.

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.9 Post-Installation: Optional Configuration Steps

4.9.1 Introduction

The steps listed below are optional.

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

31].5. Enable BWA for a Model — see Enable BWA for a Model [page 34]

4.9.2 Update the Persistence Service

Use

Transportable 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.

26 C U S T O M E R


Post-Installation






Procedure

1. 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.

Table 8:

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.

28 C U S T O M E R


Post-Installation


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.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.9.3 Set Up a Job to Publish Messages

Use

To 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.

Procedure

1. 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.

4.9.4 Enable Virus Scanning

Use

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

30 C U S T O M E R


Post-Installation

Procedure

1. 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.9.5 Configure Content Lifecycle Management

Use

Post-Installation of Content Lifecycle Management

1. 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 Destinations

For 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

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.

Use


http://help.sap.com/disclaimer?site=http://help.sap.com

There 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 identification

You 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 .

Procedure

1. 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_USA

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

You can define the applications that communicate with CLM in Customizing for Content Lifecycle Management under Define Applications.

Configuring System Registry

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).

32 C U S T O M E R


Post-Installation

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 Management

CLM 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 message

To 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 Client

If the NetWeaver Business Client is used as the information architecture, the following configuration steps must be performed:

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 URL

You 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.9.6 Enable BWA for a Model

If 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

34 C U S T O M E R


Post-Installation

http://help.sap.com/disclaimer?site=http://help.sap.com/saphelp_nw73/helpdata/en/4a/496262f3ec1c47e10000000a42189c/frameset.htm

http://help.sap.com/disclaimer?site=http://help.sap.com/saphelp_nw73/helpdata/en/4a/496262f3ec1c47e10000000a42189c/frameset.htm

5 Tips

5.1 SMS for Planning and Consolidation Package Delivery

Use

Use these instructions for SMS usage in the Planning and Consolidation installer and for patch publication.

Prerequisites

Client and SMS server are installed and configured.

Procedure

1. 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 NewProgram .

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.

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverTips C U S T O M E R 35

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.

36 C U S T O M E R


Tips

6 Troubleshooting

Client Installation Issues

By 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 installation”Open the registry table, find the key OSoftDMClientTools.DMTool under HKEY_LOCAL_MACHINE\\SOFTWARE\\Classes and delete this key.

● “.NET Framework x.x is not installed”Install the relevant version of .NET Framework before continuing.

Other Potential Issues

The 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.

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverTroubleshooting C U S T O M E R 37

7 Connecting to Solution Manager Diagnostics

Use

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.

Procedure

1. 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 Component Agents 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.

38 C U S T O M E R


Connecting to Solution Manager Diagnostics


http://help.sap.com/disclaimer?site=https://service.sap.com/~sapidb/011000358700000074392009E

8 Security Considerations and Connection Issues

8.1 Introduction

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.2 Checking for Open Ports

You 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 <serveripaddress> . 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.3 Adobe Flash Player Issues

Use

The 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.

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverSecurity Considerations and Connection Issues C U S T O M E R 39

Features

From 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 article KB402882 entitled URL requests to certain ports throw security errors in Adobe Flash Player 9.0.115.0 and higher at https://helpx.adobe.com/flash/kb/url-requests-certain-ports-throw.html 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.4 Proxy Server and Firewall Issues

For 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 ExplorerTools 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.

Internet Explorer Settings Issues

Internet 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.

40 C U S T O M E R


Security Considerations and Connection Issues

http://help.sap.com/disclaimer?site=http://www.adobe.com

http://help.sap.com/disclaimer?site=https://helpx.adobe.com/flash/kb/url-requests-certain-ports-throw.html

http://help.sap.com/disclaimer?site=https://helpx.adobe.com/flash/kb/url-requests-certain-ports-throw.html

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 Issues

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

Norton AntiVirus Issues

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

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverSecurity Considerations and Connection Issues C U S T O M E R 41

9 Virtualization Support

BPC supports only virtualization solutions that behave in a fully transparent manner to the application. If the virtualization solution does not behave fully transparently, the relevant technology partner must provide support for the virtualization solution to become transparent. If a support issue cannot be solved by the technology partner, the SAP application needs to be migrated to a non-virtual environment.

For the latest information about this topic, refer to SAP Note 1409608 .

42 C U S T O M E R


Virtualization Support


Important Disclaimers and Legal Information

Coding SamplesAny 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 to 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, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).

Installation Guide for SAP Business Planning and Consolidation 10.0 version for SAP NetWeaverImportant Disclaimers and Legal Information C U S T O M E R 43

http://help.sap.com/disclaimer/

go.sap.com/registration/contact.html

© 2017 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Material Number: 725

*725*

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Documents

Installation Guide for SAP Business Planning and