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.

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

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

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

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

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 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 Setting 'Bex Reporting' on SID Generation

Hi,
What impact does it have on ODS during data load with regards to SIDs if
In ODS Settings Bex Reporting is checked.
Thanks

Big data load performance impact, it does create a sid for each load. If you are in 7.0, then you don't need to turn the Bex Reporting if you want to report from the ods.
thanks.
Wond

Bex Query Exception Not Appearing In Bex Report

I have a created an exception in a Bex Query and built a report using the Bex Report Designer. But the exceptions that work fine in the query dont seem to work once I've embedded the query in a report. Is this right? is it not possible to use exceptions in a report or do I need to turn something on etc?
Any help much apreciated.

Hi Joel,
Pls refer the OSS # 331772 reg. this limitation. Exceptions if applied will not be dynamic in RD.
Report designer is a flat structure. You cannot collapse or expand the static columns. Hence, Conditions/Exceptions are not supported in Report Designer. You may try alternatively in WAD. It will surely work in WAD for formatted web based reports.
Thanks,
Arun Bala

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

Concatenation of Data from 4 infoobjects into a single cell in Bex Report

Hi,
I have loaded ODS with the description data. The source system for loading the ODS is the flat file. The ODS data should be a replica of the flat file.
In the flat file, there is a description field corresponding to a particular ID. This Description is greater than the standard 60 char length. So, I had to split the description while loading the flat file using single line routine in the Transfer Structure.
So, while loading different the data, I split the description field data from the flat file into 4 infoobjects and the flat file data was loaded into the ODS.
Now, from the reporting point of view, I need to display the entire description data from the 4 info-objects into a single cell in the Bex report.
Please suggest a solution for this.
****Points will be awarded***

Hi Vineet,
Thanks for the response.
Could you please help me out with the VBA script(code) that needs to be written in the macro.
Thanks in Advance.
****Points will be awarded****
Regards,
Hitesh Shetty.

RFC connection Error While run BEx Report

Hi All
I got BI 7.0 and create new user with roles only access: TR: RRMX to see only BEx Reporting... I create basically new customize role and put only one transcation code RRMX and assigned to user...
When goto BEx designer I got that error
rfc error received user has no rfc authorization for function group syst.
I am not sure what kind of authrouzation user need to only view BEx Reporting...
But when I put SAP_ALL in that profile same user, thats works fine, but I don't want to give SAP_ALL to user...
2nd question same look like BEx Analyzer the side bar when I click open nothing happend and it writedown like German language..
Please advised

Hi Alls
I am Angeline again, I resolved that problem and want to shair with you guys....
1.     Tr: PFCG and click on Maintain roles
2.     Role Name: Z_RUN_QUERIES
3.     Click on Authorization Tab Saved Entry
4.     In Edit mode Select the template: S_RS_RREPU and adopt reference (Business Content)
5.     Expand u2018Business Explorer u2013 Componentsu2019
6.     Selected: u201CType of a reporting component Calculated key figure, query restricted
7.     key figure u2013 template structure and click on Edit
8.     Un-Check REP Query
9.     Generate the Profile
10.     Create Transport number
11.     click on user TAB and define user name in it
12.     click User compare and complete compare and saved the entry
13.     TR: SU01 in User click on Roles and define Z_RUN_QUERIES and profile
Thanks

Header and Footer in a BEx report

Hi Everyone,
I have a requirement where I need to provide a space for the user to sign-off with their name and signature at the bottom of the print-out of a BEx report. For this purpose I need to provide a space at the bottom of the report where the user can write their names and sign-off. It should be something like:
Name: _________________________________-
Signature: _______________________________
Date: ___________________________________
Is there some way I can add all this as the footer text in the BEx query?
Thanks,
Ram

If the BEx query can use a "structure" in the rows section....
Under last row, add a selection = company code, set it not equal to the company code, & change the description =
NAME: ____________________________________________
Then, copy the above row, but change description to =
SIGNATURE: _____________________________________
Repeat, copy the above row, change description =
DATE: ____________________________________
If you want to add blank lines, copy one of these rows, but change description = a period = .
By setting the restriction <> to the real company code, then that row should be blank straight across, except for the description.
A better/more professional looking option is to put the BEx query into a web template, add 3 HTML rows under the query result table, add text per your specs. Then save web template to the appropriate role/folder to publish it on the portal.
Edited by: Sharon West on Dec 11, 2008 10:17 AM

Turning On Bex reporting Flag

Similar Messages

Maybe you are looking for