SAP BusinessObjects Financial Consolidation … · 4 Preparing to install SAP Financial...

Installation Guide CUSTOMER

SAP BusinessObjects Financial ConsolidationDocument Version: 10.1 Support Package 04 – 2017-02-24

SAP BusinessObjects Financial Consolidation Installation Guide

Content

1 What's new in version 10.1 of SAP Financial Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Contents of the version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Summary of Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.1 Installing SAP Financial Consolidation Core Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.2 Installing SAP Financial Consolidation Cube Designer Components for SAP HANA Modeling Views

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.3 Installing SAP Financial Consolidation Cube Designer Components for Microsoft SSAS. . . . . . . . . . . . . 103.4 Installing SAP Financial Consolidation Cube Designer Components for Star Schema. . . . . . . . . . . . . . . 113.5 Installing SAP Financial Consolidation Cube Designer Components for NetWeaver BW Cubes. . . . . . . . . 11

4 Preparing to install SAP Financial Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.1 External Components Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134.2 Microsoft SQL Server Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Creating the Financial Consolidation Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Installation prerequisites for the SQL Server client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.3 Oracle Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Server Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Client Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.4 SAP HANA Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21SAP HANA Server Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21SAP HANA Client Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.5 Databases prerequisites for Star Schema and Custom Fact Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . 234.6 Web Components Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Prerequisites for Windows Server Web Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.7 Prerequisites for the BusinessObjects Enterprise XI 4.1 platform or the SAP BusinessObjects

Information Platform Services 4.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Installing Information Platform Services 4.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.8 Configuring X.509 certificates in SAP Financial Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5 Installing Financial Consolidation Server Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325.1 Installing the SAP Financial Consolidation Broker Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Deploying the Administration Console Web Site under Windows Server. . . . . . . . . . . . . . . . . . . . . .35Configuring the Web Administration Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.2 Installing the SAP Financial Consolidation Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Installing ActivePDFServer (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Configuring Disclosure Management for HTTPS Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

2 C U S T O M E RSAP BusinessObjects Financial Consolidation Installation Guide

Content

Initializing the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Connecting to SAP Financial Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.3 Installing the SAP Financial Consolidation Web Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Installing the Financial Consolidation Web site Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Deploying the SAP Financial Consolidation Web site under Windows Server. . . . . . . . . . . . . . . . . . .59Deploying the SAP Financial Consolidation Web HTML5 site under Windows Server. . . . . . . . . . . . . 63Activating the SSL Protocol on the User Management Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

5.4 System Landscape Directory Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.5 Installing and configuring the SAP Financial Consolidation Web Services. . . . . . . . . . . . . . . . . . . . . . . 69

Deploying the SAP Financial Consolidation Web Services under Windows Server. . . . . . . . . . . . . . . 69Encrypting the settings of the web.config file (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Deleting the SAP Financial Consolidation Web Services website. . . . . . . . . . . . . . . . . . . . . . . . . . . 71Testing the SAP Financial Consolidation Web Services deployment. . . . . . . . . . . . . . . . . . . . . . . . .72

6 Installing the SAP Financial Consolidation Starter Kits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

7 Installing Financial Consolidation Cube Designer Server Components. . . . . . . . . . . . . . . . . . . . . .777.1 Installing the SAP Financial Consolidation Cube Deployer Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Running the SAP Financial Consolidation Cube Deployer setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . 787.2 Installing the SSAS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Installing Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Installing SAP Financial Consolidation UDF for Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Installing the Microsoft Datapump Component under Microsoft Windows Server. . . . . . . . . . . . . . . 87Installing the Datapump on a Separate Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.3 Configuring Cube Designer Components for SSAS Cubes generated from an SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

7.4 Installing and Configuring the NetWeaver BW Server to deploy Infocubes with SAP Financial Consolidation Cube Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Installing FPM Basis on the NetWeaver BW Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Creating BW NetWeaver Roles to deploy Infocubes with Cube Designer. . . . . . . . . . . . . . . . . . . . . 96

7.5 Installing the BusinessObjects Enterprise XI 4 platform or the SAP BusinessObjects Information Platform Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Installing SAP EPM Solutions Connection Manager on the BOE platform. . . . . . . . . . . . . . . . . . . . 102Configuring the Central Management Console for SAP Cube Designer. . . . . . . . . . . . . . . . . . . . . . 104Configuring the Central Management Server for a distributed installation. . . . . . . . . . . . . . . . . . . 106

8 Configuring the SAP Financial Consolidation Cube Designer Components. . . . . . . . . . . . . . . . . 1078.1 Configuring Cube Deployer and Cube Designer Certificates for SAP HANA. . . . . . . . . . . . . . . . . . . . . 1078.2 Reverse proxy configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088.3 Creating an EPM Connection for SAP Financial Consolidation with NetWeaver BW Cubes. . . . . . . . . . . 1108.4 Creating an EPM Connection for SAP Financial Consolidation with SSAS Cubes. . . . . . . . . . . . . . . . . . 1128.5 Creating an EPM Connection for SAP Profitability and Cost Management (PCM) and SAP Strategy

Management (SSM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

SAP BusinessObjects Financial Consolidation Installation GuideContent C U S T O M E R 3

8.6 Creating an EPM Connection for Third Party Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

8.7 Creating an EPM Connection for Star Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

8.8 Creating an EPM Connection for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

9 Installing and Configuring Cube Designer Components for SAP HANA Modeling Views. . . . . . . 1209.1 Installing the Financial Consolidation HANA Add-on Delivery Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

9.2 Generating Time Data in SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

9.3 Configuring User Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

9.4 Configuring SAP HANA Users to Access Modeling Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Configuring system rights to allow SAP HANA users to have access to Modeling Views. . . . . . . . . . 129

Configuring system rights to allow SAP HANA users to have access to Modeling Views without FC security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Configuring SAP HANA roles to inherit the Financial Consolidation security on data. . . . . . . . . . . . 130

9.5 Configuring the Financial Consolidation Data source parameters for SAP HANA deployment. . . . . . . . .131

10 Installing Client Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13310.1 Installing the SAP Financial Consolidation client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

10.2 Installing SAP Financial Consolidation Cube Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

10.3 Configuring the SAP Financial Consolidation Cube Deployer URL. . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

11 Configuring Client Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13911.1 Configuring the Windows Client for Excel Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

11.2 Configuring the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

11.3 Configuring SAP Financial Consolidation Excel Web Schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Configuring Internet Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Specific configuration for using EWS folders offline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Specific configuration in Microsoft Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Enabling Macros for Excel 2003. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Enabling Macros for Excel 2007. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Settings of the CtPlConfig.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Configuring SAP Financial Consolidation Excel Web Schedules installation folder. . . . . . . . . . . . . . 149

12 Installing and configuring under Windows Terminal Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 15012.1 Installation modes in Windows Terminal Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

12.2 Configuring the Windows Terminal Services server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

13 Installing SAP Financial Consolidation in Standalone Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15213.1 Introduction to the standard / standalone configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

13.2 Installing SAP Financial Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

13.3 Creating a Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

13.4 Configuring the Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

13.5 Connecting to SAP Financial Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158


Content

1 What's new in version 10.1 of SAP Financial Consolidation

Links to information about the new technical features and documentation changes for SAP Financial Consolidation:

What's New in Version 10.1 of SAP Financial Consolidation

New technical features in SAP Financial Consolidation 10.1

New SAP Financial Consolidation Web site developped in HTML5

All SAP Financial Consolidation web components are now released in 64-bit mode.

ActivePDF is no longer a mandatory requirement, you can now choose between Active PDF Server or the new web printing feature embedded in the product setup. Its installation is automatically performed for all application servers. This new web printing is a two-step transformation process: Microsoft XPS Document printer input transformed to HTML, then HTML to PDF.

The following platforms are no longer supported:

● Windows Server 2003● Windows XP, Vista● Microsoft SQL Server 2005● IA 64-bit (Itanium) platforms● BOE 4.0

Changes to components:

● Runtime Microsoft Visual C++ 10.0 CRT (x64)● Runtime Microsoft Visual C++ 12.0 CRT (x64)● .NET 3.5 SP1 is no longer supported and is replaced by .NET 4.5.1. This concerns the web server (ASP.NET 4.5.1), but

also application server and Windows client.

With the BOE authentication mode, SAP Financial Consolidation requires one of the following components:

● BusinessObjects Enterprise XI 4.1or 4.2 or● Information Platform Services 4.1 or 4.2 (replaces the SAP BusinessObjects User Management System)

NoteTo connect SAP Financial Consolidation with the SAP Information Platform Services or the BusinessObjects Enterprise XI 4.1 platform, the setup automatically installs a tool called SAP User Management Client.

The list of prerequisite components have changed from version 10.0 of SAP Financial Consolidation.

SAP BusinessObjects Financial Consolidation Installation GuideWhat's new in version 10.1 of SAP Financial Consolidation C U S T O M E R 5

Document History

Version Date Description

SAP Financial Consolidation 10.1 SP01 August, 2015 First release of this document.

SAP Financial Consolidation 10.1 SP03 July, 2016 A new parameter (ForceHttps) has been added when Deploying the Administration Console Web Site under Windows Server: Deploying the Administration Console Web Site under Windows Server [page 35]

SAP Financial Consolidation 10.1 SP03 July, 2016 External authentication is now done through the Business Objects Enterprise XI web service: Creating a Data Source [page 38]External Authentication Configuration String [page 42]

SAP Financial Consolidation 10.1 SP04 November, 2016 Installation guide: Configuring Cube Deployer and Cube Designer Certificates for SAP HANA [page 107]

SAP Financial Consolidation 10.1 SP04 November, 2016 Installation guide: Configuring Cube Designer Components for SSAS Cubes generated from an SAP HANA Database [page 92]


What's new in version 10.1 of SAP Financial Consolidation

2 Contents of the version

SAP Financial Consolidation is composed of one folder: SAP Financial Consolidation

This folder contains all setups for the SAP Financial Consolidation application. Instructions on how to install the application are available in this guide.

● In the FC_101_INSTALLER subfolder: the SAP Financial Consolidation setup.● In the FC_101_XL_INSTALLER subfolder: the SAP Financial Consolidation Excel Link setup, which can be

operated via a Web server.

● This folder also contains in the FC_101_ABOUT\en folder, the following documentation:○ Master Guide○ Release Notes○ Installation Guide○ Administrator's Guide○ Security Guide○ Upgrade Guide○ Web User Guide○ Windows User Guide

SAP BusinessObjects Financial Consolidation Installation GuideContents of the version C U S T O M E R 7

3 Summary of Installation Steps

3.1 Installing SAP Financial Consolidation Core Components

Step to perform Link to more information

1. Install the corresponding database client connectivity on the application servers

Preparing to install SAP Financial Consolidation [page 13]

2. Install the new version of the SAP BusinessObjects Business Intelligence platform or the SAP BusinessObjects Information Platform Services

Prerequisites for the BusinessObjects Enterprise XI 4.1 platform or the SAP BusinessObjects Information Platform Services 4.1 [page 29]

3. Install SAP Financial Consolidation 10.1 on the application and web servers

Installing the SAP Financial Consolidation Application Server [page 45]Installing the SAP Financial Consolidation Web Servers [page 56]

4. Deploy the Administration Console Web Site Deploying the Administration Console Web Site under Windows Server [page 35]

5. Deploy all the Financial Consolidation web sites Deploying the SAP Financial Consolidation Web site under Windows Server [page 59]

6. Deploy the Financial Consolidation web services Installing and configuring the SAP Financial Consolidation Web Services [page 69]

7. Configure the data source and add the Financial Consolidation web site into the web administration console

Configuring the Web Administration Console [page 37]

8. Install SAP Financial Consolidation 10.1 on the client computers

Installing the SAP Financial Consolidation client [page 133]

9. Create the users in the SAP BusinessObjects Business Intelligence platform, or migrate the existing users using the Import / Export tool.

For more information, see the "User Administration and Authentication in Financial Consolidation" chapter from the SAP Financial Consolidation Security Guide.

● Prerequisites for the BusinessObjects Enterprise XI 4.1 platform or the SAP BusinessObjects Information Platform Services 4.1 [page 29]


Summary of Installation Steps

● Installing the SAP Financial Consolidation Broker Component [page 32]● Installing the SAP Financial Consolidation Application Server [page 45]● Installing the SAP Financial Consolidation client [page 133]● Deploying the SAP Financial Consolidation Web site under Windows Server [page 59]● Deploying the SAP Financial Consolidation Web HTML5 site under Windows Server [page 63]● Installing and configuring the SAP Financial Consolidation Web Services [page 69]● Deploying the Administration Console Web Site under Windows Server [page 35]

3.2 Installing SAP Financial Consolidation Cube Designer Components for SAP HANA Modeling Views


1. Deploy the Financial Consolidation web services Installing and configuring the SAP Financial Consolidation Web Services [page 69]

2. Deploy the Financial Consolidation HANA Add-on Delivery Unit on the SAP HANA Server and configure the appropriate HANA user rights

Installing the Financial Consolidation HANA Add-on Delivery Unit [page 120]

3. Configure the SAP Financial Consolidation Data source parameters for SAP HANA deployment

Configuring the Financial Consolidation Data source parameters for SAP HANA deployment [page 131]

4. Install the SAP BusinessObjects EPM Solutions Connection Manager on the Central Management Console of the SAP BusinessObjects Business Intelligence platform

Installing SAP EPM Solutions Connection Manager on the BOE platform [page 102]

5. Install SAP Financial Consolidation Cube Designer Installing SAP Financial Consolidation Cube Designer [page 135]



7. In the Central Management Console of the SAP BusinessObjects Business Intelligence platform, create the EPM connections through the EPM Solutions Connection Manager

Creating an EPM Connection for SAP HANA [page 118]

8. Deploy your cubes For more information, see the "SAP Financial Consolidation Cube Designer User Guide"

SAP BusinessObjects Financial Consolidation Installation GuideSummary of Installation Steps C U S T O M E R 9

● Installing SAP EPM Solutions Connection Manager on the BOE platform [page 102]● Installing SAP Financial Consolidation Cube Designer [page 135]● Installing the SAP Financial Consolidation Cube Deployer Server [page 77]● Installing the Financial Consolidation HANA Add-on Delivery Unit [page 120]● Installing the SAP Financial Consolidation Cube Deployer Server [page 77]● Installing the Microsoft Datapump Component under Microsoft Windows Server [page 87]● Installing FPM Basis on the NetWeaver BW Server [page 93]

3.3 Installing SAP Financial Consolidation Cube Designer Components for Microsoft SSAS


1. Deploy the SAP Financial Consolidation web services Installing and configuring the SAP Financial Consolidation Web Services [page 69]

2. Install the Financial Consolidation Cube Deployer component on the Deployer server

Installing the SAP Financial Consolidation Cube Deployer Server [page 77]

3. Install the SAP Financial Consolidation Cube Designer UDF for Security component on the SSAS server

Installing SAP Financial Consolidation UDF for Security [page 83]

4. Install and configure the datapump if you have a new SSAS server or if you migrated the existing SSAS server

Installing the Microsoft Datapump Component under Microsoft Windows Server [page 87]

5. Install the EPM Solutions Connection Manager on the Central Management Console of the SAP BusinessObjects Business Intelligence platform


6. Install the SAP Financial Consolidation Cube Designer component

Installing SAP Financial Consolidation Cube Designer [page 135]







Creating an EPM Connection for SAP Financial Consolidation with SSAS Cubes [page 112]


3.4 Installing SAP Financial Consolidation Cube Designer Components for Star Schema



2. Install the SAP Financial Consolidation Financial Consolidation Cube Deployer on the Deployer server


3. Install the SAP BusinessObjects EPM Solutions Connection Manager on the Central Management Console of the SAP BusinessObjects Business Intelligence platform


4. Install the SAP Financial Consolidation Cube Designer Installing SAP Financial Consolidation Cube Designer [page 135]




Creating an EPM Connection for Star Schema [page 117]


3.5 Installing SAP Financial Consolidation Cube Designer Components for NetWeaver BW Cubes



SAP BusinessObjects Financial Consolidation Installation GuideSummary of Installation Steps C U S T O M E R 11


2. Install the Financial Consolidation Cube Deployer component on the Deployer server


3. Install the FPM Basis component on the NetWeaver BW Server

Installing FPM Basis on the NetWeaver BW Server [page 93]

4. Install the EPM Solutions Connection Manager on the Central Management Console of the SAP BusinessObjects Business Intelligence platform


5. Install the SAP Financial Consolidation Cube Designer component

Installing SAP Financial Consolidation Cube Designer [page 135]




Creating an EPM Connection for SAP Financial Consolidation with NetWeaver BW Cubes [page 110]




4 Preparing to install SAP Financial Consolidation

4.1 External Components Prerequisites

SAP BusinessObjects Financial Consolidation external components

The following list presents all the components that are automatically installed by the SAP BusinessObjectsFinancial Consolidation setup:

● SAP User Management Client: the SAP User Management Client (UMC) is a component that manages communication between the Financial Consolidation components and the BusinessObjects Enterprise XI 4.1 platform or the SAP Information Platform Services 4.1.

NoteThe SAP User Management Client component is automatically installed by the setup in C:\Program Files\SAP BusinessObjects. However, if you want to install it in another folder, you can manually execute the UMC.exe setup located in the UMC_101_INSTALLER folder.

● Microsoft DHTML Editing Component (For Windows Vista and +)● Microsoft Visual C++ 2005 Redistributable (x86)

NoteAs of SAP BusinessObjects Financial Consolidation Support Package 04, this component is no longer necessary, you can uninstall it if you want.

● Microsoft Visual C++ 2013 Redistributable (x86) 12.0.21005● Microsoft Visual C++ 2013 Redistributable (x64) 12.0.21005● Microsoft .Net Framework 4.5.1 English

If you want to use the web printing feature embedded in the product setup, you must ensure that the Microsoft XPS Document Writer is installed on all application servers.

Financial Consolidation Cube Designer external components

If you plan to install Financial Consolidation Cube Designer, the following table summarizes all the external components that must be installed on each Cube Designer component.

Component External components to install

Deployer ● Microsoft SQL Server 2012 components:

SAP BusinessObjects Financial Consolidation Installation GuidePreparing to install SAP Financial Consolidation C U S T O M E R 13

Component External components to install

○ sqlncli.msi

● Microsoft SQL Server 2014 components:○ SharedManagementObjects.msi○ SQL_AS_OLEDB.msi○ SQLSysClrTypes.msi

● Oracle client with the Oracle OLEDB Provider● Microsoft .Net Framework 4.5.1● Microsoft IIS with ASP.Net 4.5.1● Microsoft Web Service Enhancements (WSE) 3.0● Visual C++ Redistributable Packages for Visual Studio

2013

UDF for Security ● Microsoft .Net Framework 4.5.1● Microsoft IIS with ASP.Net 4.5.1● Microsoft Web Service Enhancements (WSE) 3.0

Datapump ● Microsoft .Net Framework 4.5.1● Microsoft IIS with ASP.Net 4.5.1● Microsoft SQL Server 2008, 2008 R2 or 2012 Analysis

Services OLE DB Provider

Designer ● Microsoft .Net Framework 4.5.1● Microsoft Web Service Enhancements (WSE) 3.0

4.2 Microsoft SQL Server Prerequisites

When you install Microsoft SQL Server, you can use the default settings proposed by the setup, except for the Authentication mode: When installing the SQL Server engine, you must select the Mixed mode authentication option.

After the SQL Server engine installation, you can modify the following settings:

Modifying the degree of parallelism

The following settings can improve performance, especially when SAP Financial Consolidation is used with a large number of concurrent users (more than 50 concurrent users).

1. Edit the properties of the SQL Server engine.2. Select the Advanced tab.3. Set the Max degree of Parallelism setting to 1 processor.


Preparing to install SAP Financial Consolidation

4.2.1 Creating the Financial Consolidation Database

Procedure

1. Create the Financial Consolidation database using the default options.

2. Create a login and make sure that this login is the database owner.

NoteYou can use the following command:

use <database> gosp_changedbowner <login>go

3. Then you must activate the READ_COMMITTED_SNAPSHOT option. This setting improve performance, especially when SAP Financial Consolidation is used with a large number of concurrent users.


CautionThis option is mandatory.

a. Log on to the SQL Server server.b. Select the SAP Financial Consolidation databases.c. Run the following query:

USE master goALTER DATABASE Mybase SET READ_COMMITTED_SNAPSHOT ONgo

CautionThe database must not be running during this query. If a connection remains open on this base, the query will be blocked.

4. In the Recovery model groupbox, select the following option:

○ Full if you want to activate the log.○ Simple if you do not want to activate the log.

NoteIf you activate the log, you must regularly back up your database logs. If you do not do so, the database log will be completely filled.

5. In the Settings groupbox, we recommend that you select the following options:

○ Auto create statistics○ Auto update statistics

The others are optional.

CautionYou should not select the Auto shrink and Auto close options on a server so as to not decrease its performance.

Only one login is required to connect to the base with SQL Server. This login must be the dbo of the base. This login can be different from the sa login.

CautionYou cannot log in using a login with the same rights as the dbo.

The database collation should be one that uses the 125X code page, e.g. the Latin1_General collation with the 1252 code page. You should select a case-insensitive (CI) and accent-sensitive (AS) sort order.



ExampleLatin1_General_CI_AS.

4.2.2 Installation prerequisites for the SQL Server client

These requirements apply to the client part of the database engines.

The SQL Server Client must be installed on:

● SAP Financial Consolidation Application server● SAP BusinessObjects Cube Deployer server● SAP Financial Consolidation Archiving Tool component

CautionYou must install the SQL Server client that corresponds to the SQL Server engine you installed.

Depending on your operating system: 32 or 64-bit versions:

● If you have a 64-bit operating system, you must install the SQL Server Client 64-bit (that automatically includes the 32-version of the client).

● If you have a 32-bit operating system, you must install the 32-bit version of SQL Server client.

NoteIt is mandatory to apply the last SQL Server Service Packs.

NoteIf you have problems connecting to the database, you may have to perform the full SQL Server client installation so that you can use the application's configuration and analysis tools. The optimal setup for SAP Financial Consolidation is an SQL Server client configured in TCP/IP mode.

NoteIf an SQL client is already installed, you should check that it is configured to function in English.


4.3 Oracle Prerequisites

4.3.1 Server Prerequisites

4.3.1.1 Oracle Installation Requirements

When installing the Oracle database engine, the required components are the Oracle server on the DBMS server and the Oracle client with the Oracle provider for OleDB on the application servers. All the other components are optional. Oracle Corporation recommends that you upgrade your client software to match the current server software and use the latest patch releases.

TipWe recommend that you install the client layer delivered with your database engine on the application server.

NoteTo find out more about the operating systems supported, recommended patches as well as installation procedures, you can consult the Oracle website at: http://www.oracle.com .

4.3.1.2 Oracle Instances Requirements

You must create a dedicated instance for the SAP Financial Consolidation database. This instance must be in OLTP mode.

NoteEven though the Financial Consolidation can be stored in an existing instance with other existing schemas, it is recommended to have a dedicated instance for the Financial Consolidation database.

SAP Financial Consolidation supports Oracle database in dedicated server mode or in shared server mode (formerly known as multi-threaded server mode).

The character set recommended for a Financial Consolidation database is AL32UTF8. The national character set recommended is UTF8. When the database is configured in archive log mode, make sure sufficient disk space is available for the archived redo logs and that the system is sized appropriately to support the system overhead associated with archiving.

Once the Oracle instance is created, you must apply the SAP Note 1431798 - Oracle 11.2.0: Database Parameter recommendations.

CautionContrary to what is mentioned in this SAP Note, the setting _OPTIM_PEEK_USER_BINDS must be set to its default value TRUE.



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

In addition to these settings, it is strongly recommended to modify the following parameters in order to increase performances:

Table 1:

DB_BLOCK_SIZE = 16384 (*) DB_CACHE_SIZE= 629145600 (**)SHARED_POOL_SIZE = 67108864SHARED_POOL_RESERVED_SIZE = 0JAVA_POOL_SIZE = 0LARGE_POOL_SIZE = 0PROCESSES = 300 (**)WORKAREA_SIZE_POLICY= AUTOPGA_AGGREGATE_TARGET=209715200 (**)OPEN_CURSORS = 1000 RECYCLEBIN=OFF

(*) depending on the type of server e.g. Windows, Unix, etc.

(**) depending on the server characteristics e.g. RAM, number of users, etc.

These settings are valid for an Oracle instance using 1 GB memory. This is the minimum value but it is recommended to use more than 1 GB memory. The Oracle automatic management of settings is supported but you will get better performance if you set the parameters manually.

For optimum performance, the value of the db_cache_size parameter should be at least three times the size of the largest consolidated data table. You should also take the RAM available on the server into account when setting the value of this parameter.

For example, if your database contains a consolidated data table whose size is 150 MB, the value of the DB_CACHE_SIZE parameter should be 471859200, i.e. 450 MB of RAM.

If more memory is available on the server, you should increase the values of the DB_CACHE_SIZE and PGA_AGGREGATE_TARGET parameters.

An Oracle connection uses 500 KB to 1 MB of RAM on the server. Because there can be as many open connections as users connected in SAP Financial Consolidation, you should ensure that there is sufficient memory available on the server to manage these connections.

Moreover, Oracle recommends setting a PGA_AGGREGATE_TARGET parameter to define the total amount of memory available for all user sessions, instead of using the SORT_AREA_SIZE parameter, used only for backward compatibility. The amount of RAM dedicated to the sort area is no longer limited to a fixed value per connection as was the case in Oracle8i. Instead, it is now allocated dynamically from Oracle9i.

4.3.1.3 Database Requirements

You should change certain settings for the Oracle client on the SAP Financial Consolidation application server. To find out more about the configuration of the Oracle client, see the Installation guide. You can also apply the same settings to the Oracle server so as to avoid configuring the Oracle client on all the application servers.

SAP Financial Consolidation uses a single Oracle account to store all its database objects and to manage all its connections to the Oracle server. Typically, multiple simultaneous connections to the server will be established with this single user account at any given time. Different schemas to separate development and production environments can coexist in the same database.


The Oracle user account requires the following privileges:

● CONNECT, RESOURCE

If your company's security policy prevents you from applying these privileges, then you can grant the following ones:

● CREATE SESSION, CREATE TABLE, CREATE SEQUENCE, CREATE CLUSTER, CREATE TYPE

For customization projects, the following additional privileges may be required:

● CREATE PROCEDURE, CREATE TRIGGER, CREATE VIEW

TipSAP technical support can provide an Oracle Database Configuration Asistant's template or a sample database creation script and initialization parameter file customized for SAP Financial Consolidation, which can be edited to suit the requirements of your site.

CautionYou must not assign the SELECT ANY TABLE privilege or assign a role including this privilege (example: DBA) to the owner of the schema.

NoteTo find out more about the different server mode configurations, archiving and other database administration topics, you can consult the Oracle Administration Guide.

4.3.2 Client Prerequisites

4.3.2.1 Installation Prerequisites for the Oracle ClientThe Oracle Client must be installed on:

● Financial Consolidation Application servers● FC Cube Deployer servers● Microsoft SSAS servers● Archiving Tool component

CautionYou must install the Oracle client version that corresponds to the Oracle database engine you installed.

Depending on your operating system: 32 or 64-bit versions:

● If you have a 64-bit operating system, you must install the 64-bit version of the Oracle Client.

CautionThis does not apply to the application server and to the Archiving Tool component: you must install the 32-bit version of the Oracle client on the Financial Consolidation server, even if it is a 64-bit version operating



system. If you install other components on the application server (like FC Cube Deployer for example), you must install both versions of the Oracle client.

● If you have a 32-bit operating system, you must install the 32-bit version of Oracle client.

NoteIt is mandatory to apply the last Oracle Patchset.

The 32-bit Oracle client and its OleDB provider that corresponds to the version of your database engine must be installed on the computers that have the server applications so that SAP Financial Consolidation can be installed and used with Oracle.

You should make sure that the character set used is AMERICAN_AMERICA. WE8MSWIN1252. You can check this parameter in the registry by changing the following key:

[HKEY_LOCAL_MACHINE\Software\Oracle]

"NLS_LANG"=" AMERICAN_AMERICA.WE8MSWIN1252"

If the value of the parameter is NA, the character set used by the client computer is the default defined on the Oracle instance of the server. If you do not want to change the value of the NLS_LANG parameter on the client computer, check that the value defined on the Oracle server is correct.

Then you must create an identical Oracle TNS name to match the one set on the Financial Consolidation administration console of the application servers.

4.4 SAP HANA Prerequisites

The following prerequisites are mandatory to run the SAP Financial Consolidation application on top of the SAP HANA database.

4.4.1 SAP HANA Server Prerequisites

SAP Financial Consolidation uses a single SAP HANA user (for example, this user is named [FC_SCHEMA] in the documentation) to store all its database objects and to manage all its connections to the SAP HANA server. Typically, multiple simultaneous connections to the server will be established with this single user account at any given time. Different schemas to separate development and production environments can coexist in the same database.

If you want to use SAP HANA to generate Modeling Views with Financial Consolidation Cube Designer, you also need another SAP HANA user which will be used as a technical account used to access the Financial Consolidation delivery unit (In this documentation, this user is named [TECHNICAL_USER]). In addition, you must create several users that will access Modeling Views [REPORTING_USER_XX].


4.4.2 SAP HANA Client Prerequisites

Prerequisites

The SAP HANA Client must be installed on all the Financial Consolidation Application servers of your environment.

NoteYou must install the SAP HANA client revision that corresponds to the SAP HANA database engine you installed.

You must install the 32-bit version client of SAP HANA on the application server (as the CtServer component is running in 32-bit mode only).

Context

Once you installed the prerequisites listed above, you must install the ODBC system Datasource.

Procedure

1. Open the ODBC Data Source Administrator by running the following command: %windir%\SysWOW64\odbcad32.exe.The ODBC Data Source Administrator dialog box opens.

2. Select the System DSN tab and then click Add.The Create New Datasource wizzard opens.

3. Select the HDBODBC32 provider and click Finish.The SAP HDB dialog box opens.

4. In the Data Source Name field, enter the name of the data source (the same name that you will enter when creating the Financial Consolidation data source).

5. Enter a description.6. Enter the Server and Port number and click Connect.7. Enter the User and Password (FC_SCHEMA user credentials) and click the Connect using SSL option if you

use the SSL protocol.8. Click OK.



4.5 Databases prerequisites for Star Schema and Custom Fact Tables

When using Star schemas and custom fact tables, you must configure the following, depending on the database engine you are using.

NoteWhen configuring the star schema database, the Business Objects and the star schema databases can be installed on separated servers.

Prerequisites for SQL Server

If you are deploying a star schema database on SQL Server, you must work with the star schema DBO.

In addition, for Star Schemas and for SQL server 2008 only, you must grant the following rights to the star schema DBO:

ALTER ANY LINKED SERVER ALTER ANY LOGIN

The Star Schema user must also have Read access to the Financial Consolidation database.

If you want to deploy a Star Schema into an Oracle database (11g or higher) from a Microsoft SQL Server 64 bits Financial Consolidation database (installed on Microsoft Windows Server 2008 R2 or higher), you must do the following:

1. Download and install the "64-bit Oracle Data Access Components (ODAC)" Oracle driver on your SQL database server: http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html

.2. Unzip the file to a folder of your choice.3. Run the following command from that folder to install the driver in the oracle client installation folder:

...\ODAC121024Xcopy_x64>.\install.bat oledb C:\app\<user>\product\11.2.0\Client_1\odac64 odac64 true

4. Reboot the SQL server machine.5. When defining the Star Schema deployment, select the “Oracle Provider for OLE DB” driver.

Prerequisites for Oracle

For Star Schemas only, the Oracle star schema owner account requires the following privileges:

CONNECT, RESOURCE, CREATE DATABASE LINK, DROP PUBLIC DATABASE LINK


http://help.sap.com/disclaimer?site=http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html

http://help.sap.com/disclaimer?site=http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html

If your company's security policy prevents you from applying these privileges, then you can grant the following ones:

CREATE SESSION, CREATE TABLE, CREATE SEQUENCE, CREATE CLUSTER, CREATE DATABASE LINK, DROP PUBLIC DATABASE LINK

For customization projects, the following additional privileges may be required:

CREATE PROCEDURE, CREATE TRIGGER, CREATE VIEW, CREATE FUNCTION

4.6 Web Components Prerequisites

4.6.1 Prerequisites for Windows Server Web Components

Before deploying SAP Financial Consolidation Web components, the following requirements must be met:

● Microsoft Windows Server 2008, 2008 R2, 2012 or 2012 R2 operating system● Microsoft .NET framework 4.5.1● Internet Information Services (IIS) 7 / 7.5 / 8 / 8.5● If you are using ActivePDFServer, this component must be installed on all application servers.

NoteAs the 10.1 version contains a new component that allows you to generate PDF, installing ActivePDFServer is no longer mandatory.

4.6.1.1 Installing IIS

Procedure

1. In the Server Manager, click Roles Add Roles .The Add Roles Wizard opens.

2. In the Select Server Roles window, select the Web Server (IIS) option.3. Click Next.

The Select Role Services window opens.4. In the Application Development zone, select the ASP.NET option.

If a message appears, click Yes.5. The options to select are the following:

○ Common HTTP Features○ Static Content○ Default Document



○ Directory Browsing○ HTTP Errors

○ Application Development○ ASP.NET○ .NET Extensibility○ ISAPI Extensions○ ISAPI Filters

○ Health and Diagnostics○ HTTP Logging○ Request Monitor

○ Security○ Basic Authentication○ Windows Authentication

CautionOnly for the HTML5 web site, if you want to use Single Sign On with Windows Authentication mode.

○ Request Filtering○ Performance

○ Static Content Compression○ Management Tools

○ IIS Management Console6. Click Next.

Click Next and then Install.7. Open the IIS Manager.8. In the Connections pane, select the server.9. In the right pane, under the IIS section, open the ISAPI and CGI Restrictions feature.10. Right-click on the ASP.NET v4.0.30319 Framework 64 bit line and select Allow.

4.6.1.2 Creating Application Pools with IIS

Context

Once IIS is installed, you must create one application pool for each SAP Financial Consolidation application that you will deploy:


● Financial Consolidation Web site● Financial Consolidation Administration Console web site● Financial Consolidation Web Services● Financial Consolidation Web HTML 5 site

NoteTo find out more about the application pool configuration options, see the Application Pools Options under Windows Server [page 27] table in the next chapter.

Procedure

1. Open the IIS Manager.2. In the Connections pane, expand and select the Application Pools.3. Right-click Application Pools and select Add Application Pool.

The Add Application Pool dialog box opens.

4. In the .Net Framework version zone, select the .Net Framework 4.0 option.5. In the Managed pipeline zone, select one of the following options:

○ The Integrated option for the following web sites:○ Financial Consolidation Web HTML 5 site○ Financial Consolidation Administration Console web site○ Financial Consolidation Web Services

○ The Classic option for the Financial Consolidation web site.6. Click OK.

You then need to configure this new application pool, as explained in the next chapter.



4.6.1.3 Application Pools Options under Windows Server

To configure the application pools options:

1. Right-click the application pool ans select Advanced Settings.The Adanced Settings dialog box opens:

2. Configure the application pool options depending on the web site you deploy. The following table summarizes these options:

Table 2:

Application Pool Properties Section Name

Options to select

Financial Consolidation Web site

General Set the Managed Pipeline Mode option to Classic mode


Application Pool Properties Section Name

Options to select

Process Model ● In the identity field, select a login and password of a user account with the following rights:○ Use the DCOM protocol,○ Have read/write access to the Financial Consolidation installation

folders,○ Have read/write access to the Financial Consolidation Web site de

ployment folder,○ Be part of the local IIS_IUSRS group,○ Be part of the same domain unless you do not want to apply DCOM

encryption.● Set the Idle timeout option to zero

Recycling Set the Regular Time Interval option to zero

Financial Consolidation Web Administration console

&

Financial Consolidation web services

&

Financial Consolidation Web HTML5 site

General Set the Managed Pipeline Mode option to Integrated mode

Process Model In the identity field, select a login and password of a user account with the following rights:

● Use the DCOM protocol,● Have read/write access to the Financial Consolidation installation folders,● Have read/write access to the Financial Consolidation Web Administration

console deployment folder,● Be part of the local IIS_IUSRS group,● Be part of the same domain unless you do not want to apply DCOM en

cryption.

4.6.1.4 Increasing limit size of HTTP requests

Context

By default, the size of files to download is limited up to 4 MB. If you want to use Data Link or EWS files, this parameter may be insufficient. To increase the size of this parameter, you must follow this procedure:

Procedure

1. Open a DOS prompt.2. Run the following command:

C:\Windows\System32\inetsrv\appcmd set config /section:requestfiltering /requestlimits.maxallowedcontentlength:40000000"



In this example, the size has been increased to 40 MB.

4.7 Prerequisites for the BusinessObjects Enterprise XI 4.1 platform or the SAP BusinessObjects Information Platform Services 4.1

Context

You can now use two platforms with SAP Financial Consolidation:

● BusinessObjects Enterprise XI 4.1 (BOE XI 4.1)If you want to install BusinessObjects Enterprise XI 4.1. For more information on how to install it, see the SAP web site: http://help.sap.com.

● Or SAP BusinessObjects Information Platform Services 4.1If you want to install the SAP BusinessObjects Information Platform Services. For more information on how to install it, see the SAP BusinessObjects Information Platform Services Installation Guide and the SAP web site: http://help.sap.com.

The SAP BusinessObjects Information Platform Services implements the BusinessObjects Enterprise XI user management sub system. It allows Enterprise Performance Management Solutions to use the BOE authentication without having to install a full BusinessObjects Enterprise XI platform.

The SAP BusinessObjects Information Platform Services does not include any BI tools available in the full BusinessObjects Enterprise XI platform. BI tools like WebI or BI Launch Pad are only available with the full BOE XI platform.

NoteYou can migrate from SAP BusinessObjects Information Platform Services to the full BusinessObjects Enterprise platform if needed.

CautionIf you use the BusinessObjects Enterprise XI 4.1 platform or the SAP BusinessObjects Information Platform Services 4.1 with the SSL protocol, you must configure the User Management Client component to use the appropriate SSL certificate on the Financial Consolidation application servers. To find out more, see the Activating the SSL Protocol on the User Management Client [page 67] chapter.

4.7.1 Installing Information Platform Services 4.1

Context

Before installing Information Platform Services 4.1, the following requirements must be met in this order:


http://help.sap.com

http://help.sap.com

Procedure

1. First install SAP Financial Consolidation.For more information, see Installing the SAP Financial Consolidation Application Server [page 45].

2. In the C:\Program Files (x86)\SAP BusinessObjects\Financial Consolidation\tools folder, copy the PlatformInstaller.exe file and paste it into the same folder where the Information Platform Services 4.1 setup is stored.

3. Execute the PlatformInstaller.exe instead of the setup.exe file for the Information Platform Services 4.1 setup.

CautionIf you try to execute the Information Platform Services 4.1 setup, you will be prompted to enter a license number which is automatically provided by the PlatformInstaller.exe.

NoteIf you cannot paste the PlatformInstaller.exe into the same folder where the Information Platform Services 4.1 setup is stored, you can execute the following DOS command:

PlatformInstaller.exe <setup_filename>

For example:

PlatformInstaller.exe D:\install_IPS\setup.exe

NoteYou can install Information Platform services (IPS xi4) on another server where FC is not installed.You just need to retrieve the PlatformInstaller.exe file from an existing FC installation folder, and execute this file as indicated above.

4.8 Configuring X.509 certificates in SAP Financial Consolidation

Context

The SAP Financial Consolidation setup installs and uses two default X.509 certificates. With these default X.509 certificates, you can use the application in a test or a development configuration. If you are running SAP Financial Consolidation and SAP BusinessObjects Cube Designer in a production environment, it is recommended that you get a certificate from a commercial or free certification authority.

By default, these certificates are not activated. You must activate them in order to communicate with other products.

These two X.509 certificates are the following:



● The first one is used to sign communications between SAP Financial Consolidation and SAP BusinessObjects Cube Designer components.

● The second one is used to sign communications between application servers if you want to use the BFC Monitoring service, that enables you to open performance counters through the Windows Performance Monitor.

To activate them, the following steps are required:

Procedure

1. In the SAP Financial Consolidation installation folder, edit the CtBroker.config file.2. Uncomment the parameter Certificate subjectName. If you want to use another certificate than the one

installed by default, enter the parameters of your own certificate.

<?xml version="1.0" encoding="utf-8"?> <configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.sap.com/2008/09/15/CtBroker/Configuration"> <SharedTrustedCertificates>     </SharedTrustedCertificates> <DataSources> </DataSources> </configuration>

3. Save and close the file.4. Restart the CtBroker service.


5 Installing Financial Consolidation Server Components

5.1 Installing the SAP Financial Consolidation Broker Component

Prerequisites

Before installing, you must use a valid Windows domain account with the Log on as a batch job and Log on as a service privileges and a password that never expires. This account must be part of the DCOM user group.

You must have write access rights on the following folders:

● the SAP Financial Consolidation installation folder● the folder where the Applicationdatasource.xml file is stored● folders where the logs are stored

NoteThe built-in system account can not be used.

RememberAs SAP Financial Consolidation 10.1 now uses a new setup technology, you are not prompted to uninstall earlier versions of SAP Financial Consolidation but you need to manually uninstall all previous versions via the Windows Control Panel before you can install SAP Financial Consolidation 10.1.

CautionIf you are installing SAP BusinessObjects Financial Consolidation on Microsoft Windows 7, Microsoft Windows Server 2008 or 2008 R2, you must install the following corresponding updates to prevent security issues: https://support.microsoft.com/en-us/kb/2533623 .

Context

NoteYou should not install SAP Financial Consolidation on a server whose name contains the _ (underscore) character.


Installing Financial Consolidation Server Components

http://help.sap.com/disclaimer?site=https://support.microsoft.com/en-us/kb/2533623

Procedure

1. Connect to the server with an administrator account.

NoteIf you carry out an installation using the "Remote Desktop Connection" tool, you are required to do this with the "Console" (mstsc /admin) session. Otherwise, SAP Financial Consolidation may not work properly.

2. Execute the Setup.exe file.

CautionYou must select the "Run as administrator" option when executing the setup.

NoteSince the SAP Financial Consolidation setup is not digitally signed, a warning message may appear when you execute the setup. This warning will not prevent you from installing Financial Consolidation thus you may ignore it and continue your setup.

If one of the components required is missing or not in the minimum version supported, the List of requirements to install dialog box opens.

CautionIf the computer you are installing is only hosting the broker component, then the SAP BusinessObjects User Management Client component is not required. As the UMC setup starts automatically, you can click Cancel and the SAP Financial Consolidation setup will continue normally.

3. Click Install.The Welcome to the setup wizard dialog box opens.

4. Click Next.5. The License Agreement dialog box opens.6. Select the I accept the terms in the license agreement option.7. Click Next.

The Destination Folder dialog box opens.8. Select the folder or enter the name of the folder where you want to install SAP Financial Consolidation and

click Next.

The Setup Type window opens.9. Select the Server installation option and click Next.

The DCOM Configuration dialog box opens.10. Enter the user login and password that will be used to start SAP Financial Consolidation and click Next.

CautionThis account must have the Log on as a batch job privilege.

The Custom setup dialog box for selecting the required components opens.

SAP BusinessObjects Financial Consolidation Installation GuideInstalling Financial Consolidation Server Components C U S T O M E R 33

11. Select the following components:

○ Application: If you check this option, all of the components required for running SAP Financial Consolidation, including the application server, will be installed.

○ Financial Consolidation Web Administration Console: This option enables you to access the tool used for managing the data sources.

NoteThe Financial Consolidation Web Administration Console component is not mandatory. You can choose to install this component on another server, the web server for example.

12. Click Next.

The Ready to install the program dialog box opens.13. If the settings are correct, click Install.

NoteDepending on the performance of your computer, the installation may last several minutes. You should not perform any other task until the installation is complete in order to ensure that the application is correctly installed.

Once the installation is complete, the Installation complete dialog box opens.14. Click Finish.15. Restart the server.



NoteWe recommend that you change the environment variables of the TEMP and TMP server so that they correspond to folders that are not linked to a user profile.

NoteIf your environment is made up of different domains or some computers are outside of the domain, you must follow the instructions provided in the Security Guide's chapter "DCOM configuration".

By default, the DCOM Authentication Level is now set to the maximum security mode (Packet Privacy) and therefore only works for domain users.

5.1.1 Deploying the Administration Console Web Site under Windows Server

Procedure

1. Open the IIS Manager.2. Create an application pool with its relevant parameters, described in the Application Pools Options under

Windows Server [page 27] chapter.

NoteFor more information on how to create an application pool, see the Web Components Prerequisites chapter of this documentation.

3. In the SAP Financial Consolidation installation folder, copy the WebAdmin subfolder.4. Paste this subfolder to \Inetpub\wwwroot\.5. You can rename this folder to reflect the URL that you want to display.

NoteYou can deploy the WebAdmin site in a folder other than the default wwwroot folder. To do so, create a virtual folder in IIS that points to the folder that you use.

6. In the IIS Manager, right-click on the folder and select Convert To application in order to deploy the web site.The Add Application dialog box opens.


7. Select the application pool you created at step 1.8. Once the application is created, click on it and double-click on the Authentication feature to open it.

Select the Anonymous Authentication line and edit it.

9. In the Edit Anonymous Authentication Credentials, enter the login and password of a user account with the following rights:○ Use the DCOM protocol,○ Have read/write access to the Financial Consolidation installation folders,○ Have read/write access to the Administration Console Web Site deployment folder,○ Be part of the local IIS_USRS group,○ Be part of the same domain unless you do not want to apply DCOM encryption.

10. Click OK.11. Right-click on Anonymous Authentication and select Enable.12. click OK.13. In the IIS Manager, go back to the Web admin site Home page and open the Application Settings feature.14. Edit the BrokerHostName parameter and modify its value with the name of the server hosting the CtBroker

component.



CautionIf the Web administration console and the CtBroker component are installed on the same machine, do not modify this parameter and leave the default Localhost value.

15. Edit the ForceHttps parameter if you want to force users to connect the Administration Console Web Site using HTTPS mode and set its value to "true".

5.1.2 Configuring the Web Administration ConsoleThe SAP Financial Consolidation web administration console is a web site used to perform all the application's administration tasks.

To start the console, connect to the Administration Console web site you deployed in the Deploying the Administration Console Web Site under Windows Server [page 35] chapters. For example, http://localhost/WebAdmin.

NoteYou should select this component when you run the SAP Financial Consolidation setup.

The Administration console appears.


The Administration console contains four views for each of the data sources:

● Configuration: this view is used to define the standard and advanced settings for the data source. For more information, see Configuring Standard Parameters [page 41] and the Administration guide ("Managing data sources" chapter) .

● Servers: this view shows the list of the different servers in use in your data source.● Operation: this view enables you to start the data source. For more information, "Starting and stopping data

sources". this view displays the list of computers defined for a given data source and the statuses of the instances run on each computer. To find out more, see the Administrator's guide ("Managing data sources" chapter).

● Activity: this view shows the list of users connected to each data source. To find out more, see the Administration guide ("Managing data sources" chapter).

● Monitoring: this view helps you to monitore the application. To find out more, see the Monitoring the Application chapter in the Administrator's Guide.

5.1.2.1 Creating a Data Source

Procedure

1. Connect to the Administration Console web site you deployed in the previous chapter. For example, http://localhost/WebAdmin.

2. Click Create a new data source.3. Enter the data source name and its password if you want to set a password to protect the data source.4. Click Next.

The DB Configuration string dialog box opens.



5. In the Select your provider field, select the appropriate OLEDB provider.

○ OraOLEDB: provider for Oracle databases○ SQLNCLI: native OLEDB provider for SQL Server 2005○ SQLNCLI10: native OLEDB provider for SQL Server 2008 and 2008 R2○ SQLNCLI11: native OLEDB provider for SQL Server 2012 and 2014○ MSDASQL: generic ODBC provider, used for SAP HANA databases

NoteDo not forget to install the necessary client database connectivity on all application servers of your environment.

6. In the Enter the data source field, enter the following information, depending on the database engine:

○ For SQL Server, enter the instance name: SERVER\INSTANCE (for a default instance, just enter the machine name).

○ For Oracle, enter the Oracle Service Name (also named TNS Name or Alias name).○ For SAP HANA, enter the ODBC data source name that you created using the generic ODBC provider (see

the SAP HANA Client Prerequisites [page 22] chapter.7. In the Enter the initial catalog field, enter the following information, depending on the database engine:

○ For SQL Server, enter the SQL Server database name.○ For Oracle and SAP HANA, you do not need to enter this parameter.


8. In the Extra parameters field, enter extra parameters if needed:For example, for a specific Oracle RAC configuration. For more information on these parameters, see Database Connection String [page 44].

9. In the Login and Password fields, enter the login and password of the database owner (for SQL Server) or the schema owner (for Oracle and SAP HANA).

NoteIf you are using Dynamic Analysis in Microsoft Excel with an SAP HANA database, the login must be capitalized.

10. Click Next.11. In the Configure the internal authentication dialog box, select the Internal authentication option and click Next.12. The Configure external authentication dialog box opens.13. Select the BusinessObjects XI authentication (Web Service) to use the BusinessObjects XI 4 platform as the

authentication provider.14. Enter the complete web service name in the CMS server name field, as follows: http://UMS-SERVER-NAME:

8080/dswsbobje/services/session.

NoteFor more information, see the next chapter.

NoteIf your BOE platform uses a CMS cluster, then you need to indicate, in the CMS server URL field, all the cluster members, one by one, separated by a coma.

NoteThe other types of authentication are no longer supported by SAP Financial Consolidation. The only reason they are available is to ensure compatibility with previous versions. You should always use the BOE authentication, unless you are migrating from a previous Financial Consolidation version, and your authentication mode must remain the same.

15. Select the Activate SSO for Web EPM Suite option if you want to user Single Sign On authentication for all EPM for Finance applications installed with the same BusinessObjects Enterprise platform.

16. Click Next.17. In the next dialog box, enter the computer on which the application server will be hosted.

If you are in a multi-server configuration, enter or select the computer that will host the first server in the architecture.

TipYou can now add as many application servers as required in the Administration console by clicking Add a new application server from the Server options menu.

18. Click Finish.

The administration console displays the new data source.



19. Open this new data source and click Operation.The console displays the new application server.

20.Check the Activate machine option.

CautionIf you do not check this option, the application server will not start.

TipOnce you have created one data source, you can create another by clicking the duplicate option in the data sources list page. Its properties will be identical to those of the data source you duplicated. You can, however, change them if required.

5.1.2.2 Configuring Standard Parameters

NoteYou cannot change the console's settings once the data source is running.

The Configuration page is used to define the settings for the data source.


The information that is in the ApplicationDataSources.xml file is displayed in this view. Because this file is encrypted for security reasons, the only way you can define a data source is via the Administration console.

5.1.2.2.1 External Authentication Configuration String

If authentication is managed by the Business Objects Enterprise XI platform, you must choose the between the two following options:

● Standard external authentication through the Business Objects Enterprise XI platform, you must select the BusinessObjects Enterprise XI authentication option and enter the name of the Central Management Server (CMS) of your BusinessObjects Enterprise XI platform in the CMS server name field.

CautionThis option is now deprecated, it is recommended that you use the Web Service as indicated below.



● External authentication through the BusinessObjects Enterprise XI web service, select the BusinessObjects Enterprise XI authentication (Web Service) option and enter the complete web service name in the CMS server name field, as follows: http://UMS-SERVER-NAME:8080/dswsbobje/services/session.

CautionIt is recommended that you use this option. This option is mandatory for all other authentication types included those using the BusinessObjects Enterprise XI platform.

If you want to use Single Sign On between EPM applications installed with the same BusinessObjects Enterprise platform, select Activate SSO for Web EPM Suite. When you select this option, a session will be kept open on the CMS during the entire Financial Consolidation session for each Financial Consolidation user. Therefore, you must make sure that your Business Objects Enterprise XI license is for a sufficient number of users.

CautionThe following authentication modes are no longer supported by SAP Financial Consolidation. The only reason they are avalaible is to ensure compatibility with previous versions. You must always use the Business Objects Enterprise authentication, unless you are migrating from a previous SAP Financial Consolidation version, and your authentication mode must remain the same.

● Active Directory / LDAP authentication● LDAP authentication● Script authentication● Plug-in authentication

CautionIf you want to use the LDAP or Active Directory authentication, you must do it into the BusinessObjects Enterprise XI Central Management Console. Additional authentication modes like SAP NetWeaver are also supported through the BOE XI platform.

NoteIf your BOE platform uses a CMS cluster, then you need to indicate, in the CMS server name field, all the cluster members, one by one, separated by a coma.

5.1.2.2.2 Internal Authentication Configuration String

This parameter authorizes the application to manage login and passwords internally.

The internal authentication mode is no longer supported, it is avalaible just to help you initialize a database. Once the database is initialized, you should always use the BOE authentication.

It can take on the following values:

● Internal authentication if you authorize the authentication to be performed directly in SAP Financial Consolidation.


● Deactivated if you only want to use an external authentication, e.g. the BusinessObjects XI platform or LDAP. To find out more, see External Authentication Configuration String [page 42].

5.1.2.2.3 Database Connection String

You can modify the database configuration when editing the Database connection string parameter.

This parameter specifies the information for connecting to the database. It can take on different values, depending on the type of connection to the database used.

CautionYou can use one of the OLEDB providers described below to connect to the database.

● SQLOLEDB● OraOLEDB● SQLNCLI● SQLNCLI10● SQLNCLI11

NotePlease note that you must fill in the login and password for connecting to the database.

When you select one of these OLEDB providers, you must then complete the syntax with information specific to your SAP Financial Consolidation environment, e.g. server and database names, logins and passwords. You can also complete the extra-parameter field for a specific syntax. In this case, only this field is taken into account and you must leave all other fields blank.

Following are several examples of OleDB syntax:

NoteIn all following examples, the connection to the SQL Server database is made with the CtServer.exe application Windows user (the DCOM account entered during the setup). This Windows user must be the database owner (dbo) of your Financial Consolidation SQL Server database.

● Oracle RAC:In Extra parameters, enter the following string: "FEN=T;FRC=5;FDL=5"

● SQL 2008 trusted connection:In Extra parameters, enter the following string: "Provider=SQLNCLI10;Server=myServerAddress;Database=myDataBase; Trusted_Connection=yes;"

● SQL 2008 encrypt data sent over the network:In Extra paramaters, enter the following string: "SQLNCLI10;Server=myServerAddress;Database=myDataBase; Trusted_Connection=yes;Encrypt=yes;

● SQL 2012 trusted connection:In Extra parameters, enter the following string:



"Provider=SQLNCLI11;Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;"

● SQL 2012 encrypt data sent over the network:In Extra paramaters, enter the following string: "SQLNCLI11;Server=myServerAddress;Database=myDataBase; Trusted_Connection=yes;Encrypt=yes;

● HANA with schema different from connected user:When you want to connect to a HANA schema different from the HANA login used in the data source, in Extra parameters, enter the following string: CS=”[SCHEMA_NAME]”.[SCHEMA_NAME] is the name of the schema where the Financial Consolidation tables are.

5.1.2.2.4 Scheduler Computer Name

In a multi-server configuration, this parameter is used to specify the application server on which tasks scheduled in the SAP Financial Consolidation Task Scheduler view will be performed. If you run a task scheduled for immediate execution, the properties defined in the parameter will not be taken into account. Tasks that have been scheduled for immediate execution will be run on the application server to which you are connected.

NoteThis computer must be one of the servers you configured for the data source.

CautionYou cannot enter "localhost" for this parameter; instead, you must specify the name of the server. This parameter is case-sensitive.

5.2 Installing the SAP Financial Consolidation Application Server

Prerequisites

Before installing, you must use a valid Windows domain account with a password that never expires. This account must be part of the DCOM user group.

You must have write access rights on the following folders:

● the SAP Financial Consolidation installation folder● folders where the logs are stored

NoteThe built-in system account can not be used.


NoteIf you want to print manual journal entries and controls on Windows Server 2012 and Windows Server 2012 R2, you must install the following: Microsoft Fix It Solution on your application server (http://%20support.microsoft.com/kb/2954953 )

RememberAs SAP Financial Consolidation 10.1 now uses a new setup technology, you are not prompted to uninstall earlier versions of SAP Financial Consolidation but you need to manually uninstall all previous versions via the Windows Control Panel before you can install SAP Financial Consolidation 10.1.


Context


NoteThe SAP BusinessObjects User Management Client component is automatically installed by the setup in C:\Program Files\SAP BusinessObjects. However, if you want to install it in another folder, you can manually execute the UMC.exe setup located in the UMC_101_INSTALLER folder.

Procedure

1. Connect to the server with an administrator account.

NoteIf you carry out an installation using the "Remote Desktop Connection" tool, you are required to do this with the "Console" (mstsc /admin) session. Otherwise, SAP Financial Consolidation may not work properly.





http://help.sap.com/disclaimer?site=http://%20support.microsoft.com/kb/2954953

http://help.sap.com/disclaimer?site=http://%20support.microsoft.com/kb/2954953







click Next.







12. Click Next.



Once the installation is complete, the Installation complete dialog box opens.14. Click Finish.15. Open the Environment Variables and add to the "Path" variable the address of the BusinessObjects Enterprise

XI 4 platform or the SAP BusinessObjects Information Platform Services 4.0. For example : C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86.

16. Restart the server.


NoteIf your environment is made up of different domains or some computers are outside of the domain, you must follow the instructions provided in the Security Guide's chapter "DCOM configuration".

By default, the DCOM Authentication Level is now set to the maximum security mode (Packet Privacy) and therefore only works for domain users.

5.2.1 Installing ActivePDFServer (optional)

Context

SAP Financial Consolidation 10.1 no longer uses by default the ActivePDFServer to generate PDF documents when printing from the Web client but now internally generates PDF documents. However, a registry option has been added to disable the new print feature and continue to use ActivePDF to generate PDF documents.

If you want to use ActivePDFServer to generate PDF documents with SAP Financial Consolidation, you must follow the procedure below:

CautionActivePDFServer must be installed on each Financial Consolidation application server composing your environment.



NoteYou will need to register the ActivePDF Server license on the Internet during the installation. Therefore, your server must have web access.

NoteYou must uninstall the old version then reinstall the new one, rather than upgrade directly from the new version.

Procedure

1. Purchase a license from ActivePDFServer.

NoteActivePDFServer is not included in the SAP Financial Consolidation package.

2. Execute the apsrvr.exe file and install ActivePDF Server as indicated during the setup.3. Create the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cartesis

\Magnitude\PrintPDF]4. Create a new DWORD (32-bit) Value: "WebPDFMode"=dword:00000001. The values can be:

○ 0 = Use ActivePDF (Use ActivePDF Server if it is installed)○ 1 = Use new PDF generator

NoteIf no value has been set, the application will use by default the new PDF generator.

NoteWe recommend that you restart the server.

Tip

When the server has been restarted, you can check that ActivePDF works properly by selecting StartPrograms ActivePDF Server Test Utility .

Next Steps

The new registry hive is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cartesis\Magnitude\PrintPDF]


New Registry entries:

"WebPDFMode"=dword:00000001

The values can be:

0 = Use ActivePDF (Use ActivePDF Print server if installed)

1 = Use new PDF generator

Entry not present in registry has same effect as WebPDFMode = 1

5.2.2 Configuring Disclosure Management for HTTPS Protocol

To connect to Disclosure Management using the HTTPS protocol, you must do the following:

● Retrieve the client certificate based on the server certificate deployed on the Disclosure Management web application.

● On each machine hosting the Financial Consolidation server (CtServer component), install the client certificate in the Local Computer > Trusted Root Certification Authorities folder.

CautionYou must install the client certificate on each application server in your environment.

5.2.3 Initializing the Database

Once you have installed a new version of SAP Financial Consolidation and configured the data sources, you must initialize the database before you connect to SAP Financial Consolidation.

CautionIf you already have a database in an older version of Financial Consolidation, refer to the SAP Financial Consolidation Upgrade Guide.

There are two types of SAP Financial Consolidation databases:

● Databases used by the setup sites (Top databases)● Databases used by the operation sites (child databases)

Top databases are used to customize the setup while child databases can only be used for operating purposes. The databases used at local data entry sites (on standalones) are child databases.

NoteBy default, SAP Financial Consolidation initializes empty databases as child databases, because this constitutes the majority of the databases that are installed.

You define whether the SAP Financial Consolidation database will be a Top or child database when you initialize it. During the initialization process, SAP Financial Consolidation will adapt the structure of the database depending



on whether it is a Top or child database. Once you have created a BusinessObjects Finance database, you cannot change its type.

5.2.3.1 Defining the Database Languages

Context

An SAP Financial Consolidation database can store text in 5 different languages. By default, these languages are French, English, German, Spanish and Japanese. It is possible to define the list of languages supported from 18 different ones.

You can define these languages only when initializing a new empty database. If the database already exists, it is not possible to change the list of languages available.

NoteIf you change the default list of languages, all your database have to use the same list (Top and Child databases must use the same list)

To define the database languages:

Procedure

1. Open the defaultlanguages.xml file located in the SAP Financial Consolidation installation folder.

<?xml version="1.0" encoding="utf-8" ?><setup xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns="http://schemas.sap.com/2008/04/29/Finance"> <lang1>fr</lang1> <lang2>en</lang2> <lang3>de</lang3> <lang4>es</lang4> <lang5>ja</lang5><site>child</site></setup>

2. Enter the code of the languages you want to set into your database. The list of available languages is:

Language Code

English en

French fr

German de

Japanese ja

Spanish es

Chinese simplified zh-CHS


Language Code

Italian it

Dutch nl

Russian ru

Korean ko

Portuguese Brazil pt

Swedish sv

Polish pl

Norwegian Bokmal nb-NO

Danish da

Finnish fi

Turkish tr

Lithuanian lt

3. Save and close the file.

Cautionif you use a starter kit, the list of languages is, by default, the following: en, de, fr, es, ja.

5.2.3.2 Defining a Top or Child Database

Context

If you want the SAP Financial Consolidation database to be defined as a Top database, you should run an executable on the application server. This script will change the SQL files used by SAP Financial Consolidation to initialize the database.

CautionThere can only be one TOP database in a group.

CautionPlease note that this executable must be run on the application server BEFORE the database is migrated via the Administration console.

To define the database as a Top database:



Procedure

1. Edit the defaultlanguages.xml file located at the root of the installation folder of the application.

<?xml version="1.0" encoding="utf-8" ?> <setup xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns="http://schemas.sap.com/2008/04/29/Finance"> <lang1>fr</lang1> <lang2>en</lang2> <lang3>de</lang3> <lang4>es</lang4> <lang5>ja</lang5> <site>top</site> </setup>

2. Complete the XML file with the languages you want to define into your database.3. In the site parameter, indicate the type of site you want to define: top or child.

4. Save and close the file.5. Open a DOS prompt command and enter the following command: “DatabasePreInitialization.exe

defaultlanguages.xml”.

5.2.3.3 Initializing the Database

If the database is empty, you should first create the structure of the SAP Financial Consolidation database. To do this, you use the Migrate command in the Administration console to initialize the database from its present version 0.0.0.0.

If the database is not empty, i.e if you are migrating from a previous version, see the SAP Financial Consolidation Upgrade Guide.

5.2.3.4 Starting and Stopping Data Sources

Context

Once the database has been initialized following installation and the data source has been configured, you must start the data source before connecting to SAP Financial Consolidation.

Procedure

1. Connect to the Administration Console web site you deployed in the previous chapter. For example, http://localhost/WebAdmin.

Click the data source you want to start.


2. Select the Data sources options menu and click Start data source or Stop stop data source.

5.2.4 Connecting to SAP Financial Consolidation

Context

Once SAP Financial Consolidation is installed on the client computer, you can connect to the application.

NoteDo not forget to install Adobe Flash Player in order to be able to use the dashboard.

Procedure

1. Select Start All Programs SAP Financial Consolidation



TipYou can also double-click the Finance.exe file.

The User Identification dialog box opens.

NoteIf the Data source groupbox is not displayed, click Options.

2. In the Data source groupbox, click the Local or Remote option to select the computer on which the data source manager is located, which will then provide the list of available SAP Financial Consolidation data sources.

3. In the Data source name list, select the data source you want to use.4. Specify the authentication information, along with the SAP Financial Consolidation user name and password,

or select the Use Windows account option.

NoteIf you do not know your username or password, please contact your system administrator.

5. Click OK.


5.3 Installing the SAP Financial Consolidation Web Servers

You install SAP Financial Consolidation web servers in five steps:

● Install the SAP Financial Consolidation Web components on the web server.

CautionIf you are installing SAP Financial Consolidation on Microsoft Windows 7, Microsoft Windows Server 2008 or 2008 R2, you must install the following corresponding updates to prevent security issues: https://support.microsoft.com/en-us/kb/2533623 .

● Configure the 4.5.1 .NET framework.● Deploy the SAP Financial Consolidation web sites in IIS.● Create the corresponding ASP.NET application in IIS.● Configure SAP Financial Consolidation web in the Administration console.

5.3.1 Installing the Financial Consolidation Web site Components

Prerequisites

Before installing, you must use a valid Windows domain account with a password that never expires. This account must be part of the DCOM user group.

Context


NoteIf IIS is located on a different computer than your SAP Financial Consolidation application server, you must install SAP Financial Consolidation Web before deploying the site.





Procedure




2. Click Run.





click Next.







○ Financial Consolidation Web Administration: This option enables you to access the tool used for managing the data sources.

○ Financial Consolidation Web site: This option installs all of the components required for running SAP Financial Consolidation Web.

○ Financial Consolidation Web Html5 site: This option installs all of the components required for running the new SAP Financial Consolidation Web Html 5 site.

12. Click Next.



Once the installation is complete, the Installation complete dialog box opens.14. Click Finish.15. Open the Environment Variables and add to the "Path" variable the address of the BusinessObjects Enterprise

XI 4 platform or the SAP BusinessObjects Information Platform Services 4.0. For example : C:\Program Files\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86.



16. Restart the machine.


5.3.2 Deploying the SAP Financial Consolidation Web site under Windows Server

Procedure

1. Create an application pool with its relevant parameters, described in the Application Pools Options under Windows Server [page 27] chapter.


2. In the SAP Financial Consolidation installation folder, copy the Web subfolder.3. Paste this subfolder to \Inetpub\wwwroot\.4. Change the subfolder's name to the name you want to assign to your website (for example, in this

documentation, FCWeb).

CautionThe name of your site must not contain the _ (underscore) character.

5. Open the IIS Manager.6. Right-click on the folder you pasted at step 3 and click Convert to Application.

The Add Application dialog box opens.7. In the Application Pool field, select the Application Pool you defined at step 1 for the SAP Financial

Consolidation web site and click OK.Click the Test Settings button if you want to test the deployment.

8. Click OK.9. Select the new site you deployed and double-click the Authentication icon.10. Right-click on Anonymous authentication and click Edit.

The Edit Anonymous Authentication Credentials dialog box opens.11. Click the Specific user option and click Set to enter a user account with the following rights:

○ Use the DCOM protocol,○ Have read/write access to the Financial Consolidation installation folders,○ Have read/write access to the Financial Consolidation Web site deployment folder,○ Be part of the local IIS_WPG group,○ Be part of the same domain unless you do not want to apply DCOM encryption.


12. Select the new site you deployed and double-click the HTTP Response Headers icon.13. In the Actions pane, click Set Common Headers.

The Set Common HTTP Response Headers dialog box opens.14. Select the Enable HTTP keep-alive and Expire Web content after options and set the Expire Web content after 1

day.15. Click OK.16. Select the new site you deployed and double-click the Handler Mappings icon.17. In the Actions pane, click Add Script Map.

The following dialog box opens.

18. In the Request Path field, enter the *.xls extension.19. In the Executable field, select the C:\WINDOWS\Microsoft.NET

\Framework64\v4.0.30319\aspnet_isapi.dll file.

20.Enter a name and click Request Restrictions.21. In the Mapping tab, do not select anything.22. In the Verbs tab, select the One of the following verbs option, and enter POST.



23. In the Access tab, select the Script option.24.Click OK.

The Add Script Map message appears, asking you if you want to allow this ISAPI extension.25. Click Yes.26.Select the new site you deployed and double-click the MIME Types icon.

The MIME Type window opens.27. In the Actions pane, click Add.

The Add MIME Type dialog box opens.28.In the file name extension field, add the .xls extension.29.In the MIME type field, enter the following: application/vnd.ms-excel.

30.Click OK.31. Repeat the same operation for the following file extensions:

File extension MIME Type

.xls application/vnd.ms-excel

.xll application/vnd.ms-excel

.xlam application/vnd.ms-excel

.ini text/plain

CautionSAP Financial Consolidation Excel Web Schedules will not work properly if you do not select these configuration options.


32. If you want to force users to connect the Administration Console Web Site using HTTPS mode, open the web.config file located in the Financial Consolidation web site deployment folder and add the "UseHTTPS" parameter and set its value to true as indicated below.

<add key="UseHTTPS" value="true"/>

5.3.2.1 Adding the Financial Consolidation Web site to the Administration Console

Prerequisites

This setting displays the URL of the HTTP server on which SAP Financial Consolidation is deployed. The Administration console uses this URL to stop and start the SAP Financial Consolidation Web server. If you deployed the application in IIS and defined /FCWebsite as the application URL, then the URL displayed here will be http://myWebServer/FCWebsite. If you do not have a Web configuration, then you should leave this parameter empty.

NoteIf this setting is filled in, then when you start SAP Financial Consolidation, the web application will also start automatically.

In the case of an architecture with multiple HTTP servers, you can specify several SAP Financial Consolidation Web URLs. If you do so, the WebServerURL parameter will display the "multi-servers" value.

Procedure

1. Connect to the Administration Console web site you deployed in the previous chapter. For example, http://localhost/FCWebsite.

2. Stop the datasource if it is running.3. Click Servers > Server options.4. Click Add a new web server.5. In the Add a new web server dialog box, enter the URL of this web server. For example, http://myWebServer/

FCWebsite.6. Click the Test button to test the URL.



5.3.3 Deploying the SAP Financial Consolidation Web HTML5 site under Windows Server

Context

In addition, it is possible to activate HTTP compression for this new site.

Procedure

1. Create an application pool with its relevant parameters, described in the Application Pools Options under Windows Server [page 27] chapter.


2. In the SAP Financial Consolidation installation folder, copy the WebHTML5 subfolder.3. Paste this subfolder to \Inetpub\wwwroot\.4. Change the subfolder's name to the name you want to assign to your website (for example, in this

documentation, FCWebHTML5).

CautionThe name of your site must not contain the _ (underscore) character.

5. Open the IIS Manager.6. Right-click on the folder you pasted at step 3 and click Convert to Application.

The Add Application dialog box opens.7. In the Application Pool field, select the Application Pool you defined at step 1 for the SAP Financial

Consolidation HTML5 web site and click OK.Click the Test Settings button if you want to test the deployment.

8. Click OK.9. Select the new site you deployed and double-click the Authentication icon.10. Right-click on Anonymous authentication and click Edit.

The Edit Anonymous Authentication Credentials dialog box opens.11. Click the Specific user option and click Set to enter a user account with the following rights:

○ Use the DCOM protocol,○ Have read/write access to the Financial Consolidation installation folders,○ Have read/write access to the Financial Consolidation Web site deployment folder,○ Be part of the local IIS_WPG group,○ Be part of the same domain unless you do not want to apply DCOM encryption.

12. If you want to activate Single Sign On with Windows Authentication mode, right-click on Windows Authenticationand select Enable.


13. Double-click the Compression icon.14. Check the Enable dynamic content compression box.15. Check the Enable static content compression box.16. Click Apply.17. Select the new site you deployed and double-click the HTTP Response Headers icon.18. In the Actions pane, click Set Common Headers.

The Set Common HTTP Response Headers dialog box opens.19. Select the Enable HTTP keep-alive and Expire Web content after options and set the Expire Web content after 1

day.20.Click OK.21. Select the new site you deployed and double-click the MIME Types icon.

The MIME Type window opens.22. In the Actions pane, click Add.

The Add MIME Type dialog box opens.23. In the file name extension field, add the .json extension.24.In the MIME type field, enter the following: application/json.

25. Click OK.26.Repeat the same operation for the following file extensions:

File extension MIME Type

.json application/json

.properties application/octet-stream

5.3.3.1 Connecting the Financial Consolidation Web HTML5 site to a Financial Consolidation data source

Procedure

1. Connect to the Administration Console web site you deployed in the previous chapter. For example, http://myWebServer/FCWebHTML5.

2. Stop the datasource if it is running.

3. Click Servers Server options .4. Click Add a new web server.5. In the Add a new web server dialog box, enter the URL of this web server. For example, http://myWebServer/

FCWebHTML5.6. Click the Test button to test the URL.7. Open the IIS Manager.8. Select the new site you deployed and double-click the Application Settings icon.



9. Edit the BrokerHostName parameter and enter the name of the server where the CtBroker component is installed.

10. In order to enable the BusinessObjects Enterprise SSO with the new HTML5 web site, edit the CMS parameter in the web.config file located in the Financial Consolidation application deployment folder:

 <add key="CMS" value="dewdfwssp4145.dhcp.wdf.sap.corp"/>

The value is the name of the machine hosting the CMS.11. Enter the name of the Central Management Server (CMS) of your BusinessObjects XI 4 platform.12. Edit the DataSourceName parameter and enter the name of the Financial Consolidation data source.13. Edit the ForceHttps parameter and set it to false if you do not use SSL encryption or if you plan not to use

SSL encryption with IIS (for example on a separate device such as reverse proxy).

CautionIt is strongly recommended to use the HTTPS mode in a production environment.

14. Edit the web.config file located in the SAP Financial Consolidation application deployment folder and add or edit the LegacyWebURL parameter and enter the URL of the legacy web site that you want to display in the HTML5 web site home page.

 <add key="LegacyWebURL" value="http://myServer/Legacy_web_URL"/> 15. If you want to use the Single Sign On mode with your BusinessObjects Enterprise platform, you must edit or

create the CMS parameter and enter the name of your BusinessObjects Enterprise server.16. Edit or create the AutoLogoutTimeout parameter. This parameter allows you to automatically disconnect

users after a certain period of time. You can set it to 300 minutes or change it to 0 if you want to deactivate it.

5.3.3.2 Defining automatic logout timeout for Financial Consolidation Web HTML5 site

Context

Users are automatically disconnected from the Financial Consolidation Web HTML5 site if there is no activity for a given period of time.

By default, the value is set to 300 minutes, but you can change it as you want.


Procedure

1. Open the IIS Manager.2. Select the new site you deployed and double-click Application Settings.3. Edit the AutoLogoutTimeout parameter and enter the number of minutes you want before disconnecting

inactive users.

5.3.3.3 Defining the number of packages displayed by default

Context

When opening a package in the Financial Consolidation Web HTML5 site, the package list view displays the 50 first packages found by default. To display more packages, you can click the More button.

You can change this default value.

Procedure

1. Open the IIS Manager.2. Select the new site you deployed and double-click Application Settings.3. Edit the PackagesPerCall parameter and enter the number of packages you want to display by default.

NoteThere is no maximum limit to the number of packages to display by default.



5.3.3.4 Configuring a Reverse Proxy for the Financial Consolidation Web HTML5 site

If you want to publish the Financial Consolidation Web HTML5 site via a reverse proxy, you need to perform the following configuration.

Context

CautionThis configuration applies only to the Financial Consolidation Web HTML5 site.

Procedure

1. Open the web.config file located in the SAP Financial Consolidation application deployment folder. For example: \Inetpub\wwwroot\FCWebHTML5Site.

2. Search for the following rows:

<authentication mode="Windows"> <forms loginUrl="~/login" defaultUrl="~/index"></forms> </authentication>

3. Replace the "~" caracter with the URL of your web site published on the reverse proxy. If your reverse proxy URL is: http//ReverseProxy.myserver.com/FCWebHtml5, then you must configure the web.config file as follows:

<authentication mode="Windows"> <forms loginUrl="http//ReverseProxy.myserver.com/FCWebHtml5/login"defaultUrl="http//ReverseProxy.myserver.com/FCWebHtml5/index"></forms> </authentication>

4. Save the web.config file.

5.3.4 Activating the SSL Protocol on the User Management Client

Context

If you use the BusinessObjects Enterprise XI 4 platform or the SAP BusinessObjects Information Platform Services 4.0 with the SSL protocol, you must configure the User Management Client component to use the appropriate SSL certificate on the Financial Consolidation application servers.


Procedure

1. Copy the public key files of your SSL certificate on the application server.2. open a DOS command prompt and go to the folder where the User Management Client is installed: C:

\Program Files (x86)\SAP BusinessObjects\SAP User Management Client XI 4.0\SAP BusinessObjects Enterprise XI 4.0\win32_x86.

3. Execute the following command: sslconfig.exe -dir C:\SSLCert -mycert clientcert.der -rootcert cacert.der -mykey client.key -passphrase passphrase.txt -protocol ssl.

These parameters correspond to the following:

Option Description

C:\SSLCert Folder containing the public key of the certificate

Clientcert.der Client SSL Certificate file

cacert.der SSL Trusted Certificates Files

Client.key SSL public key file

Private Key Passphrase File - passphrase.txt SSL public key passphrase file

5.4 System Landscape Directory Configuration

Prerequisites

CautionYou must configure SLD information only if you have installed the SAP System Landscape Directory Solution in your environment. Installing SLD is not mandatory.

Context

Once the Financial Consolidation server components are installed, you must perform the following:

Procedure

1. click Start All Programs SAP Financial Consolidation System Landscape Directory Configuration .2. In the Hostname field, enter the complete URL of the server location, followed by the port number. For

example: http://ldcist7.wdf.sap.corp:58900/sld/ds.

3. Enter your Username, the SID (system ID) of the SLD solution, your Password and click OK.



5.5 Installing and configuring the SAP Financial Consolidation Web Services

You install the SAP Financial Consolidation Web Services in five steps:

● Install the SAP Financial Consolidation Web Services on the web server.● Configure the 4.5.1 .NET framework.● Deploy the SAP Financial Consolidation Web Services in IIS.● Create the corresponding ASP.NET application in IIS.● Configure the SAP Financial Consolidation Web Services in the Administration console.

5.5.1 Deploying the SAP Financial Consolidation Web Services under Windows Server

Procedure

1. Open the IIS Manager.2. Right-click the Default Web Site.3. Create an application pool with its relevant parameters, described in the Application Pools Options under

Windows Server [page 27] chapter.


4. In the SAP Financial Consolidation installation folder, copy the WebServices subfolder.5. Paste this subfolder to \Inetpub\wwwroot\.6. You can rename this folder to reflect the URL that you want to display.

NoteYou can deploy the WebServices site in a folder other than the default wwwroot folder. To do so, create a virtual folder in IIS that points to the folder that you use.

7. In the web.config file, search for the following rows:

<appSettings> <add key="Log4NetInitFile" value="~/WS-LogConfig.xml" /> <add key="BrokerHostName" value="BrokerServerName" /> <add key="DataSource" value="DataSourceName" /> <add key="DefaultLogin" value="Login" /> <add key="DefaultPassword" value="Password" /> </appSettings> 8. Change these rows by entering the values that correspond to your SAP Financial Consolidation environment.


NoteEnter a login and password corresponding to an SAP Financial Consolidation user who needs no specific rights. You can therefore create a user dedicated to these Web Services that does not have any rights.

9. Save your changes.10. In the IIS Manager, right-click on the folder you pasted at step 4 and click Convert To application in order to

deploy the web site.11. Once the application is created, click on it and open the Authentication feature.

Select the Anonymous Authentication line and edit it.12. In the Edit Anonymous Authentication Credentials, select the IUSR user and click OK.13. Right-click on Anonymous Authentication and select Enable.

5.5.2 Encrypting the settings of the web.config file (optional)

Context

To enhance security, you can encrypt the login and password given in the web.config file using the method recommended by Microsoft for ASP.NET applications.

Procedure

1. Download the aspnet_setreg.exe tool available at the following Microsoft URL:http://support.microsoft.com/kb/329290/en .

2. Run the following command: aspnet_setreg.exe -k:SOFTWARE\Cartesis\Cartesis Finance\WebServices -u:"my_domainname\my_username" -p:"my_password"

NoteThe registry key name given here can have a different value from WebServices, especially when you want to deploy several applications.

NoteThis command generates a key in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cartesis.

3. Copy this key from HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cartesis\Cartesis Finance\WebServices and paste it into HKEY_LOCAL_MACHINE\SOFTWARE\Cartesis\Cartesis Finance\WebServices.

4. Edit the web.config file and look for the following rows:

<add key="DefaultLogin" value="my_user" /> <add key="DefaultPassword" value="my_password" />



http://help.sap.com/disclaimer?site=http://download.microsoft.com/download/2/9/8/29829651-e0f0-412e-92d0-e79da46fd7a5/aspnet_setreg.exe

http://help.sap.com/disclaimer?site=http://download.microsoft.com/download/2/9/8/29829651-e0f0-412e-92d0-e79da46fd7a5/aspnet_setreg.exe

Change these rows as shown above:

<add key="DefaultLogin" value="registry:HKLM\SOFTWARE\Cartesis\Cartesis Finance\ WebServices\ASPNET_SETREG,username" /><add key="DefaultPassword" value="registry:HKLM\SOFTWARE\Cartesis\ Cartesis Finance\WebServices\ASPNET_SETREG,password" />

5. Next, you must authorize the account that runs the .NET framework to access these new registry keys.6. Run the regedit32.exe command in the Start > Run menu and click on OK.

7. Select the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Cartesis\Cartesis Finance\WebServices\ASPNET_SETREG and right-click Permissions.

8. Click on Add and select the account that runs the web services application pool and assign the Read permission to this account.

9. Repeat steps 7 and 8 for HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cartesis\WebServices\ASPNET_SETREG.

10. Close the registry editor.

NoteTo find out more, please see the official Microsoft documentation at the following address: http://support.microsoft.com/kb/329290/en-us

5.5.3 Deleting the SAP Financial Consolidation Web Services website

Procedure

1. In the IIS administration console, select the folder containing the site that you want to delete.2. Right-click on the folder and select Properties.

The website Properties window appears.3. In the Directory tab, click on Remove.4. Click OK.5. Then delete the corresponding folder in \Inetpub\wwwroot\.


http://help.sap.com/disclaimer?site=http://support.microsoft.com/default.aspx?scid=kb;en-us;329290#5

http://help.sap.com/disclaimer?site=http://support.microsoft.com/default.aspx?scid=kb;en-us;329290#5

5.5.4 Testing the SAP Financial Consolidation Web Services deployment

Context

NoteThis procedure must be carried out on the computer on which the SAP Financial Consolidation Web services are deployed. For security reasons, this test cannot be carried out on other computers.

Procedure

1. Make sure that the SAP Financial Consolidation data source is started.2. Start Internet Explorer and enter the URL for connecting to the SAP Financial Consolidation Web Services

that you deployed. In this documentation, this is the application called WebServices. The URL is therefore: http://localhost[:IIS_port_number]/WebServices/security/AuthenticationServices.asmx

3. Click the Authenticate link.

The WSAuthenticationServices page opens.



4. In the User and Password fields, enter the login and password for connecting to SAP Financial Consolidation.5. Click Invoke.

If the application has been correctly deployed, the following message appears: userAuthenticated.

If this message does not appear, check that:

○ The SAP Financial Consolidation Web Services application exists and has been correctly deployed.○ The SAP Financial Consolidation Web Services application is connected to a valid data source.○ The SAP Financial Consolidation data source is started and is operating correctly.○ Anonymous connection is authorized in IIS for the SAP Financial Consolidation WebServices site.


6 Installing the SAP Financial Consolidation Starter Kits

Context

The Starter Kits for IFRS or Banking consist of a pre-configured set of resources for SAP Financial Consolidation. These pre-configured resources include: reports, controls and rules for performing, validating and publishing a statutory consolidation in accordance with IFRS or Banking standards.

The SAP Financial Consolidation setup contains the latest version of the Starter Kits sand automatically copies it into the application installation folder.

You can install the Starter Kits via a command available in the Administration Console of the SAP Financial Consolidation application.

This command performs the following main steps:

● Extracts the Starter Kits files.● Transfers the features to install or update the Starter Kits into the specified data source.● Stores the version information about the Starter Kits.

CautionIf you are installing the Starter Kits for the first time, you must install it in a dedicated empty database, before running the installation. If you are upgrading, you must migrate the data source before upgrading it.

NoteIf the setup detects that a Starter Kit is already installed, you cannot install it a second time on the same data source. The following error message appears: "This version of the software configuration has already been installed".

To install a Starter Kit, perform the following steps:

Procedure

1. Open the Administration Console.2. Select the data source on which you want to install a Starter Kit, and then migrate the data source using the

Migrate datasource command from the Data source options menu.

TipIt is recommended that you always migrate the data source before performing the installation.

3. Once the data source is migrated, if it is still running, stop it using the Stop datasource command from the Data source options menu.


Installing the SAP Financial Consolidation Starter Kits

NoteYou cannot install the Starter Kit if the data source has not been stopped.

4. Select the Operation node of the data source, and then in the Data source options menu, click one of the following options:

○ Install Software Configuration for IFRS○ Install Software Configuration for Banking

A message appears prompting you to confirm that you want to perform this operation.5. Click OK.

NoteThe user account used to install the Starter Kit is the Financial Consolidation Admin account.

You can see that the installation is running via the icon that appears next to the data source name:

.

Once the installation is finished, the following message appears: "Installation of the software configuration succeeded on data source XX".

6. Click Close to exit the message.7. Restart the data source.

Tip

To see which version of the Starter Kit you are using, choose Help About Financial Consolidationwindow.

SAP BusinessObjects Financial Consolidation Installation GuideInstalling the SAP Financial Consolidation Starter Kits C U S T O M E R 75

For more information about working with the Starter Kit, see the SAP Library – Starter kit for IFRS, on the SAP Help Portal: http://help.sap.com/bofincon.


Installing the SAP Financial Consolidation Starter Kits

http://help.sap.com/bofincon

7 Installing Financial Consolidation Cube Designer Server Components

7.1 Installing the SAP Financial Consolidation Cube Deployer Server

Context

CautionYou do not need to install this component if you want to generate analytics views with SAP HANA.

Before installing the deployer server, the following components are mandatory:

● Microsoft SQL Server 2012 components:○ Microsoft SQL Server 2012 Native Client (x64)

● Microsoft SQL Server 2014 components:○ Microsoft SQL Server 2014 Analysis Services OLE DB provider (x64)○ Microsoft SQL Server 2014 CLR Types (x64)○ Microsoft SQL Server 2014 Shared Management Objects (x64)○ Microsoft SQL Server 2014 Analysis Services ADOMD.NET (x64)○ Microsoft SQL Server 2014 Analysis Management Objects (x64)

● Oracle client with the Oracle OLEDB Provider● Microsoft .Net Framework 4.5.1● Microsoft IIS with ASP.Net 4.0● Runtime Microsoft Visual C++ 10.0 CRT (x64)● Runtime Microsoft Visual C++ 12.0 CRT (x64)


SAP BusinessObjects Financial Consolidation Installation GuideInstalling Financial Consolidation Cube Designer Server Components C U S T O M E R 77


7.1.1 Running the SAP Financial Consolidation Cube Deployer setup

Context

CautionYou must run the SAP Financial Consolidation Cube Deployer setup with a Windows account that belongs to the same domain as the SSAS Server.

Procedure

1. Execute the Setup.exe file located in the SAP Financial Consolidation Cube Deployer folder.



2. Install the required components before continuing with the setup.3. In the Welcome dialog box, click Next.4. Select the I accept the terms in the license agreement option and click Next.5. Specify a User Name and your Organization and check the Anyone who uses this computer (all users) box.6. Click Next.



Installing Financial Consolidation Cube Designer Server Components

7. Enter the relevant information in the following fields:

○ Choose a web site: select the web site in which you want to deploy your Deployer application.○ Choose a URL Name: enter the name of the web site to be deployed. By default, it will be called

DeployerForFinance by the setup.○ Windows account used for Deployer web site: the Deployer web site runs on a Windows account that will

access SSAS.○ Windows account password used for Deployer web site: enter the corresponding password.

CautionThis Windows account must have Administrator rights on the SSAS instance and on the Deployer machine.

CautionThis Windows account must be part of the IIS_IUSRS users group and have a password that never expires.

8. Click Next.The System Landscape Directory Options dialog box opens.


9. Enter the relevant information concerning your System Landscape Directory and click Next.

NoteYou must fill in this dialog box only if you have installed the SAP System Landscape Directory Solution in your environment. Installing SLD is not mandatory.

10. In the Destination folder dialog box, select the folder in which you want to install the application and click Next.11. If the settings are correct, click Install.12. Once the installation is complete, click Finish.

Check that the Windows account entered during the setup has the Log on as batch job right. If this is not the case, follow the procedure below:

13. Excute secpol.msc.14. Select Local Policies > User Rights Assignment and double-click Log on as batch job to check the user rights.

Next Steps

If you installed the Deployer for Finance application under Windows Server and the IIS 6 Metabase Compatibility role service was not installed, Deployer application authentication must be manually configured to Anonymous Authentication.

In the IIS Manager, edit the Deployer for Finance web site properties, and enable the Anonymous Authentication option as indicated below:



7.2 Installing the SSAS Server

7.2.1 Installing Microsoft SQL Server

Prerequisites

Before executing the setup, you must add the Application Server role to your server. To do so, click Server Manager > Roles > Add Roles > Server Roles and select the Application Server option.

Procedure

1. Execute the Microsoft SQL Server setup.2. In the SQL Server Installation Center, click New SQL Server stand-alone installation or add features to an

existing installation.3. Once the Setup Support Rules has run, click OK.4. Enter your Product Key and click Next.5. Select the I accept the license terms and click Next.6. Click Install to install Setup Support files.

The System Configuration Check dialog box opens.7. In the Feature Selection dialog box, select the following options:


○ Analysis Services○ Business Intelligence Development Studio○ Client Tools Connectivity○ Management Tools - Basic○ Management Tools - Complete

8. In the Instance Configuration, select the Named instance option and enter the name you want to give to the instance. In this documentation, we will use FC_CUBE_DESIGNER.

TipIt is recommended to use a named instance.

9. Click Next twice.10. In the Server Configuration dialog box, click Use the same account for all SQL Server services and select NT

AUTHORITY / LOCAL SYSTEM ACCOUNT.11. In the Collation tab, Keep the default settings and click Next.12. In the Analysis Services Configuration dialog box, specify the users that have administration rights on SSAS

and specify the Data Directories.13. Click Next and continue the setup.



7.2.2 Installing SAP Financial Consolidation UDF for Security

Prerequisites

NoteYou must run the SAP Financial Consolidation UDF for Security setup with a Windows account that have write access to the msmdsrv.exe.config SSAS configuration file.


● Microsoft .Net Framework 4.5.1● Microsoft IIS with ASP.Net 4.0● Microsoft SQL Server 2014 Analysis Services ADOMD.NET (x64)● Microsoft SQL Server 2014 Analysis Management Objects (x64)● Microsoft SQL Server 2012 Native Client (x64)

CautionIf you are installing SAP Financial Consolidation on Microsoft Windows 7, Microsoft Windows Server 2008 or 2008 R2, you must install the following corresponding updates to prevent security issues: https://support.microsoft.com/en-us/kb/2533623 .

Procedure

1. Execute the Setup.exe file located in the SAP Financial Consolidation UDF for Security folder.




3. Click Next.4. In the License Agreement dialog box, select the I accept the terms in the license agreement option and click

Next.5. In the Customer Information dialog box, specify a User Name, your Organization and click Next.





6. In the Choose a web site field, select the web site name of the administration web service used by the Central Management Console.

7. Click Next.The System Landscape Directory Options dialog box opens.



8. Enter the relevant information concerning your System Landscape Directory and click Next.9. In the Destination Folder dialog box, select the folder in which you want to install the application and click

Next.10. In the Confirmation dialog box, click OK.

The Ready to Install the Program dialog box opens.11. If the settings are correct, click Install.12. Once the installation is complete, click Finish.

Next Steps

You must verify the following:

1. In the IIS Manager, select the CartesisAnalyticsUDFAdminService application pool.2. Open its Advanced settings and verify that the application pool identity is set to the Built-in-account

"ApplicationPoolIdentity".


3. Then select the CartesisAnalyticsUDFAdminService web site and open the Authentication feature.4. Verify that the Basic Authentication and the ASP.NET Impersonation options are set to Enabled.



7.2.3 Installing the Microsoft Datapump Component under Microsoft Windows Server

Prerequisites

CautionIt is strongly recommended to apply the latest available Service Pack of Microsoft SQL Server before installing the Datapump component.

7.2.3.1 Getting Binaries

Procedure

1. Copy the C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\bin\isapi directory.

TipThe MSSQL directory may also be named MSSQL.2 for example.

2. Paste it into the C:\inetpub\wwwroot\directory on your data pump server and rename it with the name you want to assign to your website: for example "datapump".

NoteIf the datapump is deployed in a directory other than wwwroot, check that both the network service user and the user that will be used for anonymous access have the read and run rights on this directory.


7.2.3.2 Creating an Application Pool

Procedure

1. Open the IIS Manager.2. Create an application pool with the following options:

3. Right-click the application pool and click Advanced Settings.The Adanced Settings dialog box opens.

4. Expand the Process Model section and in the Identity zone, select the NetworkService account.5. Click OK.

7.2.3.3 Creating the Datapump Application

Procedure

1. Open the IIS Manager.2. Right-click the Default Web Site and click Add Application.

The Add Application dialog box opens.3. Create an application with the following options:



CautionIf you do not want to deploy the datapump in the C:\inetpub\wwroot\datapump, create a virtual directory that points to the \datapump folder.

7.2.3.4 Configuring the Datapump Application

Procedure

1. Once the Datapump application is created, select it and in the IIS zone, open the Authentication feature.2. Enable the Anonymous Authentication.


3. Right-click the Anonymous Authentication and select Edit.The Edit Anonymous Credentials dialog box opens.

4. Select the Specific user option and click the Set button to set a Windows user with the following rights:

○ This user MUST have a password that never expires. For security reasons, SSAS does not allow empty passwords.

○ This user MUST be a user known and authenticated by the SSAS Server (in the same domain or a domain known).

○ This user must NOT have the local administration rights on the SSAS Server, SSAS instance or SSAS database. Otherwise, the UDFFor Security component will not function.

○ This user must have the Read & execute, List folder contents, and Read permissions on the C:\inetpub\wwroot\datapump folder.

5. Select the Datapump application again and in the IIS group, open the Handlers Mappings feature.6. In the Action pane, click Add Script Map and enter the following parameters:

7. Click Request Restrictions and in the Request Restrictions dialog box, select the Verbs tab.8. Select the All verbs option and click OK.9. Back to the Handlers Mapping list, enable this Script Map.



7.2.3.5 Selecting the target Analysis Services Server

Procedure

1. Open the msmdpump.ini file located in C:\Inetpub\wwwroot\datapump.

<ConfigurationSettings> <ServerName>server_name\SSAS_instance_name</ServerName> <SessionTimeout>3600</SessionTimeout><ConnectionPoolSize>100</ConnectionPoolSize><MinThreadPoolSize>0</MinThreadPoolSize><MaxThreadPoolSize>0</MaxThreadPoolSize><MaxThreadsPerClient>4</MaxThreadsPerClient></ConfigurationSettings> />

2. In the ServerName parameter, you need to specify the SSAS server name and the SSAS instance name. If you called your SSAS instance as indicated in this documentation, you should enter BOBJ. Example: VMDTSSAS\BOBJ.

CautionDo not indicate localhost but rather the complete server name.

NoteIf you have installed SSAS with the default instance (no named instance), just enter the server name.

7.2.4 Installing the Datapump on a Separate Server

Prerequisites

The following pre-requisites are mandatory:

● Both servers must be part of the same domain.● To install the datapump, you must use a Domain Windows account with the following rights:

○ This user MUST have a password that never expires. For security reasons, SSAS does not allow empty passwords.

○ This user MUST be a user known and authenticated by the SSAS Server (in the same domain or a domain known).

○ This user must NOT have the local administration rights on the SSAS Server, SSAS instance or SSAS database. Otherwise, the UDFFor Security component will not function.

○ This user must have the Read & execute, List folder contents, and Read permissions on the C:\inetpub\wwroot\datapump folder.


Context

CautionVerify the server on which the datapump is installed and the SSAS server are communicating. If you have a firewall, verify the security policy of the domain.

Before installing the datapump, the following components are mandatory:

● IIS (for Microsoft Windows Server)● .NET Framework 3.5 SP1

Then you need to install the following components:

Procedure

1. Go to the Microsoft Web site to download the appropriate feature pack, depending on your Operating System.2. Install the corresponding OLEDB provider, depending on your Microsoft SSAS version. For example, for

Microsoft SQL Server 2008: Microsoft SQL Server 2008 Analysis Services 10.0 OLE DB Provider (april 2009 10.00.2531.00 version minimum).

3. Then follow the procedure indicated in Installing the Microsoft Datapump Component under Microsoft Windows Server [page 87] to continue with the datapump installation.

7.3 Configuring Cube Designer Components for SSAS Cubes generated from an SAP HANA Database

If you want to generate SSAS Cubes on top of a SAP HANA database, you must perform the following additional configuration:

On the SSAS Server:

1. Install the SAP HANA 32-bit client.2. Then install the SAP HANA 64-bit client.3. Copy the saphana.xsl file attached in the 2387963 SAP Note into \Program Files\Microsoft SQL

Server\MSAS11.MSSQLSERVER\OLAP\bin\Cartridges.

On the Cube Deployer server:

1. Install the SAP HANA 64-bit client.2. Create an Environment Variable named HDBCLIENT_64 (in the variable name field) and add to this variable

the path to the SAP HANA 64-bit client installation folder (variable value = C:\Program Files\SAP\hdbclient).



On the Cube Designer client component:

1. Install the SAP HANA 32-bit client.2. Open the Cartesis.InformationDelivery.Workbench.exe.config file located in \Program Files (x86)\SAP

\Financial Consolidation\Cube Designer, and add the <add key="EnableSSASCubesFromHanaDB" value="True" /> parameter in the <appsettings> section.

7.4 Installing and Configuring the NetWeaver BW Server to deploy Infocubes with SAP Financial Consolidation Cube Designer

If you want to deploy and generate NetWeaver BW cubes with with SAP Financial Consolidation Cube Designer, the following installation and configuration steps are required on the NetWeaver BW platform:

1. Install the FPM Basis component on the NetWeaver BW server.2. Create BW NetWeaver roles that allow to deploy Infocubes with the Cube Designer application.

7.4.1 Installing FPM Basis on the NetWeaver BW Server

Context

To install the FPM Basis component on the NetWeaver BW platform, the following configuration steps are required:

Procedure

1. In transaction RSA1 of the BW System, open the Global Settings menu.2. Select the Pack.Mas.Data Del option.


3. Implement the SAP Note number 1437880.4. If your version of SAP NetWeaver BW is prior to SAP_BW Release 701 SP5, you must implement the SAP Note

number 1312139.5. If your version of SAP NetWeaver BW is the SAP_BW Release 7.30 version, you must implement the SAP Note

number 1561043.6. Install the FPMBASIS 2.0 component, which must be deployed into the NetWeaver platform, following the

standard deployment procedure.

NoteFor more information, connect to the SAP Service Marketplace (SMP) and search for SAP note number 1515669.

7. Go to SMP, download and install the .SAR file named SAPK-20002INFPMBASIS.8. Depending on your database, install the following:

○ If the SAP Financial Consolidation database is a Microsoft SQL database, install the SQL Server connectivity. For more information, connect to the SAP Service Marketplace (SMP) and search for SAP note number 178949.

○ If the SAP Financial Consolidation database is an Oracle database, install the Oracle connectivity. For more information, connect to the SAP Service Marketplace (SMP) and search for SAP note number 339092.



9. Implement the SAP Note number 1427417.10. Open the SE 38 Transaction.

The ABAP Editor opens.11. In the Program field, enter SAP_RSADMIN_MAINTAIN and click Execute (F8).

The SAP_RSADMIN_MAINTAIN page opens.

12. In the OBJECT field, enter _BPC_REQU_SIZE.13. In the VALUE field, enter any integer corresponding to the number of records you want to have.

NoteThe minimum value is 50,000. You can improve deployment performances by increasing that number; however, this depends on the maximum number of table partitions allowed in your RDBMS. For more information, see the recommendations of the RDBMS engine used by your NetWeaver platform.

TipFor example: in SQL Server, the maximum number of partitions is 1,000. This number is fixed by the database engine. You can calculate limitations as follows: 50,000 * (number of maximum partitions per table).

This number is different, depending on the database engine you use.○ For SQL Server 2005, 2008 and 2008 R2: the limit is 1,000 partitions per table => 500,000 * 1,000 =

50,000,000 rows per infocube.○ For Oracle 9i and 10g release 1: the limit is 65,535 partitions per table => 50,000 * 65,535 =

327,6750,000 rows per infocube.○ For Oracle 10g release 2 and 11g: the limit is 1,048,575 => 50,000 * 1,048,575 = 52,428,750,000 rows

per infocube.

14. Click Execute (F8).15. Implement the SAP Note number 1531887 (SV_FPM 10: Missing web services in FPM Basis).


16. Do not forget to install the Certification Authorities of the SAP NetWeaver BW certificate in the Local Computer\Trusted Root Certification Authorities folder of the Cube Deployer server.

17. Configure the HTTPS protocol port with the port number 443 and add to this number your system number: 443<system_number>, for example: 44310.

NoteIf you want to enter another port number, you must edit the web.config file located in C:\Program Files\SAP BusinessObjects\DeployerForFinance\ on the Deployer server, modify the <add key="NetweaverWebServicePort" value="443$$" /> parameter and replace the 443 value with the number you want.

CautionOnce you have deployed a cube in BW, do not modify the Real-Time Data Target setting: only the Real-Time Data Target Can Be Planned; Data Loading Not Allowed option is supported.

7.4.2 Creating BW NetWeaver Roles to deploy Infocubes with Cube Designer

This section describes how to create BW NetWeaver users with dedicated roles that enables you to deploy Infocubes with Cube Designer based on SAP Financial Consolidation data.

Procedure

1. Creating a role based on an existing template:a. Execute the PFCG transaction.b. Enter a name for your role (in this documentation, we use FCDESIGN).c. Click on the Single Role button.

d. In the Authorizations tab click on Change Authorization Data.e. When prompted to select a role template, select S_RS_RDEMO and click on Adopt reference.



Now that you have set the basic authorizations, you must add manually some specific authorizations to have the correct role to deploy Infocubes with Cube Designer.

2. Adding specific authorizations:a. Click on Manually to add the following authorization: S_UQ_BFC.


b. Select the value 16 Execute for the Activity

c. Add the two following authorizations: S_CTS_ADMI and S_CTS_SADM.d. Fill the values as following:



e. Add the following authorization: S_BDS_DS.f. Fill the values as following:

g. Add the following authorization: S_RS_ADMWB.h. Fill the values as following:

i. Add the following authorization: S_RS_ICUBE.j. Fill the values as following:

k. To Add the following values to the existing Authorization Check for RFC Access, go in Cross-application Authorization Objects section, and add the following values: SYST, UQEM0, UQQ1, UQQ2, UQQ3, UQQ4


l. Save the profile and enter a Profile name and a description in the Text field.

m. Click Generate and Save.

3. Completing the role and assigning it to the user:a. In the menu tab, you must had the transactions your user will have access to.b. Click Add Transaction and enter RSA1 and then Assign transactions.

NoteYou can add more transactions but in this specific case it is not relevant.

c. Click the User tab and enter the user you previously created CUBEDESIGN.



d. Save and click on User comparison to synchronise your user with this role.e. You can now assign this role to the user that will be used for the cube generation in the Cube Designer

application.

CautionIt is mandatory to also add the SAP_BC_WEBSERVICE_CONSUMER role as the Deployer component communicates with the NW Webservices created by the FPM Basis add-on.

7.5 Installing the BusinessObjects Enterprise XI 4 platform or the SAP BusinessObjects Information Platform Services

You can now use two platforms with Cube Designer:


● BusinessObjects Enterprise XI 4 (BOE XI 4)If you want to install BusinessObjects Enterprise XI 4.

NoteOnly the Java version of the BusinessObjects Enterprise XI 4 platform is supported with SAP BusinessObjects Cube Designer components (the .NET version is not supported).

● Or SAP BusinessObjects Information Platform Services 4.If you want to install the SAP BusinessObjects Information Platform Services.

The SAP BusinessObjects Information Platform Services implements the BusinessObjects Enterprise XI user management sub system. It allows Enterprise Performance Management Solutions to use the BOE authentication without having to install a full BusinessObjects Enterprise XI platform.

The SAP BusinessObjects Information Platform Services does not include any BI tools available in the full BusinessObjects Enterprise XI platform. BI tools like BI Launch Pad are only available with the full BOE XI platform.

NoteYou can migrate from SAP BusinessObjects Information Platform Services to the full BusinessObjects Enterprise platform if needed.

7.5.1 Installing SAP EPM Solutions Connection Manager on the BOE platform

Prerequisites

To function correctly, the EPM Solutions Connection Manager needs the Microsoft XML Parser 6.0 SP1 component.

NoteYou need to install it manually. It can be found athttp://www.microsoft.com/en-gb/download/details.aspx%3Fid%3D6276 for the 64-bit version.

Context

Once you installed BusinessObjects Enterprise XI or SAP BusinessObjects Information Platform Services, you need to install on the same machine the SAP BusinessObjects EPM Solutions Connection Manager.

CautionIf you installed the BusinessObjects Enterprise XI 4 platform on several servers, you must also install the SAP BusinessObjects EPM Solutions Connection Manager on these machines.



http://help.sap.com/disclaimer?site=http://www.microsoft.com/en-gb/download/details.aspx%3Fid%3D6276

http://help.sap.com/disclaimer?site=http://www.microsoft.com/en-gb/download/details.aspx%3Fid%3D6276

NoteYou can only install the Java version of the BusinessObjects Enterprise XI platform with SAP Cube Designer (the .NET version is not supported).

Procedure

1. Stop the application server service (depending on the application server service you are using: Tomcat, WebSphere, etc.)

2. Navigate to the BOE platform (or the Information platform Services) installation directory: [BOE_INSTALL_DIR]\SAP BusinessObjects Enterprise XI 4\wdeploy\conf.

3. Open one of the corresponding configuration file, depending on your application server.For example, config.tomcat6 if your application server is Tomcat 6.

4. Modify the parameters corresponding to your environment.For example, if you use a Tomcat 6 application server, you must check the following parameters of the config.tomcat6 file:

## ## Business Objects Configuration Utility ## # as_dir: the installation directory of the application server #as_dir=/home/qaunix/Tomcat6018 as_dir=D:\SAP\BOEXIR4\Tomcat6 # as_instance: the application server instance to deploy to (represents the name of a folder in the conf/Catalina directory) as_instance=localhost #on windows, if tomcat is installed as a service, specify #service name to modify service startupparameters too as_service_name=BOEXI40Tomcat #on windows, when tomcat is installed as aservice, the name of the key where the java startup parameters arestored # (there is generally no need to touch this) as_service_key=HKLM\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\${as_service_name}\Parameters\Java # as_service_key_value: name of the String value where the java startup parameters are stored, in the keypointed to by as_service_key # (there is generally no need to touch this) as_service_key_value=Options as_service_key_value=Options

○ as_dir=D:\SAP\BOEXIR4\Tomcat6○ as_instance=localhost○ as_service_name=BOEXI40Tomcat

5. Modify it if necessary, save and close the file.6. Run the Setup.exe located in the SAP EPM Solutions Connection Manager folder.

If one of the components required is missing or not in the minimum version supported, the list of requirements to install opens.

7. Click Install.

The SAP EPM Solutions Connection Manager dialog box opens.


8. Click Next.9. In the License Agreement dialog box, select the I accept the terms in the license agreement option and click

Next.10. In the Customer Information dialog box, specify a User Name, your Organization and click Next.


11. Specify the application server you are using and click Next.12. In the Confirmation dialog box, click OK.

The Ready to Install the Program dialog box opens.13. If the settings are correct, click Install.14. Once the installation is complete, click Finish.

7.5.2 Configuring the Central Management Console for SAP Cube Designer

Procedure

1. To access the Central Management Console:

○ Click Start > Programs > Information Platform Services 4 > Information Platform Services > SAP BusinessObjects Information Platform Services Central Management Console.

○ Click Start > Programs > BusinessObjects Enterprise XI 4 > BusinessObjects Enterprise > Central Management Console.



2. Click Manage > Applications.3. Select EPM Connection Manager and right-click on it to edit its properties.

The following window opens.

4. In the Administration Web Services section, specify the protocol you want to use (HTTP or HTTPS) and the TCP port which will be configured for the UDF administration web service. You can modify this port and use a port other than the port 80 (the default).

NoteIt is not possible to manage different ports for each machine. You must use the same port number for all administration web services on your entire BusinessObjects Cube Designer platform (other Web applications can still use different IP ports and can be deployed on different IIS sites).

5. In the the Administration Account section, enter the login and password of an administrator account of the SSAS server.

6. Click Save and close.7. Right-click EPM Connection Manager > User Security.8. Define the user security you want to apply, based on the functional rights you assigned to the users in the SAP

Financial Consolidation application. For more information, see the SAP Financial Consolidation Security Guide.


7.5.3 Configuring the Central Management Server for a distributed installation

Context

If you installed the web server of the BusinessObjects Enterprise XI platform on another machine than the CMS, you must check that on the web server, the CMS is indicated. By default, the Web Services connects to the local machine name's CMS. If you want to change to a dedicated CMS, you must change the domain property in the dsws.properties file.

To do so, the following configuration steps are required:

Procedure

1. Stop the application server of the machine where the BOE is installed.2. Open the installation path folder of SAP BusinessObjects Enterprise XI 4. For example:

[InstallationPath]\Tomcat55\webapps\dswsbobje\WEBINF\classes.

3. Open the file dsws.properties and locate the following parameter: domain= .

4. Enter your CMS name.5. Close and save the dsws.properties file.

6. Start Tomcat.

To find out more, see the Central Management System documentation. http://help.sap.com/businessobject/product_guides/boexir3/en/xi3_query_as_a_web_service_en.pdf



http://help.sap.com/businessobject/product_guides/boexir3/en/xi3_query_as_a_web_service_en.pdf

http://help.sap.com/businessobject/product_guides/boexir3/en/xi3_query_as_a_web_service_en.pdf

8 Configuring the SAP Financial Consolidation Cube Designer Components

8.1 Configuring Cube Deployer and Cube Designer Certificates for SAP HANA

Context

In order to ensure security between the Cube Designer and Cube Deployer components and SAP HANA (especially if you use SAP HANA Modelling Views), you must configure the default certificate installed by the setup, or install and configure your own certificate (from a certification authority).

Procedure

1. If you are using the default certificate installed by the setup:a. On the Cube Designer client component, open the Cartesis.InformationDelivery.Workbench.exe.config file

located in \Program Files (x86)\SAP\Financial Consolidation\Cube Designer.b. Add the following two new sections: <configSections> and <SharedTrustedCertificates> into

this file.

<?xml version="1.0" encoding="UTF-8"?><configuration> <configSections> <section name="SharedTrustedCertificates" type="Cartesis.InformationDelivery.SolutionDefinitions.SharedTrustedCertificates,Cartesis.InformationDelivery.SolutionDefinitions"/> </configSections> <appSettings> <add key="SLD.Host" value=""></add> <add key="SLD.UserName" value=""></add> <add key="SLD.Password" value=""></add> <add key="SLD.Port" value=""></add> ... <add key="HanaAPIVersion" value="2"></add> <add key="EnableSSASCubesFromHanaDB" value="True"/> </appSettings> <SharedTrustedCertificates> <Certificate subjectName="CN=Extended Analytics Deployer, O=BOBJ, C=FR" store="My"/> </SharedTrustedCertificates> </configuration>

SAP BusinessObjects Financial Consolidation Installation GuideConfiguring the SAP Financial Consolidation Cube Designer Components C U S T O M E R 107

2. If you want to use your own certificates:a. On the Cube Deployer server, open the web.config file located in \Program Files\SAP\Financial

Consolidation\Cube Deployer.b. In the <SharedTrustedCertificates> section, replace the <Certificate

subjectName="CN=Extended Analytics Deployer, O=BOBJ, C=FR" store="My" /> with the corresponding information of your own certificate.

<SharedTrustedCertificates> <Certificate subjectName="CN=..., O=..., C=..." store="..."/> </SharedTrustedCertificates> </configuration>

c. Restart IIS.d. On the Cube Designer client component, open the Cartesis.InformationDelivery.Workbench.exe.config file

located in \Program Files (x86)\SAP\Financial Consolidation\Cube Designer.e. Add the following two new sections: <configSections> and <SharedTrustedCertificates> into

this file and modify it with the information of your own certificate.

<?xml version="1.0" encoding="UTF-8"?><configuration> <configSections> <section name="SharedTrustedCertificates" type="Cartesis.InformationDelivery.SolutionDefinitions.SharedTrustedCertificates,Cartesis.InformationDelivery.SolutionDefinitions"/> </configSections> <appSettings> <add key="SLD.Host" value=""></add> <add key="SLD.UserName" value=""></add> <add key="SLD.Password" value=""></add> <add key="SLD.Port" value=""></add> ... <add key="HanaAPIVersion" value="2"></add> <add key="EnableSSASCubesFromHanaDB" value="True"/> </appSettings> <SharedTrustedCertificates> <Certificate subjectName="CN=..., O=..., C=..." store="..."/> </SharedTrustedCertificates> </configuration>

NoteThe information contained in the <SharedTrustedCertificates> must be exactly the same as the information contained in the <SharedTrustedCertificates> section you added in the web.config file of the Cube Deployer server.

8.2 Reverse proxy configuration

Context

EPM for Finance applications introduce a Single Sign On (SSO) mechanism between web applications.


Configuring the SAP Financial Consolidation Cube Designer Components

SSO allows a user to sign on to one EPM for Finance web application and then use other EPM web applications without having to enter his credentials.

For example, a user enters his credentials to connect to the SAP BusinessObjects InfoView web portal and he receives a BusinessObjects Enterprise XI session cookie. From SAP BusinessObjects InfoView, he goes to the SAP Financial Consolidation web application with the same browser session, and does not need to re-enter his credentials, he is logged on automatically. His BusinessObjects Enterprise XI session cookie is reused automatically.

A reverse proxy server can be mandatory if you are using single sign-on (SSO).

For SSO to work, follow this procedure:

● Use the SAP authentication with the same BusinessObjects Enterprise platform for all EPM for Finance applications

● Use the same URL domain name for all EPM for Finance applications web sites:○ Either all EPM for Finance applications web servers must be installed on the same physical server,○ or each web application is installed on separated servers and all URLs are published on the same reverse

proxy server.

Procedure

1. If you use a reverse proxy, you need to publish the web services URL of the BusinessObjects Enterprise XI through the reverse proxy: http://[BOE_SRV]:8080/dswsbobje.For example, with Apache, it would be:

ProxyPass /dswsbobje http://[BOE_SRV]:8080/dswsbobje ProxyPassReverse /dswsbobje http://[BOE_SRV]:8080/dswsbobjeProxyPassReverseCookiePath /dswsbobje /dswsbobje

2. Then, you need to indicate in the BusinessObjects Enterprise XI platform that the web services URL are published through a reverse proxy by adding the URL of the reverse proxy. Edit the dsws.properties file located in [InstallationPath]\Tomcat55\webapps\dswsbobje\WEBINF\classes.

3. Modify the following lines with the URL of your reverse proxy.

wsresource1=ReportEngine|reportengine web service alone|http://[myproxy.mycompany.com]/dswsbobje/services/ReportEngine wsresource2=BICatalog|bicatalog web service alone|http://[myproxy.mycompany.com] /dswsbobje/services/BICatatog wsresource4=QueryService|query web service alone|http://[myproxy.mycompany.com] /dswsbobje/services/QueryService wsresource5=BIPlatform|BIPlatform web service|services/BIPlatform wsresource6=LiveOffice|Live Office web service|services/LiveOffice wsresource7=SaveService|Save web service|services/SaveService


8.3 Creating an EPM Connection for SAP Financial Consolidation with NetWeaver BW Cubes

Prerequisites

Once all the required components are installed, you need to create a connection on the BusinessObjects Enterprise XI platform.

First, you must ensure that all the requirements on the SAP Financial Consolidation platform are met:

1. Install the Web services. To find out more about the Web services installation procedure, see the Installing and configuring the SAP Financial Consolidation Web Services [page 69] chapter.

2. Configure the SAP Financial Consolidation users with the BusinessObjects Enterprise XI authentication, as indicated in the SAP Financial Consolidation Security Guide.

CautionYou must configure your NetWeaver BW platform as mentioned in Installing FPM Basis on the NetWeaver BW Server [page 93].

Context

To create the connection in the Central Management Console:

Procedure

1. Log on to the Central Management Console.2. In the Organize section, click EPM Connections.3. Click New Connection.




4. Enter a name for the connection.5. In the Source Application field, select the SAP Financial Consolidation application.6. In the Provider field, select the ODBO Provider for Netweaver BI.7. In the Server address field, enter the URL of the NetWeaver server you are going to use.8. In the System Number and Client fields, enter the system number and client of the NetWeaver BW platform.9. In the Web services URL field, enter the URL of the SAP Financial Consolidation Web Services.10. Click Save.

Once the connection is created, you need to define the appropriate security in the Central Management Console. For more information, see Configuring the Central Management Console for SAP Cube Designer [page 104].

CautionBy default, only the administrators can see all objects.


NoteYou must create the appropriate roles on the NetWeaver platform for NW cube deployment. For more information, see Installing FPM Basis on the NetWeaver BW Server [page 93]

8.4 Creating an EPM Connection for SAP Financial Consolidation with SSAS Cubes

Prerequisites


First, you have to ensure that all the requirements on the Financial Consolidation platform are met:

1. Install the Web services. To find out more about the installation procedure, see Installing and configuring the SAP Financial Consolidation Web Services [page 69].

2. Configure the Financial Consolidation users with the BusinessObjects Enterprise XI authentication, as indicated in the SAP Financial Consolidation Security Guide.

Context


Procedure

1. Logon to the Central Management Console.2. In the Organize section, click EPM Connections.3. Click New Connection.




4. Enter a name for the connection.5. In the Source Application field, select the SAP Financial Consolidation application.6. In the Provider field, select Microsoft Analysis Services 2008 or Microsoft Analysis Services 2012.7. In the Server address field, enter the URL of the datapump located on the SSAS Server.8. In the Server Name field, enter the name of the SSAS server. If you installed it with a named instance, do not

forget to indicate the name of the instance as well.9. In the Catalog field, select the SSAS database you are going to use.

CautionYou must select a catalog (an SSAS database) that is only created and used by Cube Designer.

NoteWhen creating the EPM connection, a message appears « database not found ». This is normal as the database is only created after the first solution is deployed.

10. In the Web services URL field, enter the URL of the Financial Consolidation Web Services.11. Click Save.


Once the connection is created, you must define the appropriate security in the Central Management Console. For more information, see Configuring the Central Management Console for SAP Cube Designer [page 104].


8.5 Creating an EPM Connection for SAP Profitability and Cost Management (PCM) and SAP Strategy Management (SSM)

Prerequisites


Context


Procedure





4. Enter a name for the connection.5. In the Source Application field, select the PCM, SSM or BPC application.6. In the Provider field, select the appropriate ODBO Provider.7. In the Server address field, enter the URL of the BusinessObjects Profitability and Cost Management (PCM);

SAP BusinessObjects Strategy Management (SSM).8. In the Catalog field, select the appropriate database.9. Click Save.


8.6 Creating an EPM Connection for Third Party Applications

Prerequisites



Context


Procedure



4. Enter a name for the connection.5. In the Source Application field, select the Third Party Application.6. In the Provider field:

○ Select the Microsoft Analysis Services 2008 or 2012 if you want to use this connection to generate or consult SSAS cubes.

○ Select the ODBO Provider for Netweaver BW if you want to use this connection to consult Netweaver BW cubes.

7. In the Server address field, enter the server URL.



8. If you selected the Microsoft Analysis Services 2008 or 2012 provider:

○ In the Server address field, enter the URL of the datapump located on the SSAS Server.

○ In the Catalog field, select the SSAS database you are going to use.9. If you selected the ODBO Provider for Netweaver BI:

○ In the Server address field, enter the URL of the NetWeaver server you are going to use.

○ In the System Number and Client fields, enter the system number and client of the NetWeaver BW platform.

10. Click Save.


8.7 Creating an EPM Connection for Star Schema

Prerequisites


First, you have to ensure that all the requirements on the Financial Consolidation platform are met:

1. Install the Web services. To find out more about the installation procedure, see Installing and configuring the SAP Financial Consolidation Web Services [page 69].

2. Configure the Financial Consolidation users with the BusinessObjects Enterprise XI authentication, as indicated in the SAP Financial Consolidation Security Guide.

Context


Procedure

1. Log on to the Central Management Console.2. In the Organize section, click EPM Connections.3. Click New Connection.



4. Enter a name for the connection.5. In the Source Application field, select the SAP Financial Consolidation application.6. In the Provider field, select the Star Schema provider.7. In the Web services URL field, enter the URL of the SAP Financial Consolidation Web Services.8. Click Save.


8.8 Creating an EPM Connection for SAP HANA

Context


Procedure




The following page opens.

4. Enter a name for the connection.5. In the Source Application field, select the SAP Financial Consolidation application.6. In the Provider field, select SAP HANA.7. In the Web services URL field, enter the URL of the Financial Consolidation Web Service.8. Click Save.




9 Installing and Configuring Cube Designer Components for SAP HANA Modeling Views

Before you install Cube Designer components for SAP HANA Modeling Views, make sure you have met the following requirements:

● SAP HANA SPS 11 revision 112 or higher is installed,● SAP HANA Client SPS 11 revision 112 or higher is installed on the Financial Consolidation application server.

9.1 Installing the Financial Consolidation HANA Add-on Delivery Unit

This section explains how to manually deploy the Financial Consolidation HANA Add on Delivery Unit into the SAP HANA Studio application.

Context

This HANA Add-on Delivery Unit will deploy the SAP HANA Content that the Financial Consolidation application will use to generate SAP HANA Modeling Views and the relevant SAP HANA Roles.

NoteIf you are upgrading from SAP Financial Consolidation 10.0 to SAP Financial Consolidation 10.1 and the HANA Add-on Delivery Unit is already deployed, you do not need to uninstall the previous Delivery Unit before installing the new 10.1 one.

TipThe HANA Add-on Delivery Unit 10.1 is compatible with SAP Financial Consolidation 10.0.

Procedure

1. Open SAP HANA Studio.

2. Select File Import .


Installing and Configuring Cube Designer Components for SAP HANA Modeling Views

3. In the import source list, open the SAP HANA Content, and select Delivery Unit.

4. Click Next.5. Select the Target System where you want to install the Financial Consolidation HANA Add on.6. Click Next.7. In the Select File area, select the Client option.8. Select the HCOEPMFC.tgz file that you downloaded from SAP Service Market Place.

SAP BusinessObjects Financial Consolidation Installation GuideInstalling and Configuring Cube Designer Components for SAP HANA Modeling Views C U S T O M E R 121

9. Click Finish to install and activate the Financial Consolidation HANA Add on Delivery Unit.

10. In SAP HANA Studio, open the Content folder: sap epm fc view deployer .



11. Right-click the deployer package and select New Package .The following dialog box opens:

12. In the Name field, enter: sap.epm.fc.view.deployer.content and click OK.


9.2 Generating Time Data in SAP HANA

Context

If you want to consume cubes generated with SAP HANA, you first need to generate time date in the SAP HANA database.

Procedure

1. Open SAP HANA Studio.2. From the Systems View, select the SAP HANA instance where SAP Financial Consolidation will be deployed.

3. Right-click on this instance and select SAP HANA Modeler Generate Time Data .




4. Select the following options:

○ Calendar Type: select the Gregorian type.○ From Year to Year: enter the period of time for which you want to generate time data.○ Granularity: select the Month option.


9.3 Configuring User Rights

Context

Once the Financial Consolidation HANA Add on Delivery Unit is deployed, you need to create the appropriate users and grant them the appropriate rights. The following users must be created in the SAP HANA database:

● The technical user account used to access the Delivery Unit that generates SAP HANA Modeling Views: [TECHNICAL_USER]

● The Financial Consolidation database schema owner: [FC_SCHEMA]● Several users that will access Modeling Views [REPORTING_USER_XX]

Procedure

1. Connect to SAP HANA Studio with a system account and open the [FC_SCHEMA] user.2. In the System Privileges tab, grant him the following system privileges:

○ CREATE STRUCTURED PRIVILEGE○ STRUCTURED PRIVILEGE ADMIN○ ROLE ADMIN

3. In the Object Privileges tab, select the following objects with the following privileges:

○ _SYS_BI with EXECUTE and SELECT○ _SYS_BIC with EXECUTE and SELECT○ GRANT_PRIVILEGE_ON_ACTIVATED_CONTENT(_SYS_REPO) with EXECUTE○ GRANT_SCHEMA_PRIVILEGE_ON_ACTIVATED_CONTENT(_SYS_REPO) with EXECUTE

4. Create the technical user account used to access the Delivery Unit that generates SAP HANA Modeling Views: [TECHNICAL_USER].

5. Grant this user the following role: sap.epm.fc.view.deployer.v1.roles::CubeDeployer.

6. In the System Privileges tab, grant him the following system privileges:

○ ROLE ADMIN7. In the Object Privileges tab, select the following object privileges:

○ _SYS_BI with EXECUTE and SELECT○ _SYS_BIC with EXECUTE and SELECT○ GRANT_PRIVILEGE_ON_ACTIVATED_CONTENT(_SYS_REPO) with EXECUTE



8. Then grant the [TECHNICAL_USER] the following package privileges: sap.epm.fc.view.deployer.content with the following privileges:

○ REPO.READ○ REPO.EDIT_NATIVE_OBJECTS○ REPO.ACTIVATE_NATIVE_OBJECTS○ REPO.MAINTAIN_NATIVE_PACKAGES

NoteThis user can use the basic or the X509 authentication mode.

9. Connect to SAP HANA Studio with the Financial Consolidation database schema owner: [FC_SCHEMA].

CautionYou must use the [FC_SCHEMA] user and no other user.

10. Select Security Users and open the technical user.11. In the Object Privileges of the technical user, select the [FC_SCHEMA] schema and grant him the following

privileges:

○ create any○ alter○ drop○ select


○ insert○ update○ delete○ trigger

You can also execute the following SQL queries:○ grant create any on schema [FC_SCHEMA] to [TECHNICAL_USER] ;○ grant alter on schema [FC_SCHEMA] to [TECHNICAL_USER] ;○ grant drop on schema [FC_SCHEMA] to [TECHNICAL_USER] ;○ grant select on schema [FC_SCHEMA] to [TECHNICAL_USER] ;○ grant insert on schema [FC_SCHEMA] to [TECHNICAL_USER] ;○ grant update on schema [FC_SCHEMA] to [TECHNICAL_USER] ;○ grant delete on schema [FC_SCHEMA] to [TECHNICAL_USER] ;○ grant trigger on schema [FC_SCHEMA] to [TECHNICAL_USER] ;

12. Still using the Financial Consolidation database schema owner: [FC_SCHEMA], open the _SYS_REPO user.13. In the Object Privileges, grant him the following privileges:

○ SELECT with the Grantable to Others option.○ EXECUTE with the Grantable to Others option.

You can also execute the following SQL query: grant select, execute on schema [FC_SCHEMA] to _SYS_REPO with grant option;



9.4 Configuring SAP HANA Users to Access Modeling Views

When SAP HANA Modeling Views are deployed, they can be accessed with SAP HANA users. These users must be granted specific system rights to get access to these SAP HANA Modeling Views, and must have specific roles to ensure data security.

Context

The two following sections explains:

1. How to configure system rights to allow SAP HANA users to have access to Modeling Views.2. How to assign SAP HANA roles to these users so that they inherate the Financial Consolidation security on

data.

9.4.1 Configuring system rights to allow SAP HANA users to have access to Modeling Views

Procedure

1. Connect to SAP HANA Studio with a system account and open or create the HANA user that you will use to access Modeling Views. For example, you can create the following user: [REPORTING_USER].

2. In the Object Privileges tab, select the _SYS_BI object, and grant him the EXECUTE and SELECT privileges.3. Connect to SAP HANA Studio with the Financial Consolidation database schema owner: [FC_SCHEMA] and

open the [REPORTING_USER].4. In the Object Privileges tab, select the [FC_SCHEMA] schema and grant him SELECT privilege.

9.4.2 Configuring system rights to allow SAP HANA users to have access to Modeling Views without FC security

If you want to deploy cubes without the Financial Consolidation security (the Deploy modeling views only option in the Cube Designer component), the SAP HANA users that will access these cubes must be granted the [FC_SCHEMA]_SAPFC_ANALYTIC_ROLE_CP_ALL role.

In order to create this role, you have two options:

● You deploy a cube with the Deploy modeling views only option selected, and then save a Data Access Group in the Financial Consolidation application.

● Or you deploy a cube with the Deploy option selected.


9.4.3 Configuring SAP HANA roles to inherit the Financial Consolidation security on data

The SAP HANA user that you will use to access Modeling Views [REPORTING_USER] must be assigned SAP HANA roles in order to inherit the Financial Consolidation security on data.

The Financial Consolidation application defines security on data through Data Access Groups (DAG): each Financial Consolidation user belongs to one Data Access Group.

When deploying SAP HANA Modeling Views with Financial Consolidation Cube Designer, a SAP HANA role is created for each Financial Consolidation Data Access Group. To one Data Access Group corresponds one SAP HANA role.

These roles are named: [FC_SCHEMA]_SAPFC_ANALYTIC_ROLE_[DAG_ID]_[DAG_CODE].

You must then apply these roles to the SAP HANA user that is used to access Modeling Views [REPORTING_USER].

ExampleA Financial Consolidation user is associated with one Data Access Group. The DAG internal ID is 1048060 and the DAG Code is EUROPE. The Financial Consolidation schema name is FINANCE. Once a SAP HANA modeling view has been deployed, one SAP HANA role is created: FINANCE_SAPFC_ANALYTIC_ROLE_1048060_EUROPE.

The SAP HANA user [REPORTING_USER] corresponding to the Financial Consolidation user must be granted this role to inherit the Financial Consolidation security on data.

The following stored procedure allows you to perform this mapping:

DROP PROCEDURE GRANT_ANALYTIC_PRIVILEGES_TO_USER; CREATE PROCEDURE GRANT_ANALYTIC_PRIVILEGES_TO_USER( IN userFC NVARCHAR(256), IN userHANA NVARCHAR(256) )LANGUAGE SQLSCRIPT ASBEGIN DECLARE CURSOR cur_dag FOR SELECT ROLE_NAME, DATARIGHTS_ID FROM "CT_USER", PUBLIC.ROLES where ROLE_NAME LIKE CURRENT_SCHEMA || '_SAPFC_ANALYTIC_ROLE_' || DATARIGHTS_ID || '_%' and NAME = :userFC; FOR cur_row as cur_dag DO EXEC 'GRANT "' || cur_row.ROLE_NAME || '" TO ' || :userHANA;END FOR; END; CALL GRANT_ANALYTIC_PRIVILEGES_TO_USER('USER_FC','USER_HANA');



9.5 Configuring the Financial Consolidation Data source parameters for SAP HANA deployment

Context

Before configuring the Financial Consolidation data source parameters for SAP HANA deployment, you must first deploy the web service as indicated in Installing and configuring SAP Financial Consolidation Web Services [page 69].

Procedure

1. Connect to the Financial Consolidation Administration Console web site.For example, http://localhost/WebAdmin.

2. Open the Configuration page.

3. Open the SAP HANA Deployment parameters section.4. In the Financial Consolidation HANA add on delivery unit URL field, enter the URL of the Financial

Consolidation HANA Add-on Delivery Unit that you deployed. For example: http://HANASERVER:80XX/sap/epm/fc/view/deployer where XX corresponds to the SAP HANA instance number.

5. In the Financial Consolidation data source schema field, enter the Financial Consolidation schema name [FC_SCHEMA].


6. In the SAP HANA technical user name field, enter the technical account user name used to access the Delivery Unit that generates SAP HANA Modeling Views: [TECHNICAL_USER]

7. In the Authentication mode field, select Basic or X509.8. In the SAP HANA technical user password field, enter the technical user account password, or the X509

Certificate content if you chose the X509 authentication mode.9. Click Save.



10 Installing Client Components

10.1 Installing the SAP Financial Consolidation client

Context

RememberAs SAP Financial Consolidation now uses a new setup technology, you are not prompted to uninstall earlier versions of SAP Financial Consolidation but you need to manually uninstall all previous versions via the Windows Control Panel before you can install SAP Financial Consolidation 10.1.

NoteDo not forget to install Adobe Flash Player as it is required on the client site to access the new dashboards.


Procedure



2. Click Run.



SAP BusinessObjects Financial Consolidation Installation GuideInstalling Client Components C U S T O M E R 133


CautionThe SAP BusinessObjects User Management Client component is not mandatory. As the UMC setup starts automatically, you can click Cancel and the SAP Financial Consolidation setup will continue normally.




click Next.

The Setup Type window opens.9. Select the Client installation option and click Next.

The Custom setup dialog box opens.

10. Select the following components:○ Application: If you check this option, all of the components required for running SAP Financial

Consolidation will be installed.


Installing Client Components

○ Console: This option is optional and enables you to access the tool used for managing the data sources.○ Online help: This option enables you to access the documentation in electronic format.○ Excel Link: this option lets you install Excel Link.

The Ready to install the program dialog box opens.11. If the settings are correct, click Next.

NoteThe actual installation then begins. Depending on the performance of your computer, the installation may last several minutes. You should not perform any other task until the installation is complete in order to ensure that the application is correctly installed.

Once the installation is complete, the Installation completed dialog box opens.12. Click Finish.13. Restart your computer.14. If you are planning to choose the Use Windows account option when connecting to the application, check that

you are logged on windows with the same account you used to configure your SAP Financial Consolidation user.

15. Then you need to run the following command line in a DOS prompt on the client workstation.

Finance.exe /AuthWindows

CautionIf you do not run the script, you will not be able to connect to the application using the Windows authentication.

Noteif you want to revert to the default authentication mode (no Windows authentication), then run the following command line:

Finance.exe /AuthNone

10.2 Installing SAP Financial Consolidation Cube Designer

Prerequisites


● Microsoft .Net Framework 4.5.1 or later● Runtime Microsoft Visual C++ 10.0 CRT (x86)



Procedure

1. Execute the Setup.exe file located in the SAP Cube Designer folder.2. Click Next.3. Select the I accept the terms in the license agreement option and click Next.4. Specify a User Name and your Organization and check the Anyone who uses this computer (all users) box.

CautionIf you choose the Only for me option, you must only install in the folder C:\Users\My_User\AppData\Local\Programs\SAP\Financial Consolidation\Designer\, or the application will not function correctly.

5. Click Next.The following dialog box opens.

6. Enter the URL of the Central Management Console web service. By default, the URL indicates "localhost" but it is probably installed on another server.




NoteDo not forget to indicate where the Central Management Console is deployed.

7. Click Next.8. Select the folder in which you want to install the application and click Next.9. In the Confirmation dialog box, click OK.10. If the settings are correct, click Install.11. Once the installation is complete, click Finish.

Results

You can avoid doubled amounts for self-referenced characteristics in an SSAS cube generated with Designer. You can specify that only data members (when any) are taken into account into the generated cube and that the sums of the aggregated children are taken into account only when the data member are missing on the parent node.

To do so, you can edit either one of the two in the Cartesis.InformationDelivery.Workbench.exe.config file located by default in C:\Program Files (x86)\SAP\Financial Consolidation\Designer:

● As a priority, set the "UsingDataMemberOnHierarchies" key to true, as follows: <add key="UsingDataMemberOnHierarchies" value="true" />

● If you notice that your cube deployment is slower than before, set the "OverrideDimensionAggregationsForNodesOnly" to true instead, as follows: <add key="OverrideDimensionAggregationsForNodesOnly" value="true" />

10.3 Configuring the SAP Financial Consolidation Cube Deployer URL

Procedure

1. To modify the URL of the Deployer or the BOE Central Management Server web services, edit the Cartesis.InformationDelivery.Workbench.exe.config file located by default in C:\Program Files (x86)\SAP\Financial Consolidation\Cube Designer on the Cube Designer client machine.

2. Search for the following rows and modify it:

<?xml version="1.0" encoding="utf-8"?> <configuration> <appSettings> <add key="SLD.Host" value=""></add> <add key="SLD.UserName" value=""></add> <add key="SLD.Password" value=""></add> <add key="SLD.Port" value=""></add> <add key="SLD.IsSecured" value=""></add> <add key="SLD.LocalSystemName" value="BOBJ_EADES"></add> <add key="SLD.ProductID" value="01200615320900004560"></add> <add key="SLD.ProductName" value="BOBJ FINANCE CONSOLIDATION"></add>


<add key="SLD.ProductVendor" value="sap.com"></add> <add key="SLD.ProductVersion" value="800"></add> <add key="SLD.SoftwareComponentID" value="01200314690200012536"></add> <add key="SLD.SoftwareComponentVendor" value="sap.com"></add> <add key="SLD.SoftwareComponentName" value="BOBJ_EADES"></add> <add key="SLD.SoftwareComponentVersion" value="800"></add> <add key="Log4NetInitFile" value="./Cartesis.InformationDelivery.Workbench.exe-LogConfig.xml"></add> <add key="DuplicateElementsAllowed" value="true"></add> <add key="iAnalysisStarSchemaTableNames" value="false"></add> <add key="StarSchemaAggregation" value="true"></add> <add key="IsAccountDimensionAggregatable" value="false"></add> <add key="DeployerUrl" value="http://vm-doc-deployer/DeployerForFinance/ DeploymentService.asmx"> <add key="MergeMemberMaxDisplay" value="5000"></add> <add key="MultiMeasureGroupAnalysis" value="false"></add> <add key="WebClientTimeout" value="100000"></add> <add key="DeployerPollingTimer" value="5000"></add> <add key="AttributeRelationshipType" value="Flexible"></add> <add key="BiPlatformWSUrl" value="http://vm-docboe:8080/dswsbobje/services/Session"></add> </appSettings> </configuration>

NoteYou can enter a URL containing HTTPS syntax. SSL certificates are supported and it is strongly recommended to use the HTTPS protocol in a production environment.

3. Save and close the file.



11 Configuring Client Components

11.1 Configuring the Windows Client for Excel Link

In order to ensure that Excel Link functions correctly, you must install the Microsoft Office Tools Visual Basic for Applications (VBA) component.

NoteThis component is available with the Microsoft Office installation package.

11.2 Configuring the Web Client

Context

In order to optimize navigation in SAP Financial Consolidation Web, you must follow the recommendations below.

NoteThe settings indicated here are not compulsory but enable you to improve the performance of SAP Financial Consolidation Web. Before applying these settings, please check that they are authorized by your network administrator.

CautionSAP Financial Consolidation does not work when two Web sessions are started on the same client workstation.

Procedure

1. Start Internet Explorer and select Tools > Internet Options.2. Select the General tab.3. In the Temporary Internet files groupbox, click on Settings.

The Settings window opens.4. In the Check for newer versions of stored pages groupbox, select Automatically.

SAP BusinessObjects Financial Consolidation Installation GuideConfiguring Client Components C U S T O M E R 139

CautionSAP Financial Consolidation will not work if you select Never.

CautionYou should also clear the cache regularly, especially each time a new version of SAP Financial Consolidation is installed.

5. Select the Security tab.6. Click the Trusted sites icon, and then the Sites button.7. The Trusted sites dialog box opens.8. Enter the URL of your SAP Financial Consolidation Web site and click Add.9. Click OK.10. Select the Advanced tab.11. Under Security settings, check the "Allow active content to run in files on My Computer " option.


Configuring Client Components

NoteYou should not select the "Always open pop-ups in a new tab" option. SAP Financial Consolidation Web will not work correctly.

12. Under HTTP 1.1 settings, select the Use HTTP 1.1 option to activate support for the HTTP 1.1 protocol.

13. If your computers are located on a network using a proxy server, you must also select the Use HTTP 1.1 through proxy connections as well as the Use HTTP 1.1 option, as shown below.


NoteIf you do not check this option and the Web site is accessed through the proxy, SAP Financial Consolidation Web may not work correctly.

14. open the Local Security Policy console by executing the "secpol.msc" command.

15. Go to Security Settings Local Policies Security Options and double-click User Account Control: Admin Approval Mode for the Built-in Administrator account to open it.

16. In the Local Security Setting tab, select the Enabled option.17. Restart the machine.

NoteYou must enable this security setting only on the web client, it is not required on any server component.



11.3 Configuring SAP Financial Consolidation Excel Web Schedules

11.3.1 Configuring Internet Explorer

CautionIf you are planning to use Excel Web Schedules with Microsoft Excel 2007, Internet Explorer version 7 is mandatory.

For computers with access only to Intranet and not to the Internet, you should uncheck the Check for publisher's certificate revocation option in Internet Explorer.

You do this by selecting Tools > Internet Options > Advanced tab.

If you do not do so, each time you open a SAP Financial Consolidation Excel Web Schedules, Internet Explorer will check that the security certificates are up-to-date. This results in poor performance.


11.3.2 Specific configuration for using EWS folders offline

Context

By default, Internet Explorer refuses to give pages displayed on the Internet access to local items on the computer. The items cannot be uploaded even if they have valid certificates. This problem occurs when a user tries to reconnect to EWS after entering data in a EWS workbook offline. To display the workbook correctly, the following options must be selected:

Procedure

1. Start Internet Explorer and select Tools > Internet Options.2. Select the Advanced tab.3. Under the Security heading, check the Allow active content to run in files on My Computer option.4. Edit the following registry key: [HKEY_CURRENT_USER\Software\Microsoft\Windows\ CurrentVersion

\Internet Settings\Zones\].5. In the 0 zone, search for the 2101 value.6. In the Value data field, enter the value 1.

NoteInternet Explorer will ask you to confirm the action each time you reconnect an Excel workbook to EWS.

CautionYou can avoid the confirmation message by entering 0 as the value for the registry key. However, if you do so, you will no longer receive any confirmation message for any of the Internet sites you consult. This obviously represents a security risk for the computer. Business Objects does not recommend this solution.

11.3.3 Specific configuration in Microsoft Excel

Context

CautionSAP Financial Consolidation Excel Web Schedules will not work if the Microsoft Office Tools Visual Basic for Applications component has not been installed.

NoteThe first time you open a schedule using EWS, a warning message appears. This is the standard behaviour of the application.



So that EWS functions correctly, some options must be configured in Microsoft Excel:

Procedure

1. The XLS extension should be assigned to the Microsoft Excel worksheets in the Edit File Type window in Windows Explorer (Tools > Folder Options > File Type tab > Microsoft Excel XLS Worksheet > Advanced button).

You must also check the Browse in same window option.

2. A printer should be defined for the client computer.

CautionUnder Windows 2008 Vista and Windows 7 Operating Systems, the File Type tab is no longer available. You must then apply the procedure described in the following Microsoft article:http://support.microsoft.com/kb/927009/en .

3. The macro security level should be configured with the Trust all installed add-ins and templates and Trust access to Visual Basic Project options. You can access these options in Excel by clicking on Tools > Macros > Security.


http://help.sap.com/disclaimer?site=http://support.microsoft.com/kb/927009/en

http://help.sap.com/disclaimer?site=http://support.microsoft.com/kb/927009/en

11.3.4 Enabling Macros for Excel 2003

Context

Depending on the version of Excel used, you should follow one of the procedures described below to enable the macros used for Excel Web schedules.

Procedure

1. In Excel 2003, when the schedule is opened, the Security Warning dialog box appears.2. Check the Always trust macros from this source option.3. Click Enable Macros.4. Click OK.



11.3.5 Enabling Macros for Excel 2007

Procedure

1. In Excel 2007, click the Office button and then the Excel Options button.The Excel Options dialog box opens.

2. Select Trust Center and click the Trust Center Settings button.The Trut Center dialog box opens.

3. Select Macro Settings.4. Select the Disable all macros except digitally signed macros and Trust access to the VBA project object model

options as indicated below.

5.

11.3.6 Settings of the CtPlConfig.ini File

The CtPlConfig.ini file contains the following options:


... [UserOption] HookIEDisabled =FALSE------------- variables to be added if required ------------- LoadServerXllDisabled =FALSE LoadBlankWorkbookEnabled =FALSE

HookIEDisabled

This variable is used to disable the CtHookIE.dll file. Enabled by default, this file is required in order to work around a referenced Microsoft bug that affects the integration of Excel in Internet Explorer. By applying this workaround solution, you will be able to work online in an SAP Financial Consolidation Excel Web Schedules schedule as well as in an Excel workbook on the local host.

The possible values are:

● FALSE (default value): this library is loaded by the system.● TRUE: The system does not load this library.

LoadServerXllDisabled

This variable is used to check whether or not the version of Excel Web Schedules CtPlanning.xll) on the Web server and on the client are identical.

CautionBy default, this variable is not found in the CtPlConfig.ini file. You should insert it manually if you want to use it.


● FALSE (default value): the version of the CtPlanning.xll file will be checked automatically. This means that if the version on the client computer is earlier than the one on the Web server, then it will automatically be upgraded.

● TRUE: the version of the CtPlanning.xll file will not be checked. This means that the version of SAP Financial Consolidation Excel Web Schedules on the client computer will not be automatically upgraded.

LoadBlankWorkbookEnabled

This variable is used to specify a specific mode in which local changes will not be loaded when the schedule is opened. If enabled, all local changes will be removed when the schedule is corrupted and cannot be opened with them. This is done without querying the database.



NoteBy default, this variable is not found in the CtPlConfig.ini file. You should insert it manually if you want to use it.


● FALSE (default value): the mode is disabled.● TRUE: the mode is enabled. You should proceed as described below. This enables you to open a schedule

even if it is corrupted.1. In the installation folder of the module, open the CtPlConfig.ini file.2. Save and close the file.3. Open a package that contains the uncorrupted and corrupted schedules.4. Open the uncorrupted schedule.5. The schedule opens with its local modeling.6. Open the corrupted schedule.7. The schedule will open without its local modeling.8. To ensure that the schedule will open subsequently, you can select SAP Financial Consolidation > Local

modeling > Remove local modeling.9. Close the package.10. Open the CtPlConfig.ini file again.11. Enter FALSE instead of TRUE.12. Save and close the file.

11.3.7 Configuring SAP Financial Consolidation Excel Web Schedules installation folder

Context

When an Excel Web schedule is opened for the first time, two folders are created:

● The first one is: %UserProfile%\EWS\. It contains all files related to the executable (macro). It is possible to customize a registry key to define the folder once for every time, in which all the macros are going to be downloaded. For example, if you use Citrix, the macros are being downloaded for all users only once, instead of being downloaded each time by each user.For example, this key will be: [HKEY_LOCAL_MACHINE\SOFTWARE\CARTESIS\Magnitude\Planning] "EWSDirectory"="d:\ews"

● The second one is: %UserProfile%\Application Data\SAP\EWS\. It contains all files related to the user settings: log files, ini files.This folder also contains the CtPlConfig.ini file.


12 Installing and configuring under Windows Terminal Services

The Windows Terminal Services architecture supports "application server computing", which enables the application to run on a server for multiple users.

SAP Financial Consolidation clients can be installed in Windows Terminal Services as part of the 3-tier architecture, in which screen changes in the user interface are sent to the individual client computer.

All of the processing in the application will be performed on the Windows Terminal Services server. Regardless of the line speed, the server will be able to send screen changes to the client computer without any loss in performance, using any type of LAN, WAN or other communication network.

Windows Terminal Services also coordinates all of the printing jobs to be performed by managing communication between input/output drivers.

Installing an application in a Windows Terminal Services environment, is different than installing an application in a standard Windows environment.

NoteIf complementary applications are used (e.g. Citrix MetaFrame), additional operations may be necessary (e.g. deploying the application in Citrix MetaFrame). To find out more, contact your software provider.

12.1 Installation modes in Windows Terminal Services

CautionYou should connect with the local system administrator account when installing SAP Financial Consolidation.

To install an application on a Windows Terminal Services server, you must disconnect all users and switch the server to install mode.

You can install an application in Windows TS in two different ways:

● Select Start > Settings > Control Panel and select Add/Remove programs.

NoteWhen you perform the above action, the server will switch automatically to Install mode..

● Enter the following command line to switch to install mode: change user /install.


Installing and configuring under Windows Terminal Services

12.2 Configuring the Windows Terminal Services server

Procedure

1. Once Financial Consolidation is installed, continue in Install mode. Print a SAP Financial Consolidation object (not a schedule or report). For example, print a scope. The printouts are managed by an ActiveX control that is saved the first time that it is called up. You must print a schedule on the SAP Financial Consolidation client on the Terminal Services server to complete the installation.

2. In order to optimize network traffic, you can deactivate the animation in SAP Financial Consolidation using a registry key. To do so, in the registry, create a DWORD type key in HKLM\Software\WOW6432Node\Cartesis\Magnitude\HideMagnitudeProgression.

3. Name the key HideProgressionAnimation.4. Assign the value 1 to the key.

It is also possible to customize a registry key to define the folder once for every time, in which all the macros are going to be downloaded. For example, if you use Citrix, the macros are being downloaded for all users only once, instead of being downloaded each time by each user.

5. To do so, open the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\CARTESIS\Magnitude\Planning] and add the path of the folder to the EWSDirectory value. For example, this key will be: [HKEY_LOCAL_MACHINE\SOFTWARE\CARTESIS\Magnitude\Planning] "EWSDirectory"="d:\ews".

SAP BusinessObjects Financial Consolidation Installation GuideInstalling and configuring under Windows Terminal Services C U S T O M E R 151

13 Installing SAP Financial Consolidation in Standalone Mode

13.1 Introduction to the standard / standalone configuration

The standard / standalone configuration enables you to install SAP Financial Consolidation on decentralized data entry workstations. You can use the Microsoft SQL Server 2008 Express edition to store data at data collection sites.

You perform the following 6 steps to install SAP Financial Consolidation in a standard / standalone configuration:

● Install Microsoft SQL Server 2008 Express Edition● Create an empty database in the SQL Server engine● Install SAP Financial Consolidation● Connect to the Administration console using the CtAdmin.msc tool● Configure the data source● Connect to SAP Financial Consolidation

13.2 Installing SAP Financial Consolidation

Context

RememberAs SAP Financial Consolidation now uses a new setup technology, you are not prompted to uninstall earlier versions of SAP Financial Consolidation but you need to manually uninstall all previous versions via the Windows Control Panel before you can install SAP Financial Consolidation 10.1.

NoteDo not forget to install Adobe Flash Player as it is required on the client site to access the new dashboards.


152 C U S T O M E RSAP BusinessObjects Financial Consolidation Installation GuideInstalling SAP Financial Consolidation in Standalone Mode


Procedure




2. Click Run.If one of the components required is missing or not in the minimum version supported, the List of requirements to install dialog box opens.

CautionThe SAP BusinessObjects User Management Client component is not mandatory. As the UMC setup starts automatically, you can click Cancel and the SAP Financial Consolidation setup will continue normally.




click Next.

The Setup Type window opens.9. Select the Client installation option and click Next.

The Custom setup dialog box for selecting the required components appears.

SAP BusinessObjects Financial Consolidation Installation GuideInstalling SAP Financial Consolidation in Standalone Mode C U S T O M E R 153

10. Select the components you want to install for the standard / standalone configuration.○ Application: If you check this option, all of the components required for running SAP Financial

Consolidation will be installed.○ Local Administration console - Local Data Entry Configuration ONLY: This option enables you to access

the tool used for managing the data sources. This option is active only if the setup detects that you have a SQL Server engine on your machine.

TipIf you want to be able to access the Online Help and the documentation, we recommend that you select the Online help and Documentation options. If you do not select these options here, you will not have access to this functionality once SAP Financial Consolidation is installed. You can, however, install them at a later time.

11. Click Next.

The Ready to install the program dialog box enables you to review your settings before starting the installation.

12. If the settings are correct, click Next.

NoteThe actual installation then begins. Depending on the performance of your computer, the installation may last several minutes. You should not perform any other task until the installation is complete in order to ensure that the application is correctly installed.

Once the installation is complete, the Installation complete dialog box appears.13. Click Finish.


14. Restart your computer.

NoteIf you do not restart your computer, the database will not be migrated and you will not be able to connect to SAP Financial Consolidation.

15. Double-click the ExclusiveModeInStandAlone.reg file located in the Tools subfolder of the SAP Financial Consolidation installation folder.

NoteThis creates a registry key located in [HKEY_LOCAL_MACHINE\SOFTWARE\CARTESIS\Cartesis Finance\StandAlone] "ExclusiveMode"=dword:00000001. This key authorizes the SAP Financial Consolidation server to perform transfer operations usually carried out in exclusive mode. In standalone mode, there is no point in connecting in exclusive mode as only one user will be connected to the server.

Related Information

Configuring the Web Client [page 139]

13.3 Creating a Database

Context

To create a database:

Procedure

1. Select Start > Programs > Microsoft SQL Server > Enterprise Manager.

SQL Server Enterprise Manager will open.2. Click on SQL Server Group to expand it and select the computer where you want to add a database.3. Right-click on Databases and select New Database.

The Database Properties dialog box appears.4. In the General tab, enter the name of the new database in the Name field.5. In the File properties groupbox of the Data Files tab, select the Automatically grow file, By percent and

Unrestricted file growth options as shown below.


6. Click OK.

You should change the properties of the new database.7. To do this, right-click on the database and select Properties as shown above.

The [Database name] Properties dialog box appears.8. Select the Options tab.9. In the Settings groupbox, select the options as shown below.


10. Click OK.

You have finished creating a new database.

13.4 Configuring the Data Source

Context

If you install SAP Financial Consolidation in standalone configuration, where all the components are installed on the same computer, the setup will provide the option of creating automatically a data source if it detects an SQL Server engine on the machine.

You must then configure it, if the default settings do not correspond to your environment.


Procedure

1. In the installation folder of Financial Consolidation, double-click the CtAdmin.msc.2. Open the data source named "Finance".3. Open the Standard Configuration view.

4. Double-click the DbConnectionString parameter.5. Modify the following settings, depending on your configuration:

○ Provider: SQLNCLI. If your database is a SQL Server database, you must leave the default setting.○ Data Source: it corresponds to the database servername.○ Initial Catalog: it corresponds to the database name.○ User ID: by default, the user configured is "sa". You can change it if necessary.○ Password: Change the password.

6. click OK.7. Restart the data source.

13.5 Connecting to SAP Financial Consolidation

Context

As the database has been migrated automatically, you can connect to SAP Financial Consolidation.

Procedure

1. Select Start > All Programs > SAP BusinessObjects and click on Financial Consolidation.


NoteIn the installation folder, you can also double-click on the Finance.exe file.

The Start the Application dialog box appears.

NoteIf the Data source manager groupbox does not appear, click Options.

2. In the Data source manager groupbox, select the machine where the list of data sources is located. As you are in a standard local configuration, you should select the Local option.

3. In the Data source groupbox, select the name of the data source you want to use. If you opted to create an empty database, the Finance data source appears.

4. In the Authentication groupbox, enter the username and password. When you connect to Financial Consolidation for the first time, the default user will be ADMIN and there will be no password.

NoteThis login and password is not to be confused with the SQL login and password.

NoteWhen you connect to Financial Consolidation for the first time, the ADMIN user appears by default. This enables you to connect to Financial Consolidation and create different users and user profiles, which you can then use when reconnecting.


5. Click OK.


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

SAP BusinessObjects Financial Consolidation Installation GuideImportant Disclaimers and Legal Information C U S T O M E R 161

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.

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

Date post:	24-May-2018
Category:	Documents
Upload:	vodung
View:	233 times
Download:	3 times

SAP BusinessObjects Financial Consolidation … · 4 Preparing to install SAP Financial...

Documents