How To Use Delta-Cache and Delta-Pair in BCS

How-to Guide SAP CPM
How to use Deltacache and Deltapair in SEM-BCS

Version 1.01 - November 2007 Applicable Releases: SEM-BCS 6.0 SAP_BW 700 SP 13 (included in NW2004s SPS 12)
Copyright 2007 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, Outlook,and PowerPointare registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, 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 in several other countries all over the world. 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. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP CPM How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings (Code) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.
1 Introduction / Background Business scenario

This Howto paper is used to optimize reporting performance in SEM-BCS. It should be applied for SEM-BCS 6.0 installations in addition to the scenario according to the howto paper How to... configure the Delta Load based MultiProvider Scenario. We strongly recommend to read both papers before you start to implement the proposed solutions. Both howto papers can be found in the service marketplace: http://www.service.sap.com/solutions Solution Details Business Solutions and Applications SAP Business Suite SAP ERP SAP ERP Analytics SAP Strategic Enterprise Management (SAP SEM) Business Consolidation Media Library How Tos
2 The Step By Step Solution

2.1 Ensure preconditions and migration from former implementation of the request based MultiProvider scenario
1. Check whether your installation is on the applicable release and support package stack/support package level 2. Ensure that you have already implemented the request based MultiProvider scenario with or without the modification SEM-BCS 6.0 SAP_BW 700 SP 13 (included in NW2004s SPS 12) The request based MultiProvider scenario is described in the howto paper
How to... configure the Delta Load based MultiProvider Scenario which is
the prerequisite for this howto paper
3. Ensure that variable exits are not used anymore in queries on the MultiProvider
Variable Exits for the Request-IDs must not be used anymore in queries on the MultiProvider. To ensure this, please do the following: If you use the Delta Load based MultiProvider Scenario (described in the howto paper How to... configure the Delta Load based MultiProvider Scenario as well as in the SEM-BCS 6.0 Enhancement Package 1 online documentation) and also the modification that is described in the mentioned howto paper, you should remove this modification. If you use the Delta Load based MultiProvider Scenario (described in the howto paper How to... configure the Delta Load based MultiProvider Scenario as well as in the SEM-BCS 6.0 Enhancement Package 1 online documentation) without the modification, you must change all MultiProvider queries manually: Remove the assignment of the SAP delivered SAP-Exit variable 0S_BCSRQ to characteristic 0BCS_REQUID from the global filter of all MultiProvider queries. Remove the assignment of the SAP delivered SAP-Exit variable 0S_CSRQ to characteristic 0REQUID from the global filter of all MultiProvider queries.
4. Ensure that corrections are imported 5. Read the online documentation
SAP Note no. 1063916 Various errors in delta pair Activating Delta Caching: http://help.sap.com/saphelp_nw70/helpdata /en/44/ec16e13a2e65fbe10000000a1553f7/fra meset.htm Specifying the Grouping for Delta Caching: http://help.sap.com/saphelp_nw70/helpdata /en/57/b10022e849774f9961aa179e8763b6/fra meset.htm
2.2 Make settings for the Deltacache support

6. Ensure that the preconditions for the Virtual InfoProvider are kept
New Property of the Virtual InfoProvider: Deltacache Deltacache only possible for the Virtual Provider of the totals data stream The Function Module assigned must be RSSEM_CONSOLIDATION_INFOPROV3 7. Maintain the InfoProvider properties accordingly
8. Maintain all queries based on the Virtual InfoProvider
RSRT Environment Maintenance
Query Mass
9. Make InfoProvider settings for all queries
10. Note the system behaviour after the previously described customizing
2.3 Make settings for the Deltapair support

11. Activate Deltapair support New Property of the MultiProvider: Deltapair Choose Extras Delta Pairs Only Deltacache enabled Providers can act as DeltaProviders SEM-BCS: Assign the Virtual Provider as DeltaProvider to the Reporting InfoCube Prerequisite: The Virtual Provider has the Delta Cache Class CL_RSSEM_DC_SUPPORT_VP_BCS assigned As Delta Pair Class choose CL_RSSEM_DELTAPAIR_BCS
RSDIPROP (InfoProvider: Edit Properties)
SAP AG 2005, Delta Load / Jens Heumann / 1
12. Start query mass maintenance for MultiProvider
13. Note the system behaviour after the previously described customizing
2.4
Further important information

How To Use Delta-Cache and Delta-Pair in BCS

Uploaded by

Copyright:

Available Formats

How To Use Delta-Cache and Delta-Pair in BCS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

How To Use Delta-Cache and Delta-Pair in BCS

Uploaded by

Copyright:

Available Formats

What are the prerequisites for using delta caching and delta pairs?

What steps need to be taken to configure delta caching?

How-to Guide SAP CPM

How to use Deltacache and Deltapair in SEM-BCS

1 Introduction / Background Business scenario

2 The Step By Step Solution

4. Ensure that corrections are imported 5. Read the online documentation

2.2 Make settings for the Deltacache support

8. Maintain all queries based on the Virtual InfoProvider

RSRT Environment Maintenance

9. Make InfoProvider settings for all queries

2.3 Make settings for the Deltapair support

RSDIPROP (InfoProvider: Edit Properties)

SAP AG 2005, Delta Load / Jens Heumann / 1

12. Start query mass maintenance for MultiProvider

Further important information

You might also like