Business objects CUBEDESIGNER 10.0 2010-12-09, FINANCIAL CONSOLIDATION 2010-12-09 User Manual

Download

Page 1

Cube Designer User Guide

■ SAP BusinessObjects Financial Consolidation, Cube Designer 10.0

2010-12-09

Page 2

© 2010 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and 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 warranty.

2010-12-09

Page 3

Getting Started........................................................................................................................7Chapter 1

1.1

1.2

1.3

1.4

2.1

2.2

2.3

2.4

2.5

2.5.1

2.6

2.7

2.7.1

2.7.2

3.1

3.2

3.2.1

3.2.2

3.3

3.3.1

3.4

3.4.1

3.4.2

3.4.3

3.5

3.5.1

3.6

General Overview of Cube Designer........................................................................................7

Connecting to Cube Designer..................................................................................................8

Main Steps..............................................................................................................................9

Cube Designer Functional Rights.............................................................................................9

Solutions...............................................................................................................................11Chapter 2

Introduction to Solutions........................................................................................................11

Creating Solutions.................................................................................................................11

Opening Solutions..................................................................................................................11

Renaming Solutions...............................................................................................................12

Delete Solutions....................................................................................................................12

Deleting Solutions..................................................................................................................12

Language Selection................................................................................................................13

Solution Export and Import.....................................................................................................13

Exporting Solutions................................................................................................................13

Importing Solutions................................................................................................................14

Views.....................................................................................................................................15Chapter 3

Introduction to views..............................................................................................................15

View Creation........................................................................................................................15

Scope Hierarchies Historization..............................................................................................16

Creating Views......................................................................................................................17

Language Selection................................................................................................................17

Choosing the languages for the cube.....................................................................................18

Measure Selection and Definition...........................................................................................18

Multi- or Single Measure Modes............................................................................................18

Multi-measures Behavior........................................................................................................19

Single Measure Behavior.......................................................................................................21

Scopes..................................................................................................................................23

Viewing a scope hierarchy......................................................................................................23

Merged Dimension Definition.................................................................................................23

2010-12-093

Page 4

Contents

3.6.1

3.6.2

3.6.3

3.7

3.7.1

3.7.2

3.7.3

3.7.4

3.7.5

3.7.6

3.7.7

3.7.8

3.7.9

3.7.10

3.7.11

3.8

3.8.1

3.9

Merged dimensions................................................................................................................24

Name Change and Translation for Merged Dimensions..........................................................26

Member Name and Selection for a Merged Dimension..........................................................26

Standard Dimensions.............................................................................................................30

Reporting Category Dimension Creation................................................................................31

Name Change and Translation for Standard Dimensions........................................................32

Member Name for Standard Dimensions...............................................................................33

Start and End Date Definition for Periods...............................................................................35

Member Name for the Period and Data Entry Period Dimensions...........................................36

Member Selection for Standard Dimensions..........................................................................37

Hierarchy Selection................................................................................................................40

Attribute Selection.................................................................................................................49

Standard Dimensions Exclusion.............................................................................................50

Hide Excluded Dimensions.....................................................................................................51

Database and Cube Structure Synchronization......................................................................51

View Copy.............................................................................................................................53

Copying and Pasting a View...................................................................................................54

Renaming a View...................................................................................................................54

Cube Deployments...............................................................................................................55Chapter 4

4.1

4.2

4.2.1

4.2.2

4.2.3

4.2.4

4.2.5

4.2.6

4.2.7

4.2.8

4.2.9

4.2.10

4.2.11

4.2.12

4.2.13

4.3

4.3.1

4.3.2

4.3.3

4.3.4

Introduction to Cube Deployments.........................................................................................55

SSAS Cube Deployments......................................................................................................55

SSAS Deployment Creation...................................................................................................56

SSAS Deployment and Cube Information...............................................................................57

Automatic Universe Creation.................................................................................................58

Database and Cube Data Synchronization ............................................................................59

Calculated Members..............................................................................................................61

Using your own MDX Scripts in a Deployment.......................................................................63

SSAS Named Set Creation based on SAP BusinessObjects Financial Consolidation

Characteristics and Filters......................................................................................................64

SSAS Deployment Issue Resolution......................................................................................65

External Data Loading into an SSAS Cube.............................................................................66

SSAS Cube Deployment and Processing...............................................................................68

SSAS Deployment Update.....................................................................................................71

Remove an SSAS Cube ........................................................................................................71

Remove an SSAS Database..................................................................................................72

SAP NetWeaver Business Warehouse Cube Deployments...................................................72

SAP NetWeaver Business Warehouse Deployment Creation................................................73

SAP NetWeaver Business Warehouse Deployment and Cube Information............................74

Cube Deployment based on an Existing Cube........................................................................74

SAP NetWeaver Business Intelligence Deployment Issue Resolution....................................75

2010-12-094

Page 5

Contents

4.3.5

4.3.6

4.3.7

4.3.8

4.3.9

4.3.10

4.3.11

4.4

4.4.1

4.5

4.6

4.6.1

5.1

5.2

5.2.1

5.2.2

5.2.3

5.2.4

5.2.5

5.2.6

5.3

5.4

5.4.1

5.4.2

5.5

5.6

5.6.1

5.7

5.8

External Data Loading into an SAP NetWeaver Business Warehouse Cube...........................75

SAP NetWeaver Business Warehouse Dimensions and Characteristics Organization............78

SAP NetWeaver Business Warehouse Cube Deployment and Processing............................80

Deploying only Most Detailed Data in an SAP NetWeaver Business Warehouse Cube ........83

Initialize a NetWeaver Business Warehouse Deployment.......................................................84

Remove an SAP NetWeaver Business Warehouse Cube......................................................85

Remove an SAP NetWeaver Business Warehouse InfoArea..................................................85

Deployment Copy..................................................................................................................86

Copying and Pasting a Deployment........................................................................................86

Renaming a Deployment........................................................................................................86

Audit and Delete Deployments...............................................................................................86

Auditing and Deleting Deployments........................................................................................87

Star Schema Deployments....................................................................................................89Chapter 5

Introduction to Star Schemas.................................................................................................89

Star Schema Deployment Creation........................................................................................89

Creating a Star Schema Deployment.....................................................................................90

Provider Tab...........................................................................................................................90

Connection Tab......................................................................................................................91

SQL.......................................................................................................................................91

Oracle....................................................................................................................................92

Advanced and All tabs............................................................................................................92

Prefix Name for Tables...........................................................................................................93

Several Fact Table Definition (Partitions)................................................................................93

Creating Partitions.................................................................................................................94

Removing partitions...............................................................................................................94

Star Schema Issue Resolution...............................................................................................94

Star Schema Deployment......................................................................................................94

Deploying a Star Schema.......................................................................................................96

Using iAnalysis Reports.........................................................................................................96

Member Aggregation when Excluding a Dimension................................................................96

6.1

6.2

6.2.1

6.2.2

6.2.3

6.3

6.3.1

Batches.................................................................................................................................99Chapter 6

Introduction to Batches..........................................................................................................99

Deploy, Process, Re-Process and Update Actions.................................................................99

AnalyticsBatch Messages....................................................................................................100

Deployer Messages.............................................................................................................104

Help.....................................................................................................................................105

Solution Export.....................................................................................................................106

Confirmation Message.........................................................................................................106

2010-12-095

Page 6

Contents

6.3.2

6.4

6.4.1

6.4.2

Index 115

Error Messages...................................................................................................................107

Solution Import.....................................................................................................................107

Confirmation Message.........................................................................................................108

Error Messages...................................................................................................................108

About the Application..........................................................................................................111Chapter 7

More Information.................................................................................................................113Appendix A

2010-12-096

Page 7

Getting Started

1.1 General Overview of Cube Designer

SAP BusinessObjects Financial Consolidation, cube designer is an application which enables authorized users to map the two following types of structured data:

• Data stored in a SAP BusinessObjects Financial Consolidation database.

• Data to be stored in OLAP cubes and/or star schemas.

In the above diagram, the steps are as follows:

Phase 1 - Creating a solution

When you create a solution, the SAP BusinessObjects Financial Consolidation database security parameters are loaded in the solution.

2010-12-097

Page 8

Getting Started

Phase 2 - Creating a view

When you create a view, the following SAP BusinessObjects Financial Consolidation database elements are loaded in the solution:

dimensions, members, characteristics and filters.

Phase 3 - Creating a cube deployment or a star schema deployment

• Creating a cube deployment. When you create a cube deployment, you specify on which server you

• Creating a star schema deployment. When you create a star schema deployment, you specify on

Phase 4 - Generating a cube or a star schema

• Deploying and processing a cube.

want to create the cube.

which database server you want to create the star schema.

• When you deploy a cube, the following SAP BusinessObjects Financial Consolidation database

elements are loaded in the cube: dimensions, characteristics and rollup hierarchies.

• When you process a cube, the SAP BusinessObjects Financial Consolidation database members

and data are loaded in the cube.

• Deploying a star schema. When you deploy a star schema, the following tables are created:

• Dimension tables

• Characteristic tables

• Fact table(s) containing data

Users will then be able to view and analyze the data contained in the cubes using retrieval tools, such as: SAP BusinessObjects Interactive Analysis and SAP BusinessObjects EPM solutions, add-in for Microsoft Office.

1.2 Connecting to Cube Designer

Select Start > Programs > SAP BusinessObjects > Financial Conlidation > Cube Designer.

The logon dialog box opens.

In the Credentials area, enter or select the information you use to connect to the Central Management Console of your SAP BusinessObjects Enterprise platform.

From the Name drop-down menu, select the connection you want to use.

Click the OK button.

Cube designer opens. The name of the connection appears below the window title bar.

2010-12-098

Page 9

Getting Started

1.3 Main Steps

When working with cube designer, you must deal with the following:

• Solutions

• Views

• SSAS cube deployment

• Star schema deployment

• SAP NetWeaver Business Warehouse (SAP NetWeaver BW) cube deployment

Related Topics

• Introduction to Solutions

• Introduction to views

• Introduction to Cube Deployments

• Introduction to Star Schemas

1.4 Cube Designer Functional Rights

To be able to use cube designer, you must have the following rights:

• Design cube right. This right is managed in the Central Management Console for the EPM connection

manager.

• Analytics administration right. This right is managed in SAP BusinessObjects Financial Consolidation.

To find out more about rights, refer to the SAP BusinessObjects Financial Consolidation Security Guide.

2010-12-099

Page 10

Getting Started

2010-12-0910

Page 11

Solutions

2.1 Introduction to Solutions

A solution contains one or more views and a view contains one or more deployments.

A solution is stored in the SAP BusinessObjects Financial Consolidation database.

A solution is connected to one SAP BusinessObjects Financial Consolidation data source only.

2.2 Creating Solutions

In cube designer main window, select File > New Solution.

The New Solution dialog box opens.

In the Name field, enter the name you want to give the solution.

In the Description field, enter a brief description explaining the solution. The description is optional.

Click the OK button. The new solution opens.

2.3 Opening Solutions

In cube designer main window, select File > Open Solution.

The Open Solutiondialog box opens.

Select the solution you want to open.

Click the Open button.

The solution opens.

2010-12-0911

Page 12

Solutions

2.4 Renaming Solutions

In the left part of the main window, right-click on the name of the solution you want to rename, then select Rename.

Enter the name you want.

2.5 Delete Solutions

You can delete one or several existing solutions.

Before they are deleted, you can save the solutions in external XML files, so that you will be able to re-import them later.

2.5.1 Deleting Solutions

Select File > Delete Solutions. The Delete Solutions dialog box appears.

Select the checkbox(es) for the solution(s) you want to delete.

Tip:

You can select all the solutions at the same time by clicking the Select all button.

You can save the solution(s) you delete in an XML file by selecting the Archive deleted solutions

to external XML option. This way, you will be able to re-import the solutions later if needed.

Click the Delete button. A confirmation message appears.

Click the OK button.

Note:

If you have selected the Archive deleted solutions to external XML option, a dialog box opens where you can choose the filename(s) and location(s) of where you want to save the deleted solution(s).

2010-12-0912

Page 13

Solutions

2.6 Language Selection

There are two types of language:

• Interface language. The interface language is the language used for menus, commands, buttons,

etc, that make up the interface.

• Data language. The data language is the language in which all of the translatable text and descriptions

appear.

You can change both languages at any time using the Data Language drop-down menu located in the upper part of the window and the Interface Language drop-down menu available by selecting Tools > Options > Display tab.

2.7 Solution Export and Import

If you want to create a solution based on an existing one, and modify some other information, you can do the following, using the solution import and export functions:

• Export the solution.

• Edit the exported solution and modify it so that you have a new solution.

• Import the new solution.

The import and export files are in .xml format.

Note:

• You can also import or export solutions without using cube designer interface.

• You can also execute the Cartesis.InformationDelivery.SolutionExporter.exe or

Cartesis.InformationDelivery.SolutionImporter.exe files that are located in the cube designer directory.

Related Topics

• Solution Export

• Solution Import

2.7.1 Exporting Solutions

Select File > Export Solution.

2010-12-0913

Page 14

Solutions

The Export Solutions dialog box opens.

In the Solutions to export groupbox, select which solutions you want to migrate.

Tip:

You can use the Select All or Select None buttons.

In the Export Location groupbox, select the target folder and enter the name for the XML file.

Click on Export.

2.7.2 Importing Solutions

Select File > Import Solution. The Import Solutions dialog box opens.

In the Import File groupbox, select the XML file containing the solutions you want to import.

If you want to overwrite solutions with the same name, check the Overwrite Existing Solutions box.

Click on Import.

2010-12-0914

Page 15

Views

3.1 Introduction to views

You will first create a view for a specific solution.

Once the view is created, you will carry out the following operations:

• Choosing the languages.

• Selecting and defining measures.

• Viewing scopes.

• Defining dimensions.

Related Topics

• View Creation

• Language Selection

• Measure Selection and Definition

• Scopes

• Merged Dimension Definition

• Standard Dimensions

3.2 View Creation

Creating a view consists of the following main steps:

• Selecting the type of data from the SAP BusinessObjects Financial Consolidation database: Package

or Consolidated.

• Retrieving the standard dimensions from the SAP BusinessObjects Financial Consolidation database.

The dimensions available depend on the data level you choose.

• For the package data level, the following dimensions are available: Account, Reporting Unit,

Original Reporting Unit, Data Entry Period, Period, Category, Flow, Audit ID, Currency, Share, Partner and custom dimensions which are indicated by a blue cube.

2010-12-0915

Page 16

Views

• For the consolidated data level, all the package dimensions plus the following dimensions are

available: Scope, Consolidation currency, Elimination and Variant.

Note:

The Elimination dimension is excluded by default. When you select an origin unit or a reporting unit rollup hierarchy, the Elimination dimension is automatically included in Financial Consolidation Cube Designer because it is required to view eliminations at Divisional Level. To view eliminations at group level only, you do not need the Elimination dimension, you can simply use the different audit IDs. The Elimination dimension has the five following members:

• Reported: Consolidated amount without any elimination.

• Eliminated at Group Level : Eliminations done at the level of the group.

• Consolidated at Group Level: Reported + Eliminated at Group Level.

• Eliminated at Divisional Level. Eliminations done according to the reporting unit rollup

hierarchies are eliminations by level. This requires an origin unit or a reporting unit rollup hierarchy in the cube in order to work. For each node, an Elimination leaf is automatically created in the rollup hierarchy to display the amounts that have been eliminated at divisional level.

• Consolidated at Divisional Level: Reported + Eliminated at Divisional Level.

3.2.1 Scope Hierarchies Historization

If you are working with consolidated data, you can historize the scope hierarchies for the Reporting Unit dimension. This way, you will:

• Keep track of changes in scopes.

• Keep consolidated data and not recalculate them in the cube over time.

Reporting unit scope hierarchies - and only these - will be merged into a single hierarchy.

If you choose to historize the scope hierarchies, once you have selected the members for the merged hierarchy, you will be able to choose the order in which the hierarchies will be taken into account.

You should note the following:

2010-12-0916

Page 17

Views

• In the General tab of the view, the Using Historized Scopes option is checked by default and

cannot be unchecked.

• The Historization tab (included in the Members tab) is available for the Consolidations merged

dimension and will enable you to choose the order in which the hierarchies will be taken into account.

• In the Reporting Unit dimension, the “Historized scope” hierarchy is selected as a “Parent child

hierarchy” and cannot be modified.

• The Live Access tab for the “Reporting Unit” dimension is disabled.

3.2.2 Creating Views

In the main window, right-click on the Solution name, then select Add View. The New View dialog box opens.

In the View groupbox, enter the following information:

• In the Name field, enter the name you want for the view.

• In the Description field, enter a brief description explaining the view. The description is optional.

In the Data Level groupbox, select one of the following options, depending on what type of data you want:

• Package.

• Consolidated. This option is selected by default.

Caution:

The choice you make here is definitive. Once you have clicked on the OK button, you will no longer be able to change the data level.

Click the OK button. The view appears below the solution with its dimensions.

3.3 Language Selection

You can choose the data languages you want to make available in the future cube, i.e. the languages in which all of the translatable text and descriptions will appear.

When defining an SSAS cube, you will have to choose the default language from all the languages which have been selected for this view.

2010-12-0917

Page 18

Views

Related Topics

• SSAS Deployment and Cube Information

3.3.1 Choosing the languages for the cube

Select the appropriate view.

In the Languages groupbox of the General tab, select the languages you require.

3.4 Measure Selection and Definition

A measure is an SSAS dimension that you can customize.

The available amounts for the measure dimension depend on the data level selected when creating the view.

• If the Package data level has been selected, the Local amount will be available.

• If the Consolidation data level has been selected, the Local, Converted and Consolidated amounts

will be available.

3.4.1 Multi- or Single Measure Modes

Depending on how you want the data to be retrieved in the data retrieval tools, you can choose one of the following measure modes:

• multi-measures.

Restriction:

This mode is not supported for SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployments. If you choose this mode, in the SAP NetWeaver BW deployment part, an issue to resolve will be indicated and you will have to choose the single measure mode in order to deploy the cube.

• single measure. This is the default mode.

As opposed to the multi-measure mode, the single measure mode enables you to view all detailed and non detailed data on the same measure.

2010-12-0918

Page 19

Views

Related Topics

• Multi-measures Behavior

• Single Measure Behavior

3.4.2 Multi-measures Behavior

Once you have chosen the data amount(s) you want, you can further detail the measures by including dimensional analyses. The dimensional analyses proposed contain the detailed dimensions used in the SAP BusinessObjects Financial Consolidation analysis hierarchies for the category selected.

You can select the dimensional analyses you want and you can also create new ones.

Note:

If no dimensional analysis appears, this means that no member of the Category dimension has been selected.

Each dimensional analysis you select will be available for selection in the General tab of the view.

Each dimensional analysis selected will become a measure in the future cube.

The name of a measure will appear as follows in the cube : [type of amount] - [dimensional analysis].

Example:

In the Dimensional Analysis tab, the "Partner" dimensional analysis is selected.

In the General tab of the view, the available measures are as follows:

Example:

The following example will show you how the detailed measures will appear in a cube.

In cube designer, the following elements are selected:

• Data level selected: Consolidation

• Amounts selected for the Measure dimension: Local and Consolidated

• Dimensional analysis selected: Partner/Product and Activity

2010-12-0919

Page 20

Views

In the future cube, the Measure dimension will be detailed as follows:

The Consolidation and the Local members are non-detailed amounts.

3.4.2.1 Activating the Multi-measures Mode

Select Tools > Options. The Options dialog box opens.

In the General, tab select the Multi Measure Group Analysis.

Click OK.

3.4.2.2 Selecting a Dimensional Analysis

Select the view.

Select the Dimensional Analysis tab.

Select the dimensional analysis you want.

3.4.2.3 Creating a Dimensional Analysis

Select the view.

Select the Dimensional Analysis tab.

Under Custom Measure Groups, double-click on <Double-Click here to add a new Custom Measure Group>.

The Custom Dimensional Analyses dialog box appears.

2010-12-0920

Page 21

Views

Enter a name for the analysis.

Select all the dimensions you want.

Tip:

Use the Ctrl keyboard button to select more than one dimension.

Click the OK button. The new analysis appears in the list under Custom Measure Groups and is selected by default.

3.4.2.4 Selecting Data Amounts for the Measure Dimension

Select the view.

In the Measures groupbox of the General tab, select the data amounts you want.

3.4.3 Single Measure Behavior

The dimensional analyses are automatically selected if the analysis dimensions are included in the cube.

Note:

To include a dimension in the cube, right-click on the dimension in the tree structure part of the window and select Include.

As a general rule, the data for a single measure will appear on the detailed hierarchies as follows:

The amount on the node is the result of the sum of the detail: that is, members 1, 2 and 3. The "No detail" amount is not part of the sum.

The default name for the node is: All detailed <name of the analysis dimension>. You can rename the node.

Note:

To rename this node, click the Translation tab and enter the text you want in each language available.

Caution:

It is highly recommended that you set the default member to "No detail". Otherwise, you will always see the analyzed data in the reports.

2010-12-0921

Page 22

Views

Restriction:

In SAP NetWeaver Business Warehouse deployments, the "All detailed" member includes not only all detailed child members but also the "No detail" member (that is the "NA" member).

Example:

In the Dimensional Analysis tab, the "Partner" dimensional analysis is selected.

In the General tab of the view, the available measures are as follows:

Each dimensional analysis will be aggregated in the Local, Converted and Consolidated amounts.

Example:

The following example will show you how the detailed measures will appear in a cube.

In cube designer, the following elements are selected:

• Data level selected: Consolidation

• Amounts selected for the Measure dimension: Local and Consolidated

• Dimensional analysis selected: Partner/Product and Activity

In the future cube, the Measure dimension will be detailed as follows:

Related Topics

• Selecting a Default Member for a Hierarchy

3.4.3.1 Selecting the Data Amounts (for the Measure dimension) and a Dimensional Analysis

Select the view.

In the Measures groupbox of the General tab, select the data amounts you want.

2010-12-0922

Page 23

Views

3.5 Scopes

If you have chosen to work with consolidated data, the Scopes tab appears.

The scopes displayed in the tab are related to the members selected in the Scope dimension.

The tab enables you to view the scope hierarchies.

Related Topics

• Hierarchy Selection

3.5.1 Viewing a scope hierarchy

In the tree structure part of the window, select the appropriate view.

Select the Scopes tab.

In the Scopes section, select the scope you want to view.

In the Scope Hierarchy section, the hierarchy appears.

Tip:

You can use the Show All button to display all the levels of the hierarchy.

3.6 Merged Dimension Definition

Defining merged dimensions consists of the following steps:

• Merging dimensions

• Changing and translating the name of a merged dimension

• Naming and selecting the members of a merged dimension

• Ordering scope hierarchies

Related Topics

• Merged dimensions

• Name Change and Translation for Merged Dimensions

• Member Name and Selection for a Merged Dimension

2010-12-0923

Page 24

Views

• Scope Hierarchies Order

3.6.1 Merged dimensions

3.6.1.1 Pre-defined Merges

Depending on the data level you have chosen when creating the view, you can merge the following dimension combination: Conso Definitions, Reporting ID or Consolidations.

• For the package data level, the following dimensions are available: the Category and Data Entry

Period contained in the Reporting ID.

• For the consolidated data level, all the package dimensions plus the following dimensions are

available: Scope, Consolidation currency and Variant contained in Conso Definition; Category, Data Entry Period, Scope, Consolidation currency and Variant contained in Consolidations.

3.6.1.1.1 Merging a Pre-defined Combination of Dimensions

In the tree structure part of the window, right-click the Merged Dimensions node and select one of the following: Merge 'Conso Definitions', Merge 'Reporting ID' or Merge 'Consolidations'.

Some of them may not be available. Two reasons are possible:

• The merge has already been defined and appears in the Merged Dimensions node.

• The merge cannot be performed because of the data level you have already chosen when creating

the view.

Note:

By default, none of the members are selected.

You will then select the members that will appear in the cube.

Tip:

To rename the newly merged dimension, right-click on it and select Rename.

Related Topics

• Selecting the Members of a Merged Dimension

2010-12-0924

Page 25

Views

3.6.1.2 Customized Merges

You can merge other dimensions of your choice. You can then rename the resulting merged dimension members.

Merging dimensions can result in a high volume of metadata.

On a large set of members, this behavior can lead to a cumbersome selection process. This is why you can select the members to be merged, therefore producing a smaller set of combinations.

Example: For instance, merging the following dimensions:

• Products : P1, P2

• Geography: France, UK

• Activity: A5, A6

would generate the following combinations: P1 France A5, P1 France A6, P1 UK A5, P1 UK A6, P2 France A5, P2 France A6, P2 UK A5, P2 UK A6.

3.6.1.2.1 Merging the Dimensions of your Choice

In the tree structure part of the window, right-click the Merged Dimensions node and select Add Custom merge.

The Create New Merge Definition dialog box appears.

In the Available Dimensions area, select one of the dimensions you want to merge and click the

button.

The dimension you have selected appears in the Included Dimensions area.

Repeat actions 2 and 3 for each dimension.

Note:

Each time you insert a dimension in the Included Dimensions area, the Estimated Member Count is updated. It indicates the estimated number of members that will be retrieved in the future cube if you select all members of each dimension.

Click the OK button.

The merged dimension appears under the Merged Dimensions node. By default, the dimension name is the concatenated names of the dimensions you have merged.

For example, if you have merged the “Account” and the “Flow” dimensions, the merge will be named “AccountFlow”.

Note:

By default, none of the members are selected.

2010-12-0925

Page 26

Views

To select the members that will appear in the cube.

Tip:

To rename the newly merged dimension, right-click on it and select Rename.

Related Topics

• Selecting the Members of a Merged Dimension

3.6.2 Name Change and Translation for Merged Dimensions

You can change the name of the dimension as it will appear in the future deployment.

You can also translate the name of the dimension.

3.6.2.1 Changing and Translating the Name of a Merged Dimension

The name of the merged dimension appears - in the data language displayed - in the Dimension Identity groupbox of the General tab. You can change it.

Click the Translation & Member Names tab.

Enter the text for each language.

Tip:

You can also rename a merged dimension in the current language by right-clicking on it in the left part of the window and selecting Rename in the context menu.

3.6.3 Member Name and Selection for a Merged Dimension

While creating the view, you may have chosen merged dimensions. For each merged dimension, you will now:

• Choose how the name of the members should appear in the future deployment (in the Translation

and Member Names tab).

• Choose the dimension members you want to take into account for each dimension composing the

merged dimension (this is a pre-selection), then for the merged dimension itself (in the Members tab).

2010-12-0926

Page 27

Views

Note:

By default, none of the members are selected.

A member name can appear in four ways:

• Code naming. This is the default naming type of a member. A concatenated name is created by

grouping together the codes of the members (from the SAP BusinessObjects Financial Consolidation database) contained in the merged dimension.

• Financial Consolidation naming. This is available for selection for the 'Reporting ID' and

'Consolidations' merged dimensions. In this case, the members will appear with the same description as in the SAP BusinessObjects Financial Consolidation database (in SAP BusinessObjects Financial Consolidation: Category + Data entry period = Category scenario).

• Deployment Names. A concatenated name is created by grouping together the deployment names

of the dimensions composing the merged dimension.

Restriction:

For SAP NetWeaver BW deployments, depending on the deployment names that have been selected for each dimension, merged dimension member names cannot exceed 60 characters for SAP NetWeaver BW. In this case, an issue to resolve will occur and you will have to modify the selection of the deployment name for the dimensions composing the merged dimension.

• Manual Naming. In this case, you will enter the name you want for the member in each language

available.

Tip:

You can also copy and paste the cells from cube designer to Microsoft Office Excel or from Microsoft Office Excel to cube designer, using the copy and paste buttons in the Translation and Member Names tab.

You can define the default member that will be displayed in the retrieval tool connected to the future cube. This can be done in the Default Member field of the General tab.

Restriction:

The default member will not be taken into account for an SAP NetWeaver BW deployment.

You can also specify that you do not want the name of the dimension to appear in the retrieval tool by selecting the Hide dimension name option. In this case, only the selected hierarchy name will appear.

Restriction:

The Hide dimension name function will not be taken into account for an SAP NetWeaver BW deployment.

Note:

By default, 5 000 members can be displayed for a merged dimension. You can change this number in the Merge Member Max Display field by selecting Tools > Options > Display tab.

You can select the members in the Selection tab. You can access this tab by selecting [View] > Merged dimensions > [merged dimension] > Members > Selection.

The Selection tab includes:

• The Member Display Filter groupbox.

2010-12-0927

Page 28

Views

The following elements can be used to limit which members are displayed:

• To display members containing the same text, enter the text in the Search for members

containing field. Next, open the Match against column drop-down menu and select the column in which the entered text should appear. Finally, click the Apply button.

Tip:

If you want the search to be case sensitive, select the Filtering is case sensitive option.

• To display only the members you have selected in the Elements groupbox, select the Display

selected members only option.

• You can sort a column in ascending or descending order. This can be done by selecting the

column name from the Sort column drop-down menu.

• The Members groupbox. This part displays the members, depending on the filtering applied. This

is where you select the members you want to take into account.

• The Select all members box. This option enables you to select all the members belonging to the

dimension, and not just the members that are displayed in the Members groupbox. By default, any member added to the SAP BusinessObjects Financial Consolidation structure is retrieved in cube designer. However, these new members are not automatically selected in cube designer, which means that they do not factor into the existing cube definition. To avoid having to manually select these new members, click the Select all members option. This way, the members will be added to the cube in the next deployment.

Related Topics

• Custom Filtering

3.6.3.1 Naming the Members of a Merged Dimension

Select the appropriate merged dimension.

Select the Translation and Member Names tab.

Using one of the following buttons, select the naming type you want:

• Code naming.

• Financial Consolidation naming.

Note:

This is available for selection for the 'Reporting ID' and 'Consolidations' merged dimensions.

• Deployment Names.

• Manual naming.

If you choose this option, enter the names you want for the members in each available language.

2010-12-0928

Page 29

Views

Tip:

You can also copy and paste the cells from cube designer to Microsoft Office Excel or from Microsoft Office Excel to cube designer, using the copy and paste buttons.

The member names appear in the Members groupbox of the Members tab.

3.6.3.2 Selecting the Members of a Merged Dimension

Open the node for the appropriate merged dimension.

Select one of the dimensions belonging to the merge.

Select the Members tab.

Select the Selection tab.

Note:

By default, none of the members are selected.

In the Members groupbox, check the boxes corresponding to the members you want to take into account.

Tip:

Following are some tips for selecting members:

• To select all the members displayed, click the Select Visible button.

• To deselect all the members displayed, click the Deselect Visible button.

• To select the deselected members and deselect the selected ones, click the Invert Selection

button.

• To reset the selection to its default setting, click the Reset button.

• To select all the members (not just the ones that are displayed but all the members belonging to

the dimension, in particular the newly added members in SAP BusinessObjects Financial Consolidation), check the Select all members box.

Tip:

You can use filtering criteria to limit which members are displayed. To find out more about filtering, see above.

Repeat action 2 to 5 for each dimension belonging to the merge.

In the tree structure part of the window, select the merged dimension.

Select the Members tab.

Note:

If the Members area is empty, it means that no member has been selected in any dimension.

All the members that appear are a result of the members you have selected for each dimension.

Select the members you want to be taken into account in the cube.

2010-12-0929

Page 30

Views

3.6.3.3 Scope Hierarchies Order

If you chose to historize the scope hierarchies when creating the view, the Historization tab is also available next to the Selection tab.

The Historization tab includes:

• The Scope Hierarchy Deployment Order groupbox. This groupbox displays the members selected

in the Members groupbox of the current tab or of the Selection tab. The buttons available will enable you to choose the order in which the hierarchies will be taken into account.

• The Members groupbox. This groupbox displays the members of the merged dimension. You can

select the members you want to take into account using this groupbox or in the Selection tab.

Note:

The consolidations without scope hierarchies are not displayed.

3.6.3.3.1 Ordering Scope Hierarchies for the Consolidations Merged Dimension

Select the Consolidations merged dimension.

Select the Members tab.

Select the Historization tab.

If you have not already chosen the members in the Selection tab, you can do so in the current tab by checking the ones you want to take into account.

Use the different buttons on the right side to order the members as you like.

3.7 Standard Dimensions

Defining standard dimensions consists of the following steps:

• Changing and translating the names of standard dimensions

• Naming the members of standard dimensions

• Defining the start and end date for periods

• Naming the members of the Period and Data Entry Period dimensions

• Selecting the members of standard dimensions

• Selecting hierarchies

• Selecting attributes

• Excluding standard dimensions

2010-12-0930

Page 31

Views

• Hiding excluded dimensions

• Synchronizing the database and cube structure

Related Topics

• Name Change and Translation for Standard Dimensions

• Member Name for Standard Dimensions

• Start and End Date Definition for Periods

• Member Name for the Period and Data Entry Period Dimensions

• Member Selection for Standard Dimensions

• Hierarchy Selection

• Attribute Selection

• Standard Dimensions Exclusion

• Hide Excluded Dimensions

• Database and Cube Structure Synchronization

3.7.1 Reporting Category Dimension Creation

The Reporting Category dimension (merges the Data Entry Period dimension and the Category dimension) is not available by default. You can create it.

You will then be able to create its members, choosing one category and one or several data entry periods.

3.7.1.1 Creating the Reporting Category Dimension and its Members

In the General tab of the view, select the Using Reporting Categories check box. The Reporting Category dimension is added to the dimensions' list in the tree structure part of the

window.

Select the Reporting Category dimension.

Select the Members tab.

To create a member for the dimension, click the Create button. The Reporting Category dialog box appears.

In the Code field, enter a code for the member you are creating.

In the Long Description field, enter a name for the dimension.

Select a category from the Category drop-down menu.

Select the checkboxes of the data entry periods you want to include.

2010-12-0931

Page 32

Views

Tip:

You can also use the Filter field and click on Update list to select the data entry periods you want. For example, if you want to select all occurrences of the month of June , you can enter: *.06. If you want to select all the data entry periods, you can enter *.*. The characters you can use to facilitate your selection are the same as for the Custom filtering section.

Click on OK.

Related Topics

• Custom Filtering

3.7.2 Name Change and Translation for Standard Dimensions

You choose a type of name for all the standard dimensions as they will appear in the future deployment: [code], [short description], [long description], [extra-long description], [code] - [short description], [code]

- [long description], [code] - [extra-long description], [short description] - [code], [long description] -

[code], [extra-long description] [code], or a custom name.

The name chosen will be applied by default to each dimension.

You can then change the name of each dimension as it will appear in the future deployment.

3.7.2.1 Choosing a Name for all the Standard Dimensions

In the tree structure part of the window, select Dimensions.

Select the General tab.

Select the naming type you want from the Dimension default format drop-down menu.

3.7.2.2 Changing the Name of one Standard Dimension

In the tree structure part of the window, select the appropriate dimension.

Select the General tab.

The Naming Format drop-down menu displays Use default format, which represents the default name chosen for all the standard dimensions.

If you want to change it, select the naming type you want from the Naming Format drop-down menu.

2010-12-0932

Page 33

Views

If you have selected Custom Name, the Display Name field is activated and you can enter text of your choosing for the current dimension.

Note:

You can also enter text of your choosing in each available language in the Translation tab.

3.7.3 Member Name for Standard Dimensions

While creating the view, you may have chosen standard dimensions. For each dimension, you will now choose how the name of the members should appear in the future deployment.

You choose a type of name for all the members of all the dimensions as they will appear in the future deployment: [code], [short description], [long description], [extra-long description], [code] - [short description], [code] - [long description], [code] - [extra-long description], [short description] - [code], [long description] - [code], [extra-long description] [code].

The name chosen will be applied by default to each dimension.

You can then add a prefix and/or a suffix to the default name of the members for each dimension and for each language as they will appear in the future cube.

Restriction:

Prefixes and suffixes will not be taken into account for a NetWeaver BW deployment.

If there are duplicate members, a pop-up message will appear when you deploy the cube, indicating the remaining duplicate members and asking you whether you want to continue or to stop deployment.

You can also define other naming types for all the members of all dimensions. Each standard dimension will inherit the chosen naming type. In addition to that, you can define other naming types for all members of each dimension.

In your data retrieval tool, the user will be able to choose the naming type to be displayed.

Note:

The retrieval tool must be able to read several descriptions to make this functionality effective.

Restriction:

Member name formats deployed in SAP NetWeaver BW cubes.

For a specific standard dimension, if you do not select any custom member name formats (that is if you do not click the Use custom format link in the General tab), the following formats are deployed by default in SAP NetWeaver BW cubes:

• code is deployed as an SAP NetWeaver BW short description

• short description is deployed as an SAP NetWeaver BW medium description

• long description is deployed as an SAP NetWeaver BW long description

If you select three member name formats, the following formats are deployed in SAP NetWeaver BW cubes:

2010-12-0933

Page 34

Views

• the first selected in the checkbox list is deployed as an SAP NetWeaver BW short description

• the second selected in the checkbox list is deployed as an SAP NetWeaver BW medium description

• the third selected in the checkbox list is deployed as an SAP NetWeaver BW long description

If you select a fourth format, a message appears in the Issue To Resolve tab and you cannot deploy the cube.

In concatenated formats, there are no spaces on either side of the hyphen (for example: "code-short description").

If the member names exceed a certain number of characters, they are truncated when deployed:

• short descriptions are limited to 20 characters

• medium descriptions are limited to 40 characters

• long descriptions are limited to 60 characters

3.7.3.1 Choosing a Name for all the Members of Standard Dimensions

In the tree structure part of the window, select Dimensions.

Select the Member Properties tab.

Select the naming type you want from the Formats column.

Select the naming type you want to apply by default to all the members, selecting the appropriate option in the Default format.

3.7.3.2 Changing the Name and Add a Prefix and/or a Suffix to the Name of all the Members for a Standard Dimension

In the tree structure part of the window, select the appropriate dimension.

Select the General tab.

In the Member properties area, the default format name chosen for all the members of standard dimensions is displayed.

If you want to change this name, click the Use custom format link. The Member properties area is enabled.

Select the naming type you want.

If you want to add a prefix to the member, enter the prefix you want in the Member Prefix field.

Note:

To enter the prefix you want for each language, click the Translation tab.

If you want to add a suffix to the member, enter the suffix you want in the Member Suffix field.

2010-12-0934

Page 35

Views

Note:

To enter the suffix you want for each language, click the Translation tab.

Restriction:

Prefixes and suffixes will not be taken into account for an SAP NetWeaver Business Warehouse deployment.

3.7.3.3 Adding Member Names for all the Members of all Standard Dimensions

In the tree structure part of the window, select the Dimensions node.

Select the Member Properties tab.

Select the naming type you want from the Formats column.

Enter a name of your choosing in the languages available.

Note:

To enter the name you want for each language, click the Translation tab.

3.7.3.4 Add Member Names for all the Members of a Standard Dimension

In the tree structure part of the window, select the appropriate dimension.

Select the General tab.

Note:

If you have already added member names for all the members of all standard dimensions, one or several naming types are already checked in the Formats column of the Member properties area.

If you want to change the member names, click the Use custom format link. The Member properties area is enabled.

Select the naming types you want.

Note:

To enter the name you want for each language, click the Translation tab.

3.7.4 Start and End Date Definition for Periods

2010-12-0935

Page 36

Views

You can define all the periods to make available for selection in the Period and Data Entry Period dimensions by choosing the start and the end year.

As far as the fiscal year is concerned, you can also choose the start month. To be consistent, you must choose the same start month that is defined in Financial Consolidation.

Note:

Once you have defined the dates, all the periods between the start and the end dates are available for selection in the Members area for the Period and Data Entry Period dimensions.

3.7.4.1 Defining the Dates for Periods

Select Tools > Options.

Select the Periods tab.

Define the start and end year.

Click the Apply button.

In the General tab of the appropriate solution, select the start month (for the fiscal year) from the Start Month drop-down menu.

Note:

To be consistent, you must choose the same start month that is defined in Financial Consolidation.

3.7.5 Member Name for the Period and Data Entry Period Dimensions

Note:

The Period dimension is considered as 'Time' type dimension in a cube.

In the General tab of the Period and Data Entry Period dimensions, you can choose a format defining how the name of the members should appear in the future deployment. The names can appear differently for each dimension, depending on which dimension you have selected.

You choose a type of name for all the members of the dimension as they will appear in the future deployment, using templates and adding the text you want.

The available templates are the following: [Month], [Mon], [MM], [YYYY] and [YY].

You can combine several templates and add any text, characters or punctuation you want.

Note:

If you have chosen a member prefix or suffix or both, they will be added before and after the text entered in the Period Format field.

2010-12-0936

Page 37

Views

Example:

In the Period Format field :

• 'FY' and ' - ' have been entered.

• [YY] and [Month] templates have been dragged and dropped from the Templates section.

The defined period format 'FY[YY] - [Month]' will appear as for example: FY06 - January

Example:

With the Period 2006.03 in the SAP BusinessObjects Financial Consolidation database, the results using all the different formats will be as follows:

• [Month]: March

• [Mon]: Mar

• [MM]: 03

• [YYYY]: 2006

• [YY]: 06

3.7.6 Member Selection for Standard Dimensions

For each dimension, you will now choose the dimension members you want to include in the future deployment.

To make the selection of the members easier:

• Open the Selection tab to use filtering criteria to limit which members are displayed.

• Open the Filters & Characteristics tab to use the filters or characteristics defined in the SAP

BusinessObjects Financial Consolidation database.

3.7.6.1 Custom Filtering

To make the selection of the members easier, you can open the Selection tab to use filtering criteria to limit which members are displayed.

You can access this tab by selecting View > Dimensions > [dimension] > Members > Selection.

The Selection tab includes:

2010-12-0937

Page 38

Views

• The Member Display Filter groupbox.

The following elements can be used to limit which members are displayed:

• To display members containing the same text, enter the text in the Search for members

containing field. Next, open the Match against column drop-down menu and select the column in which the entered text should appear. Finally, click the Apply button.

Tip:

If you want the search to be case sensitive, select the Filtering is case sensitive option.

• To display only the members you have selected in the Elements groupbox, select the Display

selected members only option.

• You can sort a column in ascending or descending order. This can be done by selecting the

column name from the Sort column drop-down menu.

• The Members groupbox. This groupbox displays the members, depending on the filtering applied.

This is where you select the members you want to take into account.

• The Select all members box. This option enables you to select all the members belonging to the

dimension, and not just the ones that are displayed in the Members groupbox. By default, any member added to the SAP BusinessObjects Financial Consolidation structure is retrieved in cube designer. However, these new members are not automatically selected in cube designer, which means that they do not factor into the existing cube definition. To avoid having to manually select these new members, click the Select all members option. This way, the members will be added to the cube in the next deployment.

• For a detailed dimension, the Include NA Member option is available. This option is available in

order to include the NA member in a dynamic selection, which is a selection using SAP BusinessObjects Financial Consolidation filters or characteristics.

Characters you can use in the Search for members containing field

• Literals like abc will match any element name containing at least one occurrence of 'abc'. This is

case sensistive.

• * means zero or more, + means one or more. So a+bc will match any string containing a followed

by one or more b followed by a c.

• You can group literals using [] so [ae]will match any string containing a single a or e. Hence gr[ae]y

will match 'gray' or 'grey' (but not 'graey')

• You can use a hyphen to indicate ranges. E.g. [0-9]will match any number. [0-9]* will match a

sequence of zero or more numbers. [A-Za-z] will match any single upper or lower case letter.

• You can connect multiples of these together to form more complex filters. E.g [A-Za-z]+[0-9]+ will

match any element name that starts with 1 or more letters and is followed by 1 or more numbers.

• A carat will negate a matched set, so a[^b]matches an a followed by a character other than b. [^0-9]

therefore matches any non-numeric character.

• You can do case insensitive matches using /i -- so /iABC will match 'AccountABC', 'AccountAbC' ,

'Accountabc', "CompanyABC", "abcDEF", etc.

2010-12-0938

Page 39

Views

• ^ means the start of the element name and $ the end of the name. E.g. ^A matches names starting

with A, [0-9]$ matches names ending in a number.

• Besides using * and + for repetition you can specify how many occurenes between n and m times

using {n,m}. E.g. A[0-9]{1,3} will match elements containing an A followed by between 1 and 3 numbers.

• The vertical bar | means or. So to match any element containing ABC, XYZ or 123 use ABC|XYZ|123.

• A (?) matches any single character. For example, to search for the period 2000.12, you type: 2000?12

in the "search" function.

Example:

Following are some examples:

• ABC simply matches elements which contain ABC

• ^ABC matches elements starting with ABC

• ^ABC[0-9]* - Matches element names of the form ABCxxx where xxx is a sequence of numbers

• [A-Za-z_][A-Za-z0-9_]* - Matches element names that start with a letter or underscore followed by

zero or more letters, numbers or underscores.

Related Topics

• SAP BusinessObjects Financial Consolidation Filtering

3.7.6.2 SAP BusinessObjects Financial Consolidation Filtering

To make the selection of the members easier, you can open the Filters & Characteristics tab to use the filters or characteristics defined in the SAP BusinessObjects Financial Consolidation database.

You can access this tab by selecting View > Dimensions > [dimension] > Members > Filters & Characteristics.

The Filters & Characteristics tab includes:

• The Financial Consolidation Filters & Characteristics groupbox.

You can use the following elements to help you select the members:

• Filter selection. To select filters, click the By Filter button. In the Select Filter dialog box that

appears, select one or more filters and click the OK button.

• Characteristics selection. To select characteristics, click the By Characteristic button. In the

Select Characteristic dialog box that appears, select one characteristic and the elements you want, then click the OK button.

2010-12-0939

Page 40

Views

• Once you have selected a filter or a characteristic, the members that are included in the filter or

characteristic appear in black in the Members groupbox and the Lock Selection to Filter/Characteristic option is automatically selected. If you want to select additional members, deselect the option. You will be able to select other members (which are otherwise grayed out).

• The Members groupbox. This groupbox displays the members contained in the filter(s) or

characteristic(s) selected. This is where you select the members you want to take into account.

3.7.6.3 Selecting Members for a Standard Dimension

Select the appropriate standard dimension.

Select the Members tab.

Select the Selection or the Filters & Characteristics tab.

In the Members groupbox, check the boxes corresponding to the members you want to take into account.

Tip:

Following are some tips for selecting the members:

• To select all the members displayed, click the Select Visible button.

• To deselect all the members displayed, click the Deselect Visible button.

• To select the deselected members and deselect the selected ones, click the Invert Selection

button.

• To reset the selection to its default setting, click the Reset button.

Tip:

You can use filtering criteria to limit which members are displayed. To find out more about filtering, see above.

3.7.7 Hierarchy Selection

Three types of hierarchy are available:

• Default hierarchy. A default hierarchy consists of one node grouping together a simple list of elements.

However, OLAP cubes consider this to be a hierarchy.

• Parent Child hierarchy. The SAP BusinessObjects Financial Consolidation characteristics that belong

to the same reference table as the dimension to which they are assigned are changed into "Parent Child hierarchies".

2010-12-0940

Page 41

Views

Note:

• The rollup unit and account hierarchies in SAP BusinessObjects Financial Consolidation are

treated like Parent Child hierarchies.

• When you select a rollup unit hierarchy, the Elimination dimension is automatically included in

the cube.

• For SAP NetWeaver Business Warehouse (SAP NetWeaver BW) cube deployments only, you

can select several Parent Child hierarchies per dimension and per cube with only one Scope Entity hierarchy or Category Scenario Account hierarchy.

Caution:

Some SAP BusinessObjects Financial Consolidation characteristics linked to a dimension contain circular references. Therefore, they will not be changed into a Parent Child hierarchy. The deployment will then fail.

• Named level hierarchies. The SAP BusinessObjects Financial Consolidation characteristics that do

not belong to the same reference table as the dimension to which they are assigned are changed into "Named level hierarchies".

Caution:

Financial Consolidation characteristics based on the same reference table part of a named-level hierarchy.

SAP BusinessObjects Financial Consolidation characteristics based on the same reference table (meaning characteristics that belong to the same reference table as the dimension to which they are assigned) can be part of a named-level hierarchy in cube designer. However, if you select a characteristic based on the same reference table in the Characteristics area of the Hierarchies tab, note that SAP does not guarantee that it will be supported and therefore, intermediate totals in the hierarchy may be incorrect - in both SSAS cubes and SAP NetWeaver BW cubes.

If you are using an SAP BusinessObjects Financial Consolidation database, other hierarchies are available for the Account, Reporting Unit and Origin Unit dimensions.

• For the Reporting Unit or the Origin Unit dimensions, you can select Scope Entity Hierarchy. The

hierarchies available in the drop-down menu depend on the scopes previously selected. When you select a scope hierarchy, the members of the scope linked to this scope hierarchy will automatically be selected in the Members tab.

Restriction:

If you select a scope entity hierarchy in either one of the two dimensions, the selection will not be available for the other dimension.

• For the Account dimension, you can select a Category Scenario Account Hierarchy. The hierarchies

available in the drop-down menu depend on the members selected in the Category dimension.

Note:

If you chose to historize the scope hierarchies, the Parent child hierarchy cannot be changed for the Reporting Unit dimension.

If you do not select a hierarchy or you select the Include default hierarchy option, the default hierarchy will be applied in the future cube.

2010-12-0941

Page 42

Views

Note:

• In order to obtain a simple cube, you should select only one hierarchy per dimension and per cube.

• If you have already selected a hierarchy, you are advised not to select the Include default hierarchy

option.

Restriction:

The Hide dimension name function will not be taken into account for a SAP NetWeaver BW deployment.

3.7.7.1 Parent Child hierarchies and Data Members

Data members can be created automatically on the Parent Child hierarchies of the following dimensions:

• Detailed dimensions.

• Reporting Unit dimension.

• Original Reporting Unit dimension.

By default, data members are created automatically by default; however, you can choose not to create them.

Restriction:

Even if the appropriate option is selected, data members are not included in SAP NetWeaver BW cubes.

Example:

In the example below, the total is the same in both cases. Only the display is different.

The data member for U1 has been automatically created.

The data member for U1 has not been created.

2010-12-0942

Page 43

Views

3.7.7.1.1 Choosing Data Members not to be Created

The data members are created automatically by default on the Parent Child hierarchies of some dimensions. You can choose not to create them.

Select Tools > Options. The Options dialog box appears.

In the General tab, deselect the Include Data Member option.

Click on OK.

Restriction:

Even if the option is selected, data members will not be included in SAP NetWeaver BW cubes.

3.7.7.2 Aggregation Definition

For all dimensions except for Category, Scope, Variant and Consolidation Currency, two options are available. If you select these options, the parent node will contain the aggregated total of its children amounts.

• The Enable Named Level Hierarchy Aggregations option applies to the named level and the

default hierarchies.

• The Enable Parent Child Hierarchy Aggregations option applies to parent child hierarchies.

Note:

For the Period, Data entry period and Account dimensions, the Enable Parent Child Hierarchy Aggregations option does not appear. However, you can activate this option for the Account dimension

by setting the following key in the Cartesis.InformationDelivery.Workbench.exe.config file: <add key="IsAccountDimensionAggregatable" value="true"/>.

Concurrently, for aggregatable hierarchies, you can deactivate the calculation at the "All" node level when not relevant. The Deactivate 'All' node calculation option applies to all types of hierarchies of the dimension. When the option is selected, the behavior is as follows in your data retrieval tool:

• The 'All' node is neither displayed nor calculated on a default hierarchy.

• The 'All' node is displayed but not calculated on the named level and parent child hierarchies.

Restriction:

In SAP NetWeaver Business Warehouse deployments:

• The aggregation is always performed on all dimensions (except for the Account dimension),

whether the aggregation options have been selected or not.

• When the aggregation options are selected, on an Account parent child hierarchy, the aggregations

are automatically activated also on the named level hierarchy.

2010-12-0943

Page 44

Views

3.7.7.3 Automatic Aggregations Enabled on the Period and Data Entry Period Dimension Hierarchies

You can choose to apply a different behavior on time aggregation by activating the automatic time aggregation based on SAP BusinessObjects Financial Consolidation flow types. To do so, you will choose from the Flow dimension an SAP BusinessObjects Financial Consolidation category scenario that will be used as a reference.

The behavior of the flows will be as described in the selected SAP BusinessObjects Financial Consolidation category scenario.

The time aggregation will apply to both period and data entry period dimensions, provided that they are not merged. This means that the behavior of the accounts will be driven by the selected flow as shown below:

Aggregation mode in the cubeFinancial Consolidation Flow type

Last non empty periodYear To Date

SumPeriodic (Monthly)

First non empty periodOpening flow

Last non empty periodClosing flow

Last non empty periodMovement flows

Last non empty periodOther flows

Note:

The default aggregation mode is the sum.

Restriction:

This function will not be taken into account for a SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployment.

Example:

The examples below describe the three different aggregation modes and therefore, which amounts will be displayed in your data retrieval tool. No amount has been entered in March.

In the table below, the aggregation mode is 'Last non empty period'.

In this example, as no amount has been entered for March, the amount in Quarter 1 is the amount in February, since it is the last amount that has been entered.

2010-12-0944

Page 45

Views

In the table below, the aggregation mode is 'Sum'.

In this example, all the entered amounts are added.

In the table below, the aggregation mode is 'First non empty period'.

In this example, the amount in Quarter 1 is the first amount that has been entered, which is the amount in January.

Related Topics

• Activating Automatic Time Aggregation

3.7.7.3.1 Activating Automatic Time Aggregation

This function will not be taken into account for an SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployment.

Select the Flow dimension.

Select the General tab.

Select the category scenario you want from the Defining Category Scenario drop-down menu.

Note:

If you do not want to apply the automatic time aggregation, select None from the drop-down menu.

3.7.7.4 Hierarchy Selection and Definition for the Period and Data Entry Period Dimensions

For each dimension, the fiscal hierarchy is automatically included for deployment.

2010-12-0945

Page 46

Views

You can choose to also include the calendar hierarchy.

You can define independent formatting for the fiscal and calendar hierarchies.

You can access the Hierarchies tab by selecting View > Dimensions > [dimension] > Hierarchies

In the Hierarchies tab of the Period or Data Entry Period dimensions, you can perform the following actions:

• Select a default member for the hierarchies, using the Edit button next to the Default Member field.

If only the fiscal hierarchy is included, you can select any member as the default member. If you also include the calendar hierarchy, you can only set a member that is not a node as the default member for both hierarchies. If you select a node as the default member, a message appears, explaining that the calendar hierarchy has been deselected. If you want to include the calendar hierarchy again, you must first perform a clear on the default member.

• Define the format for the fiscal hierarchy. To do so, select the format you want from the Fiscal

Hierarchy Format drop-down menu. The format you have chosen appears in the Selected Hierarchies area.

• Include the calendar hierarchy and define its format. To do so, click the Include Calendar Hierarchy

option and select the format you want from the drop-down menu. The hierarchy and the format you have chosen appears in the Selected Hierarchies area.

Note:

If you choose Code from one of the format drop-down menus, the hierarchy will appear as a list.

• Order the year members by ascending or descending order, using the Year Descending Order

option. By default, the years are in ascending order and the option is not checked. The members inside the year nodes are unchanged.

Note:

• If Code is selected for either the Fiscal Hierarchy Format or the Include Calendar Hierarchy

option, the Year Descending Order is not activated.

• If you select both calendar and fiscal hierarchies, so that the hierarchies are correctly ordered,

select Year for both hierarchies.

• Choose to add a year prefix or suffix to the quarters or semesters. You can also choose the format

for the year prefix or suffix: YY or YYYY.

Restriction:

Prefixes and suffixes will not be taken into account for a SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployment.

• Define and translate the names of semesters and quarters as they will appear in the reports. You

can do so in the Translation tab.

Note:

The Half Year Captions or Quarter Captions are not available if semesters or quarters are not part of the hierarchy format you have chosen.

Related Topics

• Start and End Date Definition for Periods

2010-12-0946

Page 47

Views

3.7.7.5 General Actions on Hierarchies

After selecting a hierarchy, you can:

• Rename and translate a hierarchy.

Restriction:

For SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployments, the name of a hierarchy must not exceed 60 characters. In this case, an issue to resolve will occur and you will have to modify the name of the hierarchy.

• Select a default member for a hierarchy. Even if several hierarchies are selected, you can choose

a default member from among the members of a single hierarchy.

• If several hierarchies are selected, including a Parent Child hierarchy, the members of the Parent

Child hierarchy will be available for selection.

• If several hierarchies are selected, not including a Parent Child hierarchy, the members of the

flat list (default hierarchy) will be available for selection.

• Enter a name in each language for the "All" node of a hierarchy.

• Sort in each level of a hierarchy:

• By code. This is the default sort method.

• By internal identifier. These are the SAP BusinessObjects Financial Consolidation database

identifiers.

• By additional descriptions, selected for dimension members.

• By attribute. If a characteristic is defined as an attribute, you can sort the hierarchy by attribute

(only at the leaf level of the hierarchy).

Note:

When a sort is performed at the leaf level of a hierarchy, the sort will be applied to each level of any hierarchy selected for this dimension.

• Suppress all the leaf members and keep only the nodes of a Named level hierarchy.

Restriction:

None of the following functions are taken into account in a SAP NetWeaver BW deployment: selecting a default member for a hierarchy, naming the "All" node in several languages, sorting in each level of a hierarchy and deleting all the leaf members of a Named level hierarchy.

Related Topics

• Renaming a Hierarchy

• Translating a Hierarchy

• Selecting a Default Member for a Hierarchy

• Setting a Name for the "All" Node of a Hierarchy

2010-12-0947

Page 48

Views

3.7.7.5.1 Selecting a Hierarchy

For SAP NetWeaver Business Warehouse (SAP NetWeaver BW) cube deployments only, you can select several Parent Child hierarchies per dimension and per cube.

• In the Characteristics or Self-referenced characteristics groupboxes, select the hierarchy required

by checking the boxes. In terms of the Account and Reporting Unit dimensions, check the Include option in order to be able to select a hierarchy from the drop-down menu.

The hierarchy appears in the Selected Hierarchies groupbox.

3.7.7.5.2 Renaming a Hierarchy

For SAP NetWevaver Business Warehouse deployments, the name of a hierarchy must not exceed 60 characters. In this case, an issue to resolve will occur and you will have to modify the name of the hierarchy.

In the Selected Hierarchies groupbox, right-click on the appropriate hierarchy and select Rename. The name of the hierarchy appears highlighted.

Enter the new name.

Note:

You can also rename the hierarchy in the Translation tab.

3.7.7.5.3 Translating a Hierarchy

For SAP NetWevaver Business Intelligence deployments, the name of a hierarchy must not exceed 60 characters. In this case, an issue to resolve will occur and you will have to modify the name of the hierarchy.

Select the Translation tab.

Enter the translations for each language.

3.7.7.5.4 Selecting a Default Member for a Hierarchy

The default member will not be taken into account for a SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployment.

In the Hierarchies tab, click the Edit button next to the Default Member field. The Choose The Default Member dialog box appears.

Select the member you want to be the default member.

Click the OK button. The default member appears in the Default Member field.

Note:

You can then remove the default member by clicking the Clear button.

3.7.7.5.5 Setting a Name for the "All" Node of a Hierarchy

The names of the "All" node will not be taken into account in a SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployment.

Select the Translation tab.

2010-12-0948

Page 49

Views

Enter the text you want for each language.

Click the OK button.

3.7.7.5.6 Sorting Hierarchies

The sort will not be taken into account for an SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployment.

In the Selected Hierarchies groupbox, right-click on the appropriate hierarchy level and select Order by Attribute.

The Select an ordering attribute dialog box appears.

Select the element on which you want the sort to be performed (code, internal identifier or an attribute).

Click the OK button.

Related Topics

• General Actions on Hierarchies

3.7.7.5.7 Deleting the Leaf Members and Keep only the Nodes of a Hierarchy

You can delete the leaf members only for a Named level hierarchy.

Note:

This funtion will not be taken into account for an SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployment.

• In the Selected Hierarchies groupbox, right-click on the top most level of the hierarchy (the name

of the hierarchy) and select Suppress Dimension Member. The leaf level is greyed out.

3.7.8 Attribute Selection

For each dimension (except for the Period and Data entry period dimensions), you can select the attributes you want to load in the cube by selecting the following elements:

• Self-referenced characteristics.

Restriction:

The attributes based on self-referenced characteristics are not supported in an SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployment.

• Characteristics.

• Properties.

2010-12-0949

Page 50

Views

Restriction:

The attributes based on boolean and text properties will not be taken into account for an SAP NetWeaver BW deployment.

These characteristics and properties are the ones defined for the dimension in SAP BusinessObjects Financial Consolidation. They are treated as attributes. The benefits are:

• Ability to perform advanced selections based on attributes and filtering expressions such as is / is

not, combined conditions, etc.

• Presentation enhancement such as the ability to create a calculated description of a member + a

characteristic.

The attribute name can be customized by the user to fit with OLAP analysis needs.

Note:

In some cases, if SAP BusinessObjects Financial Consolidation characteristics are selected as hierarchies, they will automatically be considered as attributes.

• The upper part of the screen displays all the self-characteristics, characteristics and properties that

are defined in SAP BusinessObjects Financial Consolidation for the selected dimension.

• When you select one of them, it appears in the Translation tab.

• You can then rename the characteristic or property in the different languages available by clicking

in the Translation tab and entering the text of your choice.

3.7.9 Standard Dimensions Exclusion

You chose a specific number of dimensions when creating the solution.

However, you can choose not to use specific dimensions. In other words, you can specify that you do not want some dimensions to be included in the future cube. If you exclude a dimension, the name of the dimension and the names of the members will not appear. However, the amount will appear in the cube as follows:

• If you manually select some members, the total amount of the selected members (in the Members

tab) will be exported.

• If you select the Select all members option, the total amount of all the dimension members will be

exported.

Once a dimension is excluded, you will then be able to include it again.

3.7.9.1 Excluding a Standard Dimension

2010-12-0950

Page 51

Views

In the tree structure part of the window, select the appropriate dimension.

Select the General tab.

Check the Exclude dimension box. In the tree structure part of the window, the excluded dimension appears in italics.

Note:

• You can also exclude a dimension by right-clicking on it in the tree structure and by selecting Exclude.

By default, all the members of the dimension will be aggregated.

• To reinclude an excluded dimension, uncheck the Exclude dimension box.

• You can also exclude or include all the standard dimensions by right-clicking on the Dimensions

node in the tree structure and by selecting Exclude All Dimensions or Include All Dimensions.

3.7.10 Hide Excluded Dimensions

You can hide or show the excluded dimensions that will not be deployed in the cube.

Hiding excluded dimensions enables you to mask information that is not pertinent.

3.7.10.1 Hiding Excluded Dimensions

Select Tools > Otpions > Display tab.

Check the Hide Excluded Dimensions box. In the tree structure part of the window, the excluded dimensions no longer appear.

Note:

To show the excluded dimensions again, uncheck the Hide Excluded Dimensions box.

3.7.11 Database and Cube Structure Synchronization

For each standard dimension, you can define synchronizing intervals so that the cube structure is consistent with the SAP BusinessObjects Financial Consolidation database. The members of dimensions that have been added, modified or deleted in the SAP BusinessObjects Financial Consolidation database tables will be synchronized.

2010-12-0951

Page 52

Views

If you do not activate the synchronization, the cube structure will remain in the same state it was in when you defined the dimensions. To refresh the cube structure, you will need to deploy or process the cube again.

Caution:

This synchronization only works if you have selected the members of the dimensions using characteristics.

Note:

• If you chose to historize the scope hierarchies when creating the view, the Live Access tab is

disabled for the Reporting Unit dimension.

• This function is not supported for SAP NetWeaver Business Warehouse (SAP NetWeaver BW)

deployments.

The intervals are as follows:

• Query Poll Interval. This option enables you to tell the system when to scan all the SAP

BusinessObjects Financial Consolidation tables in order to detect modifications. If modifications are detected, the system processes the synchonization. See example 1 below.

• Silence interval and Silence override interval.

These intervals will perform a partial update. The complete interval to update the cube will be Query Poll Interval + Silence interval or Silence override interval. See example 2 below.

Note:

If the user does not use the options in the Advanced part, the delay interval to update the cube will be by default equal to the Query Poll Interval + 1 second.

• Rebuild interval. This allows you to specify how often the cube should be completely processed,

regardless of whether the structure has been modified or not. See example 3 below.

Example:

If you specify the information below, the tables will be scanned every 5 minutes.

Minutes5Query Poll Interval

Example:

If you specify the information below, when the dimension is modified, the system waits until there are no modifications made in SAP BusinessObjects Financial Consolidation database for 10 minutes and then synchronizes the dimension members. If, however, there is no 10 minute break in the modifications, the system will synchronize the dimension members after 20 minutes (Silence Override Interval value).

2010-12-0952

Page 53

Views

Example:

If you specify the information below, the cube will be entirely synchronized with the dimension structure every two hours even if no modifications have been made.

3.7.11.1 Enabling the Dimension Member Synchronization

Minutes10Silence interval

Minutes20Silence override interval

Hours2Rebuild interval

In the tree structure part of the window, select the appropriate dimension.

Select the Live Access tab.

Check the Activate live access box.

Define what you want in the Query Poll Interval field and drop-down menu.

Click the Advanced button to define the other elements. This is optional.

In the Cache Settings groupbox, define the different elements. This is optional.

3.8 View Copy

You can copy and paste a view in a solution.

When you do so, you also automatically copy and paste the view's deployments.

Once you have copied a view, you can rename it.

Related Topics

• Renaming a View

2010-12-0953

Page 54

Views

3.8.1 Copying and Pasting a View

In the tree structure part of the window, right-click on the view you want to copy and select Copy.

Right-click on the solution you want the view to be copied in and select Paste.

3.9 Renaming a View

In the tree structure part of the window, right-click on the view you want to rename and select Rename The name of the view appears highlighted.

Enter the new name.

2010-12-0954

Page 55

Cube Deployments

4.1 Introduction to Cube Deployments

You can create two types of deployments:

• SSAS cube deployments

• SAP NetWeaver Business Warehouse (SAP NetWeaver BW) cube deployments

Related Topics

• SSAS Cube Deployments

• SAP NetWeaver Business Warehouse Cube Deployments

4.2 SSAS Cube Deployments

You will now create an SSAS cube deployment.

Once a deployment has been created, you will carry out the following steps:

• Entering deployment and cube information

• Specify the automatic creation of the universe associated to the cube.

• Synchronizing database and cube data

• Creating calculated members

• Using your own MDX scripts in a deployment

• Creating SSAS named sets based on SAP BusinessObjects Financial Consolidation characteristics

and filters

• Resolving issues

• Loading external data into a cube

• Deploying and processing a cube

• Updating a deployment

• Copying a deployment

2010-12-0955

Page 56

Cube Deployments

• Renaming a deployment

Related Topics

• SSAS Deployment and Cube Information

• Database and Cube Data Synchronization

• Calculated Members

• Using your own MDX Scripts in a Deployment

• SSAS Named Set Creation based on SAP BusinessObjects Financial Consolidation Characteristics

and Filters

• SSAS Deployment Issue Resolution

• External Data Loading into an SSAS Cube

• SSAS Cube Deployment and Processing

• SSAS Deployment Update

• Deployment Copy

• Renaming a Deployment

4.2.1 SSAS Deployment Creation

Creating an SSAS deployment consists of the following main steps:

• Entering a name for the deployment.

• Choosing the SSAS server. This is the server on which SSAS is installed and where the cubes will

be stored.

4.2.1.1 Creating an SSAS Deployment

In the tree structure of the main window, right-click on Deployments, then select Add Deployment. The New Deployment dialog box opens.

In the Deployment Name field, enter the name you want to give to the deployment.

In the Server Type area, select SSAS 2005.

From the Target Server drop-down menu, select the SSAS server.

Note:

You will be able to select the database in the Options tab of the deployment once it is created.

The Deployer Service Url field is filled in by default. The URL comes from the Cartesis.InformationDelivery.Workbench.exe.config file, which is located in the cube designer installation directory. You can change the URL. It will be effective for the current deployment.

2010-12-0956

Page 57

Cube Deployments

Note:

If you change the URL in the file, it will be applied to all deployments.

Click the OK button.

The deployment appears below Deployments.

4.2.2 SSAS Deployment and Cube Information

Carry out the following steps:

• Choose the SSAS database. You chose the SSAS database server while creating the deployment

and it is displayed in the General tab.

• Modify the name of the future cube. By default, the cube is given the deployment name.

• Choose the default language for the cube. The available languages are the ones chosen in the view.

All the languages chosen in the view will be available in the future cube, but a default language needs to be chosen in the deployment.

• Specify the parent amounts. In the data access group you belong to in SAP BusinessObjects Financial

Consolidation, you might not be allowed to view all the children of a specific parent. You can choose which children the parent amount should take into account:

• The parent amount is the sum of all its children, even those which you are not allowed to see. In

this case, you will uncheck the Enable Visual Totals option.

• The parent amount is the sum of only the children you are allowed to see. In this case, you will

leave the Enable Visual Totals option checked, as it is by default.

• Choose a default number format.

You choose the default number format that will be taken into account for the entire SSAS cube.

You can choose a predefined format from the Measure Format drop-down menu or you can directly enter the format of your choice in the same menu.

Note:

The format is defined at the deployment level, enabling you to apply different formats to different deployments.

You can define all of the above elements in the Options tab of a deployment.

Related Topics

• Language Selection

2010-12-0957

Page 58

Cube Deployments

4.2.3 Automatic Universe Creation

You can choose to create an OLAP universe that will be based on the SSAS cube. Once the cube is deployed, the universe is automatically created.

All the SAP BusinessObjects tools supporting OLAP universes will be able to connect to the universes generated by cube designer and retrieve SAP BusinessObjects Financial Consolidation data security.

For the universe to be created automatically, you need to enter the following information:

• Universes Folder. You must enter the path to a folder that already exists on the SAP BusinessObjects

Enterprise platform.

The path can begin with the / character but it is not mandatory.

• Universe Name. You must enter the name that you want to give to the universe.

Restriction:

The name of the universe must not contain any of the following characters: ?.*:<>|/\"'

Caution:

If the name already exists in the specified folder of the platform, the existing name will be overwritten.

Example: Path in the Universes Folder field.

/InteractiveAnalysis universes/My universes

4.2.3.1 Automatically Creating a Universe

In the Options tab of the SSAS deployment, select Automatically create associated universe. The fields below are made available.

Enter a path in the Universes Folder field.

Enter a name for the universe in the Universe Name field taking into account the appropriate syntax limitations.

Related Topics

• Automatic Universe Creation

2010-12-0958

Page 59

Cube Deployments

4.2.4 Database and Cube Data Synchronization

For each deployment, you can define synchronizing intervals so that the cube data will be consistent with the SAP BusinessObjects Financial Consolidation database data.

If you do not activate the synchronization, the cube data will remain as it was when you deployed the cube. To refresh the cube data, you will need to process the cube again.

The synchronization applies to all the tables that have been modified. If you only want to synchronize the data related to certain data entry periods, you can select them.

Caution:

In this version, the synchronization only applies to the tables that existed when the deployment was done. If a new consolidation table is created in the SAP BusinessObjects Financial Consolidation database, you will need to deploy the cube again in order to get the synchronization.

Tip:

If you want to avoid redeploying the cube, you can create and run your consolidation definitions in SAP BusinessObjects Financial Consolidation in advance, even if they are empty. As a consequence, all the consolidations will appear in cube designer and will be synchronized.

The intervals are the following:

• Query Poll Interval

• Silence interval and Silence override interval

• Rebuild interval

4.2.4.1 Query Poll Interval

This option enables you to tell the system when to scan all the SAP BusinessObjects Financial Consolidation tables in order to detect modifications. If modifications are detected, the system processes the synchonization.

Example:

So that the tables are scanned every 5 minutes, specify the following in the Query Poll Interval area: 5 Minutes.

2010-12-0959

Page 60

Cube Deployments

4.2.4.2 Silence Interval and Silence Override Interval

These intervals will perform a partial update. The complete interval to update the cube will be Query Poll Interval + Silence Interval or Silence Override Interval.

Note:

If the user does not use the options in the Advanced part, the delay interval to update the cube will be by default equal to the Query Poll Interval + 1 second.

Example:

When data is modified, the system waits until there are no modifications made for 10 minutes and then synchronizes the data and the cube. If, however, there is no 10 minute break in the modifications, the system will synchronize the data and the cube after 20 minutes.

Silence interval: 10 Minutes.

Silence override interval: 20 Minutes

4.2.4.3 Rebuild Interval

This allows you to specify how often to synchronize the data, regardless of whether the data has been modified or not.

Example:

So that the cube is synchronized with the data every two hours even if no modifications have been made, specify the following in the Rebuild interval area: 2 Hours.

4.2.4.4 Activating the Data Synchronization

In the tree structure part of the window, select the appropriate deployment.

Select the Options tab.

In the Live Access groupbox, select the Activate live access option.

2010-12-0960

Page 61

Cube Deployments

To synchronize only the data related to some data entry periods, select the For selected data Entry Periods option, then click the button next to this option to select the data entry periods of your

choice.

In the Query Poll Interval field and drop-down menu of the Cache Settings groupbox, define what you want.

Click the Advanced button to define the other elements. This is optional.

Define the different elements.

4.2.5 Calculated Members

You can create a member containing an MDX formula for the following dimensions:

• The SSAS Measure dimension

• All the merged dimensions

• All the standard dimensions

Note:

• You can also use MDX scripts.

• You can also import members that you have previously exported using the SAP BusinessObjects

EPM solutions, add-in for Microsoft Office. In the EPM add-in, these members are called "custom members".

You can choose not to display the calculated members in the retrieval tool, using the Visible option. The calculations are performed but the members are not displayed.

You can enter comments to keep track of what issue the calculated members are designed to resolve: content, etc.

You can also translate the names of calculated members in all available languages.

Example:

To calculate the percentage of a product towards its parent in the Product hierarchy, we create a new measure called "Percentage of a product towards its parent".

The formula syntax is as follows:

[Measures].[Consolidated AmountSales by product and geographical zone]/

([Product].[Productrollup].currentmember.parent,[Measures].[Consolidated AmountSales by product and geographical zone]) * 100

Comments :

• [Consolidated AmountSales by product and geographical zone] is the measure containing the

analyzing data analyzed by the Product dimension.

2010-12-0961

Page 62

Cube Deployments

• [Product].[Productrollup].currentmember.parent,[Measures].[Consolidated AmountSales by product

and geographical zone]: this means that we took the amount for the parent of the current member in the Product hierarchy (called [Productrollup]) and for the measure [Consolidated AmountSales by product and geographical zone].

This example applies if you are in multi-measure mode. If you were in single measure mode, the measure would be 'Consolidated Amount'.

Related Topics

• Using your own MDX Scripts in a Deployment

4.2.5.1 Creating Calculated Members

In the tree structure part of the window, select the appropriate deployment.

Select the Calculated Members tab.

Click the New button. The Calculated Member dialog box appears.

The Visible option is checked by default. If you do not want the calculated member to appear in the retrieval tool, deselect the option.

In the Name field, enter the name you want.

Select the appropriate option: Measure, Merged Dimension or Dimension.

Note:

The Custom option enables you to use your own MDX scripts.

If you have selected Merged Dimension or Dimension, from the Dimension drop-down menu, select the dimension for which you want to create the calculated member.

If you have selected a standard dimension, select a hierarchy from the Hierarchy drop-down menu.

Note:

• A calculated member is always linked to a specific hierarchy. For a merged dimension and a

Measure dimension, the linked hierarchy is the default hierarchy, which you do not need to select.

• The hierarchies that are available in the drop-down menu are the ones you selected in the

Hierarchies tab for the chosen dimension.

Click the button next to the Member field.

10.

Select the member you want as the parent of the calculated member.

11.

In the Expression area, enter or copy the MDX formula you want. Instead of manually entering the members in the formula, you can select the members by clicking the Insert Member button.

12.

In the Comment area, enter the text of your choice.

13.

Click the OK button.

2010-12-0962

Page 63

Cube Deployments

Related Topics

• Using your own MDX Scripts in a Deployment

4.2.5.2 Importing Calculated Members

Using the EPM add-in, you have previously created "custom members" and exported them in a file.

In the tree structure part of the window, select the appropriate deployment.

Select the Calculated Members tab.

Click the Import button. The Calculated member import wizard opens.

Select the file containing the members you want to import using the File name button and click Next.

Select the members you want to import and click Next. A summary describes which members are about to be imported.

Click Finish.

4.2.5.3 Translating Calculated Members

In the tree structure part of the window, select the appropriate deployment.

Select the Translation tab.

In the Calculated Members area, enter the names in the available languages.

4.2.6 Using your own MDX Scripts in a Deployment

You can now use your own MDX scripts in cube designer. You can therefore link a script to a specific deployment. The script will be deployed along with the cube each time you launch the deployment.

To do so, you must copy your MDX script and copy it in the Calculated Members tab in Financial Consolidation Cube Designer. The script is saved as a custom calculated member.

2010-12-0963

Page 64

Cube Deployments

4.2.6.1 Linking your Script to a Deployment

In your own tool, copy your MDX script.

In the tree structure part of the window in cube designer, select the appropriate deployment.

Select the Calculated Members tab.

Click the New button. The Calculated Member dialog box appears.

In the Name field, enter the name you want.

Select the Custom option.

In the Expression area, copy the MDX script.

In the Comment area, enter the text of your choice.

Click the OK button.

Note:

You can translate the calculated member in the Translation tab.

4.2.7 SSAS Named Set Creation based on SAP BusinessObjects Financial Consolidation Characteristics and Filters

You can create SSAS Named sets from SAP BusinessObjects Financial Consolidation characteristics, filters, or any manual selection.

A Named set is a selection of dimension members that will be used as a flat list to create reports. It is the equivalent of SAP BusinessObjects Financial Consolidation filters.

• If creating a named set from characteristics, all dimension members associated to this characteristic

value will be added to the cube.

• If creating a named set from filters, the complete filter will be retrieved.

• You can also enter an MDX formula that specifies the named set you want to create.

Provided that your data retrieval tool can retrieve named sets, you will be able to use the named sets in MDX formulas or to select a set of dimension members.

You can translate the names of named sets in all available languages.

2010-12-0964

Page 65

Cube Deployments

4.2.7.1 Creating SSAS Named Sets

In the tree structure part of the window, select the appropriate deployment.

Select the Named Sets tab.

Click the New button. The Create Named Set dialog box appears.

Enter a name for the named set.

Select the option corresponding to the source you want to use for the named set: Use characteristic, Use filter.

Note:

If you select the Supply MDX option, click the Next button, and simply enter the MDX formula that specifies the named set in the Free MDX area.

Click the Next button.

From the Select dimension drop-down menu, select the dimension that you want to use for the named set.

Click the Next button.

From the Select Characteristic drop-down menu, select the characteristic or filter you want to use as part of the named set.

10.

Click the Next button.

11.

In the Select Characteristic Member area, select the members you want to use to populate the named set.

12.

Click the Next button.

13.

Click the Finish button.

4.2.7.2 Translating SSAS Named Sets

In the tree structure part of the window, select the appropriate deployment.

Select the Translation tab.

In the Named Sets area, enter the names in the available languages.

4.2.8 SSAS Deployment Issue Resolution

2010-12-0965

Page 66

Cube Deployments

Before deploying and processing a cube, you need to resolve the issues that are listed in the Issues To Resolve tab. The tab only appears if there are issues and once you have resolved the issues, the

tab no longer appears.

In the tab, you can double-click a row indicating an issue. The location where you must correct the issue is automatically displayed.

4.2.9 External Data Loading into an SSAS Cube

You can load data that are not stored in SAP BusinessObjects Financial Consolidation directly into the cube.

Caution:

The SAP BusinessObjects Financial Consolidation database server and the external table database server must be the same type; Oracle and Oracle or SQL and SQL.

However, the following conditions must be respected:

• The table containing the external data must be defined by the user in cube designer.

• The dimension members must exist in SAP BusinessObjects Financial Consolidation database so

that the proper security applies.

• The data table must follow a specific format to be compatible.

You can load data into existing SAP BusinessObjects Financial Consolidation dimension members but no new dimensions or members can be created.

You must select in the cube designer view, the right dimensions and dimension members (based on the data that you want to import) and measures for both analyzing dimensions and data level (package/ consolidated data). For example, if the measure corresponding to an analysis (for example, by product) is not selected in the cube designer view and if the external table already contains data analyzed by product, the data will not be available in the cube deployed from this view.

Restriction:

If the Reporting Category dimension exists in a view, the table from which you want to load data must be in the SAP BusinessObjects Financial Consolidation database.

Related Topics

• Reporting Category Dimension Creation

4.2.9.1 Dimension Members

2010-12-0966

Page 67

Cube Deployments

Only a specific format for data tables is supported by cube designer. This table should contain the identifiers of the SAP BusinessObjects Financial Consolidation members for each dimension (one column by dimension in the table).

As opposed to the SAP BusinessObjects Financial Consolidation and Carat fact tables, all dimensions must be available in the external tables, especially the Category + Data Entry period dimensions (for package data) + scope, variant and consolidation currency (for consolidated data).

For these missing dimensions, the system requires that their columns are named as follows:

• Category

• Scope

• Variant

• Conscurrency

• DEPeriod

As far as other dimensions are concerned, the names of the colums are the same as in SAP BusinessObjects Financial Consolidation fact tables.

4.2.9.2 Amounts

The external table should contain one or several columns dedicated to containing data: one column named 'amount' (for package data), another column named 'convamount' for converted data, another column named 'consamount' for consolidated data. If the SSAS 2005 cube is based on package data (defined in the view from which it has been deployed), only the first column (amount) will be taken into account in the deployment. If the SSAS 2005 cube is based on consolidated data (defined in the view), the columns amount, converted amount and consolidated amount could be taken into account during the deployment step (depending on the measures selected in the view).

4.2.9.3 Server Selection and Server Information Entry

In order to load external data into a cube, you need to select the server and specify some server information. This is the server containing the tables you want to load.

Caution:

The SAP BusinessObjects Financial Consolidation database server and the external table database server must be the same type; Oracle and Oracle or SQL and SQL.

The Microsoft Data Link Properties dialog box enables you to specify the required information. This dialog box contains four tabs: Provider, Connection, Advanced and All.

2010-12-0967

Page 68

Cube Deployments

The Provider tab enables you to specify if the tables are SQL or Oracle tables.

The Connection, Advanced and All tabs are contextual and depend on the type of provider (SQL or Oracle) selected in the Provider tab.

Related Topics

• Star Schema Deployment Creation

4.2.9.4 Loading External Data into a Cube

In the tree structure part of the window, select the appropriate deployment.

Select the Custom Fact Tables tab.

Click the New button. The Custom Fact Table dialog box appears.

Click the button in the Data Source area. The Data Link Properties dialog box appears, displaying the Connection tab.

In the Connection tab, specify the required information.

You must ensure that the Allow saving password option is selected.

Click on Test Connection. A message appears, indicating whether the connection is valid or not.

If the connection is valid, click on OK. The Data Link Properties dialog box reappears.

Click on OK. The server information is displayed in the Data Source area.

10.

In the Table Name area, enter the table name as it will appear in cube designer.

11.

Leave Default in the Measure Group drop-down menu.

12.

Click on OK.

4.2.10 SSAS Cube Deployment and Processing

Deploying a cube consists of creating a cube's structure.

Processing a cube consists of loading data in a cube.

2010-12-0968

Page 69

Cube Deployments

When a cube is deployed, it is automatically processed. You can also choose to re-process only an existing cube or only one or several parts of the cube, that is packages or consolidations (depending on the data level of the view), or specific dimensions.

Before deploying a cube, the Deployment tab enables you to view all of the information that will be taken into account in the cube. This tab displays:

• All of the dimensions defined in the view.

• All SAP BusinessObjects Financial Consolidation packages or consolidations selected (depending

on the data level of the view). These are indicated by a yellow cube.

In the Action colum:

• If nothing is displayed for a specific dimension or member row, this means that the dimension or

member was excluded or had never been included in the view and therefore will not be exported.

• The following information may appear:

• Add: if the corresponding dimension or member was excluded in the last deployment but is now

• Update: if the corresponding dimension or member was included in the last deployment and is

being included.

again being included.

• Remove: if the corresponding dimension or member was included in the last deployment but is

now being excluded.

Note:

When clicking the Deployment tab, an error can occur if the timeout has been reached (if there is a large number of consolidation). To increase the timeout, you can change the WebClientTimeout key value in the Designer Cartesis.InformationDelivery.Workbench.exe.config file.

While deploying and processing a cube, you can follow the steps in the bottom part of the window.

If this part does not appear, select View > Deployment Log .

You can perform the following actions on the log:

• Display or hide one or more types of information by clicking the Errors, Warnings and/or Messages

buttons.

• Errors: Errors cause the deployment and processing to fail.

• Warnings: Warnings are indicated but do not prevent you from deploying and processing the

cube successfully.

• Messages: Messages indicate each step of the deployment and processing (for example, "Starting

to build the cube").

• Delete the log by clicking the Clear List button.

• Export the log in .csv format, by clicking the Export List button.

Note:

If there are duplicated members, a pop-up message will appear while deploying the cube, indicating the remaining duplicated members and asking you whether you want to continue or stop the deployment.

2010-12-0969

Page 70

Cube Deployments

Caution:

Before deploying and processing a cube, you need to resolve any remaining issues. If some issues are unresolved, the Issues to Resolve tab appears and the Deploy button is not accessible.

You can also deploy or process a cube without using the cube designer interface.

Related Topics

• Member Name for Standard Dimensions

• SSAS Deployment Issue Resolution

• Deploy, Process, Re-Process and Update Actions

4.2.10.1 Deploying an SSAS Cube

• In the Deployment tab, click the Deploy button.

Note:

• The cube will also be processed.

• The date of the deployment will appear in the Last Deployed On field of the General tab.

4.2.10.2 Processing an SSAS Cube

• In the Deployment tab, click the Re-Process button.

Note:

The date of the re-process will appear in the Last Processed On field of the General tab.

4.2.10.3 Processing only Parts of an SSAS Cube

If you do not want to re-process the whole cube, you can choose to re-process some parts of the cube, that is packages or consolidations (depending on the data level of the view) that are indicated by a yellow cube in the Deployment tab, or dimensions.

In the Selected column of the Deployment tab, select the checkboxes of the parts you want to process.

Click the Re-Process Selected button.

2010-12-0970

Page 71

Cube Deployments

Note:

The date of the re-process will appear in the Last Processed On field of the General tab.

4.2.11 SSAS Deployment Update

You can update a deployment.

The following items will be updated:

• Calculated members.

• Named sets.

• Live access settings.

Related Topics

• Calculated Members

• SSAS Named Set Creation based on SAP BusinessObjects Financial Consolidation Characteristics

and Filters

• Database and Cube Data Synchronization

4.2.11.1 Updating an SSAS Deployment

• In the Deployment tab, click the Update button.

4.2.12 Remove an SSAS Cube

You can remove a cube from cube designer.

In SSAS management tools, the cube, its dimensions, its corresponding data source and data source view are deleted.

4.2.12.1 Removing an SSAS Cube

2010-12-0971

Page 72

Cube Deployments

In the Deployment tab, click the Remove Cube button. A confirmation message appears.

Click the Yes button.

4.2.13 Remove an SSAS Database

You can remove a database from cube designer.

In this case, the database is deleted along with all its cubes.

4.2.13.1 Removing an SSAS Database

In the Deployment tab, click the Remove Database button. A confirmation message appears.

Click the Yes button.

4.3 SAP NetWeaver Business Warehouse Cube Deployments

You will now create a SAP NetWeaver Business Warehouse (SAP NetWeaver BW) cube deployment.

Once a deployment has been created, you will carry out the following steps:

• Enter deployment and cube information

• Resolve issues

• Load external data into a cube

• Define the organization of SAP NetWeaver BW dimensions and characteristics

• Deploy and process a cube

• Copy a deployment

• Rename a deployment

SAP BusinessObjects tools that support SAP NetWeaver BW cubes - for example: SAP Business Explorer (SAP BEx) tools, SAP BusinessObjects Interactive Analysis, and SAP BusinessObjects EPM solutions, add-in for Microsoft Office - will be able to analyze the data of these cubes.

2010-12-0972

Page 73

Cube Deployments

Restriction:

• If an SAP NetWeaver BW cube has already been deployed from a cube designer view and BEx

reports have been designed on top of this cube, these reports cannot be used again on top of a new SAP NetWeaver BW cube that will be deployed from the same view. This limitation does not exist for the EPM add-in reports.

• In an SAP BEx report, you can analyze the same metadata coming from several SAP NetWeaver

BW cubes. However, in this particular case, you cannot browse a cube that has been generated with cube designer for the following reason: the SAP BusinessObjects Financial Consolidation codes are not stored in the dimension member keys of the SAP NetWeaver BW cube generated with cube designer.

• SAP NetWeaver BW deployments do not support SAP BusinessObjects Financial Consolidation

data security.

• Additional descriptions for dimension members are not exported into SAP NetWeaver BW cubes.

Only SAP BusinessObjects Financial Consolidation code and short descriptions are always exported.

4.3.1 SAP NetWeaver Business Warehouse Deployment Creation

Creating an SAP NetWeaver Business Warehouse (SAP NetWeaver BW) deployment consists of the following main steps:

• Entering a name for the deployment.

• Entering the user name and password to SAP NetWeaver BW.

4.3.1.1 Creating an SAP NetWeaver Business Warehouse Deployment

Your administrator must provide you with the user name and password to SAP NetWeaver Business Warehouse (SAP NetWeaver BW) that you need to enter when creating the deployment.

In the tree structure of the main window, right-click on Deployments, then select Add Deployment. The New Deployment dialog box opens.

In the Deployment Name field, enter the name you want to give to the deployment.

In the Server Type area, select NetWeaver BW.

Note:

In the Server Details area, the fields Application Server, System Number and Client are filled in by default with information from the Central Management Console.

In the User and Password fields, enter the user name and password provided by your administrator.

2010-12-0973

Page 74

Cube Deployments

Note:

• The Deployer Service Url field is filled in by default. The URL comes from the

Cartesis.InformationDelivery.Workbench.exe.config file, which is located in the cube designer installation directory. You can change the URL. It will be effective for the current deployment.

• If you change the URL in the file, it will be applied to all deployments.

Click OK.

4.3.2 SAP NetWeaver Business Warehouse Deployment and Cube Information

Carry out the following steps:

• Choose the SAP NetWeaver Business Warehouse (SAP NetWeaver BW) InfoArea. The SAP

NetWeaver BW InfoArea server has automatically been specified while creating the deployment and is displayed in the General tab.

• By default, when you deploy a cube, one cube per packages or consolidation (depending on the

data level of the view) is created. You can choose to deploy all packages or consolidation in one cube by selecting the Deploy in a single infocube option.

• Choose the name of the future cube.

• If more than one language is available, select the language you want for the dimension and hierarchy

names.

Note:

• As a reminder, the languages you want to make available in the future cube have been chosen

in the view and appear available in the Options tab of the deployment (the languages that have not been selected in the view are greyed out). Only the language you select will be available in the cube for dimension and hierarchy names.

• Member names will appear in the cube in all the languages that have been selected for the view.

However, if the language of the retrieval tool you use is not available in the SAP NetWeaver BW cube, internal IDs will appear as names for the members.

You can define all of the above elements in the Options tab of a deployment.

Related Topics

• Language Selection

• SAP NetWeaver Business Warehouse Cube Deployment and Processing

4.3.3 Cube Deployment based on an Existing Cube

2010-12-0974

Page 75

Cube Deployments

You can copy an SAP NetWeaver BW cube from an environment to another one.

Reports based on technical names will continue to work in the second environment.

In the Options tab of a deployment, select the option Enable deployment based on an existing cube. Enter the server information on which the cube you want to copy is located. Then, select the InfoArea and the cube name to specify the cube you want to copy.

Example:

In your production environment, you want to deploy a cube that is based on a cube that already exist in the text environment.

4.3.4 SAP NetWeaver Business Intelligence Deployment Issue Resolution

tab no longer appears.

In the tab, you can double-click a row indicating an issue. The location where you must correct the issue is automatically displayed.

4.3.5 External Data Loading into an SAP NetWeaver Business Warehouse Cube

You can load data that are not stored in SAP BusinessObjects Financial Consolidation directly into the cube.

Caution:

The SAP BusinessObjects Financial Consolidation database server and the external table database server must be the same type; Oracle and Oracle or SQL and SQL.

However, the following conditions must be respected:

• The table containing the external data must be defined by the user in cube designer.

• The dimension members must exist in SAP BusinessObjects Financial Consolidation database.

• The data table must follow a specific format to be compatible.

You can load data into existing SAP BusinessObjects Financial Consolidation dimension members but no new dimensions or members can be created.

2010-12-0975

Page 76

Cube Deployments

is not selected in the cube designer view and if the external table already contains data analyzed by product, the data will not be available in the cube deployed from this view.

Restriction:

If the Reporting Category dimension exists in a view, the table from which you want to load data must be in the SAP BusinessObjects Financial Consolidation database.

Related Topics

• Reporting Category Dimension Creation

4.3.5.1 Dimension Members

For these missing dimensions, the system requires that their columns are named as follows:

• Category

• Scope

• Variant

• Conscurrency

• DEPeriod

As far as other dimensions are concerned, the names of the colums are the same as in SAP BusinessObjects Financial Consolidation fact tables.

4.3.5.2 Amounts

The external table should contain one or several columns dedicated to containing data: one column named 'amount' (for package data), another column named 'convamount' for converted data, another column named 'consamount' for consolidated data. If the cube is based on package data (defined in the view from which it has been deployed), only the first column (amount) will be taken into account in the deployment. If the cube is based on consolidated data (defined in the view), the columns amount, converted amount and consolidated amount could be taken into account during the deployment step (depending on the measures selected in the view).

2010-12-0976

Page 77

Cube Deployments

4.3.5.3 Server Selection and Server Information Entry

In order to load external data into a cube, you need to select the server and specify some server information. This is the server containing the tables you want to load.

Caution:

The SAP BusinessObjects Financial Consolidation database server and the external table database server must be the same type; Oracle and Oracle or SQL and SQL.

The Microsoft Data Link Properties dialog box enables you to specify the required information. This dialog box contains four tabs: Provider, Connection, Advanced and All.

The Provider tab enables you to specify if the tables are SQL or Oracle tables.

The Connection, Advanced and All tabs are contextual and depend on the type of provider (SQL or Oracle) selected in the Provider tab.

Related Topics

• Star Schema Deployment Creation

4.3.5.4 Loading External Data into the SAP NetWeaver Business Warehouse Cube

In the tree structure part of the window, select the appropriate deployment.

Select the Custom Fact Tables tab.

Click the New button. The Custom Fact Table dialog box appears.

Click the button in the Data Source area. The Data Link Properties dialog box appears, displaying the Connection tab.

In the Connection tab, specify the required information.

You must ensure that the Allow saving password option is selected.

Click on Test Connection. A message appears, indicating whether the connection is valid or not.

If the connection is valid, click on OK. The Data Link Properties dialog box reappears.

Click on OK. The server information is displayed in the Data Source area.

2010-12-0977

Page 78

Cube Deployments

10.

In the Table Name area, enter the table name as it will appear in cube designer.

11.

Leave Default in the Measure Group drop-down menu.

12.

Click on OK.

4.3.6 SAP NetWeaver Business Warehouse Dimensions and Characteristics Organization

All the SAP BusinessObjects Financial Consolidation dimensions included in the view are automatically taken into account in the cube deployment. You can add or remove SAP BusinessObjects Financial Consolidation dimensions in the future cube by including or excluding them in the view.

• All the SAP BusinessObjects Financial Consolidation dimensions are considered as SAP NetWeaver

Business Warehouse (SAP NetWeaver BW) characteristics.

• These characteristics are grouped together in what are called SAP NetWeaver BW dimensions to

ease the data retrieval in the data retrieval tool you will then use.

An organization of SAP NetWeaver BW characteristics grouped together in SAP NetWeaver BW dimensions is proposed by default in the InfoCube Dimensions tab.

You can modify this presentation at your convenience.

Note:

We strongly recommend that you first choose the SAP BusinessObjects Financial Consolidation dimensions that you want to include in the future cube; then only you can organize them. If you organize them and include or exclude a dimension afterwards, the organization may be automatically reset to its default settings.

The default organization is the following:

• Merged Dimensions. This dimension contains all merged characteristics available in the view,

including the Reporting Category characteristic.

• Consolidation Dimensions. This dimension contains Category, Data Entry Period, Scope, Variant

and Consolidation Currency if they are not used in a merged SAP BusinessObjects Financial Consolidation dimension, excluded from the view or not available due to the view data source level, meaning package or consolidated data.

• Account. This dimension contains the Account characteristic if it is available in the view, meaning

if it is included in the view or not merged together with other SAP BusinessObjects Financial Consolidation dimensions.

• Reporting Unit Dimensions. This dimension contains both Reporting Unit and Origin Unit

characteristics if they are available in the view, meaning if they are included in the view or not merged together with other SAP BusinessObjects Financial Consolidation dimensions.

• Period. This dimension contains the Period characteristic if it is available in the view, meaning if it

is included in the view or not merged together with other SAP BusinessObjects Financial Consolidation dimensions.

2010-12-0978

Page 79

Cube Deployments

• Flow. This dimension contains the Flow characteristic if it is available in the view, meaning if it is

included in the view or not merged together with other SAP BusinessObjects Financial Consolidation dimensions.

• Audit ID. This dimension contains the Audit ID characteristic if it is available in the view,meaning if

it is included in the view or not merged together with other SAP BusinessObjects Financial Consolidation dimensions.

• Currency. This dimension contains the Currency characteristic if it is available in the view, meaning

if it is included in the view or not merged together with other SAP BusinessObjects Financial Consolidation dimensions.

• Elimination. This dimension contains the Elimination characteristic if it is available in the view,

meaning if it is included in the view or not merged together with other SAP BusinessObjects Financial Consolidation dimensions.

• Analysis Dimensions. This dimension contains all SAP BusinessObjects Financial Consolidation

analysis dimensions including Share, Partner and all other custom analysis dimensions, if they are available, meaning if they are included in the view or not merged together with other SAP BusinessObjects Financial Consolidation dimensions.

Note:

As a general rule, a dimension does not appear in the tab if no characteristic is assigned to it.

You can perform the following actions:

• Move a characteristic to a lower or upper dimension.

• Create a dimension.

• Rename a dimension.

• Delete a dimension.

• Reset to the default settings.

4.3.6.1 Moving an SAP NetWeaver Business Warehouse Characteristic to a Lower or Upper Dimension

In the InfoCube Dimensions tab of the deployment, select the characteristic you want to move.

Do one of the following:

• To move the characteristic to the upper dimension, click the up arrow.

• To move the characteristic to the lower dimension, click the down arrow.

4.3.6.2 Creating an SAP NetWeaver Business Warehouse Dimension

In the InfoCube Dimensions tab of the deployment, click the Folder icon. New Dimension appears in the tree structure.

2010-12-0979

Page 80

Cube Deployments

Right-click on New Dimension and select Rename. New Dimension is highlighted.

Enter a name.

4.3.6.3 Renaming an SAP NetWeaver Business Warehouse Dimension

In the InfoCube Dimensions tab of the deployment, right-click on the dimension you want to rename, then select Rename.

Enter the name you want.

4.3.6.4 Deleting an SAP NetWeaver Business Warehouse Dimension

In the InfoCube Dimensions tab of the deployment, select the dimension you want to remove.

Click the cross button. If characteristics were grouped together in the deleted dimension, they are automatically moved to

the lower dimension.

4.3.6.5 Resetting the SAP NetWeaver Business Warehouse Dimensions and Characteristics Organization to its Default

• Click Reset.

4.3.7 SAP NetWeaver Business Warehouse Cube Deployment and Processing

Deploying a cube consists of creating a cube's structure.

Processing a cube consists of loading data in a cube.

When a cube is deployed, it is automatically processed. You can also choose to re-process only an existing cube or only one or several parts of the cube, meaning packages or consolidations (depending on the data level of the view), or specific dimensions.

2010-12-0980

Page 81

Cube Deployments

By default, when you deploy a cube, one InfoCube per package or consolidation (depending on the data level of the view) is created. You can choose to deploy all packages or consolidation in one InfoCube by selecting the Deploy in a single infocube option in the Options tab of the deployment.

Note:

• The deployment name that will be displayed in the Deployment tab, concatenates the name of the

InfoArea and the name of the cube that are entered in the Options tab.

• The Re-process selected button is not available in the Deployment tab.

You can re-deploy a cube. The cube is completely re-created with the same technical names, so that the BEx queries continue to function.

Note:

If you deploy a cube several times, respectively including, excluding and including again a standard dimension or a merged dimension:

• at the second deployment, a message indicates that technical name of the dimension has been

changed and you must update the corresponding BEx query.

• if you do not update the BEx query, at the third deployment, the technical name of the dimension

has been changed between the first and the third deployments and no message warns you to update the BEx query.

Restriction:

In an SAP BEx report, you can analyze the same metadata coming from several SAP NetWeaver BW cubes. However, in this particular case, you cannot browse a cube that has been generated with cube designer for the following reason: the SAP BusinessObjects Financial Consolidation codes are not stored in the dimension member keys of the SAP NetWeaver BW cube generated with cube designer.

Note:

When a view contains several SAP NetWeaver BW deployments, do not deploy more than one cube if they are to be deployed on the same SAP NetWeaver BW server.

Before deploying a cube, the Deployment tab enables you to view all of the information that will be taken into account in the cube. This tab displays:

• All of the dimensions defined in the view.

• All SAP BusinessObjects Financial Consolidation packages or consolidations selected (depending

on the data level of the view). These are indicated by a yellow cube.

In the Action colum:

• If nothing is displayed for a specific dimension or member row, this means that the dimension or

member was excluded or had never been included in the view and therefore will not be exported.

• The following information may appear:

• Add: if the corresponding dimension or member was excluded in the last deployment but is now

being included.

• Update: if the corresponding dimension or member was included in the last deployment and is

again being included.

• Remove: if the corresponding dimension or member was included in the last deployment but is

now being excluded.

2010-12-0981

Page 82

Cube Deployments

Note:

While deploying and processing a cube, you can follow the steps in the bottom part of the window.

If this part does not appear, select View > Deployment Log.

You can perform the following actions on the log:

• Display or hide one or more types of information by clicking the Errors, Warnings or Messages

buttons.

• Errors: Errors cause the deployment and processing to fail.

• Warnings: Warnings are indicated but do not prevent you from deploying and processing the

• Messages: Messages indicate each step of the deployment and processing (for example, "Starting

• Delete the log by clicking the Clear List button.

cube successfully.

to build the cube").

• Export the log in .csv format, by clicking the Export List button.

Note:

If there are duplicated members, a pop-up message will appear while deploying the cube, indicating the remaining duplicated members and asking you whether you want to continue or stop the deployment.

Caution:

Before deploying and processing a cube, you need to resolve any remaining issues. If some issues are unresolved, the Issues to Resolve tab appears and the Deploy button is not accessible.

You can also deploy or process a cube without using the Financial Consolidation Cube Designer interface.

Related Topics

• Member Name for Standard Dimensions

• SSAS Deployment Issue Resolution

• Deploy, Process, Re-Process and Update Actions

4.3.7.1 Deploying an SAP NetWeaver Business Warehouse Ccube

• In the Deployment tab, click the Deploy button.

Note:

The cube will also be processed.

2010-12-0982

Page 83

Cube Deployments

4.3.7.2 Processing an SAP NetWeaver Business Warehouse Cube

• In the Deployment tab, click the Re-Process button.

4.3.7.3 Processing only Parts of an SAP NetWeaver Business Warehouse Cube

If you do not want to re-process the whole cube, you can choose to re-process some parts of the cube, meaning packages or consolidations (depending on the data level of the view) that are indicated by a yellow cube in the Deployment tab, or dimensions.

Note:

If you have selected the Deploy in a single infocube option in the Options tab of the deployment, the Re-Process button is not available.

In the Selected column of the Deployment tab, select the checkboxes of the parts you want to process.

Click the Re-Process Selected button.

4.3.8 Deploying only Most Detailed Data in an SAP NetWeaver Business Warehouse Cube

Some data are not relevant for SAP NetWeaver BW cubes. If non detailed and detailed data are included in a cube, some amounts appear twice.

So that amounts do not appear twice, you can ask to include only most detailed data in a BW cube, using the Dimensional Analysis tab of a BW deployment.

The Financial Consolidation category builder's existing dimensional analysis are read, then:

• If the data are all detailed with the same level of detail, you can select the Include only most detailed

data for account flow/member option. The most detailed data for each account/flow are included and the other data are not included.

• If the data are detailed with different levels of detail, then, you can additionaly select one or more

of the following dimensions: Reporting Unit, Audit ID, Origin Unit. For example, the most detailed data for each account/flow/reporting unit are included and the other data are not included.

2010-12-0983

Page 84

Cube Deployments

Example:

By default, all the amounts below are included in the BW cube. For U1, the detailed and the non detailed data both appear: 50+20+30.

So that only the most detailed data appear for U1 (20+30), check the Include only most detailed data for account flow/member option: the most detailed data for each account/flow are included in the cube, the other amounts are ignored. However, since the data are detailed with different levels of detail, no data is included for U2.

AmountProductReporting UnitFlowAccount

50-U1F99Sales

20P1U1F99Sales

30P2U1F99Sales

25-U2F99Sales

AmountProductReporting UnitFlowAccount

-U1F99Sales

20P1U1F99Sales

30P2U1F99Sales

-U2F99Sales

So that data for U2 is also included in the cube, check also the Reporting Unit option. The most detailed amounts are included in the cube for each account/flow/reporting unit.

AmountProductReporting UnitFlowAccount

-U1F99Sales

20P1U1F99Sales

30P2U1F99Sales

25-U2F99Sales

4.3.9 Initialize a NetWeaver Business Warehouse Deployment

Once a cube has already been deployed, you can initialize the cube. The cube is completely re-created with new technical names. To do so, click Initialize.

2010-12-0984

Page 85

Cube Deployments

Note:

If an SAP NetWeaver Business Warehouse (SAP NetWeaver BW) cube has already been deployed from a cube designer view and BEx reports have been designed on top of this cube, these reports cannot be used again on top of a new SAP NetWeaver BW cube that will be initialized from the same view. This limitation does not exist for reports created with the EPM add-in for Microsoft Office.

4.3.10 Remove an SAP NetWeaver Business Warehouse Cube

You can remove a cube from cube designer.

In SAP NetWeaver Business Warehouse (SAP NetWeaver BW), all the cube elements are deleted.

4.3.10.1 Removing an SAP NetWeaver Business Warehouse Cube

In the Deployment tab, click Remove Cube. A confirmation message appears.

Click Yes.

4.3.11 Remove an SAP NetWeaver Business Warehouse InfoArea

You can remove an InfoArea from cube designer.

In this case, the InfoArea is deleted along with all its cubes.

4.3.11.1 Removing an InfoArea

In the Deployment tab, click Remove InfoArea. A confirmation message appears.

Click Yes.

2010-12-0985

Page 86

Cube Deployments

4.4 Deployment Copy

You can copy and paste a deployment in a view.

Once you have copied a deployment, you can rename it.

Related Topics

• Renaming a Deployment

4.4.1 Copying and Pasting a Deployment

In the tree structure part of the window, right-click on the deployment you want to copy and select

Copy.

Right-click on the Deployments node and select Paste.

4.5 Renaming a Deployment

In the tree structure part of the window, right-click on the deployment you want to rename and select Rename.

The name of the deployment appears highlighted.

Enter the new name.

4.6 Audit and Delete Deployments

You can now display the list of all the deployments performed in all cube designer solutions linked to the current SAP BusinessObjects Financial Consolidation data source. From this list, you can delete deployments' information from the SAP BusinessObjects Financial Consolidation database tables that are not used anymore. The following information is available:

• The name of the cube.

• The time at which the deployment was last saved (date and hour).

2010-12-0986

Page 87

Cube Deployments

4.6.1 Auditing and Deleting Deployments

Select File > Deployment Audit. The Deployment Audit dialog box appears.

To display all the list of deployments, click the Get Deployments button.

Select the checkboxes of the deployments you want to delete.

Click the Delete Selected Deployments button.

2010-12-0987

Page 88

Cube Deployments

2010-12-0988

Page 89

Star Schema Deployments

5.1 Introduction to Star Schemas

You can generate either an SQL or an Oracle star schema.

A star schema contains three types of tables:

• Fact tables. These are tables that contain data.

• Dimension tables. One table is created for each dimension.

• Characteristic tables. One table is created for each "standard" characteristic. Only characterictics

that have been selected in the view are taken into account.

However, characteristic tables are not created for characteristics that are linked to a dimension in the same reference table. For each of these characteristics, a column is created in the dimension table.

Tables can contain unicode characters. However, we recommend that you use ANSI characters and no accented characters for the table names.

Besides, a star schema:

• Does not support hierarchies.

• Does not support SAP BusinessObjects Financial Consolidation data security.

• Supports SAP BusinessObjects Financial Consolidation comments (as opposed to OLAP cubes).

5.2 Star Schema Deployment Creation

Creating a star schema deployment consists of the following main steps:

• Entering a name for the deployment.

• Selecting the server and specifying the server information. This is the server on which the star

schema will be generated.

The Microsoft Data Link Properties dialog box enables you to specify the required information. This dialog box contains four tabs: Provider, Connection, Advanced and All.

2010-12-0989

Page 90

Star Schema Deployments

The Provider tab enables you to specify if you want to generate an SQL or Oracle star schema.

The Connection, Advanced and All tabs are contextual and depend on the type of provider (SQL or Oracle) selected in the Provider tab.

5.2.1 Creating a Star Schema Deployment

In the tree structure pane of the main window, right-click on Deployments and select Add Deployment.

The New Deployment dialog box opens.

In the Server Type groupbox, select the Star Schema option. The Data Link Properties dialog box will appear, displaying the Connection tab.

In the Connection tab, specify the required information. For more information regarding SQL or Oracle providers, please refer to the paragraphs describing the tab.

You must ensure that the Allow saving password option is selected.

Click on Test Connection. A message appears, indicating whether the connection is valid or not. To find out more about this

button, please refer to the paragraphs above describing the tab.

If the connection is valid, click on OK. The Data Link Properties dialog box reappears.

Click on OK. The New deployment dialog box reappears. A default star schema deployment name is displayed

in the Deployment Name field and the server information is displayed in the Server Details groupbox.

Note:

If you want to modify server information, click on Change. The Data Link Properties dialog box will appear.

Enter the name you want to give the star schema deployment.

Click on OK. The deployment appears below Deployments in the tree structure pane. If you click on it, the

deployment will appear in the right pane of the window, displaying three tabs: General, Star Schema Options and Deployment. In the General tab, you can view the server connection information and modify it using the Change Connection button.

5.2.2 Provider Tab

This tab enables you to specify the OLE DB provider you want to use.

2010-12-0990

Page 91

Star Schema Deployments

This tab lists all OLE DB providers detected on your computer.

A provider is selected by default, depending on your SAP BusinessObjects Financial Consolidation database:

• If your SAP BusinessObjects Financial Consolidation database is SQL, then Microsoft OLE DB

Provider for SQL Server is selected by default.

• If your SAP BusinessObjects Financial Consolidation database is Oracle, then Microsoft OLE DB

Provider for Oracle is selected by default.

We highly recommend that you use the default provider.

When you click on Next, the Connection tab for the selected OLE DB provider will appear.

5.2.3 Connection Tab

This tab enables you to enter information specific to the provider selected in the Provider tab. The content of the tab depends on whether an SQL or Oracle provider was selected.

5.2.4 SQL

This Connection tab is provider-specific and displays only the connection properties required by the OLE DB provider for Microsoft SQL Server.

If you want to generate an SQL star schema, specify the following information in the Connection tab:

The SQL Server name. You can either select a server name from the drop-down menu, or type the path of the server hosting the database you want to access.

Use the Refresh button to refresh the drop-down menu.

The information to connect to the server specified above. You can either use your Windows NT authentication information or the server authentication information.

• Use Windows NT Integrated security. Select this option to specify that the provider will request

a secure (or trusted) connection to an SQL Server running on Microsoft Windows NT. When selected, SQL Server uses integrated login security to establish connections using this data source, regardless of the current login security mode at the server level. Any login ID or password entered will be ignored. The SQL Server system administrator must have associated your Microsoft Windows network ID with an SQL Server login ID.

• Use a specific user name and password. Select this option to enter a user name and password

to connect to the data source.

• User name. Enter the user ID used for authentication when you log on to the data source.

2010-12-0991

Page 92

Star Schema Deployments

• Password. Enter the password used for authentication when you log on to the data source.

• Blank password. This option enables the specified provider to return a blank password in the

connection string.

• Allow saving password. This option enables the password to be saved with the connection

string. This option must be selected.

The database. You can either select a database from the drop-down menu listing all of the databases stored on the server specified above, or type the name of the database you want to access.

• Test Connection. Click on this button to test your connection to the specified data source. If the

connection fails, ensure that the settings are correct. For example, you should recheck all spelling and case sensitivity.

5.2.5 Oracle

This Connection tab is provider-specific and displays only the connection properties required by the Microsoft OLE DB provider for Oracle.

If you want to generate an Oracle star schema, specify the following information in the Connection tab:

Server name. Enter the Oracle net service name, also known as the TNS alias.

The information to connect to the server specified above.

• User name. Enter the user ID used for authentication when you log on to the data source.

• Password. Enter the password used for authentication when you log on to the data source.

• Blank password. This option enables the specified provider to return a blank password in the

connection string.

• Allow saving password. This option enables the password to be saved with the connection

string. This option must be selected.

• Test Connection. Click on this button to test your connection to the specified data source. If the

connection fails, ensure that the settings are correct. For example, you should recheck all spelling and case sensitivity.

5.2.6 Advanced and All tabs

These two tabs display the information specified in the Provider and Connection tabs.

You should not use these tabs other than for viewing the specified properties.

2010-12-0992

Page 93

Star Schema Deployments

5.3 Prefix Name for Tables

You can enter a prefix that will be added to each table name.

Adding a prefix is strongly recommended to avoid overwriting tables if you create several star schemas within the same database.

The default prefix is the name of the deployment.

5.4 Several Fact Table Definition (Partitions)

When deploying a star schema, only one fact table is created by default. The fact table contains all of the data.

You can create several tables based on specific Data entry periods. These tables are known as "partitions". A partition corresponds to one table created for the data related to one or more Data entry periods. This means that one partition can contain one or more Data entry periods.

You can drag and drop Data entry periods into the right pane of the window.

Note:

You can drag and drop all Data entry periods except for one that must remain in the Default column. The table for this Data entry period is then considered the "default table".

You can decide how you want to name the fact tables you are creating. You can define:

• A base name. This is the main name common to all of the fact tables. Each new partition is assigned

the base name and incremented, e.g. "Partition2".

• A suffix to be added to all fact table names.

The fact tables will be named using the following syntax:

[Prefix (applied to all tables)]_[Partition name]_ [Suffix]

The default fact table will be named using the following syntax:

[Prefix (applied to all tables)]_Default_ [Suffix]

Note:

Fact table names are limited to 30 characters.

"co" (for "consolidation") or "pk" (for "package") are automatically added just before the suffix.

2010-12-0993

Page 94

Star Schema Deployments

5.4.1 Creating Partitions

In the Partition Base Name field, enter the name common to all of the partitions.

Drag and drop “Data entry periods” corresponding to the partitions you want to create from the Default column into the right pane.

One column is created for each partition and assigned the base name entered in the Partition Base Name field followed by an incremental number.

Note:

You can add one or more “Data entry periods” to one partition.

If you do not want a specific partition to be named using the base name, right-click on the partition header and select Rename Partition.

Enter the name you want in the field that appears and press the Enter key.

5.4.2 Removing partitions

To remove all of the partitions, click on Remove Fact Table Partitions.

To remove a specific partition, drag and drop it into the Default column.

5.5 Star Schema Issue Resolution

Before deploying a star schema, you need to resolve the issues that are listed in the Issues To Resolve tab. The tab only appears if there are issues and once you have resolved the issues, the tab no longer appears.

In the tab, you can double-click a row indicating an issue. The location where you must correct the issue is automatically displayed.

5.6 Star Schema Deployment

Deploying a star schema consists of creating the star schema structure and data by generating all required tables.

2010-12-0994

Page 95

Star Schema Deployments

Before deploying a star schema, the Deployment tab enables you to view all of the information that will be taken into account in the star schema tables. This tab displays:

• All of the dimensions defined in the view.

• All SAP BusinessObjects Financial Consolidation consolidations or packages selected (depending

on the data level of the view).

In the Actions column:

• If nothing is displayed for a specific dimension or member row, this means that the dimension or

member was excluded or had never been included in the view and therefore will not be exported.

• The following information may appear:

• Add: if the corresponding dimension or member was excluded in the last deployment but is now

being included.

• Update: if the corresponding dimension or member was included in the last deployment and is

again being included.

• Remove: if the corresponding dimension or member was included in the last deployment but is

now being excluded.

While deploying a star schema, you can monitor the process using the log displayed in the bottom pane of the window.

If this pane is not displayed, select View > Deployment Log.

You can perform the following actions in the log:

• Display or hide one or more types of information by clicking on the Errors, Warnings and/or

Messages buttons.

• Errors: Errors cause the deployment to fail.

• Warnings: Warnings are displayed but do not prevent you from deploying the star schema

successfully.

• Messages: Messages indicate each step of the deployment.

• Delete the log by clicking on Clear List.

• Export the log in .csv format by clicking on Export List.

Note:

Before deploying a star schema, you need to resolve existing issues. If some issues remain unresolved, the Issues to Resolve tab will remain and the Deploy button will not be accessible.

You can also deploy a star schema without using cube designer interface.

Related Topics

• Deploy, Process, Re-Process and Update Actions

2010-12-0995

Page 96

Star Schema Deployments

5.6.1 Deploying a Star Schema

• In the Deployment tab, click on Deploy.

Note:

The date of the deployment will appear in the Last Deployed On field of the General tab.

5.7 Using iAnalysis Reports

If you previously used iAnalysis reports, you can still continue to do so with cube designer.

You should ensure that the star schema tables have the same name and structure as the iAnalysis star schema tables using the “iAnalysisStarSchemaTableNames” parameter.

The “iAnalysisStarSchemaTableNames” parameter is specified in the Cartesis.InformationDelivery.Workbench.exe.config file stored in the cube designer installation folder. Its default value is "iAnalysisStarSchemaTableNames" value="false". To be able to use your iAnalysis reports, you should replace "false" with "true".

Note:

If you are a former iAnalysis user, please also refer to the Aggregating members when excluding a dimension section.

Related Topics

• Member Aggregation when Excluding a Dimension

5.8 Member Aggregation when Excluding a Dimension

If you exclude a specific dimension in a view, the dimension will not be exported to star schema tables. This may lead to one member being displayed several times with detailed amounts. If you want the amounts to be aggregated for each member, you should specify the "StarSchemaAggregation" parameter.

The "StarSchemaAggregation" parameter is specified in the Cartesis.InformationDelivery.Workbench.exe.config file stored in the cube designer installation folder. Its default value is "StarSchemaAggregation" value="false".

2010-12-0996

Page 97

Star Schema Deployments

Note:

For former iAnalysis users, it is recommended that you leave the value of "StarSchemaAggregation" as "false" if you set the "iAnalysisStarSchemaTableNames" value to "true" (see paragraph above).

The following example illustrates this:

Assuming that you have a SAP BusinessObjects Financial Consolidation database with two dimensions and a fact table:

UnitsAccounts

U1A1

U2A2

U3A3

AmountsUnitsAccounts

10U1A1

5U1A2

20U1A3

6U2A1

7U2A2

You generate a star schema from the database above and also exclude the Account dimension. Depending on the value of the "StarSchemaAggregation" parameter, there can be 2 outcomes:

• If the "StarSchemaAggregation" parameter is set to "false", the star schema fact table will look like

this:

AmountsUnits

10U1

5U1

20U1

6U2

7U2

• If the "StarSchemaAggregation" parameter is set to "true", the star schema fact table will look like

this:

2010-12-0997

Page 98

Star Schema Deployments

Rows with identical dimension definitions will be aggregated.

Note:

If rows are aggregated, then any existing SAP BusinessObjects Financial Consolidation cell comments will disappear, as they cannot be aggregated.

AmountsUnits

35U1

13U2

2010-12-0998

Page 99

Batches

6.1 Introduction to Batches

Three exe files enable you to perform the following actions without using the cube designer interface:

• Deploy an SSAS cube, an SAP NetWeaver Business Warehouse (SAP NetWeaver BW) cube or a

star schema; process or re-process parts of an SSAS cube or an SAP NetWeaver BW cube; update an SSAS cube (AnalyticsBatch).

• Export solutions (Export).

• Import solutions (Import).

The three files (AnalyticsBatch, Export and Import) are installed along with cube designer in the installation directory. Therefore, the command lines must be entered from the installation directory.

Caution:

You must not move the files from the installation directory.

In the paragraphs below, you will be provided with the correct syntax for entering the MS-DOS command lines.

Note:

The command lines contain attributes in order that this command line was more robust and besides, it allows to type the different parameters in any wished order.

6.2 Deploy, Process, Re-Process and Update Actions

The AnalyticsBatch.exe file enables you to:

• Deploy or process an SSAS cube or an SAP NetWeaver Business Warehouse (SAP NetWeaver

BW) cube.

• Re-process speficic parts of an SSAS cube or an SAP NetWeaver Business Warehouse (SAP

NetWeaver BW) cube.

• Update a cube (for SSAS only).

• Deploy a star schema.

2010-12-0999

Page 100

Batches

You must modify the default Deployer URL in the AnalyticsBatch.config file just like you must do it in the Cartesis.InformationDelivery.Workbench.exe.config file, which is located in the cube designer installation directory. To find out more about how to proceed, please refer to the SAP BusinessObjects Financial Consolidation Administration guide.

To run the AnalyticsBatch in command line mode, use the following syntax:

ANALYTICSBATCH "/DS:AnalyticsConnectionName"

"/S: solution_name" "/V:view_name" "/D:deployment_name" ["/U:user_login" "/P user_password" "/A authentication_type "] "/T:task_type"

where:

• /DS : Name of the connection

• /S : Name of the solution

• /V: Name of the view

• /D: Name of the deployment

• /U, /P and /A : SAP BusinessObjects Financial Consolidation user name, password and authentication

type. They are also the one used to connect to cube designer.

• /T:task_type is d for deployment or p for processing or r for reprocessing selected or f for updating

cube calculations/named sets (processing apply to both cube types only and updating apply to SSAS cube only).

Example: You can enter the following in the MS-DOS window

ANALYTICSBATCH "/DS:Finance" "/S:Solution1" "/V:View1"

"/D:Deployment1" "/U:ADMIN" "/P:123456" "/A:Enterprise" "/T:d"

Example: Re-process parts of a cube

You can use /T:R to re-process speficic parts of the cube. You must enter the cube parts (using their Deployment Name) between two ' characters and separate the parts with the - character.

/T:R:'A - 2001.12 - VALUECORP - IFRS - EUR', 'A - 2001.12 - VALUECORP - IFRS - USD'

Related Topics

• AnalyticsBatch Messages

• Deployer Messages

• Help

6.2.1 AnalyticsBatch Messages

2010-12-09100

Business objects CUBEDESIGNER 10.0 2010-12-09, FINANCIAL CONSOLIDATION 2010-12-09 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Getting Started

Solutions

Select File > Delete Solutions. The Delete Solutions dialog box appears.

Views

• View Creation

• Multi-measures Behavior

If you have chosen to work with consolidated data, the Scopes tab appears.

• The merge has already been defined and appears in the Merged Dimensions node.

• SAP BusinessObjects Financial Consolidation Filtering

• Activating Automatic Time Aggregation

Check the Hide Excluded Dimensions box. In the tree structure part of the window, the excluded dimensions no longer appear.

Cube Deployments

• SSAS Cube Deployments

• Automatic Universe Creation

• Query Poll Interval

So that the cube is synchronized with the data every two hours even if no modifications have been made, specify the following in the Rebuild interval area: 2 Hours.

• Using your own MDX Scripts in a Deployment

• Renaming a Deployment

Star Schema Deployments

• Member Aggregation when Excluding a Dimension

Batches

• AnalyticsBatch Messages