Operation Guide SAP BusinessObjects Spend Performance Management 3.

0 Operation Guide
Target Audience Technical Consultants System Administrators Solution Consultants Business Process Owner Support Specialist

PUBLIC Document version: 1.00 2011-05-31

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 2011 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. 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.

2/54

PUBLIC

2011-05-31

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 expressly prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or altered in any way.

2011-05-31

PUBLIC

3/54

Typographic Conventions

Example
<Example>

Description

Example Example Example

Example

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. 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 Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. Cross-references to other documentation or published works 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 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

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

4/54

PUBLIC

2011-05-31

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/ instguidesssa. The following table provides an overview of the most important document changes:
Version Date Description

1.00

2011-05-31

Initial version of document

2011-05-31

PUBLIC

5/54

Table of Contents

Chapter 1 1.1 1.2 Chapter 2 2.1 2.2 Chapter 3 3.1 3.1.1 3.1.2 3.2 3.2.1 3.2.2 3.2.3 3.2.4 Chapter 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Global Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Monitoring of the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alert Monitoring with CCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCMS Monitoring Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component-Specific Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed Monitoring and Tools for Problem and Performance Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workload Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Growth and Data Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . Management of the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Launching the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 13 14 14 17 17 20 20 21 23 23 24 24 25 25 25 26 26

6/54

PUBLIC

2011-05-31

Chapter 5 5.1 5.2 5.3 Chapter 6 6.1 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6 6.2.7 6.2.8 6.2.9 6.2.10 Chapter 7 7.1 7.2 Chapter A A.1 A.2 Chapter B B.1

Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transport and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Development Requests and Development Release Management . . . . . . . . . . . Support Packages and Patch Implementation . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problem Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BI Data Service Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimension Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Warehouse (BW) Data Not Reflected in Reports . . . . . . . . . . . . . . . . SAP Web Dispatcher Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Management Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Setup and Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP NetWeaver Business Warehouse Data Processing . . . . . . . . . . . . . . . . . . .

27 27 27 27 29 29 29 29 32 33 34 35 35 36 37 39 41

Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Related Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

2011-05-31

PUBLIC

7/54

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

1 1.1

Getting Started Global Definitions

1 Getting Started

CAUTION

This guide does not replace the daily operations handbook that we recommend customers create for their specific production operations. Designing, implementing, and running your SAP applications 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 your SAP applications 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 need other guides such as the Master Guide, Technical Infrastructure Guide, and SAP Library.

1.1 Global Definitions

SAP Application:

A SAP application is an SAP software solution that serves a specific business area like ERP, CRM, PLM, SRM, SCM.
Business Scenario:

From a microeconomic perspective, a business scenario is a cycle, which consists of several different interconnected logical processes in time. Typically, a business scenario includes several company departments and involves with other business partners. From a technical point of view, a business scenario needs at least one SAP application (SAP ERP, SAP SCM, or others) for each cycle and possibly other third-party systems. A business scenario is a unit, which can be implemented separately and reflects the customers prospective course of business.
Component:

A component is the smallest individual unit considered within the Solution Development Lifecycle; components are separately produced, delivered, installed and maintained.

2011-05-31

PUBLIC

9/54

1 1.2

Getting Started Important SAP Notes

1.2 Important SAP Notes

CAUTION

Check regularly for updates available for the Application Operations Guide.
Important SAP Notes SAP Note Number Title Comment

1563216

Spend Performance Management 3.0: Release Information Note

This Release Information Note (RIN) contains information and references to SAP Notes in the context of the installation and configuration of SAP BusinessObjects Spend Performance Management 3.0.

10/54

PUBLIC

2011-05-31

2 2.1

Technical System Landscape Software Components

2 Technical System Landscape

2.1 Software Components

For information about the system architecture and required software components, see the Master Guide on SAP Service Marketplace at http://service.sap.com/instguidesssa.

2.2 Related Documentation

For more information about the technical system landscape, see the following table:
Topic Guide/Tool Quick Link on SAP Service Marketplace
http://service.sap.com/instguidesssa

Application-specific areas such as Data Management and End User Reporting Technology Components such as SAP Web Application Server Sizing Technical Configuration Scalability High Availability Security Security

Master Guide

Master Guide Quick Sizer Tool Master Guide Master Guide Master Guide Security Map Application Security Guide

http://service.sap.com/sizing

http://service.sap.com/instguides http://service.sap.com/instguidesssa http://service.sap.com/instguides http://service.sap.com/instguidesssa http://service.sap.com/security http://service.sap.com/instguidesssa

2011-05-31

PUBLIC

11/54

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

3 3.1

Monitoring of the Application Alert Monitoring with CCMS

3 Monitoring of the Application

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

Since the application is powered by SAP NetWeaver 7.02 and higher, we recommend that you set up the monitoring infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplace at http://service.sap.com/instguides. This contains all the information relevant to monitor the SAP NetWeaver components used in the application. Proficient knowledge of system monitoring and basic knowledge of SAP NetWeaver is required to compose user-defined monitors. For more information about monitoring in the CCMS, see SAP Help Portal at http://help.sap.com SAP NetWeaver . For performance metrics monitoring, see Wily Introscope installation guide on SAP Service Marketplace at http://service.sap.com/instguides Installation & Upgrade Guides SAP Components SAP Solution Manager Release 7.0 . You can find the most up-to-date version of the installation guide there. See also the following SAP Note:
SAP Note Number Title Comment

797147

Wily Introscope Installation for SAP Customers

Installation and configuration details

3.1 Alert Monitoring with CCMS

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

617547

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

2011-05-31

PUBLIC

13/54

3 3.1

Monitoring of the Application Alert Monitoring with CCMS

3.1.1 CCMS Monitoring Installation and Setup

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

617547

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

3.1.2 Component-Specific Monitoring

You can monitor CCMS Monitors as follows.
Procedure

1. Go to transaction RZ20. 2. Select CCMS Monitor. 3. Run Status/Error Messages. 4. Choose Display Details in the toolbar. The table below shows the CCMS Monitors applicable for the application:
Component CCMS Monitor

CCMS Monitor Sets SAP CCMS Technical Expert Monitors GRMG BI Data Service component (POASBCSelfmonitoring Scenario Executed Successfully BUINW 300) CCMS Monitor Sets SAP CCMS Technical Expert Monitors GRMG The Printing Services component Selfmonitoring Scenario Executed Successfully (POASBC-BUIPRS 100) CCMS Monitor Sets SAP CCMS Monitor Templates Communications Events and Notification which is part of SAPconnect Shared Business component (POASBC 100_702 or POASBC 100_730) CCMS Monitor Sets SAP BI Monitor BI Monitor Analytics SPM 3.0 (ANAXSA Version: 300_702 or 300_730) CCMS Monitor Sets SAP BI Monitor BI Monitor Analytics OPM Foundation (OPMFND Version: 300_702 or 300_730) CCMS Monitor Sets SAP CCMS Monitor Templates Database Database Monitoring A connection RDBMS with the system where the application is installed and being used can be monitored using database monitor within CCMS. CCMS Monitor Sets SAP CCMS Monitor Templates Operating Operating Monitoring Operating system monitoring capabilities System within CCMS administration workplace are used to analyze CPU, memory, paging, disks, file system, and their corresponding health statuses.

14/54

PUBLIC

2011-05-31

3 3.1

Monitoring of the Application Alert Monitoring with CCMS CCMS Monitor

Component

CCMS Monitor Sets Dialog Overview Overview Using dialog monitoring in RZ20, the response time for dialog, network time, and number of currently logged-in users can be observed.

SAP CCMS Monitor Templates

Dialog

GMRG Monitoring for BI Data Service Component To monitor components centrally, you must use a central monitoring system (CCMS). The BI Data Service component can be monitored using the SAP CCMS Generic Request and Message Generator (GRMG) tool. It performs a connection check to the BW back-end system and retrieves metadata of a data source. To configure the GRMG scenario, perform the following steps: 1. Create a file called grmg-customizing.xml with the following content:
SYNTAX <?xml version=1.0 encoding=UTF-8?> <customizing> <control> <grmgruns>X</ grmgruns> <runlog/> <errlog/> </control> <scenarios> <scenario> <scenname>BUI_BI</scenname> <scenversion>003</scenversion> <sceninst>100</ sceninst> <scentype>URL</scentype> <scenstarturl>http://%host%:%port%/sap/ sbc/bidata/info/grmg?j_user=%user%&j_password=%password%&login_submit=true</ scenstarturl> <scenstartmod>Unknown</scenstartmod> <scentexts> <scentext> <scenlangu>EN</scenlangu> <scendesc>GRMG: BUI BI Data Services</scendesc> </ scentext> </scentexts> <components> <component> <compname>METADATA</compname> <compversion>003</compversion> <comptype>Unknown</comptype> <comptexts> <comptext> <complangu>EN</complangu> <compdesc>BI Data Services Metadata Resources Component</compdesc> </comptext> </comptexts> <properties> <property> <propname>NAMESPACE</propname> <propvalue>%namespace%</propvalue> </property> <property> <propname>DATA_SOURCE</propname> <propvalue>% data_source%</propvalue> </property> </properties> </component> </components> </scenario> </scenarios> </customizing>

You can also use the template file in the POASBCBUINW00_0.sca file. Unzip the file _POASBCBUINW00_0.sca DEPLOYARCHIVES poa~sbc~bui~server~adapter~nw~eap.sda sap.com~poa~sbc~bui~server~adapter~nw~bidata~nwbidata.ass.jar grmg-customizing.xml_ . Substitute values for %host%, %port%, %user%, %password%, %namespace%, and %data_source%. The grmg.customizing.xml file is also attached to the following SAP Note:
SAP Note Number Title Description

1591634

GRMG Monitoring for BI Data Service Component for SPM 3.0

To monitor components centrally using the GRMG tool

2. 3. 4.

Save your entries. Log on to the Central Monitoring System (CEN). Go to transaction grmg. To do that, in the execution text field in the upper left corner, enter / nRZ20 and press Enter.

2011-05-31

PUBLIC

15/54

3 3.1

Monitoring of the Application Alert Monitoring with CCMS

5. Choose Upload and select the relevant scenario. 6. Once the scenario is uploaded, to verify the content is correct, choose Edit/Delete. 7. Choose Start. GMRG Monitoring for Print Service Component The print service can be monitored using the CCMS GRMG (Generic Request and Message Generator) tool. It performs a connection check to the print service to check if the service is available. You specify the required configuration settings in a GRMG Customizing file. For more information about the monitoring, see the Operations area on SAP Service Marketplace at http://service.sap.com/instguides SAP NetWeaver <Release Version> Operations . To configure the GRMG scenario, execute the following steps: 1. Create a file called grmg-customizing.xml containing the XML below. The following values need to be set:
Value Description

%host% %port% %bui_user_name%

The IP address of the host where the NW Java server is running The port of the NW Java server This must be a username that exists on the NW Java server and that also has the BUI_USER role %bui_user_password% The password for the user
SYNTAX <customizing> <control> <grmgruns>X</grmgruns> <runlong/> <errorlog/> </ control> <scenarios> <scenario> <scenname>BUI_PS</scenname> <scenversion>001</scenversion> <sceninst>100<sceninst> <scentype>URL</ scentype> <scenstarturl> http://%host%:%port%/sap/poa/sbc/ps/CORE/grmg </ scenstarturl> <scenstartmod>Not Used</scenstartmod> <scentexts> <scentext> <scenlangu>E</scenlangu> <scendesc>GRMG: BUI Java Persistence Service</ scendesc> </scentext> </scentexts> <components> <component> <compname>GRMG_RT</compname> <compversion>001</compversion> <comptype>Not Used</comptype> <comptexts> <comptext> <complangu>E</complangu> <compdesc>Basic Authentication</compdesc> </comptext> </comptexts> <properties> <property> <proptype>No_Encrypt</proptype> <propname>LOGON_PASSWORD</propname> <propvalue>%bui_user_password%</ propvalue> </property> <property> <proptype>No_Encrypt</proptype> <propname>LOGON_USER</propname> <propvalue>%bui_user_name%</propname> </ property> <property> <proptype>No_Encrypt</proptype> <propname>USE_BASIC_AUTHENTICATION</propname> <propvalue>X</propvalue> </ property> </properties> </component> <component> <compname>PARAM</compname> <compversion>001</compversion> <comptype>Not Used</comptype> <comptexts> <comptext> <complangu>E</complangu> <compdesc>Parameter</compdesc> </ comptext> </comptexts> <properties> <property> <proptype>No_Encrypt</ proptype> <propname>PARAM</propname> <propvalue>PARAM</propvalue> </ property> </properties> </component> </components> </scenario> <scenario> <scenname>BUI_PRS</scenname> <scenversion>001</scenversion> <sceninst>100</ sceninst> <scentype>URL</scentype> <scenstarturl> http://%host%:%port%/sap/ poa/sbc/prs/print/grmg </scenstarturl> <scenstartmod>Not Used</scenstartmod> <scentexts> <scentext> <scenlangu>E</scenlangu> <scendesc>GRMG: BUI Java

16/54

PUBLIC

2011-05-31

3 3.2

Monitoring of the Application Detailed Monitoring and Tools for Problem and Performance Analysis Print Service</scendesc> </scentext> </scentexts> <components> <component> <compname>GRMG_RT</compname> <compversion>001</compversion> <comptype>Not Used</comptype> <comptexts> <comptext> <complangu>E</complangu> <compdesc>Basic Authentication</compdesc> </comptext> </comptexts> <properties> <property> <proptype>No_Encrypt</proptype> <propname>LOGON_PASSWORD</propname> <propvalue>%bui_user_name%</propvalue> </ property> <property> <proptype>No_Encrypt</proptype> <propname>LOGON_USER</ propname> <propvalue>%bui_user_name%</propvalue> </property> <property> <proptype>No_Encrypt</proptype> <propname>USE_BASIC_AUTHENTICATION</ propname> <propvalue>X</propvalue> </property> </properties> </component> <component> <compname>PARAM</compname> <compversion>001</compversion> <comptype>Not Used</comptype> <comptexts> <comptext> <complangu>E</complangu> <compdesc>Parameter</compdesc> </comptext> </comptexts> </properties> <property> <proptype>No_Encrypt</proptype> <propname>PARAM</propname> <propvalue>PARAM</propvalue> </property> </properties> </component> <components> </scenarios> </customizing>

2. 3. 4. 5. 6. 7.

Save your entries. Log on to the Central Monitoring System (CEN). Call up transaction GRMG. To do that, in the execution text field in the upper left corner, enter / nRZ20 and press Enter. Choose Upload and select the relevant scenario. Once the scenario is uploaded, choose Edit/Delete to verify that the content is correct. Choose Start.

3.2 Detailed Monitoring and Tools for Problem and Performance Analysis 3.2.1 Trace and Log Files
Trace files and log files are essential for analyzing problems. The table below shows important Log and Trace files for the application:
Component Content File Path

BI Data Service Printing Services Shared Business Analytics SPM 3.0 Analytics OPM

Runtime exceptions with running reports and value help Runtime exception with the printing service Runtime exceptions with Events and Notifications, Printing and Persistence -

defaultTrace.trc

\usr\sap\<instance_DI> \J*\j2ee\cluster\server?\log \usr\sap\<instance_DI> \J*\j2ee\cluster\server?\log Transaction SLG1; Object: /POA/* Transaction SLG1; Object: RSXSA Transaction SLG1; Object: RSXSA

defaultTrace.trc -

2011-05-31

PUBLIC

17/54

3 3.2

Monitoring of the Application Detailed Monitoring and Tools for Problem and Performance Analysis Content File Path

Component

Foundation 3.0 User Interface

Log messages pertaining to workflow (alerts, fatals, errors, status updates.) Messages are also shown in the common message region in the top-right corner of the container. Traces are enabled through log message APIs Generic System Trace Analysis System Trace RFC, HTTP, DB Analysis Generic SQL Performance Trace and SQL Analysis RFC, HTTP, DB Performance Trace Analysis Procedure

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

Transaction ST01

Transaction ST05

Configuring NetWeaver Java logs for the application: You can change the log severity using the NetWeaver log configuration. 1. Go to http://<host>:<port>/nwa Troubleshooting Logs and Traces Log Configuration . 2. Set Show to Tracing Locations. Set Location to com.sap.poa.sbc.bui.bi for BI Data Service Component. Set Location to com.sap.xapps.opm.bi for OPM Shared component. Set Location to com.sap.poa.sbc.bui.printing for Print Service Component. The logs are generated in the NetWeaver defaultTrace.trc file. For Logging Categories, all application logs are logged to /Applications/BUI. Flex Client Platform (FCP) Server-Side Log Messages The application log messages can be viewed on an ABAP server using transaction /POA/SFCPAPPLOG. All the generated logs have an expiry time set and need to be deleted explicitly using transaction SLG2. 1. Connect to the ABAP system and execute transaction /POA/SFCPAPPLOG. 2. Provide the following filters: Object: /POA/SFCP (Display Only) Subobject: FCPAPPLOG (Display Only) Optional: External ID: Category of the log message, as seen in the application log console Mandatory: Time (From/To): The required interval as seen in application log console

18/54

PUBLIC

2011-05-31

3 3.2

Monitoring of the Application Detailed Monitoring and Tools for Problem and Performance Analysis

Optional: User: User of the session Set the default values for the remaining filters as follows: Transaction Code: * Program: * Log Class: All logs Log Creation: Any Log Source and Formatting: Format Completely from Database The exported log messages are grouped based on Category/External ID and displayed. 3. For more information, select extended text under Details column. Log severity seen on the ABAP server is the same as in the application, except for 'SUCCESS' and 'FATAL' ('SUCCESS' is mapped to 'INFO', 'FATAL' is mapped to 'TERMINATION'). Problem class is 'Very Important' for 'FATAL', 'Important' for 'ERROR', and 'Medium' for other severities. Flex Client Platform (FCP) Server-Side Trace Messages The application trace messages can be viewed on an ABAP Server using transaction /POA/ SFCPAPPTRACE. All the trace messages generated have an expiry time set and need to be deleted explicitly using transaction SLG2. 1. Connect to the ABAP system, execute transaction /POA/SFCPAPPTRACE. 2. Provide the following filters: Object: /POA/SFCP (Display Only) Subobject: FCPAPPTRACE (Display Only) Optional: External ID: Category of the trace message, as seen in application log console Mandatory: Time (From/To): Required interval as seen in application log console Optional: User: User of the session Set the default values for the remaining filters as follows: Transaction Code: * Program: * Log Class: All logs Log Creation: Any Log Source and Formatting: Format Completely from Database The exported trace messages are grouped based on Category/External ID and displayed. 3. For more information, select extended text under Details column. Trace severity seen on the ABAP server is the same as in the application, except for 'SUCCESS' and 'FATAL' ('SUCCESS' is mapped to 'INFO','FATAL' is mapped to 'TERMINATION'). Problem class is 'Very Important' for 'FATAL', 'Important' for 'ERROR', and 'Medium' for other severities. Deleting Logs and Traces

2011-05-31

PUBLIC

19/54

3 3.2

Monitoring of the Application Detailed Monitoring and Tools for Problem and Performance Analysis

All application logs and traces are generated with an expiry date and Deletion before expiry attribute set to true. Hence all the logs and traces can be deleted before their expiry date. The expiry date for logs and traces is calculated based on the log-expiry-duration parameter on the server. This parameter can be configured using transaction /POA/SFCPCONFIG and specifies the number of days for which logs can reside on the server. Default value is 7. Obsolete logs and traces can be deleted as follows: 1. Connect to the ABAP system; execute transaction SLG2. 2. Provide the filters as follows: Expiry date: and logs which can be deleted before the expiry date Object: /POA/SFCP Subobject: FCPAPPLOG to FCPAPPTRACE Options: Delete immediately COMMIT Counter: 100 3. Choose Execute. Logs can also be deleted in the background using report SBAL_DELETE. For more information, see the following SAP Note:
SAP Note Number Title Comment

195157

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

3.2.2 Workload Monitors

A default workload collector as part of CCMS monitoring and workload monitor through transaction ST03N can be used to observe the workload records at application server level.
Component Monitor Detailed Description Prerequisites

Workload Monitor Transaction ST03N

Detailed analysis of workload of application servers

3.2.3 Interface Monitors

Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.
Interface
http://<host>:<port>/sap/opm/bidata/info

Detailed Description

Technology Used

http://<host>:<port>/sap/opm/bidata/ <namespace>/dataSources/<data source name>/metadata

This REST interface returns the version HTTP number of the NetWeaver BI Data Service. This REST interface returns the cube HTTP metadata for the specified data source name.

20/54

PUBLIC

2011-05-31

3 3.2

Monitoring of the Application Detailed Monitoring and Tools for Problem and Performance Analysis

3.2.4 Data Growth and Data Archiving Monitors

Component Monitor Detailed Description Prerequisites

DB tables

ST05

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

Some of the intensive database tables that can be viewed during critical long-running operations: /POA/D_XML_VALS Resource Value (XML) for persistence service /POA/D_TRN_PAYL Resource Value texts for persistence service

2011-05-31

PUBLIC

21/54

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

4 4.1

Management of the Application Launching the Application

4 Management of the Application

SAP provides you with an infrastructure to help your technical support consultants and system administrators effectively manage all SAP components and complete all tasks related to technical administration and operation. For more information about the underlying technology, see the Technical Operations Manual in the SAP Library under SAP NetWeaver.

4.1 Launching the Application

Procedure
NOTE

For SAP BusinessObjects Spend Performance Management, replace <app spm. 1. 2. How do I launch the application?
http://<host>:<port>/sap/fcprt?app-config=<app config name>

config name> with

How do I launch the application in debug mode?

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

3.

Debug binaries are loaded so that it is possible to debug issues. How do I enable debug mode in the application?
NOTE

Debug, support, and trace modes are intended for use by support personnel. To enable debug mode, the FCP server parameter pp-enable-debugging=true must be set and the URL query parameter debug=true must be used when launching the application. For example:http://<host>:<port>/sap/fcprt?app-config=<app config name>&debug=true 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. In this mode, you can check the details of the loaded configuration, such as plug-ins, their version, and their load status.

4.

2011-05-31

PUBLIC

23/54

4 4.2

Management of the Application Starting and Stopping

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

mode=true

config name>&support-

5.

How do I enable the startup trace in the application? As a prerequisite, enable the tracing on the client. When launching the application, use the URL query parameter show-trace=startup. During the loading of the client, you see a dialog with the trace information collected during startup. In this mode, the log and trace information are available, along with the UI menu. For example: http://<host>:<port>/sap/fcprt?app-config=<app config name>&showtrace=startup

4.2 Starting and Stopping

Software Component Start and Stop Sequences and Tools Sequence Tool Detailed Description

BI Data Service -

NetWeaver Administrator Example: STARTSAP STARTSAP (UNIX) SAP Management Console NetWeaver Administrator

Go to http://<host>:<port>/nwa Operations Applications . Search for application

poa~sbc~bui~server~adapter~nw~eap

Start & Stop

Java

Software Component:
POASBC

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

Printing Service -

Go to http://<host>:<port>/nwa Operations Applications . Search for application

poa~sbc~bui~server~adapter~nw~eap

Start & Stop

Java

NOTE

If you are using SAP BusinessObjects Spend Performance Management, the URL for the BI Data Service is xapps~analytics~opm~eap.

4.3 Software Configuration

This chapter explains which components or scenarios used by this application are configurable and which tools are available for adjusting.
Component Configuration Tool(s) Detailed Description

BI Data Service

System Landscape Configuration

BW Connection

24/54

PUBLIC

2011-05-31

4 4.4

Management of the Application Application Copy Configuration Tool(s) Detailed Description

Component

BI Data Service Printing Service Event and Notification

Destination Service Configuration Persistence Service; Event and Notification Service Configuration of RFC Connections Configure the Print Service Proxy Transaction SM59 Schedule (Transaction SCOT) and Set up e-mail jobs monitor (SM37) jobs

4.4 Application Copy

You cannot make a client copy, because the spend performance management application is clientindependent.

4.5 Periodic Tasks

The ABAP program SSA_HELPER_PROGRAM can be scheduled with the CACHE_CLEANUP option to clean up spend performance management applications report cache periodically. The frequency of this should approximately match the frequency of data loading. When loading data through the data management for the application, the cache is automatically invalidated, but this cleanup process is still required to reduce the database table size. The ABAP program OPM_DM_MONITOR can be optionally scheduled. It scans for new files in the import directory and notifies the system owner if new files are dropped here. We recommend not to schedule this report unless the functionality is required. This is useful if the user dropping the files in the import directory is not the same user who performs the data loading. It is not useful if the same user performs both tasks, if loading is scheduled, or if DataSources are used instead of flat files.

4.6 Load Balancing

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

2011-05-31

PUBLIC

25/54

4 4.7

Management of the Application User Management

4.7 User Management

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

4.8 High Availability

The main framework of the application is based in SAP NetWeaver. If the POASBC software component becomes unavailable, all related business scenarios stop working. Unavailability of POASBC does not break any other software components or application functions.
Detailed Component Description
POASBC

HA Setup Description

POA Shared Business Components 1.0

For more information about high availability and switchover, see the Technical Operations Manual on SAP Help Portal at http://help.sap.com SAP NetWeaver .

If ANAXSA becomes unavailable, all related business scenarios stop working. Unavailability of OPMFND would affect the Data Management scenario functionality.
Detailed Component Description
OPMFND

HA Setup Description

ANAXSA

Analytics OPM Foundation Analytics SPM 3.0

For more information about high availability and switchover, see the Technical Operations Manual on SAP Help Portal at http://help.sap.com SAP NetWeaver . For more information about high availability and switchover, see the Technical Operations Manual on SAP Help Portal at http://help.sap.com SAP NetWeaver .

26/54

PUBLIC

2011-05-31

5 5.1

Software Change Management Transport and Change Management

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 and Change Management

SAP NetWeaver includes the Change and Transport System (CTS), which is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your system landscape. For more information, see the SAP NetWeaver Technical Operations Manual on SAP Help Portal at http://help.sap.com SAP NetWeaver .

5.2 Development Requests and Development Release Management

The transport workflow provides a framework for transporting enhancements or new developments of existing business functions in a system landscape. It is an efficient method of transporting a selected number of requests into a group of transport targets, and uses clearly defined approval steps to ensure the quality of your target systems. For more information, see the Technical Operations Manual on SAP Help Portal at http:// help.sap.com SAP NetWeaver .

5.3 Support Packages and Patch Implementation

The POASBC
100_730 component is supported by the SAP Note Assistant.

2011-05-31

PUBLIC

27/54

5 5.3

Software Change Management Support Packages and Patch Implementation

The POASBC 100_702 component is supported by the SAP Note Assistant. The OPMFND 300_730 component is supported by the SAP Note Assistant. The OPMFND 300_702 component is supported by the SAP Note Assistant. The ANAXSA 300_730 component is supported by the SAP Note Assistant. The ANAXSA 300_702 component is supported by the SAP Note Assistant.

28/54

PUBLIC

2011-05-31

6 6.1

Troubleshooting Important SAP Notes

6 Troubleshooting

This section provides a central starting point for problem solving in the area of data management for system administrators or technical consultants supporting the setup, implementation or maintenance of the spend performance management application.

6.1 Important SAP Notes

Make sure that you have the latest version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes.
CAUTION

Check regularly for updates to the following SAP Notes before setting up a system for the application and using the data management. It is mandatory to apply BI_CONT 7.03 SP12 before using the application.
Important SAP Notes SAP Note Number Title Comment

1104911

xSA: Data Management This SAP Note contains corrections about problems that corrections for BI_CONT SP8 can occur in monitoring, message processing, and in the process control in data management.

6.2 Problem Analysis 6.2.1 General Problems

Procedure

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

For SAP BusinessObjects Spend Performance Management, replace <app spm.

config name> with

2011-05-31

PUBLIC

29/54

6 6.2

Troubleshooting Problem Analysis

1.

2.

3.

How do I see status of the various plug-ins and the reasons why some plug-ins are not loaded? As a prerequisite, enable the support mode. After launching the application in support mode, right-click the application and select Support Info. In the Loaded Plug-ins tab of the Support Information dialog, you can see information about the loaded plug-ins, the state of the plug-ins and the error information for plug-ins that could not be loaded. How do I see the version information of the plug-ins? As a prerequisite, enable the support mode. After launching the application in support mode, right-click the application and select Support Info. In the Loaded Plug-ins tab of the Support Information dialog, you can see information about the version and the build number of the plug-in. 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. After deploying artifacts, you can view the FCP registry table contents in the form of logical transport objects as part of the transport request in the ABAP system. To change the configuration, you need to execute the following transaction /O/POA/ SFCPCONFIG. Change the values in the Configuration Value column and choose Enter. You can check whether the values have changed by looking into the database table directly (/POA/CONFIG_INFO) Example URL:http://<host>:<port>/sap/fcprt?app-config=<app config name>&showtrace=true

Each log message can have a severity level, which can be chosen from the defined set of levels. The severity levels are ERROR, FATAL, INFO, SUCCESS, WARNING. The default severity level is INFO. At any point in time, the log targets have access to the 500 latest log messages. Logging is always enabled on the client (though you can technically set logging level to NONE, which would mean no statements are logged on the client, this is not recommended). The log console needs to be configured in the server (pp-enable-trace=true) for it to appear in the client. Both server and client parameters are required for log console to work. The log console is displayed by right-clicking in UI.

30/54

PUBLIC

2011-05-31

6 6.2

Troubleshooting Problem Analysis

To configure which levels of statements to be logged, set the FCP server parameter pp-logfilter 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-logfilter=ERROR|FATAL

4.

5.

How do I view the log console/How do I send the client logs to the server? As a prerequisite, enable the logging and tracing on the client. After launching the client, right-click and choose Show Message Log Console. The dialog box displays the logs and traces. The dialog also provides an option to transmit the client logs to the server and to turn off tracing on the client for the session duration. 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.

Error Message 1090

Action Script Error [RPC Fault faultString="Error #1090: XML parser failure: element is malformed If you receive the above error message, check whether the error occurs in data management functionality. If it does not, the error is not related to the data management proxy; the problem is in the configuration of other Web services. If the error does occur in data management, first perform the WSDL and Connection tests as described above and follow up any problems. If both tests are successful, check in the connected SAP NetWeaver Business Warehouse system whether dumps occurred in the ABAP coding using the ABAP dump analysis (transaction ST22).
Locks in the Back-End System

Unnecessary locks in the back end can also cause undesirable effects when the system attempting to allocate resources to execute a query. Make sure that no locks exist in the back-end system before loading using Display and Delete Locks (transaction SM12)
Check That All the Necessary Transports are Applied

Ensure that all transports, which are required in the back end, are available using the Transport Organizer (Extended) (transaction SE01).

2011-05-31

PUBLIC

31/54

6 6.2

Troubleshooting Problem Analysis

Check That All UOM and Currencies in the Data File are Configured

Ensure that all units of measure (UOM) and currencies that are available in the data file are configured in the BASIS using Units of Measure (transaction CUNI).
Date Formats

All dates in the data file should conform to the format selected, usually YYYYMMDD.
Concept for Restart and Recovery

In the case of a system or component (OPM Foundation UI 2.0) crash, the spend performance management application does not require any specific functionality to recover after the UI crash. No data loss occurs because there is no application-specific data for this UI component; the data for the reports comes from SAP NetWeaver Business Warehouse. If the application is restarted after an interface crash, no additional steps are required to achieve the same functionality. For example, if the UI crashes while the user is creating a report, the user just needs to restart the UI after the crash for re-synchronization to happen with the back-end server and report creation to resume successfully. Re-creating a report takes only a few steps, so the user can re-create the report without any significant impact on time. This also applies to the other application content, such as dashboards and briefing books.

6.2.2 BI Data Service Troubleshooting

In most cases, troubleshooting the BI Data Service requires tools such as HTTPWatch to see the communication between the browser client and the server.
Procedure

Unable to see the cube metadata (dimensions and measures): 1. 1. Check that the server is returning the cube metadata by using the following URL within a browser: http://<host>:<port>/sap/opm/bidata/dataSources/<data_source_name>/metadata 2. Check the client is making the above REST call using HTTPWatch when creating a new report. Check if there is an error in the response. 3. If there is an authentication error in the response, ensure SSO is configured properly or user mapping is configured for the logged-on user 4. Ensure the BW connection is configured properly. Formulas and/or navigation dimensions are not returned with the cube metadata:

32/54

PUBLIC

2011-05-31

6 6.2

Troubleshooting Problem Analysis

Check for any errors in the cube metadata response by using the following URL within a browser: http://<host>:<port>/sap/opm/bidata/dataSources/<data_source_name>/metadata 2. If there is an error related to the persistence service, ensure the persistence service destination is configured properly. Unable to run reports: Use HTTPWatch and look for the following REST call: http://<host>:<port>/sap/opm/bidata/dataSources/<data_source_name>/report Ensure the response does not have any errors. It could be a BW back-end error.

1.

6.2.3 Alerts
Procedure

The following is a list of checks that can be performed to ensure that alerts are configured properly. 1. If the application is set up to use SSO, it is mandatory to use the assertion type for SSO authentication for the alerts to work. The logon method needs to be set to SAPLOGONTICKET and the authentication type needs to be set to SAP Assertion Ticket when setting up the system landscape in the portal. Check that the BASIS settings have been made in the following locations: Trust Manager Certificate and Keys: Key Storage Authentication and Single Sign-On: Authentication System Configuration 2. Check if the following destinations are set up properly: 1. BUI_PERSISTENCE_<namespace> This HTTP destination is used to retrieve all alerts in the system associated with the application to execute them and generate update messages as required. This is also used by the BI Data Service for other operations. 1. <namespace>: Namespace of the application. 2. The URL has the following pattern: <protocol>://<server>:<port>/sap/poa/sbc/ps/ <namespace> 3. The logon data is set to a system user who has the required permissions to query the persistence service for the alerts of all users in the system. 2. BUI_EVT_AND_NOTI_<namespace> This HTTP destination is used by the application to publish messages to the inbox of the user using the event and notification service. 1. <namespace>: Namespace of the application.

2011-05-31

PUBLIC

33/54

6 6.2

Troubleshooting Problem Analysis

3. 4.

The URL has the following pattern: <protocol>://<server>:<port>/sap/poa/sbc/enrs The logon data is set to a system user who has the required authorizations to publish to the inbox of all users in the system. 1. <namespace>: Namespace of the application. 2. The URL has the following pattern: <protocol>://<server>:<port>/sap/fcprt?appconfig=<application config>. The URL is the URL of the UI. 3. There is no need to configure the logon data. 3. BUI_BASE_UI_URL_<namespace> This optional HTTP destination is used by the application to add deep linking to the alert that generated the message so the user can navigate to the alert creation screen from the message. If this is not configured, the message does not link to the alert, but the message is still published. When creating alerts in the UI, the alert is not executed unless it has been marked as Active, which is the default. When executing alerts, if there are no results returned it means that no notifications have been created.

2. 3.

6.2.4 Dimension Troubleshooting

Procedure

User-Defined Measures: If the user is unable to retrieve/create user-defined measures (User-Defined Formulas), the following is a list of checks that can be performed: 1. The HTTP Destination BUI_PERSISTENCE_<namespace> needs to be present with the following parameters: 1. <namespace> is the namespace of the application. For example, in the case of Spend Performance Management it is SPM. Note: The namespace is case sensitive 2. The URL must have the following pattern: <protocol>://<server>:<port>/sap/poa/sbc/
ps/<namespace>

Set the System ID, Client and Language appropriately. The Logon Data is set to use the Basic details (User ID and Password) and to use a system user who has the required permissions to query the persistence service for the User-Defined Measures in the system. 2. When pinging the destination, a HTTP response code of 404 is returned; this is acceptable. Anything else such as 401 or 403 suggests that the user is not authorized and hence the authorizations should be checked. The message is as follows: Received HTTP response 404. Navigation Dimensions: If the user is unable to retrieve/create the navigation dimensions the following is a list of checks that can be performed:

3. 4.

34/54

PUBLIC

2011-05-31

6 6.2

Troubleshooting Problem Analysis

1.

The HTTP Destination BUI_PERSISTENCE_<namespace> needs to be present with the following parameters: 1. <namespace> is the namespace of the application. For example, in the case of Spend Performance Management it is SPM. Note: The namespace is case sensitive. 2. The URL should have the following pattern: <protocol>://<server>:<port>/sap/poa/sbc/
ps/<namespace>

3. 4.

2.

Set the System ID, Client and Language appropriately. The Logon Data is set to use the Basic details (User ID and Password) and to use a system user who has the required permissions to query the persistence service for the Navigation Dimensions in the system. When pinging the destination, a HTTP response code of 404 is returned; this is acceptable. Anything else such as 401 or 403 suggests that the user is not authorized and hence the authorizations should be checked. The message is as follows: Received HTTP response 404.

6.2.5 Business Warehouse (BW) Data Not Reflected in Reports

Newly updated BW data is not reflected in executed reports. This is caused by old JCo connections to the BW system being reused by the NetWeaver Connection Pool. The new data is not shown if an old JCo connection is used to execute report. Connections time out and are closed by the Connection Pool if they are not reused within a specific time. If you do not want to wait for the connection to time out, try the following solutions: 1. Reduce the connection lifetime: Go to http://<host>:<port>/nwa Configuration Infrastructure Application Resources SAPFactory Connection Pooling . 2. When data is changed, remove all existing connections using transaction SM04 on the BW system.

6.2.6 SAP Web Dispatcher Troubleshooting

For information about troubleshooting the SAP Web Dispatcher, see the Administration of the SAP Web Dispatcher information on SAP Help Portal at http://help.sap.com SAP NetWeaver . For more information about troubleshooting, see the Problem Analysis Guide on SAP Help Portal at http://help.sap.com SAP NetWeaver .

2011-05-31

PUBLIC

35/54

6 6.2

Troubleshooting Problem Analysis

6.2.7 Data Management Problems

To analyze data management problems that can occur while using the application, it is very important that you determine at which stage of the data processing an error occurred.
Procedure

Uploading data to the SAP NetWeaver Business Warehouse system involves the following major steps: 1. Start the upload to the inbound data targets The data is checked and converted. Release of data to the reporting area. The process chain is started. 2. A process chain starts the data upload to the inbound layer (transactional data only) or to the data target (master data). 3. The data is uploaded to the reporting layer (transactional data only). You need to determine at which stage of the upload process the error occurred and follow the instructions: If the error occurred during the upload preparation (steps 1 and 2), see Variant A for possible reasons. If the error occurred during the data upload (steps 3 and 4), see Variant B for possible reasons. To determine at which stage the error occurred, proceed as follows: 1. Check if a batch job called BI_PROCESS_TRIGGER exists using Overview of job selection (transaction SM37).
NOTE

The existence of a batch job BI_PROCESS_TRIGGER indicates that the process has already reached the upload stage. 2. Determine if this batch job has started after the loading process from the upload wizard has started. If this is the case, follow the instructions for Variant B. Otherwise, follow the instructions for Variant A for further problem analysis. 3. Determine the relevant subcategory for the error and check the potential reasons listed for this type of problem. 4. Determine whether batch processes have been started and which type of processes they are using Overview of job selection (transaction SM37). Variant A: Data Upload not started No batch process started: Authorization Already Running Back End is Not Available Web Service is Inactive

36/54

PUBLIC

2011-05-31

6 6.2

Troubleshooting Problem Analysis

Error Message 1090 One batch process started but ended after 1 or 2 seconds (step 1): Inconsistencies in the process step metadata Checks detected inconsistencies in the files (SP2) Two batch processes started but both of them ended after 1 or 2 seconds (step 2): Server name Path for File Storage Process Chain is Inactive Data Files Second batch process ended with errors or dumps (step 2): Path for File Storage Authorization File Format Variant B: Data Upload started Upload stopped immediately and chain ended with errors (step 3): Inactive DataSource Inactive DTP No Routines in InfoPackage PSA table not in process variant Upload ran for some time and then stopped with errors (steps 3 or 4): Duplicated Records for Master Data Previous Request was Loaded with Status Red Process Chain is already running Invalid Characters / Wrong Delimiter / Wrong Decimal Separator

6.2.8 System Setup and Preparation

Server Name

In the global settings, you can define an application server to use for data extraction processes. This entry is required if you are working in a multi-application server environment and the servers are not mounted. In this case, you must enter the name of the server storing the flat files. Make sure that you spell the server name correctly, because the entry is case-sensitive. Use Application Server Overview (transaction SM51) to check whether the server name you entered and the one listed there are identical.

2011-05-31

PUBLIC

37/54

6 6.2

Troubleshooting Problem Analysis

Path for File Storage

The path for the stored flat files is not maintained correctly or does not exist. 1. Check in the global settings whether an entry for the path for import folders exists. The entry is case-sensitive. 2. Check in Display SAP Directories (transaction AL11) whether an entry for the file path exists. Make sure that the entered path appears as /usr/sap/Q75/SYS/global/xsa_import/. Remember to enter the forward slash (/) at the end of the path.
Back End is Not Available

The SAP NetWeaver Portal must be configured correctly to establish the connection to the SAP NetWeaver Business Warehouse back-end server. If you experience any connectivity problems, proceed as follows:
WSDL Test

In a Web browser, open the URL <protocol>://<webdispatcher host>:<webdispatcher port>sap/bw/ bct/xsa/opm_dm_wsdl If a valid WSDL is not displayed, review the section Configure Data Management Web Service in the Installation Guide. You should also refer to this section of the installation guide if other errors in the application indicate a problem with WSDL files, Web services or security errors. If the call to the Web Service above returns a server error, make sure that SSO is configured properly. In particular check the following profile parameters: login/accept_sso2_ticket should have the value 1and login/create_sso2_ticket should have the value 2.
Reverse Proxy Setup Problems

When you open the Data Management WSDL http://<webdispatcher server><webdispatcher port>/ sap/bw/bct/xsa/opm_dm_wsdl at the end of the file it should contain URLs pointing to the Web Dispatcher (not directly to the ABAP Web As). If the URLs are incorrect or are using the ABAP host/ port this indicates problems with the reverse proxy. Make sure you use fully qualified host names and verify all entries according to the Installation and Configuration Guide.
Connection Test

1. 2.

Execute the Web Application Server (Web AS) connection test for the system with the alias BUI_ANALYTICS_SPM. If the connection test fails, check the following: System properties for Web AS, such as host name (for example portal.sap.corp:50010) and protocol (for example HTTP) User Management (use saplogonticket)

38/54

PUBLIC

2011-05-31

6 6.2

Troubleshooting Problem Analysis

3.

Check whether the certificates for saplogonticket are configured correctly. You can use Maintain Profile Parameters (transaction RZ10) to find the correct URL and port number of the Web AS to be used for HTTP or HTTPS configuration. If the connection test is successful, check the following: The correct alias BUI_ANALYTICS_SPM is assigned to the system. The Web services are active and running in the ABAP system, and the user has permission to view and execute WSDL files.

Authorizations

To perform data management actions, the user needs to have the authorization object S_RS_XA_DM (in addition to S_RS_XA) assigned. This authorization object is added to the roles SAP_XSA_DATA_MANAGER and SAP_SPM_ADMINISTRATOR. In addition, the user needs to have standard authorizations, for example, for executing Web services. Authorization settings for the Web service execution can appear as follows:
Authorization Object S_SERVICE Authorization Object S_DEVELOP OPM_DM_X_API* OBJTYPE : WEBI ACTVT : 03

6.2.9 Data Files

File Does Not Exist

If the file does not exist on the server, a problem occurs immediately after starting the loading process. Typically, the second loading step fails to execute. Check whether the file exists in the back end using Display SAP Directories (transaction AL11) to locate the directory and the file where the data files are uploaded.
File Format

The files are usually transferred to the application server via File Transfer Protocol (FTP). You must choose the correct transfer method in the FTP application. Use BIN instead of ASCII and ensure that the file is in UTF-8 or UTF-16 format. A reliable indicator that a file is in the correct format is whether you can view and open the file using Microsoft Excel and all the data appears correctly formatted in individual columns. Choosing the incorrect transfer method leads to a codepage problem later on during the data processing. If the extracted file is not available in UTF format and exists in any other format, you can use SAP Note 752859: sapiconv (a tool for converting the encoding of files).

2011-05-31

PUBLIC

39/54

6 6.2

Troubleshooting Problem Analysis

Escape Character

Support Package 0 and 1 do not support escape characters. If a file contains these characters, you need to delete than and convert the data in a different way. Problems caused by escape characters arise during data processing in the Persistent Staging Area (PSA) tables in SAP NetWeaver Business Warehouse. The most likely problem is that the fields no longer map to each other correctly. A flat file with escape characters can appear as in the following example: Column1;Column2;Column3; SCREW_1;Screws; Utilities and more;I034;83;
Invalid Characters

The SAP NetWeaver Business Warehouse data processing allows a certain set of characteristic values only. By default, the allowed characteristic values include numbers 0 to 9 and uppercase alpha values A to Z as well as the following: Exclamation mark (!) Double quote () Percent sign (%) Apostrophe () Asterisk (*) Plus sign (+) Minus sign (-) Period (.) Forward slash (/) Colon (:) Semi-colon (;) Less than sign (<) Equal sign (=) Greater than sign (>) Question mark (?) If other characteristic values such as the section symbol (), dollar sign ($), percent sign (%), number sign (#), vertical slash (|), or micro sign () are used, these must be known by the SAP NetWeaver Business Warehouse system. Check the Customizing for details and add the additional characteristic values if necessary.
Wrong Delimiter

The supported delimiters for flat files are as follows: Comma (,)

40/54

PUBLIC

2011-05-31

6 6.2

Troubleshooting Problem Analysis

Semi-colon (;) Colon (:) Period (.) If you choose an incorrect delimiter (for example, a semi-colon instead of a comma), this leads to errors in the upload wizard during data processing in SAP NetWeaver Business Warehouse. As a result, the field mapping no longer works and some fields may not be populated with data. To resolve the issue, choose the correct delimiter and restart the data upload.
Wrong Decimal Point Separator / Thousands Separator

If thousands separators or decimal point separators are used in the flat file make sure that the characters are used only for that purpose consistently throughout the file. If the separator characters differ from the values entered in the global settings, you can experience problems during data activation in the Inbound-DataStore object (DSO) because the value cannot be interpreted correctly.

6.2.10 SAP NetWeaver Business Warehouse Data Processing

Process Chain is Inactive

The status icon for step 2 turns red or retains the status Processing after you start the data upload if the process chain has not been activated. Use Process Chain Maintenance (transaction RSPC) to check whether the process chain for the selected upload is available and active. If the process chain is not available, install the content version of the chain by using BW Metadata Repository (transaction RSOR).
DataSource is Inactive

If the DataSource is not active, the process chain will start, but then end immediately with errors. Use BW Metadata Repository (transaction RSOR) to activate the DataSource.
Inactive DTP

If the Data Transfer Protocol (DTP) is inactive, check in the process chain log whether the DTP icon is red and whether the DTP has errors. Then activate it.
Routine in InfoPackage is Not Available

Due to technical problems in SAP NetWeaver Business Warehouse, the routines in InfoPackages could not be delivered. Therefore for SP0 and SP1 all routines need to be added to the InfoPackages manually. See SAP Note 1059881 for details. If the routines are not added to the InfoPackages, the status of the data upload turns red at step 2 of the data upload process. Messages in the process chain log inform you that it was not possible to access the file neither on the application server nor on the local client.

2011-05-31

PUBLIC

41/54

6 6.2

Troubleshooting Problem Analysis

Process Chain is Already Running

The same process chain cannot be started twice in parallel. If one chain is still running, you need to wait until it is finished and then try to restart the loading process. This also applies to the Release to Reporting stage. For the release steps you do not receive a message saying that the action cannot be performed twice in parallel (SP0 and SP1 only), but you have to wait until it is finished before restarting any action.
Previous Request Has Been Loaded with Status Red

If the Release to Reporting stage completes with status Failure, check the related data target such as the DataStore object (DSO), InfoObject, or InfoCube in the SAP NetWeaver Business Warehouse. If you were able to determine the cause of the error and the issue was solved, to adjust the data in SAP NetWeaver Business Warehouse, you may need to delete the request from the relevant InfoProviders.
Duplicated Records for Master Data

This error message can appear in the SAP NetWeaver Business Warehouse monitor logs, if you try to upload master data with the same key during the same upload process. Possible reasons for the error are as follows: You have deleted a previous request from the data target but not from the PSA. If the data is loaded a second time, the previous PSA request is uploaded as well and this leads to duplicated master data records within the same upload. The field mapping did not work correctly, so some of the key fields are not mapped to a column in the file. Due to the missing key field, records are not unique and are identified as duplicated records. The flat file contains duplicated records. There is no system maintained for the file parameters or no system column (XARSYSTEM) filled in the file. Try to find the cause of the problem, delete the erroneous request from the data target, and start the data upload once again. Delete the requests in the PSA before you do this.
Errors Caused by Obsolete BI Content Objects

The following error messages can be safely ignored during the BI Content installation for the application: Version D of transformation 09040767SFK4EDMRI3SCDEGQABWTQSL7 is inconsistent Target IOBJ 0XARLPROD is not allowed Object 0E2R8KR45M0H68POUF6JWA5J7TNA4DS9 (Transformation,TRFN) could not be collected for object DTP_0YY369GVTTFZ1E0UZXEXYF0CD (D

42/54

PUBLIC

2011-05-31

6 6.2

Troubleshooting Problem Analysis

Object '0E2R8KR45M0H68POUF6JWA5J7TNA4DS9' (TRFN) of type 'Transformation' is not available in version 'D' No rule exists Target RSDS 0XA_SA_TXT_GEN XSA_PCFILE is not allowed Error saving Transformation 09040767SFK4EDMRI3SCDEGQABWTQSL7 Transformation does not exist (see long text) Error saving Data Transfer Process DTP_0YY369GVTTFZ1E0UZXEXYF0CD Transformation does not exist (see long text) Error saving Data Transfer Process DTP_D3UZJDGL12BGHLDYLXR8MPW8T Version D of transformation 09040767SFK4EDMRI3SCDEGQABWTQSL7 is inconsistent

2011-05-31

PUBLIC

43/54

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

7 7.1

Support Desk Management Remote Support Setup

7 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support organization that seamlessly integrates your end users, internal support employees, partners, and SAP Active Global Support specialists with an efficient problem resolution procedure. For support desk management, you need the methodology, management procedures, and tools infrastructure to run your internal support organization efficiently.

7.1 Remote Support Setup

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

486688

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

For further assistance, see the following SAP Note:

SAP Note Title Comment

812386

RFC connection to the SAPNet R/3 front end

For more information, see the SAP Library on Help Portal at SAP NetWeaver SAP NetWeaver 7.0 including Enhancement Package 2 SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability General Administration Tasks Setting Up Service Connections for SAP Remote Support . For a read-only access to the application, see SAP Note 1593127. For more information about standard and application-specific authorization objects, see the Security Guide on SAP Service Marketplace at http://service.sap.com/securityguide.
More Information
http://service.sap.com/access-support

2011-05-31

PUBLIC

45/54

7 7.2

Support Desk Management Problem Message Handover

7.2 Problem Message Handover

For sending problem messages and tickets to SAP, use component EPM-SA and provide a detailed and reproducible problem description.

46/54

PUBLIC

2011-05-31

A A.1

Appendix Related Guides

A Appendix

A.1 Related Guides

For more information about installation and configuration, see the Master Guide.

A.2 Related Information

The following table contains links to information relating to the Solution Operation Guide:
Content Quick Link on SAP Service Marketplace
http://service.sap.com/instguidesssa http://service.sap.com/ibc http://service.sap.com/notes http://service.sap.com/platforms http://service.sap.com/securityguide http://service.sap.com/network http://service.sap.com/ti http://service.sap.com/solutionmanager

Master Guide, Installation Guide and Upgrade Guide Master Guide, Installation Guide and Upgrade Guide Related SAP Notes Released Platforms Network Security Network Security Technical Infrastructure SAP Solution Manager

2011-05-31

PUBLIC

47/54

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

B B.1

Reference The Main SAP Documentation Types

B Reference

B.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the various phases in the life cycle of SAP software.
Cross-Phase Documentation

SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many glossary entries in English and German. Target group: Relevant for all target groups Current version: On SAP Help Portal at http://help.sap.com Glossary In the SAP system in transaction STERM SAP Library is a collection of documentation for SAP software covering functions and processes. Target group: Consultants System administrators Project teams for implementations or upgrades Current version: On SAP Help Portal at http://help.sap.com (also available as documentation DVD) The security guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for SAP NetWeaver. This document contains general guidelines and suggestions. SAP applications have a security guide of their own. Target group: System administrators Technology consultants Solution consultants Current version: On SAP Service Marketplace at http://service.sap.com/securityguide

2011-05-31

PUBLIC

49/54

B B.1

Reference The Main SAP Documentation Types

Implementation

The master guide is the starting point for implementing an SAP solution. It lists the required installable units for each business or IT scenario. It provides scenario-specific descriptions of preparation, execution, and follow-up of an implementation. It also provides references to other documents, such as installation guides, the technical infrastructure guide and SAP Notes. Target group: Technology consultants Project teams for implementations Current version: On SAP Service Marketplace at http://service.sap.com/instguides The installation guide describes the technical implementation of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. Target group: Technology consultants Project teams for implementations Current version: On SAP Service Marketplace at http://service.sap.com/instguides Configuration Documentation in SAP Solution Manager SAP Solution Manager is a life-cycle platform. One of its main functions is the configuration of business scenarios, business processes, and implementable steps. It contains Customizing activities, transactions, and so on, as well as documentation. Target group: Technology consultants Solution consultants Project teams for implementations Current version: In SAP Solution Manager The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The Customizing activities and their documentation are structured from a functional perspective. (In order to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager, which refers to the relevant Customizing activities in the individual SAP systems, is used.) Target group: Solution consultants Project teams for implementations or upgrades

50/54

PUBLIC

2011-05-31

B B.1

Reference The Main SAP Documentation Types

Current version: In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation

The technical operations manual is the starting point for operating a system that runs on SAP NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers users to the tools and documentation that are needed to carry out various tasks, such as monitoring, backup/restore, master data maintenance, transports, and tests. Target group: System administrators Current version: On SAP Service Marketplace at http://service.sap.com/instguides The application operations guide is used for operating an SAP application once all tasks in the technical operations manual have been completed. It refers users to the tools and documentation that are needed to carry out the various operations-related tasks. Target group: System administrators Technology consultants Solution consultants Current version: On SAP Service Marketplace at http://service.sap.com/instguides
Upgrade

The upgrade master guide is the starting point for upgrading the business scenarios and processes of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes. Target group: Technology consultants Project teams for upgrades Current version: On SAP Service Marketplace at http://service.sap.com/instguides The upgrade guide describes the technical upgrade of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. Target group: Technology consultants

2011-05-31

PUBLIC

51/54

B B.1

Reference The Main SAP Documentation Types

Project teams for upgrades Current version: On SAP Service Marketplace at http://service.sap.com/instguides Release notes are documents that contain short descriptions of new features in a particular release or changes to existing features since the previous release. Release notes about ABAP developments are the technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide (IMG). Target group: Consultants Project teams for upgrades Current version: On SAP Service Marketplace at http://service.sap.com/releasenotes In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguidesssa

52/54

PUBLIC

2011-05-31

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