sap businessobjects planning and consolidation 7

Operations GuideSAP BusinessObjects Planning and Consolidation 7.5version for SAP NetWeaver

Target Audience ■ Technical Consultants ■ System Administrators ■ Solution Consultants ■ Business Process Owner ■ Support Specialist

PUBLICDocument version: 3.3 – 2010-09-17

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. 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.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

2/80 PUBLIC 2010-09-17

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2010-09-17 PUBLIC 3/80

http://www.sap.com

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0


Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this operations

guide. You can find the latest version at the following location: http://service.sap.com/

instguidesEPM-BPC 7.5, version for SAP NetWeaver .

The following table provides an overview of the most important document changes.

Version Date Description

1.0 2009-12-15 First version

1.1 2010-03-10 Added a section in the “Troubleshooting” chapter about troubleshooting the transport process.

1.2 2010-04-29 Revised the section “Logging and Tracing Configuration” in the “Troubleshooting” chapter to reflect the new logging and tracing strategy.

2.0 2010-06-15 This is the update for SP03. For detailed information, refer to the appropriate SAP central note.

2.1 2010-07-12 Reworded section 5.1.4.7 Journals to clarify that journals are not transported and may not be available after transport.

3.0 2010-08-20 This is the update for SP04. For detailed information, refer to the appropriate SAP central note.

3.1 2010-08-20 Added information to “Chapter 4 – Management of Planning and Consolidation” about backing up and restoring application sets.

3.2 2010-08-24 Updated the “Client and Server Log Files” section to correct the location for the client log files.

3.3 2010-01-17 Updated the “Configure Central Management System” section to amend the CMS configuration details to reflect the parameters available on the delivered system.

4/80 PUBLIC 2010-09-17

http://service.sap.com/instguidesEPM-BPC

http://service.sap.com/instguidesEPM-BPC

Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3 Monitoring of Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 Log and Trace Files List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.2 Client and Server Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.3 Logging of Exceptions in the SLG1 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.4 Trace File for Debugging Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.5 Data Manager Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.6 Central Computing Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.6.1 Setting up a Minimal-Access User to Configure SMD . . . . . . . . . . . . . . . . . . . 20

3.6.2 Monitoring with Central Computing Management System . . . . . . . . . . . . . . 20

Chapter 4 Management of Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . 23

4.1 Managing Your Planning and Consolidation Servers . . . . . . . . . . . . . . . . . . . . 23

4.1.1 Viewing Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.1.2 Client Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.1.3 Server Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.1.4 Configuring the SLD Data Supplier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.1.5 Domain User Group Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4.1.6 Setting Up Debug Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.1.7 Server Manager Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.2 Configure Central Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.3 Migrating Users to Central Management System . . . . . . . . . . . . . . . . . . . . . . . 32

4.4 Starting and Stopping .NET Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.5 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4.5.1 Backup Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4.5.2 Backing Up and Restoring an Application Set . . . . . . . . . . . . . . . . . . . . . . . . . 34

2010-09-17 PUBLIC 5/80

4.5.2.1 Backing Up an Application Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.5.2.2 Restoring an Application Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.6 Microsoft Message Queue (MSMQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.7 Configuring IIS Web Gardens to Run Multiple Processes . . . . . . . . . . . . . . . . . 38

4.8 Best Practices for Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.8.1 Processing Tiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.8.2 Cube Fact Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.8.3 Cube Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.8.4 Cube Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.8.5 Writeback Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.8.6 SQE Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4.9 Set Up of BPF E-mail Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 5 Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.1 Transport Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.1.1 Transport Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

5.1.2 Transport Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.1.2.1 Transporting Application Sets into Production . . . . . . . . . . . . . . . . . . . . . . . . 45

5.1.2.2 Transporting Process Chains into Production . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.1.3 Transport Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5.1.4 Transport Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5.1.4.1 AppSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5.1.4.2 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5.1.4.3 Script Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.1.4.4 Table Driven Logic (Business Rules) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.1.4.5 Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.1.4.6 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.1.4.7 Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.1.4.8 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.1.4.9 Work Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1.4.10 Live Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1.4.11 Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1.4.12 Business Process Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1.4.13 Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.1.4.14 Data Manager Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6/80 PUBLIC 2010-09-17

5.1.4.15 Data Manager Transformation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.1.4.16 Data Manager Conversion Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.1.4.17 Data Manager Macro Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.1.4.18 New Files and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.1.4.19 Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.1.4.20 Other Files and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.1.4.21 Web Admin Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.1.4.22 Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.1.4.23 Dimension Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.1.4.24 Validation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.1.4.25 Data for ApShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.1.5 Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.2 Product Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6.1 Troubleshooting in Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . 61

6.2 Troubleshooting on a .NET Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6.3 Analyzing Problems Using Solution Manager Diagnostics . . . . . . . . . . . . . . . . 61

6.4 Installing Appsight Black Box Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

6.5 Reporting and Analyzing System Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

6.6 Generating and Analyzing Trace Files Using E2E Trace . . . . . . . . . . . . . . . . . . 63

6.7 Logging and Tracing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

6.7.1 Logging and Tracing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

6.7.2 Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

6.7.3 .NET Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6.8 Troubleshooting Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 7 Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.1 Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.2 CA Wily Introscope Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.3 Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

2010-09-17 PUBLIC 7/80

This page is left blank for documents that are printed on both sides.

1 Getting Started

CAUTION

This guide does not replace the daily operations handbook that we recommend customers create

for their specific production operations.

About this Guide

Designing, implementing, and running Planning and Consolidation at peak performance 24 hours a

day has never been more vital for your business success than now.

This guide provides a starting point for managing Planning and Consolidation solutions and

maintaining and running them optimally. It contains specific information for various tasks and lists

the tools that you can use to implement them. This guide also provides references to the documentation

required for these tasks, so you will sometimes also need other guides such as the Master Guide and

SAP Library.

Naming Conventions

In this document, the following naming conventions apply:

Variable Description

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

<drive> The drive where Planning and Consolidation is installed.The default for this is C:\PC_NW.

1 Getting Started

2010-09-17 PUBLIC 9/80

2 Important SAP Notes

CAUTION

Check regularly to see which SAP Notes are available for this Operations Guide.

Important SAP Notes

SAP Note Number Title Comments

1410517 SAP Planning and Consolidation 7.5 SP00, version for the NetWeaver platform

This is the Central Note for Planning and Consolidation 7.5.


This is the Central Note for Planning and Consolidation 7.5, Service Pack 01.





2 Important SAP Notes

2010-09-17 PUBLIC 11/80

3 Monitoring of Planning and Consolidation

3.1 Log and Trace Files List

This release of Planning and Consolidation provides the following set of logs on its .NET servers:

■ Trace files

BPCTRACE.x.LOG located in <drive>/Logging/Trace, where x is a number between 0 and 9, such

as BPCTRACE.5.LOG.

The default severity of traces is ERROR.

■ Log files

BPCLOG.x.LOG located in <drive>/Logging/Log, where x is a number between 0 and 9, such as

BPCLOG.5.LOG.

The default severity of logs is INFO.

NOTE

The above storage locations and the total number of log and trace files possible are the default

values. These can be changed; for more information, see .NET Server Configuration [page 70].

The .NET component writes to the logging category /Applications/<component_name>.

For information about possible severity levels for traces and logs, see Client and Server Log Files [page 13].

3.2 Client and Server Log Files

Every day the system creates two log files: one that contains information about server operations, and

one that contains information about client operations.

The following table describes the location and format of log files in log<date>.txt format:

Log File Source Location Format

.Net server components (Web server and Application server)

<Drive>\Logging on the .NET server

log<mm-dd-yyyy>.txt

EXAMPLE

log06-26-2009.txt

Client components Client installation directory log<mm-dd-yyyy>.txt


3.1 Log and Trace Files List

2010-09-17 PUBLIC 13/80

EXAMPLE

log06-26-2009.txt

You can use various levels to restrict the information that is recorded in logs. To set a level, you set a

parameter at the application set level by choosing Web Admin Tasks Application Set Parameters in the

Administration interface.

The application set parameter is LOGLEVEL, and the options are:

■ DONOTHING — This level records no issues.

■ INFO — This level records fatal problems, errors, warnings, and other system info.

■ WARNING — This level records fatal problems, errors, and warnings.

■ ERROR — This level records fatal problems and errors.

■ FATAL — This level records fatal problems.

The valid values for Trace Severity are:

■ DEBUG — This level records debug information, system information, warnings, and errors.

■ INFO — This level records errors, warnings, and other system info.

■ WARNING — This level records errors and warnings.

■ ERROR — This level records errors. (This is the default value.)

Log Files in SAP Logging Format 2.0

The following table describes the location and format of log files in SAP Logging Format 2.0:

Parser State Pos Field Name Example Value Optional Default Description

1 1 Version 2.0 No 2.0 Logging API version. This value is used for defining parsing procedure version.

2 2 DateTime 2008 01 08 14:30:36:084 No YYYY MM DD HH:MM:SS:ms of Date & time

3 3 Time Zone +6:30 No Time Zone in format +/-N:NN (where N is Number)

4 4 Severity INFO No DEBUGINFOWARNINGERROR

Severity of the record



14/80 PUBLIC 2010-09-17


5 5 SourceName com.sap.mycomponent or /System/Database

No Location or Category name

If Log Record was written using Category then value is equal to that Category name, and if Location was in use, value is equal to the Location name.

6 6 MsgCode web:0a0067 No Unique message id used in MessageID concept

7 7 CSN Component BC-JAS-ADM No Empty string (“”)

Component in the CSN system to which this message refers

8 8 DC Component tc/lm/webadmin/performance/viewer/wd

No Empty string (“”)

Development Component

9 9 Development Component

000FFE93A54 F0027000006 83000018B4 01228AEE

No GUID value Unique LogRecord ID

10 10 Correlation ID 000FFE93 No Correlation ID

Implicit properties from the J2EE engine

11 11 Application MyApplication No Empty string (“”)


12 12 Location com.sap.mycomponent No Location name

Class or package name where LogRecord was created

13 13 User MyUser No Empty string (“”)


14 14 Session MySession No Empty string (“”)


15 15 Transaction MyTransaction No Empty string (“”)




2010-09-17 PUBLIC 15/80


16 16 DSRRootContextID 38fe6ce0639411 dc96dd000ffe93 a2aa



17 17 DSRTransaction 38fe6ce0639411 dc96dd000ffe93 a2ab



18 18 DSRConnection 38fe6ce1389411 dc96dd000ffe93 a2cc



19 19 DSRCounter 20 No Empty string (“”)


20 20 ThreadName System [28] No Main Thread name

21 21 MsgType JAVA No Plain LogRecord Message type:PLAIN – message with-out argumentsJAVA – message with arguments

22 22 ResourceBundle MyResourceBundle No Empty string (“”)

ResourceBundle name

23 23 MsgText Server {0} will be down in {1} minutes!


Message

24 24 MSGArgsNo 2 Yes Number of arguments in message (for example, 2)

25 24+1 MSGArg_1 MyServer Yes First message argument

26 24+2 MSGArg_2 15 Yes Second message argument

27 24+n MSGArg_n <= MSGArgsNo

... Yes Next message argument

Example

Example log record ordered content:

Field Name Value

Version 2.0

DateTime 2008 01 08 14:30:36:084



16/80 PUBLIC 2010-09-17

Field Name Value

TimeZone +6:30

Severity INFO

SourceName com.sap.mycomponent

MsgCode web:0a0067

CSNComponent BC-JAS-ADM

DCComponent tc/lm/webadmin/performance/viewer/wd

GUID 000FFE93A54F002700000683000018B401228AEE

CorrelationID 000FFE93

Application MyApplication

Location com.sap.mycomponent

User MyUser

Session MySession

Transaction MyTransaction

DSRRootContextID 38fe6ce0639411dc96dd000ffe93a2aa

DSRTransaction 38fe6ce0639411dc96dd000ffe93b1cc

DSRConnection 38fe6ce0639411dc96dd000ffe93d345

DSRCounter 20

ThreadName System [28]

MsgType JAVA

ResourceBundle MyResourceBundle

MsgText Server {0} will be down in {1} minutes!

MSGArgsNo 2

MSGArg_1 MyServer

MSGArg_2 15

Log record example

#2.0#2008 01 08 14:30:36:084#+6:30#INFO#com.sap.mycomponent#

web:0a0067#BC-JAS-ADM#tc/lm/webadmin/performance/viewer/

wd#000FFE93A54F002700000683000018B401228AEE#000FFE

93#MyApplication#com.sap.mycomponent#MyUser#MySession#MyTransaction#38fe6ce0639411dc9

6dd000ffe93a2aa#38fe6ce063

9411dc96dd000ffe93b1cc#38fe6ce0639411dc96dd000ffe93d345#20#System [28]

#JAVA#MyResourceBundle#

Server {0} will be down in {1} minutes!#2#MyServer#15#



2010-09-17 PUBLIC 17/80

NOTE

■ All expected fields are shown on a new line.

■ Empty string values display as “”.

■ Empty numeric values display as -1.

Example

2.0

000FFE93A54F002700000683000018B401228AEE

2008 01 08 14:30:36:084

com.sap.mycomponent

MyApplication

com.sap.mycomponent

MyUser

MySession

MyTransaction

38fe6ce0639411dc96dd000ffe93b1cc

System [28]

INFO

JAVA

web:0a0067

MyResourceBundle

Server MyServer will be down in 15 minutes!

+6:30

BC-JAS-ADM

tc/lm/webadmin/performance/viewer/wd

000FFE93

38fe6ce0639411dc96dd000ffe93a2aa

38fe6ce0639411dc96dd000ffe93d345

20

3.3 Logging of Exceptions in the SLG1 System

When an exception occurs, relevant information is logged in the SLG1 system. This allows for improved

tracing and diagnosis of any exceptions that occur.

The detailed information is written in the log item and saved in the database. In the log, the object is

identified as UJ and the subobject is identified as UJK.


3.3 Logging of Exceptions in the SLG1 System

18/80 PUBLIC 2010-09-17

EXAMPLE

The following script refers to an invalid member, A1000:

*XDIM_MEMBERSET ENTITY=A1000

*WHEN TIME

*IS 2006.JAN

*REC(FACTOR=1.2)

*ENDWHEN

This generates an exception and produces the following message in the log:

Member "A1000" not exist.

3.4 Trace File for Debugging Logic

You can turn on tracing for script logic and business rules when you need to troubleshoot a particular

script or rule. We recommend that this is only used by experienced Planning and Consolidation

consultants and support. We also recommend that these files are removed periodically since they take

up a considerable amount of space.

The activity is recorded in a file called debuglogic.log and stored in <drive>\webfolders\<Appset>

\<application>\privatepublication\<username>\<date>.

3.5 Data Manager Log Files

Whenever you use a Data Manager package to move Planning and Consolidation data, the system

creates a log file. This file can be useful in troubleshooting the execution of packages. We recommend

that these files are removed once the packages have completed since they take up a considerable amount

of space.

In the NetWeaver version of Planning and Consolidation, these logs are stored in <Drive>\WEBFOLDERS

\%APPSET%\%APP%\PRIVATEPUBLICATIONS\<username>\tempfiles.

In the Microsoft version of Planning and Consolidation, these logs are stored in <Drive>\webfolders

\<Appset>\<application>\privatepublication\<username>\tempfiles.

The name of the log file contains the following details:

■ The name of the package

■ A timestamp

■ The extension .LOG

EXAMPLE

Validatetransformation20090915211503.log


3.4 Trace File for Debugging Logic

2010-09-17 PUBLIC 19/80

NOTE

In the NetWeaver version of Planning and Consolidation, passwords are masked when contained

in a log file. To be masked, however, the parameter name for passing the password must include

the substring ‘password’.

3.6 Central Computing Management System

You can set up Central Computing Management System (CCMS) within SAP Solution Manager for

monitoring your SAP Planning and Consolidation system. Before you can use CCMS, you need to

configure a special user account to access SAP Solution Manager and Diagnostics.

3.6.1 Setting up a Minimal-Access User to Configure SMD

The SAP Solution Manager and Diagnostic (SMD) tool can be used to provide Web services, such as

monitoring with the Central Computing Management System (CCMS).

The user, who performs these monitoring and diagnostic services, does not need to be able to manipulate

the Planning and Consolidation data. Therefore, it may be advisable to create a user with minimal access

rights and configure SMD to access Planning and Consolidation with this user. The following procedure

describes the creation and configuration of such a user.

Procedure1. Log on to the Apshell application set through the Admin Console.

2. Choose Security Users and then select Add new user from the Session Information action pane

3. In the Add New Users wizard, enter a suitable user name or use the Search function to find an available

user name.

4. Choose Next at all remaining steps of the wizard without entering any user details or assignments

data.

5. Check that the user has no teams or profiles assigned and click Apply.

6. Configure the SMD connection to Planning and Consolidation to use this user.

For information about setting up SMD, see Connecting to Solution Manager Diagnostics in the Planning and

Consolidation Installation Guide.

3.6.2 Monitoring with Central Computing Management System

You can set up Central Computing Management System (CCMS) within SAP Solution Manager for

monitoring .NET application servers within your SAP Planning and Consolidation system. You can set



20/80 PUBLIC 2010-09-17

up log file and process monitoring to monitor managed hosts, which are the SAP Planning and

Consolidation application servers. SAP Planning and Consolidation Monitoring in the central

monitoring system is based on SAP CCMS agent functionality, which you must install on the monitored

hosts. There is no CCMS monitoring of ABAP servers.

For information about setting up CCMS for use with Planning and Consolidation on the NetWeaver

platform, see SAP Note 1379214. For information about setting up CCMS for use with Planning and

Consolidation on the Microsoft platform, see SAP Note 1379213.

After setting up and configuring monitoring for SAP Planning and Consolidation, log on to SAP

Solution Manager, then access CCMS. In the SAP Menu, select Tools CCMS Control/Monitoring

CCMS Monitor Sets (transaction code RZ20) .

The following monitor sets are available in CCMS within SAP Solution Manager for Planning and

Consolidation:

Availability Monitoring

A simple Generic Request and Message Generator (GRMG) scenario for SAP Planning and

Consolidation is available. This checks the availability of the SAP Planning and Consolidation

application server, and presents the status of its current availability.

Error Monitoring

The log file for SAP Planning and Consolidation is monitored for error patterns. The monitor present

its status and alerts according to the presence of error messages in the SAP Planning and Consolidation

log, which is located in <Drive>\logging\log. If errors occur in this log, you can display them in

transaction CCMS by selecting Open Alerts.

Operating System Monitoring

The servers hosting the SAP Planning and Consolidation application are monitored for resource

consumption. Operating system metrics such as overall CPU and memory consumption are reported.

In addition, the following operating system processes are monitored:

■ For the NetWeaver version of Planning and Consolidation:

● w3wp.exe (Microsoft Internet Information Services application pool process)

● mqsvc.exe (Microsoft Message Queue Server process)

● dllhost.exe (DLL application process)

■ For the Microsoft version of Planning and Consolidation:

● w3wp.exe (Microsoft Internet Information Services application pool process)

● dllhost.exe (DLL application process)

● OSoftSendGovernor.exe (SAP Planning and Consolidation Send Governor process)

● OSoftInsightSchedulerWindowsService.exe (SAP Planning and Consolidation Insight process)

You can customize the thresholds for alert triggering to suit your business needs.



2010-09-17 PUBLIC 21/80



In the Microsoft version of the system, you can access technical configuration details using WebService

at http://server_name:port/osoft/app/SMDWebService/BPCSMDService.asmx.



22/80 PUBLIC 2010-09-17

4 Management of Planning and Consolidation

4.1 Managing Your Planning and Consolidation Servers

You use Server Manager to maintain a Planning and Consolidation server. The Server Manager is

accessible on the .NET Application server.

The following features are available:

■ You can view information about the server. See Viewing Server Information [page 23].

■ You can set client installation options. See Client Options [page 25].

■ You can change the options defined during the server installation. See Server Options [page 26].

■ You can define user groups to limit server access to domains or subsets of domains. See Domain User

Group Setup [page 28].

■ You can change the credentials for your component services. See Changing the Credentials for Component

Services [external document].

■ You can change the Server Manager language by selecting Options Language <Language> .

■ You can set up a debug user for use by SAP support staff. See Setting Up Debug Users [page 29]

For information on the tasks that system administrators and non-system administrators can perform

in Server Manager, see Server Manager Security [page 29].

4.1.1 Viewing Server Information

You can view system information using the Server Manager.

Features

The System Information window shows information about the server, including the Operating System

version and available memory.

You can access the System Information window by doing the following: Start Server Manager by selecting

(All) Programs SAP Server Manager from the Windows Start menu on your .NET application server.

You can click the Refresh button to refresh the information on the screen.

The configuration XML files are available on a local file system. Configuration files include

web.config.xml and machine.config.xml.



2010-09-17 PUBLIC 23/80

Planning and Consolidation provides seven remote function calls for Solution Manager to monitor

the configuration data of the system. The following table provides an overview of the mapping

relationship of the DDIC tables (available by transaction SE16) and the remote function calls for the

ABAP server.

DDIC Table Name Remote Function CallConfiguration data included Table Fields

UJA_SVR_DEFAULT UJ0_API_BPC_CONFIG_03 Planning and Consolidation system administrators

MANDT — SAP GUI Logon Client NumberIS_CMS_DONE — Specifies whether the system is running in CMS modeVALUE — The value of the field

UJA_DOMAIN UJ0_API_BPC_CONFIG_05 Supported domain

MANDT — SAP GUI Logon Client NumberGROUP_NAME — The logic group of the system userDOMAIN_TYPE — Specifies whether the system is running in domain or work group modeDOMAIN_NAME — Name of the domainREAD_ONLY — Indicates whether the value can be changed

UJA3_SFT_VERSION UJ0_API_BPC_CONFIG_07 The prerequisite ABAP software components for the system

COMPONENT — The components required by the systemSAPRELEASE — Component release versionVERSION — Component versionPATCH — Component patch versionDESC_TEXT — Component description

UJA3_CLT_OPT UJ0_API_BPC_CONFIG_08 Settings for the Client options in Server Manager

MANDT — SAP GUI Logon Client NumberFIELD — Can be customized. Currently stores the client options of the systemVALUE — The value of the field

UJQ_PARAM UJ0_API_BPC_CONFIG_11 Parameters that control the behavior of application queries

MANDT — SAP GUI Logon Client NumberAPPSET ID — Application set IDAPPLICATION ID — Application IDPARAM — The related parameter name of the applicationVALUE — The value of the parameter

UJR_PARAM UJ0_API_BPC_CONFIG_12 Parameters that control

APPSET ID — Application set IDAPPLICATION ID — Application ID



24/80 PUBLIC 2010-09-17

DDIC Table Name Remote Function CallConfiguration data included Table Fieldslocking behavior when writing data

PARAM — The related parameter name of the applicationVALUE — The value of the parameter

UJU_AUDSTING UJ0_API_BPC_CONFIG_13 Indicate audit settings for various system components

MANDT — SAP GUI Logon Client NumberAPPSET_ID — Application set IDADMIN_ON — Indicates whether auditing is turned on for the Administration moduleUSER_ON — Indicate whether auditing is turned on for the User moduleBPF_ON — Indicate whether auditing is turned on for the Business Process Flows moduleBIZRULE_ON — Indicates whether auditing is turned on for business rules functionality

More InformationMonitoring with the Management Console [external document]

4.1.2 Client Options

This function allows you to set or change options related to Planning and Consolidation clients.

FeaturesYou can access the Client Options screen from Server Manager by selecting Options Client Options.

You can set the following options:

■ Sox Compliance

You can enable the server to be Sarbanes-Oxley compliant if you want all clients that access the

server to challenge users for a user name and password.

■ Check Prerequisite Software

If you want to install a different version of a required software component than is installed during

an auto update, you can provide a different version number and file name for the desired software

program. When you change the version or file name, it impacts all subsequent client installations

and client diagnostics.

NOTE

The Microsoft XML Version is here for historical reasons. We recommend that you do not change

this value.



2010-09-17 PUBLIC 25/80

4.1.3 Server Options

This function allows you to set or change options related to Planning and Consolidation servers. The

options are originally set during the server installation.

Features

You can access the Server Options screen from Server Manager by selecting Options Server Options.

The following table describes the available options:

Server Option Value Description

Application server name The name of the application server.

- External server name TCP/IP address for accessing the server from outside a firewall.

- Virtual server name The server name for load balancing if it is installed.

- Web site The IIS web site name, if it differs from the default web site.

- HTTP compression The default value is No. (Yes provides better performance in some situations.)

- Protocol The available values are http or https. The default value is http.

- Port number The port number to which the application server connects. 80 is the default for http, 443 is the default for https.

- Authentication type Active Directory.

Scheduler Server Name The name of the server used for scheduling, usually the application server, for example, GMPV50072862B. If you have multiple application servers, select the appropriate one.

Web Server name The name of the web server, for example, GMPV50072862B

- External server name TCP/IP address for accessing the server from outside a firewall.

- Virtual server name The server name for load balancing, if it is installed.

- Website The IIS web site name, if it differs from the default web site.

- HTTP compression The default value is No. (Yes provides better performance in some situations.)

- Protocol The available values are http or https. The default value is http.

- Port number The port number to which the Reporting Services server connects. 80 is the default for http; 443 is the default for https.

- Authentication type Active Directory.

4.1.4 Configuring the SLD Data Supplier

The System Landscape Directory (SLD) Data Supplier is the central directory of all of your system

landscape information. It contains a repository of all SAP software and a representation of the technical

systems, that is, the hosts on which software is installed as well as the software products and components,

versions, support packages and patches that are currently installed. The software components of a



26/80 PUBLIC 2010-09-17

product version are installed on hosts and form systems that are visible to the administrator. An

administrator must have knowledge about all the systems that are present in the landscape and about

the versions, support packages, and patches of the software components that are installed on these

systems. This kind of information is stored in the SLD and is called the Landscape Description (LD).

The SLD is also a repository of software components that can theoretically be installed in the landscape.

This kind of information is stored in the SLD as a Component Repository (CR).

SLD data suppliers automatically register the systems on the SLD server and keep the system

information up-to-date. They collect and send data about the systems to the SLD. For every newly

discovered system or component, the SLD creates an association to the corresponding entry in the

Component Repository. Thus, the SLD provides reliable and up-to-date system landscape information.

Prerequisites

To have the SLD Data Supplier for Planning and Consolidation work with the SLD server, the SLD

server needs to be on one of the following minimum releases of SAP Netweaver Application Server

Java:

■ 7.00 SP021

■ 7.01 SP005

■ 7.02 SP002

■ 7.10 SP009

■ 7.11 SP004

Features

You maintain the SLD Agent from Server Manager by selecting Server Configure SLD .:

■ Hostname

The host on which the SLD server is deployed and running

■ Port

The HTTP or HTTPS port at which the SLD server is listening

■ User name

The user name associated with the SLD credentials

■ Password

The user password associated with the SLD credentials

■ Use HTTPS

Indicates whether the data is transferred via secure connection or not

■ SLD Upload Frequency

The number of times per that the Planning and Consolidation system transfers currently active

data to the SLD server



2010-09-17 PUBLIC 27/80

Choose Save to save the SLD Agent connection setting. Choose Upload to upload an SLD Payload file to

the SLD server.

4.1.5 Domain User Group Setup

Rather than allowing all users within Active Directory (AD) to access Planning and Consolidation, you

can limit the pool of users by adding them to a particular domain and then giving access to only those

users. This is important because if you try to add a user from the entire AD, the system may time out

while searching.

Features

You can define user groups from the Server Manager by selecting Options Define system user groups.

You use the following features for defining a user group:

■ Choosing user group names

The default group name is Domain users if a domain user installs the Planning and Consolidation

server. The default group name is Local users if a local user installs the Planning and Consolidation

server.

The group name is displayed in the Add Users assistant in the Admin Console.

You can modify the settings for an existing group by selecting the name of the group from the list.

■ Defining Filters

You use filters to define user groups. The following table includes examples of filters you can define:

Scenario Example Description

Single organizational unit (OU)

OU=Marketing Finds users of the Marketing OU.

Multiple OUs OU=Sales;OU=Marketing Finds users of the Sales and Marketing organizational units.

Multiple OUs from a single container

OU=Sales;OU=Marketing;CN=Users Finds users of the Sales and Marketing organizational units and the Users container.

A group (or user) in an OU

CN=DM,OU=Sales Finds users of the DM group in the Sales organizational unit.

Multiple groups (or users) in an OU (when

CN=DM,OU=Sales;CN=DM,OU=Sales2 Finds the users of the DM group in the Sales2 organizational unit and the users in the DM group



28/80 PUBLIC 2010-09-17

Scenario Example Descriptionmultiple groups are in a single or different groups)

in the Sales organizational unit.

Mixed condition CN=DM,OU=Sales;CN=FR,OU=Sales2; CN=HR,CN=Users

Finds users of the DM group in the Sales organizational unit, users of FR group in Sales2 organizational unit, and users of HR group in the Users container.

4.1.6 Setting Up Debug Users

Since the SAP ABAP code is interpreted (not compiled), you can debug all internal Planning and

Consolidation logic directly on your system.

Using the Debug User Setup screen, you can define which users’ sessions need to be debugged. You enter

the Planning and Consolidation user name, and then map this to an ABAP user ID and password (note

that the ABAP User ID is considered the Debug User ID).

When a user logs on to Planning and Consolidation, the system checks the user ID, and if a debug user

is specified for them, the connection to the back-end ABAP server is made with the ABAP user ID instead

of the service user. This allows the administrator to set an external breakpoint for the ABAP user ID in

the back-end ABAP system, then perform the Planning and Consolidation client operation they wish

to debug. The operation then stops when the external breakpoint is encountered, and the user is taken

into the ABAP debugger.

If no debug users are specified, all connections between the .NET application server and the ABAP

application server are made with the three base connection users (SYSADMIN, ADMIN, or USER).

Procedure

1. To set up debug users, from Server Manager, select Server Maintain Debug Users .

2. Enter the Planning and Consolidation user ID, the ABAP user ID as the debug user ID (this must

be a dialog user), and the corresponding password for the ABAP user ID, then click Update.

3. Restart the IIS service for this change to become effective.

4.1.7 Server Manager Security

This topic describes the tasks that a system administrator (the SYSADMIN user specified during the

installation) can perform in Server Manager, as well as a non system administrator.



2010-09-17 PUBLIC 29/80

Server Manager Task SYSADMIN Non SYSADMIN

Launch the Server Manager Yes Yes, but a warning is displayed

View the server informationServer Information

Yes Yes

Run server diagnosticsServer Diagnostic

Yes Yes

Reset logon credentialsServer Reset Login Credentials

Yes Yes

Set up and maintain debug usersServer Maintain Debug Users

Yes Yes

Choose the server languageOptions Language

Yes No

Set client optionsOptions Client Options (SOX Compliance)

Yes Yes

Define system user groupsOptions Define System User Groups

Yes No

4.2 Configure Central Management System

This function allows you to set or change configuration options related to the Planning and

Consolidation server authentication mode.

Prerequisites

The Central Management System (CMS) is installed and the Planning and Consolidation system has

an administrator-level ID and password to the CMS.

Features

The following authentication modes are possible:

■ Windows

■ CMS

The Server Manager Options menu has different entries according to the authentication mode selected.

Windows Authentication Mode

From the Server Manager Options menu, you have the following entries that are specific to the Windows

authentication mode:

■ Define System User Groups

Here you can define groups of Windows users that have similar system responsibilities.

■ Enable CMS Authentication mode



30/80 PUBLIC 2010-09-17

Switch from Windows authentication to CMS authentication.

NOTE

If you have more than one server, you need to change the authentication mode on all servers.

CAUTION

Once CMS authentication is enabled, it is not possible to revert to Windows authentication.

CMS Authentication Mode

We recommend CMS authentication mode. On installation of Planning and Consolidation, CMS

authentication mode is selected by default.

From the Server Manager Options menu, you have the following entries that are specific to the CMS

authentication mode:

■ Configure CMS

The following parameters can be defined in the SAP BusinessObjects User Management System view:

Parameter Description

Trusted CMS name CMS system nameIf a CMS cluster name exists, use the cluster name (multiple names should be separated by a comma “,”).

Authentication type Select the appropriate value from the list

Cache expiration duration The time (in minutes) after which the cache is cleared

Click Update to update the user management system with these new values.

■ CMS Migration

Select this option to migrate all current Windows user authentication information to CMS user

authentication information.

To use this menu option, you should be logged on to CMS as an administrator. If you are not

already logged on, enter the correct logon information when prompted.

You are guided through the following actions:

● Select one or more Windows application sets to migrate to CMS from the list that is displayed.

The system displays a list of Windows user IDs for the selected application sets.

● Click 1. Validate user to enable the system to align Windows and BusinessObjects user IDs.

A green tick indicates that a corresponding BusinessObjects user exists while a red cross means

that there is no BusinessObjects user corresponding to the Windows user ID.

● Click 2. Migrate and then click OK to migrate the validated Windows user information to CMS.

● When the migration is complete, click 3. View result to view a detailed result log of the migration

process.

If required, you can save a copy of the result log.

● Set complete



2010-09-17 PUBLIC 31/80

Click 4 Set complete.

The migrated application sets are set as CMS mode application sets. These application sets are

no longer visible in the migration wizard.

More Information

Migrating Users to Central Management System [page 32]

4.3 Migrating Users to Central Management System

You can migrate users from Windows Active Directory (AD) mode to Central Management System

(CMS) mode using a provided migration tool.

Prerequisites

Make sure you have the latest version of Planning and Consolidation by uninstalling the 7.0 .NET server

and installing the 7.5 .NET server. Select the CMS authentication method during the installation. Also,

ensure that the ABAP server is upgraded to Planning and Consolidation 7.5.

Download and install SAP BusinessObjects Enterprise Server XI 3.1 or Mini-BOE from the SAP

Marketplace. For more information, see the Installation Guide.

Enable CMS Authentication mode from Server Manager Options Enable CMS Authentication Mode or

through the installation program (select CMS as the authentication method).

Procedure

To migrate users from AD to CMS

1. Set up the secWinAD mode so that BusinessObjects Enterprise Server can map the CMS user to the

corresponding Windows AD user. This step is optional.

If you do this step, the migration tool can automatically map the Windows AD users to CMS users.

If you do not do this step, you must manually map all Planning and Consolidation users from

Windows AD to CMS.

2. Log on to Windows as the system administrator defined in table uja_svr_default. Only this system

administrator can run the migration tool. You can change the system administrator by running

program UJA3_WRITE_SYS_USERS.

3. Run the migration tool (<bpc_install_folder>\Websrvr\Web\bin\MigrationTool.exe).

4. Log on to CMS as an administrator.

5. If you set up the user mapping in step 1, the migration tool maps the Windows AD users to CMS.

You can also map all the users manually.

Check the automatic mapping and add additional user mappings manually.


4.3 Migrating Users to Central Management System

32/80 PUBLIC 2010-09-17

6. Select Attributes which may contain USER_ID.

Attributes in Planning and Consolidation dimensions may contain the USER_ID. These attributes

should be changed as the USER_ID is changed to the new CMS ID. Select the attributes that contain

USER_ID.

7. Review and click Do Migration.

The migration is executed as an ABAP job. An ABAP user can monitor the job status for detailed

information (SAPGUI transaction: SM37).

If the migration is successful, the USER_ID in all ABAP tables changes from Windows user to a CMS

user.

The migration tool cannot be run again.

If the migration fails, everything that has been done is rolled back and the USER_ID in all Planning and

Consolidation tables are still the Windows users. In this case, the migration tool can be run again.

Result

Users can log on to Planning and Consolidation through CMS authentication.

NOTE

When users have been migrated from Windows to CMS, the user's cache still contains the Windows

authentication information. Each user should clear this cache to enable all features of Planning

and Consolidation. To clear the cache, at the first login to Planning and Consolidation after the

migration to CMS:

1. Open an Interface for an Office application

2. In the eTools menu, choose Clear Current View and then Clear Local Application Information

3. Close and then reopen the Interface for an Office application

4.4 Starting and Stopping .NET Components

Use the procedures described below to start and stop Planning and Consolidation SAP NetWeaver

components on a .NET server.

NOTE

You may also need to stop and restart Planning and Consolidation components if the system is

not performing in the expected manner.

Starting Planning and Consolidation Components

In the Microsoft Control Panel, choose Administrative Tools Internet Information Services and ensure that

the OSoft site is running. If it is not running, use the context menu to start it.


4.4 Starting and Stopping .NET Components

2010-09-17 PUBLIC 33/80

Stopping Planning and Consolidation Components

In the Microsoft Control Panel, choose Administrative Tools Internet Information Services , select the OSoft

site and use the context menu to stop it.

In the Microsoft Control Panel, choose Administrative Tools Component Services Com+ Application , select

all Planning and Consolidation SAP NetWeaver components and use the context menu to stop them.

4.5 Backup and Restore

You may need to back up your entire Planning and Consolidation system. For more information about

backing up SAP NetWeaver systems, see Backup Best Practices [page 34].

A more frequent backup operation is backing up an application set. Once backed up, an application set

can be restored on the same Planning and Consolidation system or on a different system. For more

information, see Backing Up and Restoring an Application Set [page 34]

4.5.1 Backup Best Practices

Procedure

Refer to the following items for information about backing up your Planning and Consolidation system:

1. On the SAP Help Portal, refer to the backup procedures at http://help.sap.com/saphelp_nw70/

helpdata/EN/7c/efa841c1dade34e10000000a1550b0/content.htm.

2. On SAP Service Marketplace at http://service.sap.com/solutionmanagerbp, refer to

documents 084 Business Continuity Management for SAP System Landscapes and 085 Emergency Handling for

Recovery of SAP System Landscapes.

3. On the SAP Developer Network at https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/

docs/library/uuid/30c221aa- b4e5-2910-b899-d268d84c19c5, refer to the article entitled

Architecting a high availability SAP NetWeaver infrastructure.

4.5.2 Backing Up and Restoring an Application Set

Backup and restore is a tool that allows you to back up or export a Planning and Consolidation

application set. You can then restore this application set to the same or to a different Planning and

Consolidation system.

The backup and restore process supports all Planning and Consolidation data, including application

set metadata, user management data, audit data, comment data, journal data, data manager packages,

file service data, work status data including work status locks data, master data, and transaction data.



34/80 PUBLIC 2010-09-17

http://help.sap.com/saphelp_nw70/helpdata/EN/7c/efa841c1dade34e10000000a1550b0/content.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/7c/efa841c1dade34e10000000a1550b0/content.htm

http://service.sap.com/solutionmanagerbp

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30c221aa-b4e5-2910-b899-d268d84c19c5

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30c221aa-b4e5-2910-b899-d268d84c19c5

4.5.2.1 Backing Up an Application Set

Backup supports all Planning and Consolidation data. You can back up a complete application set

including large volumes of data such as transaction data, journals, comments, audit, and work status

locks data.

Procedure

1. Log on to the source system and start transaction UJBR.

2. Choose Execute Backup.

3. Choose whether to execute the backup in the Background or Foreground.

If you choose the background mode, you should specify a directory on the application server for

the output file, for example \usr\sap\BackupRestoreDirectory.

If you choose the foreground mode, the output file is created on the frontend PC or network

destination. For example, you could specify that the destination for the output file is your PC's

desktop.

4. Identify the application set that is to be backed up and the destination directory.

5. If you do not need to back up the entire application set, you can choose what parts are included

in the operation. You can choose from:

■ Metadata tables

■ Master data

■ Transaction data

We recommend that you select all parts of the application set, but you can limit the number of

transaction records that are backed up.

6. Click Execute in the Backup/Restore application toolbar.

If you are running in foreground mode, status messages are displayed in the Backup/Restore

application status bar.

If you are running in background mode, you can monitor the process using the transaction

SM37. The name of the background job is BPC_BACKUP_<AppSet_ID>.

When the backup is complete, a message screen displays any messages generated during the backup

process. You can also view these messages in the application log using transaction SLG1.

Result

The operation generates a single zip file that contains all of the relevant application set data. This zip

file contains the following components:

■ Metadata.xml

This is a single file containing all relevant metadata.



2010-09-17 PUBLIC 35/80

■ Master Data

This folder contains many CSV files, one for each dimension in the application set. Each file contains

the dimension’s master data.

■ Transaction Data

This folder contains subfolders for each application in the application set.

■ File Service

This folder contains one subfolder called ROOT, which contain all of the files and folders associated

with this application set.

4.5.2.2 Restoring an Application Set

You can restore and application to the same Planning and Consolidation system or to a different system.

This can be useful if, for example, you want to transport an application set to an SAP Planning and

Consolidation installation for troubleshooting reasons.

Procedure

1. Log on to the source system and start transaction UJBR.

2. Choose Execute Restore.

3. Choose whether to execute the restore operation the Background or Foreground.

If you choose the background mode, the restore operation needs to access the input file from a

directory on the application server.

If you choose the foreground mode, the input file must be on the frontend PC or network

destination.

4. Enter the name of the application set that is being restored. This does not have to be the same as

the application set name used in the backup, but if it is the same, the application set cannot already

exist. You must first delete the application set before trying to restore it on the target system.

You must also specify the location of the input file.

5. You can choose which parts or the application set are included in the restore operation. You can

choose from:

■ Metadata tables

■ Master data

■ Transaction data

However, we recommend that you select all parts of the application set. When making a full restore

of an application set, always select all parts.

You can also limit the number of transaction records that are restored.



36/80 PUBLIC 2010-09-17

6. You can choose to Use Tech Names from Backup File.

You use this option when you want to restore the application set using the application set prefix

and technical names that were used in the backup file. This is important when restoring an

application set to a production system that uses the Planning and Consolidation transport

framework to promote applications sets throughout the landscape. In this scenario, the technical

names must be consistent across the systems, so it is important to use these same technical names

when restoring the application set in the production system.

Use this option only in disaster-recovery situations where you need to keep the technical names

consistent. In normal situations, you would probably want to generate new technical names when

restoring an application set in a different system. It is, however, important to note that the

application set prefix must not already exist in the target system. This prefix is used when generating

the technical names for the underlying BW objects.

NOTE

You must restore metadata before restoring master or transaction data. You must also restore

master data before restoring transaction data. You may do each step individually, but we

recommend that you do all three steps at the same time.

7. Click Execute in the Backup/Restore application toolbar.

If you are running in foreground mode, status messages are displayed in the Backup/Restore

application status bar.

If you are running in background mode, you can monitor the process using the transaction

SM37. The name of the background job is BPC_RESTORE_<AppSet_ID>.

When the restore is complete, a message screen displays any messages generated during the restore

process. You can also view these messages in the application log using transaction SLG1.

4.6 Microsoft Message Queue (MSMQ)

Planning and Consolidation uses Microsoft Message Queue (MSMQ) to store information about the

progress of asynchronous tasks, such as copying an application or processing a dimension. This provides

the ability to support more than one web garden process. See Configuring IIS Web Gardens to Run Multiple

Processes [page 38]

Each Planning and Consolidation web and application server can be configured with either a local or

remote MSMQ.

For information about installing and setting up the message queue, see the Installation Guide.

Local MSMQ


4.6 Microsoft Message Queue (MSMQ)

2010-09-17 PUBLIC 37/80

Using a local MSMQ is fine if you have only a single application server. However, if you run multiple

Planning and Consolidation web and application servers, each with its own local MSMQ, you must

configure the load balancer to support Layer 3 stickiness (IP affinity) to ensure that each client request

from a particular client machine is always processed by the same web or application server.

This type of load balancing configuration is not ideal for many customers, so we recommend using the

shared remote MSMQ described below, as it allows complete freedom in load balancer configuration.

Remote MSMQ

We recommend using a shared remote queue when you run a load balanced configuration with

multiple Planning and Consolidation application servers. If you use a remote MSMQ, we also

recommend that you use a remote Private queue since the system uses only the path specified during

the installation to look up the message queue, not the Active Directory. Use FormatName:DIRECT when

specifying a remote queue path to bypass any communication with the Active Directory. The entry in

the ServerConfiguration.config looks similar to the following:

<MessageQueue value="FormatName:DIRECT=OS:<machine_name>\$Private

\bpcmessagequeue"/>

For details on MSMQ path syntax and using FormatName see:

http://msdn.microsoft.com/en-us/library/ms706083(VS.85).aspx

http://msdn.microsoft.com/en-us/library/ms700996(VS.85).aspx

4.7 Configuring IIS Web Gardens to Run Multiple Processes

Planning and Consolidation is compatible with running multiple worker processes in IIS web gardens.

Prerequisites

Microsoft Message Queue has been installed. See the Installation Guide on SAP Service Marketplace.

Procedure

To configure the number of worker processes on the Application or Web server, use the following

procedure:

1. Choose Control Panel Administrative Tools Internet Information Services (IIS) Manager. .

2. In the Internet Information Services (IIS) Manager dialog box, choose <local_computer> Application

Pools .

3. In the DefaultAppPool context menu, choose Properties.

4. Enter a value in the Maximum number of worker processes field.


4.7 Configuring IIS Web Gardens to Run Multiple Processes

38/80 PUBLIC 2010-09-17

http://msdn.microsoft.com/en-us/library/ms706083%28VS.85%29.aspx

http://msdn.microsoft.com/en-us/library/ms700996%28VS.85%29.aspx

CAUTION

There may be performance issues if the number is greater than 1, depending on number of

processors and available RAM.

4.8 Best Practices for Performance Management

A number of factors affect Planning and Consolidation performance, including the following:

■ Number of dimension members

■ Amount of transactional data in a given application

■ Number of concurrent users

■ Hardware

■ Network bandwidth

4.8.1 Processing Tiers

To optimize performance, it is useful to understand the system tiers, and the processing that occurs

on those tiers. The following table outlines them:

Tier Description

Database The following processes occur at the database level: ■ Data reads ■ Data write-backs

NOTE

Write-back performance is primarily affected by work status locks, the validation framework, concurrency lock parameters, and the security model.

■ Metadata reads and writes ■ Application file storage (book repositories, report and input templates,

unstructured data, conversion files, and transformation files)

NetWeaver ABAP Application Server

The following processes occur at the application server level: ■ Script logic, calculations, and MDX parsing ■ Parameter-driven logic ■ Data Manager loads and ETL (extraction, transform, load) ■ OLAP engine and calculations

Microsoft IIS Web and Application Server

The following processes occur at the web server level: ■ User authentication ■ Web Service request parsing and processing ■ Interface for Web

BI Accelerator (optional component)

The BI Accelerator can be used to eliminate database read times through the use of in-memory storage.



2010-09-17 PUBLIC 39/80

4.8.2 Cube Fact Tables

Each InfoCube has the following two fact tables:

■ E fact table, for compressed records

■ F fact table, for uncompressed records

Records are automatically compressed during the optimization process (zero elimination is not used).

For more information about modifying and scheduling optimization process chains, see the Data

Manager section in the application help.

4.8.3 Cube Optimization

Optimizations have been implemented as process chains. As such, you can schedule them using Data

Manager or execute them using Administration.

For more information about modifying and scheduling optimization process chains, see the Data

Manager section in the application help. For more information about executing optimization process

chains, see the see the Administration section in the application help.

4.8.4 Cube Modification

During the optimization process, Planning and Consolidation creates a shadow cube and moves the

data to that cube when the system determines a data model reorganization is needed (for performance

reasons). Any external modifications made to the cube (for example, through transaction RSA1) will

be lost, and will not be moved with the data. These modifications include such things as tablespaces,

BI Accelerator indexes, DTPs (distributed transaction processing), aggregates, and database

performance parameters.

4.8.5 Writeback Parameters

You can modify writeback parameter values in transaction UJRO. These values are maintained at the

individual application level. In general, you will not need to change the default values. They are

described in the following table:

Parameter Default Description

PACKAGE_SIZE 40000 This specifies the size into which packages will be divided during the writeback process.

SPARSITY_COEF 5 If (the number of dimensions multiplied by the number of unique members in each dimension) is greater than (number



40/80 PUBLIC 2010-09-17


of records multiplied by the this value), then the record set is considered sparse.

RECLEVEL_NR 10 If the number of records being saved is less records than or equal to this value, record-based locking will be implemented.

MULTIPLY_COEF 50 In the situation where record-level locking is not being implemented and a sparse data set is being saved, this value specifie the maximum number of members for which you can implement record level locking (that is, when to swap to using a BETWEEN range in the lock table).

INTERVAL_NR 10 In the situation where record level locking is not being implemented and the data set being saved is NOT sparse, any dimensions with less than this number of distinct member values in the dataset will be locked using their single values. If the dimension has more than this number of records, the range between the low to high values will be locked.

4.8.6 SQE Parameters

You can modify SQE parameter values in transaction UJQ0. These values are maintained at the

individual application level. In general, it is not necessary to change these values. They are described

in the following table:


SPARSITY_COEF 5 If (the number of dimensions multiplied by the number of unique members in each dimension) is greater than (number of records multiplied by this value), then the record set is considered sparse.

4.9 Set Up of BPF E-mail Notifications

Use this procedure to set up e-mail notifications sent by business process flows.

Prerequisites

Application set users must have e-mail addresses.

Features

Owners are notified by e-mail when a BPF instance is created and actions are taken. In addition, they

are notified when an instance has been completed and ready to be finalized.

Reviewers are notified by e-mail when a step region is ready for review.



2010-09-17 PUBLIC 41/80

EXAMPLE

Subject: BPF instance <name> now ready for action

Text: BPF Instance for dimensions time 2009.total and category budget. Step region(s): first active

step number and step region dimension:member. As a participant in this business process please

select the following link: HTTP://sample_link/.

Creating a BPF instance generates a notification to all users with access to the BPF monitor.

Types of BPF e-mails

Planning and Consolidation contains a number of e-mail templates by default. These are S-type (system)

templates, which you cannot modify. You can create a copy of each system template and customize

the copy for your business needs. These are C-type (customized) templates.

You can customize the title and body of C-type (customized) e-mail templates. You can input multi-

language text in the e-mail body, and you can add the following variables to display information in the

e-mail to help its recipient:

■ %INST_NAME%

■ %STEP_NAME%

■ %URL%

■ %STEP_REGION_NAME%

You can add URLs to the body of an e-mail to give users direct access to BPF web. To be able to include

a URL in an e-mail, however, you must access Server Manager and provide the Web server name and

port number used in Planning and Consolidation. In Server Manager, choose Server Maintain Web

Server Name , enter the name of the Web sever, then choose Update.

You can activate or inactivate an e-mail by entering a Y or N in Is Active.

Managing BPF e-mails

Set up and customization of BPF e-mail notification templates is done on the back-end. Perform the

following steps:

1. In SAP GUI, choose transaction code SE80 for the Object Navigator.

2. Choose Package in the left navigation pane, then enter the package name UJB.

3. Choose Programs, then run UJB_MAINTAIN_EMAIL_TMPL.

You create a copy of a system template by selecting a system template then clicking the Create customized

email template icon in the toolbar. Then, modify it as needed,



42/80 PUBLIC 2010-09-17

5 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and

testing procedures for complex software landscapes and multiple software development platforms.

These functions support your project teams, development teams, and application support teams. The

goal of Software Change Management is to establish consistent, solution-wide change management

that allows for specific maintenance procedures, global rollouts (including localizations), and open

integration with third-party products. This section provides additional information about the most

important software components.

5.1 Transport Management

Transports allow you to move an AppSet across a landscape. For example, you can transport an AppSet

from a development environment to test environment and then to a production environment.

For performance reasons during a transport, the product checks the objects that exist in the target

system and only transports objects that have changed. Additionally, not all objects are transported.

All aspects of an AppSet are transported except the following:

■ Master Data

■ Transaction Data

■ Flat Files uploaded to Data Manager

■ Any object or configuration requiring master data

When transporting, all transport-relevant objects for an AppSet are collected based on the

configuration set for what is done in development.

When importing the transport into the target system, the system checks the existing objects in the

target system and only overwrite changes if the object has changed. This way, you only transport the

changed objects for an entire AppSet. You cannot transport more granular objects than the whole

AppSet, but only the delta changes are moved. The exception to this rule is the transporting of files

within file service which are always overwritten.

An additional exception is the configuration drive in UJT_TRANS_CHG. When a transport is imported, it

checks the entries in UJT_TRANS_CHG in the target system. It does not transport this relevant

configuration if the entry is set to PRODUCTION. It only imports the configuration for entries set to

DEVELOPMENT.



2010-09-17 PUBLIC 43/80

The process of transporting involves configuring the system and then transporting. The following

subsections contain a description of the transport process and some other useful information about

transporting. If you are still having problems, refer to Troubleshooting Transport [page 71].

5.1.1 Transport Configuration

Before you can transport, you must first configure the SAP NetWeaver transport framework and then

configure which items get transported.

Prerequisites

You are the SAP NetWeaver administrator.

Procedure

1. Configure the SAP NetWeaver transport framework by creating transport domains, routes, and

other aspects of a transport.

For information, see Change and Transport System in the SAP NetWeaver Application Help on the SAP

Library at http://help.sap.com.

2. Configure the system to import Client-Dependent Objects because all Planning and Consolidation

data is client-dependent. Do the following:

■ Create User ALEREMOTE (BW Background User)

■ Create an RFC destination to allow the import method to be executed in the correct client.

Otherwise it is executed in client 000. Use transaction RSTPRFC to create the destination for

this client

For information, see Importing Client-Dependent Objects in the SAP NetWeaver Application Help on the

SAP Library at http://help.sap.com.

3. Configure which objects get transported. This involves starting the transaction SM30, going to the

table UJT_TRANS_CHG, and setting the objects to create in development and the objects to create in

production.

Anything marked as Development in the table is transported when a transport is collected from

this system. Anything marked as Production is not transported when a transport is collected from

this system.

For information about transport objects, see Transport Objects [page 46].



44/80 PUBLIC 2010-09-17

http://help.sap.com

http://help.sap.com

5.1.2 Transport Execution

5.1.2.1 Transporting Application Sets into Production

To move an application set into your production environment, use the following procedure:

1. Log on to your development SAP NetWeaver system.

2. Enter the transaction code UJBPCTR.

3. From the Planning and Consolidation Transports — Create Transport Request screen, do the following:

■ Select Insert/Modify Request to promote a new or modified application set from the development

to the staging or production system or select Delete Request to delete the application set in target

systems.

■ Enter the application set that you are promoting or deleting in the Appset Id field.

■ If you want to release the request immediately upon creating, select Release Request Directly.

NOTE

This setting does not take effect until the transport operation has been completed.

4. Choose Execute.

5. Contact IT to import the request into the target systems throughout the landscape.

Once this request is created, the transport can be viewed, maintained, and released using transaction

SE10.

5.1.2.2 Transporting Process Chains into Production

To move process chains into your production environment, use the SAP NetWeaver transport process

for process chains.

NOTE

The corresponding default instruction in table UJD_INSTRUCTIONS needs to be transported via

transaction SE16.

PrerequisitesThe process chain is assigned to component /cpmb/BCP.

5.1.3 Transport Maintenance

There are certain maintenance tasks involved with transports.

FeaturesTransport maintenance involves the following:



2010-09-17 PUBLIC 45/80

■ After deleting an AppSet, you can make sure that all data has been removed.

Use program UJT_CHECK_TABLE_ENTRIES to check how many records exist in the UJ* database

tables for a particular appset.

■ You can test the ApShell installation process or test the migration tools.

Use program UJT_DLT_TRANS_DATA to delete data from the transport shadow tables

(UJT_TRANS_OBJ and UJT_TRANS_HDR) for a particular AppSet.

NOTE

Be careful when using the UJT_DLT_TRANS_DATA program because this is a System Admin

utility.

5.1.4 Transport Objects

You can transport any of the following TLOGO objects. Any object marked for Development in the table

UJT_TRANS_CHG in transaction SM30 is transported.

For information about configuring the system for a transport and marking objects for Development,

see Transport Configuration [page 44].

5.1.4.1 AppSet

The object type ASET refers to an application set. It can be configured from transport within table

UJT_TRANS_CHG via transaction SM30. It is recommended to always have this object set to

Development. If this object is set to Production, then the application set changes are not transported.

There are valid scenarios where only specific changes may need to be imported, for example script logic

changes. At those times, this may be flagged as production to send only the sub-objects of the application

set that need to be sent. However, as a best-practice, it is recommended to transport the entire

application set to ensure all changes are fully transported and dependencies are not missed between

objects.

5.1.4.2 Application

The object type APPM refers to an application. It can be configured from transport within table

UJT_TRANS_CHG using transaction SM30. This setting controls whether applications are imported into

your target system when importing a Planning and Consolidation transport. If this is flagged to

Development, all application changes within the application set are imported. This includes which

dimensions are assigned to the application.



46/80 PUBLIC 2010-09-17

If the dimensions assigned to the application are the same in the target application set, then the

underlying technical cube in SAP NetWeaver BW does not change. However, if the dimensionality

changes in development, and then this application is transported, the transport creates a shadow cube

with the new structure and moves the application data from the old application to the new application

and then deletes the old application.

Assuming a new dimension is added in development and this new dimension is assigned to a new

application, this dimension is not pre-populated in the application with the first dimension member

from the member sheet. In most cases, customers assign a NULL value as the first member in the member

sheet as a best practice.

When transporting this application with a new dimension, there are no dimension members in the

target system. In this case, the first member is transported from development to the target system and

then this member is inserted into the application as part of the application change.

5.1.4.3 Script Logic

The object type K2SC refers to Script Logic File. It can be configured from transport within table

UJT_TRANS_CHG via transaction SM30. This setting controls whether script logic files are imported into

your target system when importing a Planning and Consolidation transport. If this is flagged to

Development, all script logic changes within the AppSet are imported.

If dimension members are hard-coded in the script logic file and dimension members are different

between source and target systems, then the script logic may need to be changed in the target system.

Therefore, it is a best practice to ensure that any dimension member being referred to in development

is the same member in production (keep the master data in sync between development and production).

Additionally, script logic files can be built more generically without hard-coding dimension members

in the script file by using data manager packages to pass parameters.

5.1.4.4 Table Driven Logic (Business Rules)

The object type TDLO refers to Business Rules configuration for consolidations. It can be configured

from transport within table UJT_TRANS_CHG via transaction SM30. This setting allows you to control

whether business rules are imported into your target system when importing a Planning and

Consolidation transport. If this is flagged to Development in the target system, all business rules changes

within the AppSet are imported.

It is typically a best practice to configure business rules in development and test them in development

before transporting them through the landscape.



2010-09-17 PUBLIC 47/80

5.1.4.5 Workbooks

The object type WORK refers to Dynamic Report Templates and Dynamic Input Schedules. It can be

configured from transport within table UJT_TRANS_CHG via transaction SM30. This setting allows you

to control whether these reports are imported into your target system when importing a Planning and

Consolidation transport. If this is flagged to Development in the target system, all workbook changes

within the AppSet are imported.

There is currently no method for transporting only some workbooks and not others. If workbooks

need to be created in production for the whole application, it is a best practice to create a sub-folder

within production within the eexcel folder that does not exist in development. All production reports

can be stored in this sub-folder. This way, they would not get overwritten when transporting an AppSet

from development to production. The file service never transports a deletion. Existing files created in

production are not deleted when transporting files.

Any workbooks stored in TEAM or USER folders are not transported with this setting. The workbooks

stored within TEAM folders are transported with the TEAM transport setting (in UJT_TRANS_CHG).

The path that gets transported is this path within file service:

<Drive>\WEBFOLDERS\%APPSET%\%APP%\EEXCEL\*

Any workbook saved to a team folder are transported as part of the TEAM transport.

5.1.4.6 Reporting

The object type REPT is currently not used within Planning and Consolidation.

5.1.4.7 Journals

As of 7.5 SP02, journal templates and journal entries are not transported. Also, transporting a remodeled

application deletes all journal templates for the application on the target system and the corresponding

journal entries are no longer accessible. It is a best practice to back up journal entries using the Data

Manager packages to backup journals prior to the transport.

5.1.4.8 Security

The object type SECU refers to member access profiles and task access profiles. It can be configured from

transport within table UJT_TRANS_CHG via transaction SM30. This setting controls whether member

access profiles and task access profiles are imported in your target system when importing a Planning



48/80 PUBLIC 2010-09-17

and Consolidation transport. If this is flagged to Development, all member access profiles and task access

profiles within the AppSet are imported.

For member access profiles, if the members are not the same between development and production,

they must be altered in production or this security object must be set to Production to avoid

transporting member access profiles. However, this one setting controls both member access profiles

and task access profiles, so you must be careful when changing it.

5.1.4.9 Work Status

The object type WSTA refers to Work Status configuration. It can be configured from transport within

table UJT_TRANS_CHG via transaction SM30. This setting allows you to control whether work status

configurations are imported in your target system when importing a Planning and Consolidation

transport. If this is flagged to Development in the target system, all work status configuration within

the AppSet are imported.

Transports support the work states and the work status settings that are defined. Transports does not

include any work status locks that have been set.

5.1.4.10 Live Reports

The object type LREP refers to Live Reports. It can be configured from transport within table

UJT_TRANS_CHG via transaction SM30. This setting allows you to control whether live reports are

imported in your target system when importing a Planning and Consolidation transport. If this is

flagged to Development in the target system, all live reports within the AppSet are imported.

5.1.4.11 Comments

The object type COMM refers to Comments. Currently, this entry is not used by Planning and

Consolidation. Transporting of comments is not supported, and there is no configuration related to

comments that needs to be transported.

5.1.4.12 Business Process Flows

The object type BPFT refers to Business Process Flows. The content of a table, whose name is defined in

table UJT_TRANS_TAB with Tlogo BPFT, is transported.

Any file, whose path is defined in table UJT_TRANS_FIL with Tlogo BPFT, is transported.



2010-09-17 PUBLIC 49/80

5.1.4.13 Audit

The object type AUDI refers to Audit. Currently, this entry is not used by Planning and Consolidation.

Transporting of audit logs or audit configuration is not supported, and there is no configuration related

to audit that needs to be transported. Audit configuration needs to be turned on directly in production

for the applications and task changes that need to be audited.

5.1.4.14 Data Manager Packages

The object type PACK refers to Data Manager Packages and Package Groups. It can be configured from

transport within table UJT_TRANS_CHG via transaction SM30. This setting controls whether Data Manager

packages and package groups are imported in your target system when importing a Planning and

Consolidation transport. If this is flagged to Development in the target system, all Data Manager packages

and package groups within the AppSet are imported.

This includes all packages in any team folders as well. Therefore, if you decide to transport this, the

TEAM object should also be flagged for transport to ensure the team exists for transporting the data

manager packages assigned to teams. Otherwise, transports of team packages fails.

5.1.4.15 Data Manager Transformation Files

The object type FTRA refers to Data Manager Transformation Files. It can be configured from transport

within table UJT_TRANS_CHG via transaction SM30. This setting controls whether Data Manager

Transformation Files are imported in your target system when importing a Planning and Consolidation

transport. If this is flagged to Development in the target system, all Data Manager transformation files

within the application set are imported.

Deletion of transformation files is not supported with transports, and must be done manually in each

system.

This does not transport any transformation files assigned to specific Team folders. These transformation

files are only transported if the TEAM object is marked as Development.

5.1.4.16 Data Manager Conversion Files

The object type FCON refers to Data Manager conversion files. It can be configured from transport within

tableUJT_TRANS_CHG via transaction SM30. This setting controls whether Data Manager conversion files

are imported in your target system when importing a Planning and Consolidation transport. If this is

flagged to Development, all Data Manager conversion files within the AppSet are imported.



50/80 PUBLIC 2010-09-17

Deletion of conversion files is not supported with transports, and must be done manually in each

system.

This does not transport any conversion files assigned to specific Team folders. These conversion files

are only transported if the TEAM object is marked as Development. Any conversion files that are stored

per user as private publications are not transported.

5.1.4.17 Data Manager Macro Files

The object type MCRO refers to Data Manager macro files. It can be configured from transport within

table UJT_TRANS_CHG via transaction SM30. This setting controls whether Data Manager macro files are

imported in your target system when importing a Planning and Consolidation transport. If this is

flagged for Development, all Data Manager macro files within the application set are imported.

5.1.4.18 New Files and Folders

There are some files and folders that only get transported the first time an AppSet is created or if a new

application is created within the AppSet.

The following folders are transported just the first time an AppSet is transported. No sub folders are

transported as part of the entry.

NOTE

This information is relevant for Planning and Consolidation 7.5 implementations. If you are

running 7.0 SP02, see Other Files and Folders [page 53].

■ AppSet

Anytime a new application within the development system is created and transported to a target

system where this new application does not already exist, this AppSet folder is transported again:

<Drive>\WEBFOLDERS\%APPSET%\

■ Application


system where this new application does not already exist, all Application folders are transported

again.

<Drive>\WEBFOLDERS\%APPSET%\%APP%\

■ AppPublications



2010-09-17 PUBLIC 51/80


system where this new application does not already exist, all AppPublications folders are

transported again:

<Drive>\WEBFOLDERS\%APPSET%\%APP%\APPPULBICATIONS

■ Data Manager


system where this new application does not already exist, all DataManager files and folders listed

below are transported again.

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\DATAFILES\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\MACROFILES\*

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\PACKAGEFILES\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\PACKAGEFILES\EXAMPLES\*

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\PACKAGEFILES\MYFILES\*

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\PACKAGEFILES\SYSTEMFILES\*

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\SELECTIONFILES\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\TRANSFORMATIONFILES\EXAMPLES\*

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\TRANSFORMATIONFILES\SYSTEMFILES\*

■ PrivatePublications


system where this new application does not already exist, all Application folders are transported

again.

<Drive>\WEBFOLDERS\%APPSET%\%APP%\PRIVATEPUBLICATIONS\

■ Anytime a new application within the development system is created and transported to a target

system where this new application does not already exist, all the following folders are transported

again:

<Drive>\WEBFOLDERS\%APPSET%\ADMINAPP\

<Drive>\WEBFOLDERS\%APPSET%\ADMINAPP\DIMCACHE

<Drive>\WEBFOLDERS\%APPSET%\APPSETPUBLICATIONS\

<Drive>\WEBFOLDERS\%APPSET%\APPSETPUBLICATIONS\LIBRARY\

<Drive>\WEBFOLDERS\%APPSET%\APPSETPUBLICATIONS\PUBLICATIONS\

<Drive>\WEBFOLDERS\%APPSET%\DOCUMENTS\

<Drive>\WEBFOLDERS\%APPSET%\SYSTEMFILES\

<Drive>\WEBFOLDERS\ADMINTEMPLATES\*



52/80 PUBLIC 2010-09-17

5.1.4.19 Team

The object type TEAM refers to Teams. It can be configured from transport within table

UJT_TRANS_CHG via transaction SM30. This setting controls whether Team files are imported in your

target system when importing a Planning and Consolidation transport. If this is flagged to

Development in the target system, all Team files within the application set are imported.

This refers to files stored under this path:

<Drive>\WEBFOLDERS\%APPSET%\%APP%\TEAM FILES\*

Teams that are created in development are never transported. User assignments for teams are not

transported because users are configured in each environment and typically, the users accessing the

development system would not be the same users to access the production system. Therefore, this

TLOGO object is only useful if the team names are the same in development and production (created

manually in each environment). Then the files for the team can be transported to the team in the

target system.

The team transport transports any conversion file or transformation files that are assigned to this team.

Data Files for Data Manager in the Team folder are not transported.

Additionally, the team transport transports any workbooks (dynamic report templates or dynamic

input schedules) that are assigned to the Team folder.

Any Data Manager packages assigned to teams are handled by the PACK object, not the TEAM object. This

means that Data Manager packages that are assigned to the team are only transported if the PACK object

is set to Development in table UJT_TRANS_CHG.

5.1.4.20 Other Files and Folders

Like transformation, conversion, and macro files, other Appset files and folders are transported as well.

In some cases, only the folder itself is transported, while in other cases, the folder as well as the folder’s

contents are transported. The “*” indicates where the contents of the folder are included. Also, some

file extension filtering is done. For example, the use of the *.LGF defines that only the files with a .LGF

extension from that folder are transported.

NOTE

This information is relevant for SAP Planning and Consolidation 7.5 and higher implementations.

If you are running 7.0 SP03, see New Files and Folders [page 51].

<Drive>\WEBFOLDERS\ADMINTEMPLATES\*

<Drive>\WEBFOLDERS\%APPSET%\

<Drive>\WEBFOLDERS\%APPSET%\ADMINAPP\



2010-09-17 PUBLIC 53/80

<Drive>\WEBFOLDERS\%APPSET%\ADMINAPP\DIMCASHE\

<Drive>\WEBFOLDERS\%APPSET%\APPSETPUBLICATIONS\

<Drive>\WEBFOLDERS\%APPSET%\APPSETPUBLICATIONS\LIBRARY\

<Drive>\WEBFOLDERS\%APPSET%\APPSETPUBLICATIONS\PUBLICATIONS\

<Drive>\WEBFOLDERS\%APPSET%\DOCUMENTS\

<Drive>\WEBFOLDERS\%APPSET%\SYSTEMFILES\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\DATAMANAGER\DATAFILES\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\EEXCEL\*

<Drive>\WEBFOLDERS\%APPSET%\%APP%\EEXCEL\INPUT SCHEDULES\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\EEXCEL\INPUT SCHEDULES\WIZARD\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\EEXCEL\PDBOOKS\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\EEXCEL\REPORTS\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\EEXCEL\REPORTS\WIZARD\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\EEXCEL\REPORTS\WIZARD\HOTANALYSIS\

<Drive>\WEBFOLDERS\%APPSET%\%APP%\JOURNALS\*

<Drive>\WEBFOLDERS\%APPSET%\ADMINAPP\%APP%\*.LGF

<Drive>\WEBFOLDERS\%APPSET%\SYSTEMLIBRARY\LOGIC LIBRARY\*.LGF

<Drive>\WEBFOLDERS\%APPSET%\ADMINAPP\LOGIC EXAMPLES\CONSOLIDATION\*.LGF

5.1.4.21 Web Admin Parameters

The object type ADEF refers to Web Admin Parameters.

All the entries listed below are transported. The X means that the specific Web Admin Parameter is

transported only the first time a new application is created. If the Web Admin Parameter exists in the

target system already because it is an application that already got transported, then the Web Admin

Parameter in the target system is not overwritten.

Transported Web Admin Parameters Transported for New Applications

ADMIN_DIM_CACHE

ALLOW_EXTENSIONS

ALLOW_FILE_SIZE X

AVAILABLEFLAG

AVAILABLEMSG

AVAILABLEURL X



54/80 PUBLIC 2010-09-17

Transported Web Admin Parameters Transported for New Applications

BPC_STATISTICS X

CALCULATION

COMMENT

DEFAULT_EXTENSIONS

FXTRANS

INTCOBOOKINGS

INTERCOMPANY

JREPORTZOOM

LOGLEVEL

MAXLRCOLUMNS X

MAXLRROWS X

MESSAGE

OPENINGBALANCE

ORG_ACCOUNTLIST

ORG_ACCOUNTOWN

ORG_OWNERSHIPCUBE

ORG_PARENTPROPERTY

OWNERSHIP_APP

SMTPAUTH X

SMTPPASSWORD X

SMTPPORT X

SMTPSERVER X

SMTPUSER X

STATUS

SYSTEM

TEMPLATEVERSION

TEMPLATE_CACHE

UPLOADTEMP

USELIM

VALIDATIONS

VERSION

YTDINPUT

The ADMIN_DIM_CACHE also has special handling. It is always incremented in the target system to

invalidate the dimension member cache when a transport is done. This is done for all dimensions.



2010-09-17 PUBLIC 55/80

5.1.4.22 Dimension

The object type DIME refers to a Dimension. It can be configured from transport within table

UJT_TRANS_CHG via transaction SM30. This setting controls whether dimensions are imported in the

target system when importing a Planning and Consolidation transport. If this is flagged to

Development, all dimension changes within the application set are imported. This includes the

properties assigned to dimensions.

If the properties assigned to a dimension change, this triggers the removing/adding of these dimensions

as navigational attributes from all associated applications within the application set. Therefore, when

transporting dimensions, it is also important to transport the applications within this application set

as well to ensure the attribute changes to the applications are also transported.

When transporting this application with a new dimension, there are no dimension members in the

target system. If an application needs to be filled by this dimension in a transport, the first member is

transported from development to the target system and then the member is inserted into the

application as part of the application change.

5.1.4.23 Dimension Property

The object type DIMA refers to a Dimension Property. It can be configured from transport within table

UJT_TRANS_CHG via transaction SM30. This setting controls whether dimension properties are imported

in the target system when importing a Planning and Consolidation transport. If this is flagged to

Development, all dimension property changes within the application set are imported. This includes

the properties assigned to dimensions.

It is strongly recommended to use the same setting used for dimensions within transporting to ensure

consistency.

5.1.4.24 Validation Rules

The object type VALD refers to Validation Rules. It can be configured from transport within table

UJT_TRANS_CHG via transaction SM30. This setting allows you to control whether validation rules are

imported in the target system when importing a Planning and Consolidation transport. If this is flagged

to Development in the target system, all validation rules within the application set are imported.

For validation rules, if the members are not the same between development and production, they must

be altered in production or this validation rule must be set to Production to omit validation rules from

the transport.



56/80 PUBLIC 2010-09-17

5.1.4.25 Data for ApShell

Although in general, data files for Data Manager are not transported, there is a special case for ApShell

which transports files in the following folder:

<Drive>\WEBFOLDERS\%APPSET%\%APP%\TEAM FILES\INSTALLATION\DATAMANGER\*

This special case allows the ApShell installation to have some sample data to load for ApShell.

5.1.5 Deployment Scenarios

There are two typical landscape deployment scenarios.

Development to Production

In the Development to Production deployment scenario, you create and maintain an AppSet in

development. All dimensions, dimension properties, and applications are created in development. A

decision needs to be made for all other objects in UJT_TRANS_CHG.

Typically, all objects are created in development and transported to production. The exceptions include

security and teams, which typically are handled landscape by landscape.

Additionally, the decision would need to be made for Workbooks (report templates and input

schedules). If this is done in development, then workbooks in production would be overwritten. If this

is done in production, then workbooks from development are not transported.

For more information, see Workbooks [page 48].

Production Only (with Development for patch testing)

In this scenario, you work in production only. When you need to apply a patch, you transport the

AppSet from Production to Development. You test the patch in Development. After the patch is

validated, you apply the patch to Production.

Best Practices for Ongoing Development

Some customers have release cycles in which they are unable to transport an entire AppSet. For example,

they may have a configuration that has Production support changes and another configuration on the

same application or Appset that is transported at a later stage in the project cycle.

In this case, you should have two AppSets in development, one for new development, and one for

production support changes. When a production support change occurs, this should be done in both

AppSets in development. When the cutover of new development needs to be transported, then the

configuration can be moved to the production support AppSet and transported.



2010-09-17 PUBLIC 57/80

5.2 Product Versioning

Product versioning in Planning and Consolidation indicates the release number, enhancement package

number, and support package number. You can also view the patch level.

Numbers for Release, Enhancement Package, and Support Package

You can view the major and minor release number, enhancement package number, and support

package number of the system by opening the About dialog box. The product version is in the following

format:

R.ME.SS

Where:

■ R is the major release number

■ M is the minor release number

■ E is the enhancement package number

■ SS is the support package number

EXAMPLE

If a product version in the About dialog box reads 7.50.01, 7 is the major release number, 5 is the

minor release number, 0 is the enhancement package number, and 03 is the support package

number.

Patch Level

Patch levels are four digits in length. For the product and .NET assemblies, the versioning (including

patch level) information is displayed in the form:

R.ME.SS.PPPP

Where R, M, E, and, SS are as above and PPPP is the patch number.

You can view the patch level of a client in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\OUTLOOKSOFT

\50\CLIENT\PATCHVER.

To check the production version, the registry key for the Admin client is HKEY_LOCAL_MACHINE

\SOFTWARE\OUTLOOKSOFT\50\ADMIN\VERSION, and for the Excel client, the path is HKEY_LOCAL_MACHINE

\SOFTWARE\OUTLOOKSOFT\50\CLIENT\VERSION.

When you install a patch, the version of changed dlls reflects the appropriate version and patch level.

For example, if you install 7.50 SP0<x>, the version of all dlls is 7.50.0<x.>.0000. If you install patch

1, the version of any changed dlls is 7.50.0<x.>.0001. The version of dlls that are not changed by a patch

does not change.

However, for Visual Basic 6.0 (VB6) and Planning and Consolidation 7.5, the versioning for the VB6 dlls

has the format:



58/80 PUBLIC 2010-09-17

R.ME.NN.SSPP

Where:

■ R is the major release number

■ M is the minor release number

■ E is the enhancement package number

■ NN cannot be used

■ SS is the support package number

■ PP is the patch number

If no patches have been installed, the patch levels on dlls are zero.



2010-09-17 PUBLIC 59/80

6 Troubleshooting

6.1 Troubleshooting in Planning and Consolidation

The following table lists common Planning and Consolidation problems that you may encounter, as

well as suggestions for troubleshooting and resolving the problem:

Problem Analysis Solution

Marginal text and buttons in Planning and Consolidation dialog boxes are unreadable or incorrectly formatted.

Determine the DPI font settings in the host computer.

On the Settings tab in the Microsoft Windows Display Properties dialog box, choose Advanced. On the General tab, ensure that the DPI setting is 96 DPI.

Features

You can view information on key statistics related to server performance. When you start Server

Manager by selecting Start All Programs SAP Server Manager , the System Information window is

displayed.

You can run a server diagnostics tool that checks for the server and client prerequisites. The results

are displayed on the screen when you select Server Diagnostic . In addition, the system saves a full

diagnostic report to the \Server Management\osoftdiagnostic.txt file.

6.2 Troubleshooting on a .NET Server

If your .NET server is not having in the expected manner, you may need to stop and restart Planning

and Consolidation components. See Starting and Stopping .NET Components [page 33].

6.3 Analyzing Problems Using Solution Manager Diagnostics

The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of

problems. For information about setting up Solution Manager Diagnostics, see Connecting to Solution

Manager Diagnostics [external document] in the Planning and Consolidation 7.5 NW Installation Guide.

6 Troubleshooting

6.1 Troubleshooting in Planning and Consolidation

2010-09-17 PUBLIC 61/80

6.4 Installing Appsight Black Box Service

Procedure

1. Download and extract the *.rar files attached to SAP Note 1356729 from SAP Service Marketplace.

2. Create a directory on your C:\ drive called Identify.

3. Copy either Triserv2.rpr or Triserv_XpressServer.rpr file into the Identify folder depending

on what application is needed to be monitored.

■ Triserv2.rpr

BlackBox profile that is used by the application. This profile outlines the type of process for

BlackBox to monitor. This filename must match the one that is in the startservice.bat file.

■ Triserv_XpressServer.rpr

The Xpress Server profile. This filename must match the one that is in the

startservice.bat file.

4. Install AppSight Black Box Service in standalone mode.

1. Run AppSight Black Box Service.exe.

2. Select Install.

3. Accept the agreement and choose Next.

4. Enter any information for username and company name and choose Next.

5. Leave the server prompt blank for standalone mode and choose Next.

6. Leave Black Box with no license option and choose Finish.

5. Copy the startservice.bat and stopservice.bat files into the Identify folder.

Startservice.bat starts the application using the profile path and the naming convention for the

log. Stopservice.bat stops the Blackbox application. You must stop the application before you can

copy the log.

6. Run startservice.bat to begin logging.

Once you start the application, the Identity folder contains an .ASLfile, which is the log that will write

all the information from the application. The computer name and date are used as a variable for the

naming convention.

The log stays at 0 bytes until the service is stopped and only then is its actual size shown.

RECOMMENDATION

Stop and start the service at the end of each day, copy the file to another folder, and have the

application create a new one. This allows you to monitor the file size.

6 Troubleshooting

6.4 Installing Appsight Black Box Service

62/80 PUBLIC 2010-09-17


6.5 Reporting and Analyzing System Changes

Within Solution Manager Diagnostics, you can use E2E Change Reporting and Change Analysis (E2E

CA) to view and report on technical configuration changes that have been made to your SAP Planning

and Consolidation systems. Change Reporting and Analysis provides a top-down view of configuration

parameters and configuration parameter changes. It is based on the data of the Configuration and

Change Database (CCDB).

Documentation is available to you on SAP Service Marketplace at http://service.sap.com/alm-

tools. Navigate to SAP Solution Manager and Tools SAP Solution Manager End-to-End Root Cause

Analysis , then review the E2E Change Analysis - User Guide as well as the documentation listed under

Installation and Configuration.

6.6 Generating and Analyzing Trace Files Using E2E Trace

You can generate trace files on client and server components for troubleshooting purposes using E2E

Trace. Trace files collect information about client and server interactions presenting trace information

about the entire request and response of a business process step. The trace files then upload to the server

for analysis in SAP Solution Manager Diagnostics (SMD). Client side and server side trace information

is displayed in the E2E Trace application in SMD.

E2E Trace is delivered and installed with Planning and Consolidation. To configure and activate tracing

on a client machine, see Logging and Tracing Configuration [external document].

After enabling and running tracing, you can obtain information about evaluating the results of the

trace in the E2E Trace Analysis - User Guide in the Diagnostics section of SAP Service Marketplace.

Prerequisites

■ Ensure that the latest Planning and Consolidation Clients with the E2E Trace plug-in are installed

on your client machine.

■ Introscope Workstation has been downloaded to your PC.

■ The DotNet Agent of the Planning and Consolidation server is online. Refer to the section Verifying

the DotNet Agent of the Planning and Consolidation Server is Online below for instructions.

■ The minimum release on the SAP Solution Manager Diagnostics side for E2E Trace Analysis is

Solution Manager 7.0 EhP 1 SP23.

Procedure

Generating and analyzing trace files using E2E Trace involves the following tasks, which are described

below:

6 Troubleshooting

6.5 Reporting and Analyzing System Changes

2010-09-17 PUBLIC 63/80

http://service.sap.com/alm-tools

http://service.sap.com/alm-tools

■ Enable tracing in the ABAP back-end system

■ Perform a trace in the Administration module

■ Perform a trace in the Microsoft Excel module

■ Manually upload the trace file to SMD if not done automatically

■ Evaluate the trace file in SAP Solution Manager

Enable Tracing in the ABAP Back-end System (NetWeaver platform only)

1. Enter the Root Cause Analysis work center of SAP Solution Manager.

2. Choose End-To-End Analysis.

3. Select the query that contains all systems involved within the E2E trace and select the system ID

of the Planning and Consolidation ABAP stack.

4. Choose Trace Analysis, which opens a new window with the E2E Trace Analysis application.

5. Select the Trace Enabling tab.

6. Select the system ID of the Planning and Consolidation ABAP stack.

7. Select Enable. A green icon displays besides the system ID.

Perform a Trace of the Administration Module

1. Launch the E2E Plug-In by running plugin-starter-gui.exe.

2. Select Assign, choose OSoftAdminMain.exe, then choose Save.

3. Select Launch, then ensure that Instrument HTTP protocol is selected and that wininet is set as the protocol.

4. When the Admin module opens, enter the following values in the E2E Trace Plug-in user interface:

1. Enter a name for your trace in Business Transaction Name.

After uploading the trace to SMD, you locate the trace by this name.

2. Set the Session Trace Level to High.

3. Enter the SMD server host.

4. Enter the SMD HTTP port.

5. Choose Start Transaction in the E2E Trace Plug-in user interface, then choose OK to log on to the

Admin module.

6. Choose Stop Transaction in the E2E Trace Plug-In user interface to upload the transaction XML to

the SMD server.

7. In the E2E Trace application within SMD, collect the corresponding trace of the .NET server and

ABAP server.

Perform a Trace of the Microsoft Excel Module

1. Launch the E2E Plug-In by running plugin-starter-gui.exe.

2. Select Assign, choose Excel.exe, then choose Save.

6 Troubleshooting


64/80 PUBLIC 2010-09-17

3. Select Launch, then ensure that Instrument HTTP protocol is selected and that wininet is set as the protocol.

4. When the Admin module opens, enter the following values in the E2E Trace Plug-in user interface:

1. Enter a name for your trace in Business Transaction Name.

After uploading the trace to SMD, you locate the trace by this name.

2. Set the Session Trace Level to High.

3. Enter the SMD server host.

4. Enter the SMD HTTP port.

5. Click Log On in the Excel tool bar.

6. Choose Start Transaction in the E2E Trace Plug-in user interface, then choose OK to log on to the

Excel module.

7. Choose Stop Transaction in the E2E Trace Plug-In user interface to upload the transaction XML to

the SMD server.

8. In the E2E Trace application within SMD, collect the corresponding trace of the .NET server and

ABAP server.

Manually Upload the Trace File

If you need to manually upload a trace file to SMD, perform these steps:

1. On the client machine on which you recorded the trace, expand the Manually upload section.

2. Choose Browse under Upload BusinessTransaction.xml. The file to upload appears in <trace plug-in

folder>\Logs.

3. Select the BusinessTransaction.xml file and choose Upload.

Evaluation of Traces in SAP Solution Manager

1. In SAP Solution Manager, access the Root Cause Analysis work center.

2. Choose End-To-End Analysis.

3. Select the query that contains all systems involved within the E2E Trace and select all systems.

4. Choose Trace Analysis to open a new window with the E2E Trace Analysis application

5. Select the trace from the list.

6. If you want the SMD to collect corresponding server side trace data, choose Select systems for trace

collection dynamically.

NOTE

This starts trace data collection and results in a list of success or error messages. If you forgot

to enable tracing or wait too long between trace recording and trace data collection (for

example, more than one day), trace data may not be found.

7. Select the first step of the recorded E2E Transaction Trace and choose Display.

8. Select the Summary tab if it is not selected.

6 Troubleshooting


2010-09-17 PUBLIC 65/80

9. Select the Message table tab.

10. Expand the tray Server Analysis and choose the Request tree tab.

11. Choose Expand all to see incoming http calls, outgoing DOTNET Connector calls, and incoming

RFC calls, then do one or more of the following:

■ To view Introscope Transaction Trace data, select a line with incoming http calls, then choose

Display Introscope Transaction Trace.

■ To view ABAP Trace data, select a line with incoming RFC calls, then choose Display aggregated

ABAP Trace.

■ To view ABAP SQL Trace data, select a line with incoming RFC calls, then choose Display ABAP

SQL Trace Summary.

Verifying the DotNet Agent of the Planning and Consolidation Server is Online

As a prerequisite for the automatic trace collection, make sure that the DotNet Agent of the Planning

and Consolidation server is online.

1. Choose Workstation New Investigator .

2. Drill down to Super Domain and locate the hostname of the .NET server.

3. When the DotNet Agent of the Planning and Consolidation server is online, the node DotNet

Process appears.

4. If the node DotNet Process does not appear, the W3WP process of the Planning and Consolidation

server may have shut down. Trigger an action on the Planning and Consolidation server such as

connecting the Admin Client to the server. After this, the node DotNet Process should appear.

More Information ■ Logging and Tracing Configuration [external document]

■ Log and Trace File Management (in the application help in the SAP Library at http://help.sap.com)

6.7 Logging and Tracing Configuration

You can create log and trace files for troubleshooting purposes. You can view the log and trace files in

the Log Viewer tool of Solution Manager diagnostics after performing the configuration described

below.

You can create log and trace files for both the client server and the .NET servers.

6.7.1 Logging and Tracing Parameters

Logging and tracing parameters use aconfiguration file named log-configuration.xml. This file is

predelivered, with the same content, for both the Client and .NET servers.

6 Troubleshooting


66/80 PUBLIC 2010-09-17

http://help.sap.com

Features

The Log Configuration File

As delivered, this file contains the following statements:

SYNTAX

<?xml version="1.0" encoding="utf-8"?> <LogTraceConfig>  <TraceSeverity value="ERROR" /> <TraceDestination value="" /> <TraceFileCount value="10" /> <MaxTraceSize value="10" /> <TraceUser value="" />  <LogSeverity value="INFO" /> <LogDestination value="" /> <LogFileCount value="10" /> <MaxLogSize value="10" />  <AppSet value="" /> </LogTraceConfig>

The following sections explain the meanings of the components of each part of the log-

configuration.xml file.

Trace Settings

The following table explains the parameters of the Trace Setting part of the log-


ParameterDefault Value Meaning

TraceSeverity ERROR You use the trace severity to control the number of trace records that are produced.The following trace severity levels are supported: ■ DEBUG ■ PATH ■ INFO ■ WARNING ■ ERROR ■ DONOTHINGChoosing a severity level means that trace records with the chosen severity, together with all more. severe trace records, are written to the trace file. For example, choosing INFO means that all information, warning, and error trace records are written to the file.DONOTHING is a special severity level. If you set it as value, no trace records are written to file. This is effectively switching off Trace.

6 Troubleshooting


2010-09-17 PUBLIC 67/80


If you set another value for TraceSeverity, for example, ERR, it is treated as DONOTHING.

TraceDestination Empty The location where you want to store the trace files. For example, <TraceDestination value=“C:\Program Files\SAP BusinessObjects\PC_NW

\Logging\Trace”>.

MaxTraceSize 10 The maximum size of single trace file. The unit is MB.

TraceFileCount 10 Trace files are named BPCtrace.x.logwhere x is a number between 0 and one less than the TraceFileCount.The first trace file to be written is BPCtrace.0.log. When this file reaches the MaxTraceSize, the next file, BPCtrace.1.log, is started. This continues until there are TraceFileCount trace files, whereupon the system overwrites BPCtrace.0.log.

TraceUser Empty The default means that the system writes trace records for all users. You can also create trace records for a specified user.

Log Settings

The following table explains the parameters of the Log Setting part of the log-configuration.xml

file.


LogSeverity INFO You use the log severity to control the number of trace records that are produced.The following log severity levels are supported: ■ INFO ■ WARNING ■ ERROR ■ DONOTHINGChoosing a severity level means that trace records with the chosen severity, together with all more. severe log records, are written to the log file. For example, choosing INFO means that all information, warning, and error log records are written to the file.DONOTHING is a special severity level. If you set it as value, no log records are written to file. This is effectively switching off Logging.If you set another value for TraceSeverity, for example, ERR, it is treated as DONOTHING.

LogDestination Empty The location where you want to store the log files. For example, <TraceDestination value=“C:\Program Files\SAP BusinessObjects\PC_NW\Logging\Log”>.

MaxLogSize 10 The maximum size of single log file. The unit is MB.

LogFileCount 10 Log files are named BPClog.x.logwhere x is a number between 0 and one less than the LogFileCount.The first log file to be written is BPClog.0.log

6 Troubleshooting


68/80 PUBLIC 2010-09-17


. When this file reaches the MaxLogSize, the next file, BPClog.1.log, is started. This continues until there are LogFileCount log files, whereupon the system overwrites BPClog.0.log.

Application Set Settings

The following table explains the parameters of the Application Set Setting part of the log-


Parameter Default Value Meaning

AppSet Empty This parameter is no longer used.

6.7.2 Client Configuration

At installation, all the configuration items in the log-configuration.xml file have their default values.

This section contains some considerations when configuring this file.

Features

Trace and Log File Destination

The defaults for TraceDestination and LogDestination are empty fields. If Planning and

Consolidation detects these empty fields at user logon, it uses <TraceDestination value="C:\Program

Files\SAP BusinessObjects\PC_NW\Logging\Trace" /> and <LogDestination value="C:\Program

Files\SAP BusinessObjects\PC_NW\Logging\Log" />.

Frequent Tasks

The following table details some frequent trace and log configuration tasks:

Task How To

Change the location of the trace or log files Change the value of TraceDestination or LogDestination.

Change the number log or trace records Change the value of TraceSeverity or LogSeverity.

Switch off log or trace Set the TraceSeverity or LogSeverity to DONOTHING.

Configuring log-configuration.xml

To change the log-configuration.xml, open the file with a text editor such as Notepad,

make and changes and save the file back to the same location.

6 Troubleshooting


2010-09-17 PUBLIC 69/80

6.7.3 .NET Server Configuration

At installation, all the configuration items in the log-configuration.xml file for the .NET server have

their default values. This section contains some considerations when configuring this file.

Features

Location of log-configuration.xml

If you have a cluster of .NET servers, you may want to use the same logging and tracing parameters for

all servers by letting them all use the same log-configuration.xml file. You can specify the location

of this file in ServerConfiguration.config, which contains the following statement:

<LogTraceConfig path=" "/>

The path is initially empty so you can specify the path to where you have put log-

configuration.xml.

If Planning and Consolidation encounters a path that is empty, it assumes that log-

configuration.xml is in the same location as ServerConfiguration.config and completes the value

of the path as follows:

<LogTraceConfig path="<drive>\Websrvr\Web\log-configuration.xml"/>

Configuring log-configuration.xml

In the Server Manager

Open the Server Manager and choose Server Maintain Log/Trace Configuration . In the Maintain Log/Trace

Configuration window, you can maintain the values of the following log and trace parameters:

■ Trace File Count

■ Max Trace Size

■ Log File Count

■ Max Log Size

If you need to change the log and trace destinations, you can edit log-configuration.xml directly.

NOTE

You can also input a value for Application Set but this has no effect.

In Administration for the Web

In Administration for the Web, choose Set AppSet Parameters. Here, you can maintain the values of the

following log and trace parameters:

■ LOGLEVEL

■ TRACELEVEL

■ TRACEUSER

Any update that you make here are automatically reflected in log-configuration.xml.

6 Troubleshooting


70/80 PUBLIC 2010-09-17

NOTE

LOGLEVEL is also stored both in the ABAP table UJA_USER_DEF. In this way, the ABAP server

can share the same logging level to record logs (transaction code SLG1). For this reason, you should

not update the value of LOGLEVEL by editing log-configuration.xml because this would not

update the ABAP table.

6.8 Troubleshooting Transport

Transports allow you to move an application set across a landscape. For example, you can transport

an application set from a development environment to a test environment and then to a production

environment.

For detailed information about how to use SAP transports, refer to Transport Management [page 43].

Features

The following are some specific situations where you may require some additional information or

troubleshooting assistance.

Deleting Objects

The two major object types exhibit different behavior patterns during the import of a transport into

the target system.

■ Table entries and data model objects (application, dimensions, properties) are deleted in the target

system when they are deleted in the development system and the application set is transported.

■ Files such as script logic and Excel templates are only updated. that is, changes to these files are

transported. Since only updates are transported, deleting files in the development system does not

impact existing files in the QA or production systems. Similarly, deleting files in the target system

does not cause any harm.

Transporting Specific Objects within an Object Type

Currently, this is not supported.

However, if you have a requirement for copying files, such as reports, and input schedules, to other

Planning and Consolidation systems, you can use the program ZUJF_COPY_FILES_TO_TARGET_SYS in

transaction SE38.

Choosing Transport Strategies

There are many SAP transport strategies. Frequently, a QA or production system is built with every

released transport from the development system.

6 Troubleshooting


2010-09-17 PUBLIC 71/80

RECOMMENDATION

We recommend that you build Planning and Consolidation systems with the last good transport.

Since the Planning and Consolidation transport framework can gather all application set objects,

the fear of missing something can be alleviated.

We also recommend that, after going live, changes are always made in the development system

and transported from there to the QA and production systems.

Changing the Data Model

Do not change the data model in target systems. A typical system landscape may contain development,

QA, and production instances. If you change objects in a target system, the transports that originate

from development will no longer import correctly.

Data model changes consist of objects such as application set, application, dimensions, or properties.

A customer can maintain the data model in the QA or production system, but this means that the

customer cannot use the transport framework since it will no longer import properly.

Other components, such as reports, input schedules, or data manager packages (not data model

related), can be changed in any instance.

Changing Data Model Objects

Do not change the structure or definition of Planning and Consolidation related data model objects

in BW. This includes objects such as application set (InfoArea), application (lMultiprovider and

InfoCube), dimensions (InfoObjects), and properties (InfoObjects). This causes subsequent transports

to fail.

Changing Technical Names

The technical name of the InfoCube or Multiprovider may change between landscapes. This is normal.

Planning and Consolidation does not transport technical names of cubes and the transport works well.

Transport Failure Solutions

The following table highlights some typical installation and transport failure scenarios and solutions.

Scenario Solution Actions

Installation failed with the error No content objects found

1. Enter transaction code RSOCONTENT2. Ensure that System is a Content Development System is not selected

Import failed with RFC errors Check SAP Note 1329651

Import or installation failed with error: Import still running, or UJT_TRANS_OBJ

1. Enter transaction code SE16 for table UJT_TRANS_OBJ2. Delete all the P version records for your application set in this table3. Reimport the request

6 Troubleshooting


72/80 PUBLIC 2010-09-17


Scenario Solution Actionsversion 'P' for AppSet is

filled

Import failed with the error: Failed to create BI

InfoObject for dimension

1. Enter transaction code RSA12. check if there are any customer-created InfoObjects or InfoCubes that

refer to the attributes of the failed dimensionIf so, break the references between Planning and Consolidation InfoObjects and your InfoObjects and InfoCubes.

3. Reimport the transport request

Import failed with the error: Dimension /CPMB/XXXX

already exists

Check if anyone has transported this dimension through the BW back end manually. If so, perform the following steps:1. Delete the InfoObjects in the BW back end (use transaction code RSD1) on

the target system2. Reimport the transport request

Import failed with the error: Failed to create infoarea

1. Enter transaction code SE062. Change the namespaces /CPMB/ and /B28/ to be modifiable3. Reimport the transport request

More Information

SAP Note 1415296.

You can also check SAP notes under the application area: EPM-BPC-NW-TRA Transport.

6 Troubleshooting


2010-09-17 PUBLIC 73/80


7 Support Desk Management

7.1 Remote Support Setup

The SAP Support team supports you throughout the entire lifecycle of your solutions, from the business

blueprint through configuration to production operation. It provides central access to tools, methods,

and preconfigured content that you can use during the evaluation, implementation, and productive

operation of your systems. SAP can provide remote support for your Planning and Consolidation

implementation using the following components:

■ SAProuter: SAProuter is an SAP program that acts as an intermediate station (proxy) in a network

connection between SAP systems, or between SAP systems and external networks. SAProuter

controls the access to your network (application level gateway), and, as such, is a useful

enhancement to an existing firewall system (port filter). SAProuter runs on the firewall host serving

and serves as the entry point to your network. SAProuter can be used to open a support connection

from SAP to your SAP system. SAP support personnel can use the connection use to access your

system. SAProuter controls and monitors these connections. You must specifically grant access

to the requestor for each connection. For more information about SAProuter, see the following

SAP Notes: 1072324 and 812732.

■ SAP Service Desk: You can use the Service Desk component to process your internal support

messages. You can forward these messages to SAP Support. In this scenario, your internal support

desk acts as the first level of Planning and Consolidation support and escalated tickets go directly

to SAP Support. For more information about the Service Desk, see https://service.sap.com/

runSAP RunSAP Roadmap Access Roadmap Design Operations End User Support Concept Incident

Management .

7.2 CA Wily Introscope Integration

To enable application analysis (including performance monitoring), CA Wily Introscope (IS) is

integrated into SAP Solution Manager Diagnostics (SMD). SAP provides CA Wily IS instrumentation

for SAP Planning and Consolidation.

IS for Microsoft .NET is an application management solution for managed .NET applications, running

on Microsoft’s Common Language Runtime (CLR) environment. CA Wily IS offers Dashboards for


7.1 Remote Support Setup

2010-09-17 PUBLIC 75/80



https://service.sap.com/runSAP

https://service.sap.com/runSAP

performance and stability analysis. In addition, the Investigator provides a detailed view on all

applications and environment metrics reported by the IS agent to the IS Enterprise Manager, which is

the CA Wily IS server and part of SAP Solution Manager. User-specific interaction can be traced in CA

Wily IS using the Transaction Trace.

Metrics, which are collected and reported through tracers defined in Probe Builder Directives .pbd

files, define the information that is collected at runtime. The CA Wily IS .NET agent collects this

information and reports it to the Enterprise Manager. The Enterprise Manager stores these metrics in

its own database. You can view performance metrics using the IS Workstation or the IS WebView

application.

Prerequisites

To enable IS for Planning and Consolidation, install and configure the CA Wily IS .NET agent on the

SAP Planning and Consolidation application server hosts.

For more about information about setting up and configuring CA Wily Introscope for SAP Planning

and Consolidation, refer to SAP Note 1126554 as well as SAP Note 797147 and its attached FAQ document.

For more information about the installation, configuration, and use of SAP Solution Manager

Diagnostics, visit the SAP Service Marketplace at http://service.sap.com/diagnostics.

Procedure

1. Log on to Root Cause Analysis workcenter of SAP Solution Manager (transaction code

solman_workcenter).

2. Select System Analysis from the detail navigation menu. Choose the query that contains the SAP

Planning and Consolidation system or find it in All Technical Systems.

3. Select the SAP Planning and Consolidation system from the systems selection table.

4. Choose CA Wily Introscope and log on to the CA Wily IS WebView.

5. Choose Start Introscope, then log on to the Introscope WebView.

6. Do any of the following:

■ Select the Console tab to view Wily Dashboards.

■ Select the Investigator tab to view the Wily Investigator tree.

■ Select the Transaction Viewer tab to view Wily Transaction Trace.

7.3 Problem Message Handover

Problem messages can be logged at SAP Support Portal on SAP Service Marketplace, which is located

at http://service.sap.com/.

You use component strings to efficiently direct your support message.



76/80 PUBLIC 2010-09-17



http://service.sap.com/diagnostics

http://service.sap.com/

NOTE

It is not necessary to use component strings to use the support portal. However, they can reduce

processing time, since their use removes the need for SAP Support to dispatch your message to

the appropriate support personnel.

The following component strings are available:

Component String Area

EPM-BPC-NW Planning and Consolidation as a whole

EPM-BPC-NW-DOC Documentation

EPM-BPC-NW-PPT Interface for Powerpoint

EPM-BPC-NW-SVM Server Manager

EPM-BPC-NW-TRA Transport

Administration: EPM-BPC-NW-ADM


EPM-BPC-NW-ADM-APP Application Management

EPM-BPC-NW-ADM-DIM Dimension Management

EPM-BPC-NW-ADM-K2 K2 Script Logic

EPM-BPC-NW-ADM-SEC Security

EPM-BPC-NW-ADM-TDL Table Driven Logic

EPM-BPC-NW-ADM-WS Work Status

Data Manager: EPM-BPC-NW-DM


EPM-BPC-NW-DM-PAC Package Management

EPM-BPC-NW-DM-RUN Package Execution

EPM-BPC-NW-DM-SCH Schedule

Interface for Excel: EPM-BPC-NW-EXC


EPM-BPC-NW-EXC-CMT Comment

EPM-BPC-NW-EXC-EV EV Functions

EPM-BPC-NW-EXC-INP Input Schedule

EPM-BPC-NW-EXC-JRN Journals

EPM-BPC-NW-EXC-RPT Report

Installation: EPM-BPC-NW-INS



2010-09-17 PUBLIC 77/80


EPM-BPC-NW-INS-NET .NET Installation

EPM-BPC-NW-INS-NW ABAP Installation

Interface for the Web: EPM-BPC-NW-WEB


EPM-BPC-NW-WEB-ADM Web Admin

EPM-BPC-NW-WEB-CNT Content Library

EPM-BPC-NW-WEB-REP Live Reporting

EPM-BPC-NW-WEB-STA Getting Started

Interface for Word: EPM-BPC-NW-WRD


EPM-BPC-NW-WRD Microsoft Word (general)

EPM-BPC-NW-WRD-SR Send/Retrieve

EPM-BPC-NW-WRD-OTH Other



78/80 PUBLIC 2010-09-17

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

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

sap businessobjects planning and consolidation 7

Documents