What is the difference between query & query view in BI 7.0 ?

Hi Experts,
What is the difference between query & query view in BI 7.0 ?
Can anyone suggest me on this.
Thanks & Regards
Sameer Khan

Hi Sameer,
Pls find the below URL for Query&Query View
http://help.sap.com/saphelp_nw04/helpdata/EN/26/6de53cce129749893b008c627ede07/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/36/18788b6bca5d02e10000009b38f983/content.htm
Thanks,
John

Similar Messages

What is the difference between 'workbookk' and ' view'?

Hi all,
What is the difference between 'workbook' and 'view'. I check some document but I don't see there is big difference.
Thanks.
J.

hi John,
We use workbooks for excel formating,like font changes, lay out changes etc...
Workbooks into which queries are inserted are no different in appearance than other Excel workbooks.
They can be saved as files, copied, sent and (using Excel functions) edited however you like and even supplemented with other data.
Views are primarily used for BW Web Reports, it is similar to the concept of workbooks is for BEx.A local view can be accessed only within a workbook in which it was saved, where as a global view can be accessed globally in the system, it is not attached to a workbook. Only Global view can be used in BW Web Templates.
u can seee the help doc for more details:
http://help.sap.com/saphelp_nw04s/helpdata/en/0d/af12403dbedd5fe10000000a155106/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/3a/89883989676778e10000000a11402f/content.htm
bye
sham'm

What is the differences between viewCriteria query modes?

Hello all,
recently we faced a performance issue in a production application. after tracing we found that the issue was caused by setting the query mode of the view criteria to in memory.
bussiness case description:
when creating a new record for table A, I want to populate one field depending on records in another table B, so I used model driven LOV.
The problem was that new records were created for both tables in the same ADF train i.e. the data for both tables were not posted or committed yet.
so by using a query based ViewObject + viewCriteria with query mode set to memory for viewCriteria I managed to populate the LOV with the correct data,
in another page I will show database records for table A with LOV to show meaningful messages to users , but I can as well create new records for table A ,but the loading of this page is very slow.
tracing:
using alter session set sql_trace=true; I found that table B is fully scanned and all rows are fetched-180000+ record-.
Problem description:
from the trace file generated found that the query issued did not have a where clause.
also found that the viewObject fetched the entire table into memory- 180000+ record,- then searched them in memory.
Solution:
changing the query mode of the viewCriteria seems to solve the issue
so in order to avoid such issues in the future ,I wanted to make sure I understand the differences between the query modes of view criteria and their impact on the performance and if there are any differences if the viewObject is based on an entity or a sql dml.
this is what I know so far -please correct me if I am mistaken-:
1)database: search the database appending the conditions of the viewCriteria to whatever the query is
2)memory: search the rows that are already in the memory.
3)both: search both database and memory.
also, in case I updated one of the records in the memory but did not yet post or commit will the fetched rows have the updated values? and if these changes fails the condition from the viewCriteria , will the rows be shown?.

The camera roll contains all the photos and videos taken on your device, as well as any saved on your device from the internet, emails, text messages, etc. The photo library contains photos synced to your device from your computer.
Only camera roll photos are synced using iCloud with photo stream. And photo stream only syncs photos, not videos.

What's the difference between hierachical & flat view

Continue to choose as many metadata categories and criteria as you like. Click the pop-up menu at the right side of any column header to add or remove the column, change the sort order, and switch between hierarchical and flat view.

Keywords in Lightroom can be arranged hierarchically. Every time you create a new keyword, you have the option to either create it as a top-level keyword or as a sub-keyword for some other keyword. By creating sub-keywords you can produce multilevel hierarchy of keywords.
For example, you can create top-level keywords "Places" and "Holidays". Then under "Places" you can add sub-keywords "USA", "Russia" and "Zanzibar". Now under "USA" you can create sub-keywords "California" and "Minnesota". And so on.
Now, when it comes to viewing your keywords, you have two options:
1) Hierarchical view: the keywords are displayed in accordance to the hierarchy you created. Firstly, only top level keywords are displayed ("Places" and "Holidays" in our example). You can expand any top-level keyword to see its sub-keywords, and so on. (In our example, expanding "Places" will display "USA", "Russia" and "Zanzibar" etc.)
2) Flat view: all keywords are displayed in one single flat list. Any hierarchical relationships between keywords are ignored. (In out example, flat viuew will display a list containing "Places", "Holidays", "USA", "Russia", "Zanzibar", "California", "Minnesota" etc. in alphabetical order.)

Query: how to use structure and selection and what's the difference between

Query: how to use structure and selection and what's the difference between these two?
Would be appreciated if some experts here give examples to demenstrate on how to use structure and selection in query and what's the difference between these two?
Thanks in advance!

Hi Kevin,
1. Well by default all the KF that you include in your query go into a Key Figure Structure. You can additionally have another structure for defining how your chars are laid out. A common example is a Calmonth structure where you have selections for 12 months, quarers and YTD values. This would be a char structure with different selections (for each month, qtr etc)
2. Yes, a selection with a KF is the same as restricting a KF. You can use am RKF is you have one on the left hand side, or if you need to do this locally in the query, right click the structure and choose New Selection, then proceed to choose your KF and reqd char values.
Hope this helps...

What is the difference between BO Designer connect BW QUERY and BW CUBEuFF1F

HI friend,
What is the difference between BO Designer connect BW QUERY and BW CUBE？
which one is better?
Best regards.
Howard

Hi Howard,
You can use autorization variables in SAP BW and maitain the security there, using that you can apply diferent security not only at Infoobject levet you can apply security per BEX Query.
Here is some informaion about BEX and SAP BusinessObjects
BI metadata feature _______SAP OLAP BAPI support level
Characteristics (incl. Time and Unit)_______ InfoCube/BEx Query
Hierarchies_______ InfoCube/BEx Query
Basic Key Figures_______ InfoCube/BEx Query
Navigational Attributes_______ BEx Query only
Display Attributes_______ InfoCube/BEx Query
Calculated Key Figures / Formulas_______ BEx Query only
Restricted Key Figures_______ BEx Query only
Custom Structures_______ BEx Query only
Variables_______ BEx Query only
I hope this help you.
BEst regards,
Fede

What is the difference between view and materialized views

Hi
What is the difference between view and materialized view ? can we update the base table using views

can we update the base table using viewsYes:
VIEWS
1. an updatable view is one that lets you perform DML on the underlying table
(see Oracle Database Concepts 10g - 5 Schema Objects)
2. non-updatable view requires INSTEAD OF Triggers
(see Oracle Database Concepts 10g - 22 Triggers)
SNAPSHOTS
You can have updateable (and writeable) snapshots - in updateable (writeable) MV replication.
Oracle uses snapshots (Materialized Views - MV) for two different purposes:
1. replication
2. automated Query Rewrite facility (first introduced in Oracle Discoverer, later included in Oracle database 8i).
Replication types in Oracle are:
a) Basic replication (MV replication)
- transaction based
- row-level
- asynchronous from master table to MV (Materialized View)
- DML replication only
- database 7 / 8.0 / 8i / 9i / 10g
- Standard and Enterprise Edition
1. Read-only MV replication
2. Updateable MV replication:
2.1 asynchronous from MV to master
2.2 synchronous from MV to master
3. Writeable MV replication
b) Multimaster replication
- transaction based
- row-level or procedural
- asynchronous or synchronous
- DML and DDL replication
- database 7 / 8.0 / 8i / 9i / 10g
- Enterprise Edition only
1. row-level asynchronous replication
2. row-level synchronous replication
3. procedural asynchronous replication
4. procedural synchronous replication
c) Streams replication
- (redo) log based
- row-level
- asynchronous
- DML and DDL replication
- database 9i / 10g (10g has Down Streams Capture)
- Enterprise Edition only (Standard Edition 10g can execute Apply process)
Regards,
Zlatko Sirotic

What are the differences between the following Oracle database views?

What are the differences between the following Oracle database views(or function)? Can they be instead of each other? Can all of them be used to pull out the execution plan from the library cache?
V$SQL_PLAN
DBA_HIST_SQL_PLAN
dbms_xplan.display_cursor function

junez wrote:
What are the differences between the following Oracle database views(or function)? Can they be instead of each other? Can all of them be used to pull out the execution plan from the library cache?
V$SQL_PLAN
DBA_HIST_SQL_PLAN
dbms_xplan.display_cursor functionV$SQL_PLAN-this is dynamic perfomance view which contain execution plan information for each child cursor loaded in the library cache.
DBA_HIST_SQL_PLAN- data dictionary view also contain execution plan information for each child cursor bun in workload repository.Actually this view captures information from V$SQL_PLAN and is used with the DBA_HIST_SQLSTAT .
dbms_xplan.display_cursor - function displays explain plan of any cursor loaded in the cursor cache. See more information below links:
http://youngcow.net/doc/oracle10g/server.102/b14237/dynviews_2120.htm
http://download.oracle.com/docs/cd/B14117_01/server.101/b10755/statviews_2154.htm
http://download.oracle.com/docs/cd/B12037_01/appdev.101/b10802/d_xplan.htm#998179

What is the difference between hidden field and view state??

Both view state and hidden field are use to store page specific information then, what is the difference between both of them??

The ViewState of a page is actually stored in a large hidden field and it contains information about the entire page whereas a single hidden field that you define yourself is used to store some single value that should not be displayed.
Please refer to the following page for more information about ASP.NET View State:
http://msdn.microsoft.com/en-us/library/ms972976.aspx
But please post your ASP.NET and web related questions at
http://forums.asp.net in the future.
Also, please remember to mark any helpful posts as answer.

What is the difference between tkprof and explainplan

Hi,
what is the difference between tkprof and explainplan.

Execution Plans and the EXPLAIN PLAN Statement
Before the database server can execute a SQL statement, Oracle must first parse the statement and develop an execution plan. The execution plan is a task list of sorts that decomposes a potentially complex SQL operation into a series of basic data access operations. For example, a query against the dept table might have an execution plan that consists of an index lookup on the deptno index, followed by a table access by ROWID.
The EXPLAIN PLAN statement allows you to submit a SQL statement to Oracle and have the database prepare the execution plan for the statement without actually executing it. The execution plan is made available to you in the form of rows inserted into a special table called a plan table. You may query the rows in the plan table using ordinary SELECT statements in order to see the steps of the execution plan for the statement you explained. You may keep multiple execution plans in the plan table by assigning each a unique statement_id. Or you may choose to delete the rows from the plan table after you are finished looking at the execution plan. You can also roll back an EXPLAIN PLAN statement in order to remove the execution plan from the plan table.
The EXPLAIN PLAN statement runs very quickly, even if the statement being explained is a query that might run for hours. This is because the statement is simply parsed and its execution plan saved into the plan table. The actual statement is never executed by EXPLAIN PLAN. Along these same lines, if the statement being explained includes bind variables, the variables never need to actually be bound. The values that would be bound are not relevant since the statement is not actually executed.
You don’t need any special system privileges in order to use the EXPLAIN PLAN statement. However, you do need to have INSERT privileges on the plan table, and you must have sufficient privileges to execute the statement you are trying to explain. The one difference is that in order to explain a statement that involves views, you must have privileges on all of the tables that make up the view. If you don’t, you’ll get an “ORA-01039: insufficient privileges on underlying objects of the view” error.
The columns that make up the plan table are as follows:
Name Null? Type
STATEMENT_ID VARCHAR2(30)
TIMESTAMP DATE
REMARKS VARCHAR2(80)
OPERATION VARCHAR2(30)
OPTIONS VARCHAR2(30)
OBJECT_NODE VARCHAR2(128)
OBJECT_OWNER VARCHAR2(30)
OBJECT_NAME VARCHAR2(30)
OBJECT_INSTANCE NUMBER(38)
OBJECT_TYPE VARCHAR2(30)
OPTIMIZER VARCHAR2(255)
SEARCH_COLUMNS NUMBER
ID NUMBER(38)
PARENT_ID NUMBER(38)
POSITION NUMBER(38)
COST NUMBER(38)
CARDINALITY NUMBER(38)
BYTES NUMBER(38)
OTHER_TAG VARCHAR2(255)
PARTITION_START VARCHAR2(255)
PARTITION_STOP VARCHAR2(255)
PARTITION_ID NUMBER(38)
OTHER LONG
DISTRIBUTION VARCHAR2(30)
There are other ways to view execution plans besides issuing the EXPLAIN PLAN statement and querying the plan table. SQL*Plus can automatically display an execution plan after each statement is executed. Also, there are many GUI tools available that allow you to click on a SQL statement in the shared pool and view its execution plan. In addition, TKPROF can optionally include execution plans in its reports as well.
Trace Files and the TKPROF Utility
TKPROF is a utility that you invoke at the operating system level in order to analyze SQL trace files and generate reports that present the trace information in a readable form. Although the details of how you invoke TKPROF vary from one platform to the next, Oracle Corporation provides TKPROF with all releases of the database and the basic functionality is the same on all platforms.
The term trace file may be a bit confusing. More recent releases of the database offer a product called Oracle Trace Collection Services. Also, Net8 is capable of generating trace files. SQL trace files are entirely different. SQL trace is a facility that you enable or disable for individual database sessions or for the entire instance as a whole. When SQL trace is enabled for a database session, the Oracle server process handling that session writes detailed information about all database calls and operations to a trace file. Special database events may be set in order to cause Oracle to write even more specific information—such as the values of bind variables—into the trace file.
SQL trace files are text files that, strictly speaking, are human readable. However, they are extremely verbose, repetitive, and cryptic. For example, if an application opens a cursor and fetches 1000 rows from the cursor one row at a time, there will be over 1000 separate entries in the trace file.
TKPROF is a program that you invoke at the operating system command prompt in order to reformat the trace file into a format that is much easier to comprehend. Each SQL statement is displayed in the report, along with counts of how many times it was parsed, executed, and fetched. CPU time, elapsed time, logical reads, physical reads, and rows processed are also reported, along with information about recursion level and misses in the library cache. TKPROF can also optionally include the execution plan for each SQL statement in the report, along with counts of how many rows were processed at each step of the execution plan.
The SQL statements can be listed in a TKPROF report in the order of how much resource they used, if desired. Also, recursive SQL statements issued by the SYS user to manage the data dictionary can be included or excluded, and TKPROF can write SQL statements from the traced session into a spool file.
How EXPLAIN PLAN and TKPROF Aid in the Application Tuning Process
EXPLAIN PLAN and TKPROF are valuable tools in the tuning process. Tuning at the application level typically yields the most dramatic results, and these two tools can help with the tuning in many different ways.
EXPLAIN PLAN and TKPROF allow you to proactively tune an application while it is in development. It is relatively easy to enable SQL trace, run an application in a test environment, run TKPROF on the trace file, and review the output to determine if application or schema changes are called for. EXPLAIN PLAN is handy for evaluating individual SQL statements.
By reviewing execution plans, you can also validate the scalability of an application. If the database operations are dependent upon full table scans of tables that could grow quite large, then there may be scalability problems ahead. On the other hand, if large tables are accessed via selective indexes, then scalability may not be a problem.
EXPLAIN PLAN and TKPROF may also be used in an existing production environment in order to zero in on resource intensive operations and get insights into how the code may be optimized. TKPROF can further be used to quantify the resources required by specific database operations or application functions.
EXPLAIN PLAN is also handy for estimating resource requirements in advance. Suppose you have an ad hoc reporting request against a very large database. Running queries through EXPLAIN PLAN will let you determine in advance if the queries are feasible or if they will be resource intensive and will take unacceptably long to run.

What is the difference between DSo and Infocube

Hello,
Kindly tell me what is the difference between DSO and Infocube?
And please tell me how to take the desicion that in whichi case we can use DSO and in which case we can use Infocube..

Hi ,
DataStore object serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level.
This data can be evaluated using a BEx query.
A DataStore object contains key fields (for example, document number/item) and data fields that can also contain character fields (for example, order status, customer) as key figures. The data from a DataStore object can be updated with a delta update into InfoCubes and/or other DataStore objects or master data tables (attributes or texts) in the same system or across different systems.
Unlike multidimensional data storage using InfoCubes, the data in DataStore objects is stored in transparent, flat database tables. The system does not create fact tables or dimension tables.
Use
The cumulative update of key figures is supported for DataStore objects, just as it is with InfoCubes, but with DataStore objects it is also possible to overwrite data fields. This is particularly important with document-related structures. If documents are changed in the source system, these changes include both numeric fields, such as the order quantity, and non-numeric fields, such as the ship-to party, status and delivery date. To reproduce these changes in the DataStore objects in the BI system, you have to overwrite the relevant fields in the DataStore objects and set them to the current value. Furthermore, you can use an overwrite and the existing change log to render a source delta enabled. This means that the delta that is further updated to the InfoCubes, for example, is calculated from two successive after-images.
An InfoCube describes (from an analysis point of view) a self-contained dataset, for example, for a business-orientated area. You analyze this dataset in a BEx query.
An InfoCube is a set of relational tables arranged according to the star schema: A large fact table in the middle surrounded by several dimension tables.
Use
InfoCubes are filled with data from one or more InfoSources or other InfoProviders. They are available as InfoProviders for analysis and reporting purposes.
Structure
The data is stored physically in an InfoCube. It consists of a number of InfoObjects that are filled with data from staging. It has the structure of a star schema.
The real-time characteristic can be assigned to an InfoCube. Real-time InfoCubes are used differently to standard InfoCubes.
ODS versus Info-cubes in a typical project scenario
ODS
why we use ods?
why is psa & ods nessasary
Hope this helps,
Regards,
CSM Reddy

What is the difference between exists and in

hi all
if i have these queries
1- select ename from emp where ename in ( select ename from emp where empno=10)
and
2- select ename from emp where exists ( select ename from emp where empno=10)
what is the difference between exists and in is that only when i use in i have to bring the field name or what.... i mean in a complex SQL queries is it will give the same answer
Thanks

You get two entirely different result sets that may be the same. Haah! What do I mean by that.
SQL> select table_name from user_tables;
TABLE_NAME
BAR
FOO
2 rows selected.
SQL> select table_name from user_tables where table_name in (select table_name from user_tables where table_name = 'FOO');
TABLE_NAME
FOO
1 row selected.
SQL> select table_name from user_tables where exists(select table_name from user_tables where table_name = 'FOO');
TABLE_NAME
BAR
FOO
2 rows selected.So, why is this? the WHERE EXISTS means 'if the next is true', much like where 1=1 being always true and 1=2 being always false. In this case, where exists could be TRUE or FALSE, depending on the subquery.
WHERE EXISTS can be useful for something like testing if we have data, without actually having to return columns.
So, if you want to see if an employee exists you might say
SELECT 1 FROM DUAL WHERE EXISTS( select * from emp where empid = 10);
If there is a row in emp for empid=10, then you get back 1 from dual;
This is what I call an 'optimistic' lookup because the WHERE EXISTS ends as soon as there is a hit. It does not care how many - only that at least one exists. It is optimistic because it will continue processing the table lookup until either it hits or reaches the end of the table - for a non-indexed query.

What is the difference between upgradation and migration.

Hi Guru's
what is the difference between upgradation and migration.
actuallly i involved in upgradation project, here my role is
1. first i check the query's in 3.5 save the query and transport the query. and check the query in bex analyzer also.
2. go to BI .7 find the query;s ,give the query name and save the query ,
3. once save the query, again will come to 3.5 open the query , it will not open. this is my job here,
come to 7.0 check the query in analyzer also.
i am having littile bit confusion, how it will comes query in 7.0, why are u saving the query's in 3.5 and 7.0
query's already available in 7.0 why are u doing this work?
can i know the upgrades those objects, is it neccessary, if necessary how can i upgrade.
infoobje , transferrules, transferstructure ,infosoure, datasoure,updaterules, ods, cubes.
Points will be Assingned ,
Thanks & Regards
prabhavathi

Hi,
I was talking in a general sense not on a query level.
If your taling about migration in that level meaning as a part of larger upgradation (in your case 3.x to 7) there may be many places where you need to do this kind of activities.
Fr eg migration into new data flow, Migration of Web templates from BW 3.x to Netweaver 2004s, etc
Hope this helps.
Thanks,
JituK

What is the difference between ws_upload and gui_upload

what is the difference between ws_upload and gui_upload
what is the difference between ws_download and gui_down load
pls tell briefly

Hi Kuamr,
UPLOAD and DOWNLOAD, the function modules used until now are not part of the standard set of ABAP commands. They are used to display the file interface on the presentation server. UPLOAD and DOWNLOAD are not compatible with USs and have been replaced by GUI_UPLOAD and GUI_DOWNLOAD.
The new function modules, GUI_UPLOAD and GUI_DOWNLOAD, have an interface that also allows you to write Unicode format to the local hard drive. For a description of these interfaces, refer to the documentation for each function module, available under SAP Easy Access " Development " Function Builder " Goto " Documentation.
Instead of using the function modules, you can use the static methods GUI_UPLOAD and GUI_DOWNLOAD of the global class CL_GUI_FRONTEND_SERVICES.
Hope this resolves your query.
Reward all the helpful answers.
Regards

What's the Difference Between OLAP and OLTP?

HI,
What's the difference between OLAP and OLTP ? and which one is Best?
-Arun.M.D

Hi,
The big difference when designing for OLAP versus OLTP is rooted in the basics of how the tables are going to be used. I'll discuss OLTP versus OLAP in context to the design of dimensional data warehouses. However, keep in mind there are more architectural components that make up a mature, best practices data warehouse than just the dimensional data warehouse.
Corporate Information Factory, 2nd Edition by W. H. Inmon, Claudia Imhoff, Ryan Sousa
Building the Data Warehouse, 2nd Edition by W. H. Inmon
With OLTP, the tables are designed to facilitate fast inserting, updating and deleting rows of information with each logical unit of work. The database design is highly normalized. Usually and at least to 3NF. Each logical unit of work in an online application will have a relatively small scope with regard to the number of tables that are referenced and/or updated. Also the online application itself handles the majority of the work for joining data to facilitate the screen functions. This means the user doesn't have to worry about traversing across large data relationship paths. A heavy dose of lookup/reference tables and much focus on referential integrity between foreign keys. The physical design of the database needs to take into considerations the need for inserting rows when deciding on physical space settings. A good book for getting a solid base understanding of modeling for OLTP is The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models by Michael C. Reingruber, William W. Gregory.
Example: Let's say we have a purchase oder management system. We need to be able to take orders for our customers, and we need to be able to sell many items on each order. We need to capture the store that sold the item, the customer that bought the item (and where we need to ship things and where to bill) and we need to make sure that we pull from the valid store_items to get the correct item number, description and price. Our OLTP data model will contain a CUSTOMER_MASTER, A CUSTOMER_ADDRESS_MASTER, A STORE_MASTER, AN ITEM_MASTER, AN ITEM_PRICE_MASTER, A PURCHASE_ORDER_MASTER AND A PURCHASE_ORDER_LINE_ITEM table. Then we might have a series of M:M relationships for example. An ITEM might have a different price for specific time periods for specific stores.
With OLAP, the tables are designed to facilitate easy access to information. Today's OLAP tools make the job of developing a query very easy. However, you still want to minimize the extensiveness of the relational model in an OLAP application. Users don't have the wills and means to learn how to work through a complex maze of table relationships. So you'll design your tables with a high degree of denormalization. The most prevalent design scheme for OLAP is the Star-Schema, popularized by Ralph Kimball. The star schema has a FACT table that contains the elements of data that are used arithmatically (counting, summing, averaging, etc.) The FACT Table is surrounded by lookup tables called Dimensions. Each Dimension table provides a reference to those things that you want to analyze by. A good book to understand how to design OLAP solutions is The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses by Ralph Kimball.
Example: let's say we want to see some key measures about purchases. We want to know how many items and the sales amount that are purchased by what kind of customer across which stores. The FACT table will contain a column for Qty-purchased and Purchase Amount. The DIMENSION tables will include the ITEM_DESC (contains the item_id & Description), the CUSTOMER_TYPE, the STORE (Store_id & store name), and TIME (contains calendar information such as the date, the month_end_date, quarter_end_date, day_of_week, etc).
Database Fundamentals > Data Warehousing and Business Intelligence with Mike Lampa
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.

What is the difference between query & query view in BI 7.0 ?

Similar Messages

Maybe you are looking for