011000358700000483512011 e

Administrator's GuideSAP BusinessObjects Planning and Consolidation 10.0version for SAP NetWeaver

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

CUSTOMERDocument version: 1.41 – 2014-01-10

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

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

www.sap.com

© Copyright 2013 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/58 CUSTOMER 2014-01-10

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

2014-01-10 CUSTOMER 3/58

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 administrator's

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

instguidesEPM-BPC 10.0, version for SAP NetWeaver .

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

Version Date Description

1.0 2012-04-23 Version 1.0 to accompany GA release

1.1 2013-01-07 Added a list of objects that support transport deletion to the topic Transport Deletion [page 38].

1.2 2013-04-30 Updated the topic “Important SAP Notes” with the central note number for support package 10.

1.3 2013-05-07 Added more objects that support transport deletion to the topic Transport Deletion [page 38].



4/58 CUSTOMER 2014-01-10

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 Setting up a Minimal-Access User to Configure SMD . . . . . . . . . . . . . . . . . . . 13

3.2 Enabling the Auto-Alert Mechanism in CCMS . . . . . . . . . . . . . . . . . . . . . . . . 14

3.3 Availability Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.4 Component-Specific Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.5 Detailed Monitoring and Tools for Problem and Performance

Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.5.1 Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.5.1.1 Logging of Exceptions in the SLG1 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.5.1.2 Trace File for Debugging Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.5.1.3 Data Manager Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.5.1.4 Trace and Log Files for Context & Insights . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.5.1.5 Trace and Log Files for Content Lifecycle Management . . . . . . . . . . . . . . . . . . 18

3.5.2 Workload Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.5.3 Data Growth and Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.5.4 Problem Analysis for CLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.5.5 Interface Monitors for CLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.5.6 Data Consistency for CLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

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

4.1 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.2 Backup Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.3 Best Practices for Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.3.1 Processing Tiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.3.2 Cube Fact Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.3.3 Cube Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.3.4 Cube Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.3.5 Writeback Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2014-01-10 CUSTOMER 5/58

4.3.6 SQE Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.4 Set Up of BPF E-mail Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.5 CLM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.6 Administration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4.6.1 Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4.6.2 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.6.3 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.6.4 Utilities for CLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.7 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.8 Scheduled Periodic Tasks for CLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.9 Scheduled Periodic Tasks for Event & Notification . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 5 Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5.1 Transport Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5.1.1 Transport Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.1.2 Transport Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.1.3 Transport Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.1.3.1 Transporting Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.1.3.2 Transport Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.1.4 Transport Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.1.5 Transport Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.1.6 Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.2 Development Requests and Development Release Management . . . . . . . . . . . 41

5.3 Quality Management and Test Management for CLM . . . . . . . . . . . . . . . . . . . 41

5.4 Support Packages and Patch Implementation . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

6.1 Troubleshooting in Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . 43

6.2 Analyzing Problems Using Solution Manager Diagnostics . . . . . . . . . . . . . . . . 43

6.3 Installing Appsight Black Box Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

6.4 Generating and Analyzing Trace Files Using E2E Trace . . . . . . . . . . . . . . . . . . 44

6.5 Logging and Tracing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.5.1 Logging and Tracing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6.5.2 Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

6.6 Troubleshooting Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

6.7 Component-Level Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

6.8 Troubleshooting for CLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.9 Troubleshooting for Event & Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6/58 CUSTOMER 2014-01-10

Chapter 7 Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

7.1 Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

7.2 Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

2014-01-10 CUSTOMER 7/58

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.

The following SAP NetWeaver documentation is relevant for Content Lifecycle Management:

Document Found At

Technical Operations Manual for SAP NetWeaver

SAP Service Marketplace at http://service.sap.com/instguides

Monitoring Setup Guide for SAP NetWeaver

SAP Service Marketplace at http://service.sap.com/instguides

SAP NetWeaver Security Guide

SAP Service Marketplace at http://service.sap.com/securityguide SAP NetWeaver

Solution Life Cycle Management by Key Capability

SAP Help Portal at http://help.sap.com SAP NetWeaver

1 Getting Started

2014-01-10 CUSTOMER 9/58

http://service.sap.com/instguides


http://service.sap.com/securityguide

http://help.sap.com

2 Important SAP Notes

CAUTION

Check regularly to see which SAP Notes are available for this Administrator's Guide.

Important SAP Notes

SAP Note Number Title Comments

1586088 SAP Planning and Consolidation 10.0 for NetWeaver Documentation Addendum

Contains information that does not appear in the application help of Planning and Consolidation 10.0, version for the SAP NetWeaver platform.

1893075 Business Planning & Consolidation 10.0 NW SP12 Central Note

This note contains installation information, enhancements, and resolved issues for SAP Planning and Consolidation 10.0 SP12, version for the SAP NetWeaver platform.
















2014-01-10 CUSTOMER 11/58










SAP Note Number Title Comments










12/58 CUSTOMER 2014-01-10





3 Monitoring of Planning and Consolidation

You use the monitoring capabilities of SAP NetWeaver to monitor Planning and Consolidation.

Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions.

The aim of this section is to provide information and documentation to monitor the application, for

example by utilizing the Computing Center Management System (CCMS) and NetWeaver ABAP

monitoring tools.

RECOMMENDATION

Since the application is powered by SAP NetWeaver 7.30, we recommend that you set up the

monitoring infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver on SAP

Service Marketplace at http://service.sap.com/instguides.

This contains all the information relevant to monitor the SAP NetWeaver components used in the

application.

Proficient knowledge of system monitoring and basic knowledge of SAP NetWeaver is required to

compose user-defined monitors. For more information about monitoring in the CCMS, see SAP Help

Portal at http://help.sap.com SAP NetWeaver .

Monitoring for Content Lifecycle Management

By default, CCMS monitoring capabilities are restricted to the local system and as CLM involves

interactions with more than one system in a typical landscape, it could be beneficial to monitor other

systems through CCMS from central CLM system.

In this case, CLM, as the central monitoring system can be configured to link CCMS monitoring from

application systems. Since currently CLM only communicates with ABAP-based systems, RFC

connection type can be used to enable monitoring across multiple systems.

3.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.


3.1 Setting up a Minimal-Access User to Configure SMD

2014-01-10 CUSTOMER 13/58


http://help.sap.com

Procedure

1. Log on to the EnvironmentShell environment through the Admin client.

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

3. In the Users view, select Add. In the Add User assistant, select the user to add in the environment

4. Choose Next at all remaining steps of the assistant without assigning the user to a team.

5. Choose Finish.

6. In the Users, check that the user has no teams or profiles assigned to it. Select the user and choose

Edit. This displays details of the team, task profile and data access profile assignments for the user.

7. 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.2 Enabling the Auto-Alert Mechanism in CCMS

The basis for application-specific alert monitoring is NetWeaver CCMS alert monitoring framework.

To enable the auto-alert mechanism of CCMS, see the following SAP Note:

SAP Note Number Title Comment

617547 RZ20: Sending alerts as mail and SMS You want to send alerts from the CCMS monitoring architecture (transaction RZ20) as an e-mail, SMS or other message type to one or several recipients.

3.3 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.

Features

In the Central Monitoring System (CEN) you can load the Planning and Consolidation template

customizing file and start the GRMG scenario to monitor availability of the application server.

NOTE

For availability monitoring, set up and use a Planning and Consolidation user with minimal access

privileges for monitoring and diagnostics related web services, such as GRMG web services. For

more information, see Setting up a Minimal-Access User to Configure SMD [page 13].

To configure the GRMG scenario for Planning and Consolidation, perform the following steps:

1. Using a suitable XML editor, edit the template customizing file BPCNW_Customizing.xml. You must

specify the URL of the scenario (host and port), as well as the username and password.

2. Save your entries.


3.2 Enabling the Auto-Alert Mechanism in CCMS

14/58 CUSTOMER 2014-01-10


3. Log on to the Central Monitoring System (CEN).

4. Go to transaction GRMG. To do that, in the execution text field in the upper left corner, enter /

nRZ20 and press Enter.

5. Choose Upload and select the relevant scenario.

6. Once the scenario is uploaded, to verify the content is correct, choose Edit/Delete.

7. Choose Start.

3.4 Component-Specific Monitoring

Existing CCMS monitoring sets can be used to monitor various resources, objects, and performance.

For example, SAP CCMS monitor template, which can be used to monitor system, database, and

background processing for the application server where the application is running.

The following existing monitors within RZ20 can be used by the application to monitor critical

conditions:

Database Monitoring

You can monitor the RDBMS connection using the CCMS database monitor. This is the connection

to the system where the application is installed and in use.

Operating System Monitoring

Operating system monitoring capabilities within CCMS administration workplace are used to analyze

CPU, memory, paging, disks, file system, and their corresponding health statuses.

Dialog Overview

Using dialog monitoring in RZ20, the response time for dialog, network time, and number of currently

logged-in users can be observed.

Error Monitoring

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

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

log. If errors occur in this log, you can display them in transaction CCMS by selecting Open Alerts.

Monitors for Content Lifecycle Management

Dialog Overview

For CLM, you can observe Web Dynpro ABAP-related attributes such as date transferred, session

timeouts, and number of roundtrips against CLM Web Dynpro application /POA/WD_CLM. This view

is also part of the delivered CLM-specific Content Lifecycle Management Monitor Set.

Background Processing

For extraction and deployment scenarios in CLM, background jobs are created for a content group.

CCMS view for background processing under Content Lifecycle Management Monitor Set can be used

to retrieve statistics such as a list of long-running background jobs, number of free or occupied work

processes, and any CLM job that was stopped abruptly.


3.4 Component-Specific Monitoring

2014-01-10 CUSTOMER 15/58

NOTE

Transaction SM37 can be used to monitor background jobs initiated by CLM.

3.5 Detailed Monitoring and Tools for Problem and Performance Analysis

This section describes the trace and log files, and monitors that you can use for detailed monitoring.

These are useful for problem and performance analysis.

3.5.1 Trace and Log Files

The following table describes the trace and log files for the application components.

Component Content File Path

Core components and services

Log messages pertaining to workflow (alerts, fatal messages, errors, status updates). Messages are also shown in the common message region in the top-right corner of the container. Traces are enabled through log message APIs

Log messages on client side are in memory. There is an option to export the messages to the server. These messages are for viewing and analyzing in the administrator tool for the application

N/A

- System Trace Analysis — RFC, HTTP, DB

- Transaction ST01

- SQL Performance Trace and Analysis — RFC, HTTP, DB

- Transaction ST05

All logs related to runtime exceptions are recorded.

■ Check BUI log in SLG1

3.5.1.1 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.

EXAMPLE

The following script refers to an invalid member, A1000:

*XDIM_MEMBERSET ENTITY=A1000

*WHEN TIME



16/58 CUSTOMER 2014-01-10

*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.5.1.2 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

\<environment>\<model>\privatepublication\<username>\<date>.

3.5.1.3 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.

These logs are stored in <Drive>\webfolders\<environment>\<model>\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.5.1.4 Trace and Log Files for Context & Insights

Component Content File Path

Context REST Details about errors and exceptions in the communication with client

- /POA/CTX/REST

Context Service Details about errors and exceptions occurring within the context server

- /POA/CTX/SERVICE



2014-01-10 CUSTOMER 17/58

3.5.1.5 Trace and Log Files for Content Lifecycle Management

Content Lifecycle Management (CLM) does not provide any special tracing and log files facility as this

can be easily obtained from the NetWeaver ABAP framework.

It is essential to collect trace and log files for RFC calls. CLM carries out critical operations through

RFC protocol to extract and deploy the contents onto application systems.

3.5.2 Workload Monitors

A default workload collector as part of CCMS monitoring and workload monitor through transaction

ST03N can be used to observe the workload records at application server level.

Component Monitor Detailed Description Prerequisites

- Workload Monitor — Transaction ST03N

Detailed analysis of workload of application servers

-

3.5.3 Data Growth and Archiving Monitors

Component Monitor Detailed Description Prerequisites

DB tables ST05 Observe critical operations and tables that take more time along with their hit and miss ratio

Switch the trace on before performing costly operations

Some of the intensive database tables that can be viewed during critical long-running operations:

■ /POA/D_XML_VALS — Resource Value (XML) for persistence service

■ /POA/D_TRN_PAYL — Resource Value texts for persistence service

Some of the CLM database tables that can be viewed during critical long-running operations:

■ /POA/D_CLM_CP02 — CLM Content group and Entity relationship

■ /POA/D_CLM_DPLR — Table for storing entity processing messages

■ /POA/D_CLM_ENT01 — CLM Entity Table

■ /POA/D_CLM_ENT02 — CLM Entity Fields value Table

■ /POA/D_CLM_ENT03 — CLM Entity — Entity Relationship

■ /POA/D_CLM_ENT10 — CLM Entity Raw Data Extract Table

3.5.4 Problem Analysis for CLM

The monitoring sets from CCMS monitoring in RZ20 can help analyze most critical bottlenecks;

however, the following table points to some problem-oriented scenarios and a recommended tracking

mechanism for CLM:



18/58 CUSTOMER 2014-01-10

CLM Scenario/Activity Problem Possible Causes Recommended Monitoring

Extraction of content from application system

Exception Occurred RFC connection failure, system failure, no authorization for RFC calls

Check system trace file (ST01)/ SM59 / SMT1 for trusted connections. CLM log in SLG1

Extraction in progress for a long time

Large amount of content Check background task in SM37 and CCMS CLM monitor

Validation errors Content in incorrect format

SLG1 – application log for CLM

Importing content from a CLM package (zip)

Exception occurred Malformed content or tempered content format

SLG1 – application log for CLM

Time out Package size is too big Check CCMS memory or buffer sizes to free resources, increase time out limits for profile parameters; usually cannot be resolved

Exporting CLM content to a package (zip)

Exception occurred Content was changed after including in package

SLG1 or check status of content group

- Time out Content size is too big Remove huge attachments, split package into two smaller packages

Deploy Content Exception occurred Incompatible system for application deployment of content, RFC connection failure, system failure, no authorization for RFC calls, no trusted system

SLG1 – application log for CLM, system trace file (ST01), SMT1 for trusted connections

Deployment takes too long

Large amount of content SM37 or CCMS for CLM deployment and polling results background job

Non recognized status in deployment log

Failure on application deployment

Check target application system, ST22, for any exceptions, authorization failures

No deployment possible Existing deployment on target system already on going

Check DB locks in SM12 (table /POA/S_CLM_DEPLKEY)

3.5.5 Interface Monitors for CLM

Content Lifecycle Management (CLM) communicates with application system using RFC. For certain

intensive operations, such as content extraction, interface monitors could be used to analyze the time

spent on each RFC call.



2014-01-10 CUSTOMER 19/58

InterfaceDetailed Description Technology Used

You configure APIs and RFC functions in Customizing for Content Lifecycle Management under Maintain System Registry API Groups .

ABAP Web Dynpro application uses these calls and interfaces at runtime

RFC

/POA/CLM_WD ABAP Web Dynpro application is accessed using HTTP

HTTP

3.5.6 Data Consistency for CLM

Content Lifecycle Management (CLM) is used as a repository containing application content. The

content in the CLM repository can be added either by extraction from various application systems or

by importing a new vendor-delivered package. During these operations CLM always loads the data first

and performs validations on top of such content to report functional inconsistencies. If there are abrupt

blockages, such as connection timeout, it can result in differences between the data maintained in CLM

and data present in other sources.

RECOMMENDATION

In this scenario, we recommend rerunning the operation as there is no impact of this operation

on any business function in CLM.



20/58 CUSTOMER 2014-01-10

4 Management of Planning and Consolidation

4.1 Starting and Stopping

The following table describes the sequence for starting and stopping the application.

Software Component Start and Stop Sequences and Tools

- Sequence Tool Detailed Description

Software Component: POASBC

1 Example: STARTSAP STARTSAP (UNIX)SAP Management Console

The application is based on SAP NetWeaver infrastructure. For more information, see the Technical Operations Manual on SAP Help Portal at http://help.sap.com SAP NetWeaver .

4.2 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.3 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 model

■ Number of concurrent users

■ Hardware

■ Network bandwidth


4.1 Starting and Stopping

2014-01-10 CUSTOMER 21/58

http://help.sap.com

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.3.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

BI Accelerator (optional component)

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

4.3.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).

4.3.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 Administration section in the application help.

4.3.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



22/58 CUSTOMER 2014-01-10

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

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

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

parameters.

4.3.5 Writeback Parameters

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

individual model 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 of records multiplied by 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.3.6 SQE Parameters

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

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

following table:

Parameter Default Description

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.



2014-01-10 CUSTOMER 23/58

4.4 Set Up of BPF E-mail Notifications

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

Prerequisites

Environment 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.

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%

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.


4.4 Set Up of BPF E-mail Notifications

24/58 CUSTOMER 2014-01-10

4.5 CLM Configuration

The following table describes the tools for configuring Content Lifecycle Management.

Component Configuration Tools Detailed Description

Content Lifecycle Management (Software Component POASBC)

Customizing — this the standard SAP tool for ABAP-based system used for component Customizing. Access it through transaction SPRO

Technical configuration: Mainly for configuring application systems and the APIs with which CLM interacts

Content Lifecycle Management (Software Component POASBC)

SAP Solution Manager SAP Solution Manager is the standard SAP tool for process and scenario-based configuration.

For more information about SAP Solution Manager, see the following SAP Note:


1230438 Solution Manager Content for SAP SRM 7.0 Additional information for using Solution Manager Content

Changing Flex Client Platform (FCP) Configuration Using Transaction (Recommended)

1. Log on to ABAP system. Execute the transaction in a new window – ‘/o/poa/sfcpconfig’.

2. Change the values in the Configuration Value column and choose Enter.

3. Optional: To troubleshoot, you can also check whether the values have changed by looking into

the database table (/poa/config_info) directly, before you exit.

4. Exit the transaction.

Platform Parameters That Can Be Set As Part Of Application Configuration

1. pp-support-mode

Expected value – true/false; default value – false

Purpose:

When set to true, the support information is displayed in the context menu on the client. This

displays details about the loaded bundles on the client. All other support information can also be

accessed by enabling this parameter.

Platform Parameters That Can Be Set As Part Of Application Configuration – Could Influence

Client‘s Behavior

1. pp-enable-lazy-loading


Purpose:

This is a kind of central switch to turn ON/OFF the lazy loading of bundles. This configuration

overrides all the lazy loading options present in any bundle’s plugin.xml. When set to true, all the

lazy loading configurations are considered by the Flex Client Platform (FCP) client. As a result, the

bundles are loaded only on demand – when required by the application. This setting is

recommended especially for large applications as this enhances the performance. When set to false,



2014-01-10 CUSTOMER 25/58


the lazy loading configurations are ignored by the FCP client and hence all the bundles are loaded

at application startup.

2. pp-enable-trace


Purpose:

Enables display of log console on FCP client. When set to true, the client can show the log console.

With URL parameter show-trace set to true, trace console is also seen. When set to false, no log

console can be opened on the application.

3. pp-enable-debugging


Purpose:

Enables debugging on FCP client. When set to true, the debug version (‘..-d.swf’) of a plug-in is

downloaded and the FCP client can run in debug mode. To debug the URL, parameter ‘debug’

must be set to true. When set to false, application debugging is disabled. As the name suggests, the

parameter must only be enabled if debugging of the application is required.

4. pp-enable-request-batching

Expected value – true/false; default value – true

Purpose:

Helps FCP client decide whether to send single/multiple requests for a plug-in manifest. When set

to false, FCP client sends single request for every single plug-in manifest. The number of requests

depend on the number of resolved bundles for an application. When set to true, FCP client sends

a single request for plug-in manifests. This reduces the number of calls to the server and hence

increases the performance.

5. pp-support-mode


Purpose:

When set to true, the support information is displayed in the context menu on the client. The

support information displays details about the loaded bundles on the client. All future support

information can also be accessed by enabling this parameter.

6. resource-expiry-duration

Expected value – No. of days; default value – 365

Purpose:

The specified number of days are added to the current date and expiry date is the resource set

accordingly. For example, if today‘s date is Mon, April 5 2010, and you have specified 2 as resource-

expiry-duration, the ‚expires‘ in HHT header of the response is set to Wed, 07 Apr 2010 00:00:00

GMT.

7. pp-log-filter

Expected value – ERROR|FATAL|SUCCESS|WARNING|INFO|NONE|*; default value – *



26/58 CUSTOMER 2014-01-10

Purpose:

Controls the display of logs and traces in the log console. All the messages that match the level set

and below levels are filtered and displayed.

8. log-expiry-duration

Expected value – duration, in number of days; default value – 7

Purpose:

Used by logger service on ABAP server component to set the expiry date on application logs.

9. enable-server-cache

Expected value – true/false; default value – true

Purpose:

Used by FCP ABAP server component to turn on/off server cache used for storing application

configuration.

Splash Configuration

1. The splash configuration in the application configuration xml contains the bundle name that is

to be used as the splash/boot information bundle.

Application Parameters

1. Apart from the platform parameters, you can configure application-wide parameters in the

<application-parameters/> section. To configure application parameters on the server (Java/

ABAP), use the same method that is used to maintain platform parameters. The only rule is that

for a parameter to be identified as an application parameter, it must be prefixed with 'app-'.

Application Parameter Defined by FCP

1. app-http-method-override


Purpose:

HTTP client uses this configuration and if the value is true the PUT/DELETE HTTP methods are

sent via a POST request. ‚false‘ means that PUT/DELETE are sent as PUT/DELETE requests

respectively.

FCP URL Parameters That Can Be Passed to Client Platform

1. config-url

This is an optional parameter that tells the platform where to pick up the application configuration

from. This can point to a static/pre-configured XML file or to any URL that can be requested via

HTTP. By default, FCP looks for an XML file with name com_sap_tc_ui_ria_fcp_config.xml.

2. execution-scope

This is an optional parameter that can be used to filter the bundles based on the unique scope in

which a particular FCP application wants to run.

3. hide-splash



2014-01-10 CUSTOMER 27/58

This is an optional parameter that when set to true, no splash screen is displayed, instead FCP shows

a progress bar with status message, and all the configurations in the application configuration for

splash are overridden.

4. show-trace

This is an optional parameter that when set to true, the client displays the log console (depending

on the pp-enable-trace parameter).

5. debug

This is an optional parameter that when set to true, the client runs in debug mode (depending on

the pp-enable-debugging parameter).

6. app-def

This is an optional parameter that can be used to pass application-specific and static configuration

to FCP applications. It can contain additional application-related content apart from standard FCP

definitions. Note: Application definition is not able to influence platform parameters (all server

parameters starting with pp-).

7. mask-feature

This is an optional parameter that can be used to filter the bundles based on the feature scope.

8. support-mode

This parameter can be used on client side to enable/disable support information. Note that support

information is visible only when both platform parameter (pp-support-mode) and URL parameter

(support-mode) are set to true.

4.6 Administration Tools

4.6.1 Logs

The application writes logs during various activities at runtime; these can be used by administrators

for auditing and monitoring purposes.

■ Application Log: Every operation and corresponding steps carried out during that operation are

recorded in the application log:

Transaction SLG1, log objects: /POA/PST and /POA/UM

The application log includes detailed information about error messages and sequential flow with

respect to technical processing in the application.

This object includes the following subobjects or categories:

● PACKAGE: Use this subobject to monitor and analyze the logs that are specific to application

packages for /POA/PST with value AUTH, OTHER, REST and for /POA/UM with value OTHER,

REST.

Content Lifecycle Management Logs



28/58 CUSTOMER 2014-01-10

■ Application Log: Every CLM operation and corresponding steps carried out during that operation

are recorded in the application log:

Transaction SLG1, object: /POA/CLM

The application log includes detailed information about error messages and sequential flow with

respect to CLM technical processing.

This object includes the following subobjects or categories:

● PACKAGE: Use this subobject to monitor and analyze the logs specific to CLM packages (all

steps performed under Manage Packages function on CLM UI)

● CHECKPOINT: All actions performed under Manage Content Groups in CLM are recorded for

analysis under this application log subobject

● DEPLOYMENT: Application logs related to deployment from CLM are recorded under this

subobject

● TECHNICAL: Additional technical log details are recorded under this subobject.

■ Deployment Log: This is available on CLM UI. It displays statuses and messages for deployments

from CLM to the application. The deployment log provides details of application-specific messages

per deployment system and per content group.

■ Change Log or Change History: For all actions that can be carried out in CLM UI, such as editing,

deployment, import, and export. CLM logs the change history using the change documents

function of ABAP. CLM change logging is enabled for packages and content groups and related

tables. This can be seen in CLM UI with View History function.

■ Customizing object or Table Logging: All Customizing, control, and system database tables

defined in CLM are enabled for logging. Analysis of this logging can be done using SCU3 transaction

in NetWeaver ABAP system if logging is switched on.

Flex Client Platform (FCP) Server-Side Log Messages

The application log messages can be viewed on an ABAP server using transaction /POA/SFCPAPPLOG.

All the generated logs have an expiry time set and need to be deleted explicitly using transaction SLG2.

1. Connect to the ABAP system and execute transaction /POA/SFCPAPPLOG.

2. Provide the following filters:

■ Object: /POA/SFCP (Display Only)

■ Subobject: FCPAPPLOG (Display Only)

■ Optional: External ID: Category of the log message, as seen in the application log console

■ Mandatory: Time (From/To): The required interval as seen in application log console

■ Optional: User: User of the session

■ Set the default values for the remaining filters as follows:

● Transaction Code: *

● Program: *

● Log Class: All logs

● Log Creation: Any



2014-01-10 CUSTOMER 29/58

● Log Source and Formatting: Format Completely from Database

The exported log messages are grouped based on Category/External ID and displayed.

3. For more information, select extended text under Details column.

Log severity seen on the ABAP server is the same as in the application, except for 'SUCCESS' and

'FATAL' ('SUCCESS' is mapped to 'INFO', 'FATAL' is mapped to 'TERMINATION'). Problem class

is 'Very Important' for 'FATAL', 'Important' for 'ERROR', and 'Medium' for other severities.

Flex Client Platform (FCP) Server-Side Trace Messages

The application trace messages can be viewed on an ABAP Server using transaction /POA/

SFCPAPPTRACE. All the trace messages generated have an expiry time set and need to be deleted

explicitly using transaction SLG2.

1. Connect to the ABAP system, execute transaction /POA/SFCPAPPTRACE.

2. Provide the following filters:

■ Object: /POA/SFCP (Display Only)

■ Subobject: FCPAPPTRACE (Display Only)

■ Optional: External ID: Category of the trace message, as seen in application log console

■ Mandatory: Time (From/To): Required interval as seen in application log console

■ Optional: User: User of the session

■ Set the default values for the remaining filters as follows:

● Transaction Code: *

● Program: *

● Log Class: All logs

● Log Creation: Any

● Log Source and Formatting: Format Completely from Database

The exported trace messages are grouped based on Category/External ID and displayed.

3. For more information, select extended text under Details column.

Trace severity seen on the ABAP server is the same as in the application, except for 'SUCCESS' and

'FATAL' ('SUCCESS' is mapped to 'INFO','FATAL' is mapped to 'TERMINATION'). Problem class

is 'Very Important' for 'FATAL', 'Important' for 'ERROR', and 'Medium' for other severities.

Deleting Logs and Traces

All application logs and traces are generated with an expiry date and Deletion before expiry attribute set to

true. Hence all the logs and traces can be deleted before their expiry date. The expiry date for logs and

traces is calculated based on the log-expiry-duration parameter on the server.

This parameter can be configured using transaction /POA/SFCPCONFIG and specifies the number of

days for which logs can reside on the server. Default value is 7.

Obsolete logs and traces can be deleted as follows:

1. Connect to the ABAP system; execute transaction SLG2.

2. Provide the filters as follows:

■ Expiry date: and logs which can be deleted before the expiry date



30/58 CUSTOMER 2014-01-10

■ Object: /POA/SFCP

■ Subobject: FCPAPPLOG to FCPAPPTRACE

■ Options: Delete immediately

■ COMMIT Counter: 100

3. Choose Execute.

Logs can also be deleted in the background using report SBAL_DELETE. For more information, see the

following SAP Note:


195157 Application log: Deletion of logs Delete log entries from database tables of application logs

4.6.2 Load Balancing

As a web-based application, the basis for logon and load balancing is a high availability landscape setup

together with a load balanced network setup.

For more information about network load balancing, see the Technical Infrastructure Guide for SAP

NetWeaver on SAP Service Marketplace at http://service.sap.com/instguides.

A load-balanced network using SAP Web Dispatcher together with logon groups in the SAP NetWeaver

systems can be used to redirect certain users to specific application servers.

4.6.3 User Management

All scenarios and components in the application use the user management functions provided by

NetWeaver.

For more information about user administration and authentication, see the application security guide

on SAP Service Marketplace at http://service.sap.com/securityguide.

4.6.4 Utilities for CLM

Content Lifecycle Management Administrator/Developer Utilities

CLM provides utilities for testing purposes, which are intended for administrators and developer user

groups.

Application API Adapter testing: Since CLM calls the RFC function modules while communicating

with application systems, it expects a certain format and interface for these API/RFC function modules.

Moreover, an appropriate system setup is also required via system registry configuration where new

application systems and their APIs are registered. For more information, see Customizing for Content

Lifecycle Management under Maintain System Registry.

In actual scenarios or for productive usage; before you run CLM with system registry settings, it is

advisable to run the test adapter utility using transaction /POA/CLM_API_TESTER. You need to provide



2014-01-10 CUSTOMER 31/58



http://service.sap.com/securityguide

the system registry ID. The transaction checks API interfaces and also performs a test run for extraction

and deployment operations.

Cleaning up the CLM database: If you are running CLM for test purposes or on a test system, and

you find CLM database tables increasing in size over time; you can use transaction /POA/

CLM_CLEANUP to delete the CLM-specific database tables.

NOTE

This program completely deletes all CLM data and does not allow any preferences to be set for

specific entry deletion from CLM database tables. Hence it is intended to be used for cleaning up

garbage or unused data from the test CLM system only.

4.7 Backup and Restore

The following table describes methods for backup and restore for application components:

Categories of System Components

Category Properties Suggested Methods for Backup and Restore Examples

VIII Original application data, standalone system based on SAP NetWeaver Application Server

Data: ■ Database and log backup, application log backup (such

as job logs in file system) ■ Backup of software, configuration log files

Standalone SAP ERP

The following table lists the CLM components relevant for backup and recovery:

Component Data to be Backed Up Backup Method/Tool Recommended Backup Frequency

POASBC Application database tables, logs Database and log backup Yearly

4.8 Scheduled Periodic Tasks for CLM

CLM uses background jobs for the execution of some operations at runtime. The following table gives

an overview of the exact programs that are scheduled in the background and the frequency at which

these are executed.

Scheduled periodic tasks for Content Lifecycle Management:

Program Name/Task

Task-Scheduling Tool

Recommended Frequency Detailed Description

/POA/R_CLM_DEPLOY_RESULTS_POLL

Automatic 10 minutes: This can be changed in

Used to retrieve the deployment results of application content


4.7 Backup and Restore

32/58 CUSTOMER 2014-01-10

Program Name/Task

Task-Scheduling Tool

Recommended Frequency Detailed DescriptionCustomizing for Content Lifecycle Management under Maintain Technical Settings.

from target application systems. For more information, see Content Group Deployment in SAP Library documentation under Content Lifecycle Management Content Group and Package Management Content Group Deployment .

Other background tasks in Content Lifecycle Management that are scheduled to run immediately:

Program Name/Task Task-Scheduling Tool Recommended Frequency Detailed Description

/POA/R_CLM_EXTRACT Automatic Immediately when the operation is triggered

Background task during content group extraction

/POA/R_CLM_DEPLOY Automatic Immediately when the operation is triggered

Background task for content group upload and deployment

4.9 Scheduled Periodic Tasks for Event & Notification

Program Name/Task Task Scheduling Tool Recommended Frequency Detailed Description

E-mail job ABAP Every minute For more information about sending messages to e-mail, see the installation guide.

Delete expired inbox items ABAP Daily Deletes messages that have been set to expire.

Reorganize and reconciliation job

ABAP Monthly or greater Reconciliation of deleted messages in Business Workplace and event and notification.

For more information about scheduled jobs, see the installation guide.


4.9 Scheduled Periodic Tasks for Event & Notification

2014-01-10 CUSTOMER 33/58

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 environment across a landscape. For example, you can transport an

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

Two modes of transport are supported:

■ Normal mode – For modifying and creating objects. In this mode, if a transported object exists in

the target system, it is modified with the changes from the source system. If it does not exist, it is

created.

■ Deletion mode – For deleting objects. In this mode, you explicitly specify the objects to delete.

All aspects of an environment are transported except transaction data.

You can transport the changes associated with an environment without having to transport the entire

environment. You can transport one or more models at a time, and select individual components of

a model, for example, dimensions, members, logic script files, work status, reports, and so on). You can

transport the deletion of models, dimensions, Data Manager packages (deletion includes renaming,

moving and deleting a package), Data Manager package groups (deletion includes renaming and

deleting a package group) and Data Manager package links.

You can also collect NetWeaver objects into a transport request, such as NetWeaver process chains. To

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

process chains. The process chain must be assigned to component /cpmb/BPC.

The following subsections contain a description of the transport process and some other useful

information about transporting. If you have problems with transports, see Troubleshooting Transport [page

49].



2014-01-10 CUSTOMER 35/58

5.1.1 Transport Objects

This section lists the objects that you can transport for environments and models.

Environment Objects

You can transport the following objects for an environment.

■ Business Rule

■ Configuration

■ Dimension

■ Model

■ Script Logic

■ Task Profile

Model Objects

You can transport the following objects for a model.

■ Books Template

■ Business Process Flow Template

■ Business Rule

■ Business Unit

■ Configuration

■ Control

■ Data Access Profile

■ Data Manager Conversion File

■ Data Manager Data File

■ Data Manager Package

■ Data Manager Package Group

■ Data Manager Package Link

■ Data Manager Transformation File

■ Dimension

■ Dimension Master Data

■ Drill Through

■ Journal Template

■ Report File

■ Report Templates

■ Script Logic

■ Task Profile

■ Team

■ Web Documents

■ Work Status Settings



36/58 CUSTOMER 2014-01-10

5.1.2 Transport Configuration

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

SAP NetWeaver includes the Change and Transport System (CTS), which is a tool that helps you to

organize development projects in the ABAP Workbench and in Customizing, and then transport the

changes between the SAP systems in your system landscape.

For more information, see the SAP NetWeaver Technical Operations Manual on SAP Help Portal at

http://help.sap.com SAP NetWeaver .

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, as 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. Select he objects to transport.

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

5.1.3 Transport Execution

5.1.3.1 Transporting Environments

You select the objects to transport from the hierarchy of objects in the environment. This allows for

the granular selection of objects. Only the objects that you select are transported. You can transport

objects with or without corresponding dependent objects. However, if you transport an object but do

not include its dependent objects in the transport, a warning is generated.

RECOMMENDATION

We recommend that you do not add a normal transport and a deletion transport for the same

environment into one customizing request. For more information, see SAP Note 1583670.



2014-01-10 CUSTOMER 37/58

http://help.sap.com

http://help.sap.com

http://help.sap.com


Procedure

1. Logon to the source system and enter transaction code RSA1.

2. In the left column, select Transport Connection.

3. Select the objects to transport:

1. In the left column, select SAP Transport Object Types .

2. In the middle column, select More Types BPC Environment .

3. Double-click Select Objects.

4. In the dialog box, select the environment to be transported and click Transfer Selections.

5. In the right column, the objects in the environment are listed. Select the objects to be

transported by selecting or deselecting the corresponding object.

4. Generate a customizing request:

1. In the right column, click the Transport Objects button.

2. In the dialog box, click the Create Request button to generate a new customizing request, then

click the Continue button.

3. In the next dialog box, enter the description and transport target, then click the Save button.

4. Click the Continue button to generate the customizing request. The selected objects are included

into the request.

5. Enter transaction code SE09 to open the transport organizer. Click Display.

5. Release the customizing task:

1. Select the task under the customizing request you just generated.

2. Click Release directly.

Transport Errors

If transport fails for an object, the changes for that object are not made in the target system. The object

in the target system remains unchanged. This does not affect the transport of other objects to the target

system.

5.1.3.2 Transport Deletion

After an object has been deleted in the source system, you can mark it for deletion in the target system.

You can select the deleted objects to transport. However, you can select only deleted objects for which

there are no dependencies.

The following objects support transport deletion:

■ Models

■ Dimensions

■ Data Manager packages

■ Data Manager package groups

■ Data Manager package links



38/58 CUSTOMER 2014-01-10

RECOMMENDATION

We recommend that you do not add a normal transport and a deletion transport for the same

environment into one customizing request. For more information, see SAP Note 1583670.

Procedure

1. Logon to the source system and enter transaction code RSA1.

2. In the left column, select Transport Connection.

3. Select the deleted objects to transport:

1. In the left column, select SAP Transport Object Types .

2. In the middle column, select More Types BPC Deletion .

3. Double-click Select Objects.

4. In the dialog box, select the environment to be transported and click Transfer Selections.

5. In the right column, all objects in the environment which have been deleted (and which do

not have dependent objects that still exist) are listed. Select the deleted objects to be transported

by selecting or deselecting the corresponding object.

4. Generate a customizing request:

1. In the right column, click the Transport Objects button.

2. In the dialog box, click the Create Request button to generate a new customizing request, then

click the Continue button.

3. In the next dialog box, enter the description and transport target, then click the Save button.

4. Click the Continue button to generate the customizing request. The selected objects are included

into the request.

5. Enter transaction code SE09 to open the transport organizer. Click Display.

5. Release the customizing task:

1. Select the task under the customizing request you just generated.

2. Choose Release directly.

Deletion Errors

If deletion fails for an object, the changes for that object are not made in the target system. The object

in the target system remains unchanged. This does not affect the deletion of other objects in the target

system.

5.1.4 Transport Log Files

After a transport has been completed, you can view the transport log. The log reports the successful

completion of a transport request, as well as warnings and errors encountered during the transport.

Procedure

To view a transport log file:

1. Select a released request.



2014-01-10 CUSTOMER 39/58


2. Click Transport Logs.

5.1.5 Transport Maintenance

There are certain maintenance tasks involved with transports.

Features

You can use the UJT_AFTER_FAIL_PROCESS program. For more information, see SAP Note 1615644.

5.1.6 Deployment Scenarios

There are two typical landscape deployment scenarios.

Development to Production

In the Development to Production deployment scenario, you create and maintain an environment in

development. All dimensions, dimension properties, and models are created in development. A decision

needs to be made for all other objects.

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.

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

environment 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 environment. For

example, they may have a configuration that has Production support changes and another

configuration on the same model or environment that is transported at a later stage in the project

cycle.

In this case, you should have two environments in development, one for new development, and one

for production support changes. When a production support change occurs, this should be done in

both environments in development. When the cutover of new development needs to be transported,

then the configuration can be moved to the production support environment and transported.



40/58 CUSTOMER 2014-01-10


5.2 Development Requests and Development Release Management

The transport workflow provides a framework for transporting enhancements or new developments

of existing business functions in a system landscape.

It is an efficient method of transporting a selected number of requests into a group of transport targets,

and uses clearly defined approval steps to ensure the quality of your target systems.

For more information, see the Technical Operations Manual on SAP Help Portal at http://

help.sap.com SAP NetWeaver .

5.3 Quality Management and Test Management for CLM

All CLM interfaces can be tested automatically through the eCATT/Test Workbench.

5.4 Support Packages and Patch Implementation

Information on the support packages (SPs) available for Content Lifecycle Management can be found

in the Release Information Notes (RIN) for each SP.

Support packages for components based on the SAP NetWeaver Application Server (ABAP) (such as

CLM) are applied using the Support Package Manager.

Detailed instructions about applying a support package stack to SAP NetWeaver are given in the SAP

NetWeaver Support Package Stack guides on SAP Service Marketplace at http://service.sap.com/

instguides.

SAP Notes that require code changes for components based on the SAP NetWeaver Application Server

(ABAP) can be applied using the SAP Note Assistant. For more information, see http://

service.sap.com/note-assistant.


5.2 Development Requests and Development Release Management

2014-01-10 CUSTOMER 41/58

http://help.sap.com

http://help.sap.com



http://service.sap.com/note-assistant

http://service.sap.com/note-assistant

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.

6.2 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 in the Planning and Consolidation NW Installation Guide.

6.3 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.

6 Troubleshooting

6.1 Troubleshooting in Planning and Consolidation

2014-01-10 CUSTOMER 43/58


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.4 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 [page 46].

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.

■ The minimum release on the SAP Solution Manager Diagnostics side for E2E Trace Analysis is

Solution Manager 7.0 EhP 1 SP23.

6 Troubleshooting


44/58 CUSTOMER 2014-01-10

Procedure

Generating and analyzing trace files using E2E Trace involves the following tasks, which are described

below:

■ 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

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 Microsoft Excel Module

1. Launch the E2E Plug-In by running plugin-starter-gui.exe.

2. Select Microsoft Office Excel and choose Launch.

3. After Excel is launched, 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.

4. Click Log On in the EPM menu in Excel.

5. Choose Start Transaction in the E2E Trace Plug-in user interface, then choose OK to log on to the

Excel 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 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.

6 Troubleshooting


2014-01-10 CUSTOMER 45/58

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.

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.

More Information

■ Logging and Tracing Configuration [page 46]

■ Log and Trace File Management (in the application help in the SAP Library at http://help.sap.com)

6.5 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 the client.

6 Troubleshooting


46/58 CUSTOMER 2014-01-10

http://help.sap.com

6.5.1 Logging and Tracing Parameters

Logging and tracing parameters use a configuration file named log-configuration.xml. This file is

predelivered for the client.

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


2014-01-10 CUSTOMER 47/58


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. 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.

6 Troubleshooting


48/58 CUSTOMER 2014-01-10

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.5.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.6 Troubleshooting Transport

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

environment 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 35].

Features

The following are some specific situations where you may require some additional information or

troubleshooting assistance.

6 Troubleshooting


2014-01-10 CUSTOMER 49/58

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 (model, dimensions, properties) are deleted in the target

system when they are deleted in the development system and the environment 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.

After deleting an environment, 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

environment.

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.

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 environment 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 environment, model, 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 environment (InfoArea), model (Multiprovider and InfoCube),

dimensions (InfoObjects), and properties (InfoObjects). This causes subsequent transports to fail.

6 Troubleshooting


50/58 CUSTOMER 2014-01-10

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 RSOCONTENT.2. 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_OBJECT version 'D'

for Environment is filled

1. Enter transaction code SE16 for table UJT_TRANS_OBJECT.2. Delete all the D version records for your environment in this table.3. Reimport the request.

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 dimension.If 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 system.2. Reimport the transport request.

Import failed with the error: Failed to create infoarea

1. Enter transaction code SE06.2. Change the namespaces /CPMB/ and /B28/ to be modifiable.3. 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.7 Component-Level Logs

All the component-level logs are written using a trace log API and are available as part of the application

log.

NOTE

For SAP BusinessObjects Planning and Consolidation, replace <app config name> with bpc.

1. How do I launch the application?

http://<host>:<port>/sap/fcprt?app-config=<app config name>

6 Troubleshooting


2014-01-10 CUSTOMER 51/58



2. How do I launch the application in debug mode?

http://<host>:<port>/sap/fcprt/d?app-config=<app config name>

3. How do I enable debug mode in the application?

To enable debug mode, the Flex Client Platform (FCP) server parameter pp-enable-

debugging=true must be set and the URL query parameter debug=true must be used when

launching the application.

For example: http://<host>:<port>/sap/fcprt?app-config=<app config name>&debug=true

4. How do I enable support mode in the application?To enable support mode, the FCP server

parameter pp-support-mode=true must be set and the URL query parameter support-

mode=true must be used when launching the application.

For example: http://<host>:<port>/sap/fcprt?app-config=<app config name>&support-

mode=true

5. How do I see status of the various plug-ins and the reasons why some plug-ins are not

loaded?

As a prerequisite, enable the support mode.

■ After launching the application in support mode, right-click the application and select Support

Info.

In the Loaded Plug-ins tab of the Support Information dialog, you can see information about the loaded

plug-ins, the state of the plug-ins and the error information for plug-ins that could not be

loaded.

6. How do I see the version information of the plug-ins?

As a prerequisite, enable the support mode.

■ After launching the application in support mode, right-click the application and select Support

Info.

In the Loaded Plug-ins tab of the Support Information dialog, you can see information about the version

and the build number of the plug-in.

7. How do I enable logging and tracing for the application client?

To enable tracing on the client, the FCP server parameter pp-enable-trace=true must be set and

the URL query parameter show-trace=true must be used when launching the application.

For example: http://<host>:<port>/sap/fcprt?app-config=<app config name>&show-

trace=true

Logging is always enabled on the client (though you can technically set logging level to NONE,

which would mean no statements are logged on the client, this is not recommended). To configure

which levels of statements to be logged, set the FCP server parameter pp-log-filter to one of the

appropriate values (ERROR|FATAL|SUCCESS|WARNING|INFO|NONE|*)

For example: To enable only statements with levels ERROR and FATAL to be logged, set pp-log-

filter=ERROR|FATAL

8. How do I enable the startup trace in the application?

6 Troubleshooting


52/58 CUSTOMER 2014-01-10

As a prerequisite, enable the tracing on the client.

When launching the application, use the URL query parameter show-trace=startup. During the

loading of the client, you see a dialog with the trace information collected during startup.

For example: http://<host>:<port>/sap/fcprt?app-config=<app config name>&show-

trace=startup

9. How do I view the log console/How do I send the client logs to the server?

As a prerequisite, enable the logging and tracing on the client.

After launching the client, right-click and choose Show Message Log Console. The dialog box displays

the logs and traces. The dialog also provides an option to transmit the client logs to the server and

to turn off tracing on the client for the session duration.

10. What do I do if the application does not start?

In SAP GUI, enter transaction SE80. Go to the MIME Repository and open SAP POA FCP

Container . Download the POASBCBUI00_0.sca file.

The version information is available in the SAP_MANIFEST file in the MANIFEST folder of the sca

archive file.

Setting Up Support User

Create a role, <DISPLAY_USER ROLE>, with limited READ rights using /POA/A_BUI authorization

object with the following field value entries:

Authorization Object Field Value Entries

/POA/A_BUI /POA/CNTTP:*

/POA/RESTP:*

/POA/PSAPP:*

/POA/PSACT:READ

/POA/ACDTP:*

/POA/AUTHT:F


/POA/RESTP:/POA/AUI_FOLDER,/POA/BUI_USER_PREFERENCES

/POA/PSAPP:*

/POA/PSACT:CREATE

/POA/ACDTP:*

/POA/AUTHT:F


/POA/RESTP:/POA/BUI_USER_PREFERENCES

/POA/PSAPP:*

/POA/PSACT:UPDATE

/POA/ACDTP:*

/POA/AUTHT:F


/POA/RESTP:/POA/BUI_USER_LINK,/POA/AUI_FOLDER

6 Troubleshooting


2014-01-10 CUSTOMER 53/58

Authorization Object Field Value Entries

/POA/PSAPP:*

/POA/PSACT:CREATECHILD

/POA/ACDTP:*

/POA/AUTHT:F

If the application is used with sub namespaces, you also need to assign /POA/A_BPT authorization

object to the role with the same field values as for /POA/A_BUI authorization object. You need an

additional entry for field name, /POA/SUBNS, and a value equal to the value of sub namespace.

Assign POA/A_FCP authorization object with authorization field value: /POA/CFCP: R

Assign the above role for the support user along with the roles /POA/BUI_FLEX_CLIENT and /POA/

BUI_UM_USER.

6.8 Troubleshooting for CLM

You can use the error report /POA/R_CLM_CG_REP01 to diagnose issues and problems with content

group extracts, where the content group is in error status, in the Content Lifecycle Management

application. It allows you to display the content group metadata and to see the breakdown of content

records.

In the SAP GUI, go to transaction SE38 and run the report for a specific content group.

6.9 Troubleshooting for Event & Notification

If messages are not being delivered, check the scheduled jobs for event and notification.

For more information about monitoring the jobs required to send messages to e-mail, see the

installation guide.

6 Troubleshooting

6.8 Troubleshooting for CLM

54/58 CUSTOMER 2014-01-10

7 Support Desk Management

7.1 Remote Support Setup

SAP support needs to be able to work remotely for highest efficiency and availability. For this support,

SAP uses the remote connection with SAProuter for a specific problem that you log by creating a

customer message in the SAP Support Portal. For information about SAProuter, see the following SAP

Note:

SAP Note Title Comment

486688 Schedule VPN connection to SAP network See also the SAP Notes that this SAP Notes refers to for specific settings or parameters that are necessary

For further assistance, see the following SAP Note:

SAP Note Title Comment

812386 RFC connection to the SAPNet R/3 front end -

7.2 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.

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-TRA Transport

Administration: EPM-BPC-NW-ADM


EPM-BPC-NW-ADM-APP Application Management


7.1 Remote Support Setup

2014-01-10 CUSTOMER 55/58



http://service.sap.com/

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

Installation: EPM-BPC-NW-INS


EPM-BPC-NW-INS-NW ABAP Installation

Web Client: EPM-BPC-NW-WEB


EPM-BPC-NW-WEB-CNT Documents View

EPM-BPC-NW-WEB-REP Web Reports

EPM-BPC-NW-WEB-STA Getting Started

POASBC Component


XAP-SBC-BUI-ABA ABAP Backend

XAP-SBC-BUI-UI Flex UI

Content Lifecycle Management


XAP-SBC-CLM Content Lifecycle Management


7.2 Problem Message Handover

56/58 CUSTOMER 2014-01-10

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2013 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.

011000358700000483512011 e

Documents

Transcript of 011000358700000483512011 e