RA2009 Bang Data Management

Data Management and Migration Best Practices for SAP BusinessObjects Strategy Management

Steve BangSAP

© SAP 2009 / 2

1. Managing Strategy Management Data and Metadata1.1. SAP BusinessObjects Strategy Management Architecture1.2 Strategy Management Data Sources1.3. Strategy Management Application Data and Metadata 1.4 Strategy Management Application Server (PAS) Data

2. Using SAP NetWeaver BW with Application Server (PAS)3. Integrating Strategy Management Data with the SAP BusinessObjects

Portfolio4. Migrating from Development to QA and Production5. Backing Up Strategy Management Files6. Optimal Data Uploading Strategies7. Wrap-up

Agenda

© SAP 2009 / 3

SAP BusinessObjects Strategy Management 7.5 Architecture

© SAP 2009 / 4

Strategy Management Data Sources

SAP BusinessObjects Strategy Management data for Strategy Management applications and Application Server (PAS) models can be sourced from the following:

Relational databases (64 bit only) on SAP NetWeaver® CEMaxDB (default): AIX, HP-UX, Linux (Red Hat and SUSE), Solaris, Windows Server 2003Oracle: AIX, HP-UX, Linux (Red Hat and SUSE), Solaris, Windows Server 2003Microsoft SQL Server: Windows Server 2003DB2: Support starting with SM 7.5 SP4 – expected Q4 2009)

Relational databases (supported for loading data into Application Server [PAS] models)Oracle, Microsoft SQL Server, DB2, etc.

SAP NetWeaver BW: InfoCubes Microsoft Excel spreadsheet files/CSV filesExternal Data LoaderSAP BusinessObjects Planning and Consolidation

KPI and initiative data (loading)Entry and Approval

© SAP 2009 / 5

Strategy Management Application Data Content

SAP BusinessObjects Strategy Management application data is stored in the CPMS_* tables of the SAP NetWeaver CE AS database for the following Strategy Management application content:

Authorization (includes users, application groups, component access, and other rights)Strings (custom strings prepended with “CC_” [Custom Code])TranslationsNamed queriesScorecards (includes contexts, scorecards, perspectives, objectives, and key performance indicators [KPIs])Initiatives Operational reviews (tied to contexts)Cause and effect (relationships between objectives)Comments (tied to contexts, objectives, KPIs, initiatives, and other comments)Entry and Approval (tied directly to a PAS model)Alerts (tied to context, users, KPIs, initiatives, and objectives)PC initiative integrationPC KPI integration

© SAP 2009 / 6

Adding Data Using Entry and Approval

The Entry and Approval functionality available in SAP BusinessObjects Strategy Management offers a secure, repeatable, workflow-based methodology for allowing business users to manually enter scorecard data

© SAP 2009 / 7

Strategy Management Application Data: Default Installation of Bootstrap Data

Before adding any custom application data to Strategy Management applications, bootstrap data is added during the SAP BusinessObjects Strategy Management installationBootstrap data includes required data for creating the Strategy Management metadata structures

Contained within the bootstrap.zip file– Added to the \SAP\SSM\InternetPub\conf directory during SCA deployments– Use the import.zip instead during installations to include sample demo data

© SAP 2009 / 8

Strategy Management Application Server (PAS) Overview

SAP BusinessObjects Strategy Management Application Server (PAS) provides a fast and powerful multidimensional OLAP database engine for use with Strategy Management applications and custom applications

Included with SAP BusinessObjects Strategy ManagementUsed primarily for providing Strategy Management application dataCan provide data to other SAP BusinessObjects Portfolio products

XcelsiusSAP BusinessObjects Web IntelligenceSAP BusinessObjects VoyagerCrystal Reports

Can provide data to most ODBO-compliant tools, like Microsoft ExcelData can be loaded from

Relational databases (for example, Oracle and Microsoft SQL Server)SAP NetWeaver BWText filesXML files

© SAP 2009 / 9

Strategy Management Application Server (PAS) Data: Creating PAS Cube Models

SAP BusinessObjects Strategy Management Application Server (PAS) cube models provide data for Strategy Management applications and custom applications

PAS models can be created usingCube Builder (Web-based)– For simple models; can be built by power users– Design based on Entry and Approval constraints– Limitations on adding and modifying modelsPAS Procedures and the PAS Administrator– Requires programming of procedures for creating dimensions, measures, etc.BW Connector Administration (a.k.a. BICA)– Used to create a PAS model by importing schemas from SAP NetWeaver BW

© SAP 2009 / 10

Creating Application Server (PAS) Models

To build complex Application Server (PAS) models, administrators perform the following steps using PAS procedures and the PAS Administrator1. Create the database (cube model)2. Set the fiscal calendar3. Create dimensions4. Create variables5. Load the data6. Consolidate the variables and, optionally, calculate variables

For simple Application Server (PAS) models, administrators and power users can use the Cube Builder (Web-based) tool1. Identify preliminary dimension information (e.g., cube name, fiscal year, default periodicity,

dimensions)2. Define and change dimension members3. Define measures4. Build PAS model

© SAP 2009 / 11

Setting the Fiscal Calendar

All time conversion calculations are based on the fiscal calendar

Application Server (PAS) “time intelligence”

Default fiscal year: Calendar yearStarts in January and ends in December

Three types of fiscal calendars

CALENDAR - Specifies a fiscal year with 12 months that coincide with calendar months

USER - Specifies a 12-month or 13-period (often called lunar) fiscal year

USER STARTING (CUSTOM) - Specifies a fiscal year of 12 periods that is completely defined by the user

© SAP 2009 / 12

Dimensions and Dimensional Structure

Stores Stores

1 2 3 4 5 876

District 1 District 2 District 3

Region 1 Region 2

Level name

Region

District

Store

Dimension Members

Consolidated levels

Detail level

© SAP 2009 / 13

Time Dimension: Periodicity

Week Number

Weekly Sales Values

Monthly Sales Value

Quarterly Sales Value

1 38,790

2 39,470

3 30,140

4 30,820 139,220

5 31,490

6 32,170

7 32,850

8 33,520 130,030

9 34,200

10 34,870

11 35,550

12 36,220

13 37,670 178,510 447,760

Periodicities convert on-the-fly

445 Fiscal Calendar

Data is presented based on the selected fiscal calendars and periodicities

© SAP 2009 / 14

Changing Dimension Structures in an Existing, Data-Populated Database

Direct impact to existing infrastructure and loaded data

Less impact:Restate historical dataRestructuring output levels of a dimension or dimensions

Consolidated data can optionally be removedDimension(s) restructured using the “Replace Calculations” keywordReconsolidate data

Most impact:Keep historical data intactRestructuring input members of a dimension or dimensions

All data must be removedDimension(s) restructured using the “Replace Calculations” keywordLoad dataConsolidate data

*Note: If data is loaded at the output level of a dimension, then this data would need to be reloaded after the dimension is restructured

© SAP 2009 / 15

Variables

Variables have zero or many dimensions associated with them “Dimensioned by” is referred to as a variable

Variables have a periodicity and beginning date for data valuesDaily, weekly, etc.

Variables contain one or more time seriesA time series contains data values for each unique combination of dimension members over time

© SAP 2009 / 16

Variable Types

Source VariablesPopulated from - external data sourcesDefault periodicity - monthly

Calculated VariablesPopulated from - sourced variablesDefault periodicity - monthly

Virtual VariablesLike calculated variables, except you define the formula instead of populating and storing the valuesInherits periodicity of the variables from which it is created

© SAP 2009 / 17

Variable Types (cont.)

Text VariablesPopulated from - external data sourcePeriodicity - constant

Temporary VariablesSame as source or calculated variables except the values are stored in the work database only

Distributed VariablesSame as source or calculated variables Values are stored in distributed model(s) which are linked to the master model

© SAP 2009 / 18

Virtual Variables

BenefitsSimilar to calculated, stored variablesData values are generated dynamically when requestedData values are not stored permanently in the databaseReduce database sizeReduce time to update database

CharacteristicsPeriodicity is undefinedThe “over time consolidation” characteristics of First, Last, Average, and Sum do not applyStorage characteristics (bytes, sparse, units) do not applyData is always calculated, including output series

© SAP 2009 / 19

Adding Virtual Variables to Databases

Zero impact on existing database structure and data

For Cube Builder databases:Modify the CUSTOM_<model_name).pro procedure – include new EXECUTE command to create new variables/KPIs

For databases built in the PAS Administrator:

USE the data databaseModify the procedure used to create variablesJOB the procedure

© SAP 2009 / 20

Distributed Variables for Performance Optimization: Model Example

Master PAS modelContains:

- Dimensions- Attributes- Virtual variables

ExpensesQuota

RevenueMargin

UnitsCosts

UnitsCosts

Monthly variables

Daily variables

Quarterly variables

Weekly variables

© SAP 2009 / 21

Attributes (Attribute Dimensions)

Characterize input members of a structural dimensionIn a 1-to-1 relationship with dimension input membersAre not uniqueCannot stand alone; always work with dimension membersFrom user’s point of view, attributes are no different than dimensionsConsolidated on-the-fly

Product dimension member: SKU1234

Color: Blue

Manufacturer: XYZ company

Style: Button-down collar

Size: Medium

Brand: ABC Company

Type: Corporate logo

© SAP 2009 / 22

Attributes: Example

By ProductResult level

Variable SizeSmallMediumLargeXLargeXXLarge

Variable ColorBlueRedGreenMulti

Variable StyleButton-down with collarButton-down no collarLong sleeveShort sleeve“3/4 sleeve”

Attribute Set

Total Color

Blue Red Green Multi

Attribute Dimension

INPUTsku1234sku2345sku5432sku6754sku9876sku0098

OUTPUTcategory1category2category3

RESULTtotal_product

Product Dimension

SizeColorsku1234 -> bluesku2345 -> bluesku5432 -> redsku6754 -> redsku9876 -> greensku0098 -> greenStyle

Attribute Variables

© SAP 2009 / 23

Adding Attribute Dimensions to a Database

Zero impact on existing database structure and data

Create an attribute setWhich in turn creates the attribute dimensions and their associate variables

Construct Attribute Dimension1. Non-Hierarchical Attribute Dimension

Build attribute set2. Hierarchical Attribute Dimension

Build attribute dimensionBuild attribute set

Load attribute variables

© SAP 2009 / 24

Loading Data into Application Server (PAS): Summary

After an Application Server (PAS) model has been created, you can load data in the cube model by following these steps:

1) Match the file layout2) Select dimension members associated with variables to be loaded3) Select measures to be loaded4) Set date range and format5) Read data from external source6) Review data (optional)

© SAP 2009 / 25

Choosing Source File Layouts: Best Practice

1 channel, 1 upccode, 83 customers18 month 83 *18 = 1,494 records

Only 83 records!

Most common: Time Down

Most efficient: Time Across

© SAP 2009 / 26

Consolidating Data

Total Product

TeaJuice

Orange Lemon Green Black

Total Region

APJEMEA

Germany UK China Japan

KPISales

Dimensioned byDimensioned by

Before Consolidation

After Consolidation

© SAP 2009 / 27

On-The-Fly Consolidation

Benefits

Increased flexibility of the model

Reduces model size

Reduces time to update models

When to use (best practices)

If you have a small dimension

Particular data combination is infrequently used

Updating or adding new data frequently

© SAP 2009 / 28

1. Managing Strategy Management Data and Metadata2. Using SAP NetWeaver BW with Application Server (PAS)

2.1. Integration Scenarios2.2. SAP NetWeaver BW and Application Server (PAS) – Differences and Terminology2.3. Integrating SAP NetWeaver BW Data with Application Server (PAS)2.4. Importing SAP NetWeaver BW Data into Application Server (PAS)2.5. Optimizing Performance Using SAP NetWeaver BW Data

3. Integrating Strategy Management Data with the SAP BusinessObjects Portfolio

4. Migrating from Development to QA and Production5. Backing Up Strategy Management-Related Files6. Optimal Data Uploading Strategies7. Wrap-up

Agenda

© SAP 2009 / 29

Comparing Application Server (PAS) and SAP NetWeaver BW Terminology

Application Server (PAS) SAP NetWeaver BW

Measure or Variable Key Figure

Dimension Characteristic (with or without hierarchy)

“Time Intelligence” <N/A>

<N/A> Time Characteristic

Model InfoProvider

Attributes Navigational Attributes

Model Security Authorizations

<N/A> Query Variables

<N/A> Currency and Unit Characteristic

Link ID Source System Connection

© SAP 2009 / 30

Key Differences Between Application Server (PAS) and SAP NetWeaver BW

Application Server (PAS) and SAP NetWeaver BW are different in two fundamental areas. It is important to understand these differences in order to better understand how to use the BW Connector Administrator.

Time IntelligenceSAP NetWeaver BW– InfoCubes contain at least one time characteristic and usually many moreApplication Server (PAS)– No specified dimension for time– Accepts a single time period for any given measure value (usually, but not necessarily,

a calendar month) and can aggregate or divide the measure value into any other time periodicity on-the-fly, using an internal PAS Calendar. [PAS “Time Intelligence”]

DimensionalitySAP NetWeaver BW– A key figure in an InfoCube is required to be dimensioned by every characteristic in the

dimension tablesApplication Server (PAS)– Every measure within a PAS model can be dimensioned differently

© SAP 2009 / 31

Application Server (PAS) Support for SAP NetWeaver BW InfoCube Data

Key considerations when loading SAP NetWeaver BW data into Application Server (PAS)

At least one standard time characteristic must be in the rows, columns, or free characteristics – 0CALMONTH is expected, but the time characteristic with highestgranularity will be usedMaximum of 12 characteristics from any given query can be brought into PASHierarchies are supportedVariables will be supported in generalOnly queries with the default single key figure structure are supportedRestricted key figures are supportedCalculated key figures might need to be redefinedBW query values should already be converted into a single currency or unit of measure

© SAP 2009 / 32

Integrating SAP NetWeaver BW Data with Application Server (PAS)

PASDatabase

Model

SM

BW ETL Layer

PIP BEx Query

Strategy Management

InfoCube

SAP NetWeaver BW

Scenario 1: Application Server (PAS) linked to SAP NetWeaver BW InfoCube, without storing data in Application Server (PAS)

Scenario 2: SAP NetWeaver BW data is loaded into Application Server (PAS)

BAPI (or ODBO)

© SAP 2009 / 33

Importing NetWeaver BW Data into Application Server (PAS)

Using the Strategy Management BW Connector Administrator, SAP NetWeaver BW data can be loaded into Application Server (PAS) and accessed directly

Summary of StepsImport BW schema into PAS modelDefine virtual variables (redefine BW calculated key figures as PAS virtual variables)Create scorecard metricsImport data– Users query data directly from PAS, but data is static as of the last import from BWSchedule model updates– Update PAS data with scheduled updates from data sourced in BW

© SAP 2009 / 34

Optimizing Performance Using SAP NetWeaver BW Data

Some tips and best practices for using SAP NetWeaver BW data with Strategy Management Application Server (PAS)

Import schema with or without importing dataUse only one query to load data into PASKey figures do not need to include any ratio calculationsLoad BW data into PAS only if poor performance

SAP NetWeaver BW Accelerator (a.k.a. BWA/BIA) will significantly boost BW performanceUsing aggregates in BW will also improve performance

Initial connections between PAS and SAP NetWeaver BW can be slow, so trigger the connection before users have access to the systemUse filters in BW queries, whenever possible, for both time and characteristicsExample

At an SAP BusinessObjects Strategy Management customer using SAP NetWeaver BW, the largest context has 14 queries loading into a single PAS model, and takes 30 to 60 seconds to load the data on the Scorecard tab– This is the initial query load only; after caching, the Scorecard loads much faster– Note that this is an exceptional case

© SAP 2009 / 35

1. Managing Strategy Management Data and Metadata2. Using SAP NetWeaver BW with Application Server (PAS)3. Integrating Strategy Management Data with the SAP

BusinessObjects Portfolio3.1. Strategy Management ODBO Data Provider3.2. Xcelsius® Integration3.3. Voyager Integration3.4. Web Intelligence Integration3.5. Using Planning and Consolidation Data for KPIs and Initiatives3.6. Risk Management Integration

4. Migrating from Development to QA and Production5. Backing Up Strategy Management Files6. Optimal Data Uploading Strategies7. Wrap-up

Agenda

© SAP 2009 / 36

Integration with the SAP BusinessObjects Portfolio

SAP BusinessObjects Strategy Management continues to be further integrated with other products within the SAP BusinessObjects portfolio, which includes solutions for enterprise performance management (EPM) and governance, risk, and compliance (GRC):

Xcelsius® softwareSAP BusinessObjects VoyagerSAP BusinessObjects Web IntelligenceSAP BusinessObjects Planning and ConsolidationSAP BusinessObjects Risk ManagementCrystal Reports

© SAP 2009 / 37

SAP BusinessObjects Strategy Management ODBO Data Provider

SAP BusinessObjects Strategy Management ODBO (OLE DB for OLAP) Data Provider is new as of SAP BusinessObjects Strategy Management 7.5 SP02

Provides access to data within SAP BusinessObjects Strategy Management applications and SAP BusinessObjects Strategy Management (PAS) cube modelsIs required for accessing SAP BusinessObjects Strategy Management data in SAP BusinessObjects Voyager, Xcelsius, SAP BusinessObjects Web Intelligence (using OLAP universes), Crystal Reports, or other ODBO clients (for example, Microsoft Excel)Consists of two DLL files, which need to be installed only onceProvides two different ODBO cube types

SSMCatalog cube– Provides an SAP BusinessObjects Strategy Management context-based cube model,

based on the contexts specified within an SAP BusinessObjects Strategy Management application– Includes the PAS cube model data for dimensions, attributes, and measures – Includes SAP BusinessObjects Strategy Management application data, including perspectives,

objectives, KPIs, and initiatives for the selected contextPASCatalog cube– Provides only the PAS cube model

– Includes only the dimensions, attributes, and measures defined in a PAS cube model

© SAP 2009 / 38

Xcelsius Integration

Xcelsius dashboard using SAP BusinessObjects Strategy Management dataTo create an Xcelsius dashboard, use the Xcelsius API to add charts, widgets, and other features[Optional] Use SAP BusinessObjects Dashboard Builder

© SAP 2009 / 39

Voyager lets analysts and power users:

Analyze scorecard data from SAP BusinessObjects Strategy Management cube models in ad hoc reportsCreate custom InfoViews for use within SAP BusinessObjects Enterprise portalsAccess data from SAP BusinessObjects Strategy Management application cube models or from custom cube modelsShare results using simple, intuitive Web interfaces

SAP BusinessObjects Voyager Integration

Use SAP BusinessObjects Voyager for ad hoc analysis of Strategy Management cubing models

© SAP 2009 / 40

SAP BusinessObjects Voyager: Integration Examples

© SAP 2009 / 41

SAP BusinessObjects Web Intelligence Integration

Providing SAP BusinessObjects Strategy Management data to SAP BusinessObjects Web Intelligence1) Add SAP BusinessObjects Web

Intelligence users and system groups in SAP BusinessObjects Central Management Console to the strategy group to identify them as SAP BusinessObjects Strategy Management users

2) Create the universe3) Assign SAP BusinessObjects Web

Intelligence users and groups to the SAP BusinessObjects Web Intelligence connection

4) Export the universe5) Create an SAP BusinessObjects Web

Intelligence document and generate a report

© SAP 2009 / 42

SAP BusinessObjects Planning and Consolidation: Providing Data for Initiatives

Providing SAP BusinessObjects Planning and Consolidation data within SAP BusinessObjects Strategy Management Initiatives

Procedure Summary1) Configure SAP NetWeaver

Composition Environment (SAP NetWeaver CE) and SAP BusinessObjects Strategy Management to accept data from the PC Web service

2) Configure application group rights to “Create Initiative Source from PC”

© SAP 2009 / 43

SAP BusinessObjects Planning and Consolidation: Providing Data for KPIs

Providing SAP BusinessObjects Planning and Consolidation data within SAP BusinessObjects Strategy Management KPIs

Procedure Summary1) Select the “PC – Scorecard

KPIs” connector in SAP BusinessObjects Strategy Management

2) Map the PC application model and SAP BusinessObjects Strategy Management scorecard data model, the associated dimensions, and time periods

3) Create the new measure in the SAP BusinessObjects Strategy Management model to store the PC KPI Actual and Target

4) Load the PC KPI data, and optionally configure PC KPI data refresh schedules

© SAP 2009 / 44

SAP BusinessObjects Risk Management: Integration Steps

Integrating SAP BusinessObjects Risk Management into SAP BusinessObjects Strategy Management – Procedure Summary

1) Edit security settings using SAP NetWeaver Web Services Administration

2) Schedule and run the SAP BusinessObjects Risk Management Batch in SSM Administration

3) Map GRC organizational units with SSM contexts using the SAP BusinessObjects Strategy Management Application –GRC Tools interface

4) Edit Java System Properties using SAP NetWeaver Administrator

© SAP 2009 / 45

SAP BusinessObjects Risk Management: Integration Examples

Display Risk Priorities from SAP BusinessObjects Risk Management in the Home PageOne-click drill into SAP BusinessObjects Risk Management from home pageScore Objectives on Key Risk Indicators and Key Performance Indicators

© SAP 2009 / 46

1. Managing Strategy Management Data and Metadata2. Using SAP NetWeaver BW with Application Server (PAS)3. Integrating Strategy Management Data with the SAP BusinessObjects

Portfolio4. Migrating from Development to QA and Production

4.1. Using the Transporter Utility4.2. Exporting Strategy Management Application Data from Source Systems4.3. Importing Strategy Management Application Data into Destination Systems4.4. Transporting Strategy Management Application Server (PAS) Data

5. Backing Up Strategy Management Files6. Optimal Data Uploading Strategies7. Wrap-up

Agenda

© SAP 2009 / 47

Using the Transporter Utility

Use the Transporter utility to move Strategy Management application data from a development server to QA and production

Can be accessed on the Strategy Tools pagehttp://<server>:<port>/strategy/tools

All of your SAP BusinessObjects Strategy Management installations should include identical versions of Strategy Management, SAP NetWeaver CE, and the SAP NetWeaver CE databaseData is stored in a relational table (not as business objects), so transporting is accomplished by individually copying the CPMS_* tablesAll of the Strategy Management schema tables contain an ID column (primary key)

ID value is globally unique– Entries are identified by this value, so data entries with the same ID value are treated as

the same record

© SAP 2009 / 48

Exporting Strategy Management Application Data from Source Systems

When exporting Strategy Management application data, remember the following:All of the Strategy Management schema tables contain an ID column (primary key)

ID value is globally unique– Entries are identified by this value, so data entries with the same ID value are treated as

the same record– During the import process, a data record in the relational database is updated with a

data record in the data file if they share the same ID valueOnly custom data is exportedWarning: The Transporter utility should not be used as a database back-up tool, since it will not backup the entire databaseData excluded from the export process

Bootstrap data which has not been modifiedAudit data (optionally included starting with SAP BusinessObjects Strategy Management 7.5 SP4)Status data for asynchronous processesModel connection data (unless you selected the option to include model connections)

© SAP 2009 / 49

Importing Strategy Management Application Data into Destination Systems

On your QA or production server, the following steps should be carefully followed:Import the bootstrap data (contained in bootstrap.zip) before importing custom application data

Should have already been done as part of the SAP BusinessObjects Strategy Management installationModifications to bootstrap data will be imported as part of the custom application data Use the import.zip file instead of bootstrap.zip to include sample data

Import custom application data after the bootstrap data importData records in the relational database are updated with a data record in the data file if they share the same ID value

Model connectionsIf model connections were not included with the exported data, then you must either manually enter the model connections or import them in a separate stepIf imported, model connections will need to be modified to reference the new server

© SAP 2009 / 50

Transporting Strategy Management Application Server (PAS) Data

To transport your Strategy Management Application Server (PAS) data from a development server to QA or production servers, perform these steps:1. From the source system, copy any customized files to the same location on the destination

system2. From the source system, copy the dimensional models to the same location on the

destination system3. On the destination system, start the Application Server (PAS) Administrator and issue a

SUPERVISOR ADD DATABASE to add the database to MASTERDBNote: If you have procedures to recreate databases, then copy the procedures to the destination system, make sure the external data sources and Link IDs are available in the new system, and recreate the databases on the destination system by running the build procedures

See the Server Upgrade guides for details on migration and upgrading Strategy Management installations

© SAP 2009 / 51



Agenda

© SAP 2009 / 52

Backing Up Strategy Management Files

Back up Strategy Management-related files to a back-up location, in case they are accidentally overwritten during upgrades or Service Pack/Hot Fix updates

Application Server (PAS) Files and Settings[Windows] Copy the lsserver.ini file (located in the Windows directory)Back up Application Server databases and procedure filesCopy the following files, located in the data directory– CGLIB, MASTERDB, SMREPORTBack up customized files (e.g., APLIB, if you created your own timesets)Back up Access LSLink subsystem-related files, if used to retrieve data from relational data sources and have an lsdal.ini file: lsdal.ini and lsdal.cnf[Linux and UNIX] Copy the following shell scripts– batchlss.csh, lsstcp.sh, runlss.csh, runlss.ksh, batchlss.ksh

© SAP 2009 / 53

Backing Up Strategy Management Files (cont.)

Interactive Publisher Files and SettingsBack up any changed (or customized) files– Use the SAP NetWeaver Directory Infrastructure (NWDI) and SAP NetWeaver

Developer Studio (NWDS), with the Strategy Management FileStore Eclipse Plug-in, for managing these files

– Code changes need to be merged into the new versions of overwritten files[Windows] Note the Registry settings related to PipAdmin Web Service, and merge these changes into a new release:– WsEndPoint, WsUserName, WsEncPwNote any other settings that you customized for your installation

Performance Management Scorecard Data and Model ConnectionsUse the Transporter utility (on the /strategy/tools page) to export the database– Select the Include Model Connections option to include all model connections (after

importing, server values might need modification)– Note: Do not apply a database filter in the export– Download the exported database, save to a ZIP file, and name it exportsm.zip (or

another name). Examine the file contents to make sure that no zero length files exist.

© SAP 2009 / 54



Agenda

© SAP 2009 / 55

Optimal Data Loading Strategies

SAP BusinessObjects Strategy Management applications should be updated with new data as required by your Strategy Management applications or custom PAS models

Typically, Strategy Management applications require only monthly and quarterly data updates, since KPIs and other data are usually tracked on a monthly or quarterly basisIf SAP NetWeaver BW is linked to a PAS model, updates will occur in real-time and require minimal attentionIf SAP NetWeaver BW queries are used to load PAS models, you will need to schedule data load updates as neededIncremental data loads and consolidations can be performed using PAS procedures, thus minimizing the impact on the Application Server (PAS) and users

© SAP 2009 / 56



Agenda

© SAP 2009 / 57

Resources: Relevant SCN Documents

The following documents are good sources of detailed information on data management issues mentioned in this presentation:

Liang, Wei, “Best Practices: The BI Connector in SSM 7.0” (PDF file), (July, 2008) www.sdn.sap.com/irj/scn/index?rid=/library/uuid/701b8da0-3135-2b10-929d-936e43164b06Look for updated version, supporting SAP BusinessObjects Strategy Management 7.5

Look for other How-To Guides and White Papers in the Strategy Management section ofSCN, located here:

www.sdn.sap.com/irj/bpx/epm?rid=/webcontent/uuid/601f130f-6808-2a10-e595-eac7e3b6772f

© SAP 2009 / 58

Resources: SAP Links

Installation guides (and sizing guide)http://service.sap.com/instguidescpm-stm * Check the Documentation Addendum for latest updates (not in other published guides)Sizing guide available for planning purposes

Knowledge Center for SAP BusinessObjects Strategy Managementhttp://help.sap.com/content/bobj/sbu/docu_sbs_stm_design.htm

Product Availability Matrix (PAM)http://service.sap.com/PAM * Includes information on supported platforms, databases, etc.

Enterprise Performance Management on SAP Community Networkwww.sdn.sap.com/irj/sdn/bpx-epm

* Requires login credentials to the SAP Service Marketplace

© SAP 2009 / 59

Resources: SAP Links (cont.)

Release Noteshttp://service.sap.com/releasenotes *To learn about new features

SAP Software Distribution Centerhttp://service.sap.com/swdc *


© SAP 2009 / 60

Resources: SAP Notes

SAP Notes Searchhttp://service.sap.com/notes *Search using “Strategy Management 7.5” as a phrase

1347610 – SAP BusinessObjects Strategy Management 7.5 SP02https://service.sap.com/sap/support/notes/1347610 *Full initial installation, or as an upgrade from SM 7.5 SP01Adds support for:– Single Sign On (SSO) with BusinessObjects Enterprise– Integration with Xcelsius dashboards– Integration with Voyager– Integration with WebIntelligence

1284823 – SAP BusinessObjects Strategy Management 7.5 Restrictionshttps://service.sap.com/sap/support/notes/1284823 *Describes known limitations and restrictions


© SAP 2009 / 61

Resources: SAP Notes (cont.)

1359550 – Using Planning and Consolidation data in Strategy Managementhttps://service.sap.com/sap/support/notes/1359550 *Contains the DLLs and documentation (how-to guide for MS version)Not supported; available only internally to SAP consultants– When SAP BusinessObjects Strategy Management 7.5 is released, the PC Web

Service will be supported and a future Strategy Management Service Pack will add support for this PC Web Service

See also Server Configuration Help documentationSee also Documentation Addendum (“Creating Initiatives and KPIs using Planning and Consolidation Data”)


© SAP 2009 / 62

Strategy Management Maximums

Selected maximums (complete list available in online help)Administrator Maximums

Contexts: 500Application groups: 100Perspectives (standard): 20Objectives: 200 (100 standard; 100 custom)Objectives/context: Users/model connection: 500KPIs: 200 (100 standard; 100 custom; unlimited index)Users: 10,000

Strategy Management application maximumsInitiatives/context: 1,000Comments/context: 10,000Milestones/initiative: 50Submilestones/milestone: 50

© SAP 2009 / 63

Strategy Management Maximums (cont.)

Selected maximums (complete list available in online help) (cont.)Dimensional Model Maximums

Dimensions that measures are dimensioned by in a view: 22Dimensions/model: 32Dimension members/dimension: 500,000Levels/dimension: 256Hierarchies/dimension: 256User-defined hierarchies/dimension: 100Dimension members in a user-defined hierarchy: 10,000Attributes/dimension in dimensional model: 50Attribute dimension members: 100,000Measures in a dimensional model: 10,000KPIs/dimensional model: 400 (total of standard and indexed)

© SAP 2009 / 64

7 Key Points to Take Home

All of the multidimensional data used within SAP BusinessObjects Strategy Management is stored in or linked to the Application Server (PAS)Unlike calculated variables, virtual variable data is generated dynamically and is not permanently stored in an Application Server (PAS) modelFor end users, attributes and attribute dimensions are displayed and manipulated just like regular dimensions and dimension membersTwo key differences between Application Server (PAS) and SAP NetWeaver BW are how time is handled (dimension vs. “time intelligence”) and dimensionalityIntegration with SAP BusinessObjects Portfolio tools allows Strategy Management data to be used with Xcelsius, Crystal Reports, SAP BusinessObjects Risk Management, SAP BusinessObjects Planning and Consolidation, SAP BusinessObjects Web Intelligence, and SAP BusinessObjects VoyagerSAP NetWeaver BW data can be used directly within Strategy Management applications using a linked connection between SAP NetWeaver BW and Application Server (PAS), without requiring data to be loaded into Application Server (PAS) modelsUse the Transporter utility to migrate Strategy Management application data from development servers to QA and production servers

© SAP 2009 / 65© SAP AG 2009. All rights reserved. / Page 65

How to contact me:Steve Bang

[email protected]

Thank you!

© SAP 2009 / 66

Copyright 2009 SAP AGAll Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver®, Duet™, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warrant.