OBJSTAT in RSRREPDIR table

Gurus
What is the significance of field OBJSTAT in the table RSRREPDIR? I have bunch of queries with status as INA (Inactive, non executable) but I know which are production queries created by users. These queries have OBJVERS as A but the OBJSTAT as INA?
Also is this a true statment to say that all the queries which have a OBJVERS as B (which are backup) have been migrated to 7.x and can be removed from the sytem or no?
Also what is the difference between the Query Generation Time and the Last Change of Query Runtime Object field?
Thanks,
AK

Hi ak ,
Plz refer to the following link . u will get the required answers.
Deleted queries still exist with B version
SAP BI RSRREPDIR Table
Hope it helps,
Thanx & Regards,
RaviChandra

Similar Messages

SAP BI RSRREPDIR Table

In RSRREPDIR Table column Objver has A, M, D,B can some explain me in more detail
my understanding is
The A version is the active version. Only this version can be executed or used by other objects.
The D version is the version delivered by SAP. With a D version (that in practice has the character of a suggestion or template), SAP can deliver objects independently of the version that is active at the customer site.
The M version is the last revised and saved version of an object. This can never be executed or used;
What does B mean?
column READMOD has A,X and H values can some one explain what they mean
Here are few points which i was able gather
H - The system transports the smallest amount of data from the database to the OLAP processor but the number of read processes is the largest. Data in the hierarchy is aggregated by the database and transferred to the OLAP processor from the lowest hierarchy level displayed in the start list. When expanding a hierarchy node, the system intentionally reads this node's children. You can improve the performance of queries with large presentation hierarchies by creating aggregates in a middle hierarchy level that is greater than or equal to the start level.
READ MOD H will be useful if you have navigational reports?
X - Data is requested in a hierarchy drilldown for the fully expanded hierarchy. The OLAP processor only requests the data required for each query navigation status in the Business Explorer. The data required is read for each navigation step. In contrast to the "Read when navigating/expanding the hierarchy" mode, the system always fully reads presentation hierarchies at tree level. When expanding nodes, the OLAP processor can read the data from the main memory. When accessing the database, the system uses the most suitable aggregate table and, if possible, aggregates in the database itself.
READMOD X is used whenever we have Hierarchical Reads?
A - There is only one read process in this mode. When executing the query in the Business Explorer, the data required for all possible navigation steps for this query is read to the OLAP processor's main memory area. When navigating, all new navigation statuses are aggregated and calculated from the main memory data.
Can I say with READMOD A the Report will be very slow?
who will decide when to use which READMOD? Which is the default READMOD?
Which is the best READMOD (I believe this will be tuff to say as it depends)?
By looking at the READMOD can we say it is a simple, Medium and complex reports?
Thanks in advance
Edited by: rukmangada1 on Aug 1, 2011 11:40 AM
Edited by: rukmangada1 on Aug 1, 2011 12:29 PM

Version B is for Backup.
In case a 3.x query gets converted by accident to 7.x version B can be used to recover it.
Have a look for more here
Deleted queries still exist with B version
Best,
Ralf

How to find lsit of Infoobjects per query in a table

Hi All,
is there a way to find list of all the info Objects per query in a table.
i know there are tables like RSZELTXREF and rszcompdir and rsrrepdir
I am not able to make out the relation between them.
All I want is to know what are the characteristics per query.
I have a list of queries and need to know what are the characteristics in them.
Please reply.
Many Thanks,
Joga

Use the below way:
1. Use RSRREPDIR table: Provide your technical name of the Query in COMPID field. Hit F8. Collec the COMPUID of the query here.
2. Use table: RSZELTXREF: Provide the COPMUID from RSRREPDIR table in SELTUID field and hit F8. in Active version. Here collect the element details from the field TELTUID.
3. Use table RSZELTTXT: and provide all the elements list that you hvae collected in step 2 in ELTUID field of this table. Hit F8. Once done you can see the individual object lists in Short text as well as in Long text.
Always use Object version as "A" to get the active object list.
Hope this clarifies your requirement.

Are Workbook settings stored in any table

Hi Gurus,
Are the workbook settings stored in any of the tables? There is a requirement for me to collect the information on whether the Refresh automatic has been checked or not for the workbooks.
It would be great, If any of you can provide me with the details of the same.
If you require more details, let me know.

Hi Pl check following tables
RSRWBINDEX List of binary large objects (Excel workbooks)
RSRWBINDEXT Titles of binary objects (Excel workbooks)
RSRWBSTORE Storage for binary large objects (Excel workbooks)
RSRWBTEMPLATE Assignment of Excel workbooks as personal templates
RSRWORKBOOK u2018Where-used listu2019 for reports in workbooks
Check the table RSRWORKBOOK
Get the ID of the workbook from RSRREPDIR table
Thanks and regards

What is the table for query name

Hi All,
I need an urgent requirement for removing duplicate technical query names from the production. Since there are few issues with the SAP given program I am customizing the SAP Program. Can any one tell me what is the table where the QUERY NAME and it's technical name can be found?
Thanks,
Alex.

hi Alex,
try RSRREPDIR, RSZCOMPDIR.
there is one oss note all the tables.
Table containing Work Book and query relation
Query Detailes
oss 792779
Symptom
Report ANALYZE_RSZ_TABLES is designed as a check-tool for detecting and solving different types of inconsistencies in the main query definition database tables.
The program is recommended for BW system administrators.
Other terms
Query definition, query, reusable, component, variable, missing elements, missing records, missing UID, INCONSISTENCY, RSZELTDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZCALC, RSZSELECT, RSRREPDIR.
Reason and Prerequisites
ATTENTION: the described version of the program is delivered with the following Support Packages:
SP27 for release BW 3.0B
SP21 for release BW 3.1C
SP13 for release BW 3.5
All versions of this report available in systems before those Support Packages are test versions which can be used only for information purposes.
Check prerequisites
Checks are possible only for elements in object version 'A' (active) and 'D' (delivered).
Checks for query elements in 'D' version are possible only in the systems which are set as content.
Checks description
Report performs checks in the tables containing the parts of the definitions of queries and query components: RSRREPDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZELTDIR and RSZELTXREF.
1. Table RSRREPDIR
The table RSRREPDIR is a header table of the generated reports. Consistency of query definition in this table allows to select a query in the Open Dialogs of fronted application and to call report generated for this particular query using transaction RSRT.
The following errors can be found:
- queries with missing definition;
- queries with missing GENUNIID;
- queries with technical names different than in RSZCOMPDIR;
- non-queries in the table.
1.1 Queries with missing definition
The queries are available only in the table RSRREPDIR and not found in the table RSZELTDIR in the corresponding object version. Such queries (in active version) can be accessed only from RSRT transaction. An attempt to execute such query will return the short dump 'Exception condition INCONSISTENCY'. The error also happens during query generation in RSRT or during mass regeneration of the queries using RSR_GEN_DIRECT_ALL_QUERIES report or application menu of transaction RSRT. The inconsistent queries can not be repaired because of missing query definitions. The recommended solution is to delete those records in order to avoid the possible system dumps.
1.2 Queries with missing GENUNIID
Queries having empty GENUNIID field in the table RSRREPDIR. Such queries may be available in the frontend and in RSRT transaction. An attempt to execute such query will return the message'GENUNIID not found'. Situation requires additional investigation at SAP. Create an OSS message for BW-BEX-ET-QDEF.
1.3 Queries with technical names different than in RSZCOMPDIR
The check outputs the queries which have different technical names in the RSRREPDIR and RSZCOMPDIR tables. Execution of a query using the technical name given in Query Designer and stored in the table RSZCOMPDIR will return the error message 'GENUNIID not found'. The system tries to find the corresponding GENUNIID for the wrong COMPID which does not exist in the system or which belong to another query. The recommended solution is to correct the wrong COMPID in the table RSRREPDIR via corresponding procedure.
1.4 Non-queries in the table
The table RSRREPDIR normally contains only reports. Query elements of other types should not exist in this table and can be deleted. In case, when such records exist in the table an attempt to access them in RSRT returns the error message 'GENUNIID not found'. The recommended solution is to delete those records from the table using the corresponding procedure.
2. Table RSZCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for queries and other reusable query components (STR, RKF and CKF).
The following errors can be found:
- local elements in RSZCOMPIC;
- components with inconsistent definition;
- components based on non-existing InfoProviders;
- components based on non-active InfoProviders.
2.1 Local elements in RZSCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for the reusable components. The local elements and also variables have no InfoProvider assignment and should not exist in this table. Those elements can be deleted via corresponding procedure.
2.2 Components with inconsistent definition
The reusable queries or query components existing in the table RSZCOMPIC, but not found in the table RSZELTDIR. Those reusable components may return 'Exception condition INCONSISTENCY' dump during accessing/execution. The situation may have different outcomes and has to be investigated at SAP. Create an OSS message for BW-BEX-ET-QDEF.
2.3 Components based on non-existing InfoProviders
Queries or query components are assigned to the InfoProviders which do not exist anymore in the system. Queries without InfoProvider are not available in Open Dialogs of frontend applications, but can be executed in RSRT. The execution will return the error message'InfoProvider not found'. The recommended solution is to delete the unnecessary components. Deletion of these queries or query components can be done directly from the list using corresponding procedure similar to RSZDELETE transaction.
2.4 Components based on non-active InfoProviders
Queries or query components which are assigned to the InfoProviders which do not exist in the system in the active version. Queries without active InfoProvider are not available in Open Dialogs of frontend applications. In case, an affected query is technically consistent, an attempt to execute it in transaction RSRT will return the message 'Activate the XXX InfoCube / InfoProvider again. Message #BRAIN 056'. Quite often this error is combined with other errors like missing GENUNIID in the RSRREPDIR or other inconsistencies. Each case has to be investigated in order to get the current status of this object. If the affected query is useless, it can be deleted from the system using transaction RSZDELETE.
The check is available only for the query elements in object version 'A' (active).
3. Table RSZCOMPDIR
The table RSZCOMPDIR is the directory table containing the main properties of all reusable components.
The following errors can be found:
- duplicated technical names (COMPID);
- components with inconsistent definition;
- components without InfoProvider assignment;
- components with missing OWNER.
3.1 Duplicated technical names (COMPID)
The check outputs queries or other reusable query components which have duplicated technical names (COMPID).
The error does not cause any dumps in ABAP or terminations in Query Designer, but may cause several symptoms in different reporting areas:
different queries are available in BEX Analyzer and RSRT under the same name;
wrong query is used as Data Source for Web Template (Web Reporting, Reporting Agent, Broadcasting, MDX);
replacement of variables does not work... etc.
The recommended solution is to provide a new technical name for the duplicated component using corresponding procedure.
ATTENTION: in case when there are only 2 components with the duplicated technical name, only one of those 2 components can be renamed using the corresponding procedure.
The alternative solution for renaming the duplicated technical names is to use the ABAP report RENAME_DUPLICATE_ELEMENTS.
3.2 Components with inconsistent definition
Reusable query components which are not found in the element directory table RSZELTDIR are displayed. This situation may cause the short dump 'Exception condition INCONSISTENCY' during accessing the affected component in Query Designer or execution the affected query in RSRT. Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.3 Components without InfoProvider assignment
All reusable query component (except variables) should be assigned to a particular InfoProvider. This assignment is located in the table RSZCOMPIC. When the record is not found in this table, the affected component may become not available in Query Designer in the corresponding InfoProvider. In some cases the error message "Component XXX.. (version A) has no InfoCube assignment". Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.4 Components with empty ONWER field
Reusable components which have empty OWNER field in the table RSZCOMPDIR are accessible by users having $USER setting in the authorization object S_RS_COMP1 (users which are authorized to their own queries or query components). This leads to authorization concept violation.
For error solution the field OWNER in the RSZCOMPDIR should be filled with any value. Execute the corresponding edit mode in order to fill the empty field with user 'SAP'. This will prevent the potential authorization violation for users with $USER setting and will take no effect on the users without this setting.
4. Table RSZELTXREF
The table RSZELTXREF contains all links and dependencies between the query elements within a query or query component.
The following errors can be found:
- missing elements (INCONSISTENCY dump);
- not supported relations between query elements;
- extended RSZELTXREF check.
4.1 Missing elements
Missing elements are those query elements which exist as the dependant objects (field TELTUID) in the table RSZELTXREF, but not available in the element directory table RSZELTDIR in corresponding object version. In case, when such elements are used in any query or other query components (STR, CKF or RKF), this may lead to ABAP short dump with 'Exception condition INCONSISTENCY' error message in query run-time or design-time. Other known symptoms of this error is, that structures, calculated key figures or restricted key figures are not available in an Info Provider in Query Designer during design-time.
The missing elements which are in use in other queries or query components, can not be automatically repaired or deleted without components where those elements are used. In most cases the manual repair operations directly in the DB tables are required. Create an OSS message for SAP component BW-BEX-ET-QDEF for further investigations and creation of a repair plan.
The missing elements which are not in use in any query or query components, can be deleted from the system via corresponding delete procedure. This deletion will not affect any existing query or query component.
ATTENTION: if missing element is variable, it can be repaired in some cases automatically using the corresponding repair procedure. See table RSZGLOBV check 5.1. 'Variables with inconsistent definition' for details.
4.2 Not supported relations between query elements
Some relations between query elements which are not supported and can cause dumps in ABAP or terminations in Query Designer (for example link STR <--> VAR). Such cases have to be additionally investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
4.3 Extended RSZELTXREF check
The extended RSZELTXREF check outputs 2 situations which, in combination with other conditions in the system, may be responsible for slow performance of all operations which involve select from the table RSZELTXREF and resolving the relations between query elements (query load, query generation, expanding of a variable list for corresponding InfoObject, expanding of a list of reusable components in Query Designer,... etc.):
- records with empty INFOCUBE field
- records which are not used in any query or query component
Records with empty INFOCUBE field
The current algorithm of resolving of relations between the query elements uses an optimization which allows to reduce the amount of data selected from the table RSZELTXREF during such operations are query load, query generate, expand a list of reusable components (STR, CKF, RKF) and so on. All relations between query elements within one reusable component based on one InfoProvider 'N' are also located within the same InfoProvider. The system has to select only records where the INFOCUBE field contain the same InfoProvider 'N' and in addition to this all other records where the INFOCUBE field is empty. This is necessary, because in all BW releases below 3.x the INFOCUBE field was not in the RSZELTXREF table and all components created before 3.x release have this field empty. Selection of records with empty INFOCUBE is required in order to ensure the consistency of processed query.
When the number of records with empty INFOCUBE is quite large (50.000 - 1 mln records), any simple operation which require resolving of the relations may take a long time, because those records are always being selected, loaded to Query Designer and processed in the design-time.
Records which are not used in any query or query component
The program makes a virtual attempt to reconstruct the table RSZELTXREF via resolving the relations between all reusable components existing in the system. All records which are not used in any query or query components are considered as non-used records. Usually these are fragments of old queries or other components which are not deleted due to former errors in the query delete algorithm.
The current version of the program contain only information about those 2 issues. See the OSS note 823804 for additional information.
ATTENTION: the extended RSZELTXREF check is recommended when all critical problems with reusable components are resolved and the system clean-up is done (no useless records in the tables, no useless non-executable queries or other affected query component available).
Starting from SP28 for BW 30B, SP22 for BW 31C and SP14 for BW 3.5 the Extended RSZELTXREF check detects and fixes the following situations:
records used in existing queries or query components with empty INFOCUBE field;
records used in existing queries or query components with wrong INFOCUBE assignment;
records with or without INFOCUBE assignment which are not used in any query or query component.
For further check details read the OSS note 859086.
5. Table RSZGLOBV
The table RSZGLOBV contains the definitions and technical properties of the variables.
The following errors can be found:
- variables with inconsistent definition;
- variables with missing or incorrect properties;
5.1 Variables with inconsistent definition. Variable not found in RSZELTDIR/RSZCOMPDIR tables.
The variable existing in the table RSZGLOBV, but not existing in the tables RSZELTDIR or RSZCOMPDIR have inconsistent definition. These situation may return 2 different error messages. When a variable is missing in RSZELTDIR table (or in both together), an attempt to expand a list of variable under a corresponding InfoProvider or a list of text/formula variables will return a message 'Inconsistency in loading...'. All variables which are created for corresponding InfoProvider, text/formula variable are not available. When a variable is missing in the RSZCOMPDIR table only the error message is 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded' in Query Designer.
In both cases the variables can be repaired via the corresponding procedure provided in the program under the technical name (COMPID) corresponding to the name in VNAM field in the table RSZGLOBV with the text 'REPAIRED BY SAP'.
As an alternative solution, when the affected variables which are not used in any query or query component can be deleted directly from the RSZGLOBV table. Both solutions will fix the reported symptoms.
ATTENTION: it is recommended to open a repaired variable in Variable Wizard of Query Designer and to adjust the definition of this variable, when it is necessary.
ATTENTION: deletion of the affected variables missing in the table RSZCOMPDIR is not possible using transaction RSZDELETE. An attempt to delete such variable will return the error message 'Component not found'.
5.2 Variables with missing or incorrect properties
Several errors can be found within this check. The variables of different type have their own sets of properties. Missing or incorrect properties may cause different error message during execution of a query where such variables are in use. In the case of the affect variables with processing type 'replacement' , the replacement may not work because of the problem.
Each case has to be investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
6. Table RSZELTDIR
The table RSZELTDIR is the main directory table containing all query elements available in the system.
ATTENTION: the RSZELTDIR check may take a long running time depending upon the table size.
The following errors can be found:
- local elements not in use;
- reusable elements not in RSZCOMPDIR table;
- reusable elements not in RSZCOMPIC table;
- structure (STR) without structure members;
- selections or RKF without definition in RSZSELECT table;
- formulas or CKF without definition in RSZCALC table;
- variables (VAR) without definition in RSZGLOBV table;
- queries (REP) without entries in RSRREPDIR table.
6.1 Local elements not in use
Local elements (field REUSABLE = false) which are not used as dependant objects in the table RSZELTXREF. These elements are useless and not accessible from Query Designer. Usually these are fragments of the definitions of old queries accumulated in system because of different problems with save/delete procedures which are not accessible by the end users. The recommended solution is to delete those elements using the corresponding delete procedure.
6.2 Reusable elements not in RSZCOMPDIR table
Reusable elements (field REUSABLE = true) must have a corresponding entry in the table RSZCOMPDIR which contains the definition and properties of this reusable component. An attempt to load such component in Query Designer may cause the error message 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded'. Additional investigations are requires at SAP. Create an OSS message for BW-BEX-ET-QDEF.
ATTENTION: Deletion of such affected components is also not possible using transaction RSZDELETE. An attempt to delete will return the message 'Component not found'.
6.3 Reusable elements not in RSZCOMPIC table
Reusable elements (field REUSABLE = true), except variables (DEFTP = 'VAR'), must have a corresponding entry in the table RSZCOMPIC which contains an InfoProvider assignment for reusable components. When a reusable component has no InfoProvider assignment it may be not available in Query Designer during design-time. Additional investigations are required at SAP. Create an OSS message for BW-BEX-ET-QDEF. In case the affected component is useless, it can be also deleted from the system using transaction RSZDELETE.
6.4 Structures (STR) without structure members
Reusable and non-reusable structures (DEFTP = 'STR') should have dependant elements (structure members). When these structure members are not found a query containing this structure returns the error message 'Element structure not correct' during generation or execution in RSRT or BEx analyzer. The program outputs a query technical name where such structures are used or the technical name of an InfoProvider if the affected structure is reusable and not used in any query. In this case it can be accessed from any query created in the same InfoProvider in Query Designer. The solution is to open the affected structure in using the latest available version of Query Designer and to create the required structure members in order to avoid the error message.
In case, when the affecter structure is local (non-reusable) and is not used in any query, this structure is not accessible by frontend users and can be deleted from the system by corresponding procedure provided in the program.
6.5 Local selection of RKFs without records in RSZSELECT table
Local selections and reusable Restricted Key Figure (DEFTP = 'SEL') usually should have the corresponding records in the DB table RSZSELECT. The program outputs all selections found in the system which have no corresponding records in the RSZSELECT table.
Usually this issue has no impact on the existing queries and produces no error messages. There are 3 possible types of selections within a query:
Normal selection - this selection represents a characteristic in Row, Columns or Free Characteristics area, Conditions or Exceptions. This situation produces no error messages, but the selection is not taken into account by OLAP.
Dummy structure member - structure member type selection can be defined using Query Designer. Such structure member produces no selection and can be used only as place holder within a query. This situation produces no error messages during generation/execution of a query containing a structure with those dummy structure members.
Cell selection - this type of selection is usually used as Cell selection and can be defined using Cell Editor in Query Designer. This situation produces no error messages, but the selection is not taken into account by OLAP.
If it is necessary, the selection definition can adjusted using the latest available version of Query Designer. The affected local selections can be accessed from the queries presented in the WHERE-USED (INFOCUBE/QUERY). The Restricted Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local selection is not used in any query or query components the recommended solution is to delete this selection using the corresponding delete procedure.
6.6 Local formulas of CKFs without records in RSZCALC table
Local formulas (DEFTP = 'FML') or Calculated Key Figures (DEFTP = 'CKF') should contain definition of the calculations in the table RSZCALC. When such definition is not found in the table RSZCALC the queries or query components which include those affected objects can not be generated or executed by OLAP. An attempt to generate such query returns the error message 'The (sub) formula XXX... is not available'.
The definitions of the affected formulas or Calculated Key Figures can be adjusted using the latest available version of Query Designer. The adjustment of a local formula is possible from the corresponding query listed presented in the program. The Calculated Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local formula is not used in any query or query components the recommended solution is to delete this formula using the corresponding delete procedure.
6.7 Variables without records in RSZGLOBV table
Variables (DEFTP = 'VAR') should exist in the table RSZGLOBV. The table RSZGLOBV contains all processing properties and definition of the variables. Query where such variables are used can not be executed without problems.
The repair procedure is not possible, because of missing definition. In case, when such variable is not used in any query, the recommended solution is to delete it from the system in order to avoid potential problems. If the affected variable is already used in other queries or query components, create an OSS message for SAP component BW-BEX-ET-QDEF. Further investigations and possible repair plan have to be created at SAP.
6.8 Queries without records in RSRREPDIR table
Queries (DEFTP = 'REP') should exist in the table RSRREPDIR. The table RSRREPDIR is a header table of generated reports and also a part of the database view V_REP_JOIN which provides data for the BEx Open/Save Dialogs.
A query which does not exist in the table RSRREPDIR is not accessible via RSRT transaction (error message 'GENUNIID not found') and not displayed in the Open/Save Dialogs of fronted applications.
The recommended solution is to delete such queries using the corresponding procedure provided in the program and similar to RSZDELETE.
In some cases the repair procedure is also possible. The success of the repair procedure depends upon the consistency of the affected query, the existence of a valid InfoProvider for this query and some other factors. For repair attempt create an OSS message for the SAP component BW-BEX-ET-QDEF.
hope this helps.

Need a table for analaysis data targets!!!!

Hi,
I need a table in BW/BI system which must have details of the infoproviders
1) How often they are loaded ?
2) whether been used in reports?
It is OK if the information is spread across multiple tables
Thanks,
Ravi

Raj,
Table with Report to CUbe/DSO linkage - RSRREPDIR
Table with Load details - RSODSACTREQ , RSSTATMANPART , RSREQDONE
Arun

Queries on Roles

Hi Friends
How can we identify the quries on a perticular user. Because we have roles on departments wise.
Now i want to identify all the queries that comes under a perticular user.
Regards,
Chama.

Hi
go to table RSZCOMPDIR
enter the user id in the owner Field
it will display the reports created by the user.
Regards
Sri
Also Check with RSRREPDIR Table also.

How to hide BEx reports in archive folders

Hello experts,
Need your advice, we currently have several reports that we want to phase out gradually, but want to keep available in case users would want to use in the few months ahead.
Can you please help confirmif possible to move BEx reports from current infoprovider folders into archive folders and then remove user role access to this folder?
We would prefer this since users currently have access to infoproviders.
I also tried this option seen in one of the earlier blogs but it fails in step 3 since it doesn't accept REP for the Detailed information for DEFTP column (error enter a valid value is shown)
1) Look in table RSRREPDIR with the query technical name. Get the COMPUID value.
2) Go to table RSZELTDIR with the COMPUID value.
3) In table RSZELTDIR, select the Active record (OBJVERS = A) and do Table Entry, Create with Template from the menu. Change the OBJVERS value in the new record to D and save the new record.
4) Go back to the RSRREPDIR table entry. Copy the Active record (OBJVERS = A) and do Table Entry, Create with Template from the menu. Change the OBJVERS value in the new record to D and save the new record.
5) In the RSRREPDIR table, delete the Active record (OBJVERS = A).
Really appreciate your help, thanks!

Hi,
I dont think this is possible.
-Vikram

Query Time Out and Shared Objects

Hi,
I have 2 questions.
1) from st22 i can get the list of users and time out information. But how can I find related query which has been time out by that user ?? as of now i was getting query information from st22 by getting abap program name which starts with "G" and find related query for that from the table rsrrepdir. But recently it is happening that i get abap program which starts with "G" from st22 time out but its not giving me any query information in RSRREPDIR table or by t-code se38.
can anyone guide me how can i get query info from st22 ? we have so many time out occuring in production have to trace that and improve the query performance.
2) 2nd question is - how can i get list of queries which are having shared objects like variables, templates, key figures, structures etc...
is there any specific table or t-code which provides that? we have to delete some queries in prod. but before that we want this list.
A.H.P. I am counting on you extensively for help coz i have seen that you reply to everybody. and i have asked same question in another forum at SDN but no reply !!!
waiting for help...

Hi Bhanu,
thank you for your prompt reply.
well, we dont have woorkbooks atall. we got the inventory list of all queries needs to be deleted in production. we are deleting very very old queries which are not even in used now. i know the variables and str. etc...remains but still needs to know how to find out the queries with shared object. i want that information in hands before i delete anything in dev. system and transport it to prod. so, i will have proof that i didnt delete anything important. hope you understands what i mean and why i need to know this !
i found few tables related to this but cannt relate them and get the info I need. RSRREPDIR, V_ELTDIR_TXT, RSZELTXREF,etc..
where used list in BEx gives us the webtemplates names nothing else. i meant not the shared objects. and if it is giving shared objects info then i guess i am not aware of it coz few queries i tried to check didnt get that info in "where used" list.
in metadata repository ?? i didnt get it!! how can i find queries with shared objects in metadata rep ?

Query definition could not be read BRAIN252

Hi All,
I have faced below issue in staging system after transport. The query is running fine on dev & quality. I can't even find the element in error in the RSZ* tables. Please share if any solution.
Note: I have collected and transport the query again, still I face the error.
During run in RSRT
During query generation in RSRT
Thanks,
Angavai Elangovan

I had quite a similar problem.
The reason was that the records in RSRREPDIR table were duplicated i.e. records for dev, quality and production were not identical.
The solution I found was:
1) SE38 run ANALYZE_RSZ_TABLES
•Select database table: RSRREPDIR
•Object Version: A
Then execute the report
2) On the check report find section Table RSRREPDIR
•View details of this section
•The detail list will contain the queries which are incorrect, and probably your query among them as well.
Then execute: Performing a rep air
You can find more information about ANALYZE_RSZ_TABLES in SAP Note 792779 - Report ANALYZE_RSZ_TABLES

BI Accelerator Project

Hi,
We have BI 7.0. Current database size is nearly 600gb. We have started a new BI project to extract data from IS-U-CCS module. We expect nearly 1TB of data for this new project. Right now we are about to complete the designing phase and start the implementation in our development system. We are going to have many canned reports and many adhoc reports. We are using BO as front end(that consumes BI queries). We have concerns about performance and we are looking for BIA implementation. I have the following questions.
1)We know that data volume is going to be very high. But we don't know at what stage we have to decide whether to go for BIA or not .My question is whether we have to implement the cubes, do test loads and run queries and check the database time and all the event ids 9000,9010 and 9011(selected/transferred) and decide whether to go for BIA or not ?.What is the rule of thumb for selecting BIA?
2)We have to put BIA implementation in our project schedule. Most of the documents tell that BIA is like a Plug and Play installation, as the vendor provides the preinstalled BIA blade servers. What is the approximate time it takes for the delivery of the BIA server and for the configuration of BIA application?. How much resource it requires from the BW team?.
3)Does the latest version of BIA supports DSO/ODS?. Do we require EHP 1 for BI 7.0 for the BIA-DSO/ODS support?.
Thanks in advance.
Thanks.
Raj.

Hi Raj,
Vitaly's article should help you and the BI team a lot before you start.
Here are some free tips/advices i can add to
Before identifying the cubes I recommend the BI team conduct a survey to find out the most wanted cubes from the business - all regions. > For each cube, check the stats for the most frequently running queries and long running queries. > For those queries, check if the queries are spending the majority of the time in DM or OLAP (use rsrt and stats). If DM time is considerable, then BIA can help.
Have a utilty program to update the RSRREPDIR table(the field is nohpa) to exclude queries
Have a utilty program to update the USR05 table(for param id = NO_BIA_USE param value = X) to exclude users
Have a utilty program to delete entries from the table RSDDTREXHPAFAIL (to enable BIA w/o waiting 30 minutes)
Have a utilty program to update the RSDDTREXADMIN table for DONT_IGNORE_BIA_OVERLOAD (in case you're overloaded-per BIA!-, your roll-ups will fail unless you update the entry above with blank)
I am sure there are notes for these tables and maybe some programs, check the OSS notes first please.
Knowing how to use the first 2 tables above not only will help you to run tests in proudction, but also have a better control for the BIA environment. For example; after a BIA version upgrade or BI upgrade you can exclude all users except the BI/Basis teams to test the queries.
Exclude the APD queries, since they create number of paralel process that can cause a big spikes in BIA. Try running one and monitor the BIA from VNC viewer. I think you can exclude them by just excluding the user ALEREMOTE. Also you may consider excludeing other batch queries such as information broadcasting
If you could(sounds like not practical) have a different naming convention for the queries that will go to BIA - like your global reports- and exclude all other queries. In theory any body can create a query in production and can bring down BIA by reading 10 years of data...Yes we allow users to create adhoc queries in production with an allowed naming convention
Aggregates that have navigational attributes will impact the change run, so check the change run log and try to get rid of those aggregates if possible
If time permits, try to reindex all the cubes once a month + reorg and bounce in unix level to have a nice, fresh start. This will help you to lower the number of requests in BIA, also refresh the temp indexes etc.
Also try to restart index services every weekend (it takes a minute). This will refresh the memory on the blades.
Lastly some tips from my recent experince for the basis team;
Adding more/new app servers requires you to evaluate the max nr of conversations parameter(check Note 1070034)
Put a procedure in place to refresh BIA manually for server additions - bia BIA couldn't communicate with the server for an unregistered RFC ( check note 1230345 )
Cheers
Tansu

How to get the role under which a query is published

Hi All.
I want to know how will I know under which role a particular query is published. I have the query name. Please provide some suggestions at the earliest.
Thanks in advance,
Sananda

Hi Sananda,
When you go to RSRREPDIR table selection screen in SE16, you will see 2 'Query' fields. Put your query technical names in second 'Query' field and execute. From the output, collect the values in first 'Query' field (GENUNIID). Take these IDs and put them in AGR_HIER table to see menu roles against these IDs. You can download data from both these tables into excel sheets and put vlookup to find menu roles against query technical names.
Hope it helps.
Thanks,
Abhishek.

How to c which queires r frequently being used

Hi all,
We want to see, which r all the queries r frequently used for reporting purpouse. how to get this?
plz let me know, its very urgent

Pushkara,
You can get some useful statistics about Queries from RSRREPDIR table. Go to SE16 >RSRREPDIR>Enter Info Cube/Multi Provider Name....it will give you all details like Last used user, last used Date etc...
Here are some useful threads about Queries/Workbook usage..
determine the workbooks
table with list of work books
Thanks
BI Consultant

Relationship between Queries and Workbooks

Hi All
I know I should know the answer to this but its been a while since I did my Queries Course.
What is the best way to find out how many Workbooks are connected to a Query.
The reason I am asking is that I have to convert a load of Workbooks from 3.5 to 7.
I have got a list of all queries run in the last year, now I want to make sure I get all associated Workbooks.
Thanks in advance.

John,
Compile a list of all your queries and feed them as a selection to the COMPID field in the RSRREPDIR table.
Take the GENUNIID from the table result and use it as input to the GENUNIID field for the table RSRWORKBOOK. This should give you a list of workbooks associated with your Queries.
Use the above result and feed as input to WORKBOOKID field of table RSRWBINDEXT to get the Workbook Desricptions.
Hope this helps.
-Sid

Access to BEX Query

Hi,
A user has been asking for access for running one of the query in BEX designer.
How do you grant access to a user for running a particular query in designer.
Can some please guide me.
Thanks.

Hi,
If the report is assigned to specific role then you will have to assign that role to the required user then only he will be able to access that query, but if report is not assigned to any role then you will have to give the general developer or read access to user.
Using AGR_HIER and RSRREPDIR tables you can check whether report is assigned to any role or not.
Regards,
Durgesh.

OBJSTAT in RSRREPDIR table

Similar Messages

Maybe you are looking for