cancel
Showing results for 
Search instead for 
Did you mean: 

Performance improvement in BPS

Former Member
0 Kudos

Hi

How the performance can be improved in BPS ?

What are the ways in which the BPS performance can be improved. Any tips will be useful.

regards,

Sarah

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

You could start with BPS_STAT0 which will let you see how much time is lost in pure read and write processes, variable executions etc.

Check for nested hierarchies. Always a bad idea.

Leverage characteristics or navigational attributes rather than hierarchies. Using a hierarchy requires reading temporary hierarchy tables and creates additional overhead compared to characteristics and navigational attributes. Therefore, characteristics or navigational attributes result in significantly better query performance than hierarchies, especially as the size of the hierarchy (e.g., the number of nodes and levels) and the complexity of the selection criteria increase.

If hierarchies are used, minimize the number of nodes to include in the query results. Including all nodes in the query results (even the ones that are not needed or blank) slows down the query processing. The u201Cnot assignedu201D nodes in the hierarchy should be filtered out, and you should use a variable to reduce the number of hierarchy nodes selected.

Make sure queries are regenerated in production using RSRT after changes to statistics, consistency changes, or aggregates.

Former Member
0 Kudos

Hi,

Ideally you should check the complete customizing. This is normally not possible because of time or resource constraints so you should:

u2022 Check specific parts of customizing to ensure quality.

u2022 Test central business processes.

u2022 Apply optimizations derived from one area to other areas.

A use case can be used as the basis for discussions about performance issues with other groups such as technical administrators, business owners, and consultants. A use case can also be used as a reference throughout the different project phases:

u2022 Use case reflects business requirements and ensures that the required business processes execute correctly.

u2022 A use case can be used as a proposal for prototype content.

u2022 A used case should be performed during the customizing phase as part of the testing phase and used to compare against different implementation scenarios.

u2022 A use case should be repeated before go live date to decrease risk and to determine the impact of the shift from sample data to productive data such as master data volume, transaction data volume, and authorizations.

System collects various statistics on BPS, SAP BW, system workload, and database.

For each step of the use case, you should evaluate if performance and memory consumption are okay.

Perform checks in the order given:

u2022 Is total runtime okay in BPS?

u2022 If not, is OLAP time OK in BW? If not, is network and frontend time OK in Basis? If not, is data selection time OK in database?

Transactions:

􀂄 BPS Statistics (BPS_STAT0)

􀂄 Workload Statistic (STAD)

When you monitor general planning performance, separate general performance issues from specific ones:

u2022 Are all users or only single users faced with an increased response time? u2013 Detect areas or users with particular problems by comparing them to the average.

u2022 Is the performance stable over days/weeks/months? Is there a trend? u2013 Detect overall performance changes.

As a first step in performance optimization, determine critical areas and continue with use case approach. Go directly to technical problem areas:

u2022 System settings (SAP notes, Going Live Check and so on)

u2022 SAP Web Application Server

u2022 SAP BW

u2022 BPS

Verify and validate your sizing information to minimize risk of insufficient system resources, for example, compare average and peak activities with expectations.

Execute BPS benchmark on a regular basis to monitor possible changes and analyze impact of system settings and system health. This is one of the key ways to ensure constant basis performance. For details, refer to SAP Note 350011.

Transactions:

􀂄 System Load und Performance Statistics (ST03)

􀂄 BPS Performance Statistics (BPS_STAT1)

􀂄 BPS Benchmark (Program UPC_BENCHMARK_EXECUTE)

Activation of statistics has a minimal impact on performance (a few tenths of a second maybe). Therefore, many customers leave it turned on in production. Aside from the statistical analysis, an additional benefit is that an audit trail shows who has done what at what time.

You can evaluate detailed statistics using transaction BPS_STAT0. You can enter get to this transaction

from the Planning Workbench (BPS0) and choose Tools u2192 Statistics.

Various criteria can be used to restrict the selection of statistical records.

Statistics are always recorded in UTC+0 time zone (GMT). However, the selection can be done based on system time.

Detailed information is available in the "BPS Performance Guide."

Collection of SEM-BPS Statistics must be activated for each

system (run transaction BPS_STAT0 and select the type of

statistics on the Statistics On/Off screen)

Several performance measurements are recorded for each

activity in BPS (layouts, functions, API, and Web interface)

Analyze single record statistics with transaction BPS_STAT0,

analyze performance statistics with transaction BPS_STAT1

The left part of the output lists statistical records. One line represents one activity by an end user. The right part of the output (Value) displays a detailed breakdown of a single activity. This is especially useful when working with Web interfaces, which can contain several layouts and functions in one activity or on one web page.

The initial list display does not contain all columns. To display the hidden columns, choose Change Layout from the toolbar.

For more information on all performance measures, refer to the "BPS Performance Guide" on the SAP Service Marketplace at service.sap.com (use the alias or quicklink /BW and choose SAP Business Planning & Simulation u2192 Performance).

Manual Planning records

u2022 MP_DATA_PUT u2013 Total time for converting the data from the logical description into a suitable format for the display tool and for transporting or displaying the data on the personal computer (PC)

u2022 MP_START_VIEWER u2013 Time when the viewer (Microsoft Excel) is started on the PC

u2022 MP_LOG_SCR u2013 Conversion of the database table into a logical description of the layout

u2022 MP_DATA_TO_FRONT u2013 Total time for transporting the cell content to the PC and for transferring data to the local instance of Microsoft Excel

u2022 MP_ABAP_EXIT u2013 ABAP Exit for filling the Excel cells with data

SAP Business Information Warehouse (SAP BW) records

u2022 BW_DATA_READ u2013 Read access to SAP BW

WEB applications

u2022 WEB_INPUT_PROC u2013 Input processing by the WEB application

u2022 WEB_INIT u2013 Initialization of the WEB application

Attribute Name: Manual Planning

u2022 CELLS_TRANS u2013 Number of transported data cells (including dummy cells and cells added in the user exit)

u2022 CELLS_PP u2013 Number of data cells prepared by SEM/BW/BW-BPS

Attribute Names: Planning Functions

u2022 RECS_READ u2013 Number of data records from the planning package

u2022 RECS_READ_REF u2013 Number of reference data records

u2022 RECS_NEW u2013 Number of data records generated

u2022 RECS_CHG u2013 Number of data records changed

u2022 RECS_DEL u2013 Number of data records deleted

TYPE contains additional information

u2022 BW_DATA_READ u2013 Lock type, such as "E" for exclusive lock, "blank" for shared lock (reference or displayed data)

u2022 NAME = "API" u2013 Name of the function module

u2022 NAME = "PF" u2013 Type of planning function

Attribute Name: WEB Applications

u2022 PAGE u2013 Name of the WEB application

u2022 T_PREV_CALL u2013 Response time of the last dialog step of the WEB planning session

Attributes for General Use

u2022 P_AREA u2013 Planning area

u2022 P_LEVELu2013 Planning level

u2022 P_PACKAGE u2013 Planning package

u2022 P_METHOD u2013 Planning method

u2022 P_PARAM u2013 Planning parameter

u2022 T_BRUTTO u2013 Total runtime (Gross)

u2022 T_NETTO u2013 Total runtime minus runtime used for subordinate elements (Net)

u2022 T_STAMP u2013 Timestamp specifying the start time

Aggregated statistics can be analyzed using transaction BPS_STAT1. Use activities.

Definition of abbreviations used in output:

u2022 BW = SAP Business Information Warehouse

u2022 MP = Manual Planning

u2022 PF = Planning Function

u2022 WEB = Web Interface

u2022 API = BPS Application Programming Interface

u2022 DB = Database

u2022 Cnt exec, no exec, DB req = number of executions or accesses

General comments:

u2022 All types of planning functions are mixed.

u2022 The average includes functions with and without BW access.

u2022 No reference data is included yet u2013 only part of the single

record statistic.

Collection of BW Statistics needs to be activated per InfoCube using Administrator Workbench u2192 Tools u2192 BW Statistics for InfoProviders.

Several performance measurements are recorded for each data selection from BPS layouts and functions (also for BW queries). Essential from a BPS perspective:

u2022 InfoCube, User, Timestamp

u2022 Number of records read by database

u2022 Number of records returned by database (aggregation)

u2022 Runtime of data selection

Aggregated statistics can easily be evaluated using the BW Statistics Workbook, which is delivered as part of the Business Content (Administrator Workbench u2192 Business Content).

Detailed statistics can be accessed using transaction SE16 and table RSDDSTAT. BPS selections are stored under OLAPMODE = '007'.

The detailed BW statistics are linked to the BPS statistics via InfoCube (derived from the planning area), user ID, and timestamp (format is YYYYMMDDhhmmss).

For details, refer to SAP Note 309955.

Please award points if helpful.