DSO - BEx Reporting Flag

Hi All !
During implementations, data flows goes like Datasource -> DSO -> Cube -> MP -> Reporting
In all DSO's, BEx reporting flag is checked. Though reporting is done on the cube. Does checking this flag reduces the performance? Please advise
With Regards
Rekha

If you tick the checkbox related to reporting in your DSO settings, it generates the SIDs at the time of data loading (while activating the data) which in turn make the DSO available for reporting.
As for the performance, these SIDs help in query performance, however it decreases the loading performance (because of the SID generation).
So take a call based on whether you really need these DSOs for reporting as well. If not, you can simply uncheck the setting for reporting. This will help you improve the loading performance.
Regards,
Yogesh

Similar Messages

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...

Turning On Bex reporting Flag

Hi,
We have ODS size of 7 million records. The Bex reporting Flag is swithched off on this ODS and I would like ON it now.
Do I have to clean the data and relaod everything back in or is it ok to switch on the Flag now and transport it?
Thanks,
AB

Hi,
You can turn on the bex reporting without deleting data, but if you activate the ODS it will create SID for the entire ODS contents. It may take long time to activate depending on the ODS size. See whether you have enough wait time in your foreground and background(while transport) before doing this.
Regards,
Raghavendra.

Bex reporting Flag

Hi,
I am planning to uncheck the Bex reporting flag in a ODS. So to transport the change do I need to transport any thing else or just the ods?
Thanks,

capture the change in ods in a request and transport that alone.
Ramesh

Bex reporting indicator in DSO's - table to check

Dear Gurus,
I have a requirement to check all the DSO's BEX reporting flag whether selected or not. Is there any table to check this settting. I have verified RSDODSO but couldn't get it. If aany one know any other way please let me know .
Thanks in advance.
Regards,
RS

SE16 - RSD_S_ODSO - Select SID generation field(tru or false) and execute .. change the number of hits to 999

BEX Reporting while ODS Activation

Hi,
I have an ODS with BEX reporting enabled. While doing ODS activation users are able to execute query on this ODS. Which giving partial report as activation is going on (it is really misleading). Is there any way to restrict users from accessing the ODS data while activation going on? Or set the reporting flag after completion of ODS activation (Currently reporting flag is getting set while activation going on)?
We are in BW 3.5, Patch Level - 0012
Thanks in advance
Vinod

Hi Vinod,
Its better to make Bex Reporting flag enabled after ODS activation.
If they are executing queries while activation of ODS is going on they were able to get data only from the requests which are loaded in ODS and r ready for reporting(activated requests).
Regards,
Rajkandula

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.

Setting the 'reportable' flag for a very large ODS

Hello Community,
I am working on a very large BW system (6 Tb), and we recently have the need to set the 'BEx Reporting' flag on some very large ODS objects.
It was my impression that setting this flag would be easy to do. But the transport that contains this flag for six large ODS objects has already been running for more than 16 hours.
Can you tell me, what actually happens in the database when the 'BEx Reporting' flag is turned on for an ODS ?
Thanks !
Keith

Hello Bhanu,
Thanks for the quick response. Are you able to provide some more information ?
are the SID values created in a new SID table ?
if the ODS was already very large, then would you expect the new SID table to also be very large ?
what about the case if a SID value already exists for the characteristic ?
Thank you !
Keith

GR and IR as separate columns in the BEx report

Hi,
I am working on a Purchasing report in which the user needs the snap shot of PO history,Like PO no.,Item,Netprice,PO Qty,Net order value,GR no.,IR number etc.
I created a view on EKPO and EKBE.Here,based on the BELNR(Material document) field we are taking GR and IR values.(When VGABE =1 BELNR=GR and VGABE = 2 BELNR=IR).I created DSO to load the data.The problem is they need the GR and IR as separate columns in the BEx report.Could u please help me how to achieve this in BI?
Thanks & Regards,
Dinakar.

Hi Neel,
I need the BELNR has to be split into GR No.and IR No. separately based on VGABE field.
Thanks & Regards,
Dinakar.

BEx report : Time diff HH:MM average Issue

Hello Guys
below is my Issue with BEx report.
I have a table with has d1 and d2 and t1 and t2.
I want the diff between them in only HH:MM, using any of the function modules.
I have got the HH:HH value into my DSO.
Then I converted the HH:HH into HH:MM in the BEx.
Now my report requirement.
I want to display the report with yearly , monthly and daily information -
let say my boss wants to compare Average time ( HH:MM) between June and July of 2007.
the report should be
year ++++++++ month ++++++ daily ++++++++ rec#++++++++ diff
2007++++++++ June++++++++ 01++++++++ 123++++++++ 31.36
2007++++++++ June++++++++ 01++++++++ 124++++++++ 11.23
2007++++++++ June ++++++++ 03 ++++++++ 152 ++++++++ 18.21
2007++++++++ July ++++++++ 01++++++++ 157 ++++++++ 12.27
2007++++++++ July++++++++ 08 ++++++++ 124 ++++++++ 15.33
now when you look at the above report layout.....what i want is to display the average time ( diff) for month of june and july.
so the average time diff of the month of june will be ( total time / record count ). same for july.
so the result should be for
JUNE - (32.36 + 11.23 + 18.21) / 3
JULY - (12.27+15.33) / 2
also it should convert the decimals (MM) into hours after 60.
I am getting the sub total for month June as ((32.36 + 11.23 + 18.21) / 3).
Its not converting the MM in HH even after 60 Min. say for example its showning 40:67. but the correct value should be 41:07
hope you got my issue.could you please suggest the solution as to how can i get the correct value under the month sub- total.
thanks,
pratap.

Hello venku chittidi ,
Thanks for the reply.
But the User wants to display the values in HH:MM instead of MM.
would it be possible to calcuate HH:MM from HH:HH in the transformation.
thanks
pratap.

Bex Report issue - transaction data of type Char not dispalyed complete

Hi BI Expers ,
I have one issue related to Bex reports here
I have complete data loaded in DSO , there is one field Job Title which is having a length of 60 char . When I am executing the report in Bex Analyzer , the value for Job Title is getting truncated after 30 characters . Although full 60 chararacters are loaded in DSO still I am not able to present them in reports .
Can some one help here , whether this is Analyzer limitation or is there some setting to fix this issue .
Regards
Anurag

Hi Anurag,
Check the Output length of the object that is giving out put as 30 charecters.
And check in Business Explorer tab option for BEx Description short, medium or High.
Hope this helps.
Veerendra.

Need suggestion for designing a BEx report

Hi,
I need suggestions for designing a BEx report.
Iu2019ve a DSO with below structure:
1. Functional Location u2013 Key
2. Maintenance Plan u2013 Key
3. Maintenance Item u2013 Key
4. Call # - Key
5. Cycle u2013 Data Field
6. Planned Date u2013 Data Field
7. Completion Date u2013 Data Field
This DSO contains data like:
Functional -
Plan --- Item -
Call# --- Cycle -
Planned Dt -
Completion Dt
Location
11177 -
     134 -
     20 -
     1 -
T1 -
     02-Jan-2011 -
     10-Jan-2011
11177 -
     134 -
     20 -
     2 -
T2 -
     15-Feb-2011 -
11177 -
     134 -
     20 -
     3 -
T1 -
     15-Mar-2011 -
11177 -
     134 -
     20 -
     4 -
M1 -
     30-Mar-2011 -
25000 -
     170 -
     145 -
     1 -
T1 -
     19-Jan-2011 -
     19-Jan-2011
25000 -
     134 -
     145 -
     2 -
T2 -
     20-Feb-2011 -
     25-Feb-2011
25000 -
     134 -
     145 -
     3 -
T1 -
     14-Mar-2011 -
Now Iu2019ve to create a report which will be executed at the end of every month and should display the list of Functional Locations whose Cycles were planned in that particular month, along with the last completed Cycle/Date.
Thus based upon above data, if I execute report at the end of (say) March then report must display:
Functional ---     Curr. Cycle --- Planned Date --- Prev. completed Cycle --- Prev Completed Date
Location
11177 -
     T1 -
     15-Mar-2011 -
---     T1 -
--     10-Jan-2011
11177 -
     M1 -
     30-Mar-2011 -
---     T1 -
--     10-Jan-2011
25000 -
     T1 -
     14-Mar-2011 -
---     T2 -
--     25-Feb-2011
Any idea how can I display Previous Completed Cycle and Completion Date (i.e. the last two columns)?
Regards,
Vikrant.

hi vikrant,
You can a Cube at the reporting layer which gets data from DSO and which has these 2 extra characteristics completion date and previous cycle along with other chars and keyfigures from DSO.
You can populate these based on your logic in the field routine.
Hope it helps.
Regards
Dev

BEX : report with real and budget on the same line

Hi everyone,
I need to create a Bex report showing on the same line :
- budget WBS element stored in a DSO (DataSource 0CO_OM_WBS_1)
- used amount stored in another DSO (DataSource 0FI_GL_4)
Data are stored in 2 different DSOs.
If a create a multiprovided with both DSOs I will get 2 lines in my report as axes are different,no ?
Thanks for any idea.
Aussie

Hi,
You can make use of infoset.You can also do a lookup from one dso to another ant transport the values in one dso.So by doin this alll your values will be stored in one place and then you can show the values in one line in report.
Please also give me the idea of keyfields of both dso's.
You can also use constant selection in report if you are using multiprovider through this to some extenet you can solve the problem of values in coming in two lines.
Also check out the below PDF for Displaying Result Row in One Line While Reporting On Multiproviderer.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70dcd7b5-6a3d-2d10-c984-e835e37071a2?quicklink=index&overridelayout=true
Hope it helps.
Regards,
AL
Edited by: AL1112 on Aug 3, 2011 11:55 AM

Bex report doesn't display full text information......

Hi Experts,
My bex report is not displaying full text information.
I have set that particular infoobject length as 40 and also have selected long text and Long Description in Bex Tab of the InfoObject.
In my DSO the data is available in complete lenght but in my Bex report it just displays half information
Instead of displaying Service Order Released its displays Service Order Rel
Can anyone help me to resolve this issue please.
Thanks

Hello,
Setting up the BEx Property for Object, is not sufficient enough to display in the query output. You can always overwrite the object level settings in the query designing.
Moreover, when you create a query, system always overwrite your object level settings and apply the query level settings.
Make sure, you have selected Long Text in the query for that characteristic.
- Danny

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

DSO - BEx Reporting Flag

Similar Messages

Maybe you are looking for