analyze rsz tables

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

Inconsistencies on Reusable

Query Elements (Objects) – BI 7.0

Applies to:

Applicable – from BW 3.0 and above. For more information, visit the EDW homepage

Summary

This article will help to understand the inconsistency issues of query reusable components, while using the BW 3.x BEx queries in BI 7.0 system. The same check can be performed in BW3.x systems, as well.

This article is to highlight the standard approach available in SAP which is safe and on-control method, to identify the various Meta – issues of the query components.

The main issue / example discussed in here talks about renaming duplicate existence of same reusable element (restriction variable) in current system.

Author: Vimalanathan Murugan

Company: Accenture Services (P) Ltd.

Created on: 28 June 2011

Author Bio

Vimal Murugan is currently working with Accenture, and is a SAP BI – ABAP consultant with 56 months of experience in SAP BW 3.5 and BI 7.0

http://www.sdn.sap.com/irj/sdn/edw

Inconsistencies on Reusable Query Elements (Objects) – BI 7.0


© 2011 SAP AG 2

Table of Contents

Query Reusable Elements .................................................................................................................................. 3

Reusable Elements: ........................................................................................................................................ 3

Inconsistencies – possible reasoning ................................................................................................................. 3 Recommendation ................................................................................................................................................ 3 Caution: ............................................................................................................................................................... 4

Least recommended: ...................................................................................................................................... 4

Recommended solution – safe & control ............................................................................................................ 4

Report for Analysis / Fix: ................................................................................................................................. 4 Tables being analyzed: ................................................................................................................................... 4 Additional Tables checked by this program: ................................................................................................... 4 IMPORTANT NOTE # 1 .................................................................................................................................. 4 IMPORTANT NOTE # 2 .................................................................................................................................. 5 SCREEN SHOT - 3.5 query designer view ..................................................................................................... 5 SCREEN SHOT – BI 7.0 query designer view ............................................................................................... 6 IMPORTANT NOTE # 3 .................................................................................................................................. 6

Point to consider before running this report - ............................................................................................................... 6 Renaming of queries also may cause an impact. ......................................................................................................... 7

IMPORTANT NOTE # 4 .................................................................................................................................. 7 Sample execution of the report – BW 3.5 ....................................................................................................... 7 Analysis ........................................................................................................................................................... 9

Table RSRREPDIR ...................................................................................................................................................... 9 Table RSZCOMPDIR ................................................................................................................................................. 10 Table RSZCOMPIC ................................................................................................................................................... 10 Table RSZELTXREF .................................................................................................................................................. 10 Table RSZGLOBV ..................................................................................................................................................... 10 Table RSZELTDIR ..................................................................................................................................................... 11 Table RSZELTTXT (Translation errors) ..................................................................................................................... 11 Table RSZELTPROP (Special checks) ...................................................................................................................... 11 Table RSZCALC ........................................................................................................................................................ 11

A quick example – BI 7.0 .................................................................................................................................. 12

IMPORTANT NOTE # 5 ................................................................................................................................ 13

BI 7.0 Test Case – intro .................................................................................................................................... 14

Solution corner .............................................................................................................................................. 14 1. Test Case - Report for Issue Fix ............................................................................................................................ 14 2. Test Case - Necessary Table Selection ................................................................................................................. 15 3. Test Case - Output log of the Report ..................................................................................................................... 15 4. Test Case - List of Duplicate Objects ..................................................................................................................... 16 5. Test Case - Object to be changed ......................................................................................................................... 16 6. Test Case – Related Meta data ............................................................................................................................. 16 7. Test Case - Objects @ Tables -Before Change ..................................................................................................... 16 8. Test Case - Objects @ Query - Before Change ..................................................................................................... 17 9. Test Case - Change Proposition ............................................................................................................................ 17 10. Test Case - Change Execution & Confirmation .................................................................................................... 18 11. Test Case - Objects got changed ......................................................................................................................... 18 12. Test Case - Objects @ Tables - After Change ..................................................................................................... 19 13. Test Case - Objects @ Query - After Change ...................................................................................................... 20

IMPORTANT NOTE # 6 ................................................................................................................................ 21

Conclusion ........................................................................................................................................................ 21 Related Content ................................................................................................................................................ 22 Disclaimer and Liability Notice .......................................................................................................................... 23



© 2011 SAP AG 3

Query Reusable Elements

Before jumping on the inconsistency analysis, let‟s try to re-cap the type of query elements that are global, i.e., reusable –

Reusable Elements:

Queries

Structures

Selection Objects

Basic Key Figures

Restricted Key Figures

Calculated Key Figures

Filters

Restriction Variables

Formula Variables

Customer Exit Variables

Inconsistencies – possible reasoning

1. Duplication of objects

2. Variation in object version

Following are the reasons for the duplicate existence of reusable query elements (Queries,

Global Structures, Basic Key figures, Restricted Key figures, Calculated Key figures).

1. Objects transported from different base systems (more that one Dev system)

2. Objects created(Dev) and transported(QA), then deleted in Dev and created again with same Tech name and transported(QA), without transporting the Deletion rule

3. Objects directly created (if allowed) in servers by different users varying with Authorizations

Recommendation

SAP recommends for consistency of objects by using unique Tech name. For those objects that already has duplicate entries can be managed by executing the available SAP standard reports

"RENAME_DUPLICATE_ELEMENTS" as per OSS Note 907025

AND / OR

“ANALYZE_RSZ_TABLES” as per OSS Notes 792779 and 1020826.



© 2011 SAP AG 4

Caution:

Least recommended:

I would not use the RENAME_DUPLICATE_ELEMENTS program which implicitly will rename the duplicate entries of all the aforementioned reusable elements and which also will have a great deal of impact in areas like Customer Exit / SAP Exit variables, Global Filters, Queries, Views etc.

This program can be used to change all duplicate elements without any check / analysis / confirmation, on a single go. And also is less recommended from my point of view.

Though, this program has a Test Run scenario to simulate and check the changes, it‟s highly recommended to go ahead with the next method.

Recommended solution – safe & control

Report for Analysis / Fix:

SE38 program name - ANALYZE_RSZ_TABLES

Tables being analyzed:

RSRREPDIR - Directory of all reports

RSZCOMPIC - Assignment reusable component <-> Info Cube

RSZCOMPDIR - Directory of reporting components

RSZELTXREF - Directory of query element references

RSZGLOBV - Global Variables in Reporting

RSZELTDIR - Directory of the reporting component elements

RSZCALC - Definition of a formula element

Additional Tables checked by this program:

RSZELTTXT - Texts of reporting component elements

RSZELTPROP - Element properties (settings)

IMPORTANT NOTE # 1

Info Object maintenance (via TCode - RSD1) as well as creation of new query components in Query Designer, both have the mechanism to prevent the creation of objects with same technical names.



© 2011 SAP AG 5

IMPORTANT NOTE # 2

This inconsistency check (reports) work well in BW 3.x and BI 7.0 versions. But the main point is, only the latest version of the reusable object will be referred upon the execution of them or their parent objects in BW 3.x systems. This is not the case with the BI 7.0 where these objects are group-referred upon its call and are considered as error in object design / maintenance. For example, if we have 3 query restriction variable of same technical name (though the COMPUID are different), only the last modified object (recent timestamp) will be referred by the BW 3.x system. And the same will throw error in BI 7.0 and will be a show-stopper for further usage. Please refer the next two screen shots.

SCREEN SHOT - 3.5 query designer view



© 2011 SAP AG 6

SCREEN SHOT – BI 7.0 query designer view

IMPORTANT NOTE # 3

Point to consider before running this report -

-- Potential problems may happen only when variables or queries are renamed.

-- A technical name of a variable can be used in the SAP/customer exit routine and renaming may stop it working.

-- Another risk is with the text variables which can be used in the texts of some other query elements (structure members, for example). In this case, replacement of such variable will not be done.



© 2011 SAP AG 7

Renaming of queries also may cause an impact.

Such objects are workbook will work correctly (here the reference if done via unique GENUNIID key from RSRREPDIR).

But web template and view are referenced via the OLD technical name and therefore after renaming will not work correctly anymore. Or let say, the template will still be working, but will represent the query which has NOT been renamed in this procedure.

Therefore only those queries have to be renamed which are less important or not used in other objects.

All other objects like STR, CKF and RKF are referenced to the other query components via ELTUIDs. This is always unique and changing the user given technical name during renaming will not affect all these references. That means renaming of such objects is the safest.

IMPORTANT NOTE # 4

As far as the duplicity of query reusable objects‟ issue is concerned, it is enough to concentrate only on the below tables.

RSZCOMPDIR - Directory of reporting components

RSZGLOBV - Global Variables in Reporting

RSZELTDIR - Directory of the reporting component elements

Sample execution of the report – BW 3.5



© 2011 SAP AG 9

Analysis

Listed below are the Inconsistencies / Errors that are picked up by this program in the current system (IDES), for each of the aforesaid tables, when ran in BI 7.0 system.

Note: Those entries that are marked with RED Color are erroneous issues that will affect the business execution and they should be fixed at the earliest.

Table RSRREPDIR

1. Queries with missing definition.

2. Queries with missing technical name (COMPID).



© 2011 SAP AG 10

Table RSZCOMPDIR

1. Components with duplicated technical names.

2. Components with empty OWNER field.

3. Components without technical name.

4. Components with special characters in technical name.

5. Components with technical name used by existing Info Objects.

6. Components available only in backup ("B") version.

Table RSZCOMPIC

1. Local elements in RSZCOMPIC table.

2. Components based on non-existing Info Providers.

3. Components based on non-active Info Providers.

4. Components based on Info Providers not available in "A" version.

5. Components not used in queries or other query components.

Table RSZELTXREF

1. No errors found.

2. Run extended check of the table RSZELTXREF.

Table RSZGLOBV

1. VPARSEL field is empty

2. FLAGLH field is empty

3. INPUT = X for variable of replacement type

4. FLAGR = 6, (replacement by hierarchy node), ATTRINM <> 0S

5. VPARSEL <> P for VARTYP = 3, 4, 5

6. Prequery (COMPID) does not exist

7. Zero text length of text variable ready for input

8. COMPID not initial. VPARSEL <> "Q"

9. Variables available only in backup version.

10. Variables not used in queries or other query components



© 2011 SAP AG 11

Table RSZELTDIR

1. Local elements not in use.

2. Structures without structure members.

3. Selections or RKFs with incomplete definition.

4. Variables with inconsistent definition.

5. Queries with inconsistent definition.

Table RSZELTTXT (Translation errors)

1. Lost line-break symbols for query elements.

Table RSZELTPROP (Special checks)

1. Hierarchy defined without required flag

2. Function "Table View" is not supported in BW 7.x

3. Where-used list for property "Calculate single Values As"

4. Where-used list for Hierarchy Nodes

Table RSZCALC

1. Formulas with non-existing operators.



© 2011 SAP AG 12

A quick example – BI 7.0

Following screen shots (upon clicking the view-glass symbol in the above screen) will picture the working of this ANALYZE_RSZ_TABLES analysis program which gives ONLY the list of duplicate entries of reusable elements that exist in the Production system (IDES, in here).



© 2011 SAP AG 13

IMPORTANT NOTE # 5

The list of duplicate entries that are observed in these screen shots should be checked upon for their usage as Customer Exit / SAP Exit / Global Filters / Queries etc., before changing their technical names.

This is because renaming their technical names will have an impact over their utilization, unless got changed manually at the Coding (for Customer & SAP Exit variables) and / or Definition (for Queries & templates) areas.

Also it‟d be pretty useful to focalize on other inconsistencies altogether, as observed by table – wise.



© 2011 SAP AG 14

BI 7.0 Test Case – intro

A restriction variable “ZA_PLNT” for the info object “0PLANT” is created and transported to QA system repeatedly, by deleting its existence in Dev system.

Thus 2 more duplicate entries of same tech name are formed in QA system.

Then by using the “ANALYZE_RSZ_TABLES” report, below cases are observed.

Solution corner

The 'Components with duplicated technical names.„ check under 'Table RSZCOMPDIR' of the ANALYZE_RSZ_TABLES report is a renaming algorithm which takes care of renaming in ALL possible and required places where the COMPID can be used and also allows new user given technical names.

So the components can be renamed according to the customer naming convention.

1. Test Case - Report for Issue Fix



© 2011 SAP AG 15

2. Test Case - Necessary Table Selection

3. Test Case - Output log of the Report



© 2011 SAP AG 16

4. Test Case - List of Duplicate Objects

5. Test Case - Object to be changed

6. Test Case – Related Meta data

This report will change the tech name (COMPID) for active version (Object version = A) of the below listed tables:

1) RSZCOMPDIR - Directory of reporting components

2) RSZELTDIR - Directory of the reporting component elements

3) RSZGLOBV - Global Variables in Reporting

7. Test Case - Objects @ Tables -Before Change



© 2011 SAP AG 21

IMPORTANT NOTE # 6

The analysis of the inconsistency over the query elements, when used the report “ANALYZE_RSZ_TABLES”, shows many objects which all need to be fixed up in the system.

This report will not take for any transport request and can be run directly in any system (Dev / QA / Prod), provided that enough user authorization is exist.

After using this report in Dev system we can attach the changed/ fixed objects under transport requests and move them to other systems, if and only if the objects with exact element ID ELTUID exists in Dev system.

If the same issue is to be considered for all duplicate objects, a very detail analysis would be required.

Conclusion

We might expect SAP to release a new version of the ANALYZE_RSZ_TABLES program where the "where-used" algorithm will include also some other possible indirect dependencies between query components and other system objects (Info Packages or Currency/Unit Translations in the case of variables, Planning functions in the case of Filters and so on).



© 2011 SAP AG 22

Related Content

Duplicated technical names (COMPID) for query components

Report ANALYZE_RSZ_TABLES

Hot fixes for check report ANALYZE_RSZ_TABLES

For more information, visit the EDW homepage

https://service.sap.com/sap/support/notes/907025



http://www.sdn.sap.com/irj/sdn/edw



© 2011 SAP AG 23

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

analyze rsz tables

Documents