How-to Guide SAP NetWeaver 04

How To Validate InfoCube Data By Comparing it with PSA Data

Version 1.00 December 2004

Applicable Releases: SAP NetWeaver 04

 Copyright 2004 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 PowerPoint are 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, SAP NetWeaver, 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 NetWeaver 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 NetWeaver. 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 Scenario
You would like to compare the contents of your InfoCube with data loaded from your source system into the PSA. In our example, we will check data that has been loaded for a specific customer.

2 Introduction
As of SAP BW 3.0A, there is an Export DataSource for the PSA. You can use this DataSource like any other DataSource, for example to read data from the PSA with a RemoteCube. In the example shown here, we will compare data that has been loaded to the InfoCube with data loaded into the PSA. In a query, you can see the data from the InfoCube in one column and the data from the corresponding PSA table in another column. You can compare the results and judge whether they match. This paper only gives you an introduction about how you can work with the PSA Export DataSource. A productive scenario will probably look much more sophisticated (see 4).

-1-

3 The Step By Step Solution

3.1 Create a Remote Cube for Reporting on Data in the PSA
1. In the PSA tree of the Administrator Workbench, generate the Export DataSource on the PSA you want to check against via the context menu.

2.

In the source system tree, display the DataSource overview of the MYSELF BW system and locate your PSA Export DataSource. The technical name is the original DataSource name (to which the PSA belongs) prefixed with a 7.

3.

From the context menu of the DataSource, choose Assign InfoSource.

-2-

4.

Enter a name for your new InfoSource and press the Create-button.

5.

Create an InfoSource for flexible update. This should be the default, so just press the green arrow to continue.

6.

Maintain the communication structure and transfer rules. Make sure that REQUEST is mapped to 0TCTREQUID (don`t change the default). The Transfer Method will automatically be set to IDOC. Activate your InfoSource.

7.

Create a RemoteCube to access data in the PSA.

-3-

8.

Choose a name and a description for the InfoCube. As InfoCube type choose SAP RemoteCube and enter the name of the InfoSource you have created in steps 4-6. Tick the Clear Source System checkbox since the SAP BW System itself is the only source system of the RemoteCube.

9.

Select characteristics and key figures, create dimensions and assign the characteristics to the dimensions (no special modeling guidelines have to be followed for a RemoteCube). Activate your RemoteCube.

10. From the context menu of the RemoteCube, choose Assign Source Systems

-4-

11. Select the source system (the SAP BW system itself) and save the assignment.

3.2 Create a MultiProvider combining the InfoCube and the RemoteCube

12. Create a MultiProvider.

13. Choose a name and a description for the new MultiProvider and press the Createbutton.

-5-

14. Select the InfoCube you want to check and the RemoteCube you have just created as the InfoProviders involved in the MultiProvider.

15. Select the characteristics you need for your check reports. Make sure 0TCTREQUID is included.

-6-

16. Identify characteristics and choose the key figures (from both InfoCubes) you would like to compare. Activate your MultiProvider.

3.3 Create a check query on the MultiProvider

17. Create a query and include the characteristics you want to use, the Request ID from the DataPackage dimension and the Data Request (GUID) for the PSA request number. It is useful to include variables for your characteristics (otherwise you may get far too much data).

-7-

18. Create selections for the Key Figures you want to check.

19. In the first selection, use your Key Figures and the InfoProvider characteristic 0INFOPROV restricted to the InfoCube (0INFOPROV is automatically available in every MultiProvider).

-8-

20. In the second selection, restrict the InfoProvider characteristic to the RemoteCube.

3.4 Run the check query

21. Run the query. In our example, we are checking data for one customer.

22. The result shows the data from PSA with corresponding Data Request (GUID) and the sum of the data from the InfoCube.

23. If you drill down on Request ID, you get the data from the InfoCube displayed with the Request ID in the InfoCube (which you can see in the InfoCube Management).

-9-

24. Optional: If you only want to check the data for the last request, you can add the variable 0LSTRQID to your InfoCube selection and

25. the variable 0MAPRQID to your RemoteCube selection. The latter is filled automatically with the PSA Request ID corresponding to the InfoCube Request ID filtered by in the first variable.

26. The result will only show data loaded with the last request.

- 10 -

4 Appendix
If you would like to automize the check described above, you can enhance the query with a variance formula and create an exception based on this new column. Afterwards, you can schedule the check with the Reporting Agent and in the case of deviations specified by the exception, you can have an e-mail sent to the administrator. This kind of check report may not always display the same figures for the InfoProvider as for the PSA for several reasons:

Data may be deleted from the PSA but still reside in the InfoCube. Data may be deleted from the InfoCube but still reside in the PSA. Data may be loaded in the PSA but never to the InfoCube. Transfer and update rules may convert the data in a way that it doesnt match the original data anymore. A more sophisticated query could help in such a case, however. The Export DataSource on the PSA is a generic DataSource using the current PSA table. If the transfer structure is changed and activated, a new table may be generated. Old data in the PSA will then no longer be accessible to the RemoteCube.

- 11 -

www.sdn.sap.com/irj/sdn/howtoguides