Bex Report Performance

Dear Friends,
I would like to know is the complex authorizations can also cause the Bex report performance.
One of my scenerio is like there are two users A & B
A is having relevant authorizations for reporting, Drill down etc which are required.
B is having SAP All authorization.
When the same report has been executed by both users on the same system.
the data retrieved by user B(SAP_ALL authorization) is quite faster than User A.
Its like ther diffference of about 10 minutes.
There are some exsclude selections in report.
So my conclusion is like the complex authorizations do also hampers the query performance.
Please confirm & share your views.
Thanks & Best Regards,
Vivek Tripathi
+91-9372313000

Hi Vivek
     Can you help us understand what was the exact problem and how you resolved it / solution at Extraction / Modeling / Reporting end.
     I have a quite similiar issue with my report i have Header + Item report on Infoset
u2022     Header report takes seconds and item report takes minutes
u2022     The same report executed with exact parameter has inconsistent performance results meaning one time it takes 1 minutes next time same report same user and same authorization takes 5 minutes.
    Any help on this would be really greatfull. Suspecting is not an issue with the report at all , as no changes happened between the pre and post check.
_Additional Information : _
We Create Secondary -Bitmap index every week end i do not see that is one of the route cause.
Except that we have our regular daily loads that are running for master data loads and transaction data loads in series.
   Thanks in Advance.
Much Regards
Jagadish Thirumalachetty.
Edited by: Jagadish Thirumalachetty on Jul 14, 2010 1:35 PM

Similar Messages

BEx Report Performance with selection-screen input

Hello Gurus,
My Bex report is working fine when the report had run with out PLANT filter in the selection-screen but when report had run with plant in the selection-screen , report running for forever.
Please let me know what I need to do improve the performance.
Saleem.

Hi Saleem, Just a few thoughts;
1. Check the M-table in RSD1 for 0PLANT. In Table View edit any blank or null values. Run the same restrictions you apply in the query at Info provider level > Display Data. If there's any lapse; you can judge where exactly the problem lies.
2. If you are using Infocube & that your master is >20% fact; you can declare the Info object as 'Line Item Dimension'.
3. Create Variants. Esp. if you are running the query for same set of data. Try Variable Preselection: You can restrict both the values + varaiables in the filter level. When you execute the values will be visibly pre-selected in selection screen.
4. As discussed in previous messages, running a SQL trace using RSRT may prove useful.

Report performance while creating report on BEx

All all!
I am creating a report on BOE 4.0 on top of BEx connection as a source. I have developed reports on top of universe in the past and i know that if we keep calculations on reporting end it hampers the report performance. Is this the same case with BEx? if we are following the best practices is it ok to say that we should keep all heavy calculations/ aggregation on BEx or backend for better report performance.
Can you guys please provide your opinion based on your experiance and knowledge. Any feedbacks will help! Thanks.

Hi,
Definitely best-practice to delegate a maximum of CKF to the Cube where possilble, put RKF in the BEx query, and Filters too.
also, add Default Values to your Variables (this will speed up generation of the bics transient universe)
also, since Patch2.10, we are seeing some significant performance improvements reducing 'document initialization' and 'time to prompts' by up to 50% (step such as these often took 1.5 minutes, even on sized systems)
Also, make sure you have BW corrections like this implemented: 1593802 Performance optimization when loading query views
In the BusinessObjects landscape - especially with BI 4.0 - it's all about Sizing and Tuning . Here is your bible the 'sizing companion' guide : http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000738725&_OBJECT=011000358700000307202011E
Pay particular attention to BICSChunkSize registry settings
Also, the -Xmx JVM Heap Size for the Adaptive Processing Server that is running the DSL_Bridge service.
Regards,
H

BEx Cell Report - Performance Issue

All,
We have a BEx Report in which I have used cell formulas extensively.
My BW ver 3.0B and parch 31. From last f32 weeks this report is working only for maximum of 9 materials. Tthe report output comes very fast. The momemnt I give 10th material or more in the parameter screen, the report never comes out.
I tried SAP Note : 976996, still the same problem.
Can anyone please help?
Thanks
RS

Hi,
just create a proper index and performance will increase. There are some SAP OSS notes who deal with this (for example field "client" should be added if'm not mistaken).
We did the same on profit center tables with huge performance increases
grtz
dries

Strange performance issue in bex report

Hello Experts,
I have a performance issue on my bex report.
I'm running the report with below selection criteria and getting 'too much data' error.
Country : equals EMEA
Category: not equlas 13
Date : 02/2010 to 12/2010.
But when I ran the report for smaller date ranges the number of records are not exceeding 13000.
02.2010 - 06.2010 - 6,555 rows
07.2010 - 09.2010 - 3,671 rows
10.2010 - 12.2010 - 2,780 rows
I know excel can't fit more than 65000 records, but I'm expecting 13000 records for my wide date range which excel can easily fit.
Any ideas on this one will be appreciated.
Regards,
Brahma Reddy

Hi,
For Question 1:
In query designer Go to the Query properties and select the tab "Variable Sequence", here you can set the order of variables as per you requirement.
For Question 2:
There will be a option "Hide Repeated Key values", if you uncheck this option then you will have the values for each row even though the material values are same.
Note; if you are viewing the report in web or WAD report you need to make the same changes in the Web template also because the settings in the query designer will be overridden when you run the query in web.
Hope this helps.
Regards,
Rk.

Report Performance Testing in BEX or Portal + process Chain testing

Hi Guru,
i am looking for a tool in BW where BEX reports or Portal reports can be tested.
What i looking for is a possibility to log on virtual users (100.+) for a report and check how faster that report can be runned.
It is a tool where i can test the process chain perormance too?
a How to could be very helpful too.
Thank in advance
SLT

I found a solution.

2004s Web report performance is not good ,though that of 3x web is OK.

Hi,
I feel 2004s Web report performance is bad, though that of 3x web is no problem (the same query is used.) it is worse than BEx analyzer.
This query has more than 1,000 records and those queries that have many records result in the same bad performance.
Of course there are many reason for this bad performance, please tell me your solution by which you solve the same problem like this.
the SIDs of EP and BI is difference here.
CPU is not consumed when 2004s web report is executed.
And I have cancelled virus scan to this web report...
Kind regards,
Masaaki

It is bad, am sure it's down to the new .net and java based technology. Aggregates are a way forwards though from what i've heard of the BI Accelerator this is the real way forwards.

Bex Report Designer: Error while loading metadata

hi experts,
I am working with BI7 Bex Report Designer and we are using SP9. when i tried to load the Query in Report Designer its giving below error.
Error while loading metadata.
Check the Query and portal settings.(but the query is working fine in Analyzer).
and its giving message class RSBOLAP, message number 018 and Description is java system error: incoming call is not authorized.
when i double click the error its giving below error details.
Diagnosis
An error occurred in the BI components on the SAP J2EE Engine.
System Response
Procedure
Contact your system administrator to have the error analyzed in detail.
Procedure for System Administration
Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.
could you plz suggest me how to rectify the problem.
regards
vadlamudi

Hi vadlamudi
The error message RSBOLAP 018 means, that the ABAP stack can't communicate with the Java Stack.
1) Please ensure, that the user, used for the Report Designer, is valid in the Portal too. Depending on the user management setup this means that there either needs to be the same user or an assigned user in the Portal.
2) In case the user is valid, it means a basic misconfiguration according to note 937697. In this case please run the Support Desk Tool and ensure, that all checks are green. Please ensure, that the latest version of the Support Desk Tool is used.
Regards,
Janine

Best approach to "migrate" from BEX reports to Webi reports ?

Hello,
i have read lots of documents regarding best practices on how to built webi reports and universes on top of BW.
But i can't find any document about best approach, not in performance way of thinking but in best way of using reports.
i mean: when end users are coming from bex reports (where they can drill down through hierarhies and use free filters ) to webi reports (where layout is quite beatiful and user can change it easely), this is not the same way of consuming reports.
I come from BO world and are new on reporting on top of BW.
for me webi is good for quite static layout reporting where data is clear and available.of course you can have prompts for interactivy and more accurate reporting. Drill down is just a functionality but is not the real purpose of the report tool.
So ,according to me there is a gap between both tools (BEX and WEBI) but end users are the same.
So i 'm wondering if you have any feedback for the best approach to build webi reports where end users are coming from bex reporting.
And how to choose between prompts, drill-down (with available filters on top of the window), fold/unfold and input controls or just having diffrent levels of hierarchies in the table/ section/ breaks but without drill down (because if you drill down, report begins weird with diffrent levels) ...?
So , if you have any feedback , advise....
thanks in advance,
Rgds,

Hi,
WEBI don't replace BEX reports, is for different audience, in fact BEX is for OLAP reports and analysis.
You can find some answer in this page
[FAQ: The Future of SAP NetWeaver Business Intelligence in the Light of the NetWeaver BI & Business Objects Roadmap|FAQ - The Future of SAP NetWeaver Business Intelligence in the Light of the NetWeaver BI&Business Objects Roadmap [original link is broken]|FAQ]
spercific for What is the future of the BEx Query Designer? you can read here
[FAQ - The Future of SAP NetWeaver Business Intelligence in the Light of the NetWeaver BI&Business Objects Roadmap [original link is broken]#section11] and here [FAQ - The Future of SAP NetWeaver Business Intelligence in the Light of the NetWeaver BI&Business Objects Roadmap [original link is broken]#section3]
The idea is to use the rigth tool for the rigth job.
You can find more information here [http://www.sdn.sap.com/irj/sdn/edw], [http://www.sap.com/solutions/sapbusinessobjects/index.epx], [http://www.sap.com/solutions/sapbusinessobjects/newsevents/index.epx], [http://www.sap.com/community/flash/BusinessIntelligenceAGuideforMidsizeCompanies.pdf]
I hope this help you.
Best regards.

Significance of BEx Reporting flag in ODS objects

Hello Masters,
I would like to know in detail, the Significance of BEx Reporting flag in ODS settings. What happens if we flag, and hat happedn when we dont ?
If, Transaction Data is loaded into the ODS, without loading the relevant Masterdata in advance, are SID's created, as it happens in cube ?
IS there a connection between SID's and ODS objects ?
best wishes,
i BI

Hi,
From SAP help : With the BEx Reporting indicator, you determine whether the ODS object is immediately available for BEx queries. If the indicator is not set, no SIDs are generated for the new characteristics when the data in the ODS object is activated. This optimizes the performance of the activation process, but the ODS object is not available as an InfoProvider for queries. Turn the indicator off for all ODS objects that are only being used for further processing of data in other data targets or that are being used in InfoSets.
http://help.sap.com/saphelp_nw04/helpdata/en/a6/1205406640c442e10000000a1550b0/content.htm
Hope this helps...

Change date format in BEx report

There is a date field in report which is character type.
ZCOMDAT - compensation date (CHAR 8)
The output of this file in report is YYYYMMDD (20110422) format which is char
This should be converted to 22-APR-2011 in BEx report.
This object is used in many reports but only in this report it should be converted.
How can this be achieved?

Hi akshara,
Apart from the above mentioned approaches i have one strange solution . You might want to consider this .
You said you have an infoobject ZCOMDAT of type char(8) .
Proceed like this :
1) In the infoobject maintain medium text for this . Insert this characteristic as an infoprovider .
2) Now since this infoobject will have the dates in the master data and hence in /BIC/PZCOMDAT table .
Create a generic datasource on this table : /BIC/PZCOMDAT .
Now create a transformation between this generic datasource & the text master data of ZCOMDAT.
map date and objvers to the text in the transformation .
And write the following routine at the field level :
If SOURCE_FIELDS-OBJVERS = 'A'.
year = SOURCE_FIELDS-/BIC/PZCOMDAT+0(4).
mon = SOURCE_FIELDS-/BIC/PZCOMDAT+4(2).
dd = SOURCE_FIELDS-/BIC/PZCOMDAT+6(2).
if mon = '01'.
mth = 'JAN'.
ELSEIF mon = '02'.
mth = 'FEB'.
ELSEIF mon = '03'.
mth = 'MAR'.
ELSEIF mon = '04'.
mth = 'APR'.
ELSEIF mon = '05'.
mth = 'MAY'.
ELSEIF mon = '06'.
mth = 'JUN'.
ELSEIF mon = '07'.
mth = 'JUL'.
ELSEIF mon = '08'.
mth = 'AUG'.
ELSEIF mon = '09'.
mth = 'SEP'.
ELSEIF mon = '10'.
mth = 'OCT'.
ELSEIF mon = '11'.
mth = 'NOV'.
ELSEIF mon = '12'.
mth = 'DEC'.
ENDIF.
CONCATENATE DD '-' MTH '-' YEAR INTO RESULT.
CLEAR:DD,MTH,YEAR.
endif.
After this load the the data . Now your text of this object will be having the date required in your format.
3) In the query level display text for this infoobject .The date will appear in the format as you desired .
You have to include the above flow in a process chain .
Using the above method will not effect your query performance also as the calculation are happening during loading .
Hope the above reply was helpful.
Kind Regards,
Ashutosh Singh
Edited by: Ashutosh Singh on May 21, 2011 9:43 AM

BO migration from BEx reports

One of my client is running on SAP IS Retail 6.0, and they have few BW reports. Now they are looking for migrating the BEx reports to BO XI.
They do not want to change anything, but want to port the reports as is to BO from BEx.
My previous experience of porting BEx reports to BO as is, without puting extra filters of something, to reduce the huge data size images was not good at all.
Is there any way to have better performance in BO than the current BEx performance, if we want to port the reports as is without any structural change?
Please share your experience with me.

My company is running Webi reports using BOBJ XI 3.1 (up to current fixpack level) on SAP BI 7.01 EHP1-SP5. This config gives 50% reduction in Memory, 30% improvement in runtimes, on average compared to 7.0 BI, according to SAP. But is it good enough for full corporate deployment?
My understanding of the Webi <-> SAP BI architecture is that we still have a large image sent to the XI Box from the query -> universe -> Webi report refresh. The big flaw here in my view is that Webi is disconnected from the OLAP database tables after the refresh, thus must 'image' everything the report requires, in our case into a 32 bit Windows NT box.
This is quite different from the SAP BI OLAP front-end model, in which user navigations are threaded in various ways (sometimes from cache, from aggregates, from indexes on the DSO characteristics etc), as we can see in our BI OLAP processing steps in BI statistics.
After the Webi refresh, there are no 'threads', or calls, back to BI ABAP tables, as the Webi report has to represent all the potential navigation in the MDX model. For this reason it seems a fundamentally resource-intensive architecture, that can induce instability when very large sets of data are retrieved in concurrent user sessions. By "large" think of the 'cubed' size (count of characteristics X count of key figures X number of transactions).
If user activity results in concurrent refresh calls to generate large report 'images' from SAP BI, I have observed 100% CPU freeze in BOBJ XI, and user lockout until resources are again freed up, which can take a very long time for certain reports. Subsequently when the large images are subjected to user OLAP navigations, CPU processing again will spike.
When running large image reports, the Webi performance has been an 'order of magnitude' slower than our reports running on ABAP web. Unfortunately, the risk is greater than just slow performance - there is the CPU and memory resources that are engaged during that extended processing interval as well.
Much depends on the normal level of user activity. This is a matter of simple statistics. Say your overalll production BI system load averages ten users per hour running reports. If Webi report runtime averages 30 minutes per refresh, and BEx ABAP runs in 5 minutes, the probabillity of concurrent resource collisions is much higher - from 10% to 50%, thus the situation can snowball rapidly.
I think SAP is working very hard on this problem, but has issued guidance as recently as May 2009, that if you have current BEx reports that are working, don't migrate them all yet. Unfortunately our users are anxious to run everything in the Webi tool, because it is indeed a super user interface.
However, customers have until 2016 until the Bex tools are phased out. Interviewed by Searchsap, Jonathan Becher, SAP Sr. VP, said, "There are lots of scenarios that BEx does just fine, if you're confident using BEx, don't rush." The same article also quoted Cindy Coyle of Coors, who had tested the Webi BOBJ: ""Don't go near Business Objects [until you get a BWA]," Coyle said, "because it'll only add more performance problems on top of what's there today." Article: http://bit.ly/2HJUqf
Edited by: Douglas Grant on Oct 18, 2009 7:26 PM
Edited by: Douglas Grant on Oct 19, 2009 9:51 AM

ODS reporting without Bex Reporting activated

Hello
As part of a review I have been doing on our current BW data loading strategy I have uncovered a number of ODS objects that have the Bex reprorting indicator active. The consequence of this is that it has a negative impact on performance when loading data into BW, particularly if we have to re-initialise the data.
We currently do not actually report off the ODS object and from the research I have done the consensus seems to be that you should leave the bex reporting indicator turned off unless absolutely necessary and to use an infoset for reporting.
In the coming week we will be faced with having to reload 15 millions+ records back into these ODS objects after doing a redesign so thought it a good time to untick this option.
I should mention that we are using a BW 3.5 system.
Any comments would be appreciated and if the preference is to use an infoset, then can someone give a practical example why you would ever want to set an ODS to allow bex reporting other than the obvious response of not wanting to create an infoset Would i be correct in stating that I wouldn't be able to use indexes to aid performance if i use infosets. I'm reluctant to pass this data into an infocube given the amount of data as it contains asset transaction postings.
An additional side question which is more for my personal interest is whether it is true that it is not preferential to include ODS objects (or infosets) within a multiprovider given that strictly speaking the ODS object is not multi-dimensional. I recently read this in an article and had not considered this before so was wondering if it is correct.
Thank you in advance for your responses.
Regards
Mark
Edited by: majohnson on Mar 31, 2011 1:35 PM

Hi Christoper
Thank you for your response. You seem very passionate about not reporting on ODS objects
What I do find interesting is that there are a number of standard content ODS objects which do have the bex reporting indicator active.
I'm forming the view that if you do not have performance issue considerations loading data into ODS objects and you can control the amount of data selected via reporting using indexes and query restrictions etc then an ODS is still useful for reporting or alternatively the infoset option. That said, this does not apply to the ODS objects I was referring to in my main post and I will be deselecting the bex reporting indicator before re-initialising the data.
I have always been led to believe by people who know more about BW than myself that the infocube is designed for summarised / targeted multidimensional data and that storing line item information in an infocube seems to be contrary to this position.
Our current design approach standard in that we load data into a staging layer (Generally ODS objects, most of which do not allow bex reporting, and some of which contain line item information), then into a transformation layer (generally infocubes) and finally we report out of multi-providers in our reporting layer.
Our general reporting strategy has been that operational style reports which would include line item reporting should be done within ECC and all other strategic, summarised reporting etc is delivered in BW.
Regards
Mark

ODS Bex Reporting Indicator

Hello All
We are using BW V3.5 and an ODS 0FIGL_O02. In the data model, this ODS was feeding up to a cube and we were reporting off a multiprovider. We encountered load and performance issues so as part of a model review we switched off the Bex Reporting Indicator in the ODS settings. It made little difference to our performance problem so we simplified the model and decided to report off the ODS after switching back on the indicator. We transported the ODS and the report separately.
This solution worked fine in our DEV and QAS clients but not in the live system. Using Bex we can open the query in prod but when we run (via a portal) we are getting the error message that "ODS 0FIGL_O02 not configured for Bex Reporting". Also if we attempt to create a new report on the ODS in Bex the ODS cannot be found.
We can see the Bex indicator is on in all clients. We have used RSDG_ODSO_ACTIVATE to check the ODS consistency in all clients and in Prod we get an amber light with the message "The Bex reporting was switched on for ODS object 0FIGL_O02" and a green light with the message "ODS object 0FIGL_O02 is consistent".
We have tried creating a new ODS using 0FIGL_O02 to copy from but again encounter the same problem in Prod.
Does anyone have any input or come across the same problem ? Should we create a brand new ODS ...?
Thanks in advance for your input.

Helen,
You can switch On BEx reporting, even ODS contains data. Initial activation of ODS takes time, as it tries to create/generates SID's for historic data.
Using "Foreign Key Relationship of Reporting-Relevant ODS Object and SID Table Characteristics" showed 2 red lights for data entries in the ODS, fine, but a data issue shouldnu2019t affect the ODS Object status?
We also get an amber light that BEx Reporting was switched on for the ODS u2013 how would we get this light to green given we canu2019t change settings in live client u2013 have already tried OSDG_ODSO_ACTIVATE and as previous posting re transporting.
Try to correct in RSRV, using option correct at menu bar. Have you tried, are you getting any message...? after correction do test again... it should be green.
Try to find out any program or function module and reactivate ODS data again to generate SID's again.
Hope it Helps
Srini

Error Transporting FI ODS with Bex Reporting On

Hello,
We are getting error
"Value Xxxxx for characteristic 0INV_DOC_NO is invalid".
"Value Xxxxx for characteristic 0REF_DOC_NO is invalid".
"Value Xxxxx for characteristic 0REF_KEY1 is invalid".
"Value Xxxxx for characteristic 0REF_KEY2 is invalid".
"Value Xxxxx for characteristic 0TXTLG is invalid".
"Value Xx#xx# for characteristic zsmthg is invalid".
in transport log while activation fo ODS, we have only checked Bex reporting flag to report on ODS and
are trying to move the request to production .
This ODS has approximately 14,000,0000 and upper level cube is working fine for reports.
Any Ideas for this error message ?
Thanks
Ooops

Hi,
when activating your ODS for reporting, the system will generate master data SIDs for all IObjs of your ODS.
In other words, your ODS was prior this setting just a table with fields not usable in reporting thus not checked when loaded.
Now the system is checking each value of the IObj and verify that it complies with the IObj rules (lower case not allowed, special characters allowed in Tx RSKC, and so on...).
If the values are fine, the system will create this master data and corresponding SIDs for all IObjs if they aren't created yet)...
All these checks are performed because you now want to report on this ODS, therefore the system will link your ODS table fields an their corresponding IObjs...
I suggest to copy your ODS to another; enable the reporting flag on the copy and start loading some data from the original to the copy and escalate the several issue you will face one by one.
Hope this helps
Olivier.

Bex Report Performance

Similar Messages

Maybe you are looking for