bpc administration guide

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

Target Audience

n Technical Consultantsn System Administratorsn Solution Consultantsn Business Process Ownern Support Specialist

PUBLICDocument version: 1.0 ‒ 04/23/2012

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

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

www.sap.com

© Copyright 2012 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 permissionof 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 othersoftware 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 orregistered trademarks of IBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated 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 registeredtrademarks 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 implementedby 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 wellas their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other product and service names mentioned are the trademarks of their respective companies. Datacontained 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 notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere 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 oraltered in any way.

2/60 PUBLIC 04/23/2012

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriateentries 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 thedocumentation

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 tospecific content on the Web

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

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

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn 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 languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

04/23/2012 PUBLIC 3/60

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 thisadministrator’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 4/23/2012 Version 1.0 to accompany GA release

4/60 PUBLIC 04/23/2012

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

Table of Contents

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

Chapter 2 Important SAP Notes . . . . . . . . . . . . . . . . . . . . 9

Chapter 3 Monitoring of Planning and Consolidation . . . . . . . . . . . 113.1 Setting up a Minimal-Access User to Configure SMD . . . . . . . . . 113.2 Enabling the Auto-Alert Mechanism in CCMS . . . . . . . . . . . . 123.3 Availability Monitoring . . . . . . . . . . . . . . . . . . . . 123.4 Component-Specific Monitoring . . . . . . . . . . . . . . . . 133.5 Detailed Monitoring and Tools for Problem and Performance Analysis . . . 143.5.1 Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . 143.5.1.1 Logging of Exceptions in the SLG1 System . . . . . . . . . . . . . 153.5.1.2 Trace File for Debugging Logic . . . . . . . . . . . . . . . . . 153.5.1.3 Data Manager Log Files . . . . . . . . . . . . . . . . . . . . 153.5.1.4 Trace and Log Files for Context & Insights . . . . . . . . . . . . . 163.5.1.5 Trace and Log Files for Content Lifecycle Management . . . . . . . . . 163.5.2 Workload Monitors . . . . . . . . . . . . . . . . . . . . . 163.5.3 Data Growth and Archiving Monitors . . . . . . . . . . . . . . . 173.5.4 Problem Analysis for CLM . . . . . . . . . . . . . . . . . . . 173.5.5 Interface Monitors for CLM . . . . . . . . . . . . . . . . . . 183.5.6 Data Consistency for CLM . . . . . . . . . . . . . . . . . . . 19

Chapter 4 Management of Planning and Consolidation . . . . . . . . . . . 214.1 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . 214.2 Backup Best Practices . . . . . . . . . . . . . . . . . . . . . 214.3 Best Practices for Performance Management . . . . . . . . . . . . 224.3.1 Processing Tiers . . . . . . . . . . . . . . . . . . . . . . . 224.3.2 Cube Fact Tables . . . . . . . . . . . . . . . . . . . . . . . 224.3.3 Cube Optimization . . . . . . . . . . . . . . . . . . . . . . 234.3.4 Cube Modification . . . . . . . . . . . . . . . . . . . . . . 234.3.5 Writeback Parameters . . . . . . . . . . . . . . . . . . . . . 234.3.6 SQE Parameters . . . . . . . . . . . . . . . . . . . . . . . 244.4 Set Up of BPF E-mail Notifications . . . . . . . . . . . . . . . . 244.5 CLM Configuration . . . . . . . . . . . . . . . . . . . . . 254.6 Administration Tools . . . . . . . . . . . . . . . . . . . . . 29

04/23/2012 PUBLIC 5/60

4.6.1 Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.6.2 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . 324.6.3 User Management . . . . . . . . . . . . . . . . . . . . . . 324.6.4 Utilities for CLM . . . . . . . . . . . . . . . . . . . . . . . 324.7 Backup and Restore . . . . . . . . . . . . . . . . . . . . . 334.8 Scheduled Periodic Tasks for CLM . . . . . . . . . . . . . . . . 334.9 Scheduled Periodic Tasks for Event & Notification . . . . . . . . . . 34

Chapter 5 Software Change Management . . . . . . . . . . . . . . . . 355.1 Transport Management . . . . . . . . . . . . . . . . . . . . 355.1.1 Transport Objects . . . . . . . . . . . . . . . . . . . . . . 365.1.2 Transport Configuration . . . . . . . . . . . . . . . . . . . 375.1.3 Transport Execution . . . . . . . . . . . . . . . . . . . . . 375.1.3.1 Transporting Environments . . . . . . . . . . . . . . . . . . 375.1.3.2 Transport Deletion . . . . . . . . . . . . . . . . . . . . . . 385.1.4 Transport Log Files . . . . . . . . . . . . . . . . . . . . . . 395.1.5 Transport Maintenance . . . . . . . . . . . . . . . . . . . . 405.1.6 Deployment Scenarios . . . . . . . . . . . . . . . . . . . . 405.2 Development Requests and Development Release Management . . . . . 415.3 Quality Management and Test Management for CLM . . . . . . . . . 415.4 Support Packages and Patch Implementation . . . . . . . . . . . . 41

Chapter 6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . 436.1 Troubleshooting in Planning and Consolidation . . . . . . . . . . . 436.2 Analyzing Problems Using Solution Manager Diagnostics . . . . . . . . 436.3 Installing Appsight Black Box Service . . . . . . . . . . . . . . . 436.4 Generating and Analyzing Trace Files Using E2E Trace . . . . . . . . . 446.5 Logging and Tracing Configuration . . . . . . . . . . . . . . . . 466.5.1 Logging and Tracing Parameters . . . . . . . . . . . . . . . . . 476.5.2 Client Configuration . . . . . . . . . . . . . . . . . . . . . 506.6 Troubleshooting Transport . . . . . . . . . . . . . . . . . . . 516.7 Component-Level Logs . . . . . . . . . . . . . . . . . . . . 536.8 Troubleshooting for CLM . . . . . . . . . . . . . . . . . . . 566.9 Troubleshooting for Event & Notification . . . . . . . . . . . . . 56

Chapter 7 Support Desk Management . . . . . . . . . . . . . . . . . . 577.1 Remote Support Setup . . . . . . . . . . . . . . . . . . . . 577.2 ProblemMessage Handover . . . . . . . . . . . . . . . . . . 57

6/60 PUBLIC 04/23/2012

1 Getting Started

1 Getting Started

Caution

This guide does not replace the daily operations handbook that we recommend customers create fortheir specific production operations.

About this Guide

Designing, implementing, and running Planning and Consolidation at peak performance 24 hours aday has never been more vital for your business success than now.This guide provides a starting point for managing Planning and Consolidation solutions andmaintaining and running them optimally. It contains specific information for various tasks andlists the tools that you can use to implement them. This guide also provides references to thedocumentation required for these tasks, so you will sometimes also need other guides such as theMaster 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 athttp://service.sap.com/instguides

Monitoring Setup Guide for SAP NetWeaver SAP Service Marketplace athttp://service.sap.com/instguides

SAP NetWeaver Security Guide SAP Service Marketplace athttp://service.sap.com/securityguide SAP

NetWeaver

Solution Life Cycle Management by Key Capability SAP Help Portal at http://help.sap.com SAPNetWeaver

04/23/2012 PUBLIC 7/60

http://service.sap.com/instguides


http://service.sap.com/securityguide

http://help.sap.com

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

2 Important SAP Notes

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 Planning and Consolidation 10.0for NetWeaver DocumentationAddendum

Contains information that does not appear in theapplication help of Planning and Consolidation10.0, version for the SAP NetWeaver platform.

1660062 SAP Planning and Consolidation10.0 SP06, version for the NetWeaverplatform

This note contains installation information,enhancements, and resolved issues for SAPPlanning and Consolidation 10.0 SP06, versionfor the SAP NetWeaver platform.











04/23/2012 PUBLIC 9/60








3 Monitoring of Planning and Consolidation

3 Monitoring of Planning andConsolidation

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, forexample by utilizing the Computing Center Management System (CCMS) and NetWeaver ABAPmonitoring tools.

Recommendation

Since the application is powered by SAP NetWeaver 7.30, we recommend that you set up themonitoring infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver on SAPService Marketplace at http://service.sap.com/instguides.

This contains all the information relevant to monitor the SAP NetWeaver components used inthe application.Proficient knowledge of system monitoring and basic knowledge of SAP NetWeaver is required tocompose user-defined monitors. For more information about monitoring in the CCMS, see SAP HelpPortal at http://help.sap.com SAP NetWeaver .Monitoring for Content Lifecycle ManagementBy default, CCMS monitoring capabilities are restricted to the local system and as CLM involvesinteractions with more than one system in a typical landscape, it could be beneficial to monitor othersystems through CCMS from central CLM system.In this case, CLM, as the central monitoring system can be configured to link CCMS monitoringfrom application systems. Since currently CLM only communicates with ABAP-based systems, RFCconnection 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 asmonitoring, with the Central Computing Management System (CCMS).The user, who performs these monitoring and diagnostic services, does not need to be able tomanipulate the Planning and Consolidation data. Therefore, it may be advisable to create a user with

04/23/2012 PUBLIC 11/60


http://help.sap.com

3 Monitoring of Planning and Consolidation3.2 Enabling the Auto-Alert Mechanism in CCMS

minimal access rights and configure SMD to access Planning and Consolidation with this user. Thefollowing procedure describes the creation and configuration of such a user.

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 pane3. In the Users view, select Add. In the Add User assistant, select the user to add in the environment4. 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 andConsolidation 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 andSMS

You want to send alerts from theCCMS monitoring architecture(transaction RZ20) as an e-mail,SMS or other message type to oneor several recipients.

3.3 Availability Monitoring

A simple Generic Request and Message Generator (GRMG) scenario for SAP Planning andConsolidation is available. This checks the availability of the SAP Planning and Consolidationapplication server, and presents the status of its current availability.

FeaturesIn the Central Monitoring System (CEN) you can load the Planning and Consolidation templatecustomizing file and start the GRMG scenario to monitor availability of the application server.

12/60 PUBLIC 04/23/2012


3 Monitoring of Planning and Consolidation3.4 Component-Specific Monitoring

Note

For availability monitoring, set up and use a Planning and Consolidation user with minimal accessprivileges for monitoring and diagnostics related web services, such as GRMGweb services. For moreinformation, see Setting up a Minimal-Access User to Configure SMD [page 11].

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. Youmust specify the URL of the scenario (host and port), as well as the username and password.

2. Save your entries.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 CCMSmonitoring 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, andbackground processing for the application server where the application is running.The following existing monitors within RZ20 can be used by the application to monitor criticalconditions:Database MonitoringYou can monitor the RDBMS connection using the CCMS database monitor. This is the connectionto the system where the application is installed and in use.Operating System MonitoringOperating systemmonitoring capabilities within CCMS administration workplace are used to analyzeCPU, memory, paging, disks, file system, and their corresponding health statuses.Dialog OverviewUsing dialog monitoring in RZ20, the response time for dialog, network time, and number ofcurrently logged-in users can be observed.Error MonitoringThe log file for SAP Planning and Consolidation is monitored for error patterns. Themonitor presentsits status and alerts according to the presence of errormessages in the SAP Planning and Consolidationlog. If errors occur in this log, you can display them in transaction CCMS by selecting Open Alerts.

Monitors for Content Lifecycle Management

Dialog Overview

04/23/2012 PUBLIC 13/60

3 Monitoring of Planning and Consolidation3.5 Detailed Monitoring and Tools for Problem and Performance Analysis

For CLM, you can observe Web Dynpro ABAP-related attributes such as date transferred, sessiontimeouts, and number of roundtrips against CLM Web Dynpro application /POA/WD_CLM. Thisview is also part of the delivered CLM-specific Content Lifecycle Management Monitor Set.Background ProcessingFor 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 beused to retrieve statistics such as a list of long-running background jobs, number of free or occupiedwork processes, and any CLM job that was stopped abruptly.

Note

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

3.5 Detailed Monitoring and Tools for Problem andPerformance 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 andservices

Log messages pertainingto workflow (alerts,fatal messages, errors,status updates). Messagesare also shown in thecommon message regionin the top-right cornerof the container. Tracesare enabled through logmessage APIs

Log messages on clientside are inmemory. Thereis an option to export themessages to the server.These messages are forviewing and analyzing inthe administrator tool forthe application

N/A

- System Trace Analysis —RFC, HTTP, DB

- Transaction ST01

- SQL Performance Traceand Analysis — RFC,HTTP, DB

- Transaction ST05

All logs related to runtime exceptions are recorded.

n Check BUI log in SLG1

14/60 PUBLIC 04/23/2012


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 forimproved 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 isidentified 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

*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 particularscript or rule. We recommend that this is only used by experienced Planning and Consolidationconsultants and support. We also recommend that these files are removed periodically since theytake 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 systemcreates a log file. This file can be useful in troubleshooting the execution of packages. We recommendthat these files are removed once the packages have completed since they take up a considerableamount of space.These logs are stored in<Drive>\webfolders\<environment>\<model>\privatepublication\<username>\tempfiles.The name of the log file contains the following details:

n The name of the packagen A timestamp

04/23/2012 PUBLIC 15/60


n 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 errorsand exceptions in thecommunication withclient

- /POA/CTX/REST

Context Service Details about errors andexceptions occurringwithin the context server

- /POA/CTX/SERVICE

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 asthis 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 throughRFC protocol to extract and deploy the contents onto application systems.

3.5.2 Workload Monitors

A default workload collector as part of CCMSmonitoring and workloadmonitor through transactionST03N can be used to observe the workload records at application server level.

Component Monitor Detailed Description Prerequisites

- Workload Monitor —Transaction ST03N

Detailed analysis ofworkload of applicationservers

-

16/60 PUBLIC 04/23/2012


3.5.3 Data Growth and Archiving Monitors

Component Monitor Detailed Description Prerequisites

DB tables ST05 Observe criticaloperations and tablesthat takemore time alongwith their hit and missratio

Switch the trace onbefore performing costlyoperations

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

n /POA/D_XML_VALS— Resource Value (XML) for persistence servicen /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:

n /POA/D_CLM_CP02— CLM Content group and Entity relationshipn /POA/D_CLM_DPLR— Table for storing entity processing messagesn /POA/D_CLM_ENT01 — CLM Entity Tablen /POA/D_CLM_ENT02 — CLM Entity Fields value Tablen /POA/D_CLM_ENT03— CLM Entity — Entity Relationshipn /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 recommendedtracking mechanism for CLM:

CLM Scenario/Activity Problem Possible Causes RecommendedMonitoring

Exception Occurred RFC connection failure,system failure, noauthorization for RFCcalls

Check system trace file(ST01)/ SM59 / SMT1 fortrusted connections. CLMlog in SLG1

Extraction in progress fora long time

Large amount of content Check background taskin SM37 and CCMS CLMmonitor

Extraction of contentfrom application system

Validation errors Content in incorrectformat

SLG1 ‒ application log forCLM

04/23/2012 PUBLIC 17/60


CLM Scenario/Activity Problem Possible Causes RecommendedMonitoring

Exception occurred Malformed content ortempered content format

SLG1 ‒ application log forCLM

Importing content from aCLM package (zip)

Time out Package size is too big Check CCMS memoryor buffer sizes to freeresources, increase timeout limits for profileparameters; usuallycannot be resolved

Exporting CLM contentto a package (zip)

Exception occurred Content was changedafter including in package

SLG1 or check status ofcontent group

- Time out Content size is too big Remove hugeattachments, split packageinto two smaller packages

Exception occurred Incompatible system forapplication deployment ofcontent, RFC connectionfailure, system failure, noauthorization for RFCcalls, no trusted system

SLG1 ‒ application logfor CLM, system trace file(ST01), SMT1 for trustedconnections

Deployment takes toolong

Large amount of content SM37 or CCMS for CLMdeployment and pollingresults background job

Non recognized status indeployment log

Failure on applicationdeployment

Check target applicationsystem, ST22, for anyexceptions, authorizationfailures

Deploy Content

No deployment possible Existing deployment ontarget system already ongoing

Check DB locksin SM12 (table/POA/S_CLM_DEPLKEY)

3.5.5 Interface Monitors for CLM

Content Lifecycle Management (CLM) communicates with application system using RFC. For certainintensive operations, such as content extraction, interface monitors could be used to analyze thetime spent on each RFC call.

18/60 PUBLIC 04/23/2012


Interface Detailed Description Technology Used

You configure APIs and RFCfunctions in Customizing forContent Lifecycle Management underMaintain System Registry API

Groups .

ABAP Web Dynpro applicationuses these calls and interfaces atruntime

RFC

/POA/CLM_WD ABAP Web Dynpro application isaccessed using HTTP

HTTP

3.5.6 Data Consistency for CLM

Content Lifecycle Management (CLM) is used as a repository containing application content. Thecontent in the CLM repository can be added either by extraction from various application systemsor by importing a new vendor-delivered package. During these operations CLM always loads thedata first and performs validations on top of such content to report functional inconsistencies. Ifthere are abrupt blockages, such as connection timeout, it can result in differences between the datamaintained 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 onany business function in CLM.

04/23/2012 PUBLIC 19/60

4 Management of Planning and Consolidation

4 Management of Planning andConsolidation

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: STARTSAPSTARTSAP (UNIX)SAP ManagementConsole

The application is basedon SAP NetWeaverinfrastructure. Formore information,see the TechnicalOperations Manualon SAP Help Portal athttp://help.sap.com

SAP NetWeaver .

4.2 Backup Best Practices

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

1. On the SAP Help Portal, refer to the backup procedures athttp://help.sap.com/saphelp_nw70/helpdata/EN/7c/efa841c1dade34e10000000a1550b0/content.htm.

2. On SAP Service Marketplace at http://service.sap.com/solutionmanagerbp, refer todocuments 084 Business Continuity Management for SAP System Landscapes and 085 Emergency Handling forRecovery of SAP System Landscapes.

3. On the SAP Developer Network athttps://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 availabilitySAP NetWeaver infrastructure.

04/23/2012 PUBLIC 21/60

http://help.sap.com

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




4 Management of Planning and Consolidation4.3 Best Practices for Performance Management

4.3 Best Practices for Performance Management

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

n Number of dimension members

n Amount of transactional data in a given modeln Number of concurrent users

n Hardware

n Network bandwidth

4.3.1 Processing Tiers

To optimize performance, it is useful to understand the system tiers, and the processing that occurson those tiers. The following table outlines them:

Tier Description

Database The following processes occur at the database level:n Data readsn Data write-backs

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

n Metadata reads and writesn Application file storage (book repositories, report and input templates,

unstructured data, conversion files, and transformation files)

NetWeaver ABAPApplication Server

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

BI Accelerator (optionalcomponent)

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

4.3.2 Cube Fact Tables

Each InfoCube has the following two fact tables:

n E fact table, for compressed recordsn F fact table, for uncompressed records

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

22/60 PUBLIC 04/23/2012

4 Management of Planning and Consolidation4.3 Best Practices for Performance Management

4.3.3 Cube Optimization

Optimizations have been implemented as process chains. As such, you can schedule them using DataManager or execute them using Administration.For more information about modifying and scheduling optimization process chains, see the DataManager section in the application help. For more information about executing optimization processchains, 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 movesthe data to that cube when the system determines a data model reorganization is needed (forperformance reasons). Any external modifications made to the cube (for example, throughtransaction RSA1) are lost, and are not moved with the data. These modifications include suchthings 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 theindividual model level. In general, you will not need to change the default values. They are describedin the following table:

Parameter Default Description

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

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

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

04/23/2012 PUBLIC 23/60

4 Management of Planning and Consolidation4.4 Set Up of BPF E-mail Notifications


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

INTERVAL_NR 10 In the situation where record level locking is not beingimplemented and the data set being saved is NOT sparse, anydimensions with less than this number of distinct membervalues in the dataset will be locked using their single values.If the dimension has more than this number of records, therange 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 theindividual model level. In general, it is not necessary to change these values. They are describedin the following table:


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

4.4 Set Up of BPF E-mail Notifications

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

PrerequisitesEnvironment users must have e-mail addresses.

FeaturesOwners are notified by e-mail when a BPF instance is created and actions are taken. In addition, theyare 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.

24/60 PUBLIC 04/23/2012

4 Management of Planning and Consolidation4.5 CLM Configuration

Example

Subject: BPF instance <name> now ready for actionText: BPF Instance for dimensions time 2009.total and category budget. Step region(s): first activestep number and step region dimension:member. As a participant in this business process pleaseselect 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 andcustomize 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 inputmulti-language text in the e-mail body, and you can add the following variables to display informationin the e-mail to help its recipient:

n %INST_NAME%

n %STEP_NAME%

n %URL%

n %STEP_REGION_NAME%

Managing BPF e-mails

Set up and customization of BPF e-mail notification templates is done on the back-end. Perform thefollowing 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 customizedemail template icon in the toolbar. Then, modify it as needed.

4.5 CLM Configuration

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

04/23/2012 PUBLIC 25/60


Component Configuration Tools Detailed Description

Content Lifecycle Management(Software Component POASBC)

Customizing— this the standardSAP tool for ABAP-based systemused for component Customizing.Access it through transaction SPRO

Technical configuration: Mainlyfor configuring application systemsand the APIs with which CLMinteracts

Content Lifecycle Management(Software Component POASBC)

SAP Solution Manager SAP Solution Manager is thestandard SAP tool for process andscenario-based configuration.

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


1230438 Solution Manager Content for SAPSRM 7.0

Additional information for usingSolution 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-modeExpected value ‒ true/false; default value ‒ falsePurpose:When set to true, the support information is displayed in the context menu on the client. Thisdisplays details about the loaded bundles on the client. All other support information can also beaccessed by enabling this parameter.

Platform Parameters That Can Be Set As Part Of Application Configuration ‒ CouldInfluence Client‘s Behavior

1. pp-enable-lazy-loadingExpected value ‒ true/false; default value ‒ falsePurpose:This is a kind of central switch to turn ON/OFF the lazy loading of bundles. This configurationoverrides all the lazy loading options present in any bundle’s plugin.xml. When set to true, allthe lazy loading configurations are considered by the Flex Client Platform (FCP) client. As aresult, the bundles are loaded only on demand ‒ when required by the application. This setting isrecommended especially for large applications as this enhances the performance. When set to

26/60 PUBLIC 04/23/2012



false, the lazy loading configurations are ignored by the FCP client and hence all the bundles areloaded at application startup.

2. pp-enable-traceExpected value ‒ true/false; default value ‒ falsePurpose: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, nolog console can be opened on the application.

3. pp-enable-debuggingExpected value ‒ true/false; default value ‒ falsePurpose:Enables debugging on FCP client. When set to true, the debug version (‘..-d.swf’) of a plug-in isdownloaded 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, theparameter must only be enabled if debugging of the application is required.

4. pp-enable-request-batchingExpected value ‒ true/false; default value ‒ truePurpose:Helps FCP client decide whether to send single/multiple requests for a plug-in manifest. Whenset to false, FCP client sends single request for every single plug-in manifest. The number ofrequests depend on the number of resolved bundles for an application. When set to true, FCPclient sends a single request for plug-in manifests. This reduces the number of calls to the serverand hence increases the performance.

5. pp-support-modeExpected value ‒ true/false; default value ‒ falsePurpose:When set to true, the support information is displayed in the context menu on the client. Thesupport information displays details about the loaded bundles on the client. All future supportinformation can also be accessed by enabling this parameter.

6. resource-expiry-durationExpected value ‒ No. of days; default value ‒ 365Purpose:The specified number of days are added to the current date and expiry date is the resourceset accordingly. For example, if today‘s date is Mon, April 5 2010, and you have specified 2 asresource-expiry-duration, the ‚expires‘ in HHT header of the response is set to Wed, 07 Apr 201000:00:00 GMT.

7. pp-log-filterExpected value ‒ ERROR|FATAL|SUCCESS|WARNING|INFO|NONE|*; default value ‒ *Purpose:

04/23/2012 PUBLIC 27/60


Controls the display of logs and traces in the log console. All the messages that match the levelset and below levels are filtered and displayed.

8. log-expiry-durationExpected value ‒ duration, in number of days; default value ‒ 7Purpose:Used by logger service on ABAP server component to set the expiry date on application logs.

9. enable-server-cacheExpected value ‒ true/false; default value ‒ truePurpose:Used by FCP ABAP server component to turn on/off server cache used for storing applicationconfiguration.

Splash Configuration

1. The splash configuration in the application configuration xml contains the bundle name that is tobe used as the splash/boot information bundle.

Application Parameters

1. Apart from the platform parameters, you can configure application-wide parameters inthe <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 isthat 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-overrideExpected value ‒ true/false; default value ‒ falsePurpose:HTTP client uses this configuration and if the value is true the PUT/DELETE HTTP methodsare sent via a POST request. ‚false‘ means that PUT/DELETE are sent as PUT/DELETE requestsrespectively.

FCP URL Parameters That Can Be Passed to Client Platform

1. config-urlThis is an optional parameter that tells the platformwhere to pick up the application configurationfrom. This can point to a static/pre-configured XML file or to any URL that can be requested viaHTTP. By default, FCP looks for an XML file with name com_sap_tc_ui_ria_fcp_config.xml.

2. execution-scopeThis is an optional parameter that can be used to filter the bundles based on the unique scope inwhich a particular FCP application wants to run.

3. hide-splash

28/60 PUBLIC 04/23/2012

4 Management of Planning and Consolidation4.6 Administration Tools

This is an optional parameter that when set to true, no splash screen is displayed, insteadFCP shows a progress bar with status message, and all the configurations in the applicationconfiguration for splash are overridden.

4. show-traceThis is an optional parameter that when set to true, the client displays the log console (dependingon the pp-enable-trace parameter).

5. debugThis is an optional parameter that when set to true, the client runs in debug mode (depending onthe pp-enable-debugging parameter).

6. app-defThis is an optional parameter that can be used to pass application-specific and static configurationto FCP applications. It can contain additional application-related content apart from standardFCP definitions. Note: Application definition is not able to influence platform parameters (allserver parameters starting with pp-).

7. mask-featureThis is an optional parameter that can be used to filter the bundles based on the feature scope.

8. support-modeThis parameter can be used on client side to enable/disable support information. Note thatsupport information is visible only when both platform parameter (pp-support-mode) and URLparameter (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 administratorsfor auditing and monitoring purposes.

n Application Log: Every operation and corresponding steps carried out during that operationare recorded in the application log:Transaction SLG1, log objects: /POA/PST and /POA/UMThe application log includes detailed information about error messages and sequential flow withrespect to technical processing in the application.This object includes the following subobjects or categories:l 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

04/23/2012 PUBLIC 29/60


n Application Log: Every CLM operation and corresponding steps carried out during thatoperation are recorded in the application log:Transaction SLG1, object: /POA/CLMThe application log includes detailed information about error messages and sequential flow withrespect to CLM technical processing.This object includes the following subobjects or categories:l PACKAGE: Use this subobject to monitor and analyze the logs specific to CLM packages (all

steps performed underManage Packages function on CLM UI)l CHECKPOINT: All actions performed underManage Content Groups in CLM are recorded for

analysis under this application log subobjectl DEPLOYMENT: Application logs related to deployment from CLM are recorded under this

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

n Deployment Log: This is available on CLM UI. It displays statuses and messages for deploymentsfrom CLM to the application. The deployment log provides details of application-specific messagesper deployment system and per content group.

n Change Log or Change History: For all actions that can be carried out in CLM UI, suchas editing, deployment, import, and export. CLM logs the change history using the changedocuments function of ABAP. CLM change logging is enabled for packages and content groupsand related tables. This can be seen in CLM UI with View History function.

n Customizing object or Table Logging: All Customizing, control, and system database tablesdefined in CLM are enabled for logging. Analysis of this logging can be done using SCU3transaction in NetWeaver ABAP system if logging is switched on.

Flex Client Platform (FCP) Server-Side Log MessagesThe 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:n Object: /POA/SFCP (Display Only)n Subobject: FCPAPPLOG (Display Only)n Optional: External ID: Category of the log message, as seen in the application log consolen Mandatory: Time (From/To): The required interval as seen in application log consolen Optional: User: User of the sessionn Set the default values for the remaining filters as follows:l Transaction Code: *

l Program: *

l Log Class: All logs

l Log Creation: Any

l Log Source and Formatting: Format Completely from DatabaseThe exported log messages are grouped based on Category/External ID and displayed.

30/60 PUBLIC 04/23/2012


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 MessagesThe 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 bedeleted explicitly using transaction SLG2.

1. Connect to the ABAP system, execute transaction /POA/SFCPAPPTRACE.2. Provide the following filters:n Object: /POA/SFCP (Display Only)n Subobject: FCPAPPTRACE (Display Only)n Optional: External ID: Category of the trace message, as seen in application log consolen Mandatory: Time (From/To): Required interval as seen in application log consolen Optional: User: User of the sessionn Set the default values for the remaining filters as follows:l Transaction Code: *

l Program: *

l Log Class: All logs

l Log Creation: Any

l Log Source and Formatting: Format Completely from DatabaseThe 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 TracesAll application logs and traces are generated with an expiry date and Deletion before expiry attribute set totrue. Hence all the logs and traces can be deleted before their expiry date. The expiry date for logs andtraces 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 ofdays 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:n Expiry date: and logs which can be deleted before the expiry date

n Object: /POA/SFCP

n Subobject: FCPAPPLOG to FCPAPPTRACE

n Options: Delete immediately

04/23/2012 PUBLIC 31/60


n 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 databasetables 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 setuptogether with a load balanced network setup.For more information about network load balancing, see the Technical Infrastructure Guide for SAPNetWeaver on SAP Service Marketplace at http://service.sap.com/instguides.A load-balanced network using SAP Web Dispatcher together with logon groups in the SAPNetWeaver 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 byNetWeaver.For more information about user administration and authentication, see the application securityguide on SAP Service Marketplace at http://service.sap.com/securityguide.

4.6.4 Utilities for CLM

Content Lifecycle Management Administrator/Developer UtilitiesCLM provides utilities for testing purposes, which are intended for administrators and developeruser groups.ApplicationAPI Adapter testing: Since CLM calls the RFC functionmodules while communicatingwith application systems, it expects a certain format and interface for these API/RFC functionmodules.Moreover, an appropriate system setup is also required via system registry configuration where newapplication systems and their APIs are registered. For more information, see Customizing for ContentLifecycle Management underMaintain System Registry.

32/60 PUBLIC 04/23/2012



http://service.sap.com/securityguide

4 Management of Planning and Consolidation4.7 Backup and Restore

In actual scenarios or for productive usage; before you run CLM with system registry settings, it isadvisable to run the test adapter utility using transaction /POA/CLM_API_TESTER. You need toprovide the system registry ID. The transaction checks API interfaces and also performs a test run forextraction and deployment operations.Cleaning up the CLM database: If you are running CLM for test purposes or on a testsystem, 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 forspecific entry deletion from CLM database tables. Hence it is intended to be used for cleaning upgarbage 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 SystemComponents

Category Properties SuggestedMethods forBackup and Restore

Examples

VIII Original applicationdata, standalone systembased on SAP NetWeaverApplication Server

Data:n Database and log

backup, applicationlog backup (such asjob logs in file system)

n 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 RecommendedBackupFrequency

POASBC Application databasetables, 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 tablegives an overview of the exact programs that are scheduled in the background and the frequencyat which these are executed.Scheduled periodic tasks for Content Lifecycle Management:

04/23/2012 PUBLIC 33/60

4 Management of Planning and Consolidation4.9 Scheduled Periodic Tasks for Event & Notification

Program Name/Task Task-Scheduling Tool RecommendedFrequency

Detailed Description

/POA/R_CLM_DE-PLOY_RESULTS_POLL

Automatic 10 minutes: This can bechanged in Customizingfor Content LifecycleManagement underMaintainTechnical Settings.

Used to retrieve thedeployment results ofapplication contentfrom target applicationsystems. For moreinformation, see ContentGroup Deployment in SAPLibrary documentationunder Content LifecycleManagement Content Groupand Package ManagementContent Group Deployment .

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

Program Name/Task Task-Scheduling Tool RecommendedFrequency


/POA/R_CLM_EX-TRACT

Automatic Immediately when theoperation is triggered

Background task duringcontent group extraction

/POA/R_CLM_DEPLOY Automatic Immediately when theoperation is triggered

Background task forcontent group uploadand deployment

4.9 Scheduled Periodic Tasks for Event & Notification

Program Name/Task Task Scheduling Tool RecommendedFrequency


E-mail job ABAP Every minute For more informationabout sendingmessages toe-mail, see the installationguide.

Delete expired inboxitems

ABAP Daily Deletes messages thathave been set to expire.

Reorganize andreconciliation job

ABAP Monthly or greater Reconciliation of deletedmessages in BusinessWorkplace and event andnotification.

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

34/60 PUBLIC 04/23/2012

5 Software Change Management

5 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, andtesting procedures for complex software landscapes and multiple software development platforms.These functions support your project teams, development teams, and application support teams. Thegoal of Software Change Management is to establish consistent, solution-wide change managementthat allows for specific maintenance procedures, global rollouts (including localizations), and openintegration with third-party products. This section provides additional information about the mostimportant software components.

5.1 Transport Management

Transports allow you to move an environment across a landscape. For example, you can transport anenvironment from a development system to a test system and then to a production system.Two modes of transport are supported:

n Normal mode ‒ For modifying and creating objects. In this mode, if a transported object exists inthe target system, it is modified with the changes from the source system. If it does not exist, itis created.

n 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 entireenvironment. You can transport one or more models at a time, and select individual components of amodel, for example, dimensions, members, logic script files, work status, reports, and so on). You cantransport the deletion of models, dimensions, Data Manager packages (deletion includes renaming,moving and deleting a package), Data Manager package groups (deletion includes renaming anddeleting a package group) and Data Manager package links.You can also collect NetWeaver objects into a transport request, such as NetWeaver process chains. Tomove process chains into your production environment, use the SAP NetWeaver transport process forprocess chains. The process chain must be assigned to component /cpmb/BPC.The following subsections contain a description of the transport process and some other usefulinformation about transporting. If you have problems with transports, see Troubleshooting Transport[page 51].

04/23/2012 PUBLIC 35/60

5 Software Change Management5.1 Transport Management

5.1.1 Transport Objects

This section lists the objects that you can transport for environments and models.Environment ObjectsYou can transport the following objects for an environment.

n Business Rule

n Configurationn Dimension

n Model

n Script Logicn Task Profile

Model ObjectsYou can transport the following objects for a model.

n Books Templaten Business Process Flow Templaten Business Rule

n Business Unit

n Configurationn Control

n Data Access Profile

n Data Manager Conversion Filen Data Manager Data Filen Data Manager Packagen Data Manager Package Groupn Data Manager Package Linkn Data Manager Transformation Filen Dimension

n Dimension Master Data

n Drill Throughn Journal Templaten Report Filen Report Templatesn Script Logicn Task Profile

n Team

n Web Documents

n Work Status Settings

36/60 PUBLIC 04/23/2012


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 toorganize development projects in the ABAP Workbench and in Customizing, and then transport thechanges between the SAP systems in your system landscape.For more information, see the SAP NetWeaver Technical Operations Manual on SAP Help Portal athttp://help.sap.com SAP NetWeaver .

PrerequisitesYou are the SAP NetWeaver administrator.

Procedure

1. Configure the SAP NetWeaver transport framework by creating transport domains, routes, andother aspects of a transport.For information, see Change and Transport System in the SAP NetWeaver Application Help on theSAP Library at http://help.sap.com.

2. Configure the system to import Client-Dependent Objects, as all Planning and Consolidationdata is client-dependent. Do the following:n Create User ALEREMOTE (BW Background User)n 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 forthis client.

For information, see Importing Client-Dependent Objects in the SAP NetWeaver Application Help on theSAP 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 forthe granular selection of objects. Only the objects that you select are transported. You can transportobjects with or without corresponding dependent objects. However, if you transport an object but donot include its dependent objects in the transport, a warning is generated.

04/23/2012 PUBLIC 37/60

http://help.sap.com

http://help.sap.com

http://help.sap.com


Recommendation

We recommend that you do not add a normal transport and a deletion transport for the sameenvironment 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 objects to transport:

a) In the left column, select SAP Transport Object Types .b) In the middle column, select More Types BPC Environment .c) Double-click Select Objects.d) In the dialog box, select the environment to be transported and click Transfer Selections.e) 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:

a) In the right column, click the Transport Objects button.b) In the dialog box, click the Create Request button to generate a new customizing request, then

click the Continue button.c) In the next dialog box, enter the description and transport target, then click the Save button.d) Click the Continue button to generate the customizing request. The selected objects are included

into the request.e) Enter transaction code SE09 to open the transport organizer. Click Display.

5. Release the customizing task:a) Select the task under the customizing request you just generated.b) Click Release directly.

Transport ErrorsIf transport fails for an object, the changes for that object are not made in the target system. Theobject in the target system remains unchanged. This does not affect the transport of other objectsto 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 targetsystem. You can select the deleted objects to transport. However, you can only select deleted objectsfor which there are no dependencies.

38/60 PUBLIC 04/23/2012



Recommendation

We recommend that you do not add a normal transport and a deletion transport for the sameenvironment 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:

a) In the left column, select SAP Transport Object Types .b) In the middle column, select More Types BPC Deletion .c) Double-click Select Objects.d) In the dialog box, select the environment to be transported and click Transfer Selections.e) 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 byselecting or deselecting the corresponding object.

4. Generate a customizing request:a) In the right column, click the Transport Objects button.b) In the dialog box, click the Create Request button to generate a new customizing request, then

click the Continue button.c) In the next dialog box, enter the description and transport target, then click the Save button.d) Click the Continue button to generate the customizing request. The selected objects are included

into the request.e) Enter transaction code SE09 to open the transport organizer. Click Display.

5. Release the customizing task:a) Select the task under the customizing request you just generated.b) Choose Release directly.

Deletion ErrorsIf deletion fails for an object, the changes for that object are not made in the target system. Theobject in the target system remains unchanged. This does not affect the deletion of other objectsin 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 successfulcompletion of a transport request, as well as warnings and errors encountered during the transport.

ProcedureTo view a transport log file:

04/23/2012 PUBLIC 39/60



1. Select a released request.2. Click Transport Logs.

5.1.5 Transport Maintenance

There are certain maintenance tasks involved with transports.

FeaturesYou 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 environmentin development. All dimensions, dimension properties, and models are created in development. Adecision needs to be made for all other objects.Typically, all objects are created in development and transported to production. The exceptionsinclude security and teams, which typically are handled landscape by landscape.Additionally, the decision would need to be made for Workbooks (report templates and inputschedules). If this is done in development, then workbooks in production would be overwritten. Ifthis 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 theenvironment from Production to Development. You test the patch in Development. After the patchis 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 anotherconfiguration on the same model or environment that is transported at a later stage in the projectcycle.In this case, you should have two environments in development, one for new development, and onefor production support changes. When a production support change occurs, this should be done inboth 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/60 PUBLIC 04/23/2012


5 Software Change Management5.2 Development Requests and Development Release Management

5.2 Development Requests and Development ReleaseManagement

The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscape.It is an efficient method of transporting a selected number of requests into a group of transporttargets, 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 athttp://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 foundin the Release Information Notes (RIN) for each SP.Support packages for components based on the SAP NetWeaver Application Server (ABAP) (such asCLM) are applied using the Support Package Manager.Detailed instructions about applying a support package stack to SAP NetWeaver aregiven in the SAP NetWeaver Support Package Stack guides on SAP Service Marketplace athttp://service.sap.com/instguides.SAP Notes that require code changes for components based on the SAP NetWeaver ApplicationServer (ABAP) can be applied using the SAP Note Assistant. For more information, seehttp://service.sap.com/note-assistant.

04/23/2012 PUBLIC 41/60

http://help.sap.com


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

6 Troubleshooting

6 Troubleshooting

6.1 Troubleshooting in Planning and Consolidation

The following table lists common Planning and Consolidation problems that you may encounter, aswell as suggestions for troubleshooting and resolving the problem:

Problem Analysis Solution

Marginal text and buttons inPlanning and Consolidation dialogboxes are unreadable or incorrectlyformatted.

Determine the DPI font settings inthe host computer.

On the Settings tab in the MicrosoftWindows Display Properties dialogbox, chooseAdvanced. On the Generaltab, ensure that the DPI setting is 96DPI.

6.2 Analyzing Problems Using Solution Manager Diagnostics

The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution ofproblems. For information about setting up Solution Manager Diagnostics, see Connecting to SolutionManager Diagnostics in the Planning and Consolidation NW Installation Guide.

6.3 Installing Appsight Black Box Service

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.n Triserv2.rpr

BlackBox profile that is used by the application. This profile outlines the type of process forBlackBox to monitor. This filename must match the one that is in the startservice.bat file.

n Triserv_XpressServer.rprThe Xpress Server profile. This filename must match the one that is in the startservice.batfile.

4. Install AppSight Black Box Service in standalone mode.a) Run AppSight Black Box Service.exe.b) Select Install.

04/23/2012 PUBLIC 43/60


6 Troubleshooting6.4 Generating and Analyzing Trace Files Using E2E Trace

c) Accept the agreement and choose Next.d) Enter any information for username and company name and choose Next.e) Leave the server prompt blank for standalone mode and choose Next.f) 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 thelog. Stopservice.bat stops the Blackbox application. You must stop the application before youcan 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 willwrite all the information from the application. The computer name and date are used as a variablefor 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 theapplication 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 usingE2E Trace. Trace files collect information about client and server interactions presenting traceinformation about the entire request and response of a business process step. The trace files thenupload to the server for analysis in SAP Solution Manager Diagnostics (SMD). Client side and serverside trace information is displayed in the E2E Trace application in SMD.E2E Trace is delivered and installed with Planning and Consolidation. To configure and activatetracing 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 thetrace in the E2E Trace Analysis - User Guide in the Diagnostics section of SAP Service Marketplace.

Prerequisites

n Ensure that the latest Planning and Consolidation Clients with the E2E Trace plug-in are installedon your client machine.

n The minimum release on the SAP Solution Manager Diagnostics side for E2E Trace Analysisis Solution Manager 7.0 EhP 1 SP23.

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

44/60 PUBLIC 04/23/2012

6 Troubleshooting6.4 Generating and Analyzing Trace Files Using E2E Trace

n Enable tracing in the ABAP back-end systemn Perform a trace in the Administration module

n Perform a trace in the Microsoft Excel module

n Manually upload the trace file to SMD if not done automaticallyn 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. SelectMicrosoft Office Excel and choose Launch.3. After Excel is launched, enter the following values in the E2E Trace Plug-in user interface:

a) Enter a name for your trace in Business Transaction Name.After uploading the trace to SMD, you locate the trace by this name.

b) Set the Session Trace Level to High.c) Enter the SMD server host.d) Enter the SMD HTTP port.

4. Click Log On in the EPMmenu 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 FileIf 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 theManually upload section.2. Choose Browse under Upload BusinessTransaction.xml. The file to upload appears in <trace plug-in

folder>\Logs.3. Select the BusinessTransaction.xml file and choose Upload.

04/23/2012 PUBLIC 45/60

6 Troubleshooting6.5 Logging and Tracing Configuration

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 application5. 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 toenable 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 theMessage 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:n To view Introscope Transaction Trace data, select a line with incoming http calls, then choose

Display Introscope Transaction Trace.n To view ABAP Trace data, select a line with incoming RFC calls, then choose Display aggregated

ABAP Trace.n To view ABAP SQL Trace data, select a line with incoming RFC calls, then choose Display ABAP

SQL Trace Summary.

More Information

n Logging and Tracing Configuration [page 46]n 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 tracefiles in the Log Viewer tool of Solution Manager diagnostics after performing the configurationdescribed below.You can create log and trace files for the client.

46/60 PUBLIC 04/23/2012

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 ispredelivered for the client.

Features

The Log Configuration File

As delivered, this file contains the following statements:

>>> MISSING TARGET TEXT FOR TEXT-ID: 'SourceCode' (language: en) <<<

<?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 thelog-configuration.xml file.

Trace Settings

The following table explains the parameters of the Trace Setting part of the log-configuration.xmlfile.

Parameter Default Value Meaning

TraceSeverity ERROR You use the trace severity tocontrol the number of tracerecords that are produced.The following trace severity levelsare supported:

04/23/2012 PUBLIC 47/60



n DEBUGn PATHn INFOn WARNINGn ERRORn DONOTHINGChoosing a severity level meansthat trace records with the chosenseverity, together with all more.severe trace records, are writtento the trace file. For example,choosing INFO means that allinformation, warning, and errortrace records are written to the file.DONOTHING is a special severitylevel. If you set it as value, no tracerecords are written to file. This iseffectively switching off Trace.If you set another value forTraceSeverity, for example, ERR,it is treated as DONOTHING.

TraceDestination Empty The location where you wantto store the trace files. Forexample, <TraceDestinationvalue=“C:\Program Files\SAP

BusinessObjects\PC_NW\Logging\Trace”>.

MaxTraceSize 10 The maximum size of single tracefile. The unit is MB.

TraceFileCount 10 Trace files are namedBPCtrace.x.logwhere x is anumber between 0 and one lessthan the TraceFileCount.The first trace file to be written isBPCtrace.0.log

. When this file reaches theMaxTraceSize, the next file,BPCtrace.1.log, is started.This continues until thereare TraceFileCount trace files,whereupon the system overwritesBPCtrace.0.log.

TraceUser Empty The default means that the systemwrites trace records for all users.You can also create trace recordsfor a specified user.

48/60 PUBLIC 04/23/2012


Log Settings

The following table explains the parameters of the Log Setting part of the log-configuration.xmlfile.


LogSeverity INFO You use the log severity to controlthe number of trace records thatare produced.The following log severity levelsare supported:n INFOn WARNINGn ERRORn DONOTHINGChoosing a severity level meansthat trace records with the chosenseverity, together with all more.severe log records, are written tothe log file. For example, choosingINFO means that all information,warning, and error log records arewritten to the file.DONOTHING is a special severitylevel. If you set it as value, no logrecords are written to file. This iseffectively switching off Logging.If you set another value forTraceSeverity, for example, ERR,it is treated as DONOTHING.

LogDestination Empty The location where you wantto store the log files. Forexample, <TraceDestinationvalue=“C:\Program Files\SAP

BusinessObjects\PC_NW\Logging\Log”>.

MaxLogSize 10 The maximum size of single logfile. The unit is MB.

LogFileCount 10 Log files are namedBPClog.x.logwhere x is a numberbetween 0 and one less than theLogFileCount.The first log file to be written isBPClog.0.log

. When this file reaches theMaxLogSize, the next file,BPClog.1.log, is started.This continues until thereare LogFileCount log files,

04/23/2012 PUBLIC 49/60



whereupon the system overwritesBPClog.0.log.

Application Set Settings

The following table explains the parameters of the Application Set Setting part of thelog-configuration.xml file.


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 defaultvalues. 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 Planningand Consolidation detects these empty fields at user logon, it uses <TraceDestinationvalue="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 orLogDestination.

Change the number log or trace records Change the value of TraceSeverity or LogSeverity.

Switch off log or trace Set the TraceSeverity or LogSeverity toDONOTHING.

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.

50/60 PUBLIC 04/23/2012

6 Troubleshooting6.6 Troubleshooting Transport

6.6 Troubleshooting Transport

Transports allow you to move an environment across a landscape. For example, you can transportan environment from a development environment to a test environment and then to a productionenvironment.For detailed information about how to use SAP transports, refer to Transport Management [page 35].

FeaturesThe following are some specific situations where you may require some additional information ortroubleshooting assistance.

Deleting Objects

The two major object types exhibit different behavior patterns during the import of a transportinto the target system.

n Table entries and data model objects (model, dimensions, properties) are deleted in the targetsystem when they are deleted in the development system and the environment is transported.

n Files such as script logic and Excel templates are only updated. that is, changes to these files aretransported. Since only updates are transported, deleting files in the development system does notimpact existing files in the QA or production systems. Similarly, deleting files in the target systemdoes not cause any harm.

After deleting an environment, you can make sure that all data has been removed. Use programUJT_CHECK_TABLE_ENTRIES to check howmany records exist in the UJ* database tables for a particularenvironment.

Choosing Transport Strategies

There are many SAP transport strategies. Frequently, a QA or production system is built with everyreleased 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 andtransported 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 containdevelopment, QA, and production instances. If you change objects in a target system, the transportsthat originate from development will no longer import correctly.

04/23/2012 PUBLIC 51/60

6 Troubleshooting6.6 Troubleshooting Transport

Data model changes consist of objects such as environment, model, dimensions, or properties. Acustomer can maintain the data model in the QA or production system, but this means that thecustomer 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 modelrelated), can be changed in any instance.

Changing Data Model Objects

Do not change the structure or definition of Planning and Consolidation related data model objectsin BW. This includes objects such as environment (InfoArea), model (Multiprovider and InfoCube),dimensions (InfoObjects), and properties (InfoObjects). This causes subsequent transports to fail.

Changing Technical Names

The technical name of the InfoCube or Multiprovider may change between landscapes. This isnormal. Planning and Consolidation does not transport technical names of cubes and the transportworks 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

found1. Enter transaction code RSOCONTENT.

2. Ensure that System is a Content Development System isnot 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 tableUJT_TRANS_OBJECT.

2. Delete all the D version records for yourenvironment in this table.

3. Reimport the request.

Import failed with the error: Failed to create BI

InfoObject for dimension1. Enter transaction code RSA1

2. check if there are any customer-createdInfoObjects or InfoCubes that refer to theattributes of the failed dimension.If so, break the references between Planning andConsolidation InfoObjects and your InfoObjectsand InfoCubes.

3. Reimport the transport request.

52/60 PUBLIC 04/23/2012


6 Troubleshooting6.7 Component-Level Logs

Scenario Solution Actions

Import failed with the error: Dimension /CPMB/XXXX

already exists

Check if anyone has transported this dimensionthrough the BW back end manually. If so, performthe following steps:

1. Delete the InfoObjects in the BW back end (usetransaction code RSD1) on the target system.


Import failed with the error: Failed to create

infoarea1. Enter transaction code SE06.

2. Change the namespaces /CPMB/ and /B28/ to bemodifiable.


More InformationSAP 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 theapplication 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>

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 parameterpp-enable-debugging=truemust be set and the URL query parameter debug=truemust beused 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 serverparameter pp-support-mode=truemust be set and the URL query parameter support-mode=truemust be used when launching the application.For example: http://<host>:<port>/sap/fcprt?app-config=<app config

name>&support-mode=true

04/23/2012 PUBLIC 53/60



5. How do I see status of the various plug-ins and the reasons why some plug-ins are notloaded?As a prerequisite, enable the support mode.n 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 theloaded plug-ins, the state of the plug-ins and the error information for plug-ins that couldnot be loaded.

6. How do I see the version information of the plug-ins?As a prerequisite, enable the support mode.n 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 theversion 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=truemust be set andthe URL query parameter show-trace=truemust 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). Toconfigure which levels of statements to be logged, set the FCP server parameter pp-log-filter toone of the appropriate values (ERROR|FATAL|SUCCESS|WARNING|INFO|NONE|*)For example: To enable only statements with levels ERROR and FATAL to be logged, setpp-log-filter=ERROR|FATAL

8. How do I enable the startup trace in the application?As a prerequisite, enable the tracing on the client.When launching the application, use the URL query parameter show-trace=startup. During theloading 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 displaysthe logs and traces. The dialog also provides an option to transmit the client logs to the serverand 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 theMIME Repository and open SAP POA FCPContainer . Download the POASBCBUI00_0.sca file.

54/60 PUBLIC 04/23/2012


The version information is available in the SAP_MANIFEST file in the MANIFEST folder of thesca archive file.

Setting Up Support UserCreate a role, <DISPLAY_USER ROLE>, with limited READ rights using /POA/A_BUI authorizationobject 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

/POA/PSAPP:*

/POA/PSACT:CREATECHILD

/POA/ACDTP:*

/POA/AUTHT:F

04/23/2012 PUBLIC 55/60

6 Troubleshooting6.8 Troubleshooting for CLM

If the application is used with sub namespaces, you also need to assign /POA/A_BPT authorizationobject to the role with the same field values as for /POA/A_BUI authorization object. You need anadditional 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: RAssign 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 contentgroup extracts, where the content group is in error status, in the Content Lifecycle Managementapplication. It allows you to display the content group metadata and to see the breakdown ofcontent 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 theinstallation guide.

56/60 PUBLIC 04/23/2012

7 Support Desk Management

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 acustomer message in the SAP Support Portal. For information about SAProuter, see the followingSAP Note:

SAP Note Title Comment

486688 Schedule VPN connection to SAPnetwork

See also the SAP Notes that this SAPNotes refers to for specific settingsor parameters that are necessary

For further assistance, see the following SAP Note:

SAP Note Title Comment

812386 RFC connection to the SAPNet R/3front end

-

7.2 Problem Message Handover

Problemmessages can be logged at SAP Support Portal on SAP Service Marketplace, which is locatedat 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 reduceprocessing time, since their use removes the need for SAP Support to dispatch your message tothe appropriate support personnel.

The following component strings are available:

Component String Area

EPM-BPC-NW Planning and Consolidation as a whole

04/23/2012 PUBLIC 57/60



http://service.sap.com/

7 Support Desk Management7.2 Problem Message Handover

EPM-BPC-NW-DOC Documentation

EPM-BPC-NW-TRA Transport

Administration: EPM-BPC-NW-ADM


EPM-BPC-NW-ADM-APP Application Management

EPM-BPC-NW-ADM-DIM Dimension Management

EPM-BPC-NW-ADM-K2 K2 Script Logic

EPM-BPC-NW-ADM-SEC Security

EPM-BPC-NW-ADM-TDL Table Driven Logic

EPM-BPC-NW-ADM-WS Work Status

Data Manager: EPM-BPC-NW-DM


EPM-BPC-NW-DM-PAC Package Management

EPM-BPC-NW-DM-RUN Package Execution

EPM-BPC-NW-DM-SCH Schedule

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

58/60 PUBLIC 04/23/2012

7 Support Desk Management7.2 Problem Message Handover

Content Lifecycle Management


XAP-SBC-CLM Content Lifecycle Management

04/23/2012 PUBLIC 59/60

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

© Copyright 2012 SAP AG. All rights reserved.Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigungdurch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.