Administrator's Guide - SAP Business Planning and ...

CUSTOMERSAP Business Planning and Consolidation, version for SAP BW/4HANA, 11.0 SPS032020-03-09

Administrator's Guide - SAP Business Planning and Consolidation, version for SAP BW/4HANA

© 2

019

SAP

SE o

r an

SAP affi

liate

com

pany

. All

right

s re

serv

ed.

THE BEST RUN

Content

1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Monitoring of Planning and Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Setting up a Minimal-Access User to Configure SMD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3 Enabling the Auto-Alert Mechanism in CCMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.4 Availability Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.5 Component-Specific Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.6 Detailed Monitoring and Tools for Problem and Performance Analysis. . . . . . . . . . . . . . . . . . . . . . . . 8

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

2.7 Setting Up SAP Solution Manager as a Central Monitoring System. . . . . . . . . . . . . . . . . . . . . . . . . . 11

3 Management of Planning and Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.1 Backup Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.2 Best Practices for Performance Management (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Processing Tiers (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Writeback Parameters (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13SQE Parameters (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Management of Data Volume (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Data Manager Parameters (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.3 Set Up of BPF E-mail Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.4 Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Logs (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Load Balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.5 Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.6 Scheduled Periodic Tasks for Events and Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 Software Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.2 Transport Management (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Transport Objects (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Transport Configuration (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Transport Execution (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2 C U S T O M E R


Content

Viewing Transport Log Files (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Transport Maintenance (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.3 Transport Management (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Transport Objects (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Transport Configuration (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Transport Execution (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Viewing Transport Log Files (Embedded only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.4 Deployment Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314.5 Development Requests and Development Release Management. . . . . . . . . . . . . . . . . . . . . . . . . . . 324.6 UJA_DATA_CHECKER (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.7 UJA_REFRESH_DIM_CACHE (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.1 Analyzing Problems Using Solution Manager Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.2 Installing Appsight Black Box Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.3 Generating and Analyzing Trace Files Using E2E Trace (Standard only). . . . . . . . . . . . . . . . . . . . . . 345.4 Logging and Tracing Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Logging and Tracing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Client Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.5 Troubleshooting Transport (Standard only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425.6 Component-Level Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445.7 Troubleshooting for Event & Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6 Support Desk Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.1 Remote Support Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.2 Logging Problem Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Administrator's Guide - SAP Business Planning and Consolidation, version for SAP BW/4HANAContent C U S T O M E R 3

1 Getting Started

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

About this Guide

Designing, implementing, and running Planning and Consolidation at peak performance 24 hours a day has never been more vital for your business success than now.

This guide provides a starting point for managing Planning and Consolidation solutions and maintaining and running them optimally. It contains specific information for various tasks and lists the tools that you can use to implement them. This guide also provides references to the documentation required for these tasks, so you will sometimes also need other documentation such as the Master Guide and the application help on SAP Help Portal.

SAP Business Planning and Consolidation 11.1, version for SAP BW/4HANA has two product variations called embedded and standard based on the way your installation is configured. When information in this guide applies to only one of the configuration types, the title of the topic contains an indicator of either Embedded only or Standard only. Topics that contain no indicator in their title apply to both embedded and standard configurations. Also, information within a single topic that differs between the configuration types will be clearly explained within the relevant content.

4 C U S T O M E R


Getting Started

2 Monitoring of Planning and Consolidation

2.1 Introduction

You use the monitoring capabilities of BW/4HANA to monitor Business Planning and Consolidation.

Monitoring is an essential task within the management of SAP solutions.

The aim of this section is to provide information and documentation to monitor the application, for example by utilizing the Computing Center Management System (CCMS).

RecommendationWe recommend that you set up the Technical Operations Manual for SAP NetWeaver available on the SAP Help Portal at help.sap.com SAP NetWeaver <7.5 or 7.4> Technical Operations for SAP NetWeaver

Technical Operations Manual Monitoring .

For more information about monitoring in CCMS, see "Monitoring and Administration Tools for Application Server ABAP” at http://help.sap.com/viewer/e067931e0b0a4b2089f4db327879cd55/7.5.6/en-US/47ce686c5a460a55e10000000a421937.html.

NoteYou must be signed in as an SAP customer or partner to see this topic.

This contains all the information relevant to monitor the BW/4HANA components used in the application.

Proficient knowledge of system monitoring and basic knowledge of SAP NetWeaver and BW/4HANA is required to compose user-defined monitors.

2.2 Setting up a Minimal-Access User to Configure SMD

The SAP Solution Manager and Diagnostic (SMD) tool can be used to provide Web services, such as monitoring, with the Central Computing Management System (CCMS).

The user who performs these monitoring and diagnostic services does not need to be able to manipulate the Business Planning and Consolidation data. Therefore, it may be advisable to create a user with minimal access rights and configure SMD to access Business Planning and Consolidation with this user. The following procedure describes the creation and configuration of such a user.

Administrator's Guide - SAP Business Planning and Consolidation, version for SAP BW/4HANAMonitoring of Planning and Consolidation C U S T O M E R 5

http://help.sap.com

http://help.sap.com/viewer/e067931e0b0a4b2089f4db327879cd55/7.5.6/en-US/47ce686c5a460a55e10000000a421937.html

http://help.sap.com/viewer/e067931e0b0a4b2089f4db327879cd55/7.5.6/en-US/47ce686c5a460a55e10000000a421937.html

Standard Configuration

For a standard configuration of Business Planning and Consolidation, follow these steps:

1. Log on to the EnvironmentShell environment through the Admin client.

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

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

For information about setting up SMD, see Connecting to Solution Manager Diagnostics in the Installation Guide for SAP Business Planning and Consolidation, version for SAP BW/4HANA on the SAP Help Portal.

Embedded Configuration

For an embedded configuration of Business Planning and Consolidation, follow these steps:

1. Enter transaction code SU01 on the Business Warehouse back-end.2. Type the name of the new user and choose Create.3. Enter transaction code PFCG and create a role.4. Add the authorization object RSBPC_ENVM to the role in the role definition.5. Assign the role to the new user.

6. Log on to the Planning and Consolidation web client, navigate to Security Users , and check that the user has no teams or profiles assigned to it. Selecting the user displays details of the team and data access profile assignments for the user.

7. Configure the SMD connection to Business Planning and Consolidation to use this user.For information about setting up SMD, see Connecting to Solution Manager Diagnostics in the Installation Guide for SAP Business Planning and Consolidation, version for SAP BW/4HANA on the SAP Help Portal.

8. After the configuration, starting with SP01, authority object UJ_IDENTI with fields UJ_APPSET = * should be assigned to the user who accesses the SAP BPC system from Solution Manager.

6 C U S T O M E R


Monitoring of Planning and Consolidation

https://help.sap.com/viewer/p/SAP_BPC_VERSION_BW4HANA


2.3 Enabling the Auto-Alert Mechanism in CCMS

The basis for application-specific alert monitoring is CCMS alert monitoring framework.

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

SAP Note Number Title Comment

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

2.4 Availability Monitoring

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

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

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

To configure the GRMG scenario for Business Planning and Consolidation, perform the following steps:

1. Using a suitable XML editor, edit the template customizing file BPCNW_Customizing.xml. You must specify the URL of the scenario (host and port), as well as the username and password.

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

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


http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/617547

2.5 Component-Specific Monitoring

Existing CCMS monitoring sets can be used to monitor various resources, objects, and performance. For example, SAP CCMS monitor template, which can be used to monitor system, database, and background processing for the application server where the application is running.

The following existing monitors within RZ20 can be used by the application to monitor critical conditions:

Database Monitoring

You can monitor the RDBMS connection using the CCMS database monitor. This is the connection to the system where the application is installed and in use.

Operating System Monitoring

Operating system monitoring capabilities within CCMS administration workplace are used to analyze CPU, memory, paging, disks, file system, and their corresponding health statuses.

Dialog Overview

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

Error Monitoring

The log file for SAP Business Planning and Consolidation is monitored for error patterns. The monitor presents its status and alerts according to the presence of error messages in the SAP Business Planning and Consolidation log. If errors occur in this log, you can display them in transaction CCMS by selecting Open Alerts.

2.6 Detailed Monitoring and Tools for Problem and Performance Analysis

2.6.1 Introduction

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

2.6.2 Displaying Statistics of Backend Performance

Use transaction UJSTAT to display statistics of backend performance.

8 C U S T O M E R



2.6.3 Trace and Log Files

2.6.3.1 Introduction

The following table describes the trace and log files for the application components.

2.6.3.2 Logging of Exceptions in the SLG1 System

When an exception occurs, relevant information is logged in the SLG1 system. This allows for improved tracing and diagnosis of any exceptions that occur.

The detailed information is written in the log item and saved in the database. In the log, the object is identified as UJ and the subobject is identified as UJK.

ExampleThe following script refers to an invalid member, A1000:

*XDIM_MEMBERSET ENTITY=A1000

*WHEN TIME

*IS 2017.JAN

*REC(FACTOR=1.2)

*ENDWHEN

This generates an exception and produces the following message in the log:

Member "A1000" does not exist

The following sub-objects are available in the system:

UJ0

UJA

UJB

UJC

UJD

UJE

UJF

UJG

UJH

UJI

UJJ

UJK


UJL

UJN

UJO

UJP

UJQ

UJR

UJT

UJTM

UJT_BACKUP_RESTORE

UJU

UJV

UJW

UJX

UJY

UJZ

UJ_UT

2.6.3.3 Trace File for Debugging Logic

You can turn on tracing for script logic and business rules when you need to troubleshoot a particular script or rule.

We recommend that only experienced Business Planning and Consolidation consultants and support personnel use this. We also recommend that you remove these files periodically since they take up a considerable amount of space.

The activity is recorded in a file called debuglogic.log and stored in <drive>\webfolders\<environment>\<model>\privatepublication\<username>\<date>.

2.6.3.4 Data Manager Log Files

Whenever you use a Data Manager package to move Business Planning and Consolidation data, the system creates a log file.

This file can be useful in troubleshooting the execution of packages. We recommend that you remove these files once the packages have completed since they take up a considerable amount of space.

These logs are stored in <Drive>\webfolders\<environment>\<model>\privatepublication\<username>\tempfiles.

10 C U S T O M E R



The name of the log file contains the following details:

● The name of the package● A timestamp● The extension .LOG

ExampleValidatetransformation20090915211503.log

2.6.4 Workload Monitors

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

Monitor Detailed Description Prerequisites

Workload Monitor — Transaction ST03N

Detailed analysis of workload of application servers

None

2.6.5 Data Growth and Archiving Monitors

Component Monitor Detailed Description Prerequisites

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

Switch the trace on before performing costly operations

2.7 Setting Up SAP Solution Manager as a Central Monitoring System

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

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



3 Management of Planning and Consolidation

3.1 Backup Best Practices

Refer to the following items for information about backing up your Business Planning and Consolidation system:

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

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

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

3.2 Best Practices for Performance Management (Standard only)

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

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

12 C U S T O M E R


Management of Planning and Consolidation

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fsaphelp_nw70%2Fhelpdata%2FEN%2F7c%2Fefa841c1dade34e10000000a1550b0%2Fcontent.htm

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fsaphelp_nw70%2Fhelpdata%2FEN%2F7c%2Fefa841c1dade34e10000000a1550b0%2Fcontent.htm

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsolutionmanagerbp

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwww.sdn.sap.com%2Firj%2Fsdn%2Fgo%2Fportal%2Fprtroot%2Fdocs%2Flibrary%2Fuuid%2F30c221aa-b4e5-2910-b899-d268d84c19c5

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwww.sdn.sap.com%2Firj%2Fsdn%2Fgo%2Fportal%2Fprtroot%2Fdocs%2Flibrary%2Fuuid%2F30c221aa-b4e5-2910-b899-d268d84c19c5

3.2.1 Processing Tiers (Standard only)

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

Tier Description

Database The following processes occur at the database level:

● Data reads● Data write-backs

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

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

data, conversion files, and transformation files)

NetWeaver ABAP Application Server

The following processes occur at the application server level:

● Script logic, calculations, and MDX parsing● Parameter-driven logic● Data Manager loads and ETL (extraction, transform, load)● OLAP engine and calculations

BI Accelerator (an optional component)

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

3.2.2 Writeback Parameters (Standard only)

You can modify writeback parameter values in transaction UJR0.

These values are maintained at the individual model level. In general, you will not need to change the default values.

Parameter Default Description

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

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

Administrator's Guide - SAP Business Planning and Consolidation, version for SAP BW/4HANAManagement of Planning and Consolidation C U S T O M E R 13


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

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

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

3.2.3 SQE Parameters (Standard only)

You can modify the SQE parameter SPARSITY_COEF in transaction UJQ0.

This value is maintained at the individual model level, but in general, making changes is not necessary.


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

3.2.4 Management of Data Volume (Standard only)

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

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

14 C U S T O M E R




3.2.5 Data Manager Parameters (Standard only)Refer to the sections in this topic for improving system performance when exporting packages with the YTD, QTD, or PERIODIC options or when loading transaction data into the system when the data volume is larger than the package size defined in Data Manager Process Chain.

Exporting packages with YTD, QTD, or PERIODIC options

When running a Data Manager export package with the YTD, QTD, or PERIODIC option and you have parent members in the selection (for example, <ALL> is selected for one or more dimensions), you may encounter a system memory issue. This may occur because the MDX query takes into account parent members for data generation.

ExampleIn the Business Planning and Consolidation model, there are 5 dimensions, which have a hierarchy depth of h1, h2, h3, h4, and h5 respectively and <ALL> is selected for these dimensions during the export. One single record on the base member now generates N = h1*h2*h3*h4*h5 records. Assume there are M records stored in the DataStore Object (advanced) according to the selection, thus M*N records would be queried. In a business scenario, usually there are more than 10 dimensions in the DataStore Object (advanced), which results a very large value of N.

To avoid this issue, consider performing the following steps:

1. If it is not necessary to export 'YTD', 'QTD', or 'PERIODIC' data, use the 'SIGNEDDATA' option when running the package. This option runs an RSDRI query and the memory consumption is dramatically less.

2. If the SIGNEDDATA option does not meet your requirements, make sure there are no parent members for the dimensions that you set in the selection. This can be achieved by using the filter function in the Data Manager member selector with the filter condition CALC=N.

3. If choosing parent members is unavoidable, there is a parameter value in the DM dynamic script that can be adjusted so that the selection is split by Data Manager. Follow these steps:

1. Click More Organize Package List in the Data Manager interface.2. Select the export package you use and click Modify.3. Click View Package in the dialog.4. In the dynamic script editor dialog, find the INFO node and the parameter %DIMVALUE%, whose default

value is E=24.5. Change the parameter value by following these steps:

1. Set the value in the form [Dimension type]=value; different pairs should be separated by a semicolon.

2. The dimension type can be all the delivered dimension types in the system: A for Account, C for Category, D for Datasrc, E for Entity, I for Intercompany, R for Currency, and T for Time.

3. Generally, set the dimension that has more members in the selection for splitting.

ExampleThere are 5 dimensions in the DataStore Object (advanced): Account (500 members), DataSrc (20 members), Category (3 members), Entity (600 members), and Time (150 members). You select <ALL> for all dimensions except for Time where you specify a fixed value. The suggested parameter value can thus be A=1;E=1 since these two dimensions have the most dimensions in the selection. For example, INFO(%DIMVALUE%,A=1;E=1). Note that this solution will generate more MDX statements to query data and therefore performance is not expected to be as high as normal.


When data volume is larger than the package size defined in Data Manager Process Chain

When loading transaction data into the system with the option Run default logic checked, the result of the logic calculation may be incorrect if the data volume is larger than the package size defined in Data Manager Process Chain.

Data Manager and script logic process data in different ways: Data Manager processes data in packages while script logic does not. If the total amount of data to load is larger than the package size defined, Data Manager will process the data in several rounds, and each time it loads the data and the default logic is invoked. When the script logic is executed for the subsequent packages of data, it will query data according to the selections and this is very likely to get data that has already been processed in previous rounds. This leads to the new result overwriting the original result.

To avoid issues, follow one of these solutions:

● Adjust the package size of the Data Manager Process Chain to a value that is larger than the total amount of data records.1. Run transaction RSPC, and double-click the process chain that is used for loading data. Then, double-

click the process variant Convert.

2. Click Display Change and set the value of SPACKAGE_SIZE to a value larger than the total number of data records to be loaded.

3. Click Save.

CautionThis may lead to a memory issue if the loaded data amount is extremely large. In this case, use one of other two solutions below.

● Load the transaction data without selecting the option Run default logic option, and later run the default logic separately after the data is loaded.

● Change the script to force the members to be calculated each time the script logic is called. As an example, if the problem lies in the ACCOUNT dimension, you can use the statement below to force the system to select the members in ACCOUNT for calculation.*XDIM_MEMBERSET GRPACCOUNT=BAS(TOTAL_ACCOUNT)

CautionThis option may slow system performance.

For more details on the information presented above, see the following table:

Parameter Where Used SAP Note

DIMVALUE Exporting package 1685951

SPACKAGE_SIZE Importing packages 1636487

16 C U S T O M E R





3.3 Set Up of BPF E-mail Notifications

For instructions on setting up e-mail notifications sent by business process flows, see the topic “Setup of E-mail Notifications” in the Business Planning and Consolidation application help available at https://help.sap.com/viewer/p/SAP_BPC_VERSION_BW4HANA.

3.4 Administration Tools

3.4.1 Logs (Standard only)

The application writes logs during various activities at runtime. These can be used by administrators for auditing and monitoring purposes.

Application Log

Every operation and corresponding steps carried out during that operation are recorded in the application log:

Transaction SLG1, log objects: /POA/PST and /POA/UM

The application log includes detailed information about error messages and sequential flow with respect to technical processing in the application.

This object includes the subobjects PACKAGE. Use this subobject to monitor and analyze the logs that are specific to application packages for /POA/PST with value AUTH, OTHER, REST and for /POA/UM with value OTHER, REST.

3.4.2 Load Balancing

As a web-based application, the basis for logon and load balancing is a high availability landscape setup together with a load balanced network setup.

For more information about network load balancing, see the Technical Infrastructure Guide for SAP NetWeaver on SAP Service Marketplace at http://service.sap.com/instguides .

A load-balanced network using SAP Web Dispatcher together with logon groups in the BW/4HANA systems can be used to redirect certain users to specific application servers.




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguides

3.4.3 User Management

All scenarios and components in the application use the user management functions provided by NetWeaver.

For more information about user administration and authentication, see the application security guide on SAP Service Marketplace at http://service.sap.com/securityguide .

3.5 Backup and Restore

The following table describes methods for backup and restore for application components:

Categories of System Components

Category Properties Suggested Methods for Backup and Restore

Examples

VIII Original application data, standalone system based on ABAP Application Server

Data:

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

● Backup of software, configuration log files

Standalone SAP ERP

3.6 Scheduled Periodic Tasks for Events and Notifications

Program Name/Task Task Scheduling Tool Recommended Frequency Detailed Description

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

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

Reorganize and reconciliation job

ABAP Monthly or greater Reconciliation of deleted messages in Business Workplace and event and notifica-tion.

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

18 C U S T O M E R



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsecurityguide

4 Software Change Management

4.1 Introduction

Software Change Management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms.

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

4.2 Transport Management (Standard only)

Transports allow you to move an environment across a landscape. For example, you can transport an environment from a development system to a test system and then to a production system.

Two modes of transport are supported:

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

● Deletion mode – For deleting objects. In this mode, you explicitly specify the objects to delete.

You can transport the changes associated with an environment without having to transport the entire environment. You can transport one or more models at a time, and select individual components of a model, for example, dimensions, members, logic script files, work status, reports, and so on). You can transport the deletion of models, dimensions, Data Manager packages (deletion includes renaming, moving and deleting a package), Data Manager package groups (deletion includes renaming and deleting a package group) and Data Manager package links.

You can also collect BW/4HANA objects into a transport request, such as BW/4HANA process chains. To move process chains into your production environment, use the SAP NetWeaver transport process for process chains. The process chain must be assigned to component /cpmb/BPC.

The following subsections contain a description of the transport process and some other useful information about transporting. If you have problems with transports, see Troubleshooting Transport (Standard only) [page 42].

4.2.1 Transport Objects (Standard only)

This section lists the objects that you can transport for environments and models.

Environment Objects

Administrator's Guide - SAP Business Planning and Consolidation, version for SAP BW/4HANASoftware Change Management C U S T O M E R 19

You can transport the following objects for an environment:

● Business Rule● Configuration● Dimension● Model● Script Logic● Task Profile

Model Objects

You can transport the following objects for a model:

● Books Template● Business Process Flow Template● Business Rule● Business Unit● Configuration● Control● Data Access Profile● Data Manager Conversion File● Data Manager Data File● Data Manager Package● Data Manager Package Group● Data Manager Package Link● Data Manager Transformation File● Dimension● Dimension Master Data● Drill Through● Journal Template● Report File● Report Templates● Script Logic● Task Profile● Team● Web Documents● Work Status Settings

4.2.2 Transport Configuration (Standard only)

Use

Before you can transport, you must first configure the BW/4HANA transport framework, which is the same as the NetWeaver transport framework.

20 C U S T O M E R


Software Change Management

Prerequisites

You are the BW/4HANA administrator.

Procedure

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

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

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

3. Select the objects to transport.For information about transport objects, see Transport Objects (Standard only) [page 19].

4.2.3 Transport Execution (Standard only)

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

4.2.3.1 Transporting Environments (Standard only)

Use

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

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


http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com



Procedure

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

1. In the left column, select SAP Transport Object Types .

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

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

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

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

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

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

Transport Errors

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

4.2.3.2 Deleting Objects by Transport (Standard only)

Use

After an object has been deleted in the source system, you can mark it for deletion in the target system. You can select the deleted objects to transport. However, you can select only deleted objects for which there are no dependencies.

The following objects support transport deletion:

● Models● Dimensions● Data Manager packages● Data Manager package groups

22 C U S T O M E R



● Data Manager package links

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

Procedure

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


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

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

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

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

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

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

Deletion Errors

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

4.2.4 Viewing Transport Log Files (Standard only)

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



Procedure

To view a transport log file:

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

4.2.5 Transport Maintenance (Standard only)

Use

There are certain maintenance tasks involved with transports.

Features

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

4.3 Transport Management (Embedded only)

Transports allow you to move an environment across a landscape. For example, you can transport an environment from a development system to a test system and then to a production system.

Same as in the standard configuration, two modes of transport are supported in an embedded configuration:

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

● Deletion mode – For deleting objects. In this mode, you create a request to record the objects you deleted in source system and release the request to transport the deletion to target system.

The following subsections contain a description of the transport process in an embedded configuration and some other useful information about transporting. If you have problems with transports, you can find SAP notes under the application area EPM-BPC-BW4-INS-TRA with helpful information.

4.3.1 Transport Objects (Embedded only)

An embedded configuration of Business Planning and Consolidation supports collective transport by adopting Business Warehouse transport framework. Currently you can choose one or more of the following objects and include them in one transport request for export:

24 C U S T O M E R




● Environment● Model● BPF template● Team● Data access profile● Business rule● Task sequence● Control rules● Control sets and assignments● Journal template

In the embedded configuration, an environment is transported along with related parameters; a model is transported along with its work status settings, system report settings, control context , comments and business rule types enabled for each model.

Object Dependency

You can transport objects with or without corresponding objects they depend on . However, if you transport an object and do not include the objects it depends on in the transport, an error may occur. Dependencies between the objects are as follows:

Objects (TLOGO) Depends on (TLOGO) Referenced by

Environment (ENVM)

Model (MODL) ENVM, ALVL, ADSO, HCPR

Business Process Flow Templates (BBPF)

ENVM /

Data Access Profile (BDAP) ENVM TEAM

Methods and Multipliers (CEBR) ENVM

Business rules for models (CMBR) ENVM, MODL

Task sequence (CMBT) ENVM, MODL CMBR, CTCR

Control rules (CTCR) ENVM, MODL

Control sets/control assignments (CTCS)

ENVM, MODL CTCR

Journal templates (JRNL) ENVM, MODL


RecommendationIf you perform a transport for the first time, we recommend you include all objects in one request and transport them together. Later, if you made changes to an object that has a lot of dependencies such as an environment, you should transport this object first before transporting any objects that depend on it.

Component of Objects

For each object, you can select individual components of the object to transport without having to transport the entire object and all its components.

An environment contains the following components:

● Model● Team● BPF templates● Business rule methods● Business rule multipliers

A model contains the following components:

● Basic InfoProviders● All the related objects (defined by standard Business Warehouse) of this basic InfoProvider● Business rules (carry forward, account-based calculation, currency translation, elimination and

adjustment, IC booking and US Elimination)● Control rules● Control sets and control assignments● Journal template

NoteBoth valid and invalid models can be transported. The transport of a control set automatically includes all control assignments created for the control set.

For detailed steps about how to select individual components and include them in a request, refer to Transport Execution (Embedded only) [page 28]

4.3.2 Transport Configuration (Embedded only)

Before you can transport, you must first configure the BW/4HANA transport framework.

Prerequisites

You are the BW/4HANA administrator.

26 C U S T O M E R



Context

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

Procedure

1. Configure the transport framework by creating transport domains, routes, and other aspects of a transport. For information, see Change and Transport System in the SAP NetWeaver Application Help on the SAP Help Portal at help.sap.com.

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

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

3. Select the objects to transport. For more information, see Transport Objects (Embedded only) [page 24].


http://help.sap.com

http://help.sap.com

http://help.sap.com

4.3.3 Transport Execution (Embedded only)

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

4.3.3.1 Creating or Modifying Objects by Transport (Embedded only)

In this topic, we take the object environment as an example. You select the objects to transport from the hierarchy of objects in the environment. This allows for the granular selection of objects. Only the objects that you select are transported.

Context

RecommendationWe recommend that you do not add a normal transport and a deletion transport for the same environment into a single customizing request.

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

Procedure

1. Log on to the source system and enter transaction code RSA1.

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


2. In the middle column, select Planning BPC Embedded Environment .3. Double-click Select Objects.4. In the dialog box, select the environment to be transported and click Transfer Selections.5. In the right column, the objects in the environment are listed. If the objects are not listed, right-click

the environment and choose Add Optional Objects. Select the objects to be transported by selecting or deselecting corresponding objects.

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

Continue button.

28 C U S T O M E R



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

the request.5. Go to transaction code SE38 and enter RSTRANSCHECK to check quality of the objects to be

transported.6. Enter transaction code SE09 to open the transport organizer. Click Display.

5. Release the customizing task by selecting the task under the customizing request you just generated, then click Release directly.

6. After successfully releasing the task, install the objects in the target system if you transport D-version instead of A-version objects:1. Enter transaction code RSA1 in the target system.2. In the left column, select BI Content, then click Object Types.3. Click Object Type.

4. Select Planning BPC Embedded Model Select Objects .5. Choose your model, then click Install.

4.3.3.2 Deleting Objects by Transport (Embedded only)

Context

After an object has been deleted in the source system, you can mark it for deletion in the target system.

The following objects support transport deletion:

● Environment● Model● BPF template● Team● Data access profile● Business rule● Task sequence● Control rules● Control sets and assignments● Journal template

RecommendationWe recommend that you do not add a normal transport and a deletion transport for the same environment into a single request.

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


Procedure

1. Generate a workbench request:1. Enter transaction code se09.2. Choose Create (F6) and select Workbench Request.3. Enter a description for your request and create a transport request where your deletion changes can

be included.4. Go to transaction code se16.5. Enter the table name RSBPC0_TR_DELETE and choose Create Entries.6. Enter the name of the new request. Then the request will be ready for recording all the deletion

operations.7. Delete one or more objects in the front-end of the source system. Your delete operation are recorded in

this transport request.8. Go to transaction code SE38 and enter RSTRANSCHECK to check quality of the objects to be

transported.2. Release the workbench task:

1. Enter transaction code SE09 to open the transport organizer, then click Display.2. Select the task under the workbench request you generated by performing the steps above.3. Choose Release. Deletion of the objects will be transported to the target system.

4.3.4 Viewing Transport Log Files (Embedded only)

After a transport has been completed, you can view the transport log.

Context

The log reports the successful completion of a transport request as well as any warnings and errors encountered during the transport.

Procedure

1. Enter transaction code SE09 to open the transport organizer, then click Display.

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

30 C U S T O M E R



4.4 Deployment Scenarios

There are two typical landscape deployment scenarios.

Development to Production

In the Development to Production deployment scenario, you create and maintain an environment in development. All dimensions, dimension properties, and models are created in development. A decision needs to be made for all other objects.

Typically, all objects are created in development and transported to production. The exceptions include security and teams, which typically are handled landscape by landscape.

Production Only (with Development for patch testing)

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

Best Practices for Ongoing Development

Some customers have release cycles in which they are unable to transport an entire environment. For example, they may have a configuration that has Production support changes and another configuration on the same model or environment that is transported at a later stage in the project cycle.

In this case, you should have two environments in development: one for new development, and one for production support changes. When a production support change occurs, this should be done in both environments in development. When the cutover of new development needs to be transported, then the configuration can be moved to the production support environment and transported.


4.5 Development Requests and Development Release Management

Use

4.6 UJA_DATA_CHECKER (Standard only)

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

4.7 UJA_REFRESH_DIM_CACHE (Standard only)

Use the program UJA_REFRESH_DIM_CACHE to sync the dynamic dimension table and BW dimension table. This clears the cache, but does not delete dimension members and transaction data.

To run UJA_REFRESH_DIM_CACHE, log onto the BW server, go to transaction code SE38, then execute UJA_REFRESH_DIM_CACHE.

32 C U S T O M E R



5 Troubleshooting

5.1 Analyzing Problems Using Solution Manager Diagnostics

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

5.2 Installing Appsight Black Box Service

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

what application is needed to be monitored.○ Triserv2.rpr

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

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

4. Install AppSight Black Box Service in standalone mode.1. Run AppSight Black Box Service.exe.2. Select Install.3. Accept the agreement and choose Next.4. Enter any information for username and company name and choose Next.5. Leave the server prompt blank for standalone mode and choose Next.6. Leave Black Box with no license option and choose Finish.

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

6. Run startservice.bat to begin logging.

Once you start the application, the Identity folder contains an .ASLfile, which is the log that will write all the information from the application. The computer name and date are used as a variable for the naming convention.

The log stays at 0 bytes until the service is stopped and only then is its actual size shown.

Administrator's Guide - SAP Business Planning and Consolidation, version for SAP BW/4HANATroubleshooting C U S T O M E R 33


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

5.3 Generating and Analyzing Trace Files Using E2E Trace (Standard only)

Use

You can generate trace files on client and server components for troubleshooting purposes using E2E Trace. Trace files collect information about client and server interactions presenting trace information about the entire request and response of a business process step. The trace files then upload to the server for analysis in SAP Solution Manager Diagnostics (SMD). Client side and server side trace information is displayed in the E2E Trace application in SMD.

E2E Trace is delivered and installed with Business Planning and Consolidation. To configure and activate tracing on a client machine, see Logging and Tracing Configuration [page 36].

After enabling and running tracing, you can obtain information about evaluating the results of the trace in the Diagnostics section of the E2E Trace Analysis - User Guide on SAP Help Portal.

Prerequisites

● Ensure that the latest Business Planning and Consolidation Clients with the E2E Trace plug-in are installed on your client machine.

● The minimum release on the SAP Solution Manager Diagnostics side for E2E Trace Analysis is Solution Manager 7.0 EhP 1 SP23.

Procedure

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

● Enable tracing in the ABAP back-end system● Perform a trace in the Administration module● Perform a trace in the Microsoft Excel module● Manually upload the trace file to SMD if not done automatically● Evaluate the trace file in SAP Solution Manager

34 C U S T O M E R


Troubleshooting

Enable Tracing in the ABAP Back-end System

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

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

Perform a Trace of the Microsoft Excel Module

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

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

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

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

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

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

Manually Upload the Trace File

If you need to manually upload a trace file to SMD, perform these steps:

1. On the client machine on which you recorded the trace, expand the Manually upload section.2. Choose Browse under Upload BusinessTransaction.xml. The file to upload appears in <trace plug-in

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

Evaluation of Traces in SAP Solution Manager

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

collection dynamically.

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


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

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

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

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

Trace Summary.

More Information

● Logging and Tracing Configuration [page 36]● Log and Trace File Management (in the application help in the SAP Library at http://help.sap.com )

5.4 Logging and Tracing Configuration

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

You can create log and trace files for the client.

5.4.1 Logging and Tracing Parameters

Use

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

Features

Statements in the Log Configuration File

36 C U S T O M E R


Troubleshooting


As delivered, this file contains the following statements:

<?xml version="1.0" encoding="utf-8"?> <LogTraceConfig>  <TraceSeverity value="ERROR" /> <TraceDestination value="" /> <TraceFileCount value="10" /> <MaxTraceSize value="10" /> <TraceUser value="" />  <LogSeverity value="INFO" /> <LogDestination value="" /> <LogFileCount value="10" /> <MaxLogSize value="10" />  <AppSet value="" /> </LogTraceConfig>

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

Trace Settings

The following table explains the parameters of the Trace Setting section of the log-configuration.xml file.

Parameter Default Value Meaning

TraceSeverity ERROR You use the trace severity to control the number of trace records that are produced.

The following trace severity levels are supported:

● DEBUG● PATH● INFO● WARNING● ERROR● DONOTHING

Choosing a severity level means that trace records with the chosen severity, together with all more. severe trace records, are written to the trace file. For example, choosing INFO means that all information, warning, and error trace records are written to the file.

DONOTHING is a special severity level. If you set it as value, no trace records are written to file. This is effectively switching off Trace.

If you set another value for TraceSeverity, for example, ERR, it is treated as DONOTHING.

TraceDestination Empty The location where you want to store the trace files. For example, <TraceDestination value=“C:\Program Files\SAP BusinessObjects\PC_NW\Logging\Trace”>.

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

38 C U S T O M E R


Troubleshooting


TraceFileCount 10 Trace files are named BPCtrace.x.logwhere x is a number between 0 and one less than the TraceFileCount.

The first trace file to be written is BPCtrace.0.log.

When this file reaches the MaxTraceSize, the next file, BPCtrace.1.log, is started. This continues until there are TraceFileCount trace files, whereupon the system overwrites BPCtrace.0.log.

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

Log Settings

The following table explains the parameters of the Log Setting section of the log-configuration.xml file.



LogSeverity INFO You use the log severity to control the number of trace records that are produced.

The following log severity levels are supported:

● INFO● WARNING● ERROR● DONOTHING

Choosing a severity level means that trace records with the chosen severity, together with all more. severe log records, are written to the log file. For example, choosing INFO means that all information, warning, and error log records are written to the file.

DONOTHING is a special severity level. If you set it as value, no log records are written to file. This is effectively switching off Logging.

If you set another value for TraceSeverity, for example, ERR, it is treated as DONOTHING.

LogDestination Empty The location where you want to store the log files. For example, <TraceDestination value=“C:\Program Files\SAP BusinessObjects\PC_NW\Logging\Log”>.

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

40 C U S T O M E R


Troubleshooting


LogFileCount 10 Log files are named BPClog.x.logwhere x is a number between 0 and one less than the LogFileCount.

The first log file to be written is BPClog.0.log.

When this file reaches the MaxLogSize, the next file, BPClog.1.log, is started. This continues until there are LogFileCount log files, whereupon the system overwrites BPClog.0.log.

Application Set Settings

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

5.4.2 Client Configuration

Use

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

Features

Trace and Log File Destination

The defaults for TraceDestination and LogDestination are empty fields. If Business Planning and Consolidation detects these empty fields at user logon, it uses <TraceDestination value="C:\Program Files\SAP BusinessObjects\PC_NW\Logging\Trace" /> and <LogDestination value="C:\Program Files\SAP BusinessObjects\PC_NW\Logging\Log" />.

Frequent Tasks


The following table details some frequent trace and log configuration tasks:

Task How To

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

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

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

Configuring log-configuration.xml

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

5.5 Troubleshooting Transport (Standard only)

Use

Transports allow you to move an environment across a landscape. For example, you can transport an environment from a development environment to a test environment and then to a production environment.

For detailed information about how to use SAP transports, refer to Transport Management (Embedded only) [page 24].

Features

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

Deleting Objects

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

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

● Files such as script logic and Excel templates are only updated. That is, changes to these files are transported. Since only updates are transported, deleting files in the development system does not impact existing files in the test or production systems. Similarly, deleting files in the target system does not cause any harm.

42 C U S T O M E R


Troubleshooting

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

Choosing Transport Strategies

There are many SAP transport strategies. Frequently, a test or production system is built with every released transport from the development system.

RecommendationWe recommend that you build Business Planning and Consolidation systems with the last good transport. Since the Business Planning and Consolidation transport framework can gather all environment objects, the fear of missing something can be alleviated.

We also recommend that, after going live, changes are always made in the development system and transported from there to the test and production systems.

Changing the Data Model Objects

Do not change the data model in target systems. A typical system landscape may contain development, test, and production instances. If you change objects in a target system, the transports that originate from development will no longer import correctly.

Data model changes consist of objects such as environment, model, dimensions, or properties. You can maintain the data model in the test or production system, but this means that you cannot use the transport framework since it will no longer import properly.

Other components, such as worksheets or data manager packages (not data model related), can be changed in any instance.

Changing Data Model Objects

Do not change the structure or definition of Business Planning and Consolidation related data model objects in BW. This includes objects such as environment (InfoArea), model (CompositeProvider and advanced DataStore Object), dimensions (InfoObjects), and properties (InfoObjects). This causes subsequent transports to fail.

Changing Technical Names

The technical name of the DataStore Object (advanced) or CompositeProvider may change between landscapes. This is normal. Business Planning and Consolidation does not transport technical names of DataStore Objects (advanced) and the transport works well.

Transport Failure Solutions

The following table highlights some typical installation and transport failure scenarios and solutions.

Scenario Solution Actions

Installation failed with the error No content objects found

1. Enter transaction code RSOCONTENT.

2. Ensure that System is a Content Development System is not selected.

Import failed with RFC errors Refer to SAP Note 1329651 .



Scenario Solution Actions

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

1. Enter transaction code SE16 for table UJT_TRANS_OBJECT.

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

3. Reimport the request.

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

1. Go to the BW modeling tools.2. See if there are any InfoObjects or DataStore Objects

(advanced) that refer to the attributes of the failed dimension.If so, break the references between Business Planning and Consolidation InfoObjects and your InfoObjects and DataStore Objects (advanced).

3. Reimport the transport request.

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

Check if anyone has transported this dimension through the BW back end manually. If so, perform the following steps:

1. Delete the InfoObjects in the BW Modeling tools on the target system.


Import failed with the error: Failed to create infoarea

1. Enter transaction code SE06.

2. Change the namespaces /CPMB/ and /B28/ to be modifiable.


More Information

SAP Note 1415296 .

You can also check SAP notes under the application area: EPM-BPC-BW4-INS-TRA.

5.6 Component-Level Logs

Use

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

NoteFor SAP Business Planning and Consolidation, replace <app config name> with bpc.

44 C U S T O M E R


Troubleshooting


1. How do I launch the application?http://<host>:<port>/sap/fcprt?app-config=<app config name>

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

3. How do I enable debug mode in the application?To enable debug mode, the Flex Client Platform (FCP) server parameter pp-enable-debugging=true must be set and the URL query parameter debug=true must be used when launching the application.For example: http://<host>:<port>/sap/fcprt?app-config=<app config name>&debug=true

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

5. How do I see status of the various plug-ins and the reasons why some plug-ins are not loaded?As a prerequisite, enable the support mode.○ After launching the application in support mode, right-click the application and select Support Info.

In the Loaded Plug-ins tab of the Support Information dialog, you can see information about the loaded plug-ins, the state of the plug-ins and the error information for plug-ins that could not be loaded.

6. How do I see the version information of the plug-ins?As a prerequisite, enable the support mode.○ After launching the application in support mode, right-click the application and select Support Info.

In the Loaded Plug-ins tab of the Support Information dialog, you can see information about the version and the build number of the plug-in.

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

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

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


5.7 Troubleshooting for Event & Notification

If messages are not being delivered, check the scheduled jobs for event and notification.

For more information about monitoring the jobs required to send messages to e-mail, see the Installation Guide - SAP Business Planning and Consolidation, version for SAP BW/4HANA available on the SAP Help Portal.

46 C U S T O M E R


Troubleshooting

6 Support Desk Management

6.1 Remote Support Setup

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

SAP Note Title Comment

486688 Schedule VPN connection to SAP network

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

For further assistance, see the following SAP Note:

SAP Note Title Comment

812386 RFC connection to the SAPNet R/3 front end

-

6.2 Logging Problem Messages

Problem messages can be logged at SAP Support Portal on SAP Service Marketplace, which is located at http://service.sap.com/ .

You can use component strings to efficiently direct your support message. Although using component strings, doing so can reduce processing time since their use assists in dispatching your message to the appropriate support personnel.

For both the standard and embedded configuration of Business Planning and Consolidation as a whole, use the component string EPM_BPC_BW4.

The components are then broken down into feature levels. For example, for modeling-related issues of the application, choose the component EPM_BPC_BW4_MOD under the main component EPM_BPC_BW4.

Administrator's Guide - SAP Business Planning and Consolidation, version for SAP BW/4HANASupport Desk Management C U S T O M E R 47



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

48 C U S T O M E R


Important Disclaimers and Legal Information

Administrator's Guide - SAP Business Planning and Consolidation, version for SAP BW/4HANAImportant Disclaimers and Legal Information C U S T O M E R 49

www.sap.com/contactsap

© 2019 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 https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

Administrator's Guide - SAP Business Planning and ...

Documents

Transcript of Administrator's Guide - SAP Business Planning and ...