Generic Extraction - query view and infoset query difference

Hi Guys,
I want to know the Generic datasource difference between Extraction from view and Extraction from Query .I have read some threads and documents, still i am not getting the exact difference.
My understanding :
Views: combination of tables to view the end result , we use views.
Infoset query also with help of SQ01, 02, 03 : we combine tables to see the result.
both use primary key to select the data.
Please help me.
Thanks ,
Nithi.

Hi Nithi ,
When we build the datasource on the View
View is basically a table in which you can take data from many table combniation .
in view you can specify the table join condtion and selection condtion
View data gets updated as the data in the source table gets updated
When we build the datasource on the Infoset
Data source str gets filled from the infoset query .you need to use SQ01 and Sq02 transaction for this
in infoset you can define the tables from which you want to read the date .There is also facilty to write ABAP code which will process the data and fill the the data source str using infoset query
infoset query read the data from infoset and transfer to data structure
Thanks
Rajendra

Similar Messages

When to go for generic extraction using view and infoset query?

Hi,
Can anyone clarify me when we should go for generic extraction using view and when we should go for generic extraction using infoset query....
Also what is the difference between view and infoset?
I tried but could not find out....
Regards,
Kalyani.

Hi Kalyani,
We normally go for View or infoset when the data to be fetched in BW is distributed in different tables in SAP R/3.
Had the data been available in one table we can easily build our datasource on that table but if there are more tables then its not possible to do it without Views or Infosets. You can use Function Modules to build your datasource in case it involves complex logic to figure out the data from various tables.
Depending upon the table relationships we create view and include various fields from these tables in that view. Same is with the Infosets, you can have more flexible options like Outer Join, left outer Join etc.
Regards,
Pratap Sone

Generic Extractors for HR Reports using views and Infoset Query

Hi Friends... I am working to come out with the HR reports in BW for the HR reports which are already there in R/3. The HR reports in R/3 are created based on Infoset Query.I could not find any standard business content cubes which can give me these reports.
1)So please can anyone give me step by step approach so to create a generic extractors based on Infoset Query.
2)And also how to populate the data into the fields of the generic extractor which is created by Infoset Query( Please provide any sample ABAP code if available)
3)can anyone give me step by step approach so to create a generic extractors based on View/Table.
4)And also how to populate the data into the fields of the generic extractor which is created by View/Table( Please provide any sample ABAP code if available)
Thanks

Hi Kalyani,
We normally go for View or infoset when the data to be fetched in BW is distributed in different tables in SAP R/3.
Had the data been available in one table we can easily build our datasource on that table but if there are more tables then its not possible to do it without Views or Infosets. You can use Function Modules to build your datasource in case it involves complex logic to figure out the data from various tables.
Depending upon the table relationships we create view and include various fields from these tables in that view. Same is with the Infosets, you can have more flexible options like Outer Join, left outer Join etc.
Regards,
Pratap Sone

Difference btn View and a Query

Hello there,
I am having difficulty conceptualizing the difference btn a view and a query.
I searched the forum but did not get very useful information.
Can someone explain in plain language how a view is different from a query?
Thank you.

Hi Kara,
Have you seen this thread:
Re: What is view
And also this one:
Re: Difference: query- report- view- workbook
Hope this helps...
Message was edited by: Bhanu Gupta
Thanks for pointing that out. I have changed them, plese try again.

What is an infoset and infoset query?

hello can anyone tell me about
infoset and infoset query.

Infoset is based on Joins. Infocube, DSO and infoobject can be used to make infoset.
How to Create Infoset Query (SAP Query)
Steps on how to proceed to create a Query:
ADHOC QUERY
A query can be created to extract information from master records i.e Infotypes. For example, by creating a query , the data relating to an employee contained in various Infotypes can be extracted.
Proceedure :
Decide on the various Infotypes we want to make the query. Decide on the area where we want to query i.e Global area or Standard area. Standard area is client specific and globel area will include all clients.
Menu : HR PM Admn - Information System - Adhoc Query
Select area standard and select the user group already created
Creation of new query :
TC SQ03 - Select Environment Select Standard Area - Enter -- If new user group is to be created, enter name of the user group, click on create and enter necessary information and exit after saving
TC SQ02 - Enter name of the Infoset Create enter name of Infoset - Data source -- > Table join by basis table give name of table e.g pa0000 - Enter - Click on insert table if we want to include more tables give name of table one by one and after finishing, place cursor on the joining lines and right click to delete unwanted relationships - check - and go back - field groups - include all table fields - click on generate button   - go out
TC SQ03 - Select user group -   eg. Payroll
Infoset - Enter name of newly created Infoset
Assign users and Infosets - Assign infosets - put tick on payroll - save and go back
TC PAAH - Expand the nodes and put tick on relevant fields depending upon necessity
Save the query by giving the same name as infoset for easyness.
If this answer helps, pls assign points.
Thanx in advance.

Sapquery , adhoc query and Infoset query

any body having any material for ADHOC QUERY , SAP QUERY and Infoset query with detail explanation and steps for creation.
plz forward it to me??????????

hi,
   sap query r used to design reports to see the data according to our selections in this daa is fetched from diff tables its much easier to desing reports using this
             infoset query is somthign used with BI ints used to read data form PSA some temp storage loc
           if i am wrong someone correct me
reward if useful
ravi

Diff Between Saved Query Views and Work Books

Hi..
Can some one explain me the diff betwen Saved Query views and Workbooks interms of their use, and operation..
thanks..
kishore

hi kishore,
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
shameem

How to prevent end user to create a Query View and save back to BW Server?

Dear All :
Do Someone know that how to setup authorization for Bex Query View Creation? We want to prevent end user to create a Query View to save back to BW Server his favorite folder. when our user run Bex Query, he can base on this query and use Bex Analyzer's save function to save a Query View and save into his favorite folder.
My question is :
1. Can we set up a Authorization to prevent end user to save Bex Query View?
2. Or can I remove Save function from Bex Analyzer to prevent end user use save function, But Developer should not to be prevent .
Thanks for all of your kindly response.
Best Regard
Lawrence Kuo

Hi.
Yes, you can do it like you outline in your point 1):
You need to use the authorization object S_RS_COMP for this. This object let's you control what parts/components of a query the user can do stuff to. So, in your case, you need to have a role for the users, where you do not grant create-access to the component QVW, and then you need another role for developers, where you grant full access or whatever you need for your developers.
See [this post|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a6c54319-0e01-0010-20a4-fb81ad32f330?QuickLink=events&overridelayout=true&5003637661135] and the [SAP Help entry|http://help.sap.com/saphelp_nw70/helpdata/en/80/1a6859e07211d2acb80000e829fbfe/content.htm].
You will also need to use the authorization object S_RS_COMP1. If you already have a productive system with users doing reporting, both objects will be maintained in one of the roles already.
You also want to consider using the object S_RS_PARAM to allow users to create variants for the variabel screen.
Good luck.
Jacob

Source tables for Query views and book marks

Hi Gurus,
We are planning to recreate Query views based on a perticular query from ODS to cube.
1. Is there a table that can provide me all the query views created on the portal, Created by(User Name), description based on the query name.
Basically i am looking for the following:
INPUT: Query Name
OUTPUT:
List of all the query views created on that query
The user name or id who created the query view
Description of the query view
2. I tried in meta data repository but it only gives me query views create in older version of the portal and not 7.0.
Appreciate your immediate assistance.
Thanks,
Ravi Ananthuni

Hi Ravi,
You can get the views created on the query and the ods too. But not through table...
This may not the right process but you can find what you want.
Open WAD --> add any web item into the template --> On the left pane --> Generic --> Data Provider --> Query/View --> Click on the View icon present there.....
A popup window opens --> Click on Infoareas --> Goto your Info provider present there --> Expand it, you will find the query created on the info provider and the Views created on that query.
Hope this helps u...
Regards,
KK.

Difference Beetween Query Designer and Adhoc Query Designer

Hello!
can any one explain me what exactly is Adhoc query designer and how is it different from Bex Query designer. can you please provide me links for Adhoc query designer (not to Bex query designer)
with regards
ashwin

Hi Ashwin,
See this link:
http://help.sap.com/saphelp_nw04/helpdata/en/1f/03223c5f00612be10000000a11402f/content.htm
Basically the Adhoc query designer is a web item that you can include in a web template to allow the user to create or change queries in the web environment. It has some limitations like you cannot use variables, and can only use one structure.
Hope this helps...

Generic extraction (table,view,functionmodule)

hi
In generic Extaction when we use table and view and function module and sap qu (scenario)
AND
plz send some examples
Please search the forums before posting

Hi,
when Standard Extractors are not supporting to your requirement then we go with Generic Extraction.
Here we have Three different types to design generic extractors
Table
View
Function Module
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33
https://websmp103.sap-ag.de/~sapidb/011000358700007535452002
Hope this will help you.
Thanks
Prasad

Executing Query Views not populating Query Cache?

Hi, I'm executing 3 query views in a web template. I was expecting this to populate the cache for the query which they are based upon, but they are not?
Can anyone verify this behavior?
Thanks!

Hi,
A query uses a cache entry only if it is suitable for it regarding navigational status, filters...
I recommend you to read this how to guide:
https://websmp103.sap-ag.de/~sapdownload/011000358700004339892004E/HowToOLAPCache.pdf
Have a detalied look at sections 3.4 and 3.5:
<i>Cached query results can be used only for the same query. In some cases, real subsets of
cached query result sets can be used; this is possible, if the three following requirements are
met:
It is the same query ID
All selection criteria of the second query must be contained in those of the first call, i.e.
the query result set of the cached query is a superset of the second query
Note that the selection variable must defined as changeable with query navigation! If the
variable was not changeable, the variable value would be part of cache entry key and,
hence, the cache entry could only be used for exactly the same variable values.
The characteristics with differing selection criteria are included in the drill-down of the
cached query result</i>
Hope it helps,
David.
Message was edited by: David Sirvent

Extract error for an Infoset Query based Datasource

Hello All,
When I test a Info set Query Extraction in RSA3, I am facing the error message:
The field 'ZBW_EXTRACT' is unknown, but there are following fields with similar name '%COUNT-ZBW_EXTRACT'.
Syntax Error in Program 'AQZZSYSTBWGENER.....'
The Program is an Internal system generated program.
Has anyone faced the issue and know the way out..?
Definitely, will award points..
Thanks in advance,
Ameya.

Hi Ameya,
which system are you testing this? I mean are you testing this in dev or qa? If you are testing in QA, make sure you import the infoset correctly. It is a different procedure. Hope it helps.
Thanks and Regards
Subray Hegde

View and the query for the view giving different datasets

I have a view created with the below syntax.
CREATE OR REPLACE FORCE VIEW vw_name (/*column names*/ )
AS SELECT /*column names*/ from tables
When I execute the query with which the view is constructed , I m getting different data set which contains 4690 rows
and when I exeute the view I m getting dataset which contains only 4657 rows.
Can you please explain why the differnce in count when the source for both is the same.

Can you please explain why the differnce in count when the source for both is the same.Answer should be one of the following
1. The two query are not same
2. The table data has been modified
3. You are seeing at the wrong thing (manual error)

Views and corelated query

Hi ,
1> When are views useful?(scenarios where u could use)
2> when are corelated subqueries used?(scenarios where u could use)
Thanks in advance

When are views useful?
A view is simply the representation of a SQL statement that is stored in memory so that it can easily be re-used. For example, if we frequently issue the following query
SELECT empid FROM emp;
I might well want to make this a view (the reality is that we would probably never create a view for a statement this simple but we wanted to use an easy example).
To create a view use the create view command as seen in this example
CREATE VIEW view_emp
AS
SELECT empid FROM emp;
This command creates a new view called VIEW_EMP
Benefits of Oracle Views
* Commonality of code being used.
* Security.
* Predicate pushing
when are corelated subqueries used?(scenarios where u could use)
A correlated subquery is a subquery that uses values from the outer query. The Oracle database wants to execute the subquery once and use the results for all the evaluations in the outer query. With a correlated subquery, the database must run the subquery for each evaluation because it is based on the outer query’s data.
SQL> select
2 book_key,
3 store_key,
4 quantity
5 from
6 sales s
7 where
8 quantity < (select max(quantity)
9 from sales
10 where book_key = s.book_key);
BOOK_K STOR QUANTITY
B101 S101 1000
B102 S102 10
B102 S103 200
B116 S105 100
B101 S105 8000
B109 S109 100
81 rows selected.
In the example above, the subquery references the book_key in the outer query. The value of the book_key changes by row of the outer query, so the database must rerun the subquery for each row comparison. This has a significant performance impact on the execution time of the query, and for that reason, correlated subqueries should be avoided if possible.
The outer query knows nothing about the inner query except its results. For that reason, the outer query cannot reference any columns in the subquery. However, the subquery has access to the outer query and can reference outer query columns, thus the correlated subquery.

Generic Extraction - query view and infoset query difference

Similar Messages

Maybe you are looking for