Missing BW Queries

Hello all,
I am facing an issue where BW queries are missing. They are there and active in table RSZCOMPDIR, but are not retrievable in the Query Designer or the Analyzer. If I try to recreate them in Query Designer, it won't let me because the system recognizes that the technical names exist already. Has anyone encountered this before?
Thanks,
Chad

All,
Thank you for your answers. I was still unable to run the queries in RSRT. I went into RSRREPDIR and created "dummy" entries, which were copies of the "M" records that did exist. Creating Active records allowed me to open the queries in Designer. From there, I did a series of Save As and Deletes to replace the manually edited records with generated ones when I saved. Then, I went to RSRT and directly generated all queries against that cube. I will transport to QA and hopefully didn't cause a massive ref integrity issue among the query tables!
Points assigned !

Similar Messages

Urgent! Hierarchy Nodes Missing in Queries

Hi,
For cost center hierarchy, some nodes r missing in the Query. I checked in the cost center hierarchy tab page. i could see all the nodes in 0Costcenter and as well as in source system. How can i get all the hierarchies nodes. what exactly the problem. why some nodes r missing.
please respond me immediately if any body faced with same kind of problem.
Nagesh.
Message was edited by: Nagesh Ganisetti
Message was edited by: Nagesh Ganisetti

could u please confirm any body... Hierarchy node will be displayed only when relevant Transactional data si available?
for my costcenter hierarchy, Somes nodes r missing.
plz guide me.
Nagesh
Message was edited by: Nagesh Ganisetti

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.

Preformance Tuning assistance

Greeting all,
Using: Oracle 10.1.0.5.0
I seem to be having a bit of a problem wiht the length of time my queries take to run.
I'm reading the Preformance and Tuning manual, but am not having much luck ( making next to no since)
I ran the Hit/Miss ratio queries I found that were off linked in another post and they seem to be fine, but over the past month or two, queries that used to take 2 - 3 minutes to run are now taking 15 - 20 minutes. I've tried playing around with some hints, but they dont seem to do anything to help speed up the process. Any thoughts or idea would be muchly appericated.
-Joseph

Did you do a sql trace on the queries and used tkprof to analyze what is taking so long?
http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96533/sqltrace.htm#1018

Can we edit the System Report queries to add some missing fields ?

Hello,
I'm using SAP Business One 2005 A and I was wondering if there was a way to edit the system report queries. Sometime, I'm only missing calculated fields in the existing report. Something as easy as the difference between 2 dates is not working with the formula fields.
Instead of rewriting everything, could we simply see that original query and edit it to add the missing fields ?
I don't like the fact I can't add my own created report from a query in the main menu. Since I couldn't do anything with the Backorder reports by default, I created mine with my own SQL query. Can't I replace the existing one with my own ?
Thank you
Daniel Gagnon

Hi Daniel,
You can edit a system query but then you can only save it as a user query (ie you cannot overwrite the system queries).
User queries can't be placed in the Main Menu using the standard GUI though you could add them to the User Menu tab so your users can get to them easily. I think to add them to the Main Menu would require the development of an add-on that updated the Main Menu and triggered the running of the query when the user clicked on the menu option.
The other thing to look at is using XL Reporter for your reports rather than the Query Generator. With XL Reporter you can automatically add reports to the main menu.
Kind Regards,
Owen

Am I missing something regarding database queries from BPEL?

Hi,
I'm trying to execute what I would think is a simple query from within a BPEL process against an Oracle 10g database.
I have a root table, meter_reading that has an id, a time, a value, and a foreign key to a meter_reading_type table with a simple id-name-description format.
How do I create a PartnerLink in BPEL that queries for the last reading of a particular type? The SQL is easy. The problem is that with the relationship, I can't find the proper format for a pass-through query so that I can do the subselect AND the select by type (name column).
Also, is it possible with the BPEL PM/OC4J combination to output the queries being generated from Toplink?
I've looked through the toplink docs, but they seem to refer to doing this in Java, not in the toplink_mappings.xml file.
Any help would be appreciated. If I'm missing something obvious, please point it out.
Thanks for your time,
Chris

I am guessing from the examples and from looking around that the only solution to this complexity is stored procs and functions. What happens if you're not allowed to use them? Seems like an awkward part of a product that is owned by Oracle.
C

Continual library cache misses in trace file for spatial queries

Hi all,
Could somebody explain to me how the SQL parse engine works for spatial queries.
My understanding is that Oracle creates a hash value for SQL that is parsed with no errors. This hash value is then stored in the library cache ready to be matched against other incoming SQL statements. This provides one of the main reasons for using parametising SQL in languages such as PL/SQL, .Net etc and improves performance on query intensive applications.
However i have noticed that for spatial, any queries except for refreshes of identical ones already sent, the SQL engines re parses the query. This can take upto 0.2 seconds which is causing a performance bottle neck.
When looking at the full trace file of a single spatial query using SDO_FILTER with a query window the amount of additional internal queries that are performed is quiet a lot. Are these additional queries included in the total parse time?
I am wondering why for spatial queries the only way to get a hit in the library cache was to refresh an exact same SQL that had been previously sent?
Thanks
Daniel

Those additional internal queries are not included in the parse time,
if they are used in the execution time.
Edited by: yhu on Mar 4, 2011 10:52 AM

Missing functions in DW CC - insert Spry and •Select Modify Media Queries.

In DW CC under the "insert" menu there should be "spry" not there
in Modify, there should be "media Queries" not there
Are these in a new place? can't fid this stuff

Pure CSS Drop-Menu
http://jsfiddle.net/NancyO/zN7fU/
CSS3 Dropdown Menus
http://www.red-team-design.com/css3-dropdown-menu
PVII's Pop-Menu Magic3 (commercial DW extension)
http://www.projectseven.com/products/menusystems/pmm3/index.htm
jQuery Superfish
http://users.tpg.com.au/j_birch/plugins/superfish/
jQuery MegaMenu 2
http://www.geektantra.com/2010/05/jquery-megamenu-2/
jQuery MeanMenu (responsive on mobile)
http://www.meanthemes.com/plugins/meanmenu/
Nancy O.

Invoice document missing in MCSI report

Hi Friends,
This is regarding missing invoice documents in MCSI report in our production system.
it was found that two invoice document numbers for a customer were missing where as these two documents are being displayed in BW report.
I have checked in Info structure table through SQVI query and found that these invoice are not available. STAFO field in VBRK table is updated for these two invoice documents.
Can anyone tell me what is the process to analyse the issue and how to update only those two missing invoice documents in MCSI report (Infostructure).
Regards,
Praveen.

Hi,
Thanks for your immediate response....
- Doc. statistics group @ Invoice type / item category could be missing
- At the time of execution of report, these settings might not be in place i.e. these doc type / item cat- may not relevant for statistics.
The above points you have mentioned are not valid as there is no new configuration made and further this is a support project.
I hope the third point which you have mentioned as below is a valid one.
- Proper updation of info structure might not be done.
As per this message, I understood that there was no proper updation of infostructure for those two invoice document numbers. Further, to update two invoice documents in infostructures, we need to run transaction code OLI9.
Can you please comment on my below queries:
- Can the transaction be run in live system during any time?
- Is there any impact on other invoice data in infostructures?
- If the transaction is executed, all the current infostructures get updated with correct invoice data?
- What is the impact of executing Txn - MCVV. Does this transaction only simulates and gives the log on updation of invoice document? or it also adjusts/ updates any data in system?
Thanks & regards,
Praveen.

Very urgent Enhancement category for include or subtype missing

HI all;
I am currently on BI 7.0 release
I have a cube A that activated in Development. I transported cube A to Staging get the following error
Enhancement category for include or subtype missing
Enhancement category for include or subtype missing
No active nametab exists for /BIC/DZIP_INT9
Termination due to inconsistencies
Table (Statements could not be generated)
Flag: 'Incorrect enhancement category' could not be upda
Enhancement category for table missing
Enhancement category for include or subtype missing
No active nametab exists for /BIC/DZIP_INTP
and the cube couldn't activate in staging.
I re-transport this cube A a few times with difference option of grouping and still no luck.
in Development, i copied cube A to cube Aa, then transport new cube Aa to staging, then everything went ok. the new cube Aa is activated in staging area.
I couldn't use the new name Aa since all the queries using the A name.
Is there any possible solution that could help?
Thanks.
Rainnie

jj

BT Vision + box ( black box ) - Missing the end o...

Fitted new BT Vision + box to allow me to have BT Sport in August 2013 . I don't have Infinity as my house doesn't have a Fibre Cabinet yet . All is working OK apart from we regularly miss the end of programmes which have been set up to record . I never had this issue with the Silver BT Vision box for the many years I have been using BT Vision. Im pretty sure lots of other people have this issue , can someone advise of a fix for this or is the New BT Vision + box not up to the job or is there another explanation . I rang technical helpdesk which was offshore only to be told sounds like an issue with our Freeview signal missing the end of programmes .
Mike in Dundee

Hi 802502696,
For help with this issue check out this link
If you're still having problems after following this advice reply back on this thread.
Cheers
Robbie
BTCare Community Mod
If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
We are sorry that we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

InfoStore is missing Indexes, database corrupt

Recently, we added two new Crystal users to our AD domain. Following the usual procedure, we went into the Crystal Management Console to add them to Crystal. (We go to Authentication, then the "Windows AD" tab and click the "update" button.)
We were prompted with the Error:
Error updating Windows AD authentication properties: The object already exists in the collection
After opening a case with SAP, we discovered our Information Store (CMS_InfoObjects5) is missing all of the Indexes, including the one that constrains the "ObjectID' to a unique field. After inspecting the database, we determined there are many duplicate "ObjectIDs". It looks like we have duplicate users (Administrator, Guest and some others) and some other duplicate objects (I think these may be reports, it is impossible to tell since the columns contain binary data). (This explains the error message above!)
We have about 200 reports configured in this Information Store/DB with various permissions assigned to each report. It would be a huge undertaking to rebuild the DB manually.
Can anyone recommend a way to recover from this? I have tried the following scenario:
Created a new/empty Information Store and copied all the records from the corrupt database to this new store. For the records that were duplicated I copied over all the "older" (based on the modifieddate field) duplicates and left out the "newer" ones. We then pointed our CMS to this databse and after going into Authentication then "Windows AD" tab, we were still unable to do an "Update". (It wasn't the same error, it was a new one but I forgot what the exact error was).
Next, I did the exact same thing, but this time I copied all of the "newer" records from the existing/corrupt database to this new/empty database. This time, I can't even login. I get an error message about not being able to load the authentication plug in. I get this message if I try to log using "Windows AD" or "Enterprise".
I am not sure what to do next. I decided to try using the SDK to pull out a list of all of the reports and permissions from our current DB and from our backup DB (from a few months ago, before all of the indexes disappeared). I decided we could go back to that version of the database (the backup) if I had a list of all the new reports and permissions. (We could update those manually to get the backup DB in sync with our current data). Although, I am unable to get the SDK or any of the sample code to work. I ran into various problems such as: The sample code seems to be written for Visual Studio 2003 and .Net 2.0 and I can't get it to compile. So, I inspected the code and pulled out some of the SQL commands and tried running the queries directly, but realized the table names are different. The sample code expects a table name of "CI_INFOOBJECTS", but that table doesn't exist in our database. We do have "CMS_InfoObjects5", but it has a different schema from the "CI_INFOOBJECTS". This is so frustrating!!!
Even though the existing DB/InfoStore is corrupt (well, not really corrupt, but it is missing all of the indexes and therefore the proper constraints and therefore we can't add new users), the server still "works". All permissions/reports/users are in tact, we just can't add any new users. (We can add reports and assign permissions properly though.)
I suppose I need to open our case back up with SAP, but first I wanted to get some opinions from folks here on the forum.
Any ideas? How would you approach this problem?

No, I haven;t but I did consider it.
I wonder if it will stop when it comes across the duplicate entries, or if it will just skip them? Anyone?

Report Builder Layout Model Missing

when I went to edit an existing report in 10g, I found the display of the Layout model is missing.
The fields and frames are all visible in the Object Navigator but they just don't show up in the layout screen.
Is there an easy way to fix this - or do i have to rebuild the report from the queries?
**** Doh **** Noticed the layout model was pointing to the Trailer pages - hence no details.
Apologies
Edited by: Elaine L on Feb 8, 2010 12:34 PM

hi,
first u check u r layout model ,
totally three sections are there
1) header section
2) main section
3) trailer section
i think u r checking the layout in header or trailer section
first u have to check in the main section
if its not there u can with other two sections,
in these three sections not available in u r layout , go to the object navigator in the main section --> select the some fileds and repeating frame
and apply the color of black of red in selected fields and repeating frames,
after that check u r layout model

WebI report based on Universe upon SAP BEx Queries:Prompt issue

Hi,
I am creating Web Intelligence report using Universe based on SAP Bex Queries. In WebI report I created a filter condition as I need to run report based on two specidc dates. I need to schedule report to run 2nd of every month to show data for last month. At present I have the following filter : date between 'Start Date' and 'End Date'. 'Start Date' should always be 'first date of previous month' and End Date be always must be 'Last date of previous Month'. How to do this. The solution I thought would be to create variables at report/universe level ('first date of previous month' and 'Last date of previous Month') and use in the filter using 'Object from this Query' option.But this 'Object from this Query' option is missing in the prompt.Is there any work around to achieve this.? Could you please help me.
Nanda Kishore

Hi all,
I have a related question too.
I have 2 queries and need a Combined BEx query written on this for reporting. (WebI)
In the 2 queries, there is a Field which needs to be restricted.
But this field should not be restricted in the Combined BEx query.
So I thought of restricting the Field at the report level. But in this case, the user gets a prompt to enter a value for the field.
And this is not desirable as per the requirement.
COuld you please tell me if there is another way of handling this without the user being prompted to enter a value while the report is being run, but still I need selection at the Field level.
Thanks and Regards,
Srilakshmi B

Layout issue in export multiple queries to single excel

Hi ,
While exporting more than one queries on web template to single excel (with help of HowToWebPrinting document ), i am facing layout problems.
EX. if my web template has 4 queries in below format
A B
C D
where A,B,C,D are different queries
on web printing to single excel, i get all queries in excel but they are in form
A
B
C
D
i.e with distorted layout. Is there a way out to have the exported EXCEL in same layout as that of my report
Any ideas would be appreciated in this regard.
Best Regards
Deepali

Thanks Deepak for your suggestion on trying to enhance
Z_PRINT_SERVICE class.
But in my system, i have z_print_help_service & not z_print_service. Is it something that is missing.
To add to it, i have one more issue.
I have a strange scenario.
In some webtemplates, when i do export , my all data is coming.
In some alternate columns are coming on export in one row
& other row its fine, while on web report all columns are existing .
Has anybody faced missing data on export .
Unless this problem gets resolved, we can't be sure of what is being produced & won't be able to implement. Below are lines i am using
in each template.
<param name="HELP_SERVICE" value="Z_PRINT_HELP_SERVICE_ALL_DP"/>
<param name="HELP_SERVICE_CLASS" value="ZCL_RSR_XLS_HELP_WINDOW_PRINT"/>

Missing BW Queries

Similar Messages

Maybe you are looking for