Free characteristics in Webi? & variable screen from bex to webi

[Former Member]

Hello,

Where would you add the free characteristics while designing the webi query? Is there such a concept as free char in webi, free char has been great help for our end users.

Also when you are creating universe on a bex query, would all the variables that you have created in variable screen come over as pre defined filters in Webi? Like if you have variable for a single mandatory fiscal year or Selection option variable for Funds Center how would these come over in webi?

Please let me know. Thanks in advance.

[Former Member · Accepted solution]

Hi,

the basis concept of free characteristics in webi can be found from XI SP3 on, with a feature called "query stripping". Having that enabled, will only send the needed dimensions to the backend, as opposed to all dimensions in the webi query.

You add the "free characteristic" to the webi query then.

All BEx variables will transform into the BO counterparts, e.g. in BEx a single mandatory variable on fiscal year, will become a single mandatory prompt in webi. Here some interesting links for you:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e058e44e-9497-2b10-f9b8-aab169b01...

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008d15dc-f76c-2b10-968a-fafe5a121...

Regards

[Former Member · Accepted solution]

Thanks Victor and Madhu,

SO basically in Bex you used to create one query and add a few free charateristics as " we might use them" cannot be done in webi before SP3? Basically for every new object which is needed on the report you have to create a new query how how do you do it?

If the Result object of the query lets says have org unit, employee area, amployee sub area and employee and this query is saved a webi document, after the user runs it can the user lets say get rid of the employee and save a "view" per say for himself in his My Documents?

Thanks again.

[Former Member · Accepted solution]

Before query stripping, every characteristic you add thinking "we might use them", would have an impact on performance.

For every new object that you need in the report, you would easily edit the webi query and add the object to the report.

Yes, you can edit a report and save it under your favorites folder, thus creating a personalized "view" of the report. Taking your example, you could delete the column "employee" from the report and save it under your personal folder.

[Former Member · Accepted solution]

Thanks Victor for the explanation -

+Before query stripping, every characteristic you add thinking "we might use them", would have an impact on performance.

For every new object that you need in the report, you would easily edit the webi query and add the object to the report+

When you say, you would easily edit the webi query and the add the object but if this query is used by multiple user than the change will will affect all users right?

Yes, you can edit a report and save it under your favorites folder, thus creating a personalized "view" of the report. Taking your example, you could delete the column "employee" from the report and save it under your personal folder

I think I am going in the same direction as first questions, probabaly I am not understanding the difference between query and report. When a user edits a report he is not affecting the query?

When you create a webi document report designer gives it a technical name?

Thanks again Victor.

[Former Member · Accepted solution]

Hi,

let me start from scratch. There is a huge difference between a BEx query and a webi query, same is valid between query and report.

A webi query is just a bunch of dimensions (In BW language: characteristics) and key figures that you would like to use in your report, in order to visualize the webi query with data, you need the webi report with certain components, lets say a table or chart. A webi query can only be created from within a webi report and is only valid for the webi report where it resides.

When you create a report from a BEx query, your layers would be in following order:

-webi report with embedded webi query

-Universe

-BEx Query

Now to your first question, if a change in the webi query will affect all the users using that particular query: It will affect the webi report and with it, the users that have access to that report. Key point to understand here is that the webi query resides inside the webi report, thus it will affect only 1 specific report, nothing more. But of course you could do that in your favorites folder, any change will only affect your copy of the report (and thus your copy of the webi query)

To your second question: When a user edits a report he is not affecting the query? Exactly, you can edit the report (e.g. convert a table to a chart) without making any changes to the webi query.

Third question: When you create a webi document report designer gives it a technical name? Your report will be given an ID which is unique in the system and an CUID which is unique in a system landscape (dev and prod).

Best Regards

[Former Member · Accepted solution]

Victor,

That is some really good information you have given me and that gives me a very good insight. I have one more questions about webi query v/s webi report like who creates what in what sequence.

So let me see if I can re-iterate in a way what you said. Let us say I create a webi query (I am assuming we create query and give users the access to that) and you save it as what webi document in public folder now users can take that webi query choose the dimensions and measures and filters (pre-defined or user defined) and create a webi report out of it and save it in their my folders or their dept folder in public folders?

Correct me if I am wrong and thanks for patiently answering some of these very basic questions for me.

Thanks.

[Former Member · Accepted solution]

Hi Cathy,

The only point is that the whole process concentrates on the webi report (not on the webi query). So, you create a basic webi report, share it on InfoView, and give access to certain users to that report. Everything else you said is exactly right.

Regards

[Former Member · Accepted solution]

Thanks Victor for answering all the questions patiently.

[former_member192236 · Accepted solution]

Hi Victor,

Need clarification on Query stripping. How it works. Correct me if my understanding is wrong..

We are dragging 5dim obj and 2measure obj to Result Objs pane.On execution, BO requests data(from BW) for those 5dim and 2measure obj and displays the report and stored in microcube cache. Now the property 'Query Stripping' is enabled and the user removes one of the column(dim obj) from the report. So on refresh, BO requests data from cache only for 4dim obj and 2measure obj eventhough microcube has 5dim,2measure obj..Is this correct? Is this how the performance improves bcos of Stripping property?...So Does it mean Query stripping helps only in these scenarios...?

Pls clarify i could not fully grasp how the system improves the performace bcos of Query Stripping property and its working nature.

Many thanks in advance.

Regards,

Kesavan.

[Former Member]

Hi,

It may be helpful to you:

http://wiki.sdn.sap.com/wiki/display/BOBJ/OptimizequerywithQueryStrippinginWeb+Intelligence

All the Best,

Madhu...