Infoset Query Performance

MSSQL Server 2000
BW 3.1C
R/3 6.20
BW 3.0B Frontend
I created an infoset with 2 huge tables (one holding approx. 10 mil records w/ 20+ attribs, and the other holding approx. 3 mil records w/ 30+ attribs). I didnt include ALL attributes in the infoset, maybe just 15 total on both of the tables. They do have a common field to join, one is the key field of one table, and the other is the attribute of the other. They are both info objects with master data.
The join is an inner join in which the tables have a 1 to many relationship.
I created indeces individually for each table. But when I run a query that SHOULD use the indeces, it still takes a very long time to run (approx. 5-10 mins, per navigation). When viewing the Run Schedule for this query, it does show that it scans for clustered indeces for the (many table) and regular indeces for the (one table). But
Any suggestions on how I could have this query run faster?

To whom are interested in the Infoset topic.
As of Release 2.0B, the InfoSet Query is available in BW as a tool for special requests from the area of the master data reporting. A new InfoProvider, also known as an InfoSet, was introduced into BW for Release 3.0A.
The OSS Note 486789 provides recommendations about using InfoSets in different BW releases and explains in more details the difference among SAP Query, InfoSet Query, InfoSet (Basis), InfoSet (BW).
Hope this can be useful for all of you, guys.
Bye,
Roberto

Similar Messages

How to improve query performance using infoset

I create one infoset that including 4 char.and 3 DSO which all are time-dependent.When query run, system show very poor perfomance, sometimes no data show in BEX anayzer. In this case I have to close BEX analyzer at first and then open it again, after that it show real results. It seems very strange. Does anybody has experience on infoset performance improvement. pls info, thanks!

Hi
As info set itself doesn't have any data so it improves Performance
also go through the below tips.
Find the query Run-time
where to find the query Run-time ?
557870 'FAQ BW Query Performance'
130696 - Performance trace in BW
This info may be helpful.
General tips
Using aggregates and compression.
Using less and complex cell definitions if possible.
1. Avoid using too many nav. attr
2. Avoid RKF and CKF
3. Many chars in row.
By using T-codes ST03 or ST03N
Go to transaction ST03 > switch to expert mode > from left side menu > and there in system load history and distribution for a particular day > check query execution time.
Statistical Records Part 4: How to read ST03N datasets from DB in NW2004
How to read ST03N datasets from DB
Try table rsddstats to get the statistics
Using cache memory will decrease the loading time of the report.
Run reporting agent at night and sending results to email. This will ensure use of OLAP cache. So later report execution will retrieve the result faster from the OLAP cache.
Also try
1. Use different parameters in ST03 to see the two important parameters aggregation ratio and records transferred to F/E to DB selected.
2. Use the program SAP_INFOCUBE_DESIGNS (Performance of BW infocubes) to see the aggregation ratio for the cube. If the cube does not appear in the list of this report, try to run RSRV checks on the cube and aggregates.
Go to SE38 > Run the program SAP_INFOCUBE_DESIGNS
It will shown dimension Vs Fact tables Size in percent.If you mean speed of queries on a cube as performance metric of cube,measure query runtime.
3. To check the performance of the aggregates,see the columns valuation and usage in aggregates.
Open the Aggregates...and observe VALUATION and USAGE columns.
"---" sign is the valuation of the aggregate. You can say -3 is the valuation of the aggregate design and usage. ++ means that its compression is good and access is also more (in effect, performance is good). If you check its compression ratio, it must be good. -- means the compression ratio is not so good and access is also not so good (performance is not so good).The more is the positives...more is useful the aggregate and more it satisfies the number of queries. The greater the number of minus signs, the worse the evaluation of the aggregate. The larger the number of plus signs, the better the evaluation of the aggregate.
if "-----" then it means it just an overhead. Aggregate can potentially be deleted and "+++++" means Aggregate is potentially very useful.
In valuation column,if there are more positive sign it means that the aggregate performance is good and it is useful to have this aggregate.But if it has more negative sign it means we need not better use that aggregate.
In usage column,we will come to know how far the aggregate has been used in query.
Thus we can check the performance of the aggregate.
Refer.
http://help.sap.com/saphelp_nw70/helpdata/en/b8/23813b310c4a0ee10000000a114084/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/60/f0fb411e255f24e10000000a1550b0/frameset.htm
performance ISSUE related to AGGREGATE
Note 356732 - Performance Tuning for Queries with Aggregates
Note 166433 - Options for finding aggregates (find optimal aggregates for an InfoCube)
4. Run your query in RSRT and run the query in the debug mode. Select "Display Aggregates Found" and "Do not use cache" in the debug mode. This will tell you if it hit any aggregates while running. If it does not show any aggregates, you might want to redesign your aggregates for the query.
Also your query performance can depend upon criteria and since you have given selection only on one infoprovider...just check if you are selecting huge amount of data in the report
Check for the query read mode in RSRT.(whether its A,X or H)..advisable read mode is X.
5. In BI 7 statistics need to be activated for ST03 and BI admin cockpit to work.
By implementing BW Statistics Business Content - you need to install, feed data and through ready made reports which for analysis.
http://help.sap.com/saphelp_nw70/helpdata/en/26/4bc0417951d117e10000000a155106/frameset.htm
/people/vikash.agrawal/blog/2006/04/17/query-performance-150-is-aggregates-the-way-out-for-me
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1955ba90-0201-0010-d3aa-8b2a4ef6bbb2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
http://help.sap.com/saphelp_nw04/helpdata/en/c1/0dbf65e04311d286d6006008b32e84/frameset.htm
You can go to T-Code DB20 which gives you all the performance related information like
Partitions
Databases
Schemas
Buffer Pools
Tablespaces etc
use tool RSDDK_CHECK_AGGREGATE in se38 to check for the corrupt aggregates
If aggregates contain incorrect data, you must regenerate them.
202469 - Using aggregate check tool
Note 646402 - Programs for checking aggregates (as of BW 3.0B SP15)
You can find out whether an aggregate is usefull or useless you can find out through a proccess of checking the tables RSDDSTATAGGRDEF*
Run the query in RSRT with statistics execute and come back you will get STATUID... copy this and check in the table...
This gives you exactly which infoobjects it's hitting, if any one of the object is missing it's useless aggregate.
6
Check SE11 > table RSDDAGGRDIR . You can find the last callup in the table.
Generate Report in RSRT
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4c0ab590-0201-0010-bd9a-8332d8b4f09c
Business Intelligence Journal Improving Query Performance in Data Warehouses
http://www.tdwi.org/Publications/BIJournal/display.aspx?ID=7891
Achieving BI Query Performance Building Business Intelligence
http://www.dmreview.com/issues/20051001/1038109-1.html
Assign points if useful
Cheers
SM

Infoset query of vendor payments at the cost distribution level

We would like an infoset query of vendor payments at the cost distribution level of the document. The issue seems to be joining vendor to the document cost distribution lines.
1.) BSAK + BSIK can be combined with an infoset data structure but only contain the vendor line of a document; the cost distribution lines are not in the tables.
2.) BSIS + BSAS can be combined with an infoset data structure but lack vendor data and joins (to a vendor source) are not an option with data structures. Vendor data added with an additional field is too slow to be a primary selection field.
3.) Logical data base KDF in an infoset returns only the vendor line of a document, not the cost distribution lines.
4.) Logical data base BRM in an infoset can have vendor from BSAK/BSIK attached by an additional field but performance is too slow to be useful. Joins are not an option in a logical data base infoset.
5.) Complete data is lacking when table joins between document cost distribution tables and vendor data tables are possible, (SPL actual line item table & BSIP or FMIFIIT & FMIFIHD). BSIP lacks AB documents (reversals). FM tables lack general ledger only documents.
6.) BSAK and BSIK together have complete vendor data but joins of both to a basis table do not work well. Left outer joins are too slow, inner joins won’t work since the tables have mutually exclusive data.
It would be ideal to have vendor in BKPF, like FMIFIHD has, but it isn't a field.
Does anyone know of any other options? I have seen the helpful thread on How to Read BSEG Efficiently

Hi,
This is SAP Business one reporting and printing forum. Please find correct forum and repost above discussion to get quick response.
Please close this thread here with helpful answer.
Thanks & Regards,
Nagarajan

Infoset query of vendor payments at the cost distribution level of the document

We would like an infoset query of vendor payments at the cost distribution level of the document. The issue seems to be joining vendor to the document cost distribution lines.
1.) BSAK + BSIK can be combined with an infoset data structure but only contain the vendor line of a document; the cost distribution lines are not in the tables.
2.) BSIS + BSAS can be combined with an infoset data structure but lack vendor data and joins (to a vendor source) are not an option with data structures. Vendor data added with an additional field is too slow to be a primary selection field.
3.) Logical data base KDF in an infoset returns only the vendor line of a document, not the cost distribution lines.
4.) Logical data base BRM in an infoset can have vendor from BSAK/BSIK attached by an additional field but performance is too slow to be useful. Joins are not an option in a logical data base infoset.
5.) Complete data is lacking when table joins between document cost distribution tables and vendor data tables are possible, (SPL actual line item table & BSIP or FMIFIHD & FMIFIIT). BSIP lacks AB documents (reversals). FM tables lack general ledger only documents.
6.) BSAK and BSIK together have complete vendor data but joins of both to a basis table are not an option. Left outer joins are too slow, inner joins won’t work since the tables have mutually exclusive data.
Does anyone know of any other options?

Hi,
This is SAP Business one reporting and printing forum. Please find correct forum and repost above discussion to get quick response.
Please close this thread here with helpful answer.
Thanks & Regards,
Nagarajan

Creating Infoset query based on ABAP program

Hello
I have 3 tables FEBEP, BKPF and BSEG and I need to join the 3 tables based on:
FEBEP-MANDT = BKPF-MANDT = BSEG-MANDT
FEBEP-NBBLN = BKPF-BELNR = BSEG-AUGBL
FEBEP-GJAHR = BKPF-GJAHR = BSEG-GJAHR
Then I have a few view fields from all the 3 tables. After this I can build an infoset query based on structure + ABAP program, and a generic datasource on top of it.
Can someone give me the ABAP code to be written SE38? Also should I select integrated program/external program in the infoset query?
Thanks,
Srini.

Hi,
Even if you create an ABAP program for infoset, you will writing a SELECT statement from BSEG table which is quite huge.
And you will putting JOIN with other tables.
Performance wise this is not advisble.
Why do not try the following other tables and check if the fields you need are available?
You can't join BSEG as it is a Cluster Table.In the place of BSEG you can use:
Account Recivables data use BSID and BSAD tables
GL Account Related data use BSIS and BSAS tables
Account payables data use BSIK and BSAK tables
Thanks.

Select distinct from an infoset query

Hello
I need to select distinct / delete duplicate from an infoset query created thru SQ02.
Please let me to know how this can be done?
Many thanks in advance!
regards
Sanjyot

Hi,
You can verywell use infoset query if you are doing following things
Join using Keyfields to retreive data from tables
If not using keyfields create index for those table fields in those fields which will improve in accessing database
Try to use minimum of tables of small size dont try to join big tables like GLPCA and all.
Try to load small set of data like a period or month. Dont try for a year or so.
if your performance is good for aperiod you can go for a year.
If you are good in function module you can try function module in which you will have the option of specifying no of records to be selected usign package size.
Hope this helps for you.
Thanks,
Arun

Advices about creating a datasource from an infoset query

Hi all,
i have to create a datasource with extraction from an infoset query in R3, i have many questions:
1- i have heard about the bad performance using a Datasource from an Infoset query, how can i improve this?
2- The infoset query doesnt exist in R3 Develop, but this exist in R3 Prod, what do i must to do? create a false infosetquery in R3 D, with just the same name of the info set query in R3 Prod? or what else?,
3- some material to improve this development about create datasources from an infoset query.
thanks guys!

Hi,
You can verywell use infoset query if you are doing following things
Join using Keyfields to retreive data from tables
If not using keyfields create index for those table fields in those fields which will improve in accessing database
Try to use minimum of tables of small size dont try to join big tables like GLPCA and all.
Try to load small set of data like a period or month. Dont try for a year or so.
if your performance is good for aperiod you can go for a year.
If you are good in function module you can try function module in which you will have the option of specifying no of records to be selected usign package size.
Hope this helps for you.
Thanks,
Arun

Tuning query performance

Dear experts,
I have a question regarding as the performance of a BW query.
It takes 10 minutes to display about 23 thousands lines.
This query read the data from an ODS object.
According to the "where" clause in the "select" statement monitored via Oracle session when the query was running, I created an index for this ODS object.
After rerunning the query, I found that the index had been taken by Oracle in reading this table (estimated cost is reduced to 2 from about 3000).
However, it takes the same time as before.
Is there any other reason or other factors that I should consider in tuning the performance of this query?K
Thanks in advance

Hi David,
Query performance when reporting on ODS object is slower compared to infocubes, infosets, multiproviders etc because of no aggregates and other performance techinques in DSO.
Basically for DSO/ODS you need to turn on the BEx reporting flag, which again is an overhead for query execution and affects performance.
To improve the performance when reporting on ODS you can create secondary indexes from BW workbench.
Please check the below links.
[Re: performance issues of ODS]
[Which criteria to follow to pick InfoObj. as secondary index of ODS?;
Hope this helps.
Regards,
Haritha.

Infoset Query - Long run times

Hi All,
I was running a Bex query on top of an infoset query a few days ago with no problems and very good performance. Now, returning any number of records it runs and timesout. I know that there will be recommendations related to statistics and possibly those related to the active table of the ODS. I have checked these and they have been recently updated. In fact, when I manually update the statistics the behaviour is the same. The structure of the infoset has not changed.
We are running 3.0B on DB2.
Any ideas?
Robert Zovic
Arinso International

Hi Giridharan,
you check whether the hierarchy SIDs are updated properly, structure, to date are all fine.
check the difference between X and Y hierarchy.
Regards,
Prakasha A

When we would create genric extractor on a infoset query

hi All,
we have infoset queries inour R/3 But very confused whether i should i go for generic with querry or genric with views.
Actually the scenario is I have the insfoset query on logical data base
I can create a generic extractor with view from the tables used by above infoset query. but there are structures in that infoset query .
so to create an generic extractor with view on a structure is not possible neither a function module is possible.
last option is creating generic extractor with view and enhancing the extractor with required fields form structure.
but i feel it would be very easy creating a generic with the same infoset querry
can u give me suggestion pls
All the answers would be appreciated by points
Thanks and Regards,
D

Hi...
SAP Query / InfoSet Query is a powerful tool for defining reports in the SAP
source systems and supports different forms of reporting. It allows users to define
and execute their own reports on data in the SAP system without any knowledge
of the ABAP programming language.
Reports are structured by entering texts and selecting fields and options in SAP
Query. The relevant fields can be selected more easily using InfoSets (before
release 4.6C, InfoSets were known as functional areas).
InfoSets are viewed as DataSources. These data sources can be used for extracting into SAP BW.
To create an InfoSet from the DataSource definition, perform these steps:
1. Fill out all the required entry fields (application component, descriptions).
2. Choose Extraction from Query.
3. Choose Save. A new screen is displayed.
4. Assign a name for your InfoSet and choose InfoSet Maintenance.
5. In the screen that follows, choose Create.
6. Select the data source (DB tables/views, joins, logical DB, and so on).
7. Define the field groups and assign the fields
An InfoSet is a special view of a dataset (logical database, table join, table,
sequential file) that is used by SAP Query as a data source. InfoSets, therefore,
determine the tables or fields in these tables that can be referenced by a report. In
most cases, InfoSets are based on logical databases.
SAP Query features a component for maintaining InfoSets. When you create an
InfoSet, a data source in an application system is selected. SAP Query is relevant
for the Business InformationWarehouse because it allows you to define the extract
structure by selecting fields in a logical database, table join or other datasets in the form of an InfoSet. In this way, you can use the generic data extraction function for master or transaction data from any InfoSet. When you do so, a query is created for an InfoSet that retrieves data and transfers it to the generic extractor.
InfoSets represent an additional, convenient data source for extracting data
generically. Logical databases in all SAP applications, table joins and further
datasets can be used as a data source for SAP BW.
Hope this would help u
with regards,
hari kv

Infoset Query Usage

Hello All,
I am trying to create generic data source in RSO2 by using Infoset Query Method.I would like to extract around 7 lakh records from it.
my query is: how about desiging an infoset query which has to pull around 7 lakh records once in a month?
please let me know if theer will be any performance issues in doing this.
Thanks in advance
Regards
Ramprasad

Hi,
Why you don't use "Extraction from View" method in RSO2 ?
Krzys

Infoset query: Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED

Hi
I have searched the forum and could not find suitable solution for my problem.
We have an infoset query whose data source is an ABAP program and this is within our BW system only. Earlier it used to run perfectly fine. Recently, due to the increasing data, the load for the same is failing because of memory issue with runtime Error TSV_TNEW_PAGE_ALLOC_FAILED . The dump occurs within 5-7 minutes of the data load. Once, we give some more filter selections in the infopackage, it runs fine.
Our problem is neither we can increase the memory any further nor we want to give filter selections in the infopackage. Also, once we execute the ABAP program alone, it runs fine.
Any help to solve this problem is appreciated.
Cheers
Chanda

Hi,
There are 3 ways to avoid this kind of problem:
1) Reduce the data set - if it is possible to process this in smaller
chunks then please do. This is an infoset query - please be more restrictive in your selections
- please refer to note 354657.
When you work with infosets that use tables or joins then it is
possible to read packages (from Rel. 6.10 on). When you work with
infosets that use logical databases or data retrieval programs than
it is not possible to read packaged - by technical restrictions.
That means that the query is executed completely taking all restrictions
into account and the result is stored internally.
2) Re-allocate some of the unused shared memories to program memory.
A prime candidate for this is Roll and Page "In Memory" values.
Alternative memory management via PHYSMEMSIZE generally overallocates
roll and page memory. Please reduce the amounts allocated to the "in
memory" part (see ST02) using the parameters below, for instance:
rdisp/ROLL_MAXFS....Total amt of ROLL (Filesystem+SHM); in 8KB blocks
rdisp/ROLL_SHM......Shared memory element of Roll; in 8KB blocks
rdisp/PG_MAXFS......Total amt of Page (Filesystem+SHM); in 8KB blocks
rdisp/PG_SHM........Shared memory element of Roll; in 8KB blocks
=>Filsystem amt = MAXFS - SHM
60MB or so each in memory should be sufficient.
This should allow an extra 260Mb or so for process memory.
Bear in mind however that Roll_SHM MUST be greater than 10% of
Roll_MAXFS.
This will not affect alternative memory management operation in any way.
3) Reduce the em/global_area_MB from 128 to 64MB.
These measures should give you ~320MB additionally per work process.
To get even more - if there is a 64 bit machine in the landscape then
redirect the load there.
I would like for you to review the SAP Note 712664. Although
the Notes 20527, 369726 and 166551 specifically refers to this
and has helped resolve multiple performance problems.
I hope it can help you.
Fran.

Infoset Query is not available for generic Extractor

Hi,
I've created an infoset in SAP ECC with sq02. Then I've created an Infoset Query on top of this Infoset, because I wanted to exclude records with specific values. Now I want to use this Infoset Query (with the filter restrictions) in my generic DataSource. I can only chosse the Infoset, but not the InfoSet Query. Normally I use the filter in the InfoPackage, but neither IP nor DTP can exclude values with a pattern (f.e. exclude all record that contains a $ symbol in the string)
Any suggestions?
Thanks and regards,
Sebastian

I agree with Jen, that BW side routines would work just fine.
If it is extractor performance you are worried about and that is why you want to build the $ exclusion in the select, then I would suggest just creating an extractor from scratch using a custom written function module. It's actually very strait forward and provides many advantages over table/view/InfoSet based generic extractors.
I am not a fan of using InfoSets for generic extractors.. but you can create InfoSets based on a data read program in which case you code all the selects and whatnot. But if you go that far with the InfoSet, why not just write the FM...
Thanks

How to improve query performance of an ODS- with 320 million records

Issue:
The reports are giving time-outs while execution.
Scenario:
We have an ODS having approximately 320 millions of records in it.
The reports are based on
The ODS and
InfoSets based on this ODS.
These reports are giving time-outs while execution.
Few facts about this ODS:
There are around 75 restricted and calculated keyfigures used in the query definition.
We cant replace this ODS by cube as there is requirement of InfoSet on it.
This is in BW 3.5 environment.
Few things we tried:
Secondary Indices are created on the fields which are appearing in the selection screen of the reports. Its not worked.
The Restriction/Calculation logic in the query definition can be moved to backend. Will it make the difference?
Question:
Can you suggest the ways to improve the query performance of this ODS?
Your immediate response is highly appreciated. Thanks in advance.

Hey!
I think Oliver's questions are good. 320 Mio records are to much for an ODS. If you can get rid of the InfoSet that would be helpful. Why exactly do you need it? If you don't need you could partition your ODS with a characteristic and report over an MultiProvider.
Is there a way to delete some data from the ODS?
Maybe you make an Upgrade to 7.0 in the next time? There you can use InfoSets on InfoCubes.
You also could try to precalculation like sam say. This is possible with reporting agent or Information Broadcasting. Then you have it in your cache. Look that your cache is large enough. Maybe you can use a table or something.
Do you just need to make one or some special reports on a special time? Maybe you can make an update in another ODS writing just the result in it. For this you can use update rules or maybe analysisprocess designer (transaction RSANWB) is the better way.
Maybe it is also possible to increase the parameter for your dialog-runtime rdisp/max_wprun_time (If you don't know, you basis should. Else look here https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ab254cf2-0c01-0010-c28d-b26d04627e61)
Best regards,
Peter

Query performance.

Hi
I have created a procedure that accepts two bind variables from a report. The user will select one or the other, both or neither of the variables. To return the appropriate results i have created a view with the entire result set and in the procedure are a number of if statements that determine what to place in the where clause selecting from the view, depending on what variables populated.
My concern is that the query that generates the view includes several joins and in total outputs around 150,000 records and seems to be rather slow to run.
Would you recommend another solution such as placing the query in the procedure itself repeated for every if statement?
Or should I work on the query performance?
What would be the most efficient solution for my problem?
Any advice would be greatly appreciated.
Thanks

[url http://forums.oracle.com/forums/thread.jspa?threadID=501834&tstart=0]When your query takes too long

Infoset Query Performance

Similar Messages

Maybe you are looking for