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

Similar Messages

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

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

Report on standard ODS object and transactional ODS object

hi gurus
i have an infoset which is built on two transactional ODS objects and one standard ODS object which gets the data on regulr schedule. the transactional ODS obejcts get the user entered data.
when i query on the infoset, i am getting the data. and when i query on the standard ODS object i am getting the data. but when i am trying to create a query on the combination of the Infoset and the ODS object i am not getting the data.
is there any way to generate report on the standard ods object and Infoset from transactional ods objects.
your help will be greatly appreciated.
thanks in advance
vijaykumar

Hello ViJaY,
how r u ?
Try creating a MultiProvider with the Standard ODS and InfoSet.
Best Regards....
Sankar Kumar

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

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

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.

BEx setting in an ODS

At the moment I am loading to an Inventory Snapshot ODS which does not have the BEx reporting flag set.
After the loads are complete am I able to change the setting and switch the BEx flag on and thereafter be able to report on the ODS or would I need the setting checked before the load? Thanks

Hi Niten,
It's better do before the data load. Because you may not activate ODS again with BEx flag set after data load.
See so more here:
Re: ODS Reporting
Best regards,
Eugene

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

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

Unable to see ODS Object in BEx.

Hi all,
I am unable to see an ODS object in BEx, which is an active ODS Object with data in modelling.
Can any one show me a way out, how to find this ODS object in BEx as well.
Thanks in advance,
Regards.

Hi Robert Zovic
Thanks for your answer,
When I switced on th same..following is the eror message:
The BEx Reporting was switched on for ODS object 0RPM_DS02 ---> long text
Message no. RSDODSO157
System response
When activating ODS object 0RPM_DS02 SIDs have to be got for all characteristic values in the ODS tables, provided that these characteristic values are not already assigned any SIDs. This is required because the SIDs are used in BEx Reporting.
The activation of ODS object 0RPM_DS02 can thus take a while longer.
Procedure
If the activation of ODS object 0RPM_DS02 terminates due to timeout you have to activate the ODS object with the program RSDG_ODSO_ACTIVATE in the background.
I'm working on this, is there any other way out for the
same.
Thanks.
Regards.

ODS BEx Indicator flag

How can I check what ODS have the BEx Indicator flag checked? Thanks

Hi Niten,
Double click on ODS -- go to Settings (folder / tab) see the BEx Reporting - if there is tick in check box that mean you can do reporting on this ODS otherwise not.
hope it helps
regards
Vikash

ODS Bex Reporting Off and SID Question??

Hi...
We were looking at the Specific question below:----
We have switched off the BEx reporting functionality on an ODS and are using an Infoset to query against the ODS, so there is only 1 table in this Infoset.
Question:----
Does the Query written on this Infoset need to go through a SID table fo eg: It spends a lot of time in Serial Nbr SID table (/BIC/SZSERNR) which is an Infobject used in the ODS.
I tried a few things as explained below:----
I actually created a few New Infobjects based on the Infobjects from the Original ODS. We created a new ODS similar to the original ODS by replacing some of the Old Infobjects with the New Infobjects. I switched Off the Bex Reporting option for this ODS. It did not inserts any SIDs while loading the Data into this New ODS...However while executing the Query on an Infoset built on this New ODS, it updated the SID table for the New Infobjects.
I was wondering when the option of Switching Off BEx Reporting is to facilitate faster Loading of Data, why does the query need to insert the SIDs during the Query execution as that increases the Response time on the Query. These New Infobjects are not used in any Infocubes so is there a necessity to maintain the SIDs as we are trying to Query on an Infoset.
Please provide your valuable opinions..
Thanks and Regards
Andy

Andy,
I'm not sure, but this could be a track.
The ODS or Infoset are checked to update the BW Statistics? Maybe a update is taken if BW Statistics are tracking the query execution on these dataproviders.
Henrique

Significance of BEx Reporting flag in ODS objects

Similar Messages

Maybe you are looking for