SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP...

128
PUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects Profitability and Cost Management Administrator's Guide

Transcript of SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP...

Page 1: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

PUBLIC

SAP BusinessObjects Profitability and Cost ManagementDocument Version: 10.0 – 2016-10-06

SAP BusinessObjects Profitability and Cost Management Administrator's Guide

Page 2: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Content

1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 Target Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41.2 Global Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 History of Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.4 SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Technical System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72.1 Component Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72.2 Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Monitoring of SAP BusinessObjects Profitability and Cost Management. . . . . . . . . . . . . . . . . . . . 83.1 Alert Monitoring with Model Builder Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.2 Detailed Monitoring and Tools for Problem and Performance Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . 8

Trace and Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Data Growth and Data Archiving Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Event Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 Management of SAP BusinessObjects Profitability and Cost Management. . . . . . . . . . . . . . . . . . 234.1 Starting and Stopping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Standard Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Non-Standard Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

4.2 Software Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Configuring Multiple System Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

4.3 Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Controlling Profitability and Cost Management Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Profitability and Cost Mangement System Information Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41SAP BusinessObjects Profitability and Cost Management Remote Configuration Tool. . . . . . . . . . . 53Registering SAP BusinessObjects Profitability and Cost Management with the SAP System Landscape Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Model Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4.4 Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Archive Procedures for Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79System Backup Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Web Client Data Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4.5 Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Scheduled Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Required Manual Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4.6 Load Balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

2 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Content

Page 3: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Load Balancing with Model Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854.7 User Management Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

User Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914.8 Language Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

To Create a Data Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95To Rename a Data Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95To Delete a Data Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.9 Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5 High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

6 Troubleshooting SAP BusinessObjects Profitability and Cost Management. . . . . . . . . . . . . . . . 1006.1 Using the System Information Tool for Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006.2 Error Codes and Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Common Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

6.3 ActiveX Control Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108The ActiveX Control Cannot Update to the Latest Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109After Installation, the Control Does Not Appear in the Downloaded Program Files Folder. . . . . . . . . 111Hidden Conflict Directories are Created. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Error Message: Download has failed (the connection was interrupted). Unknown Response: 0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Application Exception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Cleaning Out the Registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

6.4 SAP BusinessIntelligence Platform Integration Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126.5 Root Cause Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

End to End Trace Launcher and Client-Side Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Application Passports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115NCS Thresholds and Performance Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116AppSight Console Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

SAP BusinessObjects Profitability and Cost Management Administrator's GuideContent P U B L I C 3

Page 4: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

1 Getting Started

This guide provides a starting point for managing your SAP BusinessObjects Profitability and Cost Management 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 will sometimes also need other guides such as the SAP BusinessObjects Profitability and Cost Management Master Guide, and SAP BusinessObjects Profitability and Cost Management Installation Guide.

1.1 Target Groups

The information in this guide applies to the following types of users:

● Technical Consultants● System Administrators● Solution Consultants● Business Process Owners● Support Specialists

1.2 Global Definitions

● SAP Application - An SAP application is an SAP software solution that serves a specific business area.● 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 involvement 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 customer's 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.

1.3 History of Changes

This is version 1.2 of the document. The most recent version of the SAP BusinessObjects Profitability and Cost Management Administrator's Guide is always located on the SAP Service Marketplace at service.sap.com/instguides. The following table provides an overview of the most important changes in prior versions:

4 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Getting Started

Page 5: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

NoteAlways ensure that you use the most current version of the Administrator's Guide.

Version Date Important Changes

1.0 May-10-2011 First version of the SAP BusinessObjects Profitability and Cost Management Administrator's Guide for SAP BusinessObjects Profitability and Cost Management 10.0.

1.1 August-2011 As part of the updated Profitability and Cost Management version released in August 2011, the document contains the following amendments or additions: :

● The “Backup and Restore” section contains an additional reference to the SAP BusinessObjects Database Administrator's Guide for information about detailed backup and restore procedures.

● An additional list of error codes in the “Error Codes and Messages” section describes each error number and corresponding message that appears in the software.

● The “SAP BusinessObjects Profitability and Cost Management Remote Configuration Tool” topic contains additional information about settings that cannot be distributed to remote machines, and a distinction between using the tool to distribute client configuration settings rather than server configuration settings is made.

1.2 November-2013 As part of the release for Support Package 08, the following topics are updated with information on the new PCMExcelService:

● “Ancillary Services”● “Sevice Dependencies”

1.4 SAP Notes

The following SAP Notes can be referenced for additional information:

SAP BusinessObjects Profitability and Cost Management Administrator's GuideGetting Started P U B L I C 5

Page 6: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Description SAP Note

Wily Introscope Installation for SAP Customers SAP Note 797147

Introscope 7.2.3 Release Notes SAP Note 1237887

6 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Getting Started

Page 7: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

2 Technical System Landscape

The system infrastructure is comprised of system and software components that are required for the SAP BusinessObjects Profitability and Cost Management software to function successfully.

2.1 Component Matrix

Please refer to the following guides for a detailed software and system component matrix:

● SAP BusinessObjects Profitability and Cost Management Master Guide● SAP BusinessObjects Profitability and Cost Management Installation Guide

2.2 Related Documentation

The following table lists where you can find more information about the technical system landscape:

Topic Guide Location

“Software components in SAP BusinessObjects Profitability and Cost Management”

SAP BusinessObjects Profitability and Cost Management Master Guide

SAP Service Marketplace (service.sap.com)

“System component installation order” SAP BusinessObjects Profitability and Cost Management Installation Guide

SAP Service Marketplace (service.sap.com)

“Installation in a BusinessIntelligence platform environment”

SAP BusinessObjects Profitability and Cost Management Installation Guide

SAP Service Marketplace (service.sap.com)

“Installing and configuring SAP BusinessObjects Profitability and Cost Management”

SAP BusinessObjects Profitability and Cost Management Installation Guide

SAP Service Marketplace (service.sap.com)

Wily Introscope Installation and User Guides http://service.sap.com/diagnostics

SAP Solution Manager Diagnostics Agent 7.20

Setup Guide http://service.sap.com/diagnostics

Related Information

SAP Service Marketplace

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTechnical System Landscape P U B L I C 7

Page 8: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

3 Monitoring of SAP BusinessObjects Profitability and Cost Management

The types of monitoring that are available in the system are as follows:

● Model Builder alerts● Trace and log files● Data growth and data archiving monitors● Event logs

3.1 Alert Monitoring with Model Builder Alerts

Alert messages are provided in the Model Builder application, to supply information on the current state of the model and the user session. There are three different types of alert message:

Security AlertModel AlertLocal Alert

Security Alerts provide system wide user information such as failed login attempts, and can be seen by all users of the software.

Security Alerts and Model Alerts can be archived to a TXT file of your choice.

Further information on Model Builder alerts can be found in the SAP BusinessObjects Profitability and Cost Management Modeling User Guide.

3.2 Detailed Monitoring and Tools for Problem and Performance Analysis

3.2.1 Trace and Log Files

Trace and log files are essential for analyzing problems.

The location of the log files is specified in the Log Files Location screen during the configuration of SAP BusinessObjects Profitability and Cost Management. The default folder location is C:\PCMTemp\Logs.

8 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Monitoring of SAP BusinessObjects Profitability and Cost Management

Page 9: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Table 1: Log files

Component Content File Path

Web These logs contain a list of transactions with the following details:

● Date● Time● Session ID (if applicable)● Thread ID● I, E or D as appropriate (where I = Information, E =

Error, D = Debug)● Message (may include the transaction time)

They are useful for investigating problems with web server performance. They need to be managed so that the directory contains the most recent logs, because the latest log is the one of interest.

PCMIISPlugin.dll-YYYYMMDD.log

C:\PCMTemp\Logs

Configure For each application, there is a single file to which errors are appended whenever they occur in that application. The files contain details of the error message, a call stack for debugging code, and some information about the ma­chine that produced the error. The files should be man­aged so that they do not become too large. It is recom­mended that the files are archived on a regular basis (a monthly interval would be sufficient), however because they are only text files they should not present any prob­lems if left to grow for an extended period of time.

PCMConfigErrors.log

C:\PCMTemp\Logs

Model Builder PCMError.log

Report Manager

RSEditErrors.log

Work Manager Client

WMErrors.log

Work Manager Server

An error message is generated in the extremely rare sit­uation of a serious engine error. A single file is generated for an individual error.

WM Service log n (where n = file number 1-999)

C:\PCMTemp\Logs

The System Information utility provides access to the log files on the Summary screen. On the LogFiles tab, you can select the required log file from the Logfiles list.

The number and size of dump files (usually DMP code dump files as opposed to the much smaller .DMI information files) is also something that needs to be managed on a regular basis. These files are created whenever the PCMModel, PCMMain, or PCMServer services terminate abnormally from within the system (as opposed to being terminated by Task Manager or some other external means).

The DMI file contains header information about the associated DMP file such as which version of the software it was created under. The DMP file is a code dump that can be interpreted by SAP to determine which lines of code may have generated the resultant error within the service that was dumped.

The DMP and DMI files may be requested by SAP Customer Assurance if the system is experiencing stability issues, but otherwise can be removed or archived as and when you require.

Errors generated by the application backend servers are stored in the standard Microsoft Windows event log. They can be reviewed in the Event Viewer under the source of PCM Messages.

Related Information

Profitability and Cost Mangement System Information Tool [page 41]

SAP BusinessObjects Profitability and Cost Management Administrator's GuideMonitoring of SAP BusinessObjects Profitability and Cost Management P U B L I C 9

Page 10: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Log Files tab [page 45]

3.2.2 Data Growth and Data Archiving Monitors

The fastest growing tables in a system vary depending on the models in use. In cases where a problem exists in the model, the Alerts table can increase most rapidly, and needs to be monitored.

Other tables that can grow quickly are the Data tables (particularly the Activity Driver Value, the Revenue and the Resource Driver Value tables) and the Dimension tables.

The names of Data tables are listed in the “Database Data Tables” topic.

The Dimension tables are listed in the “Database Dimension Tables” topic.

For further information on monitoring and archiving data growth, refer to the SAP BusinessObjects Profitability and Cost Management Database Administrator's Guide.

3.2.2.1 Database Data Tables

OM_ASSMETRICEMPLOYEEOM_ASSMETRICRESPCENTEROM_ASSOBJECTIVEEMPLOYEEOM_ASSOBJECTIVEINITIATIVEOM_ASSOBJECTIVELOBJECTIVEOM_ASSOBJECTIVEMETRICOM_ASSOBJECTIVERESPCENTEROM_BOUNDARYINFOOM_EMPLOYEEBOM_EMPLOYEEBOUNDARYOM_ICONVALUEOM_METRICACTUALOM_METRICADJUSTMENTOM_METRICADJUSTTARGETOM_METRICBOM_METRICBASEPOINTOM_METRICBOUNDARYOM_METRICTARGETOM_OBJECTIVEACTUALOM_OBJECTIVEADJUSTMENTOM_OBJECTIVEADJUSTTARGETOM_OBJECTIVEBOM_OBJECTIVEBASEPOINTOM_OBJECTIVEBOUNDARYOM_OBJECTIVEMETRICWEIGHTING

10 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Monitoring of SAP BusinessObjects Profitability and Cost Management

Page 11: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

OM_OBJECTIVETARGETOM_OBJECTIVEWEIGHTINGOM_OBJMETRICWEIGHTINGOM_OVRMETRICEMPLOYEE OM_OVROBJECTIVEEMPLOYEE PP_ACTIVITYDRIVERVALUEPP_ACTIVITYDRIVERDELTAPP_ACTIVITYDRIVERTARGETPP_ASSRESPCENTERACTIVITYPP_BOMMAKEUPPP_BOMPRODUCTION PP_BOMUNITSSOLDPP_CURRENCYRATESPP_DEFAULTBOMMAKEUPPP_EMPLOYEEBPP_EMPLOYEERDSPP_EXTERNALACTIVITYVALUEPP_EXTERNALBOMUNITRATEPP_EXTERNALCOSTOBJECTVALUEPP_HVEXTACTCOUNITRATEPP_HVACTIVITYDRIVERVOLUMEPP_LINEITEMDETAILPP_LINEITEMFIXEDVALUEPP_LINEITEMDELTAPP_LINEITEMVALUEPP_LINEITEMVARVALUEPP_RESOURCEDRIVERDELTAPP_RESOURCEDRIVERDSPLITPP_RESOURCEDRIVERSPLITPP_RESOURCEDRIVERTARSPLITPP_RESOURCEDRIVERVALUEPP_RESOURCEDRIVERTARGETPP_REVENUEPP_SERVICEDRIVERDELTAPP_SERVICEDRIVERTARGETPP_SERVICEDRIVERVALUEPP_SERVICEFACTORPP_SPREADVALUEPP_WORKSHEETVALUE

3.2.2.2 Database Dimension Tables

For each of the dimension names listed below, three Dimension Tables exist, using the naming format

SAP BusinessObjects Profitability and Cost Management Administrator's GuideMonitoring of SAP BusinessObjects Profitability and Cost Management P U B L I C 11

Page 12: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

PP_#PP_#_NAMEPP_AT_#

(where # = dimension name):

ACTIVITYACTIVITYDRIVERBOUNDARYCOSTOBJECT1COSTOBJECT2COSTOBJECT3COSTOBJECT4COSTOBJECT5CAPACITYRULECURRENCYDTCOSTOBJECT1DTCOSTOBJECT2DTCOSTOBJECT3DTCOSTOBJECT4DTCOSTOBJECT5EMPLOYEEICONINITIATIVELINEITEMLINEITEMDETAILMETRICOBJECTIVEPERIODRESOURCEDRIVERRESPCENTERREVENUETYPESERVICESPREADUSERRULEVERSIONWORKSHEET1WORKSHEET2

3.2.3 Event Logs

Any issues that arise from opening or closing models are recorded in the following locations:

● Microsoft Windows Application server event log● Detailed application events log

12 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Monitoring of SAP BusinessObjects Profitability and Cost Management

Page 13: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

You initially configure the complexity of the log information while installing and configuring the application in the SAP BusinessObjects Profitability and Cost Management Configuration Wizard.

Related Information

Microsoft Windows Application Server Event Log [page 13]Detailed Application Event Log [page 13]

3.2.3.1 Microsoft Windows Application Server Event Log

In the Event Viewer screen, in the Windows Logs Application list, some of the following types of information for the PCM Messages are available:

● the name of the model● the name of user who opened the model● the names of any additional users logged into the model● messages when models are initialized or about to close● free disk space warnings● stopping and starting of software services

These detailed messages can assist with tracking the series of events that may have lead to a failure.

ExamplePCM Security Service: Service\Open\Model <Model Name> model Initializing

PCM Security Service: Service\Open\Model <Model Name> model Running Active Users <usernames>

PCM Model Service: Service\Logging\Free disk space is less than 2GB on the Model Directories

3.2.3.2 Detailed Application Event Log

With the Events logs, you can control the level of information tracked from day to day in a component. All application servers can generate logs and write events to one or more log files.

The log event message levels are:

● Debug● Path● Info● Warning● Error

SAP BusinessObjects Profitability and Cost Management Administrator's GuideMonitoring of SAP BusinessObjects Profitability and Cost Management P U B L I C 13

Page 14: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

● Fatal

For each component, you can define a destination log file and the minimum level of messages to be listed in the log file. For example, you can have:

● A day to day log file listing output errors and fatal events.● A log file that lists a specific path level, for using to debug a specific problem.

NoteThe event logging provides a historic picture of events on a machine, and provides useful information for debugging purposes. However for debugging issues in general in an application, we recommend that you use the CA Wily Introscope tracing.

● A log for a specific component/class/method.● A log for a PCMMain component sent to the c:\temp\ directory, and logs for a PCMServer component sent

to the default log location (C:\PCMTemp\Logs).

During the installation and configuration of the application, the user activates the log-configuration.xml file In the Advanced Server Options Server Logging Options . This file includes:

● Entries for each application service configured● Server severity errors

You configure the complexity of the log information detailed in the log-configuration.xml at one of the following locations:

● In the Server Logging Options section of the Advanced Server Options panel in the SAP BusinessObjects Profitability and Cost Management Configuration Wizard.

NoteTo update the settings on logs, launch the SAP BusinessObjects Profitability and Cost Management Configuration Wizard from Start Programs SAP BusinessObjects Profitability and Cost Management

Tools Configure .

● In the log-configuration.xml file using a text editor; however we recommend that you use the configuration wizard to update the file.

Related Information

log-configuration.xml File [page 15]Sample of log-configuration.xml file [page 15]

14 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Monitoring of SAP BusinessObjects Profitability and Cost Management

Page 15: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

3.2.3.2.1 log-configuration.xml File

The log-configuration.xml file controls the logging output for all the application servers installed on a single machine. The location of the log file is determined by the following registry key set up during installation:

HKEY_LOCAL_MACHINE\Software\Business Objects\Profitability\ApplicationDataDir

It defaults to the following value path:

[CommonAppDataFolder]\SAP BusinessObjects\PCM

Where [CommonAppDataFolder] is the path defined by the operating system on which the application is installed, for example, in Windows Vista it is C:\ProgramData\.

NoteBy default, the ProgramData folder is hidden, unless you have enabled View Hidden Folders in your browser explorer application.

The log-configuration.xml is located in the folder as specified by the registry key, within the ITSAM directory. For example, on Windows Server 2008 it is:

C:\ProgramData\SAP BusinessObjects\PCM\ITSAM

If the log-configuration.xml file does not exist, events are not logged.

Changes to configuration are applied live to any running SAP BusinessObjects Profitability and Cost Management application server and the system checks approximately every 30 seconds for changes in the configuration. Any changes are effective from that point. The application servers do not need to be restarted for changes to the log configuration to be applied.

Related Information

Sample of log-configuration.xml file [page 15]

3.2.3.2.1.1 Sample of log-configuration.xml file

The following sample log file defines multiple log destinations. Each destination XML tag details the log output options for that destination.

Example

<?xml version="1.0"?><log-configuration> <log-destinations> <log-destination name="PCMServer" type="PCMServer" pattern="%t/%c.%g.glf" effective-severity="ERROR" limit="5242880"/> <log-filters> <log-filter type="PCMServer::CEPOConnect::Login"/>

SAP BusinessObjects Profitability and Cost Management Administrator's GuideMonitoring of SAP BusinessObjects Profitability and Cost Management P U B L I C 15

Page 16: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

</log-filters> <log-destination name="PCMStatus" type="PCMStatus" pattern="%t/%c.glf" effective-severity="ERROR"/> <log-destination name="PCMMain" type="PCMMain" pattern="%t/%c.%g.glf" effective-severity="ERROR" count="10" limit="209715200"/> <log-destination name="PCMModel" type="PCMModel" pattern="%t/%c.%u.glf" effective-severity="ERROR"/> <log-destination name="PCMWorkManagerService" type="PCMWorkManagerService" pattern="%t/%c.glf" effective-severity="ERROR"/> <log-destination name="PCMReportService" type="PCMReportService" pattern="%t/%c.glf" effective-severity="ERROR"/> <log-destination name="PCMConfigurationService" type="PCMConfigurationService" pattern="%t/%c.glf" effective-severity="ERROR"/> </log-destinations> </log-configuration>

The second destination defined in this configuration shows an example of the filtering that can be applied to a log file, which further restricts events listed to the log file by Component::Class::Method.

3.2.3.2.1.2 File Attributes for log-configuration.xml

You can use the following attributes to configure the log-configuration.xml.

Table 2:

Attribute What it defines

name The name that describes the destination tag. The resulting output is a log entry in the log file whenever the logging is started for the destination, for example, when a software service starts and the first log event message is raised. If name is not specific, it defaults to SAP Standard.

type The application component to which the destination will apply. See the “Type attributes” section for a definition of the valid values.

pattern The output log filename, which can contain macros, that defines common paths and ad­ditional information. See the “Pattern attributes” section for more information.

effective-severity The minimum event severity level to be listed in the log file. See the “Effective-Severity attributes” section for more information.

count and limit The parameters that control log rotation. See the “Log Rotation” section for more infor­mation.

log-filter type An extra level of event control.

3.2.3.2.1.2.1 Type Attributes for log-configuration.xml

The type attribute that is set for a destination controls the SAP BusinessObjects Profitability and Cost Management component to which the destination applies.

One or more destinations can be specified for the same type. If, for example, you create a destination that outputs errors, and another destination that outputs information events, the first destination would only have Error & Fatal events in the log file, the second would have Information, Warnings, Errors & Fatal events. The logging

16 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Monitoring of SAP BusinessObjects Profitability and Cost Management

Page 17: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

implementation is optimized so that the event is only raised once, but is written to the appropriate log file as needed.

NoteThe attribute values are not case sensitive.

The following table defines the values for the destination's type attribute.

Table 3:

Type attribute value Executable that is logged

PCMServer PCMServer.exe

PCMMain PCMMain.exe

PCMModel PCMModel.exe

PCMWorkManagerService PCMWorkManagerService.exe

PCMStatus PCMStatus.exe

PCMWebService PCMWebService.exe

PCMIISPlugin PCMIISPlugin.dll

PCMConfigurationService PCMRemoteConfiguration.exe

PCMReportService RMMain.exe

Related Information

File Attributes for log-configuration.xml [page 16]log-configuration.xml File [page 15]

3.2.3.2.1.2.2 Pattern Attributes for log-configuration.xml

The pattern attribute defines the filename and path for the log output file.

Aspects of the attribute:

● This attribute in its simplest form can be set to a literal path and filename like D:\PCMLogs\MyLogFile.log.● The pattern has to be unique for each log destination. If the logging system detects that this filename is not

unique, it automatically changes the pattern to the default log pattern (%t/%c.%u.log).● The forward slash (/) or back slash (\) can be used in the pattern as the directory separator. The logging

system automatically translates these symbols to the required separator for the platform.● Percent (%[character]) macros can be added that are expanded to various paths and values by the logging

system.

The following table defines the valid %macros and their meaning.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideMonitoring of SAP BusinessObjects Profitability and Cost Management P U B L I C 17

Page 18: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Table 4:

%macro Description

%c Component Name

This macro expands to the SAP BusinessObjects Profitability and Cost Management application server name as defined in the destination type attribute. For example, if the destination has a type of PCMServer, %c will expand to PCMServer in the log filename.

%t Default logging directory

This macro reads the standard SAP BusinessObjects Profitability and Cost Management log files di­rectory name from the SAP BusinessObjects Profitability and Cost Management registry key. The log file directory name comes from the application configuration.

%h The service home directory

This macro expands to the service home directory.

%u A unique series of characters that guarantees that the file name is unique. The system uses a GUID to generate this and takes the form of:

{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

%g Sequence number for log file rotation. See the “Log Rotation” section for more information.

%% Used to insert a single percent (%) sign into the filename.

Related Information

File Attributes for log-configuration.xml [page 16]log-configuration.xml File [page 15]

3.2.3.2.1.2.2.1 Log Rotation for log-configuration.xml

Log rotation options instruct the system to determine the turnaround, or rotation rate of the log files.

Table 5:

Attribute What it defines

limit The file limit that determines when the current log file contents are backlogged to a renamed file and a new list of events started.

If the %g attribute is specified in a Pattern attribute and there is no limit attribute specified, then the log file is written to c:\logs\mylogfile.0.log and continues to grow in size indefi­nitely.

18 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Monitoring of SAP BusinessObjects Profitability and Cost Management

Page 19: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Attribute What it defines

count The number of rotated log files kept in the history.

If the count attribute is not specified, or is zero, then rotated log files are maintained indefinitely and are not removed. In this case, system administrators should monitor these files to ensure they do not use an excessive amount of disk space.

If the count attribute is set to a numeric value, then this number of log files is maintained auto­matically by the system. When a log file rotation number equals or exceeds this value, then the file is deleted.

The presence of a %g macro in the Pattern attribute activates this functionality.

For example, a pattern of c:\logs\mylogfile.%g.log sends log messages to c:\logs\mylogfile.0.log. When the log file size reaches the value as specified by the limit attribute, the log file is renamed to c:\logs\mylogfile.1.log. New events are sent to a new c:\logs\mylogfile.0.log file. If there was an existing c:\logs\mylogfile.1.log file, it is renamed to c:\logs\mylogfile.2.log and so on.

Because changes to the log file are picked up by the application servers without need for a restart, changing the log count can have side effects.

For example, you have specified a log rotation of 10, and the log files 0 to 9 have been created. If you lower the log rotation number to 5, and save the configuration, when the application server picks up the changes and writes the next log event, the files 5 through 9 are automatically deleted because they exceed the new log level.

If you will need the log files at a later date, move them elsewhere before changing the rotation count. If you removed the %g from the patterns, then any existing rotated log files are left in the log folder because the logging no longer processes the rotation.

Related Information

Pattern Attributes for log-configuration.xml [page 17]File Attributes for log-configuration.xml [page 16]log-configuration.xml File [page 15]

3.2.3.2.1.2.3 Effective-Severity attributes for log-configuration.xml

The effective-severity attribute controls the level of detail that is output to a log file. The severity level determines the minimum level of events logged. For example, if you set the level to Info, the log file lists Info, Warning, Error, and Fatal events.

Table 6:

Severity Details

All Outputs all log events.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideMonitoring of SAP BusinessObjects Profitability and Cost Management P U B L I C 19

Page 20: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Severity Details

Debug Offers a highly detailed level of information.

This severity should only be used if requested to resolve a specific problem.

Path For tracing the execution flow. An event is created at the start and end of every method.

For example, it is used in the context of entering and leaving a method, and looping and branch­ing operations. Like Debug, Path generates a very detailed log and should be used with caution.

Info Informational text, mostly for echoing what has been performed

Warning Anomalous events from which the application can recover to fulfill a required task, but which need attention from a developer or administrator.

Error Errors from which the application can recover, but which stop the application from fulfilling a required task.

Fatal Errors from which the application cannot recover, and where a severe situation causes a fatal termination.

None No log event output is required.

NoteThe attribute values are not case sensitive.

NoteIf no severity is specified the default value of "Error" is used.

Related Information

File Attributes for log-configuration.xml [page 16]log-configuration.xml File [page 15]

3.2.3.2.1.2.4 Log-Filter Type for log-configuration.xml

The log-filter attribute adds an extra level of event control. Filtering is designed to aid you in working with the SAP BusinessObjects Profitability and Cost Management support teams in diagnosing problems, and allows you to filter the log events for a specific destination down to a Component/Class/Method call.

Filters use the child tag <log-filters>, followed by one or more child <log-filters> attributes in the log-filters section. The <log-filter> has a type attribute that defines the filter to be applied.

20 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Monitoring of SAP BusinessObjects Profitability and Cost Management

Page 21: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Filters are applied by matching the filter string supplied by the filter's type attribute in the log-configuration.xml file against the method that is written to the log file.

You do not need to supply the whole string. For example, if you set the filter to PCMServer::CEPOConnect::, then any events that are raised by methods in the CEPOConnect class are added to the log file. In addition, PCMServer::CEPO matches any methods on any classes starting with CEPO in PCMServer.

Related Information

File Attributes for log-configuration.xml [page 16]log-configuration.xml File [page 15]

3.2.3.2.2 Log Message Format

The Event logs use the Generic Logfile Format (GLF). The file contains:

● A header section● In the file body a sequence of records separated by the RECORD_SEPARATOR character

The log message format for components are:

""Time|SourceName|ThreadId|Severity|Text""

Where:

● Time is the date and time using the format: YYYY MMM DD HH:MM:SS. For example ""2010 10 21 14:07:52""● SourceName is [ComponentName]::[ClassName]::[MethodName]● ThreadId is the Thread ID● Severity is the error severity, like Debug, Path, Info, Warning Error or Fatal● Text is the log message

A Profitability and Cost Management Log message (Text) uses the following format:

[Message Text] @ [filename]:[line number]

Example

FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2 FILE_ID:{F0D1FEDD-3B7F-407C-9150-18008301A7F5} (this is different for each file)ENCODING:UTF8RECORD_SEPARATOR:10COLUMN_SEPARATOR:94ESC_CHARACTER:0COLUMNS:Time|SourceName|ThreadId|Severity|TextSEVERITY_MAP:Debug|Debug|Path|Path|Info|Information|Warning|Warning|Error|Error|Fatal|Fatal HEADER_END2010 10 21 14:07:52^LogInformation^2696^Info^Logging started for log-destination:PCMStatus@.\log_destination.cpp:440 2010 10 21 14:07:47^PCMStatus::main^3824^Info^PCMStatus started@.\PADStatus.cpp:31"

SAP BusinessObjects Profitability and Cost Management Administrator's GuideMonitoring of SAP BusinessObjects Profitability and Cost Management P U B L I C 21

Page 22: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Related Information

Detailed Application Event Log [page 13]

3.2.3.3 Log File Generation

Logs generated by Profitability and Cost Management components can be viewed using the SAP Snap-In for Microsoft Management Console (SAP MMC). The SAP MMC can be installed on any machine including non-Profitability and Cost Management machines; however the Profitability and Cost Management logs that the user wants to view, for example GLF log files, need to be on the machine where SAP MMC is installed, or accessible from a remote machine.

To view files via SAP MMC, open a command line and type the following command:

C:\%windir%\sapmmcsnap.msc -SAP_VIEWTRACE "[relative path of GLF log file]"

For example:

%windir%\sapmmcsnap.msc -SAP_VIEWTRACE "D:\ShareFolder\ITSAM_Logs\PCMServer.glf"

NoteThe header section of the log file will not be displayed, as the contents of the header is only used to structure or format the log output.

Refer to the following website for information on SAP MMC: SAP MMC Snap-In

22 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Monitoring of SAP BusinessObjects Profitability and Cost Management

Page 23: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4 Management of SAP BusinessObjects Profitability and Cost Management

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.

4.1 Starting and Stopping

4.1.1 Standard Methods

The standard methods of starting and stopping the system are the methods that we recommend to ensure the success of retaining system data.

4.1.1.1 Starting the System

Prerequisites

Ensure that all services are operating normally, and errors have not been encountered before attempting to start the system.

Procedure

1. Ensure that PCMMODEL processes are not running from a previous session.To check which processes are running, press CTRL + ALT + DELETE or right-click the taskbar and select Task Manager to open the Windows Task Manager and click the Processes tab to view which processes are running.

2. Initiate the required software applications. The applications automatically start the relevant services.

NoteThe Report Manager service needs to be started. The client does not start this service automatically.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 23

Page 24: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.1.1.2 Stopping the System

Context

Use this procedure for closing down the system when the system is operating correctly, but the server must be shut down, for maintenance for example.

Procedure

1. In the User Monitor utility, check the User Details tab to see which users are currently using the system and ask them to log off.

NoteDo not use the Logoff button to force the users to log off. If you have the Work Manager application installed, you may notice a remaining user account logged into the Work Manager service. Do not forcibly log off this user, because it is running the PCMWorkmanagerService.

2. Once all the client user sessions have cleared, click Stop All in the Service Manager utility to stop all services. This clears the PCMWorkmanagerService account if you have this application installed.The system is now fully closed down and all user sessions and connections have been terminated.

Related Information

The Profitability and Cost Management Service Manager Tool [page 39]User Monitor [page 91]

4.1.2 Non-Standard Methods

If the system cannot be started or shut down using standard methods, then the procedures in this section can be used to terminate the system processes.

Where possible, the recommended SAP BusinessObjects Profitability and Cost Management tools need to be used to perform these procedures due to the interdependence of some services. Closing the system down correctly also aids the preservation of calculated results, and reduces the impact of a sudden closure on your user community. This also ensures that the system can be re-started with the shortest possible outage.

To stop the system, the following tasks must be carried out in order:

1. Determine the system status2. Use the Service Manager application to stop all the services (This is automatically performed in the correct

order). If this fails, click Kill all to terminate any orphaned services. Alternatively, use Stop All or Kill All in the Services tab for Current Services and Processes in the System Information utility.

24 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 25: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

3. Check the status of the PCMModel services using Windows Task Manager and terminate if necessary.

There may be more than one currently running PCMModel process listed in the Task Manager at any time. It is often difficult to identify which PCMModel process is the one that has failed and needs to be terminated.

Related Information

The Profitability and Cost Management Service Manager Tool [page 39]

4.1.2.1 Identifying Orphan PCMModel Processes

All PCMModel processes are controlled by their associated PCMMain service. In the event of a system failure it is possible for these processes to become disconnected from the parent service, and become orphan processes. If these processes are not terminated, then they may block future model requests, and may also continue to consume resources.

It is essential that all orphan PCMModel processes are cleared before restarting any servers, or resetting any services. The system has the capability to recover from minor interruptions to service availability, and to regenerate any temporary results associated with a particular model process.

To prevent possible regeneration loops, the software also attempts to restart processes that have had data source connections terminated. The first step in dealing with this is for you to identify such processes, and to terminate them before proceeding.

4.1.2.1.1 To Identify an Orphan PCMMODEL Process

Context

It is often difficult to differentiate between a running and an orphan model process after a service interruption, however, the Windows Task Manager application can be used to help identify these processes.

Procedure

1. To launch Windows Task Manager, right-click the Windows Task Bar and click Task Manager, or press CTRL + ALT + DEL and click Task Manager.

2. Click the Processes tab.3. In the list of processes, check for more than one of the following signs that may indicate the existence of an

orphan Model process:

○ A lack of CPU activity for extended periods of time (not calculating)

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 25

Page 26: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

○ The absence of input/output (I/O) disk operations (not writing results)○ Static memory usage (the memory usage does not increase to store results)○ The CPU time does not increase

NoteA single indicator cannot reliably identify an orphan process, but a combination of all or several of these indicators provides reliable guidance in most cases.

4.1.2.2 The Effects of Terminating the System

Terminating the SAP BusinessObjects Profitability and Cost Management system services has a number of potential effects upon both the user connections to the server, and the status of the models in which users were working when the system was terminated. The effects from closing each individual service are listed in the table below:

Profitability and Cost Management Service / Server Termination effect

PCMMain ● Previously requested data held in the cache is lost.● Results calculated during the session held in cache are

lost.● Communication between the Application server or Web

server and the database is lost.● Client sessions are unable to validate, and cannot

request new data views.

PCMServer ● Client sessions are unable to validate.● PCMMain service closes down shortly afterwards.● Any pending data transfers will be unable to complete

(e.g. web updates pending).

PCMModel ● Client sessions are unable to validate, and cannot request new data views.

● If other current model processes are not running, and users are not logged on, then the PCMMain service closes down shortly afterwards.

● Any pending data transfers will be unable to complete (e.g. web updates pending).

● Results files stored in the current Model directory folder will be orphaned and invalidated.

PCMWorkManagerService ● Any current client Work Manager sessions will be unable to validate, request new data, or save changes to the database.

● Scheduled workflow tasks may fail to trigger, or take the appropriate actions as a result of a trigger.

PCMReportService ● Any current client Report Manager sessions will be unable to validate, request new data, or save changes to the database.

26 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 27: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Profitability and Cost Management Service / Server Termination effect

Web Server ● Web users cannot connect with the model if the web server is unavailable.

Related Information

Controlling Profitability and Cost Management Services [page 35]

4.1.2.3 Starting the System After Termination

4.1.2.3.1 Re-establishing services

The following services are started when the operating system is restarted:

Service Startup Type Additional Service information

PCMMain Manual N/A

PCMReportService Automatic This service needs to be started; it does not start automatically from a client request.

PCMServer Manual N/A

PCMTransportService Automatic N/A

PCMWorkManagerService Manual It is possible to develop a SAP BusinessObjects Profitability and Cost Management workflow using the Work Manager workflow designer application, without the associated PCMWorkManagerService service running. In this case, the workflow cannot be tested or implemented because it requires the service to be running to co-ordinate workflow activities and to monitor workflow status.

NoteThe PCMWorkManagerService is automatically started by the PCMWorkManagerAutoBootService

PCMWorkManagerAutobootService

Automatic N/A

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 27

Page 28: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

NoteAny services that have a status of “stopped” can be started manually in the Service Manager application.

Related Information

Controlling Profitability and Cost Management Services [page 35]

4.1.2.3.2 Recovering results

When the system is restarted, several automatic housekeeping tasks are initiated by a specific service for each available model on the current Model server:

Service / Server Housekeeping Task

PCMMain ● Removes temporary (TMP files) from the temporary Model folder.

● Removes invalid model folders and associated temporary files.

● Deletes empty model folders.

PCMModel ● Deletes empty model folders.● If EPM files do not exist in the current model folder, then

the PCMMain service creates a new file to store temporary results.

Related Information

Controlling Profitability and Cost Management Services [page 35]

4.2 Software Configuration

This section explains which components or scenarios used by the application are configurable and which tools are available for adjusting.

Configuration Tool(s) Detailed Description

SAP BusinessObjects Profitability and Cost Management Configuration Wizard

Allows Administrators to define network and system component communication methods, types of system

28 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 29: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Configuration Tool(s) Detailed Description

component installation, and general software file locations, for new installations, upgrades or re-configuration purposes.

SAP BusinessObjects Profitability and Cost Management Silent Install Wizard (PCMSilentInstaller.exe)

The Silent Installer is a configuration tool that enables the software to be silently installed by batch file commands. The executable file (PCMSilentInstaller.exe) is located in the PCM_75_TOOLS folder on the SAP BusinessObjects Profitability and Cost Management installation CD, and allows Administrators to configure an installation batch file through screens in a Wizard. More detailed information on the use of this tool can be found in the SAP BusinessObjects Profitability and Cost Management Installation Guide.

SAP BusinessObjects Profitability and Cost Management Configuration Wizard

During the initial installation of the product, the software is configured for the first time in the SAP BusinessObjects Profitability and Cost Management Configuration Wizard. This is launched on completion of the installation process on both server and client machines, and can also be accessed from the Start ProgramsSAP BusinessObjects Profitability and Cost Management Tools Configure menu for re-configuration purposes.

The majority of the software configuration settings are stored in the registry, and each time the Wizard is executed, the configuration settings of the servers are copied from the default registry locations to a separate area in the registry, from where they can be restored after a re-installation of the software. When the software is uninstalled, the software configuration settings (DCOM, Report service, etc) are removed from the registry in the standard way, and the retained copy of the settings is used when the Wizard is initiated after a re-installation of the software.

During an original configuration of the software, a selection of languages are available to choose from in which to view the Wizard screens. The language selection here additionally sets the display language in the software user interface. However, if the wizard is re-launched for re-configuration purposes, the Language Options screen is not displayed, and language settings are available to configure in the Model Builder application through the Tools Options Language Selection menu.

The following software components are available to configure in the wizard:

● The type of client-server communication method, including DCOM security configuration and IP filtering for Sockets configuration.

● Definition of the Installation type - Primary or Secondary Application server, client machine, Work Manager server or client, Web server or client, or Report Manager server or client.

● The type of Web server (Microsoft Internet Information Services (IIS) or proprietary).● Microsoft SQL or Oracle Database Connectivity settings, including database level auditing.● Folder locations for:

○ Software models○ Log files○ Work Manager workflow files○ Web server temporary files

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 29

Page 30: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

● License configuration.● Types of user login security authentication for integration with LDAP or Windows Active Directory across

multiple domains, Single Sign On security in an SAP BusinessObjects Business Intelligence platform environment, and user login security for the Web.

● Book and model objects for the BusinessObjects Enterprise InfoView application.● Multiple system login options to enable users to select a server to log in to on the Login screen.● Web server location for the SAP BusinessObjects Financial Information Management application in an SAP

BusinessObjects Business Intelligence platform environment.● SAP System Landscape Directory registration.● Remote Configuration Tool installation type.● The level of performance counters that are produced for analysis through NCS configuration.● Application passport tracing.● Detailed server logging options.

Specific information about how to use this tool is covered in the SAP BusinessObjects Profitability and Cost Management Installation Guide.

Related Information

Application Passports [page 115]

4.2.1 Configuring Multiple System Login

You can have multiple systems set up in your organization, each containing several servers with multiple clients. A typical example is a set up that uses two systems: one for development and one for production. In this case, it is useful for a user who works with both systems to be able to select the system they want to log in to from the Login screen.

The Multiple System Login feature allows a user to connect to the required system by selecting the primary application server from a list that you configure. You can also allow users to enter a server of their own choice at login. The login methods that end-users log in with can also be configured. These settings are configured in the Profitability and Cost Management Configuration Wizard.

A typical scenario of multiple clients logging into different servers is shown in the following diagram:

30 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 31: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 31

Page 32: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.2.1.1 Configuring Login Options and Multiple System Login settings

The SAP BusinessObjects Profitability and Cost Management Configuration Wizard contains the following two screens to configure login options for end-users:

● Login Options● Multi System Options

4.2.1.1.1 Configuring Login Options

The Login Options screen allows you to control the login methods from which users can choose on the Login screen. You can allow users to select from a list of authentication types, as well as setting the default login type. The following options are available to select:

● Allow Users to Select from the List of Available Authentication Types● Default - this selects whichever Single Sign On type is highlighted as default.

If you select a combination of Allow Users to Select from the List of Available Authentication Types and a default Single Sign On type, the user is presented with a list of authentication types to choose from, and the type you have selected as default is displayed as the default choice in the Authentication Type list on the Login screen. A default Single Sign On type must exist, but the user can select a different type when logging in.

If you deselect the Allow Users to Select from the List of Available Authentication Types option, the list of authentication types is hidden on the Login screen, and the user is forced to login with the Single Sign On type that you set as default.

NoteInitially, the default Single Sign On type is set to Profitability and Cost Management Standard Security.

4.2.1.1.2 Configuring Multiple System Options

The Multi System Options screen allows you to control which servers are available on the Login screen, and whether users can manually enter the names of servers to connect to.

There are two checkbox options to select as follows:

● Allow the user to select from the list of available servers● Allow the User to Enter a Server Name During Login

The first checkbox overrides the second checkbox, so that if you deselect the first checkbox, then the second checkbox is automatically disabled. So, with the first checkbox selected, users are able to select from a list of servers. Then optionally the second checkbox can be selected to give them the extra ability to manually enter server names.

In addition, you can combine options across the two screens to control which options are displayed to the user. If you deselect the Allow the user to select from the list of available servers, and on the Login Options screen,

32 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 33: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

deselect Allow users to select from the list of available authentication types, then the end-user sees only the User Name and Password boxes on the Login screen, and their authentication type is the type you have selected as default.

This combination can be selected if you only required standard Profitability and Cost Management login authentication, and the end-user only needs to enter a user name and password to login to the system.

4.2.1.2 Distributing Multiple System Login Settings to Clients

Context

If you have a large amount of client machines for which you want to configure multiple system login, we recommend the following rollout process:

(Refer to the SAP BusinessObjects Profitability and Cost Management Installation Guide for step-by-step configuration instructions.)

Procedure

1. Install and configure the software with required Single Sign On login and multiple system login options on the primary application server, followed by any secondary application servers.

2. Then install and configure the software with required Single Sign On login and multiple system login options on one client machine.

3. Run the Configuration Wizard in file mode on the client machine by entering the following command at the command prompt: (The Program Files folder may be different between 32-bit and 64-bit operating systems.)C:\Program Files\SAP BusinessObjects\PCM\PCMConfigure.exe /fileThe SAP BusinessObjects Profitability and Cost Management Configuration Utility is launched.

4. Click Configure Read to load the current configuration of the client into the Configuration Utility.5. Click Yes to confirm the upload of configuration settings and click OK on the information message.

6. Click the Save button in the toolbar, or click File Save .7. Enter a name for the configuration file in the File name box and click Save. Save the .ecf file to an accessible

network location to distribute to client machines.8. Create a batch file to distribute the ECF configuration file to clients, for example:

@ECHO OFF :: This batch file silently configures Profitability and CostManagement.ECHO***********************************************************ECHO START CONFIGURING PROFITABILITY AND COST MANAGEMENTECHO***********************************************************ECHO.ECHO.:: Configure PCM using the /file option of PCMConfigure"C:\Program Files\SAP BusinessObjects\PCM\PCMConfigure.exe" "C:\PCM_ConfigFile.ecf" /file

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 33

Page 34: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

echo.echo.ECHO************************************************************ECHO FINISH CONFIGURING PROFITABILITY AND COST MANAGEMENTECHO************************************************************ECHO.ECHO.ECHO.

4.2.1.3 Adding a New Server

The servers that are available in the Login screen for end users to choose from are stored in the following local registry key:

● For 32-bit machines: HKEY_LOCAL_MACHINE\software\Business Objects\Profitability\DefaultPCMServers

● For 64-bit machines: HKEY_LOCAL_MACHINE\software\wow6432node\Business Objects\Profitability\DefaultPCMServers

If a new server is added, and you want to make the server available for users to log in to, we recommend the following method of distributing the new server name to client machines:

● Use the Remote Configuration tool to add the server name into a configuration file and distribute the file to client machines.

Other distribution methods are available, including the following:

● Use Group Policy to push the registry key out to client machines with the new server name in the key. This method requires the involvement of the IT department.

● If you have configured multiple system login options to allow users to manually enter a server name on the Login screen, then users can enter the new server name at login time. On successful connection, the new server is automatically saved to the local registry key. This method places the emphasis on end-users to enter the correct server name for a successful connection.

Related Information

SAP BusinessObjects Profitability and Cost Management Remote Configuration Tool [page 53]

4.3 Administration Tools

The following table lists the available software administration tools to manage various areas of the product:

34 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 35: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Tool Detailed Description

Console This tool allows the setup of command-line statements to establish scheduled tasks to run commands against the various software applications. Refer to the SAP BusinessObjects Profitability and Cost Management Console User Guide.

User Monitor This administration tool allows you to monitor model usage. The primary function of this tool is to enable Administrators to manage application usage during software upgrades or removal procedures. Refer to the “User Monitor” section.

Service Manager Enables the administration of the main software application services. Refer to the “Controlling Profitability and Cost Management Services” section.

System Information This administration utility provides information about the current status of the software. It is mainly used to manage software versioning, users and models. Refer to the “Profitability and Cost Management System Information Tool” section.

Model Administration The Model Administration dialog box provides access to functions that enable you to manage models, alter model properties, and control model access. Refer to the “Model Administration” section.

You can also use the Dependencies Viewer screen in the Model Builder application to view the dependencies that arise from the assignments and rules in a model. Refer to the SAP BusinessObjects Profitability and Cost Management Modeling User Guide.

Related Information

User Monitor [page 91]Controlling Profitability and Cost Management Services [page 35]Using the System Information Tool for Troubleshooting [page 100]Model Administration [page 68]

4.3.1 Controlling Profitability and Cost Management Services

The Profitability and Cost Management Service Manager is used to control the status of the main Profitability and Cost Management services by starting or stopping them manually, or closing them down if required. While this can also be performed in the Services applet provided with the operating system, the Service Manager application offers a safer and more reliable method of control because it ensures that any services that have a dependency on another service in order to operate, are started or stopped in the right order, at the right time, and with due consideration given to the preservation of model results.

Other ancillary Profitability and Cost Management system services cannot be controlled by the Service Manager and must only be adjusted by the System Administrator.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 35

Page 36: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Further advice may be obtained on the correct procedures for starting up and shutting down services, in the form of a document available via SAP Customer Support.

Related Information

The Profitability and Cost Management Service Manager Tool [page 39]

4.3.1.1 Controllable Services

The services that are controlled by the Service Manager are:

● PCMMain● PCMServer ● PCMReportService ● PCMWorkManagerService

4.3.1.1.1 PCMMain

This service controls the interaction of model data and model security between the application and the Application Server. It also houses one of the main caches of data from previously retrieved results. Terminating this service may affect model results.

4.3.1.1.2 PCMServer

This service controls the security access of the overall system, through logon authentication. Session information is stored on the database so that connected users are not logged out after restarting this service.

4.3.1.1.3 PCMReportService

This service controls the servicing of client requests for printing reports that have been requested to print by a Report Manager Task. Other reports printed by a client on an ad-hoc basis are unaffected by the status of this service.

4.3.1.1.4 PCMWorkManagerService

This service monitors for and reacts to changes in published Workflow processes.

36 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 37: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.1.2 Ancillary Services

The ancillary services play a supporting role to the main services. These services cannot be controlled from the Service Manager interface.

4.3.1.2.1 PCMStatus

This service monitors the status of other services. If a model service closes, this causes the PCMStatus service to prompt the PCMMain service to start the process of compacting temporary results files.

4.3.1.2.2 PCMWebService

This service handles all HTTP protocol traffic between the Web Server and Web Client machines. The PCMWebService is only listed if the proprietary Web Server is installed (that is, not the IIS Web Server, which is handled by its own Control Panel applet). Resetting this service logs connected web users out of the system.

4.3.1.2.3 PCMExcelService

PCMExcelService accepts requests from the SAP BusinessObjects Solutions, add-in for Microsoft Office (EPM add-in) and also applies updates from the EPM add-in to the Profitability and Cost Management system. The EPM add-in connects to the service via the PCM REST Connection. The PCM REST Connection enables write-back to the the Profitability and Cost Management system.

4.3.1.2.4 Sockets Transport Services

The Sockets Transport Layer is available as an alternative to the default DCOM Transport Layer. Profitability and Cost Management remains a COM-based application, but the implementation of Sockets offers a simpler mechanism to provide remote application services.

The sockets services have similar names to those of the main services. They are identified by ending with the letters “IPS”.

4.3.1.2.4.1 PCMTransportService

This service is the main service controlling the socket connections between the clients and servers. It acts as a central co-ordinator of all the socket requests from the other ancillary services, and manages the pooling of connections for re-use.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 37

Page 38: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

The PCMTransportService can be managed through the usual Windows Services applet found in the Administrative Tools section of the Control Panel.

CautionOther supporting transport services cannot be managed in this way and must not be started or stopped independently of the PCMTransportService.

4.3.1.2.4.2 PCMServerIPS

This service translates calls from the PCMServer service into IP requests for socket connections.

4.3.1.2.4.3 PCMMainIPS

The service that translates calls from the PCMMain service into IP requests for socket connections.

4.3.1.2.4.4 PCMModelIPS

The service that translates calls from the PCMModel service into IP requests for socket connections.

4.3.1.2.4.5 PCMWorkManagerServiceIPS

The service that translates calls from the PCMWorkManagerService into IP requests for socket connections.

4.3.1.3 Service Dependencies

Some services are dependent upon other services in order to run. The dependencies are managed by the Service Manager in such a way that, as services are stopped and started, Service Manager takes into account the dependencies between services and changes the status of linked services accordingly. For example, if a user uses the Stop All command, Service Manager stops PCMMain before it stops PCMServer.

The following table describes the various service dependencies:

Table 7:

Service / Server Linked to

PCMMain PCMServer

38 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 39: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Service / Server Linked to

PCMWorkManagerService

PCMReportService

PCMExcelService

PCMMainIPS PCMTransportService

PCMModelIPS

PCMServerIPS

PCMWFM

4.3.1.4 The Profitability and Cost Management Service Manager Tool

The Profitability and Cost Management Service Manager utility is installed with the server components.

4.3.1.4.1 To Launch Service Manager

Procedure

1. Select Start All Programs SAP BusinessObjects Profitability and Cost Management Tools Service Manager .

2. After launching the application from the Start menu, the Service Manager appears as an icon in the System

Tray: (part of the Windows Task Bar). Open the application by double-clicking the icon or select Open Service Manager from the context menu.

4.3.1.4.2 User Interface

The Service Manager interface lists the name and filepath of each service and displays their status. These can be:

● Running● Stopped● Stop Pending – the PCMMain service demonstrates this status when it is saving calculated results before

closing down.

The interface also provides the following commands to manage services:

RefreshStart service

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 39

Page 40: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Stop serviceStop AllKill all

4.3.1.4.2.1 Refresh

Refresh determines the current status of any services that are listed. This function can be used to verify the status of a service if it has been changed by a Profitability and Cost Management application, or manually using the Services applet available from the Windows Control Panel.

Services that are started or stopped using the Service Manager automatically have their status updated without the requirement to refresh the status screen manually.

4.3.1.4.2.2 Start Service

Start Service starts a service that is currently stopped. A running service displays a green triangular icon.

4.3.1.4.2.3 Stop Service

Stop Service stops a service that is currently running. A stopped service displays a red square icon.

4.3.1.4.2.4 Stop All Services

Stop All stops each of the services consecutively in the correct order. Performing this action is the same as closing a model, thus it preserves any calculated results files.

Related Information

Stopping the System [page 24]

4.3.1.4.2.5 Kill All Services

Kill All terminates all running services immediately. This bypasses the usual safe shutdown procedure, thus causing any existing results to be lost.

40 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 41: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

If a service does not terminate after using this function the service must be stopped using Task Manager in Interactive Mode, or restart your server.

4.3.1.4.2.6 Auto-Start When Login

Checking this option starts the Service Manager application automatically whenever the operating system is started.

4.3.1.4.3 Stopping Services in the Correct Order

If it is absolutely necessary to stop the services manually, it is important that this task is carried out in the correct and following order:

● PCMWebService● PCMWorkManagerService● PCMMain● PCMServer

Task Manager must then be used to clear out any remaining process instances created by the PCMModel service.

NoteIt is important to be aware of the impact of terminating model services on any related temporary results.

4.3.2 Profitability and Cost Mangement System Information Tool

The SAP BusinessObjects Profitability and Cost Management System Information utility is a useful tool to display information about the current status of the Profitability and Cost Management system. It brings together many of the functions that are available elsewhere in Profitability and Cost Management, and which are of particular use to Administrators, into a single easy-to-use application.

There are two main areas of functionality:

System InformationReporting

4.3.2.1 System Information

Administrators can use Profitability and Cost Management System Information to check that the Profitability and Cost Management system has all of the correct software installed, and to manage users and models.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 41

Page 42: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Profitability and Cost Management System Information contains information about the following areas of the system:

● Currently running Profitability and Cost Management applications● Model information● Current users● Technical information about the machine hosting the application● A prerequisite compatibility check● A list of services and processes● Settings for Internet Information Server (if installed)● Settings for SQL Server or Oracle (if installed)

Related Information

Available System Information [page 42]

4.3.2.1.1 Available System Information

When the System Information utility is initiated, the System Summary details are displayed by default in the right-hand pane. The default main screen is shown below:

42 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 43: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

You can select functions from the main menu in the left-hand pane. The sections that follow describe these options.

4.3.2.1.1.1 System Summary

Provides a summary listing of the specification of the machine upon which the Profitability and Cost Management System Information tool is run.

The listing includes information about the computer resources including:

The operating system (including version and build number)Locale and Time ZoneNumber and type of processorsMemory resources (virtual, physical, and paging file)Drive mappings

4.3.2.1.1.2 Prerequisites

The prerequisites are essential third party components that Profitability and Cost Management relies upon for particular functions such as accessing the Database Server, generating XML format files, and processing VBScript.

The following sections describe the information that can be returned via System Information in relation to these components.

4.3.2.1.1.2.1 Data Access Components

Microsoft supplies a package of components for data access, collectively known as MDAC. Profitability and Cost Management System Information can report the version of the overall package, and specifically reports the version number of several essential components:

OLEDB32.DLLSQLOLEDB.DLLORAOLEDB.DLLMSADO15.DLL

NoteThe presence of SQLOLEDB and ORAOLEDB DLL files is dependent upon which client software is installed on the machine. Installing Microsoft’s MDAC components will install the SQLOLEDB driver, while installing the Oracle Client software will result in the ORAOLEDB component appearing in the list.The OLEDB and MSADO components should have the same file version as the overall MDAC package.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 43

Page 44: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.2.1.1.2.2 XML Parser

The version of the currently installed MSXML library file can be found in this section. Only one file is required to support XML-rendering capabilities. The file service pack information can be seen in the File Description column.

4.3.2.1.1.2.3 Scripting Engine

The Windows Scripting Host controller file is detailed in this section. The information found here can also be cross-checked by running the command CSCRIPT in a command window.

4.3.2.1.1.2.4 Internet Explorer

The current version of Internet Explorer can be confirmed in this section. The currently supported version of IE should be cross-checked against that listed in the Profitability and Cost Management Master guide.

4.3.2.1.1.3 Summary

The Summary tabs contain all of the current installation configuration settings. They provide a useful summary of all the relevant Profitability and Cost Management settings in one place. The tabs are:

SummaryFilesLogFilesSerial NumbersComponents' DCOM Permissions

4.3.2.1.1.3.1 Summary tab

This screen is a summary of the roles that the current server is supporting. This tab displays the following information:

● Whether the server is registered for a role, for example the primary application server● Service account credentials● Primary server connection details, if that role is performed● Web server details, if that role is performed● Model server resources, such as free disk space and available memory● Version of the currently installed ActiveX web component

44 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 45: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.2.1.1.3.2 Files tab

This screen lists the files currently located in the directories related to Profitability and Cost Management. Select the required directory from the drop-down list. Access to the following directories is provided:

● The installation directory for Profitability and Cost Management files, including executables● The Common Files directory for shared files● The current Models directory for temporary results storage area● The Log Files directory where logs generated by Profitability and Cost Management are stored● The Web Files directory for the files copied to an IIS virtual directory

The file lists can be used to determine whether the version numbers match with the currently installed version number.

4.3.2.1.1.3.3 Log Files tab

Use this tab to inspect the contents of the Log Files directory. The drop-down list provides access to all the types of log file that Profitability and Cost Management stores, as follows:

● Web activity logs (PCM COM Provider logs)● Configuration errors such as errors that result from the use of the Profitability and Cost Management

Configuration Wizard● The main Profitability and Cost Management error log, which records details of any displayed error

4.3.2.1.1.3.4 Serial Numbers tab

Keep track of the serial numbers in use with this tab. It displays the encrypted key, its duration (time-limited, permanent, or evaluation), the product licensed, and the number of users that the license permits.

NoteSerial numbers cannot be changed in this application; this must be done using the Profitability and Cost Management Configuration Wizard utility.

4.3.2.1.1.3.5 Components' DCOM Permissions tab

This tab shows each service registered against the current server, along with the names of users and groups that have Access or Launch permissions granted to them. Default settings mean that no specific DCOM configuration has been applied.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 45

Page 46: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.2.1.1.4 Current Services and Processes

When accessing the list of services and processes you are prompted to log in using Profitability and Cost Management account credentials. Supplying a valid login gives access to enhanced information. Canceling the login still gives access to service and process information.

4.3.2.1.1.4.1 Services tab

Each Profitability and Cost Management service is listed with the exception of the PCMModel processes, which appears in the Processes tab.

The service list has the same functions as the Profitability and Cost Management Service Manager. The information is shown in the columns detailed below:

● Service Name – the name that the service is registered as, as seen in the Properties dialog box of the Services tool from the Administrative Tasks program group.

● Status – whether the service is Running, Stopped, or is in a Stop Pending state. Stop Pending means that a request has been made to the service to stop once it has completed the currently running request.

● Logon as – the name of the Windows account used to activate the service.● Path – the file path to the service file.

The panel of buttons at the bottom of this tab gives control over the service state, as follows:

● Refresh – updates the display by polling the service to determine its current state.● Start Service - starts a selected service if it is in a stopped state.● Stop Service – stops a selected service if it is currently running.● Stop All – stops all listed running services.● Kill All – first attempts to stop all listed running services, and then terminates all currently running Profitability

and Cost Management processes if they do not respond to the call to stop.

Related Information

Models [page 47]The Profitability and Cost Management Service Manager Tool [page 39]

4.3.2.1.1.4.2 Processes tab

By default, only Profitability and Cost Management processes that are running are listed in this tab, but you can display all processes by deselecting the View only PCM processes check box.

The Processes tab gives a more detailed view of the Profitability and Cost Management services that are currently running. In this tab you can view the following:

46 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 47: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

● The Process Identifier (PID) for the Profitability and Cost Management process. If a successful login was supplied when prompted by Profitability and Cost Management System Information, the name of the model is shown in brackets alongside the appropriate PCMModel processes.

● The account being used to run the process in the User Name column.● The current memory usage for the process● The file path to the service or process

Selecting a service from the list enables the End Process button. This button terminates the selected process, like the Windows Task Manager, and can be used for the same purposes.

4.3.2.1.1.5 Current Users

The Current Users screen provides a list of current users, using the same functionality as the SAP BusinessObjects Profitability and Cost Management User Monitor application, which is described in this document.

In particular the Logoff button should be used with caution, and we recommend that you read the relevant section in this document for information concerning this feature and its use.

Related Information

User Monitor [page 91]Logging off a User [page 92]

4.3.2.1.1.6 Models

When accessing the list of models, you may be prompted to log in using Profitability and Cost Management account credentials. Supplying a valid login gives access to detailed model information. Canceling the login gives restricted access to model information.

Once the list appears, click a model to access the Model Processes and Information tabs.

4.3.2.1.1.6.1 Model Processes tab

When a model is selected, this tab first determines whether the model is open or not. If the model is not open, the screen does not show model information

Click the Model Information tab to open the model and obtain detailed information. This action can start a Profitability and Cost Management calculation if the model has Automatic Calculation set, however the calculation will stop when the model process has closed down. The model process automatically closes after a few minutes. Therefore you may notice some CPU activity on the Application Server while inspecting models using this application.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 47

Page 48: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

NoteRemaining in the Model Information tab keeps the currently selected model open.

The Model Processes tab comprises two panes, showing lists of model and user details. In the upper pane is a list of PCMModel processes in use by the selected model, for example how many copies of the model are running at once, or in the case of a partitioned model, the number of simultaneous open partitions. The information columns show the model’s process identifier (PID), and which <Versions>, <Periods>, and <Responsibility Centers> are contained within the model. This is particularly useful for partitioned models that may have been partitioned by one of these dimensions.

In the lower pane is a list of users that are currently logged into the selected model. Unlike the Current Users section, this information is specific to the model selected.

The Model Processes tab displays a number of buttons:

● Kill Model – Terminates the currently accessed model by stopping the associated PCMModel process.● Logoff – Logs the selected user off the system.● Update – Manually refreshes the information in this screen, updating any changes to the information

displayed.

The Auto Refresh check box toggles between either updating the information in the Model Processes tab automatically, or manually using the Update button.

4.3.2.1.1.6.2 Model Information tab

This screen gives more detail on the internal structure of the model being scrutinized. The model description and current model server (application server) are listed, along with the model statistical information. This is the same information as supplied by the Model Statistics function in the Profitability and Cost Management Model Builder application.

The model statistics show the number of dimension items that exist within the model, and the number of potential calculations that might be performed for each value. To see the number of potential calculations, select a value—for example CurrencyRate—from the list named Calculate possible number of combinations. The number of combinations displays to the right of the list.

4.3.2.1.1.7 Microsoft IIS

Microsoft Internet Information Services (IIS) system information is displayed on the following two tabs:

IIS InformationIIS Configuration Browser

48 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 49: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.2.1.1.7.1 IIS Information tab

Context

The IIS Information tab provides three panes of information relating to Microsoft's Internet Information Services (IIS) web server.

The header area lists the current version and file path for the web server and its files.

The upper pane displays relevant information for IIS. The timeout values—the length of time that the web server will wait until it assumes that no activity is taking place—are shown here. These values cannot be amended in this application.

Procedure

1. Click Run IIS Admin to open the IIS Admin application.This opens an instance of Microsoft's Internet Information Services (IIS) Management console in a separate window.

2. Modify the values in the IIS Admin application.The lower pane gives information concerning the versions of the files that Profitability and Cost Management is dependent upon to serve web pages. Two versions are displayed, with the File Version number including service pack information.

4.3.2.1.1.7.2 IIS Configuration Browser tab

This screen shows the entire registry key structure as it relates to Internet Information Services (IIS) settings. Browse using the tree structure in the left-hand pane to see the setting values in the right-hand pane.

The following IIS settings are available:

● IISAdmin – Settings for the IIS Administration application (IISADMIN).● Logging – If IIS Logging is enabled then the settings for this feature are listed here.● W3SVC – The primary source of IIS information. These settings are where all of the Profitability-related IIS

information is stored.● MimeMap – The MimeMap property provides a list of the file name extensions for Multipurpose Internet Mail

Extensions (MIME) mappings.● MSFTPSVC – These settings are used to configure the FTP service and sites.● SmtpSvc – These settings are related to the Logging section above and log internet activity from the web

server.● EventManager – Contains a list of registered events that IIS is aware of.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 49

Page 50: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.2.1.1.8 Microsoft SQL Server

If the machine has a Microsoft SQL Server database, the following information is available.

NoteThis information does not refer to your Profitability and Cost Management database, if it resides on a separate server.

4.3.2.1.1.8.1 SQL Server tab

The header area shows the current Microsoft SQL Server version and service pack. The pane below the header lists the Microsoft SQL Server files that are necessary for interaction with Profitability and Cost Management, along with the following information:

● File name – the name of the file as it can be found on the database server● File path – the location of the file on the database server● Version – the version of the file● File version – more detailed file version information● File description – a short explanation of the application or file

Below this pane are two buttons that allow you invoke the two most common SQL Server tools:

● Run Enterprise Manager- Opens an instance of Microsoft's SQL Server Enterprise Manager console in a separate window.

● Run Query Analyzer - Opens an instance of Microsoft's SQL Server Query Analyzer application in a separate window.

4.3.2.1.1.9 Oracle

If the machine has an Oracle database, the following information is available.

NoteThis information does not refer to your Profitability and Cost Management database if it resides on a separate server.

4.3.2.1.1.9.1 Oracle Database tab

The header displays the current Oracle database instance name, along with the name of the currently configured tablespace, reported as the user name. The pane below the header lists the Oracle version and other settings, such as:

50 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 51: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Language and RegionCharacter setCurrency settingsDate and Time settingsSort order

4.3.2.2 Reporting

The primary purpose of the Profitability and Cost Management System Information tool is to report information back to Business Object’s Helpdesk in the event that this information is requested to troubleshoot an issue or request.

The utility can be used to produce a summary or detailed report of the system information.

Related Information

Reporting from System Information [page 51]

4.3.2.3 Reporting from System Information

Business Objects Helpdesk may request information in the format of a report, to better understand the system that is under discussion.

You can access the Profitability and Cost Management System Information reporting options from the File menu on the main menu bar, or via the icons on the toolbar.

4.3.2.3.1 Create Detailed Report

The Detailed Report contains all the information that could be relevant to the installation and support of Profitability and Cost Management. In addition to the information provided as part of the Summary Report, the following additional sections are included:

● A list of files in the installation directory (by default C:\Program Files\SAP Business Objects\PCM)● A list of files in the common files directory (by default C:\Program Files\Common Files\SAP Business

Objects)● A list of model directories (used to store temporary result files)● A list of files in the log files directory (by default C:\PCMTemp\Logs)● A list of serial numbers and their associated user numbers● DCOM settings showing access and launch permissions● A list of processes currently running on the machine

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 51

Page 52: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

● A list of the licensed Profitability and Cost Management products, and the number of licensed users currently logged on

NoteTo create a complete Detailed Report, use a profile that has Local Administrator rights over the machine being analyzed. Profiles with less privileges may contain less information, because information is only gathered according to the rights of the currently logged on Windows user.

4.3.2.3.2 Print Summary Report

Sends the information produced for a Summary Report directly to the default printer.

4.3.2.3.3 Create Summary Report

Use this function to create a summary report. Profitability and Cost Management System Information prompts you to provide a location for the resulting text file.

The contents of a Summary Report are as follows:

● A system summary● List of Profitability and Cost Management prerequisite files and versions installed on the current machine● A list of server registration details, including service account credentials● Internet Information Server, SQL Server, and/or Oracle database information (file versions and locations)

Related Information

Prerequisites [page 43]System Summary [page 43]

4.3.2.3.4 Mail Detailed Report

Before mailing the report, you are prompted to save the report to a text file. This file is then attached to an e-mail template for you to complete the recipient's mail address, and to amend the message body.

In addition to the Detailed Report text file, any existing log files from the Profitability and Cost Management Log Files directory are also included to provide a comprehensive snapshot of the current machine, from a Profitability and Cost Management perspective.

This mail facility will utilize the current SMTP service's settings to deliver the Profitability and Cost Management Detailed Report. If no SMTP service is installed or configured then this function will not work.

52 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 53: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

NoteRefer to the type of information that is produced in a Detailed Report, and the limitations of the logged on user profile.

4.3.3 SAP BusinessObjects Profitability and Cost Management Remote Configuration Tool

The Remote Configuration tool is designed to distribute configuration files to multiple client machines and is available in a Windows version and a Web version. The Remote Configuration tool works by running the Profitability and Cost Management Configure tool in file mode, and depending on which version you are using, you can use the Remote Configuration tool to do the following:

● Retrieve, update, and publish configuration files to local and remote client machines.● Launch and use the System Information, User Monitor, and Service Manager tools.

The Remote Configuration tool cannot be used to distribute DCOM, or Report Service settings to primary and secondary application servers, even if the configuration file to be distributed originates from a server configured with these settings. The Remote Configuration tool is designed for the sole purpose of distributing configuration settings to multiple client machines, and not to restore server configuration settings.

Any machine that you want to configure remotely must have the Remote Configuration service installed and running properly. For more information, see the SAP BusinessObjects Profitability and Cost Management Installation Guide.

4.3.3.1 Remote Configuration Security

To configure security for remote configuration, we recommend that you create a user group specifically for remote configuration administrators. The members of the group should be Administrator users who have the right to perform remote configurations, but do not have the right to work with model data. Access to the Remote Configuration tool is controlled by the Remote Configuration Security security descriptor. For more information on the descriptor and how to create user groups, see the SAP BusinessObjects Profitability and Cost Management Security Guide.

4.3.3.2 Configuration Files

When you retrieve a configuration file using the Remote Configuration tool, the Configure tool creates an ECF file that contains all the configuration information for that machine (except DCOM security settings and Report Service Account settings), including the contents of the following files:

Application-passport.xmlNCS.conflog-configuration.xml

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 53

Page 54: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

For more information on these files, see the relevant topics in the SAP BusinessObjects Profitability and Cost Management Administrator's Guide.

When you publish a configuration (ECF) file to a machine using the Remote Configuration tool, the Configure tool applies all the settings in the ECF file to that machine.

ExampleSample entries in an ECF file

[LogConfigurationFile] 0=<?xml%20version="1.0"?><log-configuration>1=%20%20<log-destinations>2=%20%20%20%20<log-destination%20name="PCMServer"%20type="PCMServer" %20pattern="%t/%c.glf"%20effective-severity="ERROR"/>3=%20%20%20%20<log-destination%20name="PCMStatus"%20type="PCMStatus" %20pattern="%t/%c.glf"%20effective-severity="ERROR"/>4=%20%20%20%20<log-destination%20name="PCMMain"%20type="PCMMain" %20pattern="%t/%c.%g.glf"%20effective-severity="ERROR"%20count="10"%20limit="209715200"/>5=%20%20%20%20<log-destination%20name="PCMModel"%20type="PCMModel" %20pattern="%t/%c.%u.glf"%20effective-severity="ERROR"/>6=%20%20</log-destinations>7=</log-configuration>8=</log-configuration>[ApplicationPassportFile]0=<?xml%20version="1.0"?><pcmconfig>1=%20%20<application-passport%20type="PCMServer"%20level="OFF"/>2=%20%20<application-passport%20type="PCMMain"%20level="ON"/>3=%20%20<application-passport%20type="PCMModel"%20level="OFF"/>4=</pcmconfig>[NCSConfigFile]0=system_name=PCM_NCS1=instrument_level_threshold=02=agent_port=597183=agent_host=localhost 4=datasending_method=socket

4.3.3.3 Remote Configuration Tool - Web Version

The Web version of the Remote Configuration tool allows you to do the following:

● Retrieve configuration files for local and remote machines.● Publish configuration files to local and remote machines.● Retrieve a System Information report for a local or remote machine.● Use the User Monitor tool functionality to view currently logged on users and log off selected users.● Use the Service Manager tool functionality to stop and start services on local and remote machines.

54 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 55: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.3.3.1 To Access the Web Version of the Remote Configuration Tool

Procedure

1. To open the web version of Remote Configuration, open a browser and enter the URL http://<web server name>/remoteconfiguration.

NoteThe first time that you visit the web site, it may take some time to load. On subsequent visits, the site` should load much more quickly.

2. In the login dialog box, select a server and authentication type (if available), then enter your login credentials and click LoginThe Home page of the Remote Configuration tool appears.

4.3.3.3.2 Remote Configuration Tool: Web Version Interface

When you access the Web version of the Remote Configuration tool, you are presented with the Home page. The Home page includes a large pane which contains the following icons:

Configuration ManagementSystem InformationService ManagerUser Monitor

Click an icon to access a tool, or alternatively, click one of the tabs with the same names that are provided along the top of the screen.

An information panel on the right of the screen displays helpful information relevant to each page.

You can log out of the tool by clicking the Logout command, which is alongside your username in the top left-hand corner of the page header.

4.3.3.3.3 To Retrieve a Configuration File in the Web Version of the Remote Configuration Tool

Context

To retrieve the configuration file for a local or remote machine, proceed as follows:

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 55

Page 56: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Procedure

1. On the Home page, click the Configuration Management icon or the Configuration Management option at the top of the screen.

2. In Configuration Management, enter or select a machine name in the Machine Name list box.3. Enter a port number in the Port box.

The default value is 8000.4. Click Retrieve.

A list of available configurationsis shown in the pane beneath the Port box .5. Select a configuration and click Next.

The selected configuration is displayed.

4.3.3.3.4 Publishing Configuration Files in the Web Version of the Remote Configuration Tool

You can publish a configuration file that you have retrieved to the local machine or to single or multiple remote machines. You need to provide the machine name and port number of the machine you want to publish the file to, or alternatively, you can provide a list of machines in the form of a CSV (comma separated values) file. The CSV file should list the machine names and port numbers in the following format:

<machine name>:<port number>,<machine name>:<port number>

If you do not provide port numbers, the system uses the default port number, 8000.

4.3.3.3.4.1 To Publish a Configuration File in the Web Version of the Remote Configuration Tool

Context

To publish a configuration file to either a single or multiple machines, proceed as follows:

Procedure

1. In the web version of the Remote Configuration tool, follow the steps to retrieve a configuration file.2. When you have retrieved the file, click Next.3. Depending on whether you want to publish the file to a single or multiple machines, perform one of the

following:

○ To publish to a single machine, enter a machine name and a port number and click Add.

56 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 57: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

○ Repeat the step above to specify multiple machines to publish the configuration file to.○ To publish to multiple machines using a CSV file, click Browse. In the Choose File to Upload dialog box,

select the CSV file that lists the machines to which you want to publish and click Upload.

A list of the machine(s) you specified is displayed. Each machine has a check box.4. Select the check box(es) for the machine(s) to which you want to publish the configuration file and click

Finish.To select all the machine at once, select the check box next to the MachineName column heading.The page lists the machine name and the status of the publish.

4.3.3.3.5 Using System Information in the Web Version of the Remote Configuration Tool

In the Web version of the Remote Configuration tool, you can retrieve a System Information report for a local or remote machine. For more information on the System Information tool and the report it produces, see the “Profitability and Cost Management System Information Tool” section in the SAP BusinessObjects Profitability and Cost Management Administrator's Guide.

4.3.3.3.5.1 To Retrieve a System Information Report in the Web Version of the Remote Configuration Tool

Context

To retrieve a System Information report for a local or remote machine, proceed as follows:

Procedure

1. In the Home page of the Remote Configuration tool, click the System Information icon or System Information at the top of the screen.

2. In System Information, enter a machine name in the Machine Name list box and a port number in the Port box.3. Click Retrieve.

The System Information report is displayed.

Results

Retrieving the report can take some time, depending on the network and the configuration of the machine for which you are retrieving the report.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 57

Page 58: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.3.3.6 Using Service Manager in the Web Version of the Remote Configuration Tool

In the Web version of the Remote Configuration tool, you can use the Service Manager tool to stop and start services on local and remote machines. For more information on the Service Manager, see the Controlling Profitability and Cost Management Services section in the SAP BusinessObjects Profitability and Cost Management Administrator's Guide.

4.3.3.3.6.1 To Use Service Manager in the Web Version of the Remote Configuration Tool

Context

To stop and start services on local or remore machines, proceed as follows:

Procedure

1. In the Home page of the Remote Configuration tool, click the Service Manager icon or Service Manager at the top of the screen.

2. In Service Manager, enter a machine name in the Machine Name list box and a port number in the Port box.3. Click Refresh.

The services for the machine are listed. Each service has a check box, and information for each service is provided under the column headings Name, Status, Startup Type, and Log On As.

4. To stop or start a service, select the check box next to the relevant service and click Stop or Start.You can select all the services at once by selecting the check box next to the Name column heading.

4.3.3.3.7 Using User Monitor in the Web Verison of the Remote Configuration Tool.

In the Web version of the Remote Configuration tool, you can use the User Monitor tool to see which users are connected to the application server that you are currently logged in to and to log off users, if necessary.

For more information on the User Monitor tool, see the “User Monitor” section of the SAP BusinessObjects Profitability and Cost Management Administrator's Guide.

58 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 59: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.3.3.7.1 To Use User Monitor in the Web version of the Remote Configuration Tool

Context

To view the users connected to the server you are currently logged in to, proceed as follows:

Procedure

1. In the Home page, click the User Monitor icon or the User Monitor tab.The User Monitor screen displays all users connected to the server machine. Each user has a check box and information for each user is listed under the column headings Username, Client Machine, Logged In Date/Time, Model, Primary Server, and Product.

2. To filter the list of users, select a column heading, for example, UserName, from the Filter Results list, enter the search term in the filter box, and click Apply Filter.The list of users is filtered according to the term you entered.

3. To log off a user, select the relevant check box and click Logout Users. To select all users, click the check box in the table header.

4.3.3.4 Remote Configuration Tool - Windows Version

The Windows version of the Remote Configuration tool allows you to do the following:

● Retrieve and update configuration files for local and remote machines.● Publish configuration files to local and remote machines.● Launch the System Information tool and retrieve a report for a local or remote machine.● Launch and use the User Monitor tool.● Launch and use the Service Manager tool.

4.3.3.4.1 To Access the Windows Version fo the Remote Configuration Tool

Context

To open the Remote Configuration tool, proceed as follows:

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 59

Page 60: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Procedure

1. Select Start Programs SAP BusinessObjects Profitability and Cost Management Tools Remote Configuration

2. In the login dialog box, select a server and authentication type (if available), enter your login credentials, and click OK.

4.3.3.4.2 Remote Configuration Tool: Windows Version Interface

The Remote Configuration interface comprises a large pane in which configuration files and tools are displayed, with a navigation pane on the left in which tools and commands are grouped as follows:

● Configuration Management

- Retrieve Configuration

- Publish Configuration● System Information

- Open Report

- Retrieve Report● Tools

- System Information

- Service Manager

- User Monitor

You can expand and contract items in the navigation pane by clicking the relevant heading. You can also access the tools and commands from the icons in the toolbar and from menus.

4.3.3.4.3 To Retrieve a Configuration File in the Windows Version of the Remote Configuration Tool

Context

In the Remote Configuration Tool, you can retrieve a configuration file for a local or remote machine. To do so, proceed as follows:

60 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 61: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Procedure

1. In Remote Configuration, perform one of the following actions:

○ Click Retrieve Configuration in the navigation pane.

○ Click the Retrieve Configuration File icon - .

○ Select Configuration Management Retrieve Configuration File .2. In the Retrieve the Configurations of a Machine dialog box, enter a machine name in the list and a port number

in the box, and click Search.A list of configurations is displayed in the pane below the port number box.

3. Select a configuration and click Open.

NoteIf you select the current live configuration of the selected machine, you can create a backup of the configuration by clicking Backup. If you choose to open the current live configuration, you are prompted to name and save the configuration file before continuing.

The configuration file for the selected machine is displayed.

4.3.3.4.4 Editing Configuration Files

Once you have retrieved a configuration file, you can edit it and/or publish it to other machines.

You can edit a configuration file in plain text mode - - or you can edit it using the Configure tool - . We recommend using the Configure tool because any text error when editing in plain text mode can result in an invalid configuration.

If you edit with the Configure tool, the tool does not display as a wizard as it does during setup and configuration, but as a dialog box with each screen of the wizard available as a tabbed page. All configuration options are available for editing, for more information on setting configuration options, see the SAP BusinessObjects Profitability and Cost Management Installation Guide.

When you have completed editing the file, save your changes.

4.3.3.4.5 Publishing Configuration Files in the Windows Version of the Remote Configuration Tool

Once you've retrieved a configuration file, the Remote Configuration tool allows you to do the following:

● Publish the configuration to the local machine, by clicking the Apply Configuration to this Machine icon - .● Publish the configuration to remote machines by manually entering the machine names and port numbers.● Save the list of manually entered machine names and port numbers as a CSV (comma separated values) file.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 61

Page 62: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

● Publish the configuration to remote machines by loading a CSV file that lists the machine name and port number in the following format:

<machine name>:<port number>,<machine name>:<port number>

.

4.3.3.4.5.1 To Publish a Configuration File in the Windows Version of the Remote Configuration Tool

Prerequisites

You have retrieved a configuration file and the file is open.

Context

To publish the file, proceed as follows:

Procedure

1. In Remote Configuration, perform one of the following actions:

○ Click Publish Configuration in the navigation pane.

○ Click the Publish Configuration icon - .

○ Select Configuration Management Publish Configuration .2. In the Distribution list dialog box, follow one of these steps to specify machines you want to publish the

configuration to:

○ Enter a machine name and a port number in the Machine Name and Port Number fields. Repeat this step for all machines that you want to publish to.

○ Click Load CSV, and in the Open Machine Name List dialog box, locate and open the CSV file that contains the list of machines that you want to publish the configuration to.

All machines are listed with a check box next to the machine name. If you want to save the list as a CSV file, click Save CSV, and then name and save the file.

3. To select a machine to publish to, select the relevant check box. To select all machines in the list, click Select All.

4. Click PublishThe Distribute New Configuration Process Status dialog box displays the status of the publish. You can save the details of the status as a text report by clicking Save Report and then naming and saving the file.

62 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 63: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.3.4.6 Using System Information in the Windows Version of the Remote Configuration Tool

The Windows version of the Remote Configuration tool allows you to do the following:

Open an existing System Information report for the local machine.Retrieve a System Information report for a remote machine.Launch and use the System Information tool for the local machine.

For more information on the System Information tool, see the “Profitability and Cost Management System Information” section in the SAP BusinessObjects Profitability and Cost Management Administrator's Guide.

4.3.3.4.6.1 To Open a System Information Report in the Windows Version of the Remote Configuration Tool.

Context

To open an existing System Information report for the local machine, proceed as follows:

Procedure

1. In the Remote Configuration tool, perform one of the following actions:

○ Click Open Report in the navigation pane.

○ Click the Open Report icon - .

○ Select System Information Open Local System Information Report2. In the Open PCM System Information Report dialog box, navigate to the report and click Open.

The report is displayed in window with two tabs that provide two different views of the report: Report View and XML View.

4.3.3.4.6.2 To Retrieve a System Information Report in the Windows Version of the Remote Configuration Tool

Context

To retrieve a System Information report for a remote machine, proceed as follows:

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 63

Page 64: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Procedure

1. In Remote Configuration, perform one of the following actions:

○ Click Retrieve Report in the navigation pane.

○ Click the Retrieve a System Information Report icon - .

○ Select System Information Retrieve Remote System Information Report .2. In the Retrieve Remote System Information Report dialog box, enter a machine name and a port number in the

relevant list, and click OK.The report is displayed in window with two tabs that provide two different views of the report: Report View and XML View.

4.3.3.4.6.3 To Launch System Information from the Windows Version of the Remote Configuration Tool

Procedure

To launch the System Information tool, perform one of the following actions:

○ Click System Information in the navigation pane.

○ Click the Launch System Information icon - .

○ Select Tools System Information .

4.3.3.4.7 Using Service Manager in the Windows Version of the Remote Configuration Tool

In the Windows version of the Remote Configuration tool, you can launch the Service Manager tool and use it to control services on the local machine or on remote machines.

For more information on the Service Manager tool, see the “Controlling Profitability and Cost Management Services ” section of the SAP BusinessObjects Profitability and Cost Management Administrator's Guide.

4.3.3.4.7.1 To Launch Service Manager in the Windows Version of the Remote Configuration Tool

Context

To launch the Service Manager tool for a local or remote machine, proceed as follows:

64 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 65: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Procedure

1. In Remote Configuration, perform one of the following actions:

○ Click Service Manager in the navigation pane.

○ Click the Service Manager icon - .

○ Select Tools Service Manager .2. In the Choose Target Machine dialog box, select Local Machine or select Remote Machine and enter a machine

name.The format in which you enter a machine name depends on how your network is setup. You may need to enter a machine name, a fully qualified domain name, or an IP address. Contact your network administrator to determine which format you must use.

3. Click OK.The Service Manager tool appears.

Results

When Service Manager opens in Remote Configuration, the Kill All button is not available. This is to prevent a user inadvertently using the command to stop all services and close off the entire session, which also results in a loss of connectivity for all other users who are using the tool in that session. To prevent loss of connectivity due to a user inadvertently stopping the remote configuration service on a local or remote machine, the remote configuration service - PCMWCFHost - is not listed in the Services tab in Service Manager.

4.3.3.4.8 Using User Monitor in the Windows Version of the Remote Configuration Tool

The Windows version of the Remote Configuration tool allows you to launch the User Monitor tool so that you can view which users are connected to the server you are currently logged in to and to log off users, if required.

For more information on the User Monitor and how to use it, see the User Monitor section of the SAP BusinessObjects Profitability and Cost Management Administrator's Guide.

4.3.3.4.8.1 To Launch User Monitor in the Windows Version of the Remote Configuration Tool

Procedure

To launch the User Monitor tool, perform one of the following actions:

○ Click User Monitor in the navigation panel.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 65

Page 66: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

○ Click the Launch User Monitor icon - .

○ Select Tools User Monitor .

The User Monitor appears.

4.3.3.4.9 Resetting Lists of Machine Names

The Windows version of the Remote Configuration tool retains the most recently used machine names in lists so that you enter machine names quickly and easily. However if you find that the lists become too long or contain machine names that are no longer used, you can reset the lists.

To do this, select Tools Options Reset Recent Machine Names , and the lists return to a blank state.

4.3.4 Registering SAP BusinessObjects Profitability and Cost Management with the SAP System Landscape Directory

If you have an SAP system in place, you can create a snapshot of your existing Profitability and Cost Management system landscape information in the form of an XML file and send it to the SAP System Landscape Directory (SLD) server. This allows the SLD server to analyse your Profitability and Cost Management servers and enables you to track which system components are installed and activated on a given machine.

There are two command line (CLI) utilities called sldreg.exe and SLDDataSetGen.exe that can be run on your application servers to create and transfer an XML file to the SLD server, effectively registering the software with the SLD. These CLI files are run automatically from within the Profitability and Cost Management Configure tool when SLD connection details are entered.

The XML file can be created in either of the following ways:

● Recommended method: In the SLD Connection screen in Profitability and Cost Management Configure. You can enter SLD connection details on this screen and when you click Next, the sldest.cfg connection file is generated. The pcmslddataset.xml is created and sent to the SLD server when you click Finish or Cancel on the Congratulations screen.

● If you experience connectivity issues, you can run the two CLI utilities from the command line with parameters that produce log files for analysis.

4.3.4.1 Configuring SAP System Landscape Directory Settings

Context

In the Profitability and Cost Management Configure tool, the SLD Connection screen enables you to enter SLD connection settings and automatically generate a configuration file with connection parameters. To do this, follow

66 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 67: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

the instructions in the topic “Configuring the Application Server” in the SAP BusinessObjects Profitability and Cost Management Installation Guide.

The information you enter on the SLD Connection screen is used to create the secure SLD connection file: SLDdest.cfg, which contains encrypted authentication information to allow a connection to the SLD server. The landscape information is generated in the form of a pcmslddataset.xml file, and this is sent to the SLD server when either Finish or Cancel is clicked on the subsequent Congratulations screen.

4.3.4.2 Running the SAP Registration Tools Manually

Prerequisites

Before you can run the command-line registration tools manually, you must initially configure the connection settings in the SLD Connection screen in Profitability and Cost Management Configure. This ensures that the SLD Instance Identifier value is written to the registry for the tools to use as part of the connection details.

Context

The following utilities are provided to create and transfer Profitability and Cost Management landscape information to the SLD server:

● sldreg.exe - This is a standard SAP utility that allows you to create the secure connection information file: SLDdest.cfg.

● SLDDataSetGen.exe - This a Profitability and Cost Management utility that generates the Profitability and Cost Management system landscape information, and creates the pcmslddataset.xml file. The sldreg.exe needs to be run again to send the pcmslddataset.xml file to the SLD server, using connection information specified in the sldest.cfg file.

Each utility has a standard help facility that lists valid parameters to run as part of the command. Available parameters are displayed when the command is entered at the command prompt followed by pressing the Enter key.

To run the commands manually on each server:

Procedure

1. Open a command prompt and navigate to the directory where the utilities are located. Usually this is: C:\ProgramData\SAP BusinessObjects\PCM\, but may differ between 32-bit and 64-bit operating systems.

2. Run the command: sldreg -configure [location]\slddest.cfg -user [sld user name] -pass [sld password] -host [sld server hostname] -port [sld server port] and press Enter .The following configuration file is created: slddest.cfg.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 67

Page 68: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

3. Run the command: sldDataSetgen [location]\PCMSldDataSet.xml and press Enter .The file PCMSldDataSet.xml containing landscape information is generated.

4. Run the command: sldreg -connectfile "[location]\slddest.cfg" -file "[location]\PCMSldDataSet.xml" -logfile "[location]\SLDLog.txt"This sends the generated Profitability and Cost Management system landscape information to the specified SLD server. The optional -logfile switch writes all transmitted HTTP requests to a text file for analysis.

4.3.5 Model Administration

Model Administration can only be performed within the Model Builder application by an Administrator or a Model Builder who has been given the appropriate access rights via security descriptors. Administrator users automatically inherit these access rights and can assign them to other users. General model administration tasks such as creating and deleting models are performed through the Model Administration screen.

The Model Administration screen provides access to functionality that enables you to manage models and alter model properties. You will also be able to set the model access for User Groups using the Security tab, and set up Model Partitioning using the Partitioning tab.

NoteWe strongly advise that you keep the number of models on a database to an absolute minimum because each model present on a system (whether enabled or disabled) significantly increases the number of records held in the database. So with each additional model on a database, response times for significant tasks such as calculation and export / import can be detrimentally affected.

Similarly, regular database maintenance must be carried out on your database server to maintain the size of and to optimize performance of database and log files.

Related Information

Modify Model Properties [page 70]

4.3.5.1 Using Model Administration

Only an Administrator has access to the full range of functions in the Model Administration screen, including Administration, Security, and Partitioning. Model Builders may have access to a basic set of model management functions, but this is at the discretion of the Administrator.

The Model Administration screen has three tabs: Administration, Security and Partitioning. A set of model management functions is provided under the Administration tab through buttons displayed along the foot of the screen, which includes:

● Create a New model

68 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 69: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

● Open● Copy● Rename and● Delete a model.

Model maintenance functionality is also provided via the Modify button, which allows you to change the properties of a model properties, such as its description, the model server, and whether or not it is enabled or audited.

The Administration tab displays a list of the models to which you have access. Information on each model is displayed under the following column headings:

Model NameModel DescriptionModel Server - the server the model is assigned toStatus - whether the model is enabled or disabledCreation Date - the date and time a model is created is generated automaticallyAuditing - whether auditing is enabled or disabledModel Type - for example, Profitability and Costing, Bill of Materials, Objectives and Metrics, or Transactional CostingModel State - the operational status of the model; for example, whether the model is Stopped or RunningUsers Connected - the number of users currently connected to the modelModel ID (for more information see “Model ID and Unique Model ID”)Unique Model ID (for more information see “Model ID and Unique Model ID”)

You can configure which columns to display in the Administration tab by right-clicking a column heading and selecting or deselecting the column names in the context menu.

To apply a Model Administration function, select the required model, then either click the appropriate button at the bottom of the screen or select an option from the context menu.

TipTo open a model, you can double-click a specific model name.

Related Information

To Create a New Model [page 71]Copy Model [page 75]Rename Model [page 75]Delete Model [page 76]

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 69

Page 70: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.5.1.1 To Access Model Administration

Context

The Model Administration screen can be accessed only if you are logged into the Model Builder application without a model open. With the appropriate Action Access security privilege, you can achieve this in the following three ways:

Procedure

● Close the model you are in and click the Manage Models toolbar icon .

● Close the model you are in and select Tools Model Admin .● After entering your user name and password to log in, the Model Selection dialog box is displayed, where you

can click Model Admin.The first time you access the software, the list of available models in the Model Administration screen appears blank; otherwise it will show all accessible models.

Results

Any of the above three methods give you access to Model Administration.

Related Information

Model Administration [page 68]

4.3.5.1.2 Modify Model Properties

Clicking the Modify button for a selected model in the Model Administration screen invokes the Model Properties dialog box. The dialog box contains Model Name and New Model Description boxes, as well as a Model Server list. It also has two check boxes: Model Enabled and Audit Model.

NoteWithout the required security privilege within the Model Definition Security Descriptor, this option is not displayed in the Model Administration screen. The Administrator has this privilege by default.

70 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 71: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Related Information

To Access Model Administration [page 70]

4.3.5.1.3 Model ID and Unique Model ID

The Model ID or MID is generated and stored automatically when a model is created. The system allocates the next number available. This number cannot be altered.

The Unique Model ID or UMID defaults to the same value as the Model ID when the model is created. The UMID is stored in the PROPERTY table of the model and does not change when a model is renamed, copied, imported, or exported. If the PROPERTY table for a model is exported and then imported into another model, the UMID in the imported XML overwrites the existing UMID. Otherwise, the UMID of a model does not change unless you change it manually in Manage Properties (see the SAP BusinessObjects Profitability and Cost Management Modeling User Guide) or by using the Console command uniquemodelid (see the SAP BusinessObjects Profitability and Cost Management Console User Guide).

The UMID is used for the Drill-to-Origin command in the grid context menu and when accessing SAP BusinessObjects Financial Information Management from book script.

4.3.5.2 To Create a New Model

Context

In the Model Administration screen, you use the New function to create a new model. This function is available only to users with the required action access security privilege.

Procedure

1. Click New.2. In the Create a new Model dialog box, type a unique model name in the Model Name box.

NoteCertain characters are disallowed in model names because they cause problems in the web aspects of the software.

3. Select a model type from the Model Type list.4. Type a description for the model if required in the New Model Description box.5. If more that one Model Server exists, assign the model to a server in the Model Server list.6. Provided Database Auditing has been enabled during configuration of the software, you also have the option

of recording audit information for this model by selecting the Audit Model check box.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 71

Page 72: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Please refer to your Database User Guide for further information on Database Auditing.

Results

When a new model is created:

● The model's creation date is stored automatically. Models that were created prior to Release 2.5 appear with a default creation date of '01/01/1900'.

● The model's Model ID and Unique Model ID values are generated and stored automatically.

Related Information

Model ID and Unique Model ID [page 71]To Access Model Administration [page 70]

4.3.5.3 Model Development

The most effective way to develop models is to create three separate systems in which you can develop and test model stability before releasing them to Model Builders and End users to access in a production environment.

As an Administrator, you can set up development, test and production systems, each containing a primary application server (with additional secondary application servers), a database server and a web server. Models can be created in the development system, and then promoted to the test and production systems using the existing import and export methods.

4.3.5.3.1 Creating Development, Test and Production Systems

Procedure

1. Create the development, test and production systems.2. Create the appropriate users in each system.

72 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 73: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.3.5.3.2 Overview of Promoting a Model

Procedure

1. The Model Builder creates the model in the development system.2. The Administrator promotes the model to the test system, and eventually to the production system.3. Model Builders and End users can access the models in the production system.

4.3.5.3.2.1 Promoting Models

Models are promoted in one of the following ways:

● Using Model Builder, perform a manual export from one system and manually import the model on to another system. If the target environment includes a number of model servers, then the transported model must be assigned to the required server manually. If a server is not specified, the model is transported by default to the primary server.

NoteIf the model already exists in the destination system, the export ignores the model instead of overwriting it.

● Optionally, in Model Builder, through the Model > Export menu, select the required components to be moved between environments, and create and save an ESP file. Use the file as a parameter in the transportmodel command in the Console or Console Wizard. The transportmodel command is described in detail in the SAP BusinessObjects Profitability and Cost Management Console Guide.

You can choose to export the following model information using an ESP file:

● Model Structure● Data Tables● Security● Results

NoteWe do not recommend exporting results, because they cannot be imported into the destination system. We recommend that only the first three items are exported.

4.3.5.3.2.1.1 Manual Actions for Promoting Models Between Systems

If you are promoting models between systems, the following options may also need to be considered:

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 73

Page 74: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Application Task Description

Console If you have created Console jobs in one system and want to move them in to another system, the jobs are reliant on the model name and user information being the same in each system. To move them on to another system, then copy the Console INI file(s) that you created for each Console job. These files may also contain references to Data Bridge CTF and SPE files that are model-specific.

Data Bridge If you configured Data Bridge external ODBC data sources, then you will have to re-create these definitions in Data Bridge in the system to which you are promoting the model to.

Work Manager If there are existing Work Manager processes, then copy over the Work Manager MWF process files.

Model Builder In Tools Security , manually set up the users in whichever system the model has been copied to.

NoteTo save time in a new system setup you can export the user security information, and then on the destination environment select the affected users and reset the default password. This saves you the task of recreating each user on the destination system. This approach is not recommended in an environment with existing users account because the users have the inconvenience of having to reset the password.

In Tools Security System Properties , set the password controls.

Configure This task is only applicable for new systems: In the Configuration Wizard, navigate to the Multi System Options screen and add the application server that contains the newly copied model to the list of available servers, and then select Allow users to select from the list of available servers.

4.3.5.3.2.2 Access to the Production System by End Users

Prerequisites

● If the environment is new, you need to check the Multi System Options screen in the Configuration Wizard to ensure that the server is available to users.

● Ensure that the security groups and their security definitions are copied over, the users are added into the system and the group membership defined.

● End users need to receive their login name and the default password.

74 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 75: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Context

To access the production environment:

Procedure

1. Log in to the production environment.2. If this is your first time logging in, you enter the default password. At the prompt to change the password,

enter a new password.

4.3.5.4 Copy Model

The Copy function is only available to users with the appropriate action access security privilege. It is located in the Model Administration screen. Selecting the Copy function duplicates the selected model. Without the required security privilege this option is disabled. The name given to the new model must be unique. All the items, values, and Books created in the existing model are reproduced in the duplicate model.

Related Information

To Access Model Administration [page 70]

4.3.5.5 Rename Model

In the Model Administration screen, you can use the Rename function to change the name and description of a model. This function is only available to users with the appropriate action access security privilege.

4.3.5.5.1 To Rename a Model

Context

In the Model Administration screen, you can use the Rename function to change the name or description of a model.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 75

Page 76: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Procedure

1. In the Model Administration screen, select the model you want to rename and click Rename.2. In the Enter New Details dialog box, type a new model name in the New Model Name box.

The new model name must be unique and should avoid certain characters because these can cause problems in web use and when importing with Data Bridge.

TipIf you wish, you can copy and paste some or all of the old model name from the Old Model Name box. This allows you to reuse some or all of the old model name easily, without retyping the name.

3. If required, type a description in the New Model Description box.4. Click OK.

Results

The renamed model displays in the list of models in the Model Administration screen.

Related Information

To Access Model Administration [page 70]

4.3.5.6 Delete Model

In the Model Administration screen, the Delete function is used to delete a model. This function is available only to users with the required action access security privilege. Without the required security privilege this option is not displayed. Administrators and Model Builders have this privilege by default.

NoteTake great care when deleting a model because this operation can not be undone.

Before a model is deleted you are required to confirm the operation. You are also offered the options to delete the audit records or views (grids or layouts) associated with the model. Should you prefer to delete individual layouts at a later date, rather than all at once, you can still delete them from your file store using the Delete option in

Model View Builder Load Layout , or you can delete layouts from the database. Similarly, you can still delete audit records from the database at a later date, if preferred. More information on selective deletion of audit records can be found in the SAP BusinessObjects Profitability and Cost Management Database Administrator's Guide.

76 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 77: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

NoteYou cannot delete a model that another user has currently opened. A message box informs you of this when you click Delete.

Related Information

To Access Model Administration [page 70]

4.3.5.6.1 To Delete a Model

Prerequisites

Be absolutely certain that you want to delete a model. This action cannot be undone.

Procedure

1. In the Administration tab of the Model Administration screen, select the model you want to delete and click Delete.

2. In the confirmation dialog box, indicate whether all audit records or all views (layouts) for the model are to be deleted by selecting or deselecting the relevant check boxes, and then click Yes.The model is deleted and no longer appears in the list in the Administration tab.

4.3.5.7 Change Model Server

This function is available only to users with the appropriate security privilege. To change the Model Server for a model, you click Modify in the Model Administration screen. The Model Properties dialog box displays a list of the available Model Servers on which a model can run. This can be used to organize load spreading by allocating specific models to particular model servers. Because each model must operate through a single model server, use this function only when you have several models in use and wish to separate their model server loadings.

This feature also provides a convenient means for dealing with model servers that break down or require maintenance because it allows processing to be switched to another model server. However, you should not exercise this option on existing models that are in use. You can see which users are using which models through the User Monitor application.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 77

Page 78: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Related Information

To Access Model Administration [page 70]Modify Model Properties [page 70]User Management Tools [page 90]

4.3.5.8 Amend Model Description

A model’s description is displayed against the model on the Administration tab of the Model Administration screen. The Modify function can be used to edit, add, or change the description by accessing the Model Properties dialog box, in which you can add or edit text in the New Model Description box.

Related Information

To Access Model Administration [page 70]Modify Model Properties [page 70]

4.3.5.9 Enable/Disable Model

The Status column of the The Model Administration screen indicates whether a model is enabled or not. A user can open a model only if it is enabled. You can amend the model status by selecting Modify from the Model Administration screen. The Model Properties dialog then displays. If the Model Enabled check box is cleared, the model is disabled and is invisible to users until it is enabled again. This function is only available to users with the appropriate security privilege.

Related Information

To Access Model Administration [page 70]Modify Model Properties [page 70]

4.3.5.10 Audit Model

The Model Administration screen indicates whether auditing is enabled or disabled for a model. You locate the function to turn auditing on or off by selecting the model in the Model Administration screen and clicking Modify. The Model Properties dialog box displays. Provided Database Auditing has been enabled during configuration, you have the option of recording audit information for the model (please refer to your Database User Guide for further

78 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 79: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

information on Database Auditing) by selecting the Audit Model check box. This function is available only to administrators.

Related Information

To Access Model Administration [page 70]Modify Model Properties [page 70]

4.4 Backup and Restore

You need to back up your system landscape regularly to ensure that you can restore and recover it in case of failure.

The backup and restore strategy for your system landscape should not only consider SAP systems but should also be embedded in overall business requirements and incorporate your company's entire process flow.

In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of a data center through fire. It is most important in this context that you ensure that backup devices are not lost together with normal data storage (separation of storage locations).

You can also find more detailed procedures in the “Maintenance” section of the SAP BusinessObjects Database Administrator's Guide.

4.4.1 Archive Procedures for Models

The archiving of data is a task that is performed in conjunction with the Model Builder users. They are aware of which models have data (usually a <Version> and <Period> combination) that require archiving.

Archiving data from a model by <Version> and <Period> is a two-stage process:

1. Perform an export of the required <Versions> and <Periods>2. Remove the exported <Versions> and <Periods> from the model

4.4.1.1 Model Export

The Export Dimensions tab within the Import/Export screen is used to export specific Version and Period combinations. This tab allows you to choose particular Versions and Periods to export, either at a branch or leaf item level.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 79

Page 80: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

TipAlways check with the Model Builder users before removing any Versions or Periods as they may have data that they wish to copy to another area of the model.

NoteIf you have exported this data you can restore it into a new Version or Period in the Data Bridge application.

If the data needs to be restored then the Data Bridge application allows the mapping of data into existing structures, or to create new ones to hold the data.

4.4.1.1.1 Model Archive Automation

Many of the model maintenance tasks can be automated using the PCMCONSOLE utility.

The PCMCONSOLE utility is a suitable tool for automating backup, archive and model maintenance tasks. A sample script that can be used to archive unwanted models is shown in the example below.

Please refer to the document SAP BusinessObjects Profitability and Cost Management Console User Guide for details of how to use this utility, and for a comprehensive list of parameters and some example command lines.

ExampleThe following script can be placed into a batch file, and then referenced from a scheduled task. This script backs up a model called “Model1” to XML format, and then deletes it from the current database:

PCMCONSOLE user=administrator password=administrator export=C:\archivedmodel1.xml delete=model1 log=c:\archive_log.txt

4.4.1.2 Model Copy

The Copy function in the Model Administration screen allows you to duplicate a selected model. All the items, values, and Books created in the existing model are reproduced in the duplicate model, but the name given to the new model must be unique.

You use this method of backup, for example, when you are about to make major changes to a model and you want a copy of the model in its original state.

Related Information

Copy Model [page 75]

80 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 81: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.4.1.2.1 To Copy a Model

Prerequisites

You must have the required action access security privilege to copy a model. Otherwise, this function is disabled in the Model Administration screen.

Procedure

1. In the Administration tab of the Model Administration screen, select the model you want to copy and click Copy.

2. In the Enter New Details dialog box, type a new unique name for the duplicate model in the New Model Name box.You can copy and paste the text in the Old Model Name box, which allows you to use all or part of the original model name without having to retype it.

3. Type a description in the New Model Description box, if required, and then click OK.

Results

The duplicate model is listed in the Model Administration screen.

4.4.2 System Backup Procedures

It is recommended that the SAP BusinessObjects Profitability and Cost Management system is an integral part of your regular backup procedures. The most important component to be included in a backup is the Database server, as this stores the raw source data for the whole system. All other data (such as results) can be re-calculated from the source data.

Once the backups have been performed, ensure that the number and size of the retained files is monitored to ensure that they are not using valuable disk space that may be required by the Application or Database servers.

It is also recommended that the Database Transaction Log is truncated and shrunk on a regular basis to ensure that the data in the database is consistent and current. Often these files can become very large and unmanageable, and it is advisable to include this action as part of the Database backup procedure.

For further information on database maintenance, refer to the SAP BusinessObjects Profitability and Cost Management Database Administrator's Guide.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 81

Page 82: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.4.3 Web Client Data Recovery

To allow end-users to recover Web client data changes in the event of a system crash, a registry key is available to control whether values can be retained locally to still allow updates to the application server.

By default, if the web browser closes unexpectedly during a web session, any changes to model data that have occurred are not saved, and the end-user has to re-enter the data. By distributing a registry key to web client machines, you can control whether data is saved locally or not by changing the value of the key.

4.4.3.1 Enabling Web Client Updates

Context

To enable Web client data values to be persisted locally to allow updates to occur, the following DWORD registry key value must exist in the registry of the web client machine and be set to a non-zero value:

HKEY_CURRENT_USER\Software\Business Objects\Profitability\Web\PersistLocal

We recommend that you use Microsoft Group Policy Editor to distribute this registry setting out to web client machines.

Once the key has a non-zero value, for example; 1, any changes made in web books are saved in to a temporary file. If the web browser session closes unexpectedly, the end-user is presented with the following message:

There are <number> unsaved updates for this model from <data and time>. Do you want to load these now?

If the end-user clicks Yes, the updates are loaded from the temporary file and saved. If the end-user clicks No, the updates are deleted from the file.

4.4.3.2 Disabling Web Client Updates

Context

The ability to save web client data locally is disabled by default because of the absence of the following registry key:

HKEY_CURRENT_USER\Software\Business Objects\Profitability\Web\PersistLocal

If you have distributed the registry key to a Web client and enable updates, and now want to disable updates again, set the registry key value to zero.

82 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 83: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.5 Periodic Tasks

4.5.1 Scheduled Periodic Tasks

The database component of the application architecture is essential to the smooth running of the system as a whole.This section provides some recommendations as to the type and frequency of database maintenance tasks that should be undertaken on the RDBMS that you are using.

Note that these recommendations should not take precedence over the designated DBA tasks that may exist within your organization already - they are merely provided for information if procedures do not exist already.

Table 8: Database maintenance task frequency

Task Recommended Frequency Detailed Description

Full database backup Weekly, or twice weekly during periods of frequent change

To be performed when changes are not being made to the system to ensure in­tegrity

Incremental backup Daily, or twice daily during periods of fre­quent change

Truncate log files Weekly

Re-index tables As required Due to the trade-off between fragmenta­tion of indexes and the loss of query sta­tistics, the user may determine the fre­quency dependant upon an investigation of query performance times.

Shrink database Weekly, or twice weekly during periods of frequent change

This should be performed as part of the full database backup procedure.

4.5.2 Required Manual Periodic Tasks

Although the relational database systems that are supported by the application have robust transactional processes they may become inconsistent if transactions are prevented from completing abruptly and repeatedly. Therefore it is recommended that you perform some database checks on a regular basis, or if you have had to terminate lengthy transactions (e.g. imports and exports) on more than one occasion in a short period of time.

Inconsistencies in the data tables can be investigated by the appropriate database commands. For Microsoft SQL Server, refer to the topic “To check Microsoft SQL Server table structures”.

In an Oracle database, use the ANALYZE command (for further information, consult the relevant databse documenation).

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 83

Page 84: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.5.2.1 To Check Microsoft SQL Server Table Structures

Context

In a Microsoft SQL Server database, to check the table structures:

Procedure

1. Open the Query Analyser application with a new query window.2. Type: DBCC CHECKDB(<database name>)

The query results pane displays a list of the tables checked, and any inconsistencies that have been found. It also attempts to fix minor problems.

4.6 Load Balancing

The system supports parallel processing, which gives you the ability to scale your system processing power and control it more efficiently. It allows your operations to function using a number of parallel processors and a number of hosts and gives you the flexibility to determine how to allocate and use your system resources.

Table 9: Setup and Tools for Logging On and Load Balancing

Scenario Detailed Description Tools to be used

Control allocation of CPU cores. The model server calculation engine and consolidation engine are multi-threaded, and run on multiple CPU cores. The alloca­tion of CPU cores can be controlled by CPU throttling options. Refer to the SAP Busines­sObjects Profitability and Cost Management Modeling User Guide topic “CPU Throttling Options”.

In Model Builder, use the model calculation options:

● Background calculation● Maximum CPU Usage● First CPU Usage

Select different servers for spe­cific models.

Load spreading can be controlled by speci­fying the server for a model to run on. You can change which model server a model runs on or you can choose the model server when opening the model. Refer to the SAP BusinessObjects Profitability and Cost Man­agement Modeling User Guide topics “Modi­fying a model” and “Opening a model”.

In Model Builder, use Model Administration

Modify or use Model Selection

Change Model server .

84 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 85: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Scenario Detailed Description Tools to be used

Choose which landscape to work in.

The system can support multiple Profitability and Cost Management land­scapes; for example a development, produc­tion and system landscape or different land­scapes by geographical location. Users can choose which landscape to log into by se­lecting the appropriate server when logging in. Refer to the SAP BusinessObjects Profita­bility and Cost Management Modeling User Guide topic “Logging into a Profitability and Cost Management Application”.

Use the Model Builder Login dialog to select the required server.

Split a model over multiple serv­ers.

A model can be partitioned across multiple servers in order to use the combined disk space, memory space and processing power of several servers at once. Contact your customer support representative for further advice and see the “Load Balancing wth Model Partioning” section.

In Model Builder Model Administration, use the model partitioning functionality on the Partitioning tab.

4.6.1 Load Balancing with Model Partitioning

This section contains information relating to the operation of Model partitioning in SAP BusinessObjects Profitability and Cost Management. It describes what model partitioning is; discusses the benefits of model partitioning; describes the available methods of partitioning; discusses the type of models best suited to partitioning; and outlines the criteria by which you evaluate partitioning for a model

Model partitioning is a means of distributing the model calculation process and data storage to make the most efficient use of Application server resources.

The application uses a single calculation process for each model. This process uses up to 2GB of logical memory space during the calculation of a model. If additional space is required for the creation and manipulation of results, temporary memory-mapped files are created and stored on the hard drive of the server in the model file directory.

To perform model partitioning, you must be a member of the ADMINISTRATORS user group.

Other restrictions are as follows:

● You can partition models only of the Profitability and Costing type● If you use model partitioning, do not also implement CPU throttling.● Model partitions must be independent of each other.

4.6.1.1 The Benefits of Model Partitioning

To reduce the overhead of swapping data to and from a disk drive, and also to take full advantage of processors available in other model servers (a number of model servers can be deployed in an organization), a model can be partitioned across multiple servers and use the combined disk space, memory space, and processing power of several servers at once.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 85

Page 86: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

A partitioned model can be split across several model servers, but this is not visible to the user of that model. The model appears and reacts in the same way as an unpartitioned model.

A partitioned model that makes efficient use of the available server resources is faster to calculate, and data that is split across the drives of multiple servers reduces reliance on a single data storage area. However, inefficient partitioning - such as when a model contains a large number of dependent values, or when data is accessed over a Wide Area Network - can slow down model calculation. When you assess the need to partition a model, always weigh the benefits against the potential detrimental effects.

4.6.1.2 Considerations for Model Partitioning

Not all models are suitable for partitioning. The topics that follow examine the criteria by which you evaluate how suitable a model is for partitioning.

Areas to examine when you consider partitioning include the following:

● Does the model meet the criteria for partitioning?● Are the data relationships in the model fully understood?● Are there model servers with sufficient unused resources to support a partitioned model?● Is the model stable and unlikely to change?

4.6.1.2.1 Model Partitioning Criteria

It is essential that model partitions are independent of each other. Therefore, criteria for determining whether a model is suitable for partitioning include the following:

● There is a natural split for the business data. For example, each <Responsibility Center> governs its own data, or the business reports every quarter.

● User groups are in close connection to the application hardware. They are on the same network as the servers and are not distributed over a Wide Area Network.

● The model design is stable and unchanging. The model must be fully built and without errors, because it cannot be changed after partitioning.

More specific criteria are the size of the model and the degree of dependency between values. Model that cannot be partitioned include the following:

● Models that contain <Services>● Models that contain <Activity> Re-assignments● Models that contain Cross Model Rules

Partitioning divides each partition into a separate model process. Models containing the elements listed above cannot be partitioned because calculation cannot be performed between model processes.

86 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 87: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.6.1.2.1.1 Model Size

Only Profitability and Costing type models can be partitioned. Of these, large, uncomplicated models are good candidates for partitioning. A large model is any model that causes your servers to work at their optimum levels and beyond. If the server disk drive is low on space after calculating results, you may have a large model.

Indicators that can help you in determing whether a model is large include the following:

● The model directory temporary files take up several gigabytes of space.● The model has many <Versions>, <Periods>, and <Responsibility Centers> combinations. A simple

calculation of the number of elements in each hierarchy gives you an indication as follows:○ If <Versions> x <Periods> x <Responsibility Centers> = less than 2, 500 combinations, SMALL○ If <Versions> x <Periods> x <Responsibility Centers> = up to 20,000 combinations, MEDIUM○ If <Versions> x <Periods> x <Responsibility Centers> = more than 20,000 combinations,

LARGE● All <Activity> Costs are sent to <Cost Objects> dimensions

NoteThese are not strict criteria, and are offered as a guideline only.

4.6.1.2.1.2 Model Dependencies

Determining the degree of complexity and interdependence for a model helps you to evaluate whether a model is suitable for partitioning. A model that is complex, or highly interdependent, is slower to operate if partitioned. There should be no dependencies between partitions.

A model may not be suitable for partioning if it has the following characteristics:

● It is not a Profitability and Costing type model● There are many dependencies between <Versions>, <Periods>, and <Responsibility Centers>.● The model dependencies are at a high level, for example, All/All/All.● The model takes more than four hours to calculate all its results.● You male extensive use of rules in the <Line Item>, <Resource Driver>, <Activity>, or <Worksheet>

dimensions.● Grid built in View Builder that represent the higher levels of your business are slow to display data.● The server CPUs operate at close to 100% continuously during calculation.

A more specific method of working out the inter-relationship of data in a model is to use the Dependency Viewer tool in the Model Builder application.

4.6.1.2.1.3 Model Stability

A model is considered to be stable when it meets the following conditions:

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 87

Page 88: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

● Development is completed, and no more structural changes need to be made.● No critical errors are reported in the Model Alerts screen.

Once a model is stable it can be partitioned, and no further changes must be allowed to the model structure or rules.

4.6.1.2.2 Assessing Model Dependencies

To discover the degree of model value interdependency, use the Dependencies Viewer tool. ( ModelDependencies Viewer .

Changes to values in one dimension cause values that are dependant to be removed from the tempory results store and the various application software caches. The Dependency Viewer displays a list of the types of value affected by change, and the extent of that effect.

For more information on interpreting the analysis provided by the Dependency Viewer, see the SAP BusinessObjects Profitability and Cost Management Modeling User Guide.

4.6.1.2.3 Storing Partitioned Data

Partitioning involves storing your model data in locations other than on a single server. Using the disk drive capacity of other servers provides the following benefits:

● A larger working space for model calculation files● You can store larger models● You can localize the storage and maintenance of data

To partition in this way, configure the model servers as secondary servers using the Configure tool.

Before you can partition data onto networked servers, ensure that the DCOM settings are using an account that has permissions to access data across the network. For more information on configuring DCOM settings see the SAP BusinessObjects Profitability and Cost Management Installation Guide.

NoteOpening a partitioned model takes considerably longer than an unpartitioned model. You may need to consider using a console job to open the model at a quiet time for very large models.

4.6.1.3 Partitioning a Model

Before you start, you must be a member of the Model Administrators security group.

88 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 89: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.6.1.3.1 To Partition a Model

Procedure

1. Log in to Model Builder.2. In the Model Selection screen, instead of opening your model, click Model Admin.3. In the Model Administration screen, select the model that you want to partition and click the Partitioning tab.

The Partitioning tab displays the model name and description in a pane on the left-hand side. Partitioning options and Add, Delete, Move Up, and Move Down commands are available in the right-hand pane.

4. Select one of the following options:○ Open this model only on default server <server name> – This option leaves the model intact as a single

data source.○ Partition this model across several processes/servers – This involves partitioning the model on single or

multiple servers.If you select the second option, the Add command becomes active.

5. Click Add to display the Model Partition screen.

4.6.1.3.2 Opening a Model on a Single Server

The default option is to open a model on a single model server. When the model is opened, a single model file is accessed from a single model directory on the model server.

4.6.1.3.3 To Split a Model into Several Processes

Procedure

1. Select a Version, Period, and Responsibility Center combination.2. Choose to create a partition on the same model server.

A directory is created on the model server for each partition created.

4.6.1.3.4 To Open a Model Across Several Servers

To split a model into several processes across different model servers:

1. Select a Version, Period, and Responsibility Center combination.2. Choose to create a new partition on different model servers.

Each model server creates a directory to store the partition data.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 89

Page 90: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.6.1.3.5 The Model Partition Screen

The Model Partition screen allows you to configure partitioning for a selected model. Lists are available to select the following for a partition:

<Version><Periods><Responsibility Centers>Model ServersPartition Numbers

4.6.1.3.5.1 To Configure the Partition Settings

Procedure

1. Select the Version, Period, and Responsibility Center.Attributes may also be used to partition data.

2. From the Model Server list, select the server that will store the partitioned data.3. From the Partition Number list, choose the partition where you wish to store the data.

The default partition, existing partitions, or new partitions are all valid options. This means that you can choose to keep particular Version, Period, and Responsibility Center data combinations together in the same partition if they contain interdependent data.Once you have selected these options, the model will be partitioned when it is opened using the Model Builder application, or the Console tool.

4.7 User Management Tools

Scenario Detailed Description Tools

Logoff users that are connected to the system for software upgrade or maintenance purposes.

The User Monitor tool enables Administrators to locate which models are in use on the network, and logoff any associated established system user connections. Users can also log themselves out of applications in this tool, but cannot log out other users.

User Monitor

Create new and edit existing users and groups, and apply security access settings in the SAP BusinessObjects Profitability and Cost Management software.

Users, groups and associated security settings are managed in the User and Group Maintenance area of the Model Builder application. More detailed instructions are located in the SAP

Model Builder - User and Group Maintenance

90 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 91: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Scenario Detailed Description Tools

BusinessObjects Profitability and Cost Management Security Guide and the SAP BusinessObjects Profitability and Cost Management Modeling User Guide.

Synchronize SAP BusinessObjects Profitability and Cost Management user accounts with BusinessObjects Enterprise user accounts.

Import and export user accounts between systems in a BusinessObjects Enterprise environment for Single Sign On security authentication. The User Synchronization tool is described in the SAP BusinessObjects Profitability and Cost Management Integration Guide

Model Builder - User Synchronization

Define the type of user authentication that is used to establish user logons.

Configure the type of logon security to be implemented for users of the system. The Single Sign On screen in the Configure tool allows a type of user login to be specified depending on the environment. User login security can be integrated with Windows Active Directory, LDAP security, BusinessObjects Enterpris environments, and so on. Refer to the SAP BusinessObjects Profitability and Cost Management Installation Guide for further details.

SAP BusinessObjects Profitability and Cost Management Configuration Wizard

4.7.1 User Monitor

SAP BusinessObjects Profitability and Cost Management has an additional tool available on the primary server, which can monitor users currently connected to the software. The User Monitor is an administration tool with limited but essential housekeeping functionality.

It displays the users currently logged in, accompanied by useful information regarding user types, the client machine that users are connecting from, the time they logged on, and the model they currently have open. It also allows you to forcibly log off connected users. The logout function also allows users to reuse their login when they have been logged out as the result of a fault; however this does not constitute a forced logout.

When a user is forcibly logged out of the system by an Administrator, a message is displayed to the user as follows:

Your session has been manually terminated by an authorized user. Please contact the System Administrator!

End-users can also log their own session out of a SAP BusinessObjects Profitability and Cost Management application. This is performed in exactly the same way in User Monitor, and only allows the user to log off their own sessions which have the same GUID. Users who are members of the Administrator group can log other users out, whereas non-Administrator users can only log themselves out.

The SAP BusinessObjects Profitability and Cost Management System Information tool also contains the same functions to log users out of the system. This can be found in the Current Users section of the tool.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 91

Page 92: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Related Information

Using the System Information Tool for Troubleshooting [page 100]

4.7.1.1 User Details

In User Monitor, logged in users are displayed in the User Details tab. This displays:

● User Name - as defined in the User and Group Maintenance screen.● User Type - the user group to which the user is assigned to (for example Model Builder, Book Builder, or End

User.● Client Machine - the workstation that the user is connected to as defined in your network.● Primary Server - the server that the client is connected to (this could differ if the Web Server is set up on a

different machine).● Logon Date - the date and time that the user logged on to the system.● Model Name - displays the name of the open model.

Once you launch the User Monitor, click Update to manually refresh the display for the users currently logged in. You can also choose to automatically refresh the screen by selecting Auto Refresh check box, which will display changes immediately, rather than requiring a manual refresh.

It is also possible to filter the list of logins by selecting the Apply Filter check box, selecting the column on which to filter from the Filter Column list and entering a value in the Filter Value box.

Related Information

User Monitor [page 91]

4.7.1.2 Logging off a User

The Logoff command on the User Details tab of the User Monitor is useful in certain circumstances. Although you might not want to log off an actively working user, this function is useful when a user is apparently logged into the server, but has no client application running - for example, if the user has encountered system problems.

The Logoff function cannot terminate user sessions immediately. It invalidates the sessions until such time as the user next makes a request to a service (which can be some time after having been invalidated). During this period the user can continue to interact with the software until they make a new request for data.

The server monitors user activity behind the scenes. Where no activity has occurred for some period of time, it will automatically time out a user session. If the user needs to re-enter the application quickly and cannot wait for this automatic logoff, or some additional factors have contributed towards this system discrepancy, an Administrator can log off a user.

92 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 93: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

NoteYou can also log off users from the primary server in the Configuration Wizard Current Users screen. However, by doing this you are also stopping any processes like current model calculations, imports, and exports. Using the user Monitor utility allows the system administrator to be more selective.

Related Information

User Monitor [page 91]To logoff a User [page 93]

4.7.1.2.1 To logoff a User

Context

You must belong to the ADMINISTRATORS group to log off another User.

NoteLogging out all users allows the services to close, which causes a forced logout for all users. Restarting the Profitability and Cost Management service also causes all users to be logged out.

To log off a user:

Procedure

1. Select the user from the list displayed in the User Details tab.2. Click Logoff.3. Enter a valid administrator user name and password in the Login dialog box and click OK.

The selected user sessions are invalidated.

Results

The user concerned receives a message on their client machine informing them that they are about to be logged out. Changes to Books in the process of being edited may be lost and the book appears to be locked the next time Model Builder or Book Builder is opened. A client application error may occur, but because a user is only likely to be logged off due to database or application server issues, this is of little or no significance.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 93

Page 94: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Related Information

Logging off a User [page 92]

4.7.1.3 License Details

In User Monitor, the License Details tab displays all the license options you have available within the software according to the licenses purchased.

This screen also displays the current number of user types logged onto the system and the total number of licenses available for each of these user types.

Once you have launched the User Monitor, click the Update button to manually refresh the display of the users currently logged in.

NoteSome system-defined Groups have privileges to use other applications without requiring additional licenses, for example, a member of the MODELBUILDERS group can also use the Web Client or Book Viewer. Users logging into an application in this way will be listed in the User Details tab but not in the License Details tab.

Related Information

User Monitor [page 91]

4.8 Language Capabilities

Several additional functions have been provided to support a customized user interface. Because the software has to operate in a multi-national framework, it has been designed to operate in several international languages. When you select your preferred language, all of the application's screen and dialog box text should appear in that language. As your model is constructed, new items can be given names with several selectable alternatives (Aliases) to further support individual language choice.

It is possible to rename dimension items to a preferred alternative for different users using the Data Aliases function. The original name will be retained, but a user may choose to view an item under an alternative alias. An example where this might be useful is for different languages or where certain users may prefer to use codes rather than names.

For more information on Data Aliases, see the SAP BusinessObjects Profitability and Cost Management Modeling User Guide.

94 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 95: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

4.8.1 To Create a Data Alias

Context

Alternative terms are grouped according to a Data Alias which must first be created by an administrator. To create a Data Alias:

Procedure

1. Select Tools Manage Data Aliases .The Manage Data Aliases dialog box displays, showing any predefined aliases, for example DEFAULT ALIAS, CODES, and EPO CODE.

2. Click Add.A new alias is added with the default name Alias1. The name text is editable, so type a new name for the Data Alias if required.

3. Press Enter.You can continue to add any other aliases required by repeating the previous step.The new Data Alias will be displayed in the Available Data Aliases area.

4. Click Close.

Results

The new Data Alias displays in the dimensions Data Aliases pane. The Data Alias is now available for users to select as the Primary Alias.

4.8.2 To Rename a Data Alias

Context

You can rename Data Aliases using Manage Data Aliases.

NoteYou cannot rename the predefined default Aliases.

To rename an Alias:

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 95

Page 96: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Procedure

1. Select Tools Manage Data Aliases .2. Select the Data Alias to be renamed in the Available Data Aliases area.3. Click Rename and then type a new name over the highlighted text of the original name.4. Press Enter.

Results

The new Data Alias name displays in the Data Aliases pane.

4.8.3 To Delete a Data Alias

Context

You can delete Data Aliases using Manage Data Aliases.

NoteYou cannot delete the predefined default Aliases.

To delete an Alias:

Procedure

1. Select Tools Manage Data Aliases .2. Select the required name in the Available Data Aliases area and click Delete.

A message box appears asking you to confirm your selected deletion.3. Click Yes to accept or No to cancel the operation.

4.9 Printing

The following table lists specific areas of the software that can output data to reports and files for printing. Further information is available in the specified relevant documentation.

96 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management

Page 97: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Table 10: Available printing methods

Application Available printing methods Related documentation

Report Manager Print a report from any installed SAP BusinessObjects Profitability and Cost ManagementReport Manager appli­cation to a printer, and create desktop shortcuts to reports.

SAP BusinessObjects Profitability and Cost Management Report Manager User Guide

Create or amend scripts to control the distribution of re­ports.

Produce an Adobe PDF report from a published book (re­quires Adobe Acrobat to be installed).

Model Builder Print model dimension hierarchy structures direct to a printer from the dimension context menu.

SAP BusinessObjects Profitability and Cost Management Modeling User Guide

Export model dimension hierarchy structures to TXT, HTML or RTF files.

The Table Report tab in the Export screen displays all the tables and fields that can be imported and exported to. A print option is available from the context menu.

The Books Manager contains a print preview option to pre­view books before they are distributed to clients, and also contains options to print directly to printer or save books to RTF or PDF.

System Information A summary or detailed report of system information can be created and stored in a TXT or RTF file for reference or printing, or the same information can be printed directly to printer.

The “Profitability and Cost Man­agement System Information Tool” section in this document

Book Viewer or Web client On the web or in the Book Viewer application, an option is provided to generate grid data stored in a book report ob­ject in PDF format.

SAP BusinessObjects Profitability and Cost Management Modeling User Guide

Work Manager Workflow process definitions can be printed directly to printer, and viewed in print preview mode. This is especially useful for analyzing or communicating workflow processes within a business environment.

SAP BusinessObjects Profitability and Cost Management Work Man­ager User Guide

SAP BusinessObjects Profitability and Cost Management Administrator's GuideManagement of SAP BusinessObjects Profitability and Cost Management P U B L I C 97

Page 98: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

5 High Availability

In SAP BusinessObjects Profitability and Cost Management, the following components are potentially a single point of failure:

● Database Server - Access to the database schema is lost if this component becomes unavailable.● Primary Application Server - For information on the effects of the Primary Application Server becoming

unavailable, see “The effects of terminating the system” for PCMServer, PCMMain and PCMModel.● Web Server - Users would lose connection with the model if the web server became unavailable.● Citrix Server - If unavailable, remote users would find the interface inoperable in applications such as Model

Builder.

Table 11: Components with single point of failure

Component Detailed description High Availability Setup Description

Database Server Handles the storage and retrieval of model data, which is passed to the Appli­cation (Model) Server for consolidation or calculation.

High Availability is achieved by installing an additional database server and using the clustering solution provided by Mi­crosoft SQL Server or Oracle, as appro­priate.

Primary Application Server Runs the following services:

● PCMServer - controls the security access of the overall system.

● PCMMain - controls the interaction of model data and model security between the application and the Ap­plication Server. It also houses one of the main caches of data from previously retrieved results.

● PCMModel - provides services re­quired to calculate models.

Clustering is not supported by these services and so High Availability cannot be provided. However, PCMServer stores session information on the data­base, so that the state of logged in users is maintained: in the event of a machine crash, Application Servers can be re­started or switched so that web End Users do not have to re-log in, and they are not aware of the interruption.

Secondary Application Server Runs PCMMain and PCMModel (as for Primary Application Server).

In the event of a machine failure, in an in­stallation with multiple Secondary Appli­cation Servers, it is possible to manually assign an alternative server to a working model. For more information, see “Change Model Server”.

98 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

High Availability

Page 99: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Component Detailed description High Availability Setup Description

Web Server Enables web or intranet users to view and update model data via Books, and to generate reports, via a web browser.

High Availability is provided by using one of the following third party NLB (Network Load Balancing) solutions:

1. Software based NLB: This function­ality is built into the Microsoft Windows Server Operating System providing a low cost solution. A sec­ond network card is installed in each web server creating a private net­work allowing the NLB software to decide which web server will answer a particular request coming from the first network card.

2. Appliance based NLB: This solution uses an NLB box together with addi­tional cabling to physically provide access to multiple web servers. This solution is recommended as being more reliable than the first method.

Citrix Server By supplying greater control and per­formance, the Citrix Server provides full speed access to distant or wireless con­nected users.

Citrix Server is an add on to Microsoft Terminal Server and can be used to bring multiple Terminal Servers together in a Farm, providing a single resource to which users will connect.

Related Information

The Effects of Terminating the System [page 26]Change Model Server [page 77]

SAP BusinessObjects Profitability and Cost Management Administrator's GuideHigh Availability P U B L I C 99

Page 100: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

6 Troubleshooting SAP BusinessObjects Profitability and Cost Management

6.1 Using the System Information Tool for Troubleshooting

Use the System Information tool to create a summary or a detailed report, which you can retain, or which may be requested by Solution Management for troubleshooting configuration and performance issues. Information that can be included in the reports includes the following:

● A summary of the server● Check if system prerequisites are correct● Current users and the models they are logged in to● Settings (including file versions, logs, serial numbers, and DCOM settings)● The status of application services and processes● Information about models (dimension statistics and value combinations)

Related Information

Profitability and Cost Mangement System Information Tool [page 41]Reporting from System Information [page 51]

6.2 Error Codes and Messages

There are various error codes and messages that can appear in different components of the software. You can find all standard error codes listed in this section, with some of the most common error messages. Common errors can be resolved by following the provided guidelines to analyze and debug the issue.

6.2.1 Error Codes

Error codes that may appear in SAP BusinessObjects Profitability and Cost Management are listed below with corresponding error messages:

100 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 101: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Table 12:

Error Code Error Message

0x80004002 Error connecting to PCM server <server_name> - Please check that the PCM server name is correct.

0x800706BA Error connecting to PCM Server <server_name> - Please check that the PCM server name is correct.

0x80880001 Incorrect Support Version

0x80880002 Your session has been manually terminated by an authorized user. Please contact the System Administrator!

0x80880003 Encryption Failed

0x80880004 Unable to login. Invalid username or password.

0x80880005 MsgBox Function not allowed

0x80880006 Model Failed To Open

0x80880007 Unable to login. Incorrect database version.

0x80880008 Model already open

0x80880009 Model already exists

0x8088000A Model Disabled

0x8088000B Name already exists

0x8088000C Security Violation

0x8088000D Unable to Login. Invalid License.

0x8088000E Too Many Users

0x8088000F Unable to login. The user is already logged in.

0x80880010 Unknown Error

0x80880011 Failed to Open Database

0x80880012 Unable to login. The user has insufficient security to run application.

0x80880013 There is an inconsistency within a user defined rule.

0x80880014 The user defined rules are now consistent.

0x80880017 Unable to login. The account is disabled. Please contact the system administrator to re-enable your account

0x80880018 Unable to login. Too many login failures have occurred. The account is now disabled. Please contact the system administrator to re-enable your account

0x80880019 Incorrect server configuration. Please contact your administrator to check the server and client configurations.

0x8088001B Evaluation licence has expired

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 101

Page 102: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Error Code Error Message

0x8088001C Security violation. The database contains unlicensed group assignments. Please ask the system administrator to reduce assignments or purchase further licences

0x8088001E User is already logged on and can't be deleted

0x8088001F Error exporting data to CSV, invalid ANSI character!

0x80880020 Unknown value

0x80880021 General Database Error

0x80880025 Your password has now expired, your account will now be disabled. Please contact your system administrator to re-enable your account.

0x80880026 Your password will expire in <number> day(s), Do you want to change it now?

0x80880027 Your password has expired and must be changed before proceeding.

0x80880028 The new password must be at least 5 characters.

0x80880029 The new passwordyou entered does not meet the requirements defined by your administrator. You must include a non-alpha character such as 012345!$@.

0x8088002A The new password you entered has been used before. Please enter a new password.

0x8088002B Single sign on has failed!

0x8088002C Single sign on has failed, required DLL not found!

0x8088002D Single sign on has failed, invalid DLL!

0x8088002E Single Sign On login has failed (GetUser function has failed). Please contact the system administrator.

0x8088002F Single Sign On login has failed (CheckUser function has failed). Please contact the system administrator.

0x80880031 The xml for the book is too long.

0x80880033 Your SAP BusinessObjects Enterprise user has not been granted access to Profitability and Cost Management. Your SAP BusinessObjects Enterprise account needs to be synchronized with Profitability and Cost Management. Contact your System Administrator.

0x80880035 Incorrect Model type.

0x80880036 Name of ID already exists.

0x80880037 Process Terminated. The SAP BusinessObjects Business Intelligence Client is not present or has not been installed correctly.

102 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 103: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Error Code Error Message

0x80880038 Login Process Terminated. The SAP BusinessObjects Business Intelligence Client is not present or has not been installed correctly on the Profitability and Cost Management Web Server. Please contact your System Administrator.

0x80880039 Login Process Terminated. The SAP BusinessObjects Business Intelligence User Management Client is not present or has not been installed correctly.

0x8088003A SAP BusinessObjects Enterprise Login Process Terminated.

0x8088003B Enterprise Single Sign On cannot be configured for this machine.

0x8088003C Your password has expired, and must be changed now before proceeding.

0x8088003E Access Denied. You cannot log on to an older version of the CMS.

0x80880040 Error creating the SAP BusinessObjects User Management Client (UMC) classes. Please check that the UMC is correctly installed and registered.

0x80890001 Workflow ID is invalid

0x80890002 Client has not Attached to Work Manager

0x80890003 Workflow Type is invalid

0x80890004 Process Definition does not exist.

0x80890005 There is no valid attached session.

0x80890006 The GUI stream read failed.

0x80890007 Invalid Process Definition.

0x80890008 Cannot read variant.

0x80890009 Unexpected variant type.

0x8089000A Attach failed.

0x8089000B Unexpected variant type.

0x8089000C You do not have sufficient access rights.

0x8089000D Unable to perform action, object already locked by <user_name>.

0x8089000E Unable to perform action, no valid version found.

0x8089000F Not all the selected process definitions could be deleted.

0x80890010 Object not locked by user.

0x80890011 Process Definition does not exist.

0x80892001 View could not be added.

0x80892002 Security descriptor not found

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 103

Page 104: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Error Code Error Message

0x8089300C The new BI launch pad objects cannot be created in the CMS. The CMS has not been updated to contain the required Profitability and Cost Management Plug-ins. Contact your administrator to have these plugins added to the CMS.

0x8089300F The Profitability and Cost Management <folder_name> BI launch pad folder cannot be created. A folder of the name <folder_name> already exists in the <folder_name> BI launch pad folder. This folder was not created by Profitability and Cost Management. Please delete the existing <folder_name> folder, rename it or move it to another location.

0x80893010 The <folder_name> BI launch pad folder cannot be created. A folder of the name <folder_name> already exists in BI launch pad. This folder was not created by Profitability and Cost Management. Please delete the existing <folder_name> folder, rename it or move it to another location.

0x80893011 Insufficient Rights to Create SAP BusinessObjects Enterprise User Account

0x80893020 Could not retrieve job id

0x80893021 Could not retrieve export job id. Job <job_id> could not be found

0x80893022 Could not load export definition. Job <job_id> could not be found

0x80893023 Could not retrieve data manager layout

0x80893027 Could not export view. File <file_name> already exists

0x80893028 The edit configuration operation failed. The fail code is: <fail code>

0x80920001 Could not create view.

0x80920009 Could not connect to server.

6.2.2 Common Error Messages

Some of the most common installation and configuration error messages that you may encounter with the application are listed in the following tables:

Table 13: Communication Errors

Error Description

Failed to connect to Primary server, the fol­lowing error occurred. Error 0x800706BA. (800706ba) The RPC server is unavailable.

This error occurs at installation when the client tries to access a server that is unavailable. This can mean that either the server name is incorrect or that the server cannot be accessed.

COM Surrogate errors These errors can occur if the Application Protection option under IIS Default Web Site properties is not set to High (Isolated).

104 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 105: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Error Description

No such interface supported When the application uses the sockets method of communication transport, er­rors can occur if the IP filter settings are too restrictive. This message appears if the server is unable to provide the requested communication. The message can also appear when an application cannot be started, or alternatively it can ap­pear once an application that is unable to carry out an operation has been opened.

Access Violation errors (web client) This type of error can occur when trying to log in as a web client if the web server has not been configured with sufficient security privileges.

Access Violation errors (windows cli­ent)

This error appears for a variety of reasons but is generally caused by the client not establishing a successful connection to the model server.

This error can occur in the following situations:

● After an initial installation● When the application has previously been successfully installed and ac­

cessed

Access Denied This error can occur when you try to access the default web book using the web client. It appears within the details accessed through a yellow warning icon to the bottom left of the Internet Explorer window. This error can be caused by an incorrect web address being used; such as when an IP address is defined with the Web Server configuration screen, but the address used by the web client is a machine name.

Table 14: Configuration Errors

Error Description

Failed to connect to Primary Server, the fol­lowing error occurred. Error 0x80880001. Incorrect Support Version.

This error occurs at installation on a client machine, when a different version of the software is being installed to that installed on the server.

Class Not Registered This error message can appear after logging in to the application. You may be able to see models in the Model Selection screen but they cannot be opened.

Web Page Unavailable If problems tend to occur when lots of users access web pages at the same time, it can be due to problems loading and unloading the required DLL on the web server. This problem can manifest in various ways, but the most common are Web Page Unavailable errors or general locking of the CPU on the web server machine.

Connection closed gracefully This error may appear when trying to log in to the web client and is generally caused by configuration issues.

Table 15: General Errors

Error Description

File Name does not start with %PDF

This error can occur on the Web client when trying to view a PDF file. This is normally due to the anonymous access account in IIS that allows IIS to control passwords.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 105

Page 106: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

6.2.2.1 Resolving Errors

The following sections describe how to resolve the most common communication and configuration related errors.

Incorrect Support Version Error

1. In the Configuration Wizard, click OK to close the error message and then click Cancel on the Test Connection to Primary Server screen.

2. Click Finish.3. Uninstall the product using Add/Remove Programs from Control Panel and then re-install using the correct

version.

The RPC Server is Unavailable Error

1. In the Configuration Wizard, click OK to close the error message and then click Back to return to the Client Setup screen.

2. Check that the server name is correct. If the server name is correct, check that the server is visible within My Network Places in Windows Explorer. If it is not visible, check the server and network connections.

3. Incorrect DCOM configuration may also be a factor. Check that DCOM has been set up successfully on all servers required.

No Such Interface Supported Error

Check the rules that have been defined in Advanced IP Filtering, to ensure that they do not block any IP services from that address.

Class Not Registered

This error can be caused by any one of the scenarios listed below:

● Different versions of the software are installed on the same machine.● A primary server is not installed on the machine, only model servers are present or the primary server is a

different build to secondary servers.● The required application is not installed, but a primary server exists.

106 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 107: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

COM Surrogate Errors

Set the Application Protection option under IIS Default Web Site properties to High (Isolated).

Microsoft Windows Client Access Violation After Initial Installation

1. Check that the Model server is running.2. Check that the DCOM settings have been configured correctly.

The machine that you are attempting to connect from should be included in the DCOM access and launch settings for PCMMain (depending on the application running) and for PCMServer.

This setting can be either individuals or an NT Domain group that has been granted suitable permissions.

Microsoft Windows Client Access Violation on a Pre-established Installation

1. Check if the model server is currently running and available. If the server is not available, then restart the server to allow users to connect.

2. If the server is apparently running successfully and other users can connect, run the SAP BusinessObjects Profitability and Cost Management Configuration Wizard on the affected client machine.

Web Client: Access Violation Error

This error could be caused by one of the following scenarios:

● DCOM Security permissions are set on all servers - When the software components are spread across several servers, DCOM must be configured to allow user access across all these machines. All users within the network domain who wish to access the software, must be added to the DCOM security settings on all the server machines (this can be either individual users or user groups).

● IIS Anonymous User Security - The user defined under Anonymous User authentication security does not have sufficient security privileges. We advise that you choose a user within the network domain who has read and write access on the web server machine. If problems persist, check that this user is set up within the DCOM settings on the other servers with which the web server communicates.

Web Client: Access Denied Error

This error can be caused by an incorrect web address being used; such as when an IP address is defined in the Web Server configuration screen, but the address used by the web client is a machine name. In this instance, enter the alternate address used for the web server to log in to the software.

Alternatively, the error can occur when more than one web server exists on an SAP BusinessObjects Profitability and Cost Management system, but the same IUSR account is used within Microsoft Internet Information Services

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 107

Page 108: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

(IIS). Where several web servers exist, different domain users must be used in IIS to avoid a conflict of access permissions between the web servers.

Web Page Unavailable Error

This error can occur if using IIS as a web server after the software has been installed. Typically, a web user cannot see the software banner page and this standard IIS error is displayed. To solve this problem, perform the following steps:

1. Check that the web files are stored in the default IIS folder (this is often \inetpub\wwwroot\) by using Profitability and Cost Management Configuration Wizard. If a Profitability and Cost Management folder does not exist under this path, then you may need to create a Profitability and Cost Management subfolder in which to store the files.

NoteIf IIS was not installed before the installation of the software, you must create a virtual directory to access the web files created during installation (usually beneath the default root directory) on IIS. To access the IIS configuration program, proceed as follows:

1. Open Control Panel and select Administrative Tools\Internet Services Manager.

2. Select the Default Web Site node and select New Virtual Directory from the right-click context menu.

3. When prompted to supply an alias name for the directory, type EPM.2. If Report server is installed, but a port number is used in the configuration that is currently in use by some

other application, the software web pages may not be accessed. In this case, avoid port 80. Change the port number in the Report Server configuration screen of the Configuration Wizard to a free port to allow web access to books.

Connection Closed Gracefully Message

Check the web server settings are correct as defined in the “To configure a new Web server” section of the SAP BusinessObjects Profitability and Cost Management Installation Guide.

6.3 ActiveX Control Issues

Issues with the ActiveX control can include the following:

● The ActiveX control fails to update to the latest version.● After installation, the EPODataXConnection Control fails to appear in the Downloaded Program Files

folder.● Hidden conflict directions are created.

108 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 109: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

● The following error message displays: Download has failed (the connection was interrupted). Unknown response: 0

● Application exceptions occur.

6.3.1 The ActiveX Control Cannot Update to the Latest Version

The ActiveX Control can fail to update to the latest version if there has been a major change in the version of the software. To resolve the issue, proceed as follows:

1. Open Control Panel Add/Remove programs to check whether a previous remotely deployed installation of the ActiveX control is present on the machine. (Look for SAP BusinessObjects Profitability and Cost Management Web Setup.) If necessary, uninstall any previous version.

2. Ensure that the user has the correct permissions to enable then to download the control automatically. To do this, ensure the application's web site is registered in the Trusted Sites zone, and that the user has permissions to write to their Downloaded Program Files folder.

3. Remove any previous version of the control that exists in the Downloaded Program Files folder. In the folder, the control is named EPODataConnectionControl.

4. Return to the application's web site to obtain the prompt to download the latest version of the ActiveX control.

6.3.1.1 To Check the Version of the ActiveX Control

Context

If you suspect that you have an incorrect version of the ActiveX control, check the version using one of the following methods:

Procedure

1. On the client machine, navigate to C:\Windows\Downloaded Program Files and check the version listed in the Version column of the Explorer window.

2. Open the System Information tool and select Summary in the navigation tree. The Summary tab lists the version of the Web ActiveX.

3. In the INSTALL.LOG file, check the time and date stamp of the PCMDataX.CAB file.

4. Check the Version property of the PCMDataX.CAB file in the source web files folder, for example C:\Program Files\SAP BusinessObjects\PCM\WebFiles.

5. Log in to the application web site and check the version number displayed on the initial login screen.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 109

Page 110: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Related Information

Summary tab [page 44]

6.3.1.2 Removing Previous Installations of the ActiveX Control

One issue related to updating the ActiveX control from one major version of the product to another is that the names of the control and the source folders change between versions. The following table lists the name changes for the ActiveX control and source folders for versions 2.4 to 10.0.

Version ActiveX control filename Default source location

2.4 EPODataX.ocx C:\Program Files\EPO\WebFiles

11.20 EPODataX.ocx C:\Program Files\Business Objects\EPM\WebFiles

11.30 EPMDataX.ocx C:\Program Files\Business Objects\Profitability\WebFiles

7.0 EPMDataX.ocx C:\Program Files\Business Objects\Profitability\WebFiles

7.5 PCMDataX.ocx C:\Program Files\SAP BusinessObjects\PCM\WebFiles

10.0 PCMDataX.ocx C:\Program Files\SAP BusinessObjects\PCM\WebFiles

To resolve issues relating to updating the ActiveX control, we recommend that you remove any trace of the previous version's registered controls and source folders before you deploy the latest version of the ActiveX control. Remove the following folders:

C:\Program Files\Common Files\Business ObjectsC:\Program Files\Common Files\ALG SoftwareC:\Progam Files\Business ObjectsC:\Program Files\EPOC:\<Windows Directory>\Downloaded Program Files - For this directory remove ONLY the EPODataConnection Control component

110 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 111: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

6.3.2 After Installation, the Control Does Not Appear in the Downloaded Program Files Folder

If the EPODataXConnection Control component does not display in the Downloaded Program Files folder after installation, the most likely reason is that the control has been deployed remotely. As a result, the control is registered to another location and was never downloaded to the Downloaded Program Files folder. Open Control Panel Add/Remove Programs to check whether the installation has taken place. Look for SAP BusinessObjects Profitability and Cost Management Web Setup.

6.3.3 Hidden Conflict Directories are Created

If you believe that you have downloaded the ActiveX control, but you cannot find it using Windows Explorer, it can be because the control is in a hidden conflict directory.

If the browser downloads the ActiveX control, but finds that it conflicts with an existing control, the system creates a hidden conflict directory in the Downloaded Program Files folder. The latest ActiveX control is placed in the hidden conflict directory, from which the browser loads the control. This creates a hidden cached control that you cannot view with Windows Explorer.

To find hidden controls, check for [CONFLICT] subdirectories using the command prompt window with, for example, the following command:

C:WINDOWS\Downloaded Program Files> dir /w

6.3.4 Error Message: Download has failed (the connection was interrupted). Unknown Response: 0

If you receive the above error message, the browser request for a connection to the Application server was interrupted and either the connection could not be established or the data could not be retrieved. To resolve the issue, proceed as follows:

● From the client machine, ping the IP address of the Primary Application server to test the connection to the Application server.

● From the client machine, ping the URL of the web server to check the connection to the Web server.● Check the status of the application services to ensure that the model being accessed can be opened and

logged into using the Model Builder application interface. For more information, see the “Services Processes” section.

6.3.5 Application Exception

An application exception can occur if there has been a major change in the version of the software. To resolve this issue, follow the same steps as for an ActiveX control that will not update to the latest version.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 111

Page 112: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Related Information

The ActiveX Control Cannot Update to the Latest Version [page 109]

6.3.6 Cleaning Out the Registry

If all other actions have failed to provide a current working ActiveX component downloaded or installed in the current directory, you can clean out the registry to resolve the issue.

CautionCleaning out the registry is a last resort. We recommend you create a backup of the current registry before making any changes.

To ensure that you do not have conflicts with previous versions of the deployed or installed ActiveX control, unregister the currently installed version. To do this, open the command window, navigate to the Downloaded Program Files directory, and perform the following deregistration commands:

REGSVR32 - u PCMDATAX.OCXREGSVR32 - u EPMDATAX.OCX

These commands remove most of the registry entries. However some entries can remain in the following registry keys and must be removed manually :

● HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\CODE STORE DATABASE\DISTRIBUTION UNITSSearch each entry, using the Contains and then Files keys, for entries relating to either the PCMDataX.ocx file or the EPMDataX.ocx file. Remove the files.

● HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS\CURRENT VERSION\MODULE USAGERemove all keys that reference EPM or PCM files.

6.4 SAP BusinessIntelligence Platform Integration Issues

For information on troubleshooting problems when integrating with SAP BusinessIntelligence platform, see the “Troubleshooting” section of the SAP BusinessObjects Profitability and Cost Management Integration Guide.

6.5 Root Cause Analysis

CA Wily Introscope is an application that is integrated with SAP Solution Manager to collect performance and scoping metrics, and to carry out end to end tracing on installed software components such as SAP BusinessObjects Profitability and Cost Management. To enable the software to communicate with CA Wily Introscope, the SAP Solution Manager Diagnostics (SMD) Agent 7.20 needs to be installed.

112 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 113: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

In Profitability and Cost Management, you can set up different methods to collect metrics for problem solving, and these are:

● End to End Tracing - An End to End Trace Launcher tool is available on client machines. This tool performs passport tracing on client-side components and reports them in CA Wily Introscope for further analysis. This tool uses the settings you configure in the NCS.conf file on the application or web server to route the information.

● Application passport - This method applies an application passport string to software components running on the application server. The application passport strings can then be searched for in CA Wily Introscope to view scoping metrics for these components. The application passport can be switched on or off for each server component in the Profitability and Cost Management Configuration Wizard, and the settings are saved in the application-passport.xml file on the application server. Application passport settings are switched off by default.

NoteYou need to know the application passport string assigned to each server component to search on in CA Wily Introscope. Refer to the “Application Passport Strings for Tracking Events” topic for further information.

● Native Component Supportability (NCS) - This is an SAP utility (installed automatically with the software) that you can configure on the application and web server(s) to produce performance metrics and scoping information in CA Wily Introscope. This is also configured in the Profitability and Cost Management Configuration Wizard and settings are saved in the NCS.conf file. More specifically, this method of tracing produces scoping information for functions, and the level of information is determined by the instrument and calculation level thresholds you configure.

NoteFor this method, you need to know about the different performance counters and instrument and calculation level thresholds that are available. Refer to the “NCS Thresholds and Performance Counters” topic for further information.

Installation and configuration instructions for the SMD Agent, NCS settings, and application passport tracing can be found in the SAP BusinessObjects Profitability and Cost Management Installation Guide. The End to End Trace Launcher tool is installed on client machines by default.

Related Information

Application Passport Strings for Tracking Events [page 116]NCS Thresholds and Performance Counters [page 116]

6.5.1 End to End Trace Launcher and Client-Side Components

The End to End Trace Launcher tool enables passport tracing for Profitability and Cost Management applications using the ncs.conf file on the application or web server to route the client information to CA Wily Introscope.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 113

Page 114: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Usually, the tool is used to try and solve problems that may be occurring for User A, but not for User B, so passport strings are applied to functions that are being called specifically by User A to try and resolve why there is a difference in performance or expected results between the two users.

A sample scenario for using the tool is:

1. A user calls a Solution Manager for help with an issue.2. The Solution Manager instructs the user to open the End to End Trace Launcher and run log and trace query.3. The Solution Manager troubleshoots the issue with user based on trace and log information in CA Wily

Introscope.

Related Information

NCS Thresholds and Performance Counters [page 116]

6.5.1.1 Running the End to End Trace Launcher

Procedure

1. Click Start Programs SAP BusinessObjects Profitability and Cost Management Tools End to End Trace Launcher .

2. In the End to End Trace Launcher panel, select the application you want to launch.The Command Line Argument is provided by the End to End Trace Launcher. You can add additional parameters if necessary. The application that is being launched must be passed the passport=%s parameter, where the %s is later replaced with the passport string. The precise format of the command line argument depends on which application you select in the Select Application to Launch list.

3. Click Copy next to the Passport box.The Passport number is a system-generated number to which all the trace information is associated in the trace requested.

4. Send the Passport number to the Solution Manager.The Solution Manager uses this number when looking up the trace records.

5. Click Launch.The End to End Trace Launcher opens the application you selected. The application functions in the same way; however the End to End Trace Launcher has passed on the extra passport parameter in the command line and the client application then uses this whenever it talks to an application server.

6.5.1.2 When to Use Application Passports With the End to End Trace Launcher

The workings of an application server can be separated into two areas:

114 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 115: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

1. Code that is accessible by making a call to an application server.For example, requesting a list of items in a dimension or requesting for the current value of a cell in a grid. If you need to trace an issue with these sorts of requests, which originate from a client executable, then you can use the End to End Trace Launcher to initiate the trace for a specific client, sending the information to CA Wily Introscope for analysis.

2. Functionality that cannot be accessed by a client request. For example, the PCMModel calculation processes and calculates the results in the background and does this irrespective of any client requests. To perform a trace of what is happening in these areas, enable the application passport, which instructs the application server to forward tracing information to CA Wily Introscope for analysis.

6.5.2 Application Passports

Application passports can be configured during the initial configuration of the application, or at a later date by re-running the Configuration Wizard. When you switch on an application passport for a process, you then need to change the NCS instrument level threshold value to whichever level of scoping information you require from the application server. This is because the default value of the instrument_level_threshold parameter in the ncs.conf file is zero (disabled), so even though application passport tracing is switched on, the scoping information will not be sent to the CA Wily Introscope server unless a valid value is passed into the ncs.conf file.

The following files contain configuration settings for scoping:

● application-passport.xml● ncs.conf

For information on setting up application passport tracing, consult the SAP BusinessObjects Profitability and Cost Management Installation Guide.

Related Information

When to Use Application Passports With the End to End Trace Launcher [page 114]

6.5.2.1 Application Passport Settings

You can configure passport tracing for server components in the application-passport.xml file, located in the appdata configuration folder, which also contains logging configuration settings. The application-passport level is set to whatever was selected when the application was initially configured. By default, the level is set to OFF.

ExampleDefault application-passport.xml file

<?xml version="1.0" encoding="utf-8"?> <pcmconfig> <application-passport type="PCMServer" level="OFF" />

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 115

Page 116: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

<application-passport type="PCMMain" level="OFF" /> <application-passport type="PCMModel" level="OFF" /> <application-passport type="PCMWorkManagerService" level="OFF" /> </pcmconfig>

NoteThe application passport is only checked when the executable starts and is not checked dynamically like the other configuration files.

6.5.2.1.1 Application Passport Strings for Tracking Events

When you analyze the results in CA Wily Introscope, you can use the following predefined application passport strings in filters to track the application passport events:

Table 16:

Component Type Application Passport Search String

PCMServer FD3894724E824B6f87D1014454B3745A*

PCMMain AD23066A22D74CB0BBC5AA9C26878FCC*

PCMModel BF3921F7EAA4455B98A21BA458FF32CA*

PCMWorkManagerService 3BEEBA3DB03E43E48F2A6A9A987EBE13*

NoteThese application passport strings are not used if the server components have been initiated by the End to End Trace Launcher tool on a client machine, because it has separate passport strings that can be filtered on in CA Wily Introscope for analysis.

6.5.3 NCS Thresholds and Performance Counters

The instrumentation_level_threshold section of the ncs.config file, determines which passport threshold to use.

The bit size for instrument_level_threshold is 16 bit, of which the highest 5 bits are used as separate flags and the lower 13 bits are used for the more traditional call level scoping.

Example

system_name=PCM_NCS instrument_level_threshold=4

116 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 117: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

6.5.3.1 Calculating the Instrument Level Threshold

When you want to track calls made from the user interface (also referred to as the call level depth) and you are using all 5 levels; we recommend that you use the following calculation:

255 call level depth OR Version / Period calculation OR RunRule OR Sub rule scoping.

Example255 = FF (in HEXADECIMAL)

FF OR 8000 OR 4000 OR 2000 = 0xE0FF = 57599 (in DECIMAL)

6.5.3.2 Calculation Level Thresholds

The typical calculation level thresholds are:

Table 17:

Threshold types Sample HEX Value Calculated Decimal Value

Count Level 1 - Version over period threads (0x8000) 8000 32768

Count Level 2 - Rules run (0x4000) (See Note) 4000 16384

Count Level 3 - Rule scripts (0x2000) (See Note) 2000 8192

Count Level 4 - Stages (0x1000) 1000 4096

Count Level 5 - Performance counters enabled or processed (0x0800)

0800 2048

NoteCount levels 2 and 3 produce a large quantity of information about start and end timings of rule scripts. Setting the calculation level to these thresholds is designed to identify the rules into which you can add start and end timing VBScript functions.

Switches

Setting switches in the instrumentation_level_threshold allows metrics to be sent to the appropriate category.

Table 18:

Switch Description

0x8000 Switch on scoping timing for Calculation Threads. The switch allows you to see how many calculation threads are being started and their lifespan. Information detailing the Version and Period being calculated is associated with each of the scoped threads.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 117

Page 118: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Switch Description

0x4000 Switch on the scoping of rules. The switch allows you to see which rules are being run and their lifespan. Information detailing the Rule name and type is associated with each of the scoped items.

0x2000 Switch on the scoping calls for rules. The switch allows you to modify your rules to include calls to startTim­ing, appendInfo and endTiming to allow you to identify which areas of a specific rule are taking time.

0x1000 Switch on scoping timing for the various stages of the full calculation. The switch allows you to see how long each of the stages of calculation is taking.

0x0800 Switch on or off the reporting of Performance Counters, such as Data requests, Interface calls, Memory us­age, Import and Calculation Throughput.

TipWhen all bits are switched on, it is very easy to generate millions of performance metrics to be sent to CA Wily Introscope. This can result in a flood of too much information to CA Wily Introscope, which then chooses to report nothing. Unless you have a very small model, we recommend that you do not switch on all the counters at once. Doing this can generate millions of scoping and performance counter records that need to then be analysed by CA Wily Introscope.

If you are having performance problems, start with the Version Period threads, and see if there is a specific period/version combination that is particularly active. Switch this off and enable the stages flag to see which area of the calculation is taking the time. Re-enable the Version Period and Rules to find out which Version Period and Rule are causing the problem. When you have identified the specific rule, you can turn all the options off apart from the rule scripts and add the tracing code the to the rule to identify individual blocks/lines or braches of code that are taking time in the rule.

Threshold levels

You can configure combination calculation level thresholds, however possible combination calculation level thresholds are:

Table 19:

Threshold level HEX Value Decimal Value

Count Level 1 OR Count Level 2 8000 OR 4000 = 0xC000 49152

Count Level 1 OR Count Level 3 8000 OR 2000 = 0xA000 40960

Count Level 1 OR Count Level 2 OR Count Level 3 8000 OR 4000 OR 2000 = 0xE000 57344

Count Level 1 OR Count Level 2 OR Count Level 3 OR Count Level 4

8000 OR 4000 OR 2000 OR 1000 = 0xF000

61440

Count Level 1 OR Count Level 2 OR Count Level 3 OR Count Level 4 OR Count Level 5

8000 OR 4000 OR 2000 OR 1000 OR 0800 = F800

63488

Interface calls OR Count Level 1 OR Count Level 2 OR Count Level 3

255 OR 8000 OR 4000 OR 2000 OR 1000= 0xe0FF

57599

Interface calls OR Count Level 1 OR Count Level 2 OR Count Level 3 OR Count Level 4

255 OR 8000 OR 4000 OR 2000 OR 1000= 0xF0FF

61695

118 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 119: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Threshold level HEX Value Decimal Value

Interface calls OR Count Level 1 OR Count Level 2 OR Count Level 3 OR Count Level 4 OR Count Level 5

FF OR 8000 OR 4000 OR 2000 OR 1000 OR 0800 = F8FF

63743

Exampleinstrument_level_threshold=57599 is 0xE0FF. In other words, 255 call level depth AND Version/Period calculation AND RunRule AND sub rule scoping

instrument_level_threshold=57344 is 0xE000. In other words, Version/Period calculation AND RunRule AND sub rule scoping.

6.5.3.3 Predefined Performance Counters

The following web server performance counters are available via CA Wily Introscope Enterprise Manager:

6.5.3.3.1 Application Server Performance Counters

Interface

Table 20:

Performance Counters Description Component Implementation

Interface | Active calls Increments when a call to the public in­terface occurs, and decrements when the call finishes

PCMSERVER, PCMMAIN, PCMMODEL, PCMWORKMANAGERSERVICE

Interface | Errors Increases when an error occurred in an interface call, as in the case of a unsuc­cessful result passed back

PCMSERVER, PCMMAIN, PCMMODEL, PCMWORKMANAGERSERVICE

Interface | Total calls Increments every time the public inter­face is called

PCMSERVER, PCMMAIN, PCMMODEL, PCMWORKMANAGERSERVICE

Sessions

Table 21:

Performance Counters Description Component Implementation

Sessions | Attached clients Increments every time a client success­fully attaches to the interface, and de­creases when the client is detached

PCMSERVER, PCMMAIN, PCMWORK­MANAGERSERVICE

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 119

Page 120: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Performance Counters Description Component Implementation

Sessions | Invalid Session Request Occurs when a request happens and an invalid session identifier is passed

PCMSERVER, PCMMAIN, PCMWORK­MANAGERSERVICE

Sessions | Logged in Increases when a user logs in, and de­creases when it logs out

PCMSERVER

Sessions | Opened Models Counts the number of models opened across all the model servers in the land­scape.

PCMSERVER

Data

Table 22:

Performance Counters Description Component Implementation

Data | Get Values Request Increments while getting an value PCMMAIN, PCMMODEL

Data | Item Memo Request Increments while getting an item memo PCMMAIN, PCMMODEL

Data | Item Memo Set Request Increments while setting an item memo PCMMAIN, PCMMODEL

Data | Item Name Request Increments while getting an item name PCMMAIN, PCMMODEL

Data | Item Name Set Request Increments while setting an item name PCMMAIN, PCMMODEL

Data | Set Values Request Increments while setting an value PCMMAIN, PCMMODEL

Books

Table 23:

Performance Counters Description Component Implementation

Books | Get Book Definition Increments while retrieving the book contents (published or unpublished)

PCMMAIN

Books | Set Book Definition Increments while setting the book con­tents (published or unpublished)

PCMMAIN

Alerts

Table 24:

Performance Counters Description Component Implementation

Alerts | Calculation Incremented when a calculation alert is raised

PCMSERVER, PCMMAIN, PCMMODEL, PCMWORKMANAGERSERVICE

120 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 121: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Performance Counters Description Component Implementation

Alerts | Critical Incremented when a critical alert is raised

PCMSERVER, PCMMAIN, PCMMODEL, PCMWORKMANAGERSERVICE

Alerts | Information Incremented when an information alert is raised

PCMSERVER, PCMMAIN, PCMMODEL, PCMWORKMANAGERSERVICE

Alerts | Warning Incremented when a warning alert is raised

PCMSERVER, PCMMAIN, PCMMODEL, PCMWORKMANAGERSERVICE

Throughput

Table 25:

Performance Counters Description Component Implementation

Throughput | Calculation Total throughput for the calculation process

PCMMODEL

Throughput | Import Total throughput for an Import process PCMMAIN

6.5.3.3.2 Web Server Performance Counters

Requests

Table 26:

Performance Counters Description Component Implementation

Requests | Bytes Received Counts the total number of bytes sent to the server

PCMIISPLUGIN, PCMWEBSERVICE

Requests | Bytes Sent Counts the total number of bytes sent back in responses from the server

PCMIISPLUGIN, PCMWEBSERVICE

Requests | Error Count Increments whenever an error occurs in the processing of a request, as in the case of authentication errors, invalid re­quests, and general errors

PCMIISPLUGIN, PCMWEBSERVICE

Requests | In Progress Incremented when a request is received by the web server, and decremented when the request has finished

PCMIISPLUGIN, PCMWEBSERVICE

Requests | Total Incremented when a request is received by the server

PCMIISPLUGIN, PCMWEBSERVICE

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 121

Page 122: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Value Requests

Table 27:

Performance Counters Description Component Implementation

Value Requests | Batches In Progress Incremented when a batch of values is requested, for example by a grid or chart, and decremented when the values have been retrieved.

PCMIISPLUGIN, PCMWEBSERVICE

Value Requests | Batches Total Incremented when a batch of values are requested, for example by a grid or chart

PCMIISPLUGIN, PCMWEBSERVICE

Value Requests | Values In Progress Incremented by the number of values re­quested in a batch, and decremented when they are retrieved

PCMIISPLUGIN, PCMWEBSERVICE

Value Requests | Values Total Incremented by the number of values re­quested in a batch

PCMIISPLUGIN, PCMWEBSERVICE

Expand Layouts Requests

Table 28:

Performance Counters Description Component Implementation

Expand Layouts Requests | In Progress Incremented when a request to expand a grid definition is received, and decre­mented when it has finished processing the request

PCMIISPLUGIN, PCMWEBSERVICE

Expand Layouts Requests | Total Incremented when a request to expand a grid definition is received

PCMIISPLUGIN, PCMWEBSERVICE

Remove Zeros

Table 29:

Performance Counters Description Component Implementation

Remove Zeros | In Progress Incremented when a request to remove zeros from a grid is received, and decre­mented when it has finished processing the request

PCMIISPLUGIN, PCMWEBSERVICE

Remove Zeros | Total Incremented when a request to remove zeros from a grid is received

PCMIISPLUGIN, PCMWEBSERVICE

122 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 123: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Schema Requests

Table 30:

Performance Counters Description Component Implementation

Schema Requests | In Progress Incremented when a request for a mod­el's schema is received, and decre­mented when it has finished processing the request

PCMIISPLUGIN, PCMWEBSERVICE

Schema Requests | Total Incremented when a request for a mod­el's schema is received

PCMIISPLUGIN, PCMWEBSERVICE

Book Requests

Table 31:

Performance Counters Description Component Implementation

Book Requests | Book Not Found Incremented if the requested book is not found, as in the case where the book name is incorrect

PCMIISPLUGIN, PCMWEBSERVICE

Book Requests | In Progress Incremented when a book is requested, and decremented when it has finished processing

PCMIISPLUGIN, PCMWEBSERVICE

Book Requests | Needs Regeneration Incremented if the book needs regenera­tion, as in the case where the security has been altered or the book republished

PCMIISPLUGIN, PCMWEBSERVICE

Book Requests | Render in Progress Incremented while a book is in the Ren­der to HTML process, and decremented when that process has finished

PCMIISPLUGIN, PCMWEBSERVICE

Book Requests | Retrieved From Cache HTML

Incremented when a book definition has been retrieved from the cached HTML

PCMIISPLUGIN, PCMWEBSERVICE

Book Requests | Retrieved From Cache XML

Incremented when a book definition has been retrieved from the cached XML

PCMIISPLUGIN, PCMWEBSERVICE

Book Requests | Retrieved From Server Incremented when a book definition has to be retrieved from the application server

PCMIISPLUGIN, PCMWEBSERVICE

Book Requests | Total Incremented when a book is requested PCMIISPLUGIN, PCMWEBSERVICE

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 123

Page 124: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

6.5.3.3.3 PCM Model Performance Counters

Table 32:

Memory Counters Description Component Implementation

Memory | Allocation Errors Incremented if a Major Memory Alloca­tion error has occurred

PCMMODEL

Memory | Allocation Mapping Errors Incremented if a Major Memory Alloca­tion error has occurred when trying to Map Memory

PCMMODEL

Memory | Memory Recycle Count Incremented if the Actual Memory upper threshold has been reached

PCMMODEL

Memory | Memory Files Open Count Current number of opened Memory Files PCMMODEL

Memory | Large Memory Files Allocated Count of Big Memory Files PCMMODEL

Memory | Small Memory Files Allocated Count of Small Memory Objects PCMMODEL

Memory | Current Memory Usage (bytes)

Current size in bytes of Active Mapped Memory

PCMMODEL

Memory | Preferred Maximum Active Memory Threshold (bytes)

Preferred Maximum Active Memory Threshold

PCMMODEL

Memory | Preferred Active Memory Threshold (bytes)

Preferred Active Memory Threshold PCMMODEL

6.5.3.3.4 Work Manager Performance Counters

Table 33:

Performance Counters Description Component Implementation

Work Manager | Email Requests Proc­essed

Number of bulk email requests proc­essed

PCMWORKMANAGERSERVICE

Work Manager | Emails Requests Pend­ing

Number of bulk email requests waiting to be processed

PCMWORKMANAGERSERVICE

Work Manager | Email Errors Number of errors encountered while processing emails. This relates to errors with any SMTP conversations

PCMWORKMANAGERSERVICE

Work Manager | Emails Sent Number of successful email conversa­tions. This relates to the number of SMTP conversations

PCMWORKMANAGERSERVICE

Work Manager | Active Instances Number of active Work Manager instan­ces in the system

PCMWORKMANAGERSERVICE

Work Manager | Console Jobs Started Number of console jobs started PCMWORKMANAGERSERVICE

124 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management

Page 125: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

6.5.4 AppSight Console Support

AppSight Console is a third party solution management software application that allows remote troubleshooting of client machines. If a client experiences operational problems, one of the functions of the software is to record information about running software programs, (including SAP BusinessObjects Profitability and Cost Management programs). This type of remote recording is performed through an AppSight Console server that communicates with AppSight Console client software installed on the remote client machine.

If the AppSight Console server is unable to communicate with the AppSight Console client software, several SAP BusinessObjects Profitability and Cost Management recording files are available for the remote user to run manually under instruction from an SAP Solution Management representative.

The filenames and descriptions are listed in the table below:

Filename Description

C:\Program Files\SAP BusinessObjects\PCM\ITSAM\Appsight\PCMConfigure.rpr

A file that contains a set of recording instructions to record and capture code execution of the PCMConfigure.exe program.

C:\Program Files\SAP BusinessObjects\PCM\ITSAM\Appsight\PCMDatabridge.rpr

A file that contains a set of recording instructions to record and capture code execution of the DBUI.exe program.

C:\Program Files\SAP BusinessObjects\PCM\ITSAM\Appsight\PCMReportManager.rpr

A file that contains a set of recording instructions to record and capture code execution of the RMUI.exe program.

C:\Program Files\SAP BusinessObjects\PCM\ITSAM\Appsight\PCMUI.rpr

A file that contains a set of recording instructions to record and capture code execution of the PCMUI.exe program.

C:\Program Files\SAP BusinessObjects\PCM\ITSAM\Appsight\PCMWorkManager.rpr

A file that contains a set of recording instructions to record and capture code execution of the WMUI.exe program.

SAP BusinessObjects Profitability and Cost Management Administrator's GuideTroubleshooting SAP BusinessObjects Profitability and Cost Management P U B L I C 125

Page 126: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).

126 P U B L I CSAP BusinessObjects Profitability and Cost Management Administrator's Guide

Important Disclaimers and Legal Information

Page 127: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

SAP BusinessObjects Profitability and Cost Management Administrator's GuideImportant Disclaimers and Legal Information P U B L I C 127

Page 128: SAP BusinessObjects Profitability and Cost Management ... · PDF filePUBLIC SAP BusinessObjects Profitability and Cost Management Document Version: 10.0 – 2016-10-06 SAP BusinessObjects

go.sap.com/registration/contact.html

© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.