Need Query Name at top of 0ANALYSIS_PATTERN Template

Hi, When I run my query using template 0ANALYSIS_PATTERN it shows the query name at the top of the template.
I created a master template with 0ANALYSIS_PATTERN embedded as a WEB TEMPLATE WEB ITEM. When I execute my Master Template it shows the text of the Master Web Template Description. Any way to get it to show the query description instead?
Thanks!

Change the data binding of the text web item to use the Data Provider Description. In this case the description of the query.
Thanks!

Similar Messages

Need To Find Query Name Used In A Bookmark

Hi,
I have a bookmark that is not based off a web template. It was created by running the query on the web and then saving the bookmark from there. We have since forgotten the query technical name. How can I find it out?
(I have tried looking at table RSZWBOOKMARK but it doesn't have any info about the query. And the web template id field is blank since we didn't create the bookmark that way.)
Thanks,
Audrey

Audrey,
We had a similar need recently to report on bookmarks in the BW system by user, query, InfoProvider, etc. We ended up having a custom ABAP developed here to piece some of the information together for a report. In our scenario, the bookmark links were actually being stored in the BW user's favorites, so it took additional linkage to go from there as well.
You may want to look at some of the same tables we had to access here. Try looking at data in the RSZWOBJ table -- the keys to this table would be OBJID (use the RSZWBOOKMARK-BOOKMARKID) and OBJVERS ('A'). Because of the way the data is stored with this, you may have to use ABAP code similar to the one below to get Bookmark info. I took a few snippets of code out of a program to help show this -- here the field WS_INFOPROVIDERID is getting filled with the query name behind the bookmark.
sample working storage below -
DATA:
l_s_id_objvers TYPE rszw_s_id_objvers,
l_s_rszwobj    TYPE rszwobj,
l_sx_bookmark TYPE rszw_sx_bookmark,
WS_DP_LIST     TYPE line of rszw_sx_bookmark-DP_LIST,
WS_INFOPROVIDERID TYPE rszwobj-OBJID.
sample logic for reading RSZWOBJ table ---
l_s_id_objvers-objid   = <wherever you store BOOKMARKID>.
l_s_id_objvers-objvers = 'A'.
IMPORT bookmark = l_sx_bookmark
FROM DATABASE RSZWOBJ(bm)
      ID l_s_id_objvers
      TO l_s_rszwobj.
IF SY-SUBRC = 0.
LOOP AT l_sx_bookmark-DP_LIST into WS_DP_LIST
      WHERE VALUE = 'DP'.
    WS_INFOPROVIDERID = WS_DP_LIST-NAME.
    EXIT.
ENDLOOP.
ENDIF.
Hope this helps... Jody

Query Name in variable pop-up on the web with standard template

While using the the standard template (0QUERY_TEMPLATE or 0ADHOC) the variable pop-up title bar contain the text: "Variable for Ad Hoc Report". Is there a way to cutomize this so for example you are able to show the query name: :Variable for query XXX"?

Hi Mike,
I don't think there is much hope in this area. There was another post on this topic that you can look at:
Re: Web Reporting - Variable Screen - Title of Report

Cube/query name is not available in trx MDXTEST

Hi All
I was trying to use a custom BI query on top of infocube 0CP_SLSC6 as a source for mdx queries. I have set the property Allow External Access To This Query in BEx for the custom BI query. But in trx mdxtest I cant see the cube name in CATALOG list or the query name in CUBE list; However if I select infoprovider for CATALOG then I can see the cube name in CUBE list. Any clue how to sort this out. Thanks in advance
Thanks & Regards
Sudip

I just had the same problem ... this is how I did it:
I don't think you need to enable the query for OLE DB access to use MDXTEST - MDXTEST is just an MDX Query writer helper tool.
To text your query/report you can just use direct entry and paste in the technical name of the query or other object; using Shift+F4 or click on the edit button (the one with the notepad and pencil)... then paste the name.
You can get the technical name of your query/report from the end of the execute string from Favourites e.g.
<prt_protcl>://<prt_server>/<bi_launcher>?QUERY=REP_20100610164528
So from your Favourites, pretend you are going to change your query/report and copy the technical name REP_xxxxx or whatever and paste it into MDXTEST...
Then choose your syntax template and add your rows and columns etc.
Unfortunately our MDXTEST doesn't seem to be working! as I get the error message "during allocate / CPIC-CALL: 'ThSAPCMRCV'"
Which is covered elsewhere ... so I will contact our Admin

Rescue Query name

Dear all,
I need to rescue the names of every Query in my page dynamically.
I'd like to use it in every my page to check the Query ExecutionTime.
How can I rescue the query name?
thanks in advance
Best regards

Yes, but now I have another problem...
If Application.cfm is the first page that CF run... now I need to create a "footer" page that CF run every time when it's finish to load any page...
have you some idea?? :-)
thank you very much... this is my template:
<cftry>
    <cfobject action="CREATE" type="JAVA" class="coldfusion.server.ServiceFactory" name="factory">
    <cfset cfdebugger = factory.getDebuggingService()>
    <cfcatch type="Any"></cfcatch>
</cftry>

<cfset qEvents = cfdebugger.getDebugger().getData()>

<cftry>
<cfquery dbType="query" name="cfdebug_queries" debug="false">
SELECT *, (endTime - startTime) AS executionTime
FROM qEvents
WHERE type = 'SqlQuery'
</cfquery>
<cfscript>
if( cfdebug_queries.recordCount eq 1 and not len(trim(cfdebug_queries.executionTime)) )
   querySetCell(cfdebug_queries, "executionTime", "0", 1);
</cfscript>
<cfcatch type="Any">
<cfscript>
   cfdebug_queries = queryNew('ATTRIBUTES, BODY, CACHEDQUERY, CATEGORY, DATASOURCE, ENDTIME, EXECUTIONTIME, LINE, MESSAGE, NAME, PARENT, PRIORITY, RESULT, ROWCOUNT, STACKTRACE, STARTTIME, TEMPLATE, TIMESTAMP, TYPE, URL, et');
</cfscript>
</cfcatch>
</cftry>

<cfset qQueries = QueryNew("Name, Time, Records, Template, OrarioEsecuzione")>
<cfloop query="cfdebug_queries">

<cfif Max(cfdebug_queries.executionTime, 0) GT 3000>
     <cfset QueryAddRow(qQueries)>
        <cfset QuerySetCell(qQueries, "Name", cfdebug_queries.name)>
        <cfset QuerySetCell(qQueries, "Time", Max(cfdebug_queries.executionTime, 0))>
        <cfif IsDefined("cfdebug_queries.rowcount") AND IsNumeric(cfdebug_queries.rowcount)>
         <cfset QuerySetCell(qQueries, "Records", Max(cfdebug_queries.rowcount, 0))>
        <cfelseif IsDefined("cfdebug_queries.result.recordCount")>
         <cfset QuerySetCell(qQueries, "Records", cfdebug_queries.result.recordCount)>
        </cfif>
        <cfset QuerySetCell(qQueries, "Template", cfdebug_queries.template)>
        <cfset QuerySetCell(qQueries, "OrarioEsecuzione", TimeFormat(cfdebug_queries.timestamp, "HH:mm:ss.SSS"))>
</cfif>
</cfloop>
<cfif qQueries.recordcount GT 0>

    <cfif config EQ "PRODUZIONE">
<cfset alert_to = mail_sviluppo>
    <cfelse>
        <cfset alert_to = mailtest>
    </cfif>
    <cfmail to="#alert_to#" from="#frommail#" password="#pwd_server#" server="#mailserver#" username="#login_server#" port="#porta_SMTP#" subject="Problemi nell'esecuzione di query" type="text" charset="iso-8859-1">
Sono stati riscontrati problemi sulle seguenti query:
<cfloop query="qQueries">
- Query: #qQueries.name# (Tempo: #qQueries.time#ms):
n.Records: #qQueries.Records# -- Template: #qQueries.template#
</cfloop>
    </cfmail>
</cfif>

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.

How to find a query name from report name

I have a report in my system with the name AQICMM==========P2============ . I believe this was created from a query. How to find the query corresponding to this report ? I need to change the logic for certain columns of the report. How to know if this was created from SQVI or SQ01 or any other transaction.
THanks.

Found it..Query name is P2. It was in a different query area..Standard area and not custom area where I was initially looking at.
Edited by: Shareen Hegde on Aug 22, 2008 5:14 PM

Need query to find out whether exactly 2 columns are used in any index ?

Suppose i have two columns ID and Status (or any number of columns ) belongs to table customer...
Now I want to create below index
Ex. create index test1 on customer (ID , Status )
But before creating this index i want to check that whether there is already index on these 2 columns ? May be by other name ?
Need query for this.
Plz help.

Hi Shubhangi,
Your requirement is very difficult to fulfill , i have made an attempt to replicate your reqrmnt & write a query wherein you need to compromise on few things , let us see if it works for you
Supply table_name/owner & Number of column on which you want to find indexes
e.g.
select distinct INDEX_NAME,column_name
from dba_ind_columns
where index_name in (select distinct index_name
from dba_ind_columns
where table_name='&table_name'
and table_owner='&owner'
having count(column_name)=&column_count group by index_name);
Enter value for table_name: ADDRESS
Enter value for owner: ASAP
Enter value for column_count: 2
INDEX_NAME COLUMN_NAME
FKIDX_AD__SF_ST_FO SF_STRUC_FORMAT_NM
FKIDX_AD__SF_ST_FO SF_TYPE_NM
SQL> /
Enter value for table_name: ADDRESS
Enter value for owner: ASAP
Enter value for column_count: 3
INDEX_NAME COLUMN_NAME
FKIDX_AD__SF_ST_FO_1 POSTAL_CD
FKIDX_AD__SF_ST_FO_1 SF_STRUC_FORMAT_NM
FKIDX_AD__SF_ST_FO_1 SF_TYPE_NM
Thanks,
Ajay More
http://moreajays.blogspot.com

POWL 'Query Name is already open in another session'

Hi there,
Our users are constantly getting the following error message when using POWL's in the Portal.
Query <Name> is already open in another session' (POWL 016)
The error occurs when a user tries to refresh a query and the query is locked in another session (ENQUEUE_EPOWL_QUERY_EDIT Exception foreign_lock).
There are various root causes to why this error happens, system, application, communication etc. The one I am seeking help on occurs when the user abruptly terminates the browser session (forced or unforced) and the orphaned session is unable to close properly leaving the POWL query locked.
We are currently informing the users to
1.) close all windows and reload the worklist.
and in certain circumstances
2.) log off and log on again
The above workaround doesnt always solve the problem. We are reluctant to give users access to SM12.
Has anybody encountered something similar, if so were their specific settings, notes, code etc. which needed to be implemented?
Cheers
John P

Try the following steps
Please implement the note 1836401 and the prerequisites 1873487,1902580 .
Identify the POWL Query name and set the refresh type as: 'refresh on every LIST VISIT'.
Important: Run the report POWL_D01 and remove the result list of your POWL
Application ID, it#s very important because the cache would still contain the old refresh type and will not recognize the new refresh type, please run the report at first for one user ant test the behaviour, if it works run it for all other user
Pass the application parameter REFRESHA with value X to your POWL application. After that retest your issue, it should work. if not implement the note 1975395 and its prerequisites and test again
Best regards,
Robert.

Editing the Query name for all reports in PRD.

Dear All,
I have created 25 reports using Query Designer.We have moved all the reports to BI Production. And Clients are using these reports using the Tool Bex Analyser.
Every time they are navigating through open Query -> Info Areas -> Data targets and Query.
Instead of going this way, is there any other way to Open a query easily.
And they wants to modify the Report name and the Technical name for all the reports. Can we able to edit the Query name for all reports, or do i need to go for SAVE AS for all querys.
Pls Suggest.
Thanks,
Ram

Hi Ram,
1. For the first question; if it user specific query then ask the users to save them at the FAVORITES so that there is no need to go to the dataprovider specific.
Or they can create the reports as favorites user menu screen of that particular user.
2. In order to change the technical name and description of the queries goto RSZC t-code> give the source and target infoprovider as same> select queries>click on the reports>click on transfer selections-->
Then you get a screen to change the description and technical name.
But this is pertained to Infoprovider level.
You can see all the reports on the infoprovider (cube/ods).
Hope you understood.
Regards,
Ravi Kanth

WAD: How-to get query name and pass to URL

Hi,
The task: In a BI 7.0 web template - get the technical query name and use that to open a URL in the format http://<MYURL>&DOCUMENTATION=<QUERYNAME>. So:
1) User clicks an icon
2) Get technical name of query
3) Open the documentation for that query using a URL
How can this be done? Do I have to use the Custom Extension web item and implement a new class using the interface IF_BICS_CONS_WEBITEM_CUST_EXIT? If so, do you have an example of how this can be done? OR even better is there an easier way to accomplish this?
Thanks in advance,
Jacob

Hi Daniel,
you could get the query name in ABAP code, also. Here is a snippet from the execute method. The Query name should be in l_sx_view at the end.
best regards
Arne
TYPE-POOLS:
rrx1.
DATA:
l_string TYPE string,
l_xml TYPE string,
l_xml_xstring TYPE xstring,
l_sx_view TYPE rrx1_sx_view,
* Line Feed, CR
c_lf TYPE string,
l_h_lf(2) TYPE x VALUE '0D0A',
l_r_conv TYPE REF TO cl_abap_conv_in_ce.
* Get the line feed and carriage return for unicode
l_r_conv = cl_abap_conv_in_ce=>create( input = l_h_lf ).
l_r_conv->read( IMPORTING data = c_lf ).
DATA:
l_t_data_providers TYPE cl_bics_cons_webitem_util=>tn_t_data_provider,
l_s_data_providers TYPE cl_bics_cons_webitem_util=>tn_s_data_provider,
l_r_variable_container TYPE REF TO if_ixml_node.
CLEAR e_xml.
TRY.
*     All data passed to the webitem exit is hold in I_XML using XML.
*     The XML is UTF-8 encoded. You can convert the UTF-8 xstring
*     to a simple ABAP string by calling the following method:
*     ==================================================================
      CALL METHOD cl_bics_cons_webitem_util=>utf8_xstring_2_string
        EXPORTING
          i_utf8_xstring = i_xml
        RECEIVING
          r_string       = l_xml.
*     The XML includes sections about the used data provider and about the
*     variable container. The following method parses the XML and
*     provides the IF_IXML_NODE instances for data providers and for the
*     variable container.
*     ==================================================================
      CALL METHOD cl_bics_cons_webitem_util=>parse_xml
        EXPORTING
          i_xml                  = i_xml
        IMPORTING
          e_t_data_providers     = l_t_data_providers
          e_r_variable_container = l_r_variable_container.
* 01 Get name of first Data Provider
      READ TABLE l_t_data_providers INDEX 1 INTO l_s_data_providers.
      CALL TRANSFORMATION bics_cons_webitem_filter_by_dp
      PARAMETERS dataprovider = l_s_data_providers-name
      SOURCE XML i_xml
      RESULT XML l_xml_xstring.
      CALL METHOD cl_bics_cons_state_converter=>convert_xml
        EXPORTING
          i_xml     = l_xml_xstring
        IMPORTING
          e_sx_view = l_sx_view.

No authorization for the component (query name)!

Hello all,
when i am publishing the query in web, the following error message is displayed!
"No authorization for the component (query name)!"
i had installed and configured everything here, so the person responsible for authorization is none other than me. what i shud do now? shud i add any other authorization profile to the username created? or still any configuartion is required?
please let me know!
Thanks,
Ravi

Hi ARK,
thanks for the info.
i had assigned SAP_ALL and SAP_NEW profiles to the user.
let me say clearly that when i am executing the Query in the designer it is working fine,no issues in Bex browser too. but when i want to publish safely exexuted query in web (clicking the button publish the query in web) i am getting the above mentioned error!
do suggest me what is the authorization profile that is needed to serve my purpose?
hope this time i am clear!
Ravi

Get query name by program name

Hi experts,
Someone built a query A, and generated it to program B.
Now I need update query A, but I only know program B. How to get the query name by program name?
Many thanks.

Check the page 14 in [this document>>|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40bec8da-4cd8-2910-27a9-81f5ce10676c?quicklink=index&overridelayout=true]

Find query name based on workbook id and vice versa

Hi,
I need to developed a progarm in which user can enter Query name ( tech name ) and it should display all workbooks releated to it and vice versa .
Is there any tables which stores this relationship.?
Wating for response.
Thx in advance .
Regards
Nilesh

hi Nilesh,
Table RSRWORKBOOK WORKBOOKID, GENUNIID is the query ID;
goto RSRREPDIR for detail query properties
(query belongs, in bex analyzer, right click cell 'properties', tab 'information' - query id)
Queries in Work Book
determine the workbooks
table with list of work books
hope this helps.

Query Related to TOP-OF-PAGE Overflow

Hi All,
I had a Different query,
The selection screen input value we pass we need to print on TOP-OF-PAGE...
I did fine and when its get overflow like exceeding page its going to short dump...
exp:/ i have 100 records.
i am printing on top-of-page...
it prints only 37 records...
Can anyone guide me how to print the continous text
Thanks and Regards,
Krishna.

Hi Friends,
I have declared as...
No standard page heading line-size 132 line-count 100.
But it is printing upto max 37 lines...
Its not taking more than a page
Can any more tries....
Thanks and Regards,
Krishna.

Need Query Name at top of 0ANALYSIS_PATTERN Template

Similar Messages

Maybe you are looking for