SAP Cloud for Planning has been designed as a people-centric cloud application, which will help to make your financial planning, forecasting, and business analysis work simpler and more enjoyable!

RADICALLY SIMPLIFY PLANNING

BPC EPM Scaledata formatting with Dimension member property and formula - SAP BPC 10.1 NW

- Created by Krish Raju.

Background: Few of the BPC Financial reports are to be reported in 1000s and millions.  This can be achieved using simple dynamic formatting using the Excel standard conditional formatting using the Excel custom formatting function (#,##0.0,,). There are few limitations in using this format. The cell values are displayed based on the scaling in 1000s, but the actual underlying values are not changed.

For example in the below Excel formatting for in 1000s, the cell displays correctly but the actual cell values is still the full numeric value. This causes issue while converting the worksheet to standard Excel for circulation. If you copy the report and paste it in Excel, the scaling is lost.

Suggested Solution - use EPMScaleData with Dimension Member formatting:  There are many formatting options available within EPM FormattingSheet function and can also be implemented for specific Dimension member property. This helps to retain the Local member formula without being overwritten by the dynamic formatting

This solution works well in BPC 10.0 / 10.1 and EMP SP18. I am sure this will still work in the higher EPM SP level as well.

Benefits of the formatting option.

1. Scaling is automatically applied in EPM report for the specific Olap member dimension and property. Scaling is automatically applied to member & children even if drill-down in EPM reports
2. EPM Local members and formulas in rows and columns are not disturbed.
3. EPM Report copied and pasted to a new Excel report as value still retains its scaling.
4. Scaling and report is accurate as the scaling parameters Dimension members are fixed based on page axis values.

Steps to implement the EPM Scaledata formatting

1. In the EPMformatting sheet Add Dimension member and property for Account dimension.
2. Update the EMPScaledata formula in the “Use” column in the Dimension member / Property section of the formatting sheet.
3. Update Scaling values in the report

Step#1 – Update Dimension member property

Make sure the formatting is Active by checking the box in the formatting sheet.

Account member property FIN_STMT = PL / BS used to exclude Local members from the default formatting, Local members uses Excel formula and in few cases % formatting.

In the Dimension/ Member formatting section of formatting sheet. Click “Add Member property”, go to Property Selection tab.

Select fist set of Dimension and property

Click “Add Multiple selection”

Select next set of Dim and property

Click Add to Multiple Selection (if necessary)

Go to Multiple selection overview

Click OK

The Dimension member and property selection is displayed in the formatting sheet.

Number formatting - In the Data column of the formatting sheet, update number and font format

Step#2 - Update the EMPScaledata formula in the “Use” column in the EPMFormatting Sheet.

In the EPMFormatting Sheet in “Use” column of the formatting sheet, copy the below formula and adjust the “empmememberid” cell references based on the actual cell in the report sheet. – For example the scaling factor is in cell D1 and cell A6 is Audit dimension in the report.

EPM Scale data formula:  (Content = =(epmscaledata(, $d$1, epmmemberid($a$6), epmmemberid($a$7),  epmmemberid($a$8), epmmemberid($a$9), epmmemberid($a$10), epmmemberid($a$11),epmmemberid(b$17), epmmemberid(b$18), epmmemberid(b$19), epmmemberid($a20))))

Note: It is recommended to include all the Dimension members used in the report in the scale formula. If the dimendsion members are not in the formaula, the report values are derived based on the EPM Context members even if this is defined in the Page axis of the report.

For example, in the below report all the page axis Dimension dell referenced in the formatting formula.

Step# 3- Maintain Scaling factor: In the Excel report, maintain scaling factor for 1000 and Million in one of the cell (cell D1 in this example) with drop-down selection option.

Step#4 – Apply Dynamic formatting setting in the Edit report options tab

As explained earlier this formatting is applied to all Olap member values. Local Member values are derived in the report and hence it will use the original format or specifically defined format. This is to prevent overwriting special format used for ratio percentages.

Krish Raju

Raju.krish@yahoo.com

Installing SAP Disclosure Management 10.1

This document explains what is installed during a server installation of Disclosure Management 10.1 In the following articles I will further explain the configuration and installation/configuration of additional components (Task Engine, XBRL, client etc.)

The Disclosure Management installation files can be found here:

https://support.sap.com/software/installations.html

For the Installation Guide, check:

http://help.sap.com/bodm

Installation procedure

1. Starting the installation

Unzip the “51049916.zip” file and go to the DM_SERVER_APPL_SERVER_10_1 that has been created when extracting.

Run the DMAPPLSERV00.exe file (note: this is DM 10.1 SP00, the zip also contains the Service Packs (SP01, SP02, SP03) and if you have never installed Disclosure Management, you can start with any SP installation)

2. The Welcome screen appears

Make sure it mentions the SAP Disclosure Management application server

3. The prerequisites

Note: if prerequisites are not met, you need to install these separately, they are not included in the DM installer

4. SQL Server details

SAP Disclosure Management will create a DB on MS SQL Server (no other RDBMS are supported)

On the first screen, the server, DB name and the user/password are provided

Note: this user/password is for the creation of the DB, it is not the authentication used by the application to connect to the DB at run-time

5. Database server credentials

Here the user/password is provided that will be used by Disclosure Management to connect to the DB

Note: if the user does not exist, the install procedure will create it

6. Application server settings

Specify settings for the DM application. These are mostly IIS settings (port, binding etc.)

Note: it is recommended to install DM as a 64-bit application

The default path where DM will be deployed is C:\inetpub\wwwroot\SAP\SAP Disclosure Management

7. Application server security settings

DM can be installed with Basic or AD authentication (note: this is for the actual login to the DM application, it is not related to the SQL server authentication)

8. Notification for user “admin”

When using Basic authentication, a user will be created (admin). Note the password

9. After the installation completes, this message should appear

Some issues that may occur during the installation:

Error 27506: Error executing SQL script during Server Installation

Several issues after Server Installation

HTTP Error 500.21 - Internal server Error during Server Installation

How to disable WebDAV Access

Error 27502 Cannot Connect to Microsoft SQL Server during DMS Service Pack installation

Disclosure Management and Load Balancing /Failover cluster

Web Farm/ Cluster Configuration for Connection Strings

Installation XBRL - Java JRE 1.7 not found

What has been installed?

Let’s check what the installer has installed.

1. SQL Server

A database called “DisclosureManagement” (based on step 4.) and a user called “CDMUser” (based on step 5.) The user has access to the DM database (2 roles are created)

Within the DB, the table “Security.Users” has 1 record, the user “Admin” (based on step 8.)

2. Application server (IIS)

Within IIS, DM will have created its own application pool

The main DM website is also deployed (various settings based on step 6.)

The code and configuration files are in C:\inetpub\wwwroot\SAP\SAP Disclosure Management

(again, based on step 6.)

The “web.config” file will have details on authentication mode used (Basic or Active Directory)

Testing the installation

You should be able to connect to URL http://dsm101/Account/LogOn

(Note: based on selected settings, this may be http://server:/<dm_site>:port/Account/Logon or  http://server:/<dm_site>:port/Account/LogonAD)

With the login/password given in step 8.you should get this screen, indicating the SAP Disclosure Management application server installation is successfully completed.

This document explains the steps to upgrade the Disclosure Management 10.1 application server.

Introduction

There are 2 types of upgrades, Service Packs and Patches.

Unlike many other SAP products, the SPs and Patches of Disclosure Management 10.1 are not cumulative, so you have to be careful with the upgrade path.

In general, you cannot skip SPs, so if you are on DM 10.1 SP02 and want to upgrade to DM 10.1 SP05, you would need to install SP03, SP04 and SP05

With patches, there is a small difference. If you are on a patch within a SP and there have been subsequent patches within that SP, you need to install these, before continuing with the next SP

An example:

Assume these are the versions available

DM 10.1 SP00

DM 10.1 SP01

DM 10.1 SP01patch1

DM10.1 SP01patch2

DM 10.1 SP02

DM 10.1 SP02patch1

DM 10.1 SP03

DM 10.1 SP04

You are on DM 10.1 SP01 and want to upgrade to DM 10.1 SP04

--> You need to install SP02, SP03, SP04

You are on DM 10.1 SP01patch1 and want to upgrade to DM 10.1 SP04

-->You need to install SP01patch2, SP02, SP03, SP04

Note: this also applies to DM 10.0 so if you are upgrading to DM 10.1 you need to go through the SPs of DM 10.0 and DM 10.1

If you are not sure on what has been installed, check via the following SQL:

select*from Setup.DMSetupSchemaVersion

This provides a history of all SPs and patches that have been installed (this should not show any ‘gaps’)

Installation of Service Pack

1. Download the file from SMP (http://service.sap.com)

In this example we are upgrading to DM 10.1 SP02

2. Execute the file

The initial wizard pop-up shows you are installing an SP for the DM application server

3. Verification and DB backup

Check on the screen that you are performing a correct SP upgrade. In this case, it shows we are going from SP01 to SP02, which is correct.

You can decide to make a backup of the DM database (this is optional, but recommended)

Note: if you do make the backup, it will be placed in C:\Program Files\Microsoft SQL Server\MSSQLxx.MyInstance\MSSQL\Backup

For example: C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup

4. Installation completes

5. Verify by logging in and checking the “About” box

This should give the new SP level (and the table Setup.DMSetupSchemaVersion will have been updated)

The steps for a patch installation are identical.

Introduction

This document outlines the steps to install the Disclosure Management Client. The client is an add-in that will be visible in the Microsoft Office products (i.e. Excel, Word, PowerPoint).

Unlike the application server, you can directly install the required Service Pack you need. Be aware: the client version needs to match the server, so do not have the server on DM 10.1 SP04 and access it with a DM 10.1 SP02 client.

To upgrade the client, first uninstall the current version and then proceed with the installation of the required SP level.

Installation

1. Download the installation file from SMP (http://service.sap.com)

2. Initial screen from Installation Wizard

Ensure you are running the client installation

3. The prerequisites

Note: the DM 10.1 client is still a pure 32-bit add-in and cannot be installed in Office 64-bit

4. Installation path

By default, the client will be installed in C:\Program Files (x86)\SAP\SAP Disclosure Management

5. Installation runs…

6. Installation completes successfully

7. Verify the installation

In Excel, you should have an option in the ribbon called “SAP Disclosure Management”

This is a COM Add-in in Excel (adxloader.dll)

Note: after the installation, the add-in is also visible in other Office products – no additional installation is needed

For example, in MS PowerPoint

Uninstalling the DM client

If the DM 10.1 client needs to be uninstalled (for example, for an upgrade), use the Windows “Programs” feature and select “Uninstall”

Silent installation

To perform a silent installation of the Dsiclosure Management Client, you can use the following steps;

1. Rename the setup executable to DMClient.exe

2. Open a command prompt in administrator mode and navigate to the directory where the setup executable is located.

3. Execute the following command:

  DMClient.exe /s /v/qn

4. Monitor the task manager, you will see the executable running and will install the DM client.

After the executable has disappeared from the task manger it means the installation has completed.

Some possible issues

• Unable to uninstall client - Error 1720
• Unable to install Disclosure Management Client Support Package

Introduction

The Task Engine is used to perform long-running and resource-consuming tasks in SAP Disclosure Management. The task engine is a Microsoft Windows service that enables you to decouple resource-consuming tasks from the SAP Dislcosure Management server application running on IIS, thus avoiding performance impairments when working with SAP Disclosure Management.

Installation

1. Installation file

From the initial downloaded files (see Installing SAP Disclosure Management 10.1) go to the \DATA_UNITS\DM_SERVER_APPL_SERVER_10_1 subfolder and execute the file

2. Installation wizard welcome screen

Ensure you are installing the Task Engine

3, The prerequisites

4. The installation folder

By default, the Task Engine will be installed in C:\Program Files\SAP\SAP Disclosure Management TaskEngine\

5. Specify the database that the TaskEngine will use

Note: this obviously has to be the same as the main DM application server is using

6. Define user/password for access to the database

It is recommended to use the same user and password as the DM application server is using

7. Installation completes successfully

What has been installed?

1. The required files are installed (C:\Program Files\SAP\SAP Disclosure Management TaskEngine\)

Within this folder, there is a configuration file, called “SAP.DM.TaskEngine.Console.exe.config”

This has a BaseAddress (URL to be used later)

2. In the Windows Services, the Task Engine is listed (and should be started)

3. The Task Engine uses the DM web-services

These web-services were installed by the DM application server installation. You can check in IIS, under the DM website there is a folder called Webservices and this contains 1 subfolder called PublicAPI.

Within this, there is one WCF service file called “DataImport.svc”

If you browse this file, you should get the following page – this indicates the web-services are running

Configuring the Task Engine

In the DM application, some settings need to be configured for the Task Engine

1. System configuration

In Administration, System configuration, open the ‘Miscellaneous’ tab

Specify the Task Engine web services URL (see step 1 of the previous section)

Note: the 2605 port is not mandatory, you can change this (both in the “SAP.DM.TaskEngine.Console.exe.config” file and in this tab)

2. Landscape

Specify the IP (server name or FQDN) and port

3. Check the logs

In the Administration, Log files, you should have access to the “Log files task engine”

Note: the log files are physically stored on the application server and you can control this by setting the path in the “Log.config” (in C:\Program Files\SAP\SAP Disclosure Management TaskEngine)

Verifying the Task Engine

To test that the Task Engine is working correctly, you must perform an operation that uses the Task Engine. One of these is the “publish period” function.

1. Setup ‘publishing

In Administration, System Config, open the “Publishing” tab

Define a folder (and option password) where the published archives will be stored

2. Publish a period

3. Result

The Task should start

Another function that uses the Task Engine, is the integration between DM and SAP Financial Consolidation.

There is an excellent video that explains this function: Integrate SAP Financial Consolidation with SAP Disclosure Management

After the initial installation (see Installing SAP Disclosure Management 10.1), we need to configure a few basic items to get the application running.

1. Login with the user that was created during the installation

Add the details (email, name) and change the password

2. Save this, you should now have access to this page

System configuration

1. Select the “Administration” tab. Option “System Configuration”

On the tab “E-mail”, configure the email server (and account used). Emails are used in the workflow

2. Miscellaneous tab

Here you define some display options (company, name, description) that are shown in the browser tabs

Also configure the root folder of the web-service.

Note: sometimes this option only works with IP-address or FQDN (if the DNS cannot be resolved)

3. Landscape tab

Define the Application server, with the server-name and port

(in example below, DSM101, 80)

4. Verify logs

Check that the application server is correctly defined, by going to the option “Administration”, “Logs”, “Log files Application server”

Note: the logs are physically stored in C:\inetpub\wwwroot\SAP\SAP Disclosure Management\Logs\AppServer (on the application server)

See also: How to configure log files in version 10.1

Plugins

Disclosure Management uses a number of plugins for document conversion and rendering (e.g. PDF creation, XBRL preview, Excel-to-PDF etc.)

These plugins are .dll files that are uploaded into the application and subsequently registered.

It is important to have the plugins that match the application version (so, there are SP-specific plugins)

You can download the plugins from SMP (http://service.sap.com) and which ones are needed depends on your business needs.

1. Download the plugin (they are zipped in an archive)

2. On the “Administration”, “Plugins” option

Browse to the downloaded file (use the .zip directly, there is no need to unzip the files)

3. Upload file

4. Register

Click register and answer ‘yes’

5. Result – the plugins are registered

Repeat these steps for all required plugins.There are currently 12 plugins

• DM E-BILANZ PLUGIN 10.1
• DM EXCEL TO PDF PLUGIN 10.1
• DM REPORTING PLUGINS 10.1
• EU XBRL CONS. VAL. PLUGIN 10.1
• EU XBRL EXCEL PREV PLUGIN 10.1
• EU XBRL VALIDATION PLUGIN 10.1
• EU XBRL WEB PREV PLUGIN 10.1
• UK HMRC IXBRL CREAT. PLG 10.1
• US SEC CALC TRACE PLUGIN 10.1
• US SEC PREVIEW PLUGIN 10.1
• US SEC VALIDATION PLUGIN 10.1
• US SEC XBRL CREATION PLG 10.1

User

1. Go to “Administration”, “Users”

Edit the “Admin” user

2. In the Roles tab

Select all the pre-defined roles

3. Result

User now has access to all functions (Report, Monitoring, Settings, XBRL Factory, Transport, and Administration)

With this is in place, you have completed the initial configuration and can continue functional setup (define users, periods, reports etc.)

Advanced settings

Changing DB connection

If you need to change the database that Disclose Management uses (or the user/password needs to be changed), please follow this procedure.

1. Configuration file

The connection details are stored in

C:\inetpub\wwwroot\SAP\SAP Disclosure Management\bin\cundus.enterpriseReporting.Services.dll.config

2. Open the file with an (XML) editor

The section <connectionStrings> contains the connection details (but is encrypted)

3. Highlight the section as per below and delete it

4. Add back the > in <connectionStrings>

5. Add the connection string

<addconnectionString="Data Source=SQLServerName;Initial Catalog=DMDatabaseName;Integrated Security=False; User Id=DMDatabaseUser; Password=DMDatabaseInitial1;MultipleActiveResultSets=True" name="enterpriseReporting" providerName="System.Data.SqlClient"></add>

Use the following:

1. Data Source=SQLServerName --> name of SQL Server
2. Initial Catalog=DMDatabaseName --> name of DM database
3. User Id=DMDatabaseUser --> SQL user who has access to DB
4. Password=DMDatabaseInitial1 --> SQL user’s password

6. Save the file

7. Restart the DM website

After restart, the connection string will be encrypted again, and DM will now connect to the new DB

Change user in DB

If you are locked out of the application and do not remember the password that was used in the initial installation, you can use the following to change the password

1. Open MS SQL Management Studio

Run the following SQL (if the name was still “Admin” you can use the 1^st, if the name was changed, use the 2^nd)

updateSecurity.Users

setpassword='/fRdD/EnzjCZPOhV1G0N/A==', IsActive='True'

wherelogin='Admin'

updateSecurity.Users

setpassword='/fRdD/EnzjCZPOhV1G0N/A==', IsActive='True'

whereID=1

After this, you can login with password  = super (all lowercase)

Introduction

The SAP Disclosure Management XBRL service is part of the SAP Disclosure Management Server, but is delivered separately. This enables the XBRL Service to be installed on a different machine.

Installation

1. Installation file

From the initial downloaded files (see Installing SAP Disclosure Management 10.1) go to the DATA_UNITS\DM_SERVER_XBRL_SERVICE_10_1\WIN32 sub-folder and execute the file

2. Wizard welcome screen

Make sure you are installing the XBRL Service

3. The prerequisites

4. The installation folder

By default, the XBRL Service will be installed in C:\Program Files\SAP\SAP Disclosure Management XBRL Service

5. Installation completes successfully

Configuring the XBRL Service

1. Service

Check that the SAP Disclosure Management XBRL Service is running (start it up if needed)

2. Configuration file

Open  C:\Program Files\SAP\SAP Disclosure Management XBRL\ServicecsfService_ValidationServiceHost.exe.config and set the Java path

Note: you can find the path in the Java parameters

3. System configuration

Login to the DM application

In Administration, System configuration, open the ‘Landscape’ tab

Specify the IP (server name or FQDN) and port. By default, the XBRL services uses port 2981

4. Check the logs

In the Administration, Log files, you should have access to the “Log files XBRL service”

Note: the log files are physically stored on the application server and you can control this by setting the path in the “Log.config”  (C:\Program Files\SAP\SAP Disclosure Management XBRL Service)

“The content has been moved to SCN WIKI, the new link is: RELEASED NOTES AND KBAS - March 2015 - Enterprise Performance Management - SCN Wiki

-- This Blog will be removed by Dec 31, 2015.”

KBAs and notes released in the last 30 days(as of 03/26/2015)

Introduction

You can use the Archiving Tool to store historical consolidated data in archive databases and still access it from the Financial Consolidation application.

This document shows what technically happens at DB level to the tables

Procedure

The consolidations in FC are stored in ct_coXXXX tables. The XXXX indicates a unique identifier and the data for each consolidation definition will be stored in one single table.

You can determine what table holds the data by using this SQL

/* Consolidated */

select p.id, a.name as'category',

ltrim(str(1900+(p.updper&536608768)/262144))+'.'+

right('00'+ltrim(str((p.updper&253952)/8192)),2)as'period',

1. b.name as'scope',
2. c.name as'variant',
3. d.name as'currency'

from ct_coref p, ct_phase a, ct_scope_code b, ct_variant c, ct_curncy d

where a.id=p.phase and

1. p.scope = b.id and
2. p.variant=c.id and
3. p.curncy = d.id

For example, the consolidation data for {A – 2016.01 – SAP – SAP – USD} is stored in ct_co0050

When you archive (for full documentation, see section "12 Archiving tool" of the "SAP BusinessObjects Financial Consolidation Administrator's Guide"

you first connect to the source database (and also specify the target database, in my example FC_BAK)

You then select the consolidation(s) you want to archive.

In my example, I take the consolidation {A – 2016.01 – SAP – SAP – USD}

When selecting "Execute" the system will show what table will be backed up. Here you can verify that the correct ct_coXXXX table is selected (in this example, it is ct_co0050)

The archiving completes (100%)

What has been done in DB's

1. In the original DB (FC10) the table has been deleted

2. In the backup database (FC_BAK, in this example), the table has been created

3. In the original DB, there is now a ‘view’ ct_co0050 which is linked to the archived table (i.e. a view to a different DB schema)

The archive tool uses this during the 'archive' process

CREATE VIEW dbo.viewname

AS

  SELECT column_names

    FROM [AnotherServer].[AnotherServerDatabase].dbo.[Table1];

Result

The result is that on the original database, the archiving of the consolidation table is completely transparent

If you run an SQL (e.g. FC report, Cube Designer deployment), the result will still be the same, although the table is physically in a different DB

Introduction

Data in Microsoft Office Excel tables of data caches often has no unique identifiers. To transform data into context-related data with a unique ID, you define ER named ranges and assign a name starting with "ER_"

You can tag and save each value of a range. With the Tag Monitor, you can track the changes of specific report values and provide a concise overview of changes applied to those values. For example you can see how the total amount of liabilities has been modified over the time the annual report has been elaborated.

Procedure to create ER range

1. Table in Excel

Let's assume you have a table like this

2. Define the ranges

You need to have the following ranges

ER_KEYS_<tag>

ER_LABELS_<tag>

ER_VALUES_<tag>_<value_tag>

Note: the ER_VALUES can be repeated n times

You can create a range, by simply selecting the cells (e.g. A1..A5) and then entering the name in the Excel 'name box'

Note: you can also do this in Excel's "Name Manager" (CTRL-F3)

In the end, you should end up with something like this :

3. Validate your ER range

Select the option "List Ranges" from the DM ribbon. You should see the "Valid" message

Note: a possible error could be that your keys are not unique

4. Data linking the ER range

In the Data Link the named range will now appear with its <tag> name. In this example, Q4TABLE

Note also that the ER_KEYS values are not displayed, only the labels and values

5. Monitor changes

In the Tag monitor you can now track the changes of the ER Named ranges

Additional Information

For additional information, please refer to the DM User Guide

Introduction

This document outlines how to install Disclosure Management services packs and patches via a command prompt

Why using the command prompt

When you perform the initial installation of Disclosure Management (see Installing SAP Disclosure Management 10.1 ) the system will prompt for DB server, DB name, user + pwd

All this information is stored (encrypted) in a registry key. When you run a Service Pack (or patch), this information is re-used, so that the DB can automatically be updated via scripts, without any user prompts

However, this means that if any of these parameters changes (for example, you moved servers, the pwd changed etc.) the patch installation will fail. This is a typical error message you may get

Currently, the only option is to run the SP / patch installations via the commend prompt

Note: there is no way to update the registry key with the new information

Procedure

The installation of Service packs via command prompt is explained in this note:

Install SAP Disclosure Management with SQL server parameters

Here is an example of how to perform this

1. The current version is 10.1 SP05PL01

2. The DB is also at this level (verified with "SELECT *  FROM [dsm].[Setup].[DMSetupSchemaVersion]" )

3. The server and DB used (i.e. where you moved the DB to)

4. Download the SP / patch and place it in a folder on the application server

5. Open the CMD prompt (with Admin rights)

6. Go to the folder where the SP has been downloaded to

As the note explains, the syntax is:

setup.exe /v"IS_SQLSERVER_DO_NOT_USE_REG=1 IS_SQLSERVER_SERVER=UsedServer IS_SQLSERVER_DATABASE=usedDB IS_SQLSERVER_AUTHENTICATION=1 IS_SQLSERVER_USERNAME=DBUser IS_SQLSERVER_PASSWORD=DBPwd"

Note: you can replace setup.exe with the actual SP executable name

7. The notification screens will still appear as normal

8. The installation will complete and you can verify in the DB that the SQL scripts were executed on the correct DB

BPC EPM Scaledata formatting with Dimension member property and formula - SAP BPC 10.1 NW

- Created by Krish Raju.

Background: Few of the BPC Financial reports are to be reported in 1000s and millions.  This can be achieved using simple dynamic formatting using the Excel standard conditional formatting using the Excel custom formatting function (#,##0.0,,). There are few limitations in using this format. The cell values are displayed based on the scaling in 1000s, but the actual underlying values are not changed.

For example in the below Excel formatting for in 1000s, the cell displays correctly but the actual cell values is still the full numeric value. This causes issue while converting the worksheet to standard Excel for circulation. If you copy the report and paste it in Excel, the scaling is lost.

Suggested Solution - use EPMScaleData with Dimension Member formatting:  There are many formatting options available within EPM FormattingSheet function and can also be implemented for specific Dimension member property. This helps to retain the Local member formula without being overwritten by the dynamic formatting

This solution works well in BPC 10.0 / 10.1 and EMP SP18. I am sure this will still work in the higher EPM SP level as well.

Benefits of the formatting option.

1. Scaling is automatically applied in EPM report for the specific Olap member dimension and property. Scaling is automatically applied to member & children even if drill-down in EPM reports
2. EPM Local members and formulas in rows and columns are not disturbed.
3. EPM Report copied and pasted to a new Excel report as value still retains its scaling.
4. Scaling and report is accurate as the scaling parameters Dimension members are fixed based on page axis values.

Steps to implement the EPM Scaledata formatting

1. In the EPMformatting sheet Add Dimension member and property for Account dimension.
2. Update the EMPScaledata formula in the “Use” column in the Dimension member / Property section of the formatting sheet.
3. Update Scaling values in the report

Step#1 – Update Dimension member property

Make sure the formatting is Active by checking the box in the formatting sheet.

Account member property FIN_STMT = PL / BS used to exclude Local members from the default formatting, Local members uses Excel formula and in few cases % formatting.

In the Dimension/ Member formatting section of formatting sheet. Click “Add Member property”, go to Property Selection tab.

Select fist set of Dimension and property

Click “Add Multiple selection”

Select next set of Dim and property

Click Add to Multiple Selection (if necessary)

Go to Multiple selection overview

Click OK

The Dimension member and property selection is displayed in the formatting sheet.

Number formatting - In the Data column of the formatting sheet, update number and font format

Step#2 - Update the EMPScaledata formula in the “Use” column in the EPMFormatting Sheet.

In the EPMFormatting Sheet in “Use” column of the formatting sheet, copy the below formula and adjust the “empmememberid” cell references based on the actual cell in the report sheet. – For example the scaling factor is in cell D1 and cell A6 is Audit dimension in the report.

EPM Scale data formula:  (Content = =(epmscaledata(, $d$1, epmmemberid($a$6), epmmemberid($a$7),  epmmemberid($a$8), epmmemberid($a$9), epmmemberid($a$10), epmmemberid($a$11),epmmemberid(b$17), epmmemberid(b$18), epmmemberid(b$19), epmmemberid($a20))))

Note: It is recommended to include all the Dimension members used in the report in the scale formula. If the dimendsion members are not in the formaula, the report values are derived based on the EPM Context members even if this is defined in the Page axis of the report.

For example, in the below report all the page axis Dimension dell referenced in the formatting formula.

Step# 3- Maintain Scaling factor: In the Excel report, maintain scaling factor for 1000 and Million in one of the cell (cell D1 in this example) with drop-down selection option.

Step#4 – Apply Dynamic formatting setting in the Edit report options tab

As explained earlier this formatting is applied to all Olap member values. Local Member values are derived in the report and hence it will use the original format or specifically defined format. This is to prevent overwriting special format used for ratio percentages.

Krish Raju

Raju.krish@yahoo.com

Installing SAP Disclosure Management 10.1

This document explains what is installed during a server installation of Disclosure Management 10.1 In the following articles I will further explain the configuration and installation/configuration of additional components (Task Engine, XBRL, client etc.)

The Disclosure Management installation files can be found here:

https://support.sap.com/software/installations.html

For the Installation Guide, check:

http://help.sap.com/bodm

Installation procedure

1. Starting the installation

Unzip the “51049916.zip” file and go to the DM_SERVER_APPL_SERVER_10_1 that has been created when extracting.

Run the DMAPPLSERV00.exe file (note: this is DM 10.1 SP00, the zip also contains the Service Packs (SP01, SP02, SP03) and if you have never installed Disclosure Management, you can start with any SP installation)

2. The Welcome screen appears

Make sure it mentions the SAP Disclosure Management application server

3. The prerequisites

Note: if prerequisites are not met, you need to install these separately, they are not included in the DM installer

4. SQL Server details

SAP Disclosure Management will create a DB on MS SQL Server (no other RDBMS are supported)

On the first screen, the server, DB name and the user/password are provided

Note: this user/password is for the creation of the DB, it is not the authentication used by the application to connect to the DB at run-time

5. Database server credentials

Here the user/password is provided that will be used by Disclosure Management to connect to the DB

Note: if the user does not exist, the install procedure will create it

6. Application server settings

Specify settings for the DM application. These are mostly IIS settings (port, binding etc.)

Note: it is recommended to install DM as a 64-bit application

The default path where DM will be deployed is C:\inetpub\wwwroot\SAP\SAP Disclosure Management

7. Application server security settings

DM can be installed with Basic or AD authentication (note: this is for the actual login to the DM application, it is not related to the SQL server authentication)

8. Notification for user “admin”

When using Basic authentication, a user will be created (admin). Note the password

9. After the installation completes, this message should appear

Some issues that may occur during the installation:

Error 27506: Error executing SQL script during Server Installation

Several issues after Server Installation

HTTP Error 500.21 - Internal server Error during Server Installation

How to disable WebDAV Access

Error 27502 Cannot Connect to Microsoft SQL Server during DMS Service Pack installation

Disclosure Management and Load Balancing /Failover cluster

Web Farm/ Cluster Configuration for Connection Strings

Installation XBRL - Java JRE 1.7 not found

What has been installed?

Let’s check what the installer has installed.

1. SQL Server

A database called “DisclosureManagement” (based on step 4.) and a user called “CDMUser” (based on step 5.) The user has access to the DM database (2 roles are created)

Within the DB, the table “Security.Users” has 1 record, the user “Admin” (based on step 8.)

2. Application server (IIS)

Within IIS, DM will have created its own application pool

The main DM website is also deployed (various settings based on step 6.)

The code and configuration files are in C:\inetpub\wwwroot\SAP\SAP Disclosure Management

(again, based on step 6.)

The “web.config” file will have details on authentication mode used (Basic or Active Directory)

Testing the installation

You should be able to connect to URL http://dsm101/Account/LogOn

(Note: based on selected settings, this may be http://server:/<dm_site>:port/Account/Logon or  http://server:/<dm_site>:port/Account/LogonAD)

With the login/password given in step 8.you should get this screen, indicating the SAP Disclosure Management application server installation is successfully completed.

This document explains the steps to upgrade the Disclosure Management 10.1 application server.

Introduction

There are 2 types of upgrades, Service Packs and Patches.

Unlike many other SAP products, the SPs and Patches of Disclosure Management 10.1 are not cumulative, so you have to be careful with the upgrade path.

In general, you cannot skip SPs, so if you are on DM 10.1 SP02 and want to upgrade to DM 10.1 SP05, you would need to install SP03, SP04 and SP05

With patches, there is a small difference. If you are on a patch within a SP and there have been subsequent patches within that SP, you need to install these, before continuing with the next SP

An example:

Assume these are the versions available

DM 10.1 SP00

DM 10.1 SP01

DM 10.1 SP01patch1

DM10.1 SP01patch2

DM 10.1 SP02

DM 10.1 SP02patch1

DM 10.1 SP03

DM 10.1 SP04

You are on DM 10.1 SP01 and want to upgrade to DM 10.1 SP04

--> You need to install SP02, SP03, SP04

You are on DM 10.1 SP01patch1 and want to upgrade to DM 10.1 SP04

-->You need to install SP01patch2, SP02, SP03, SP04

Note: this also applies to DM 10.0 so if you are upgrading to DM 10.1 you need to go through the SPs of DM 10.0 and DM 10.1

If you are not sure on what has been installed, check via the following SQL:

select*from Setup.DMSetupSchemaVersion

This provides a history of all SPs and patches that have been installed (this should not show any ‘gaps’)

Installation of Service Pack

1. Download the file from SMP (http://service.sap.com)

In this example we are upgrading to DM 10.1 SP02

2. Execute the file

The initial wizard pop-up shows you are installing an SP for the DM application server

3. Verification and DB backup

Check on the screen that you are performing a correct SP upgrade. In this case, it shows we are going from SP01 to SP02, which is correct.

You can decide to make a backup of the DM database (this is optional, but recommended)

Note: if you do make the backup, it will be placed in C:\Program Files\Microsoft SQL Server\MSSQLxx.MyInstance\MSSQL\Backup

For example: C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup

4. Installation completes

5. Verify by logging in and checking the “About” box

This should give the new SP level (and the table Setup.DMSetupSchemaVersion will have been updated)

The steps for a patch installation are identical.

Introduction

This document outlines the steps to install the Disclosure Management Client. The client is an add-in that will be visible in the Microsoft Office products (i.e. Excel, Word, PowerPoint).

Unlike the application server, you can directly install the required Service Pack you need. Be aware: the client version needs to match the server, so do not have the server on DM 10.1 SP04 and access it with a DM 10.1 SP02 client.

To upgrade the client, first uninstall the current version and then proceed with the installation of the required SP level.

Installation

1. Download the installation file from SMP (http://service.sap.com)

2. Initial screen from Installation Wizard

Ensure you are running the client installation

3. The prerequisites

Note: the DM 10.1 client is still a pure 32-bit add-in and cannot be installed in Office 64-bit

4. Installation path

By default, the client will be installed in C:\Program Files (x86)\SAP\SAP Disclosure Management

5. Installation runs…

6. Installation completes successfully

7. Verify the installation

In Excel, you should have an option in the ribbon called “SAP Disclosure Management”

This is a COM Add-in in Excel (adxloader.dll)

Note: after the installation, the add-in is also visible in other Office products – no additional installation is needed

For example, in MS PowerPoint

Uninstalling the DM client

If the DM 10.1 client needs to be uninstalled (for example, for an upgrade), use the Windows “Programs” feature and select “Uninstall”

Silent installation

To perform a silent installation of the Dsiclosure Management Client, you can use the following steps;

1. Rename the setup executable to DMClient.exe

2. Open a command prompt in administrator mode and navigate to the directory where the setup executable is located.

3. Execute the following command:

  DMClient.exe /s /v/qn

4. Monitor the task manager, you will see the executable running and will install the DM client.

After the executable has disappeared from the task manger it means the installation has completed.

Some possible issues

• Unable to uninstall client - Error 1720
• Unable to install Disclosure Management Client Support Package

Introduction

The Task Engine is used to perform long-running and resource-consuming tasks in SAP Disclosure Management. The task engine is a Microsoft Windows service that enables you to decouple resource-consuming tasks from the SAP Dislcosure Management server application running on IIS, thus avoiding performance impairments when working with SAP Disclosure Management.

Installation

1. Installation file

From the initial downloaded files (see Installing SAP Disclosure Management 10.1) go to the \DATA_UNITS\DM_SERVER_APPL_SERVER_10_1 subfolder and execute the file

2. Installation wizard welcome screen

Ensure you are installing the Task Engine

3, The prerequisites

4. The installation folder

By default, the Task Engine will be installed in C:\Program Files\SAP\SAP Disclosure Management TaskEngine\

5. Specify the database that the TaskEngine will use

Note: this obviously has to be the same as the main DM application server is using

6. Define user/password for access to the database

It is recommended to use the same user and password as the DM application server is using

7. Installation completes successfully

What has been installed?

1. The required files are installed (C:\Program Files\SAP\SAP Disclosure Management TaskEngine\)

Within this folder, there is a configuration file, called “SAP.DM.TaskEngine.Console.exe.config”

This has a BaseAddress (URL to be used later)

2. In the Windows Services, the Task Engine is listed (and should be started)

3. The Task Engine uses the DM web-services

These web-services were installed by the DM application server installation. You can check in IIS, under the DM website there is a folder called Webservices and this contains 1 subfolder called PublicAPI.

Within this, there is one WCF service file called “DataImport.svc”

If you browse this file, you should get the following page – this indicates the web-services are running

Configuring the Task Engine

In the DM application, some settings need to be configured for the Task Engine

1. System configuration

In Administration, System configuration, open the ‘Miscellaneous’ tab

Specify the Task Engine web services URL (see step 1 of the previous section)

Note: the 2605 port is not mandatory, you can change this (both in the “SAP.DM.TaskEngine.Console.exe.config” file and in this tab)

2. Landscape

Specify the IP (server name or FQDN) and port

3. Check the logs

In the Administration, Log files, you should have access to the “Log files task engine”

Note: the log files are physically stored on the application server and you can control this by setting the path in the “Log.config” (in C:\Program Files\SAP\SAP Disclosure Management TaskEngine)

Verifying the Task Engine

To test that the Task Engine is working correctly, you must perform an operation that uses the Task Engine. One of these is the “publish period” function.

1. Setup ‘publishing

In Administration, System Config, open the “Publishing” tab

Define a folder (and option password) where the published archives will be stored

2. Publish a period

3. Result

The Task should start

Another function that uses the Task Engine, is the integration between DM and SAP Financial Consolidation.

There is an excellent video that explains this function: Integrate SAP Financial Consolidation with SAP Disclosure Management