Improving ODS Activation Time

[Former Member]

Applies to:

SAP BW 3.5x / Business Intelligence 7.3x.

Summary:

  For checking the quality of data loaded into DSO and making data available for reporting and for staging we do activation of DSO. But DSO Activation takes huge time depending up on the volume of data. This long time taken for activation delays the process chain run and hence causes subsequent delay in delivery of reports.

Author(s)     :  Amit Kumar Trivedi

Company    :   Infosys Limited

Created on  :  25 October 2012

Author Bio

Amit Kumar Trivedi works as Senior Systems Engineer in Infosys Limited. He has 3 years of experience in

SAP BW. He has worked on Various Support and implementation Projects.

Table of Contents

.

1. Summary ………………………………………………………………………………………………3
2. How to do Activation ………………………………………………………………………………….3
3. Ways to Improve ODS Activation Timing …………………………………………………………..5
4. Precautions ………………………………………………………………………………………….. 11
5. Related Content ………………………………………………………………………………………11
6. Copyright ………………………………………………………………………………………………12

1.   Summary

For checking the quality of data loaded into DSO and making data available for reporting and for staging we do Activation of DSO. But DSO activation takes huge time depending up on the volume of data. This long time taken for activation delays the process chain run and hence causes subsequent delay in delivery of reports.

2. How to do Activation?

1. Load the data into the DSO .Request will appear in the manage screen of DSO.

b. Click on Activation as shown in the below screenshot. A New window will be opened.

     c. Select the Request and Click on Start for starting the activation.

        

     d. Once Activation is done we will get an indicator (as shown below) that Activation is done.

        

3.  Ways to improve ODS Activation Timing

   3.1 Delete the Change Log table of ODS :-  It is always recommended to delete the Change Log table  time to time otherwise it can grow rapidly  This increase in Size of table will hit the Loading Performance as well the activation timing of ODS .

   3.2 Removing  SID Generation  Flag :- If we are not using ODS for Reporting Purpose and just we are using for staging purpose (for further processing to Info Providers) , Then we should remove the  SID Flag in the DSO Settings as shown below .

             

                SID generation has three setting available:-

•   During Reporting: - No SIDs will be generated during the activation of DSO, only when Query is executed SIDs is generated.
•   During Activation: - SIDs is created during activation of data.
•   Never Create SIDs: - SIDs is not created on Activation or during Reporting

Note: - If we are keeping mode as “Never Create SIDs” and creating a Query on top of the same ODS query cannot be executed. However it will be possible to include the DSO in Info Sets and create a query.

      3.3 Change Runtime Parameters For Activation :-

           Go to t. code RSODSO_SETTINGS.  i e. Maintenance of Runtime Parameter of DSO

           

              Now here we can change the System settings for all the DSOs or only to specific DSOs as well.

              Here is the list of options available:-

                   -  Cross- DataStore          :-  For all the DSOs in the system

                   -  DataStore-Specific        : - Only for Specific DSOs.

               In Our case, we will do changes only to specific DSO by choosing “DataStore-Specific”.

              

                A new window will open as shown below.

               

                   Check the Parameter for Activation .

                   Default values are as follows:-

                            - Maximum Package Size                     :- 20,000

                            - Maximum Wait Time for Process         :- 300

                  Note:- Above values are based on Hardware capacity and configuration values , may vary system to system .

To improve the Activation of DSO when the records are huge , we can increase both the parameters . The change in parameters should be based on  the   system capability , So please check with basis team to ensure after changes overall performance  of the system should not degrade .

For example :- In our case we are maintaining below values :

  - Maximum Package Size                     :- 50,000

- Maximum Wait Time for Process         :- 600

                   

         3.4   Changing Background Parallel Process for Activation :-

                Go to t. code RSODSO_SETTINGS. i.e. Maintenance of Runtime Parameter of DSO .

             

Proceed similarly as we did in the above point and then click as shown below. New window will open where we can do changes in the No. of Parallel Process .

             

               

We can increase the parallel processes from 3 to 4/5 depending up on capability of the system. Check the available background processes during activation of DSO before doing the changes.

            

               We can use both the setting mentioned in point 3.3 and  3.4 together  as well to improve the ODS Activation timing .

4.  Precautions:

While doing this configuration test it completely in Development, Integration, Quality, UAT systems because these configurations can hamper overall  system  performance badly. Also keep your Basis consultant informed while applying these changes.

5. Related Content:

   Please include at least three references to SDN documents or web pages.

   Reference 1 :- scn.sap.com/thread/426079

   Reference 2 :- www.sdn.sap.com/.../f0d82054-f705-2e10-75b8-fc0f42

   Reference 3 :- scn.sap.com/message/9217742

6.  Copyright

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

  These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.