Table for variables of a query

Hi,
I want to find the list and details of variables used in all the queries built on a multiprovider. Can any one plz help in giving the table name whcih give the details of
variable name, Type(userexit/manual input/replacement path), Details(ready for i/p) etc.
Is there any table which gives the details of such information.
Regards,
Geetha

Hi Srini/Shanti
Thanks for your valuable inputs. The above table gives me the details of a particular variable if i know the variable name.
But my requirement is something different, Let me be more clear on it,
I have some 70 queries built on my multiprovider. Now there is some requirement where i have to take the list of all the variables used in those 70 queries. I have limited time to open each n every query and search n make a list of variables and their types.
So i need some help on the table whcih can give me the details of all the list of variable used in the queries.
Thanks,
Geetha

Similar Messages

Table for variable

Hi gurus,
Where can I find the definition of the variable in my queries ... in which table are they stored ?
Thanks in advance
Aleksi

Hi,
RSZGLOBV is table for variables.
For variable definition:
1.Open any Query in Query designer
2.in lafet panel,navigate to required characteristic
3.Expand it(click on + sign)
4.Expand 'characteristic value variables
5.From context menu of variable-->Edit.
It will show variable definition.
or
right click on a characteristic(if variable is being used in Query)>restrict>click on 'variables' tab>right click on required variable->change
Thanks
Message was edited by: Murali

Table for 2way,3way matching .query to generate invoice with 2 ways matchin

hi
table for 2way,3way matching .query to generate invoice with 2 ways matching
plz help me
thanks

Hello John, I put the (1,2,3) list in the query to show it works with multiple invoices.
You should comment out the conditions:
select a.invoice_no, b.child, sum(a.amount) from invoice_detail a,
select
child,
decode (instr(scbp,'.'),0,scbp,
substr(scbp, 1, instr(scbp,'.') -1)
) starting_child
from (
select ltrim(sys_connect_by_path(child,'.'),'.') scbp,
child from
element_relation
start with child in (select element_id from invoice_detail /* where invoice_no in (1,2,3) */)
connect by child = prior parent
) b
where a.element_id = b.starting_child
/* and a.invoice_no in (1,2,3) */
group by a.invoice_no,b.child
order by 1,2to show it works for all invoices
regards, Tony

External Table for Variable Length EBCDIC file with RDWs

I am loading an ebcdic file where the record length is stored in the first 4 bytes. I am able to read the 4 bytes using the db's native character set, ie;
records variable 4
characterset WE8MSWIN1252
data is little endianBut I have to then convert each string column individually on the select, ie;
convert(my_col, 'WE8MSWIN1252', 'WE8EBCDIC37')If I change the character set to ebcdic;
records variable 4
characterset WE8EBCDIC37
data is little endianI get the following error reading the first 4 bytes;
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-29400: data cartridge error
KUP-04019: illegal length found for VAR record in file ...We can not use the ftp conversion as the file contains packed decimals.
There are other options for converting the file but I am wondering if was able to get an external table to read a native ebcdic file without a pre-process step.

I am loading an ebcdic file where the record length is stored in the first 4 bytes. I am able to read the 4 bytes using the db's native character set, ie;
records variable 4
characterset WE8MSWIN1252
data is little endianBut I have to then convert each string column individually on the select, ie;
convert(my_col, 'WE8MSWIN1252', 'WE8EBCDIC37')If I change the character set to ebcdic;
records variable 4
characterset WE8EBCDIC37
data is little endianI get the following error reading the first 4 bytes;
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-29400: data cartridge error
KUP-04019: illegal length found for VAR record in file ...We can not use the ftp conversion as the file contains packed decimals.
There are other options for converting the file but I am wondering if was able to get an external table to read a native ebcdic file without a pre-process step.

To accept all date formats for variables

Hi,
I am getting a vadidation message on refresh of a query on entering European date format in the selection criteria "Please enter value in permitted format for variable XXXX"
I need date to accept all date formats for variables to execute query.
Currently US date format has been accomodated, On entering European date format i get the above validation message.
Please suggest how do i supress this validation message or any other thoughts on the same.
If anyone experienced the same before or applied any notes plz send the SAP Note number for the same. I am currently on BW 3.5.
Message was edited by:
tyson m

tyson,
why dont you control the date display through the user creation / user details option - then your date entries should sort themselves out.
Arun

How to find out query name in customer exit for variables

We use the same customer exit variable in different queries. In the customer exit we want to find out, which query has called the customer exit. With the technical query name we want to read a master data table entry.
e.g. If we come from query ZG1_TEST1 we want to use selection sel1
Query name | selection
ZG1_TEST1 | sel1
ZG1_TEST2 | sel2
How can we find out the query name in the customer exit for variables?
Thanks for your help,
Evi

Hi Evi,
check out the structure I_S_RKB1D in your exit. It contains the query.
Siggi

How to override security for table access when using SAP Query?

We have a number of infosets which use table join between PA0001 and CATSDB table. To execute a query based on such a query you would need access to table auth group PA through S_TABU_DIS. This was earlier not a problem as SAP query was earlier used by support staff and not end users. We do not want to give S_TABU_DIS with to end users as this amounts to givin them access to all PA tables.
The generated code for the query checks for the condition
"%rtmode-no_authchk = space"
before going for the authorization check.
Thus, ideally the authorization check for an InfoSet can be skipped if we can pass X for this variable from the InfoSet definition. Is there a way to do this?
Would appreciste any inputs to help suppress the authorization check at this point. Thanks.....

>
Julius Bussche wrote:
> Perhaps you could replace it with a class of your own (transaction SE24)?
>
> I have not tried to do this; it was just a thought.
>
> Kind regards,
> Julius
unfortunately this does not work. SAP saw fit to 'hard-code' the implementation of the interface in RSAQEXCE:
(only parts of that abap displayed here).
170 data: iref type ref to if_query_tab_access_authority.
1107 *       FORM AUTHORITY_BEGIN
1112 form authority_begin using p_auth_classname type AQS_CLSNA.
1119   perform authority_init using p_auth_classname.
1120   call method iref->access_authority_begin.
well for my part (searching a solution for a query on LTAK, wanting L_LGNUM as an object) i'm out of ideas. i shall have to modify SAP-standard and disable the class and do my own coding in the info-set. no other possibility - i cannot allow S_TABU_DIS for group LA and even if i did, what help would it be - i would have to allow that to all companies in that client having WM - and that would be literally all - i need LGNUM here!

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.

Error while running a query-Input for variable 'Posting Period is invalid

Hi All,
NOTE: This error is only cropping up when I input 12 in the posting period variable selection. If I put in any other value from 1-11 I am not getting any errors. Any ideas why this might be happening?
I am getting the following error when I try and run a query - "Input for variable 'Posting Period (Single entry, mandatory)' is invalid" - On further clicking on this error the message displayed is as follows -
Diagnosis
Variable Posting Period (Single Value Entry, Mandatory) is used as a lower limit (X) and an upper limit () in an interval selection. This limit has the value #.
System Response
Procedure
Enter a different value for variable Posting Period (Single Value Entry, Mandatory). If the value of the other limit is determined by another variable, you can change its value also.
Procedure for System Administration

OK.
Well, if the variable is not used in any interval selection, then I would say "something happened to it".
I would make a copy of the query and run it to check if I get the same problem with period 12.
   -> If not, something is wrong in the original query (you can proceed as below, if changes to original are permitted).
If so, then try removing the variable completely from the query and hardcode restriction to 12.
   -> If problem still persists, I would have to do some thinking.
If problem is gone, then add the variable again. Check.
   -> If problem is back, then the variable "is sick". Only quick thing to do, is to build an identical variable and use that one.
If problem also happens with the new variable, then it's time to share this experience with someone else and consider raising an OSS.
Good luck!
Jacob
P.S: what fisc year variant are you using?
Edited by: Jacob Jansen on Jan 25, 2010 8:36 PM

URGENT HELP Required: Solution to avoid Full table scan for a PL/SQL query

Hi Everyone,
When I checked the EXPLAIN PLAN for the below SQL query, I saw that Full table scans is going on both the tables TABLE_A and TABLE_B
UPDATE TABLE_A a
SET a.current_commit_date =
(SELECT MAX (b.loading_date)
FROM TABLE_B b
WHERE a.sales_order_id = b.sales_order_id
AND a.sales_order_line_id = b.sales_order_line_id
AND b.confirmed_qty > 0
AND b.data_flag IS NULL
OR b.schedule_line_delivery_date >= '23 NOV 2008')
Though the TABLE_A is a small table having nearly 1 lakh records, the TABLE_B is a huge table, having nearly 2 and a half crore records.
I created an Index on the TABLE_B having all its fields used in the WHERE clause. But, still the explain plan is showing FULL TABLE SCAN only.
When I run the query, it is taking long long time to execute (more than 1 day) and each time I have to kill the session.
Please please help me in optimizing this.
Thanks,
Sudhindra

Check the instruction again, you're leaving out information we need in order to help you, like optimizer information.
- Post your exact database version, that is: the result of select * from v$version;
- Don't use TOAD's execution plan, but use
SQL> explain plan for <your_query>;
SQL> select * from table(dbms_xplan.display);(You can execute that in TOAD as well).
Don't forget you need to use the {noformat}{noformat} tag in order to post formatted code/output/execution plans etc.
It's also explained in the instruction.
When was the last time statistics were gathered for table_a and table_b?
You can find out by issuing the following query:select table_name
, last_analyzed
, num_rows
from user_tables
where table_name in ('TABLE_A', 'TABLE_B');
Can you also post the results of these counts;select count(*)
from table_b
where confirmed_qty > 0;
select count(*)
from table_b
where data_flag is null;
select count(*)
from table_b
where schedule_line_delivery_date >= /* assuming you're using a date, and not a string*/ to_date('23 NOV 2008', 'dd mon yyyy');

Standard table for finding query where used list

Are there any standard tables available to find the list of web templates, bex reports and views using a particular query?
i.e if i have the query name i should be able to find out where all it is being used.
Thanks,
Archna

Hello,
You have to join multiple tables to achieve this, here we go
FOR QUERY Related Information
RSRREPDIR - Directory of all reports (Query GENUNIID)
Choose Type of a reporting component -> REP
Tips :
Choose Type of a reporting component -> QVW for query view
SE11 -> RSZ* -> F4 gives you all tables related to queries
For WORKBOOK Related Information
Use the FM RRMX_WORKBOOK_QUERIES_GET to get the queries in a workbook by selecting the workbook ID from table RSRWORKBOOK
Tips :
SE11 -> RSRWB* -> F4 gives you all tables related to workbooks
SE37 ->RRMX_WORKBOOKS* -> F4 gives you all the FM related to workbooks
For Webtemplate Related Information
Choose the dataprovider for query / view ID.
SE11 -> RSZWOBJXREF - Structure of the BW Objects in a Template
Also see,
SE11 - > RSZWTEMPLATE - Header Table for BW HTML Templates
Thanks
Chandran

How to edit the properties for existing variables in BEX query, so that I can get multiple input selections

Dear fellow developers,
I'm trying to edit an existing variable using BEX query, so that it can allow multiple input selections.
As you can see in the screenshot attached, the option is selectable during creation.
However, during editing of an existing field, this field (Details -> Basic Settings -> Variable Represents) is not selectable.
Does anyone knows why, and how to remedy this?

Yes you can do it at the table level.
Go to SE11 enter table name as RSZGLOBV.
Enter the technical name of variable in VNAM field..You need to change the value in VPARSEL column.
Please make sure to get the where used list of this variable so that you can know the impact,if something goes wrong.
Also change it in DEV and then transport across the landscape.
PS:Same thing has been described in this blog as well
Changing BI variable parameters
Regards,
AL
Message was edited by: Anshu Lilhori

Querying CMS tables for users' security, history & favorites

Hello,
We are running BOBJ over a BW environment, and we've been asked to help design a Webdynpro interface that reads a user's security credentials in both BW and BOBJ servers and pulls in all reports, Bex or BOBJ, that they have access to.
To do this, we would need to query the CMS tables for:
All reports a user is authorized to view
Groups a user is associated with
User's History
User's Favorites
Does anyone have suggestions? I've researched Query Builder, but I'm not sure if it can help us, as it accesses three virtual tables instead of the physical tables in the CMS. The option I am guessing we will need to use is SDK.
I'm fairly new to both BW and BOBJ, so any advice is appreciated.
Thanks
Scott

Hello Scott,
Did you check the possibility of using Audit universe and reports? Please check below link for some useful sample files.
http://scn.sap.com/docs/DOC-53904
Regards,
Nikhil Joy

Tables for Fiels Fixed Value and Variable Value

Hi,
Can any one tell me where the actual fixed and variable costs are stored in which table and also the planned costs. I have checked it, but it is showing RKPLN as data structure. We are doing development report where in standard Cost Center Report we need to have break up of fixed and variable cost. Please guide me where exactly these fields are stored in which table. its very urgent.

Hi,
In regard to the tables for planned data please do a search of the forum as this question has already been asked a few times. E.g. here:
CO PLANNING TABLES
In regard to fixed / variable actual costs: these are not stored in separate tables. If a posting contains fixed and variable portions, for example postings resulting from splitting (KSS2), then the fixed portion is stored in the COEP- WKFBTR (line items) and COSS-WKF* fields (summary items). Please observe SAP note 192107 on this issue.
Regards
Karl

Table for query technical information

i need the table from where the LAST REFRESHED DATE in the technical info of a query is taken.
i have written this little piece of code on table RSMDATASTATE which changes the last_changed field.
DATA TAB LIKE RSMDATASTATE occurs 0 with header line.
data v(14) type c.
concatenate sy-datum sy-uzeit into v.
*concatenate v znewdate+0(4) into v.
data znewdate like RSMDATASTATE-last_change.
ZNEWDATE = '20080101073200'.
*znewdate = v.
break-point.
SELECT * FROM RSMDATASTATE INTO TAB WHERE
INFOCUBE in ('PBUDPLAN', 'PSPL',
'PGFS_HR', 'PGFSWBS2', 'PEXPS', 'PCCA_C11','PCCA_C11',
'MOR_HRS', 'DFIAR_C03').
append tab.
endselect.
*write tab-infocube.
loop at tab.
move znewdate to tab-last_change.
modify RSMDATASTATE from tab.
endloop.
this seems to be having no effect on the technical info when i run the query.
i believe there r these rsz* tables, but i couldn't find the last refreshed field their.

Hi,
Check this table for the date.
RSZCOMPDIR give Query tech name in place of COMPID.
Also tables RSBBSQUERYDIR and RSBBSQUERYT will have data on query and query texts respectively.
Regards
Karthik

Table for variables of a query

Similar Messages

Maybe you are looking for