Nw Bpc 101 Administration Guide

Administrator's GuideDocument version: 1.3 2014-11-28

SAP Business Planning and Consolidation 10.1version for SAP NetWeaver

CUSTOMER

Copyright 2014 SAP SE or an SAP affiliate company. Alle Rechte vorbehalten. All rights reserved. Tous droits rservs. .Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.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.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 Support Services and may not be modified or altered in any way.

2

CUSTOMER Copyright 2014 SAP SE or an SAP affiliate company.All rights reserved. SAP Business Planning and Consolidation 10.1

Typographic Conventions

Table 1Example Description Angle brackets indicate that you replace these words or characters with appropriate entries

to make entries in the system, for example, Enter your .

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

Example Emphasized words or expressions

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

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

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

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

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

Cross-references to other documentation or published worksExample Output on the screen following a user action, for example, messages

Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

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

EXAMPLE Keys on the keyboard

SAP Business Planning and Consolidation 10.1Typographic Conventions

CUSTOMER Copyright 2014 SAP SE or an SAP affiliate company.

All rights reserved. 3

Document History

CautionBefore you start your implementation, make sure you have the latest version of this guide. You can find the latest version at the following location: help.sap.com/bopacnw101.

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

Table 2Version Date Description1.0 2014-05-14 First version of this document.1.1 2014-06-11 Updated the topic Important SAP Notes with the central notes for SP01 and SP02.1.2 2014-09-15 Updated the topic Important SAP Notes with the central note for SP03.1.3 2014-11-28 Updated the topic Important SAP Notes with the central note for SP04.

4

CUSTOMER Copyright 2014 SAP SE or an SAP affiliate company.All rights reserved.

SAP Business Planning and Consolidation 10.1Document History

Content

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

2 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Monitoring of Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.1 Setting up a Minimal-Access User to Configure SMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.2 Enabling the Auto-Alert Mechanism in CCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.3 Availability Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.4 Component-Specific Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.5 Detailed Monitoring and Tools for Problem and Performance Analysis . . . . . . . . . . . . . . . . . . . . . . . . 11

Displaying Statistics of Backend Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Workload Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Data Growth and Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.6 Setting Up SAP Solution Manager as a Central Monitoring System . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4 Management of Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.1 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.2 Backup Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.3 Best Practices for Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Processing Tiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Cube Fact Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Cube Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Cube Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Writeback Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 SQE Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Management of Data Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.4 Set Up of BPF E-mail Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.5 Administration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.6 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.7 Scheduled Periodic Tasks for Event & Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5 Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.1 Transport Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Transport Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Transport Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Transport Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Transport Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Transport Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

5.2 Development Requests and Development Release Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

SAP Business Planning and Consolidation 10.1Content



5.3 UJA_DATA_CHECKER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.4 UJA_REFRESH_DIM_CACHE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.1 Troubleshooting in Business Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.2 Analyzing Problems Using Solution Manager Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.3 Installing Appsight Black Box Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.4 Generating and Analyzing Trace Files Using E2E Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.5 Logging and Tracing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Logging and Tracing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6.6 Troubleshooting Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376.7 Component-Level Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396.8 Troubleshooting for Event & Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

7 Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427.1 Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427.2 Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6


SAP Business Planning and Consolidation 10.1Content

1 Getting Started

CautionThis guide does not replace the daily operations handbook that we recommend customers create for their specific production operations.

About this GuideDesigning, implementing, and running Planning and Consolidation at peak performance 24 hours a day has never been more vital for your business success than now.This guide provides a starting point for managing Planning and Consolidation solutions and maintaining and running them optimally. It contains specific information for various tasks and lists the tools that you can use to implement them. This guide also provides references to the documentation required for these tasks, so you will sometimes also need other documentation such as the Master Guide and the SAP Library application help.

SAP Business Planning and Consolidation 10.1Getting Started



2 Important SAP Notes

Refer to these central notes for installation instructions and important information about each release.

CautionCheck regularly to see which SAP notes are available for SAP Business Planning & Consolidation.

Table 3Central Note Number Release

1916316 SAP Business Planning & Consolidation 10.1 for SAP NetWeaver

2023281 Support package 4 of SAP Business Planning & Consolidation 10.1 NW




8


SAP Business Planning and Consolidation 10.1Important SAP Notes

3 Monitoring of Planning and Consolidation

You use the monitoring capabilities of SAP NetWeaver to monitor Planning and Consolidation.Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions.The aim of this section is to provide information and documentation to monitor the application, for example by utilizing the Computing Center Management System (CCMS) and NetWeaver ABAP monitoring tools.

RecommendationSince the application is powered by SAP NetWeaver 7.4, we recommend that you set up the monitoring infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplace at service.sap.com/instguides.

This contains all the information relevant to monitoring the SAP NetWeaver components used in the application.Proficient knowledge of system monitoring and basic knowledge of SAP NetWeaver is required to compose user-defined monitors. For more information about monitoring in the CCMS, see SAP Help Portal at help.sap.comSAP NetWeaver .

3.1 Setting up a Minimal-Access User to Configure SMDThe SAP Solution Manager and Diagnostic (SMD) tool can be used to provide Web services, such as monitoring, with the Central Computing Management System (CCMS).The user who performs these monitoring and diagnostic services does not need to be able to manipulate the Planning and Consolidation data. Therefore, it may be advisable to create a user with minimal access rights and configure SMD to access Planning and Consolidation with this user. The following procedure describes the creation and configuration of such a user.

Procedure

1. Log on to the EnvironmentShell environment through the Admin client.2. Choose Security Users and then select Add new user from the Session Information action pane.3. In the Users view, select Add. In the Add User assistant, select the user to add in the environment.4. Choose Next for all remaining steps of the assistant without assigning the user to a team.5. Choose Finish.6. In Users, check that the user has no teams or profiles assigned to it. Select the user and choose Edit. This

displays details of the team, task profile, and data access profile assignments for the user.7. Configure the SMD connection to Planning and Consolidation to use this user.

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

SAP Business Planning and Consolidation 10.1Monitoring of Planning and Consolidation



3.2 Enabling the Auto-Alert Mechanism in CCMS

The basis for application-specific alert monitoring is the NetWeaver CCMS alert monitoring framework.To enable the auto-alert mechanism of CCMS, see the following SAP Note:Table 4SAP Note Number Title Comment

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

3.3 Availability Monitoring

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

Features

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

NoteFor availability monitoring, set up and use a Planning and Consolidation user with minimal access privileges for monitoring and diagnostics related web services, such as GRMG web services. For more information, see Setting up a Minimal-Access User to Configure SMD [page 9].

To configure the GRMG scenario for Planning and Consolidation, perform the following steps:1. Using a suitable XML editor, edit the template customizing file BPCNW_Customizing.xml. You must specify

the URL of the scenario (host and port), as well as the username and password.2. Save your entries.3. Log on to the Central Monitoring System (CEN).4. Go to transaction GRMG. To do that, in the execution text field in the upper left corner, enter /nRZ20 and

press Enter.5. Choose Upload and select the relevant scenario.6. Once the scenario is uploaded, verify the content is correct by choosing Edit/Delete.7. Choose Start.

10



3.4 Component-Specific MonitoringExisting CCMS monitoring sets can be used to monitor various resources, objects, and performance. For example, SAP CCMS monitor template, which can be used to monitor system, database, and background processing for the application server where the application is running.The following existing monitors within RZ20 can be used by the application to monitor critical conditions:Database MonitoringYou can monitor the RDBMS connection using the CCMS database monitor. This is the connection to the system where the application is installed and in use.Operating System MonitoringOperating system monitoring capabilities within CCMS administration workplace are used to analyze CPU, memory, paging, disks, file system, and their corresponding health statuses.Dialog OverviewUsing dialog monitoring in RZ20, the response time for dialog, network time, and number of currently logged-in users can be observed.Error MonitoringThe log file for SAP Business Planning and Consolidation is monitored for error patterns. The monitor presents its status and alerts according to the presence of error messages in the SAP Business Planning and Consolidation log. If errors occur in this log, you can display them in transaction CCMS by selecting Open Alerts.

3.5 Detailed Monitoring and Tools for Problem and Performance Analysis

This section describes the trace files, log files, and monitors you can use for detailed monitoring. These are useful for problem solving and performance analysis.

3.5.1 Displaying Statistics of Backend PerformanceUse transaction UJSTAT to display statistics of backend performance.

3.5.2 Trace and Log FilesThe following table describes the trace and log files for the application components.Table 5Component Content File Path

Core components and services

Log messages pertaining to workflow (alerts, fatal messages, errors, status

Log messages on client side are in memory. There is an option to export the

N/A




Component Content File Pathupdates). Messages are also shown in the common message region in the top-right corner of the container. Traces are enabled through log message APIs

messages to the server. These messages are for viewing and analyzing in the administrator tool for the application

- System Trace Analysis RFC, HTTP, DB

- Transaction ST01

- SQL Performance Trace and Analysis RFC, HTTP, DB

- Transaction ST05

All logs related to runtime exceptions are recorded. Check BUI log in SLG1

3.5.2.1 Logging of Exceptions in the SLG1 SystemWhen an exception occurs, relevant information is logged in the SLG1 system. This allows for improved tracing and diagnosis of any exceptions that occur.The detailed information is written in the log item and saved in the database. In the log, the object is identified as UJ and the subobject is identified as UJK.

ExampleThe following script refers to an invalid member, A1000:*XDIM_MEMBERSET ENTITY=A1000*WHEN TIME*IS 2006.JAN*REC(FACTOR=1.2)*ENDWHENThis generates an exception and produces the following message in the log:Member "A1000" does not exist

FeaturesThe following sub-objects are available in the system:UJ0UJAUJBUJCUJD

12



UJEUJFUJGUJHUJIUJJUJKUJLUJNUJOUJPUJQUJRUJTUJTMUJT_BACKUP_RESTOREUJUUJVUJWUJXUJYUJZUJ_UT

3.5.2.2 Trace File for Debugging LogicYou can turn on tracing for script logic and business rules when you need to troubleshoot a particular script or rule. We recommend that only experienced Business Planning and Consolidation consultants and support personnel use this. We also recommend that these files are removed periodically since they take up a considerable amount of space.The activity is recorded in a file called debuglogic.log and stored in \webfolders\\\privatepublication\\.

3.5.2.3 Data Manager Log FilesWhenever you use a Data Manager package to move Business Planning and Consolidation data, the system creates a log file. This file can be useful in troubleshooting the execution of packages. We recommend that you remove these files once the packages have completed since they take up a considerable amount of space.




These logs are stored in \webfolders\\\privatepublication\\tempfiles.The name of the log file contains the following details: The name of the package A timestamp The extension .LOG

ExampleValidatetransformation20090915211503.log

3.5.2.4 Trace and Log Files for Context & InsightsTable 6Component Content Path

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

/POA/CTX/REST

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

/POA/CTX/SERVICE

3.5.3 Workload MonitorsA default workload collector as part of CCMS monitoring and the workload monitor through transaction ST03N observes the workload records at the application server level.Table 7Monitor Detailed Description Prerequisites

Workload Monitor Transaction ST03N

Detailed analysis of the workload of application servers

None

3.5.4 Data Growth and Archiving MonitorsTable 8Component Monitor Detailed Description Prerequisites

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

Switch the trace on before performing costly operations

14



3.6 Setting Up SAP Solution Manager as a Central Monitoring System

SAP Solution Manager can be used as a central monitoring system for SAP Business Planning and Consolidation for NetWeaver. Basic availability monitoring (GRMG scenario), error monitoring (log file monitoring), and operating system monitoring (process monitoring) are supported.

ProcedureTo set up SAP Solution Manager as a central monitoring system, see SAP Note 1379214.




4 Management of Planning and Consolidation

4.1 Starting and StoppingThe following table describes the sequence for starting and stopping the application.Table 9Software Component Start and Stop Sequences and Tools

- Sequence Tool Detailed Description

Software Component: POASBC

1 Example: STARTSAP STARTSAP (UNIX)SAP Management Console

The application is based on SAP NetWeaver infrastructure. For more information, see the Technical Operations Manual on SAP Help Portal at

help.sap.com SAP NetWeaver .

4.2 Backup Best PracticesProcedureRefer to the following items for information about backing up your Business Planning and Consolidation system:1. On the SAP Help Portal, refer to the backup procedures at help.sap.com/saphelp_nw70/helpdata/EN/7c/

efa841c1dade34e10000000a1550b0/content.htm.2. On SAP Service Marketplace at service.sap.com/solutionmanagerbp, refer to documents 084 Business

Continuity Management for SAP System Landscapes and 085 Emergency Handling for Recovery of SAP System Landscapes.

3. On the SAP Developer Network at www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30c221aa-b4e5-2910-b899-d268d84c19c5, refer to the article entitled Architecting a high availability SAP NetWeaver infrastructure.

4.3 Best Practices for Performance ManagementA number of factors affect Business Planning and Consolidation performance, including the following: Number of dimension members

16


SAP Business Planning and Consolidation 10.1Management of Planning and Consolidation

Amount of transactional data in a given model Number of concurrent users Hardware Network bandwidth Management of data volume

4.3.1 Processing Tiers

To optimize performance, it is useful to understand the system tiers and the processing that occurs on those tiers.Table 10Tier Description

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

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

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

data, conversion files, and transformation files)

NetWeaver ABAP Application Server

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

BI Accelerator (an optional component)

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

4.3.2 Cube Fact Tables

Each InfoCube has the following two fact tables: E fact table, for compressed records F fact table, for uncompressed records

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




4.3.3 Cube OptimizationOptimizations have been implemented as process chains. As such, you can schedule them using Data Manager or execute them using Administration.For more information about modifying and scheduling optimization process chains, see the Data Manager section in the application help. For more information about executing optimization process chains, see the Administration section in the application help.

4.3.4 Cube ModificationDuring the optimization process, Business Planning and Consolidation creates a shadow cube and moves the data to that cube when the system determines a data model reorganization is needed (for performance reasons). Any external modifications made to the cube (for example, through transaction RSA1) are lost, and are not moved with the data. These modifications include such things as tablespaces, BI Accelerator indexes, DTPs (distributed transaction processing), aggregates, and database performance parameters.

4.3.5 Writeback ParametersYou can modify writeback parameter values in transaction UJR0. These values are maintained at the individual model level. In general, you will not need to change the default values.Table 11Parameter Default Description

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

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

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

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

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

18



4.3.6 SQE ParametersYou can modify SQE parameter values in transaction UJQ0. These values are maintained at the individual model level. In general, it is not necessary to change these values.Table 12Parameter Default Description

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

4.3.7 Management of Data VolumeIn a production environment of Business Planning and Consolidation, data volume might increase gradually over time. The increase in data volume might result in performance degradation in certain modules and system resources might be consumed excessively in some extreme cases.

ProcedureTo avoid this scenario, review and implement the recommended data volume management strategies described in SAP Note 1705431.

4.4 Set Up of BPF E-mail NotificationsUse this procedure to set up e-mail notifications sent by business process flows.

PrerequisitesEnvironment users must have e-mail addresses.

FeaturesOwners are notified by e-mail when a BPF instance is created and actions are taken. In addition, they are notified when an instance has been completed and ready to be finalized.Reviewers are notified by e-mail when a step region is ready for review.

ExampleSubject: BPF instance now ready for action




Text: BPF Instance for dimensions time 2009.total and category budget. Step region(s): first active step number and step region dimension:member. As a participant in this business process please select the following link: HTTP://sample_link/.

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

Types of BPF e-mailsBusiness Planning and Consolidation contains a number of e-mail templates by default. These are S-type (system) templates, which you cannot modify. You can, however, create a copy of each system template and customize the copy for your business needs. These are C-type (customized) templates.You can customize the title and body of C-type (customized) e-mail templates. You can input multi-language text in the e-mail body, and you can add the following variables to display information in the e-mail to help its recipient: %INST_NAME% %STEP_NAME% %URL% %STEP_REGION_NAME%

Managing BPF e-mailsSet up and customization of BPF e-mail notification templates is done on the back-end. Perform the following steps:1. In SAP GUI, choose transaction code SE80 for the Object Navigator.2. Choose Package in the left navigation pane, then enter the package name UJB.3. Choose Programs, then run UJB_MAINTAIN_EMAIL_TMPL.

You create a copy of a system template by selecting a system template then clicking the Create customized email template icon in the toolbar. Then, modify it as needed.

4.5 Administration Tools

4.5.1 Logs

The application writes logs during various activities at runtime; these can be used by administrators for auditing and monitoring purposes. Application Log: Every operation and corresponding steps carried out during that operation are recorded in

the application log:Transaction SLG1, log object UJ.The application log includes detailed information about error messages and sequential flow with respect to technical processing in the application.This object includes the UJA subobject.

20



4.5.2 Load BalancingAs a web-based application, the basis for logon and load balancing is a high availability landscape setup together with a load balanced network setup.For more information about network load balancing, see the Technical Infrastructure Guide for SAP NetWeaver on SAP Service Marketplace at service.sap.com/instguides.A load-balanced network using SAP Web Dispatcher together with logon groups in the SAP NetWeaver systems can be used to redirect certain users to specific application servers.

4.5.3 User ManagementAll scenarios and components in the application use the user management functions provided by NetWeaver.For more information about user administration and authentication, see the application security guide on SAP Service Marketplace at service.sap.com/securityguide.

4.6 Backup and RestoreThe following table describes methods for backup and restore for application components:Table 13Categories of System Components

Category Properties Suggested Methods for Backup and Restore

Examples

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

Data: Database and log

backup, application log backup (such as job logs in file system)

Backup of software, configuration log files

Standalone SAP ERP

4.7 Scheduled Periodic Tasks for Event & NotificationTable 14Program Name/Task Task Scheduling Tool Recommended Frequency Detailed Description

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




Program Name/Task Task Scheduling Tool Recommended Frequency Detailed Description

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

Reorganize and reconciliation job

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

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

22



5 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams. The goal of Software Change Management is to establish consistent, solution-wide change management that allows for specific maintenance procedures, global rollouts (including localizations), and open integration with third-party products. This section provides additional information about the most important software components.

5.1 Transport ManagementTransports allow you to move an environment across a landscape. For example, you can transport an environment from a development system to a test system and then to a production system.Two modes of transport are supported: Normal mode For modifying and creating objects. In this mode, if a transported object exists in the target

system, it is modified with the changes from the source system. If it does not exist, it is created. Deletion mode For deleting objects. In this mode, you explicitly specify the objects to delete.

All aspects of an environment are transported except transaction data.You can transport the changes associated with an environment without having to transport the entire environment. You can transport one or more models at a time, and select individual components of a model, for example, dimensions, members, logic script files, work status, reports, and so on). You can transport the deletion of models, dimensions, Data Manager packages (deletion includes renaming, moving and deleting a package), Data Manager package groups (deletion includes renaming and deleting a package group) and Data Manager package links.You can also collect NetWeaver objects into a transport request, such as NetWeaver process chains. To move process chains into your production environment, use the SAP NetWeaver transport process for process chains. The process chain must be assigned to component /cpmb/BPC.The following subsections contain a description of the transport process and some other useful information about transporting. If you have problems with transports, see Troubleshooting Transport [page 37].

5.1.1 Transport ObjectsThis section lists the objects that you can transport for environments and models.Environment ObjectsYou can transport the following objects for an environment: Business Rule Configuration Dimension

SAP Business Planning and Consolidation 10.1Software Change Management



Model Script Logic Task Profile

Model ObjectsYou can transport the following objects for a model: Books Template Business Process Flow Template Business Rule Business Unit Configuration Control Data Access Profile Data Manager Conversion File Data Manager Data File Data Manager Package Data Manager Package Group Data Manager Package Link Data Manager Transformation File Dimension Dimension Master Data Drill Through Journal Template Report File Report Templates Script Logic Task Profile Team Web Documents Work Status Settings

5.1.2 Transport ConfigurationBefore you can transport, you must first configure the SAP NetWeaver transport framework.SAP NetWeaver includes the Change and Transport System (CTS), which is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your system landscape.For more information, see the SAP NetWeaver Technical Operations Manual on SAP Help Portal at

help.sap.com SAP NetWeaver .

24



PrerequisitesYou are the SAP NetWeaver administrator.

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

aspects of a transport.For information, see Change and Transport System in the SAP NetWeaver Application Help on the SAP Library at help.sap.com.

2. Configure the system to import Client-Dependent Objects, as all Planning and Consolidation data is client-dependent. Do the following: Create user ALEREMOTE (BW background user) Create an RFC destination to allow the import method to be executed in the correct client. Otherwise, it is

executed in client 000. Use transaction RSTPRFC to create the destination for this client.For information, see Importing Client-Dependent Objects in the SAP NetWeaver Application Help on the SAP Library at help.sap.com.

3. Select the objects to transport.For information about transport objects, see Transport Objects [page 23].

5.1.3 Transport ExecutionThe topics in this section explain how to perform a transport of objects from a source environment to a destination environment and how to delete an object in a destination environment after it has been removed from the source environment.

5.1.3.1 Transporting EnvironmentsYou select the objects to transport from the hierarchy of objects in the environment. This allows for the granular selection of objects. Only the objects that you select are transported. You can transport objects with or without corresponding dependent objects. However, if you transport an object but do not include its dependent objects in the transport, a warning is generated.

RecommendationWe recommend that you do not add a normal transport and a deletion transport for the same environment into one customizing request. For more information, see SAP Note 1583670.

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




2. In the left column, select Transport Connection.3. Select the objects to transport:

1. In the left column, select SAP Transport Object Types .2. In the middle column, select More Types BPC Environment .3. Double-click Select Objects.4. In the dialog box, select the environment to be transported and click Transfer Selections.5. In the right column, the objects in the environment are listed. Select the objects to be transported by

selecting or deselecting the corresponding object.4. Generate a customizing request:

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

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

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

5. Release the customizing task:1. Select the task under the customizing request you just generated.2. Click Release directly.

Transport ErrorsIf transport fails for an object, the changes for that object are not made in the target system. The object in the target system remains unchanged. This does not affect the transport of other objects to the target system.

5.1.3.2 Deleting Objects by TransportAfter an object has been deleted in the source system, you can mark it for deletion in the target system. You can select the deleted objects to transport. However, you can select only deleted objects for which there are no dependencies.The following objects support transport deletion: Models Dimensions Data Manager packages Data Manager package groups Data Manager package links

RecommendationWe recommend that you do not add a normal transport and a deletion transport for the same environment into one customizing request. For more information, see SAP Note 1583670.

26



Procedure

1. Logon to the source system and enter transaction code RSA1.2. In the left column, select Transport Connection.3. Select the deleted objects to transport:

1. In the left column, select SAP Transport Object Types .2. In the middle column, select More Types BPC Deletion .3. Double-click Select Objects.4. In the dialog box, select the environment to be transported and click Transfer Selections.5. In the right column, all objects in the environment which have been deleted (and which do not have

dependent objects that still exist) are listed. Select the deleted objects to be transported by selecting or deselecting the corresponding object.

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

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

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

5. Release the customizing task:1. Select the task under the customizing request you just generated.2. Choose Release directly.

Deletion ErrorsIf deletion fails for an object, the changes for that object are not made in the target system. The object in the target system remains unchanged. This does not affect the deletion of other objects in the target system.

5.1.4 Transport Log Files

After a transport has been completed, you can view the transport log. The log reports the successful completion of a transport request, as well as warnings and errors encountered during the transport.

Procedure

To view a transport log file:1. Select a released request.2. Click Transport Logs.




5.1.5 Transport MaintenanceThere are certain maintenance tasks involved with transports.

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

5.1.6 Deployment ScenariosThere are two typical landscape deployment scenarios.

Development to ProductionIn the Development to Production deployment scenario, you create and maintain an environment in development. All dimensions, dimension properties, and models are created in development. A decision needs to be made for all other objects.Typically, all objects are created in development and transported to production. The exceptions include security and teams, which typically are handled landscape by landscape.Additionally, the decision would need to be made for workbooks (report templates and input schedules). If this is done in development, then workbooks in production would be overwritten. If this is done in production, then workbooks from development are not transported.

Production Only (with Development for patch testing)In this scenario, you work in production only. When you need to apply a patch, you transport the environment from Production to Development. You test the patch in Development. After the patch is validated, you apply the patch to Production.

Best Practices for Ongoing DevelopmentSome customers have release cycles in which they are unable to transport an entire environment. For example, they may have a configuration that has Production support changes and another configuration on the same model or environment that is transported at a later stage in the project cycle.In this case, you should have two environments in development: one for new development, and one for production support changes. When a production support change occurs, this should be done in both environments in development. When the cutover of new development needs to be transported, then the configuration can be moved to the production support environment and transported.

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.

28



It is an efficient method of transporting a selected number of requests into a group of transport targets, and uses clearly defined approval steps to ensure the quality of your target systems.For more information, see the Technical Operations Manual on SAP Help Portal at help.sap.com SAP NetWeaver .

5.3 UJA_DATA_CHECKERTo run UJA_DATA_CHECKER, log onto the BW server, go to transaction code SE38, then execute UJA_DATA_CHECKER.

5.4 UJA_REFRESH_DIM_CACHEUse the program UJA_REFRESH_DIM_CACHE to sync the dynamic dimension table and BW dimension table. This clears the cache, but does not delete dimension members and transaction data.To run UJA_REFRESH_DIM_CACHE, log onto the BW server, go to transaction code SE38, then execute UJA_REFRESH_DIM_CACHE.




6 Troubleshooting

6.1 Troubleshooting in Business Planning and ConsolidationThe following table lists a problem that you may encounter and a suggestion for resolving the problem:Table 15Problem Analysis Solution

Marginal text and buttons in Business Planning and Consolidation dialog boxes are unreadable or incorrectly formatted.

Determine the DPI font settings in the host computer.

On the Settings tab in the Microsoft Windows Display Properties dialog box, choose Advanced. On the General tab, ensure that the DPI setting is 96 DPI.

6.2 Analyzing Problems Using Solution Manager DiagnosticsThe diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems. For information about setting up Solution Manager Diagnostics, see Connecting to Solution Manager Diagnostics in the Planning and Consolidation NW Installation Guide.

6.3 Installing Appsight Black Box ServiceProcedure1. Download and extract the *.rar files attached to SAP Note 1356729 from SAP Service Marketplace.2. Create a directory on your C:\ drive called Identify.3. Copy either Triserv2.rpr or Triserv_XpressServer.rpr file into the Identify folder depending on what

application is needed to be monitored. Triserv2.rpr

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

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

4. Install AppSight Black Box Service in standalone mode.1. Run AppSight Black Box Service.exe.2. Select Install.3. Accept the agreement and choose Next.4. Enter any information for username and company name and choose Next.

30


SAP Business Planning and Consolidation 10.1Troubleshooting

5. Leave the server prompt blank for standalone mode and choose Next.6. Leave Black Box with no license option and choose Finish.

5. Copy the startservice.bat and stopservice.bat files into the Identify folder.Startservice.bat starts the application using the profile path and the naming convention for the log. Stopservice.bat stops the Black Box application. You must stop the application before you can copy the log.

6. Run startservice.bat to begin logging.Once you start the application, the Identity folder contains an .ASLfile, which is the log that will write all the information from the application. The computer name and date are used as a variable for the naming convention.The log stays at 0 bytes until the service is stopped and only then is its actual size shown.

RecommendationStop and start the service at the end of each day, copy the file to another folder, and have the application create a new one. This allows you to monitor the file size.

6.4 Generating and Analyzing Trace Files Using E2E TraceYou can generate trace files on client and server components for troubleshooting purposes using E2E Trace. Trace files collect information about client and server interactions presenting trace information about the entire request and response of a business process step. The trace files then upload to the server for analysis in SAP Solution Manager Diagnostics (SMD). Client side and server side trace information is displayed in the E2E Trace application in SMD.E2E Trace is delivered and installed with Business Planning and Consolidation. To configure and activate tracing on a client machine, see Logging and Tracing Configuration [page 33].After enabling and running tracing, you can obtain information about evaluating the results of the trace in the E2E Trace Analysis - User Guide in the Diagnostics section of SAP Service Marketplace.

Prerequisites Ensure that the latest Business Planning and Consolidation Clients with the E2E Trace plug-in are installed on

your client machine. The minimum release on the SAP Solution Manager Diagnostics side for E2E Trace Analysis is Solution

Manager 7.0 EhP 1 SP23.

ProcedureGenerating and analyzing trace files using E2E Trace involves the following tasks, which are described below: Enable tracing in the ABAP back-end system Perform a trace in the Administration module Perform a trace in the Microsoft Excel module Manually upload the trace file to SMD if not done automatically Evaluate the trace file in SAP Solution Manager




Enable Tracing in the ABAP Back-end System1. Enter the Root Cause Analysis work center of SAP Solution Manager.2. Choose End-To-End Analysis.3. Select the query that contains all systems involved within the E2E trace and select the system ID of the

Business Planning and Consolidation ABAP stack.4. Choose Trace Analysis, which opens a new window with the E2E Trace Analysis application.5. Select the Trace Enabling tab.6. Select the system ID of the Business Planning and Consolidation ABAP stack.7. Select Enable. A green icon displays besides the system ID.

Perform a Trace of the Microsoft Excel Module1. Launch the E2E Plug-In by running plugin-starter-gui.exe.2. Select Microsoft Office Excel and choose Launch.3. After Excel is launched, enter the following values in the E2E Trace Plug-in user interface:

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

2. Set the Session Trace Level to High.3. Enter the SMD server host.4. Enter the SMD HTTP port.

4. Click Log On in the EPM menu in Excel.5. Choose Start Transaction in the E2E Trace Plug-in user interface, then choose OK to log on to the Excel

module.6. Choose Stop Transaction in the E2E Trace Plug-In user interface to upload the transaction XML to the SMD

server.7. In the E2E Trace application within SMD, collect the corresponding trace of the ABAP server.

Manually Upload the Trace FileIf you need to manually upload a trace file to SMD, perform these steps:1. On the client machine on which you recorded the trace, expand the Manually upload section.2. Choose Browse under Upload BusinessTransaction.xml. The file to upload appears in \Logs.3. Select the BusinessTransaction.xml file and choose Upload.

Evaluation of Traces in SAP Solution Manager1. In SAP Solution Manager, access the Root Cause Analysis work center.2. Choose End-To-End Analysis.3. Select the query that contains all systems involved within the E2E Trace and select all systems.4. Choose Trace Analysis to open a new window with the E2E Trace Analysis application.5. Select the trace from the list.6. If you want the SMD to collect corresponding server side trace data, choose Select systems for trace

collection dynamically.

32



NoteThis starts trace data collection and results in a list of success or error messages. If you forgot to enable tracing or wait too long between trace recording and trace data collection (for example, more than one day), trace data may not be found.

7. Select the first step of the recorded E2E Transaction Trace and choose Display.8. Select the Summary tab if it is not selected.9. Select the Message table tab.10. Expand the tray Server Analysis and choose the Request tree tab.11. Choose Expand all to see incoming http calls, outgoing DOTNET Connector calls, and incoming RFC calls,

then do one or more of the following: To view Introscope Transaction Trace data, select a line with incoming http calls, then choose Display

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

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

Trace Summary.

More Information Logging and Tracing Configuration [page 33] Log and Trace File Management (in the application help in the SAP Library at help.sap.com)

6.5 Logging and Tracing ConfigurationYou can create log and trace files for troubleshooting purposes. You can view the log and trace files in the Log Viewer tool of Solution Manager diagnostics after performing the configuration described below.You can create log and trace files for the client.

6.5.1 Logging and Tracing ParametersLogging and tracing parameters use a configuration file named log-configuration.xml. This file is predelivered for the client.

FeaturesStatements in the Log Configuration FileAs delivered, this file contains the following statements:




Syntax

The following sections explain the meanings of the components of each part of the log-configuration.xml file.

Trace SettingsThe following table explains the parameters of the Trace Setting section of the log-configuration.xml file.Table 16Parameter Default Value Meaning

TraceSeverity ERROR You use the trace severity to control the number of trace records that are produced.The following trace severity levels are supported: DEBUG PATH INFO WARNING ERROR DONOTHING

Choosing a severity level means that trace records with the chosen severity, together with all more. severe trace records, are written to the trace file. For example, choosing INFO means that all information, warning, and error trace records are written to the file.DONOTHING is a special severity level. If you set it as value, no trace records

34



Parameter Default Value Meaningare written to file. This is effectively switching off Trace.If you set another value for TraceSeverity, for example, ERR, it is treated as DONOTHING.

TraceDestination Empty The location where you want to store the trace files. For example, .

MaxTraceSize 10 The maximum size of single trace file. The unit is MB.

TraceFileCount 10 Trace files are named BPCtrace.x.logwhere x is a number between 0 and one less than the TraceFileCount.The first trace file to be written is BPCtrace.0.log. When this file reaches the MaxTraceSize, the next file, BPCtrace.1.log, is started. This continues until there are TraceFileCount trace files, whereupon the system overwrites BPCtrace.0.log.

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

Log SettingsThe following table explains the parameters of the Log Setting section of the log-configuration.xml file.Table 17Parameter Default Value Meaning

LogSeverity INFO You use the log severity to control the number of trace records that are produced.The following log severity levels are supported: INFO WARNING




Parameter Default Value Meaning ERROR DONOTHING

Choosing a severity level means that trace records with the chosen severity, together with all more. severe log records, are written to the log file. For example, choosing INFO means that all information, warning, and error log records are written to the file.DONOTHING is a special severity level. If you set it as value, no log records are written to file. This is effectively switching off Logging.If you set another value for TraceSeverity, for example, ERR, it is treated as DONOTHING.

LogDestination Empty The location where you want to store the log files. For example, .

MaxLogSize 10 The maximum size of single log file. The unit is MB.

LogFileCount 10 Log files are named BPClog.x.logwhere x is a number between 0 and one less than the LogFileCount.The first log file to be written is BPClog.0.log. When this file reaches the MaxLogSize, the next file, BPClog.1.log, is started. This continues until there are LogFileCount log files, whereupon the system overwrites BPClog.0.log.

Application Set SettingsThe AppSet parameter of the Application Set Setting section of the log-configuration.xml file is no longer used.

36



6.5.2 Client ConfigurationAt installation, all the configuration items in the log-configuration.xml file have default values. This section contains some considerations when configuring this file.

Features

Trace and Log File DestinationThe defaults for TraceDestination and LogDestination are empty fields. If Business Planning and Consolidation detects these empty fields at user logon, it uses and .

Frequent TasksThe following table details some frequent trace and log configuration tasks:Table 18Task How To

Change the location of the trace or log files Change the value of TraceDestination or LogDestination.

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

Switch off log or trace Set the TraceSeverity or LogSeverity to DONOTHING.

Configuring log-configuration.xmlTo change the log-configuration.xml, open the file with a text editor such as Notepad, make changes, and save the file back to the same location.

6.6 Troubleshooting TransportTransports allow you to move an environment across a landscape. For example, you can transport an environment from a development environment to a test environment and then to a production environment.For detailed information about how to use SAP transports, refer to Transport Management [page 23].

Features

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




Deleting ObjectsThe two major object types exhibit different behavior patterns during the import of a transport into the target system. Table entries and data model objects (model, dimensions, properties) are deleted in the target system when

they are deleted in the development system and the environment is transported. Files such as script logic and Excel templates are only updated. That is, changes to these files are

transported. Since only updates are transported, deleting files in the development system does not impact existing files in the QA or production systems. Similarly, deleting files in the target system does not cause any harm.

After deleting an environment, you can make sure that all data has been removed. Use program UJT_CHECK_TABLE_ENTRIES to check how many records exist in the UJ* database tables for a particular environment.

Choosing Transport StrategiesThere are many SAP transport strategies. Frequently, a QA or production system is built with every released transport from the development system.

RecommendationWe recommend that you build Business Planning and Consolidation systems with the last good transport. Since the Business Planning and Consolidation transport framework can gather all environment objects, the fear of missing something can be alleviated.We also recommend that, after going live, changes are always made in the development system and transported from there to the QA and production systems.

Changing the Data ModelDo not change the data model in target systems. A typical system landscape may contain development, QA, and production instances. If you change objects in a target system, the transports that originate from development will no longer import correctly.Data model changes consist of objects such as environment, model, dimensions, or properties. You can maintain the data model in the QA or production system, but this means that you cannot use the transport framework since it will no longer import properly.Other components, such as reports, input schedules, or data manager packages (not data model related), can be changed in any instance.

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

Changing Technical NamesThe technical name of the InfoCube or Multiprovider may change between landscapes. This is normal. Business Planning and Consolidation does not transport technical names of cubes and the transport works well.

Transport Failure SolutionsThe following table highlights some typical installation and transport failure scenarios and solutions.

38



Table 19Scenario Solution Actions

Installation failed with the error No content objects found

1. Enter transaction code RSOCONTENT.2. Ensure that System is a Content Development System is

not selected.

Import failed with RFC errors Refer to SAP Note 1329651.

Import or installation failed with error: Import still running or UJT_TRANS_OBJECT version 'D' for Environment is filled

1. Enter transaction code SE16 for table UJT_TRANS_OBJECT.

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

3. Reimport the request.

Import failed with the error: Failed to create BI InfoObject for dimension

1. Enter transaction code RSA1.2. See if there are any InfoObjects or InfoCubes that refer

to the attributes of the failed dimension.If so, break the references between Business Planning and Consolidation InfoObjects and your InfoObjects and InfoCubes.

3. Reimport the transport request.

Import failed with the error: Dimension /CPMB/XXXX already exists

Check if anyone has transported this dimension through the BW back end manually. If so, perform the following steps:1. Delete the InfoObjects in the BW back end (use

transaction code RSD1) on the target system.2. Reimport the transport request.

Import failed with the error: Failed to create infoarea

1. Enter transaction code SE06.2. Change the namespaces /CPMB/ and /B28/ to be

modifiable.3. Reimport the transport request.

More Information

SAP Note 1415296.You can also check SAP notes under the application area: EPM-BPC-NW-TRA Transport.

6.7 Component-Level Logs

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




NoteFor SAP Business Planning and Consolidation, replace with bpc.

1. How do I launch the application?http://:/sap/fcprt?app-config=

2. How do I launch the application in debug mode?http://:/sap/fcprt/d?app-config=

3. How do I enable support mode in the application? To enable support mode, the FCP server parameter pp-support-mode=true must be set and the URL query parameter support-mode=true must be used when launching the application.For example: http://:/sap/fcprt?app-config=&support-mode=true

4. How do I see the status of the various plug-ins and the reasons why some plug-ins are not loaded?As a prerequisite, enable support mode.1. After launching the application in support mode, right-click the application and select Support Info.2. In the Loaded Plug-ins tab of the Support Information dialog, you can see information about the loaded

plug-ins, the state of the plug-ins and the error information for plug-ins that could not be loaded.5. How do I see the version information of the plug-ins?

As a prerequisite, enable support mode.1. After launching the application in support mode, right-click the application and select Support Info.2. In the Loaded Plug-ins tab of the Support Information dialog, you can see information about the version

and the build number of the plug-in.6. How do I enable logging and tracing for the application client?

To enable tracing on the client, the FCP server parameter pp-enable-trace=true must be set and the URL query parameter show-trace=true must be used when launching the application.For example: http://:/sap/fcprt?app-config=&show-trace=trueLogging is always enabled on the client (though you can technically set logging level to NONE, which would mean no statements are logged on the client; this is not recommended). To configure which levels of statements to be logged, set the FCP server parameter pp-log-filter to one of the appropriate values (ERROR|FATAL|SUCCESS|WARNING|INFO|NONE|*)For example: To enable only statements with levels ERROR and FATAL to be logged, set pp-log-filter=ERROR|FATAL

7. How do I enable the startup trace in the application?As a prerequisite, enable tracing on the client.When launching the application, use the URL query parameter show-trace=startup. During the loading of the client, you see a dialog with the trace information collected during startup.For example: http://:/sap/fcprt?app-config=&show-trace=startup

8. How do I view the log console? How do I send the client logs to the server?As a prerequisite, enable logging and tracing on the client.

40



After launching the client, right-click and choose Show Message Log Console. The dialog box displays the logs and traces. The dialog also provides an option to transmit the client logs to the server and to turn off tracing on the client for the session duration.

9. What do I do if the application does not start?In SAP GUI, enter transaction SE80. Go to the MIME Repository and open SAP POA FCP Container . Download the POASBCBUI00_0.sca file.The version information is available in the SAP_MANIFEST file in the MANIFEST folder of the sca archive file.

6.8 Troubleshooting for Event & NotificationIf messages are not being delivered, check the scheduled jobs for event and notification.For more information about monitoring the jobs required to send messages to e-mail, see the installation guide.




7 Support Desk Management

7.1 Remote Support SetupSAP support needs to be able to work remotely for highest efficiency and availability. For this support, SAP uses the remote connection with SAProuter for a specific problem that you log by creating a customer message in the SAP Support Portal. For information about SAProuter, see the following SAP Note:Table 20SAP Note Title Comment

486688 Schedule VPN connection to SAP network

See also the SAP Notes that this note refers to for specific settings or parameters that are necessary.

For further assistance, see the following SAP Note:Table 21SAP Note Title Comment

812386 RFC connection to the SAPNet R/3 front end

None

7.2 Problem Message HandoverProblem messages can be logged at SAP Support Portal on SAP Service Marketplace, which is located at service.sap.com/.You use component strings to efficiently direct your support message.

NoteIt is not necessary to use component strings to use the support portal. However, they can reduce processing time, since their use removes the need for SAP Support to dispatch your message to the appropriate support personnel.

The following component strings are available:Table 22Component String Area

EPM-BPC-NW Business Planning and Consolidation as a whole

EPM-BPC-NW-DOC Documentation

EPM-BPC-NW-TRA Transport

Administration

42


SAP Business Planning and Consolidation 10.1Support Desk Management

Table 23Component String Area

EPM-BPC-NW-ADM Administration

EPM-BPC-NW-ADM-APP Application Management

EPM-BPC-NW-ADM-DIM Dimension Management

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

EPM-BPC-NW-ADM-SEC Security

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

EPM-BPC-NW-ADM-WS Work Status

Data ManagerTable 24Component String Area

EPM-BPC-NW-DM Data Manager

EPM-BPC-NW-DM-PAC Package Management

EPM-BPC-NW-DM-RUN Package Execution

EPM-BPC-NW-DM-SCH Schedule

InstallationTable 25Component String Area

EPM-BPC-NW-INS Installation

EPM-BPC-NW-INS-NW ABAP Installation

Web ClientTable 26Component String Area

EPM-BPC-NW-WEB Web Client

EPM-BPC-NW-WEB-CNT Documents View

EPM-BPC-NW-WEB-REP Web Reports

EPM-BPC-NW-WEB-STA Getting Started

SAP Business Planning and Consolidation 10.1Support Desk Management



www.sap.com

SAP Business Planning and Consolidation 10.1Table of Contents1 Getting Started2 Important SAP Notes3 Monitoring of Planning and Consolidation3.1 Setting up a Minimal-Access User to Configure SMD3.2 Enabling the Auto-Alert Mechanism in CCMS3.3 Availability Monitoring3.4 Component-Specific Monitoring3.5 Detailed Monitoring and Tools for Problem and Performance Analysis3.5.1 Displaying Statistics of Backend Performance3.5.2 Trace and Log Files3.5.2.1 Logging of Exceptions in the SLG1 System3.5.2.2 Trace File for Debugging Logic3.5.2.3 Data Manager Log Files3.5.2.4 Trace and Log Files for Context & Insights

3.5.3 Workload Monitors3.5.4 Data Growth and Archiving Monitors

3.6 Setting Up SAP Solution Manager as a Central Monitoring System

4 Management of Planning and Consolidation4.1 Starting and Stopping4.2 Backup Best Practices4.3 Best Practices for Performance Management4.3.1 Processing Tiers4.3.2 Cube Fact Tables4.3.3 Cube Optimization4.3.4 Cube Modification4.3.5 Writeback Parameters4.3.6 SQE Parameters4.3.7 Management of Data Volume

4.4 Set Up of BPF E-mail Notifications4.5 Administration Tools4.5.1 Logs4.5.2 Load Balancing4.5.3 User Management

4.6 Backup and Restore4.7 Scheduled Periodic Tasks for Event & Notification

5 Software Change Management5.1 Transport Management5.1.1 Transport Objects5.1.2 Transport Configuration5.1.3 Transport Execution5.1.3.1 Transporting Environments5.1.3.2 Deleting Objects by Transport

5.1.4 Transport Log Files5.1.5 Transport Maintenance5.1.6 Deployment Scenarios

5.2 Development Requests and Development Release Management5.3 UJA_DATA_CHECKER5.4 UJA_REFRESH_DIM_CACHE

6 Troubleshooting6.1 Troubleshooting in Business Planning and Consolidation6.2 Analyzing Problems Using Solution Manager Diagnostics6.3 Installing Appsight Black Box Service6.4 Generating and Analyzing Trace Files Using E2E Trace6.5 Logging and Tracing Configuration6.5.1 Logging and Tracing Parameters6.5.2 Client Configuration

6.6 Troubleshooting Transport6.7 Component-Level Logs6.8 Troubleshooting for Event & Notification

7 Support Desk Management7.1 Remote Support Setup7.2 Problem Message Handover

Copyright and Trademarks