n

n
n
n
n




































“ ”








™ ’





“ ”










n


n

n

n

n











¸


































































































































































































¸
































¸




































¸











































n

































n

n




n



























n

n


n

n

n

n

n
— —
n




























































































¸


















































¸ ¸
¸



¸





n

n

n

n

n






n

n




n

n





n

n

n

n







n

n















































































n

n

n

n





































‒ ‘ ’
¸





‒ ‒







‒ ‒












‒ ‒





‒ ‒

‘ ’
‘ ’



‒ ‒







‒ ‒





‒ ‒



‚ ‘


‒ ‒







‒ ‒



‒ ‒










’ ’


‒ ‒


‚ ‘





































n






l







n






l


l


l


l

n



n




n








n

n

n

n

n

n

l

l

l

l

l
¸





’ ’
’ ’ ’ ’ ’ ’ ’ ’ ’ ’
’ ’ ’ ’ ’ ’ ’ ’ ’ ’






n

n

n

n

n

n

l

l

l

l

l
¸


’ ’
’ ’ ’ ’ ’ ’ ’ ’ ’ ’
’ ’ ’ ’ ’ ’ ’ ’ ’ ’

¸







n
¸
n

n

n




n




























¸


























n




n
























¸










¸



















































n



n

















¸



n

n

n

n

n

n



n

n

n

n

n

n

n

n

n

n

n

n

n

n

n

n

n

n

n

n

n

n

n

n




















n

n


























¸


































¸










































































































¸
¸

n



n













¸


















¸



n


n







n

n

n

n

n












¸ ¸ ¸



























¸











n


n


n



n
¸
n















































n

n

n

n

n

n




















































n

n

n

n












































































¸


n


n




























¸

















’ ’






























































n

¸
¸




n

¸
¸




























































































































































SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +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 permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2 from Michael Kay (http://saxon.sf.net/), XSLT version 1.
Disclaimer

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

2/60

PUBLIC

04/23/2012

Typographic Conventions

Example
<Example>

Description

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 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 n Output on the screen following a user action, for example, messages n Source code or syntax quoted directly from a program n File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard

Example Example Example
Example

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

04/23/2012

PUBLIC

3/60

version for SAP NetWeaver . make sure you have the latest version of this administrator’s guide.0.Document History Caution Before you start the implementation. You can find the latest version at the following location: http://service.0 4/23/2012 Version 1.com/instguidesEPM-BPC 10. The following table provides an overview of the most important document changes.0 to accompany GA release 4/60 PUBLIC 04/23/2012 .sap. Version Date Description 1.

Cube Modification . . . . . . . . . . . . .1. . . . . . . . . . . . .1 4. . . . . . . . . . . . . . . . . . . . . . . . Management of Planning and Consolidation Starting and Stopping . . . . . . . .5. .5.1 3. . CLM Configuration . .5. . . . . . . . . . . . Writeback Parameters . . . .4 3. . . . . . . . . . .3 3. . . . . . .5. . . . . . Data Consistency for CLM . . . .3. .1. . Component-Specific Monitoring . .5 4. . . . . . .4 4.3. . . . . . . .4 3. . . . . . . . . . . Enabling the Auto-Alert Mechanism in CCMS . . . . . . . . . . . . . . . . . . Trace File for Debugging Logic . . . . . .5. . . . . . . .2 3. . . . . . . Backup Best Practices . . . .3 3.5. . . . . . .1 3. . . . . .1. . Workload Monitors . . . . . . . . . . . . . . .1 4.6 4. . . .3 4. . . .2 3. . . . . . . . . . . . . . . Trace and Log Files for Content Lifecycle Management . . . .1. . . . . Problem Analysis for CLM . . . . . . . . . . . . . . . . .5.2 4. . . . . Processing Tiers . . . . . . . . . . . . . . . .5 3. . . Administration Tools . . . . . . . 04/23/2012 PUBLIC 5/60 . . . . . . . . . . . . . . .6 Getting Started . . . . . . . . . . . . Best Practices for Performance Management . . . SQE Parameters . . . Availability Monitoring . . . . . . .5 3. . . . . . . 7 9 11 11 12 12 13 14 14 15 15 15 16 16 16 17 17 18 19 21 21 21 22 22 22 23 23 23 24 24 25 29 Important SAP Notes . . . . . . . . . . . . . . .6 Chapter 4 4. . . . . . . . .5 4. . . . . Setting up a Minimal-Access User to Configure SMD . .3. . Interface Monitors for CLM . . Monitoring of Planning and Consolidation . .2 4. . . . . . . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Manager Log Files . . . . . . . . . . . . . . . . . . . .5. . . . . . . . . . . . . . . .3.2 3. Cube Fact Tables . . .1. .4 4.5 3. . . . . . . . . . .5. . .5. . . . . . Data Growth and Archiving Monitors . . . . . . . . . .1 3. . . . . . . . . Cube Optimization .3. . . . . . . . . . . . .3 4. . . . . . . . . . .3 3. . Trace and Log Files for Context & Insights . . . . . . . . . Set Up of BPF E-mail Notifications . . . . . . . .3. . . . . . . . .4 3. . . . . . . . .Table of Contents Chapter 1 Chapter 2 Chapter 3 3. . . . . Logging of Exceptions in the SLG1 System . . . . . . . . . . . Detailed Monitoring and Tools for Problem and Performance Analysis Trace and Log Files . . . . . . . . . . .

Transport Objects . . . . . . Installing Appsight Black Box Service . . . . . . . . . . . . .5. . Utilities for CLM .3 5. . . .1 5. Development Requests and Development Release Management Quality Management and Test Management for CLM . . . . . . . . . . . Support Packages and Patch Implementation . .6. . .1 7. . . . . . . . . . Troubleshooting for CLM . .1. . . . . . .6 5. . . . .2 5. . . . . Component-Level Logs . . Transport Management . . .6. . . .5. . . . . . . . Analyzing Problems Using Solution Manager Diagnostics . . . . . . . . . .2 4. . . . . . . . . . . . . . . . . .1 6. . . . . . . . . . . . . . . . . . . . . . . . . . . Generating and Analyzing Trace Files Using E2E Trace . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . .4 Chapter 6 6. . . . . . . . . . . .6 6. . . . . . . . . . . . . . . . . Transporting Environments .7 4. . . Troubleshooting Transport . . . . . . . . . Load Balancing .4 6. . . . . . . . . . .1 5. . . . . . . 6/60 PUBLIC 04/23/2012 . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . .5 6. . . . . . . . . . .7 6. . . . . . . . . .4 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 6. . . . . . . .1. . . . . . . .2 Logs .8 6. . .3 5. . . . . . . . . Remote Support Setup .1 6. . . . . .3.9 Chapter 7 7. . . . . . . . . . . . . . Troubleshooting for Event & Notification . . Transport Log Files . . 29 32 32 32 33 33 34 35 35 36 37 37 37 38 39 40 40 41 41 41 43 43 43 43 44 46 47 50 51 53 56 56 57 57 57 Software Change Management . . . . . . . . . .2 5. .9 Chapter 5 5. . Backup and Restore . .1. . . Scheduled Periodic Tasks for CLM . . . . . . . . . . Transport Configuration . . . . . . . . . .1 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 6. . . . . . Support Desk Management . . . . . . . .1.1 4. . Logging and Tracing Configuration .5 5. . . . . . . . . . . Transport Deletion . . . . . . . . . .1. . . . . . . Client Configuration . . . . . . . . . . . . . . . . . .2 6. .1. . . . . . . . . . . . . . . . . . .4. . . . . . . .1. . . . . . . . . . .8 4. . . . . . . . . . . . Transport Execution . . User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 4. Problem Message Handover . . . . . . . . . . . . Deployment Scenarios . Troubleshooting in Planning and Consolidation . . . . . . . . . Transport Maintenance . Logging and Tracing Parameters . .1. . . . . . Scheduled Periodic Tasks for Event & Notification . . . . . . . . .3 4. . . . . . . .2 5. . . . . . . . .6. . . . . . .6. . . . . . . . .

sap. It contains specific information for various tasks and lists the tools that you can use to implement them.sap. This guide also provides references to the documentation required for these tasks. About this Guide Designing.com 04/23/2012 PUBLIC 7/60 . The following SAP NetWeaver documentation is relevant for Content Lifecycle Management: Document Found At Technical Operations Manual for SAP NetWeaver Monitoring Setup Guide for SAP NetWeaver SAP NetWeaver Security Guide SAP Service Marketplace at http://service. implementing.com/instguides SAP Service Marketplace at http://service.sap.com/securityguide SAP SAP NetWeaver Solution Life Cycle Management by Key Capability SAP Help Portal at NetWeaver http://help. and running Planning and Consolidation at peak performance 24 hours a day has never been more vital for your business success than now. This guide provides a starting point for managing Planning and Consolidation solutions and maintaining and running them optimally.sap. so you will sometimes also need other guides such as the Master Guide and SAP Library.com/instguides SAP Service Marketplace at http://service.1 Getting Started 1 Getting Started Caution This guide does not replace the daily operations handbook that we recommend customers create for their specific production operations.

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

SAP Planning and Consolidation This note contains installation information. and resolved issues for SAP Planning and Consolidation 10. 10.0 SP03. Important SAP Notes SAP Note Number Title Comments 1586088 Planning and Consolidation 10. and resolved issues for SAP platform Planning and Consolidation 10.0 SP02. enhancements. version for the NetWeaver enhancements. and resolved issues for SAP platform Planning and Consolidation 10.0 SP06.0 for NetWeaver Documentation Addendum Contains information that does not appear in the application help of Planning and Consolidation 10.0 SP02. version for the NetWeaver enhancements. version for the NetWeaver enhancements.0 SP05.0. version for the SAP NetWeaver platform.0 SP01. 10.0 SP05. SAP Planning and Consolidation 10. version for the NetWeaver platform This note contains installation information. 10. version for the SAP NetWeaver platform. SAP Planning and Consolidation This note contains installation information. 1660062 SAP Planning and Consolidation This note contains installation information. and resolved issues for SAP platform Planning and Consolidation 10. version for the NetWeaver enhancements. version for the NetWeaver enhancements.0 SP04. 10. SAP Planning and Consolidation This note contains installation information. version for the SAP NetWeaver platform. version for the SAP NetWeaver platform. and resolved issues for SAP platform Planning and Consolidation 10. version for the SAP NetWeaver platform. and resolved issues for SAP platform Planning and Consolidation 10. 1627973 1615237 1597468 1580564 1573567 04/23/2012 PUBLIC 9/60 .0 SP01.0 SP04. 10. SAP Planning and Consolidation This note contains installation information.0 SP06. version for the SAP NetWeaver platform.2 Important SAP Notes 2 Important SAP Notes Caution Check regularly to see which SAP Notes are available for this Administrator’s Guide. version for the SAP NetWeaver platform.0 SP03.

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

as the central monitoring system can be configured to link CCMS monitoring from application systems.3 Monitoring of Planning and Consolidation 3 Monitoring of Planning and Consolidation You use the monitoring capabilities of SAP NetWeaver to monitor Planning and Consolidation. CCMS monitoring capabilities are restricted to the local system and as CLM involves interactions with more than one system in a typical landscape. who performs these monitoring and diagnostic services.30. see SAP Help Portal at http://help. In this case.com/instguides. For more information about monitoring in the CCMS. The user. Monitoring for Content Lifecycle Management By default. Recommendation Since the application is powered by SAP NetWeaver 7. Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions. it may be advisable to create a user with 04/23/2012 PUBLIC 11/60 . Proficient knowledge of system monitoring and basic knowledge of SAP NetWeaver is required to compose user-defined monitors. Since currently CLM only communicates with ABAP-based systems. This contains all the information relevant to monitor the SAP NetWeaver components used in the application.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.sap. 3.sap. we recommend that you set up the monitoring infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplace at http://service.com SAP NetWeaver . Therefore. The aim of this section is to provide information and documentation to monitor the application. RFC connection type can be used to enable monitoring across multiple systems. with the Central Computing Management System (CCMS). for example by utilizing the Computing Center Management System (CCMS) and NetWeaver ABAP monitoring tools. does not need to be able to manipulate the Planning and Consolidation data. CLM. such as monitoring. it could be beneficial to monitor other systems through CCMS from central CLM system.

3 3. To enable the auto-alert mechanism of CCMS. This displays details of the team. see Connecting to Solution Manager Diagnostics in the Planning and Consolidation Installation Guide. see the following SAP Note: SAP Note Number Title Comment 617547 RZ20: Sending alerts as mail and SMS You want to send alerts from the CCMS monitoring architecture (transaction RZ20) as an e-mail. Choose Finish. 2. For information about setting up SMD. task profile and data access profile assignments for the user. Procedure 1. 4.2 Monitoring of Planning and Consolidation Enabling the Auto-Alert Mechanism in CCMS minimal access rights and configure SMD to access Planning and Consolidation with this user.3 Availability Monitoring A simple Generic Request and Message Generator (GRMG) scenario for SAP Planning and Consolidation is available.2 Enabling the Auto-Alert Mechanism in CCMS The basis for application-specific alert monitoring is NetWeaver CCMS alert monitoring framework. SMS or other message type to one or several recipients. In the Add User assistant. and presents the status of its current availability. check that the user has no teams or profiles assigned to it. Choose Security Users and then select Add new user from the Session Information action pane In the Users view. select the user to add in the environment Choose Next at all remaining steps of the assistant without assigning the user to a team. This checks the availability of the SAP Planning and Consolidation application server. select Add. 7. 3. 12/60 PUBLIC 04/23/2012 . 5. 3. Log on to the EnvironmentShell environment through the Admin client. In the Users. Features In the Central Monitoring System (CEN) you can load the Planning and Consolidation template customizing file and start the GRMG scenario to monitor availability of the application server. Select the user and choose Edit. 6. The following procedure describes the creation and configuration of such a user. 3. Configure the SMD connection to Planning and Consolidation to use this user.

To configure the GRMG scenario for Planning and Consolidation. edit the template customizing file BPCNW_Customizing. 2. 7. and number of currently logged-in users can be observed. perform the following steps: 1. This is the connection to the system where the application is installed and in use. For example.4 Component-Specific Monitoring Existing CCMS monitoring sets can be used to monitor various resources. Log on to the Central Monitoring System (CEN). as well as the username and password. Choose Start. Using a suitable XML editor. enter /nRZ20 and press Enter.4 Monitoring of Planning and Consolidation Component-Specific Monitoring Note For availability monitoring. To do that. objects. which can be used to monitor system. The monitor presents its status and alerts according to the presence of error messages in the SAP Planning and Consolidation log.xml. database. and background processing for the application server where the application is running. Operating System Monitoring Operating system monitoring capabilities within CCMS administration workplace are used to analyze CPU. SAP CCMS monitor template. see Setting up a Minimal-Access User to Configure SMD [page 11].3 3. The following existing monitors within RZ20 can be used by the application to monitor critical conditions: Database Monitoring You can monitor the RDBMS connection using the CCMS database monitor. you can display them in transaction CCMS by selecting Open Alerts. and performance. 5. network time. and their corresponding health statuses. paging. 3. file system. disks. You must specify the URL of the scenario (host and port). 6. Go to transaction GRMG. Dialog Overview Using dialog monitoring in RZ20. memory. 3. Save your entries. Choose Upload and select the relevant scenario. in the execution text field in the upper left corner. the response time for dialog. 4. to verify the content is correct. If errors occur in this log. Error Monitoring The log file for SAP Planning and Consolidation is monitored for error patterns. set up and use a Planning and Consolidation user with minimal access privileges for monitoring and diagnostics related web services. For more information. Monitors for Content Lifecycle Management Dialog Overview 04/23/2012 PUBLIC 13/60 . such as GRMG web services. choose Edit/Delete. Once the scenario is uploaded.

DB - Transaction ST01 Transaction ST05 All logs related to runtime exceptions are recorded. HTTP. 3. and number of roundtrips against CLM Web Dynpro application /POA/WD_CLM. status updates). These are useful for problem and performance analysis. background jobs are created for a content group. These messages are for viewing and analyzing in the administrator tool for the application - System Trace Analysis — RFC.3 3.5 Monitoring of Planning and Consolidation Detailed Monitoring and Tools for Problem and Performance Analysis For CLM. Note Transaction SM37 can be used to monitor background jobs initiated by CLM. There is an option to export the messages to the server. number of free or occupied work processes. CCMS view for background processing under Content Lifecycle Management Monitor Set can be used to retrieve statistics such as a list of long-running background jobs. session timeouts.5 Detailed Monitoring and Tools for Problem and Performance Analysis This section describes the trace and log files. Messages are also shown in the common message region in the top-right corner of the container. n Check BUI log in SLG1 14/60 PUBLIC 04/23/2012 . Background Processing For extraction and deployment scenarios in CLM. Traces are enabled through log message APIs Log messages on client N/A side are in memory. This view is also part of the delivered CLM-specific Content Lifecycle Management Monitor Set. and any CLM job that was stopped abruptly. you can observe Web Dynpro ABAP-related attributes such as date transferred. and monitors that you can use for detailed monitoring. 3. DB SQL Performance Trace and Analysis — RFC.5. Component Content File Path Core components and services Log messages pertaining to workflow (alerts.1 Trace and Log Files The following table describes the trace and log files for the application components. fatal messages. errors. HTTP.

Example The following script refers to an invalid member.3 Data Manager Log Files Whenever you use a Data Manager package to move Planning and Consolidation data. This allows for improved tracing and diagnosis of any exceptions that occur. The name of the log file contains the following details: n The name of the package n A timestamp 04/23/2012 PUBLIC 15/60 . the system creates a log file.5. 3. relevant information is logged in the SLG1 system. 3.JAN *REC(FACTOR=1.5.5. The detailed information is written in the log item and saved in the database.log and stored in <drive>\webfolders\<environment>\<model>\privatepublication\<username>\<date>. In the log.1. We recommend that this is only used by experienced Planning and Consolidation consultants and support.1. The activity is recorded in a file called debuglogic.5 Monitoring of Planning and Consolidation Detailed Monitoring and Tools for Problem and Performance Analysis 3. the object is identified as UJ and the subobject is identified as UJK.2) *ENDWHEN This generates an exception and produces the following message in the log: Member "A1000" not exist. These logs are stored in <Drive>\webfolders\<environment>\<model>\privatepublication\<username>\tempfiles.1. We recommend that these files are removed once the packages have completed since they take up a considerable amount of space. We also recommend that these files are removed periodically since they take up a considerable amount of space. A1000: *XDIM_MEMBERSET ENTITY=A1000 *WHEN TIME *IS 2006.1 Logging of Exceptions in the SLG1 System When an exception occurs.3 3.2 Trace File for Debugging Logic You can turn on tracing for script logic and business rules when you need to troubleshoot a particular script or rule. This file can be useful in troubleshooting the execution of packages.

1.log 3.1.5 Trace and Log Files for Content Lifecycle Management Content Lifecycle Management (CLM) does not provide any special tracing and log files facility as this can be easily obtained from the NetWeaver ABAP framework.LOG Example Validatetransformation20090915211503.2 Workload Monitors A default workload collector as part of CCMS monitoring and workload monitor through transaction ST03N can be used to observe the workload records at application server level. 3.4 Trace and Log Files for Context & Insights Component Content File Path Context REST Details about errors and exceptions in the communication with client - /POA/CTX/REST Context Service Details about errors and exceptions occurring within the context server /POA/CTX/SERVICE 3. It is essential to collect trace and log files for RFC calls.5.5 Monitoring of Planning and Consolidation Detailed Monitoring and Tools for Problem and Performance Analysis n The extension .3 3. Component Monitor Detailed Description Prerequisites - Workload Monitor — Transaction ST03N Detailed analysis of workload of application servers - 16/60 PUBLIC 04/23/2012 .5.5. CLM carries out critical operations through RFC protocol to extract and deploy the contents onto application systems.

3 3.5

Monitoring of Planning and Consolidation Detailed Monitoring and Tools for Problem and Performance Analysis

3.5.3 Data Growth and Archiving Monitors
Component Monitor Detailed Description Prerequisites

DB tables

ST05

Observe critical Switch the trace on operations and tables before performing costly that take more time along operations with their hit and miss ratio

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 service n /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 n n n n n /POA/D_CLM_CP02 — CLM Content group and Entity relationship /POA/D_CLM_DPLR — Table for storing entity processing messages /POA/D_CLM_ENT01 — CLM Entity Table /POA/D_CLM_ENT02 — CLM Entity Fields value Table /POA/D_CLM_ENT03 — CLM Entity — Entity Relationship /POA/D_CLM_ENT10 — CLM Entity Raw Data Extract Table

3.5.4 Problem Analysis for CLM
The monitoring sets from CCMS monitoring in RZ20 can help analyze most critical bottlenecks; however, the following table points to some problem-oriented scenarios and a recommended tracking mechanism for CLM:
CLM Scenario/Activity Problem Possible Causes Recommended Monitoring

Extraction of content from application system

Exception Occurred

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

Check system trace file (ST01)/ SM59 / SMT1 for trusted connections. CLM log in SLG1 Check background task in SM37 and CCMS CLM monitor SLG1 ‒ application log for CLM

Extraction in progress for Large amount of content a long time Validation errors Content in incorrect format

04/23/2012

PUBLIC

17/60

3 3.5

Monitoring of Planning and Consolidation Detailed Monitoring and Tools for Problem and Performance Analysis

CLM Scenario/Activity

Problem

Possible Causes

Recommended Monitoring

Importing content from a Exception occurred CLM package (zip) Time out

Malformed content or SLG1 ‒ application log for tempered content format CLM Package size is too big Check CCMS memory or buffer sizes to free resources, increase time out limits for profile parameters; usually cannot be resolved

Exporting CLM content to a package (zip) -

Exception occurred Time out

Content was changed SLG1 or check status of after including in package content group Content size is too big Remove huge attachments, split package into two smaller packages SLG1 ‒ application log for CLM, system trace file (ST01), SMT1 for trusted connections

Deploy Content

Exception occurred

Incompatible system for application deployment of content, RFC connection failure, system failure, no authorization for RFC calls, no trusted system Large amount of content

Deployment takes too long

SM37 or CCMS for CLM deployment and polling results background job Check target application system, ST22, for any exceptions, authorization failures Check DB locks in SM12 (table /POA/S_CLM_DEPLKEY)

Non recognized status in Failure on application deployment log deployment

No deployment possible

Existing deployment on target system already on going

3.5.5 Interface Monitors for CLM
Content Lifecycle Management (CLM) communicates with application system using RFC. For certain intensive operations, such as content extraction, interface monitors could be used to analyze the time spent on each RFC call.

18/60

PUBLIC

04/23/2012

3 3.5

Monitoring of Planning and Consolidation Detailed Monitoring and Tools for Problem and Performance Analysis

Interface

Detailed Description

Technology Used

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

ABAP Web Dynpro application uses these calls and interfaces at runtime

RFC

ABAP Web Dynpro application is accessed using HTTP

HTTP

3.5.6 Data Consistency for CLM
Content Lifecycle Management (CLM) is used as a repository containing application content. The content in the CLM repository can be added either by extraction from various application systems or by importing a new vendor-delivered package. During these operations CLM always loads the data first and performs validations on top of such content to report functional inconsistencies. If there are abrupt blockages, such as connection timeout, it can result in differences between the data maintained in CLM and data present in other sources.
Recommendation

In this scenario, we recommend rerunning the operation as there is no impact of this operation on any business function in CLM.

04/23/2012

PUBLIC

19/60

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

com SAP NetWeaver . For more information.sap.sap. 04/23/2012 PUBLIC 21/60 .2 Backup Best Practices Refer to the following items for information about backing up your Planning and Consolidation system: 1. 4.htm.com/saphelp_nw70/helpdata/EN/7c/efa841c1dade34e10000000a1550b0/content.sap. refer to the article entitled Architecting a high availability SAP NetWeaver infrastructure.sap. On the SAP Developer Network at https://www.com/solutionmanagerbp. refer to the backup procedures at http://help. Software Component Start and Stop Sequences and Tools Software Component: POASBC Sequence 1 Tool Example: STARTSAP STARTSAP (UNIX) SAP Management Console Detailed Description The application is based on SAP NetWeaver infrastructure. see the Technical Operations Manual on SAP Help Portal at http://help.1 Starting and Stopping The following table describes the sequence for starting and stopping the application.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30c221aab4e5-2910-b899-d268d84c19c5.4 Management of Planning and Consolidation 4 Management of Planning and Consolidation 4. On the SAP Help Portal.sdn. refer to documents 084 Business Continuity Management for SAP System Landscapes and 085 Emergency Handling for Recovery of SAP System Landscapes. 3. On SAP Service Marketplace at http://service. 2.

calculations. report and input templates.4 4. conversion files.3.3. load) n OLAP engine and calculations BI Accelerator (optional The BI Accelerator can be used to eliminate database read times through the use of in-memory storage.1 Processing Tiers To optimize performance.3 Management of Planning and Consolidation Best Practices for Performance Management 4. and the processing that occurs on those tiers. it is useful to understand the system tiers. n Metadata reads and writes n Application file storage (book repositories. 22/60 PUBLIC 04/23/2012 . and MDX parsing n Parameter-driven logic n Data Manager loads and ETL (extraction. for compressed records n F fact table.3 Best Practices for Performance Management A number of factors affect Planning and Consolidation performance. component) 4. for uncompressed records Records are automatically compressed during the optimization process (zero elimination is not used). the validation framework. transform. including the following: n n n n n Number of dimension members Amount of transactional data in a given model Number of concurrent users Hardware Network bandwidth 4. and transformation files) NetWeaver ABAP Application Server The following processes occur at the application server level: n Script logic. unstructured data. and the security model. The following table outlines them: Tier Description Database The following processes occur at the database level: n Data reads n Data write-backs Note Write-back performance is primarily affected by work status locks.2 Cube Fact Tables Each InfoCube has the following two fact tables: n E fact table. concurrency lock parameters.

then the record set is considered sparse. In general.3 Management of Planning and Consolidation Best Practices for Performance Management 4. aggregates. They are described in the following table: Parameter Default Description PACKAGE_SIZE SPARSITY_COEF 40000 5 This specifies the size into which packages will be divided during the writeback process.3.3. These modifications include such things as tablespaces. RECLEVEL_NR 10 04/23/2012 PUBLIC 23/60 .4 Cube Modification During the optimization process. For more information about executing optimization process chains. For more information about modifying and scheduling optimization process chains. If the number of records being saved is less records than or equal to this value. you can schedule them using Data Manager or execute them using Administration.3 Cube Optimization Optimizations have been implemented as process chains. BI Accelerator indexes. see the Administration section in the application help.3.4 4. If (the number of dimensions multiplied by the number of unique members in each dimension) is greater than (number of records multiplied by this value). through transaction RSA1) are lost. 4.5 Writeback Parameters You can modify writeback parameter values in transaction UJR0. record-based locking will be implemented. Planning and Consolidation creates a shadow cube and moves the data to that cube when the system determines a data model reorganization is needed (for performance reasons). These values are maintained at the individual model level. DTPs (distributed transaction processing). see the Data Manager section in the application help. and are not moved with the data. 4. As such. Any external modifications made to the cube (for example. you will not need to change the default values. and database performance parameters.

INTERVAL_NR 10 4. the range between the low to high values will be locked.4 Set Up of BPF E-mail Notifications Use this procedure to set up e-mail notifications sent by business process flows. Features Owners are notified by e-mail when a BPF instance is created and actions are taken. In the situation where record level locking is not being implemented and the data set being saved is NOT sparse.4 Management of Planning and Consolidation Set Up of BPF E-mail Notifications Parameter Default Description MULTIPLY_COEF 50 In the situation where record-level locking is not being implemented and a sparse data set is being saved. they are notified when an instance has been completed and ready to be finalized. Prerequisites Environment users must have e-mail addresses. then the record set is considered sparse.3.6 SQE Parameters You can modify SQE parameter values in transaction UJQ0. Reviewers are notified by e-mail when a step region is ready for review. In general. They are described in the following table: Parameter Default Description SPARSITY_COEF 5 If (the number of dimensions multiplied by the number of unique members in each dimension) is greater than (number of records multiplied by this value). when to swap to using a BETWEEN range in the lock table). In addition. These values are maintained at the individual model level. 4. it is not necessary to change these values. any dimensions with less than this number of distinct member values in the dataset will be locked using their single values. 24/60 PUBLIC 04/23/2012 . this value specifie the maximum number of members for which you can implement record level locking (that is. If the dimension has more than this number of records.4 4.

You create a copy of a system template by selecting a system template then clicking the Create customized email template icon in the toolbar. You can customize the title and body of C-type (customized) e-mail templates. Step region(s): first active step number and step region dimension:member. and you can add the following variables to display information in the e-mail to help its recipient: n n n n %INST_NAME% %STEP_NAME% %URL% %STEP_REGION_NAME% Managing BPF e-mails Set up and customization of BPF e-mail notification templates is done on the back-end. Then. Choose Package in the left navigation pane. Creating a BPF instance generates a notification to all users with access to the BPF monitor.4 4. Choose Programs. You can input multi-language text in the e-mail body. modify it as needed. In SAP GUI.total and category budget. which you cannot modify. As a participant in this business process please select the following link: HTTP://sample_link/. You can create a copy of each system template and customize the copy for your business needs. These are S-type (system) templates. Perform the following steps: 1. These are C-type (customized) templates. Types of BPF e-mails Planning and Consolidation contains a number of e-mail templates by default. 3. then enter the package name UJB.5 Management of Planning and Consolidation CLM Configuration Example Subject: BPF instance <name> now ready for action Text: BPF Instance for dimensions time 2009. choose transaction code SE80 for the Object Navigator. then run UJB_MAINTAIN_EMAIL_TMPL.5 CLM Configuration The following table describes the tools for configuring Content Lifecycle Management. 04/23/2012 PUBLIC 25/60 . 2. 4.

Execute the transaction in a new window ‒ ‘/o/poa/sfcpconfig’. the bundles are loaded only on demand ‒ when required by the application.4 4. Log on to ABAP system. default value ‒ false Purpose: When set to true. This displays details about the loaded bundles on the client. 4. When set to true. pp-support-mode Expected value ‒ true/false.0 Solution Manager Content Changing Flex Client Platform (FCP) Configuration Using Transaction (Recommended) 1.5 Management of Planning and Consolidation CLM Configuration Component Configuration Tools Detailed Description Content Lifecycle Management (Software Component POASBC) Customizing — this the standard SAP tool for ABAP-based system used for component Customizing. Optional: To troubleshoot. Access it through transaction SPRO SAP Solution Manager Technical configuration: Mainly for configuring application systems and the APIs with which CLM interacts SAP Solution Manager is the standard SAP tool for process and scenario-based configuration. pp-enable-lazy-loading Expected value ‒ true/false. default value ‒ false Purpose: This is a kind of central switch to turn ON/OFF the lazy loading of bundles. When set to 26/60 PUBLIC 04/23/2012 . Content Lifecycle Management (Software Component POASBC) For more information about SAP Solution Manager. 3. you can also check whether the values have changed by looking into the database table (/poa/config_info) directly.xml. all the lazy loading configurations are considered by the Flex Client Platform (FCP) client. see the following SAP Note: SAP Note Number Title Comment 1230438 Solution Manager Content for SAP Additional information for using SRM 7. As a result. Change the values in the Configuration Value column and choose Enter. before you exit. Exit the transaction. Platform Parameters That Can Be Set As Part Of Application Configuration 1. This configuration overrides all the lazy loading options present in any bundle’s plugin. This setting is recommended especially for large applications as this enhances the performance. 2. Platform Parameters That Can Be Set As Part Of Application Configuration ‒ Could Influence Client‘s Behavior 1. All other support information can also be accessed by enabling this parameter. the support information is displayed in the context menu on the client.

FCP client sends a single request for plug-in manifests. As the name suggests. When set to false. 5. 07 Apr 2010 00:00:00 GMT. When set to false. pp-enable-request-batching Expected value ‒ true/false.5 Management of Planning and Consolidation CLM Configuration 2. the support information is displayed in the context menu on the client. the ‚expires‘ in HHT header of the response is set to Wed. default value ‒ false Purpose: When set to true. 7. April 5 2010. pp-log-filter Expected value ‒ ERROR|FATAL|SUCCESS|WARNING|INFO|NONE|*. 4. When set to false. To debug the URL. if today‘s date is Mon. With URL parameter show-trace set to true. and you have specified 2 as resource-expiry-duration. The number of requests depend on the number of resolved bundles for an application. This reduces the number of calls to the server and hence increases the performance. When set to true. pp-support-mode Expected value ‒ true/false. of days. the debug version (‘. default value ‒ 365 Purpose: The specified number of days are added to the current date and expiry date is the resource set accordingly. When set to true. pp-enable-debugging Expected value ‒ true/false. All future support information can also be accessed by enabling this parameter. false. default value ‒ false Purpose: Enables debugging on FCP client. application debugging is disabled. The support information displays details about the loaded bundles on the client. default value ‒ true Purpose: Helps FCP client decide whether to send single/multiple requests for a plug-in manifest. trace console is also seen.4 4. default value ‒ false Purpose: Enables display of log console on FCP client.swf’) of a plug-in is downloaded and the FCP client can run in debug mode. FCP client sends single request for every single plug-in manifest. pp-enable-trace Expected value ‒ true/false. the lazy loading configurations are ignored by the FCP client and hence all the bundles are loaded at application startup. the parameter must only be enabled if debugging of the application is required. no log console can be opened on the application. parameter ‘debug’ must be set to true. When set to true. 6. 3. the client can show the log console. default value ‒ * Purpose: 04/23/2012 PUBLIC 27/60 .-d.. resource-expiry-duration Expected value ‒ No. For example.

it must be prefixed with ’app-’. you can configure application-wide parameters in the <application-parameters/> section. 8. FCP URL Parameters That Can Be Passed to Client Platform 1. By default. app-http-method-override Expected value ‒ true/false. This can point to a static/pre-configured XML file or to any URL that can be requested via HTTP. 9. default value ‒ 7 Purpose: Used by logger service on ABAP server component to set the expiry date on application logs. 3. To configure application parameters on the server (Java/ABAP). use the same method that is used to maintain platform parameters. The splash configuration in the application configuration xml contains the bundle name that is to be used as the splash/boot information bundle. log-expiry-duration Expected value ‒ duration.4 4. Application Parameter Defined by FCP 1. 2. default value ‒ false Purpose: HTTP client uses this configuration and if the value is true the PUT/DELETE HTTP methods are sent via a POST request.xml. Application Parameters 1. Splash Configuration 1. ‚false‘ means that PUT/DELETE are sent as PUT/DELETE requests respectively.5 Management of Planning and Consolidation CLM Configuration Controls the display of logs and traces in the log console. default value ‒ true Purpose: Used by FCP ABAP server component to turn on/off server cache used for storing application configuration. hide-splash 28/60 PUBLIC 04/23/2012 . FCP looks for an XML file with name com_sap_tc_ui_ria_fcp_config. All the messages that match the level set and below levels are filtered and displayed. config-url This is an optional parameter that tells the platform where to pick up the application configuration from. Apart from the platform parameters. enable-server-cache Expected value ‒ true/false. in number of days. The only rule is that for a parameter to be identified as an application parameter. execution-scope This is an optional parameter that can be used to filter the bundles based on the unique scope in which a particular FCP application wants to run.

the client runs in debug mode (depending on the pp-enable-debugging parameter). It can contain additional application-related content apart from standard FCP definitions. no splash screen is displayed. Content Lifecycle Management Logs 04/23/2012 PUBLIC 29/60 . these can be used by administrators for auditing and monitoring purposes. 8. support-mode This parameter can be used on client side to enable/disable support information. 4. and all the configurations in the application configuration for splash are overridden.6 Management of Planning and Consolidation Administration Tools 4. This is an optional parameter that when set to true.4 4. app-def This is an optional parameter that can be used to pass application-specific and static configuration to FCP applications. the client displays the log console (depending on the pp-enable-trace parameter). 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. instead FCP shows a progress bar with status message. show-trace This is an optional parameter that when set to true. REST and for /POA/UM with value OTHER.6. OTHER. 6. log objects: /POA/PST and /POA/UM The application log includes detailed information about error messages and sequential flow with respect to technical processing in the application. mask-feature This is an optional parameter that can be used to filter the bundles based on the feature scope. debug This is an optional parameter that when set to true. n Application Log: Every operation and corresponding steps carried out during that operation are recorded in the application log: Transaction SLG1. 7. Note: Application definition is not able to influence platform parameters (all server parameters starting with pp-). 5. REST. Note that support information is visible only when both platform parameter (pp-support-mode) and URL parameter (support-mode) are set to true.1 Logs The application writes logs during various activities at runtime.6 Administration Tools 4.

such as editing. n Change Log or Change History: For all actions that can be carried out in CLM UI. Provide the following filters: n Object: /POA/SFCP (Display Only) n Subobject: FCPAPPLOG (Display Only) n Optional: External ID: Category of the log message. deployment. Connect to the ABAP system and execute transaction /POA/SFCPAPPLOG.4 4. as seen in the application log console n Mandatory: Time (From/To): The required interval as seen in application log console n Optional: User: User of the session n 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 Database The exported log messages are grouped based on Category/External ID and displayed. All the generated logs have an expiry time set and need to be deleted explicitly using transaction SLG2. 30/60 PUBLIC 04/23/2012 . and system database tables defined in CLM are enabled for logging. 2. object: /POA/CLM The application log includes detailed information about error messages and sequential flow with respect to CLM technical processing. It displays statuses and messages for deployments from CLM to the application. n Customizing object or Table Logging: All Customizing. This can be seen in CLM UI with View History function. 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 under Manage Packages function on CLM UI) l CHECKPOINT: All actions performed under Manage Content Groups in CLM are recorded for analysis under this application log subobject l DEPLOYMENT: Application logs related to deployment from CLM are recorded under this subobject l TECHNICAL: Additional technical log details are recorded under this subobject. CLM change logging is enabled for packages and content groups and related tables. control. and export. Analysis of this logging can be done using SCU3 transaction in NetWeaver ABAP system if logging is switched on. Flex Client Platform (FCP) Server-Side Log Messages The application log messages can be viewed on an ABAP server using transaction /POA/SFCPAPPLOG. CLM logs the change history using the change documents function of ABAP. The deployment log provides details of application-specific messages per deployment system and per content group. import.6 Management of Planning and Consolidation Administration Tools n Application Log: Every CLM operation and corresponding steps carried out during that operation are recorded in the application log: Transaction SLG1. 1. n Deployment Log: This is available on CLM UI.

4 4. For more information.’FATAL’ is mapped to ’TERMINATION’).6 Management of Planning and Consolidation Administration Tools 3. Flex Client Platform (FCP) Server-Side Trace Messages The application trace messages can be viewed on an ABAP Server using transaction /POA/SFCPAPPTRACE. ’Important’ for ’ERROR’. This parameter can be configured using transaction /POA/SFCPCONFIG and specifies the number of days for which logs can reside on the server. 1. select extended text under Details column. Deleting Logs and Traces All application logs and traces are generated with an expiry date and Deletion before expiry attribute set to true. and ’Medium’ for other severities. and ’Medium’ for other severities. Log severity seen on the ABAP server is the same as in the application. ’Important’ for ’ERROR’. except for ’SUCCESS’ and ’FATAL’ (’SUCCESS’ is mapped to ’INFO’. execute transaction SLG2. For more information. Connect to the ABAP system. Connect to the ABAP system. 2. execute transaction /POA/SFCPAPPTRACE. except for ’SUCCESS’ and ’FATAL’ (’SUCCESS’ is mapped to ’INFO’. All the trace messages generated have an expiry time set and need to be deleted explicitly using transaction SLG2. Problem class is ’Very Important’ for ’FATAL’. Default value is 7. Provide the following filters: n Object: /POA/SFCP (Display Only) n Subobject: FCPAPPTRACE (Display Only) n Optional: External ID: Category of the trace message. 3. as seen in application log console n Mandatory: Time (From/To): Required interval as seen in application log console n Optional: User: User of the session n 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 Database The exported trace messages are grouped based on Category/External ID and displayed. Obsolete logs and traces can be deleted as follows: 1. The expiry date for logs and traces is calculated based on the log-expiry-duration parameter on the server. Trace severity seen on the ABAP server is the same as in the application. Hence all the logs and traces can be deleted before their expiry date. 2. select extended text under Details column. 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 . ’FATAL’ is mapped to ’TERMINATION’). Problem class is ’Very Important’ for ’FATAL’.

2 Load Balancing As a web-based application.6 Management of Planning and Consolidation Administration Tools n COMMIT Counter: 100 3.sap.6.sap.3 User Management All scenarios and components in the application use the user management functions provided by NetWeaver. For more information about network load balancing. 4.4 4.4 Utilities for CLM Content Lifecycle Management Administrator/Developer Utilities CLM provides utilities for testing purposes. see the Technical Infrastructure Guide for SAP NetWeaver on SAP Service Marketplace at http://service. an appropriate system setup is also required via system registry configuration where new application systems and their APIs are registered. Logs can also be deleted in the background using report SBAL_DELETE. which are intended for administrators and developer user groups. see Customizing for Content Lifecycle Management under Maintain System Registry. 32/60 PUBLIC 04/23/2012 . 4. For more information. the basis for logon and load balancing is a high availability landscape setup together with a load balanced network setup. A load-balanced network using SAP Web Dispatcher together with logon groups in the SAP NetWeaver systems can be used to redirect certain users to specific application servers. it expects a certain format and interface for these API/RFC function modules. For more information.com/securityguide. Choose Execute. Moreover.6.com/instguides. For more information about user administration and authentication.6. see the following SAP Note: SAP Note Number Title Comment 195157 Application log: Deletion of logs Delete log entries from database tables of application logs 4. Application API Adapter testing: Since CLM calls the RFC function modules while communicating with application systems. see the application security guide on SAP Service Marketplace at http://service.

it is advisable to run the test adapter utility using transaction /POA/CLM_API_TESTER. logs Database and log backup Yearly 4. you can use transaction /POA/CLM_CLEANUP to delete the CLM-specific database tables. 4. The transaction checks API interfaces and also performs a test run for extraction and deployment operations.4 4. before you run CLM with system registry settings. Scheduled periodic tasks for Content Lifecycle Management: 04/23/2012 PUBLIC 33/60 .8 Scheduled Periodic Tasks for CLM CLM uses background jobs for the execution of some operations at runtime. Note This program completely deletes all CLM data and does not allow any preferences to be set for specific entry deletion from CLM database tables. and you find CLM database tables increasing in size over time. standalone system based on SAP NetWeaver Application Server Data: Standalone SAP ERP Database and log n backup. You need to provide the system registry ID. configuration log files The following table lists the CLM components relevant for backup and recovery: Component POASBC Data to be Backed Up Backup Method/Tool Recommended Backup Frequency Application database tables. Hence it is intended to be used for cleaning up garbage or unused data from the test CLM system only.7 Management of Planning and Consolidation Backup and Restore In actual scenarios or for productive usage. application log backup (such as job logs in file system) n Backup of software.7 Backup and Restore The following table describes methods for backup and restore for application components: Categories of System Components Category Properties Suggested Methods for Backup and Restore Examples VIII Original application data. The following table gives an overview of the exact programs that are scheduled in the background and the frequency at which these are executed. Cleaning up the CLM database: If you are running CLM for test purposes or on a test system.

9 Scheduled Periodic Tasks for Event & Notification Program Name/Task Task Scheduling Tool Recommended Frequency Detailed Description E-mail job ABAP Every minute For more information about sending messages to e-mail. Delete expired inbox items Reorganize and reconciliation job ABAP ABAP Daily Monthly or greater For more information about scheduled jobs. Other background tasks in Content Lifecycle Management that are scheduled to run immediately: Program Name/Task Task-Scheduling Tool Recommended Frequency Detailed Description /POA/R_CLM_EXTRACT /POA/R_CLM_DEPLOY Automatic Automatic Immediately when the operation is triggered Immediately when the operation is triggered Background task during content group extraction Background task for content group upload and deployment 4. For more information. see the installation guide. Deletes messages that have been set to expire. 34/60 PUBLIC 04/23/2012 . Used to retrieve the deployment results of application content from target application systems. see the installation guide. Reconciliation of deleted messages in Business Workplace and event and notification. see Content Group Deployment in SAP Library documentation under Content Lifecycle Management Content Group and Package Management Content Group Deployment .4 4.9 Management of Planning and Consolidation Scheduled Periodic Tasks for Event & Notification Program Name/Task Task-Scheduling Tool Recommended Frequency Detailed Description /POA/R_CLM_DEPLOY_RESULTS_POLL Automatic 10 minutes: This can be changed in Customizing for Content Lifecycle Management under Maintain Technical Settings.

global rollouts (including localizations). Two modes of transport are supported: n Normal mode ‒ For modifying and creating objects. it is modified with the changes from the source system. moving and deleting a package). You can also collect NetWeaver objects into a transport request. and testing procedures for complex software landscapes and multiple software development platforms. Data Manager packages (deletion includes renaming. Data Manager package groups (deletion includes renaming and deleting a package group) and Data Manager package links. dimensions. if a transported object exists in the target system. The goal of Software Change Management is to establish consistent. 04/23/2012 PUBLIC 35/60 . it is created. dimensions. These functions support your project teams. members. In this mode. development teams. logic script files.1 Transport Management Transports allow you to move an environment across a landscape. You can transport the changes associated with an environment without having to transport the entire environment. You can transport the deletion of models.5 Software Change Management 5 Software Change Management Software Change Management standardizes and automates software distribution. solution-wide change management that allows for specific maintenance procedures. use the SAP NetWeaver transport process for process chains. If you have problems with transports. You can transport one or more models at a time. n Deletion mode ‒ For deleting objects. you can transport an environment from a development system to a test system and then to a production system. maintenance. and so on). In this mode. for example. work status. To move process chains into your production environment. All aspects of an environment are transported except transaction data. reports. For example. and select individual components of a model. see Troubleshooting Transport [page 51]. and open integration with third-party products. you explicitly specify the objects to delete. 5. and application support teams. such as NetWeaver process chains. The following subsections contain a description of the transport process and some other useful information about transporting. The process chain must be assigned to component /cpmb/BPC. If it does not exist. This section provides additional information about the most important software components.

1 Transport Objects This section lists the objects that you can transport for environments and models.5 5.1 Software Change Management Transport Management 5. n n n n n n Business Rule Configuration Dimension Model Script Logic Task Profile Model Objects You can transport the following objects for a model.1. n n n n n n n n n n n n n n n n n n n n n n n n Books Template Business Process Flow Template Business Rule Business Unit Configuration Control Data Access Profile Data Manager Conversion File Data Manager Data File Data Manager Package Data Manager Package Group Data Manager Package Link Data Manager Transformation File Dimension Dimension Master Data Drill Through Journal Template Report File Report Templates Script Logic Task Profile Team Web Documents Work Status Settings 36/60 PUBLIC 04/23/2012 . Environment Objects You can transport the following objects for an environment.

see the SAP NetWeaver Technical Operations Manual on SAP Help Portal at http://help. which is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing. However. 3. Otherwise it is executed in client 000. Select he objects to transport. as all Planning and Consolidation data is client-dependent.1 Software Change Management Transport Management 5.sap. Configure the system to import Client-Dependent Objects. Use transaction RSTPRFC to create the destination for this client. Only the objects that you select are transported.2 Transport Configuration Before you can transport. 2.3 Transport Execution 5.com. see Change and Transport System in the SAP NetWeaver Application Help on the SAP Library at http://help. SAP NetWeaver includes the Change and Transport System (CTS). Procedure 1. For information about transport objects.3. For more information. a warning is generated. 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. For information. Configure the SAP NetWeaver transport framework by creating transport domains. 5.5 5. routes. you must first configure the SAP NetWeaver transport framework. For information. Prerequisites You are the SAP NetWeaver administrator.1. and then transport the changes between the SAP systems in your system landscape. if you transport an object but do not include its dependent objects in the transport. This allows for the granular selection of objects. You can transport objects with or without corresponding dependent objects. see Importing Client-Dependent Objects in the SAP NetWeaver Application Help on the SAP Library at http://help.com.sap.1 Transporting Environments You select the objects to transport from the hierarchy of objects in the environment. and other aspects of a transport.1.1. 04/23/2012 PUBLIC 37/60 .sap.com SAP NetWeaver . see Transport Objects [page 36].

d) Click the Continue button to generate the customizing request. click the Create Request button to generate a new customizing request. Transport Errors If transport fails for an object. Generate a customizing request: a) In the right column. Select the objects to transport: a) In the left column. Procedure 1. c) In the next dialog box. you can mark it for deletion in the target system.5 5. d) In the dialog box. click the Transport Objects button. 3. select More Types BPC Environment . In the left column.1. However. 4. The selected objects are included into the request. b) In the middle column. then click the Continue button. see SAP Note 1583670. e) In the right column. you can only select deleted objects for which there are no dependencies.1 Software Change Management Transport Management Recommendation We recommend that you do not add a normal transport and a deletion transport for the same environment into one customizing request. b) In the dialog box. c) Double-click Select Objects. the changes for that object are not made in the target system. 38/60 PUBLIC 04/23/2012 . You can select the deleted objects to transport. b) Click Release directly. select the environment to be transported and click Transfer Selections. This does not affect the transport of other objects to the target system.3. 5. select Transport Connection. enter the description and transport target. 5. Release the customizing task: a) Select the task under the customizing request you just generated. 2. then click the Save button. The object in the target system remains unchanged. Logon to the source system and enter transaction code RSA1. the objects in the environment are listed. Click Display. Select the objects to be transported by selecting or deselecting the corresponding object.2 Transport Deletion After an object has been deleted in the source system. e) Enter transaction code SE09 to open the transport organizer. select SAP Transport Object Types . For more information.

5 5. c) In the next dialog box. Release the customizing task: a) Select the task under the customizing request you just generated. e) In the right column. select the environment to be transported and click Transfer Selections. you can view the transport log. 4. see SAP Note 1583670. Procedure 1. The selected objects are included into the request. b) Choose Release directly. For more information. The object in the target system remains unchanged. select More Types BPC Deletion . Deletion Errors If deletion fails for an object. enter the description and transport target. click the Transport Objects button. The log reports the successful completion of a transport request. Select the deleted objects to be transported by selecting or deselecting the corresponding object. b) In the middle column. 2. c) Double-click Select Objects.4 Transport Log Files After a transport has been completed. d) In the dialog box. 3. select Transport Connection. then click the Save button. e) Enter transaction code SE09 to open the transport organizer. all objects in the environment which have been deleted (and which do not have dependent objects that still exist) are listed. then click the Continue button. the changes for that object are not made in the target system. d) Click the Continue button to generate the customizing request. 5. In the left column. click the Create Request button to generate a new customizing request. as well as warnings and errors encountered during the transport.1. select SAP Transport Object Types .1 Software Change Management Transport Management Recommendation We recommend that you do not add a normal transport and a deletion transport for the same environment into one customizing request. Generate a customizing request: a) In the right column. 5. b) In the dialog box. Procedure To view a transport log file: 04/23/2012 PUBLIC 39/60 . This does not affect the deletion of other objects in the target system. Click Display. Logon to the source system and enter transaction code RSA1. Select the deleted objects to transport: a) In the left column.

5. When you need to apply a patch. You test the patch in Development. then workbooks from development are not transported. For more information.6 Deployment Scenarios There are two typical landscape deployment scenarios.1.1 Software Change Management Transport Management 1. 2. If this is done in development. you should have two environments in development. all objects are created in development and transported to production. 5. see SAP Note 1615644. Development to Production In the Development to Production deployment scenario. and models are created in development. you create and maintain an environment in development. the decision would need to be made for Workbooks (report templates and input schedules). When a production support change occurs. When the cutover of new development needs to be transported. this should be done in both environments in development. they may have a configuration that has Production support changes and another configuration on the same model or environment that is transported at a later stage in the project cycle. one for new development. Typically. If this is done in production. Additionally. and one for production support changes. All dimensions. you transport the environment from Production to Development. Best Practices for Ongoing Development Some customers have release cycles in which they are unable to transport an entire environment. Features You can use the UJT_AFTER_FAIL_PROCESS program. Select a released request. you apply the patch to Production. you work in production only.1. A decision needs to be made for all other objects. 40/60 PUBLIC 04/23/2012 .5 5. In this case. then the configuration can be moved to the production support environment and transported.5 Transport Maintenance There are certain maintenance tasks involved with transports. which typically are handled landscape by landscape. Click Transport Logs. dimension properties. After the patch is validated. Production Only (with Development for patch testing) In this scenario. The exceptions include security and teams. For example. then workbooks in production would be overwritten.

It is an efficient method of transporting a selected number of requests into a group of transport targets.4 Support Packages and Patch Implementation Information on the support packages (SPs) available for Content Lifecycle Management can be found in the Release Information Notes (RIN) for each SP. 5.2 Development Requests and Development Release Management The transport workflow provides a framework for transporting enhancements or new developments of existing business functions in a system landscape.sap. 04/23/2012 PUBLIC 41/60 . 5.com SAP NetWeaver .2 Software Change Management Development Requests and Development Release Management 5.com/instguides. For more information. For more information.sap. and uses clearly defined approval steps to ensure the quality of your target systems. SAP Notes that require code changes for components based on the SAP NetWeaver Application Server (ABAP) can be applied using the SAP Note Assistant. see http://service.3 Quality Management and Test Management for CLM All CLM interfaces can be tested automatically through the eCATT/Test Workbench.com/note-assistant.5 5.sap. Detailed instructions about applying a support package stack to SAP NetWeaver are given in the SAP NetWeaver Support Package Stack guides on SAP Service Marketplace at http://service. Support packages for components based on the SAP NetWeaver Application Server (ABAP) (such as CLM) are applied using the Support Package Manager. see the Technical Operations Manual on SAP Help Portal at http://help.

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

1 Troubleshooting in Planning and Consolidation The following table lists common Planning and Consolidation problems that you may encounter. Marginal text and buttons in Determine the DPI font settings in Planning and Consolidation dialog the host computer. Install AppSight Black Box Service in standalone mode. Download and extract the *. a) Run AppSight Black Box Service.exe. 04/23/2012 PUBLIC 43/60 . 6. analysis. choose Advanced. as well as suggestions for troubleshooting and resolving the problem: Problem Analysis Solution On the Settings tab in the Microsoft Windows Display Properties dialog box. and resolution of problems. Copy either Triserv2. 2. n Triserv_XpressServer. This filename must match the one that is in the startservice.rpr or Triserv_XpressServer. For information about setting up Solution Manager Diagnostics. This profile outlines the type of process for BlackBox to monitor.rpr file into the Identify folder depending on what application is needed to be monitored.bat file.bat file. This filename must match the one that is in the startservice. see Connecting to Solution Manager Diagnostics in the Planning and Consolidation NW Installation Guide. Create a directory on your C:\ drive called Identify.3 Installing Appsight Black Box Service 1.rpr BlackBox profile that is used by the application.rar files attached to SAP Note 1356729 from SAP Service Marketplace.2 Analyzing Problems Using Solution Manager Diagnostics The diagnostics functions in SAP Solution Manager allow identification.rpr The Xpress Server profile. On the General tab. ensure that the DPI setting is 96 DPI. 3. b) Select Install. boxes are unreadable or incorrectly formatted. 4. n Triserv2.6 Troubleshooting 6 Troubleshooting 6. 6.

the Identity folder contains an . This allows you to monitor the file size.bat and stopservice.bat stops the Blackbox application. n The minimum release on the SAP Solution Manager Diagnostics side for E2E Trace Analysis is Solution Manager 7. The log stays at 0 bytes until the service is stopped and only then is its actual size shown. Client side and server side trace information is displayed in the E2E Trace application in SMD. Generating and analyzing trace files using E2E Trace involves the following tasks. You must stop the application before you can copy the log. Copy the startservice. which are described below: 44/60 PUBLIC 04/23/2012 . E2E Trace is delivered and installed with Planning and Consolidation. Startservice.bat to begin logging.ASLfile. Trace files collect information about client and server interactions presenting trace information about the entire request and response of a business process step. The trace files then upload to the server for analysis in SAP Solution Manager Diagnostics (SMD). Stopservice. Recommendation Stop and start the service at the end of each day. To configure and activate tracing on a client machine.bat starts the application using the profile path and the naming convention for the log. and have the application create a new one. 6. copy the file to another folder.4 Troubleshooting Generating and Analyzing Trace Files Using E2E Trace c) Accept the agreement and choose Next. e) Leave the server prompt blank for standalone mode and choose Next.User Guide in the Diagnostics section of SAP Service Marketplace. 6. The computer name and date are used as a variable for the naming convention.0 EhP 1 SP23.6 6. Run startservice. f) Leave Black Box with no license option and choose Finish. you can obtain information about evaluating the results of the trace in the E2E Trace Analysis . which is the log that will write all the information from the application.bat files into the Identify folder. 5. Prerequisites n Ensure that the latest Planning and Consolidation Clients with the E2E Trace plug-in are installed on your client machine. see Logging and Tracing Configuration [page 46]. After enabling and running tracing. d) Enter any information for username and company name and choose Next. Once you start the application.4 Generating and Analyzing Trace Files Using E2E Trace You can generate trace files on client and server components for troubleshooting purposes using E2E Trace.

exe. expand the Manually upload section. 4. 6. Choose Stop Transaction in the E2E Trace Plug-In user interface to upload the transaction XML to the SMD server. 5. Choose End-To-End Analysis. A green icon displays besides the system ID. The file to upload appears in <trace plug-in folder>\Logs. c) Enter the SMD server host. Select the system ID of the Planning and Consolidation ABAP stack. On the client machine on which you recorded the trace. Select Microsoft Office Excel and choose Launch. 3. Perform a Trace of the Microsoft Excel Module 1. Select the query that contains all systems involved within the E2E trace and select the system ID of the Planning and Consolidation ABAP stack. Select the BusinessTransaction. 5.xml file and choose Upload. After Excel is launched. Click Log On in the EPM menu in Excel.xml. 2. Select Enable. 3.6 6. 2. you locate the trace by this name.4 Troubleshooting Generating and Analyzing Trace Files Using E2E Trace n n n n n Enable tracing in the ABAP back-end system Perform a trace in the Administration module Perform a trace in the Microsoft Excel module Manually upload the trace file to SMD if not done automatically Evaluate the trace file in SAP Solution Manager Enable Tracing in the ABAP Back-end System 1. Launch the E2E Plug-In by running plugin-starter-gui. Choose Start Transaction in the E2E Trace Plug-in user interface. 7. which opens a new window with the E2E Trace Analysis application. Enter the Root Cause Analysis work center of SAP Solution Manager. Choose Browse under Upload BusinessTransaction. d) Enter the SMD HTTP port. 3. 04/23/2012 PUBLIC 45/60 . 6. Choose Trace Analysis. Manually Upload the Trace File If you need to manually upload a trace file to SMD. b) Set the Session Trace Level to High. 2. 4. In the E2E Trace application within SMD. 7. perform these steps: 1. then choose OK to log on to the Excel module. enter the following values in the E2E Trace Plug-in user interface: a) Enter a name for your trace in Business Transaction Name. Select the Trace Enabling tab. collect the corresponding trace of the ABAP server. After uploading the trace to SMD.

select a line with incoming RFC calls. trace data may not be found. Expand the tray Server Analysis and choose the Request tree tab. then choose Display aggregated ABAP Trace.5 Troubleshooting Logging and Tracing Configuration Evaluation of Traces in SAP Solution Manager 1. Choose End-To-End Analysis. Choose Trace Analysis to open a new window with the E2E Trace Analysis application Select the trace from the list. then choose Display Introscope Transaction Trace. In SAP Solution Manager. If you forgot to enable tracing or wait too long between trace recording and trace data collection (for example. n To view ABAP SQL Trace data. 5. Choose Expand all to see incoming http calls. 4. Note This starts trace data collection and results in a list of success or error messages. Select the Summary tab if it is not selected. outgoing DOTNET Connector calls.com) 6. then do one or more of the following: n To view Introscope Transaction Trace data. 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. 46/60 PUBLIC 04/23/2012 . then choose Display ABAP SQL Trace Summary. Select the Message table tab. You can view the log and trace files in the Log Viewer tool of Solution Manager diagnostics after performing the configuration described below. Select the query that contains all systems involved within the E2E Trace and select all systems. If you want the SMD to collect corresponding server side trace data. 8.sap. 10.5 Logging and Tracing Configuration You can create log and trace files for troubleshooting purposes. choose Select systems for trace collection dynamically. 3. more than one day). Select the first step of the recorded E2E Transaction Trace and choose Display. You can create log and trace files for the client. 7.6 6. select a line with incoming RFC calls. n To view ABAP Trace data. 11. 9. 6. select a line with incoming http calls. access the Root Cause Analysis work center. and incoming RFC calls. 2.

Log Setting --> <LogSeverity value="INFO" /> <LogDestination value="" /> <LogFileCount value="10" /> <MaxLogSize value="10" /> <!-.Application Set setting --> <AppSet value="" /> </LogTraceConfig> The following sections explain the meanings of the components of each part of the log-configuration. This file is predelivered for the client.Trace Setting --> <TraceSeverity value="ERROR" /> <TraceDestination value="" /> <TraceFileCount value="10" /> <MaxTraceSize value="10" /> <TraceUser value="" /> <!-.xml. The following trace severity levels are supported: 04/23/2012 PUBLIC 47/60 .5. Parameter TraceSeverity Setting part of the log-configuration.0" encoding="utf-8"?> <LogTraceConfig> <!-.1 Logging and Tracing Parameters Logging and tracing parameters use a configuration file named log-configuration.5 Troubleshooting Logging and Tracing Configuration 6. Features The Log Configuration File As delivered.xml Default Value Meaning ERROR You use the trace severity to control the number of trace records that are produced.xml file. Trace Settings The following table explains the parameters of the Trace file.6 6. this file contains the following statements: >>> MISSING TARGET TEXT FOR TEXT-ID: 'SourceCode' (language: en) <<< <?xml version="1.

and error trace records are written to the file. together with all more. The first trace file to be written is BPCtrace. TraceUser Empty The default means that the system writes trace records for all users. MaxTraceSize 10 10 The maximum size of single trace file.x. <TraceDestination value=“C:\Program Files\SAP BusinessObjects\PC_NW\Logging\Trace”>. is started. Trace files are named BPCtrace. You can also create trace records for a specified user. warning. 48/60 PUBLIC 04/23/2012 . For example. This is effectively switching off Trace.log TraceFileCount . For example. TraceDestination Empty The location where you want to store the trace files.0. for example. If you set it as value. The unit is MB.log. DONOTHING is a special severity level. If you set another value for TraceSeverity.log.6 6. When this file reaches the MaxTraceSize. the next file. no trace records are written to file. whereupon the system overwrites BPCtrace. BPCtrace.logwhere x is a number between 0 and one less than the TraceFileCount. ERR. This continues until there are TraceFileCount trace files. it is treated as DONOTHING.1. severe trace records.0. are written to the trace file. choosing INFO means that all information.5 Troubleshooting Logging and Tracing Configuration Parameter Default Value Meaning n DEBUG n PATH n INFO n WARNING n ERROR n DONOTHING Choosing a severity level means that trace records with the chosen severity.

The location where you want to store the log files. The following log severity levels are supported: n INFO n WARNING n ERROR n DONOTHING Choosing a severity level means that trace records with the chosen severity. This is effectively switching off Logging. This continues until there are LogFileCount log files. For example. no log records are written to file. When this file reaches the MaxLogSize. DONOTHING is a special severity level.xml Default Value Meaning INFO You use the log severity to control the number of trace records that are produced.5 Troubleshooting Logging and Tracing Configuration Log Settings The following table explains the parameters of the Log file.6 6. 04/23/2012 PUBLIC 49/60 . it is treated as DONOTHING. is started.0. Parameter LogSeverity Setting part of the log-configuration. For example. severe log records. If you set it as value. choosing INFO means that all information.x. LogDestination Empty MaxLogSize 10 10 The maximum size of single log file. together with all more. the next file. are written to the log file. Log files are named BPClog. BPClog. warning. <TraceDestination value=“C:\Program Files\SAP BusinessObjects\PC_NW\Logging\Log”>. The unit is MB.log LogFileCount . ERR. and error log records are written to the file. The first log file to be written is BPClog.logwhere x is a number between 0 and one less than the LogFileCount. for example. If you set another value for TraceSeverity.log.1.

0. 50/60 PUBLIC 04/23/2012 . all the configuration items in the log-configuration.5. open the file with a text editor such as Notepad.xml file. Features Trace and Log File Destination The defaults for TraceDestination and LogDestination are empty fields.xml To change the log-configuration.5 Troubleshooting Logging and Tracing Configuration Parameter Default Value Meaning whereupon the system overwrites BPClog. Application Set Settings The following table explains the parameters of the Application log-configuration. 6. make and changes and save the file back to the same location.xml.log.6 6. If Planning and Consolidation detects these empty fields at user logon. 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 number log or trace records Switch off log or trace Change the value of TraceDestination or LogDestination. Change the value of TraceSeverity or LogSeverity. it uses <TraceDestination value="C:\Program Files\SAP BusinessObjects\PC_NW\Logging\Trace" /> and <LogDestination value="C:\Program Files\SAP BusinessObjects\PC_NW\Logging\Log" />. Parameter AppSet Set Setting part of the Default Value Meaning Empty This parameter is no longer used.2 Client Configuration At installation. Configuring log-configuration. This section contains some considerations when configuring this file. Set the TraceSeverity or LogSeverity to DONOTHING.xml file have their default values.

properties) are deleted in the target system when they are deleted in the development system and the environment is transported. deleting files in the target system does not cause any harm. Since only updates are transported. n Table entries and data model objects (model. Similarly. Features The following are some specific situations where you may require some additional information or troubleshooting assistance. Choosing Transport Strategies There are many SAP transport strategies. If you change objects in a target system. and production instances. you can transport an environment from a development environment to a test environment and then to a production environment.6 Troubleshooting Transport Transports allow you to move an environment across a landscape. After deleting an environment. QA. Frequently. refer to Transport Management [page 35]. n Files such as script logic and Excel templates are only updated. a QA or production system is built with every released transport from the development system. For detailed information about how to use SAP transports. dimensions. that is. Use program UJT_CHECK_TABLE_ENTRIES to check how many records exist in the UJ* database tables for a particular environment. For example. Recommendation We recommend that you build Planning and Consolidation systems with the last good transport. Deleting Objects The two major object types exhibit different behavior patterns during the import of a transport into the target system. deleting files in the development system does not impact existing files in the QA or production systems. Changing the Data Model Do not change the data model in target systems. A typical system landscape may contain development. changes to these files are transported.6 Troubleshooting Troubleshooting Transport 6. the transports that originate from development will no longer import correctly. after going live. you can make sure that all data has been removed. We also recommend that. the fear of missing something can be alleviated. Since the Planning and Consolidation transport framework can gather all environment objects. changes are always made in the development system and transported from there to the QA and production systems. 04/23/2012 PUBLIC 51/60 .6 6.

Enter transaction code SE16 for table running. Scenario Solution Actions content objects Installation failed with the error No found 1. Reimport the transport request. Environment is filled 2. Enter transaction code RSOCONTENT. Planning and Consolidation does not transport technical names of cubes and the transport works well. or UJT_TRANS_OBJECT version ’D’ for UJT_TRANS_OBJECT. 3. or data manager packages (not data model related). input schedules. check if there are any customer-created InfoObjects or InfoCubes that refer to the attributes of the failed dimension. can be changed in any instance. Check SAP Note 1329651 Import failed with RFC errors Import or installation failed with error: Import still 1. This includes objects such as environment (InfoArea). such as reports. but this means that the customer cannot use the transport framework since it will no longer import properly.6 Troubleshooting Troubleshooting Transport Data model changes consist of objects such as environment. 52/60 PUBLIC 04/23/2012 . Failed to create BI Import failed with the error: InfoObject for dimension 1. or properties. break the references between Planning and Consolidation InfoObjects and your InfoObjects and InfoCubes. This is normal. If so.6 6. A customer can maintain the data model in the QA or production system. Changing Data Model Objects Do not change the structure or definition of Planning and Consolidation related data model objects in BW. dimensions (InfoObjects). Enter transaction code RSA1 2. Delete all the D version records for your environment in this table. Changing Technical Names The technical name of the InfoCube or Multiprovider may change between landscapes. Transport Failure Solutions The following table highlights some typical installation and transport failure scenarios and solutions. 2. model. 3. model (Multiprovider and InfoCube). Other components. Ensure that System is a Content Development System is not selected. Reimport the request. dimensions. and properties (InfoObjects). This causes subsequent transports to fail.

For example: http://<host>:<port>/sap/fcprt?app-config=<app config name>&support-mode=true 04/23/2012 PUBLIC 53/60 . 3.7 Component-Level Logs All the component-level logs are written using a trace log API and are available as part of the application log. Import failed with the error: infoarea Failed to create More Information SAP Note 1415296. the FCP server parameter pp-support-mode=true must be set and the URL query parameter support-mode=true must be used when launching the application. 1. You can also check SAP notes under the application area: EPM-BPC-NW-TRA Transport. Reimport the transport request. the Flex Client Platform (FCP) server parameter pp-enable-debugging=true must be set and the URL query parameter debug=true must be used when launching the application. Note For SAP BusinessObjects Planning and Consolidation.6 6. http://<host>:<port>/sap/fcprt?app-config=<app config name> 2. perform the following steps: 1. 2. How do I launch the application? config name> with bpc. For example: http://<host>:<port>/sap/fcprt?app-config=<app config name>&debug=true 4. Reimport the transport request.7 Troubleshooting Component-Level Logs Scenario Solution Actions /CPMB/XXXX Import failed with the error: Dimension already exists Check if anyone has transported this dimension through the BW back end manually. 2. How do I enable support mode in the application?To enable support mode. Enter transaction code SE06. Delete the InfoObjects in the BW back end (use transaction code RSD1) on the target system. 6. Change the namespaces /CPMB/ and /B28/ to be modifiable. How do I enable debug mode in the application? To enable debug mode. If so. replace <app 1. How do I launch the application in debug mode? http://<host>:<port>/sap/fcprt/d?app-config=<app config name> 3.

The dialog also provides an option to transmit the client logs to the server and to turn off tracing on the client for the session duration. set the FCP server parameter pp-log-filter to one of the appropriate values (ERROR|FATAL|SUCCESS|WARNING|INFO|NONE|*) For example: To enable only statements with levels ERROR and FATAL to be logged. 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. How do I see status of the various plug-ins and the reasons why some plug-ins are not loaded? As a prerequisite. After launching the client. Download the POASBCBUI00_0. enable the support mode. 10. n After launching the application in support mode. To configure which levels of statements to be logged. set pp-log-filter=ERROR|FATAL 8. you see a dialog with the trace information collected during startup. use the URL query parameter show-trace=startup.7 Troubleshooting Component-Level Logs 5. the FCP server parameter pp-enable-trace=true must be set and the URL query parameter show-trace=true must be used when launching the application.6 6. you can see information about the loaded plug-ins. 6. In the Loaded Plug-ins tab of the Support Information dialog. this is not recommended). enable the support mode. How do I enable logging and tracing for the application client? To enable tracing on the client. the state of the plug-ins and the error information for plug-ins that could not be loaded. 54/60 PUBLIC 04/23/2012 . you can see information about the version and the build number of the plug-in. The dialog box displays the logs and traces. which would mean no statements are logged on the client. right-click the application and select Support Info. Go to the MIME Repository and open SAP POA FCP Container . right-click the application and select Support Info. 7. n After launching the application in support mode. enable the logging and tracing on the client. In the Loaded Plug-ins tab of the Support Information dialog.sca file. How do I view the log console/How do I send the client logs to the server? As a prerequisite. How do I enable the startup trace in the application? As a prerequisite. right-click and choose Show Message Log Console. During the loading of the client. When launching the application. For example: http://<host>:<port>/sap/fcprt?app-config=<app config name>&show-trace=startup 9. enable the tracing on the client. What do I do if the application does not start? In SAP GUI. enter transaction SE80. How do I see the version information of the plug-ins? As a prerequisite.

<DISPLAY_USER ROLE>.7 Troubleshooting Component-Level Logs The version information is available in the SAP_MANIFEST file in the MANIFEST folder of the sca archive file. Setting Up Support User Create a role./POA/ AUI_FOLDER /POA/PSAPP:* /POA/PSACT:CREATECHILD /POA/ACDTP:* /POA/AUTHT:F 04/23/2012 PUBLIC 55/60 ./POA/ BUI_USER_PREFERENCES /POA/PSAPP:* /POA/PSACT:CREATE /POA/ACDTP:* /POA/AUTHT:F /POA/A_BUI /POA/CNTTP:* /POA/RESTP:/POA/BUI_USER_PREFERENCES /POA/PSAPP:* /POA/PSACT:UPDATE /POA/ACDTP:* /POA/AUTHT:F /POA/A_BUI /POA/CNTTP:* /POA/RESTP:/POA/BUI_USER_LINK.6 6. with limited READ rights using /POA/A_BUI authorization object with the following field value entries: Authorization Object Field Value Entries /POA/A_BUI /POA/CNTTP:* /POA/RESTP:* /POA/PSAPP:* /POA/PSACT:READ /POA/ACDTP:* /POA/AUTHT:F /POA/A_BUI /POA/CNTTP:* /POA/RESTP:/POA/AUI_FOLDER.

9 Troubleshooting for Event & Notification If messages are not being delivered. in the Content Lifecycle Management application. /POA/SUBNS. 56/60 PUBLIC 04/23/2012 . 6.8 Troubleshooting Troubleshooting for CLM If the application is used with sub namespaces. check the scheduled jobs for event and notification. Assign POA/A_FCP authorization object with authorization field value: /POA/CFCP: R Assign the above role for the support user along with the roles /POA/BUI_FLEX_CLIENT and /POA/BUI_UM_USER. go to transaction SE38 and run the report for a specific content group. where the content group is in error status. It allows you to display the content group metadata and to see the breakdown of content records. For more information about monitoring the jobs required to send messages to e-mail. 6. In the SAP GUI. see the installation guide. and a value equal to the value of sub namespace. you also need to assign /POA/A_BPT authorization object to the role with the same field values as for /POA/A_BUI authorization object.6 6. You need an additional entry for field name.8 Troubleshooting for CLM You can use the error report /POA/R_CLM_CG_REP01 to diagnose issues and problems with content group extracts.

2 Problem Message Handover Problem messages can be logged at SAP Support Portal on SAP Service Marketplace. Note It is not necessary to use component strings to use the support portal. since their use removes the need for SAP Support to dispatch your message to the appropriate support personnel. For information about SAProuter. However. The following component strings are available: Component String EPM-BPC-NW Area Planning and Consolidation as a whole 04/23/2012 PUBLIC 57/60 .7 Support Desk Management 7 Support Desk Management 7. For this support.com/. see the following SAP Note: SAP Note Title Comment 812386 RFC connection to the SAPNet R/3 front end 7.sap. which is located at http://service.1 Remote Support Setup SAP support needs to be able to work remotely for highest efficiency and availability. they can reduce processing time. see the following SAP Note: SAP Note Title Comment 486688 Schedule VPN connection to SAP network See also the SAP Notes that this SAP Notes refers to for specific settings or parameters that are necessary For further assistance. You use component strings to efficiently direct your support message. SAP uses the remote connection with SAProuter for a specific problem that you log by creating a customer message in the SAP Support Portal.

7 7.2 Support Desk Management Problem Message Handover EPM-BPC-NW-DOC EPM-BPC-NW-TRA Documentation Transport Administration: EPM-BPC-NW-ADM Component String EPM-BPC-NW-ADM-APP EPM-BPC-NW-ADM-DIM EPM-BPC-NW-ADM-K2 EPM-BPC-NW-ADM-SEC EPM-BPC-NW-ADM-TDL EPM-BPC-NW-ADM-WS Area Application Management Dimension Management K2 Script Logic Security Table Driven Logic Work Status Data Manager: EPM-BPC-NW-DM Component String EPM-BPC-NW-DM-PAC EPM-BPC-NW-DM-RUN EPM-BPC-NW-DM-SCH Area Package Management Package Execution Schedule Installation: EPM-BPC-NW-INS Component String EPM-BPC-NW-INS-NW Area ABAP Installation Web Client: EPM-BPC-NW-WEB Component String EPM-BPC-NW-WEB-CNT EPM-BPC-NW-WEB-REP EPM-BPC-NW-WEB-STA Area Documents View Web Reports Getting Started POASBC Component Component String XAP-SBC-BUI-ABA XAP-SBC-BUI-UI Area ABAP Backend Flex UI 58/60 PUBLIC 04/23/2012 .

7 7.2 Support Desk Management Problem Message Handover Content Lifecycle Management Component String XAP-SBC-CLM Area Content Lifecycle Management 04/23/2012 PUBLIC 59/60 .

sap.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.com © Copyright 2012 SAP AG. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind. . zu welchem Zweck und in welcher Form auch immer. All rights reserved.

Sign up to vote on this title
UsefulNot useful