Query View Workbook

You formatted a query view ( By changing Fonts/column width etc ) and saved as workbook in your favorites in the Browser.

When you execute the workbook thru the browser you get the format that has been saved. However, you loose the format when you click the Refresh Button.

How to set permanent settings so that formatting remains same as has been designed in the workbook?

You can do this :-

In Excel using BW, you have what I categorize as 2 different types of cells.

You have "Excel" Cells and "BW" Cells. You can determine which you are in by selecting a cell and right mouse clicking. If you get the BW options (Drilldown, Swap, Insert.....) then you are in a BW Cell. If you get the standard (Cut, Copy, Paste) you are in the Excel Cells.

If you are formatting an Excel Cell, Format using the option from the Excel Menu. If it is a BW Cell, Format using the option from the BW Toolbar (5th button from right).

When you refresh you will retain your settings.

Also, as a hint, you don't have to select all of your BW cells when formatting. Select a characteristic and format using the BW toolbar and all characteristics will format. Same goes for key figures, Free characteristics etc.

BW uses the "BW Style Tool"to format. For more detail and customization follow the below steps:

1. Download OSS Note #300570.

2. On your machine
Find / Execute SAPBEXS.XLA -> Click Enable Macros.

BEX Query Authorizations

We are have authorization issues with Querries. We have created a generic
Role that has some Standard Query's for our Company attached to this Role.
We give access to this role to our user community. The problem we are
having is that the users can Execute the querries and what they are suppose
to do is only Save the Workbook to there favorites. We are running across
a problem because some of the users are saving the workbook as existing
workbook. So when they do this it wipes out the Query in that Role. How
can I stop users from overlaying the MASTER Query. There has to be a way
that you can protect a query so that it cannot be changed. Because we
have generic querries that are being used throughout our company, I need to
be able to protect the query so that it can only be saved to users
Favorites.

-----Reply Message-----
Subject: RE: BEX Query Authorizations

We would appreciate anyones input that could help us with this authorization
issue that we are having. Maybe if we could get input as to how other
Companies are handling there workbooks. There has to be a company that is
having the same problems with Workbooks being overwritten.

Any input would help

-----Reply Message-----
Subject: RE: BEX Query Authorizations

Hi,

Unfortunately I haven't managed to restrict access
to workbook depending on its menu location.

Hey gurus, it would be great to know any more ideas...

Best Regards,

-----Reply Message-----
Subject: RE: BEX Query Authorizations

Hi,

We tried changing the role and are unable to overly the generic role. But
we're unable to save a workbook to our favorites. Any ideas??

-----Reply Message-----
Subject: RE: BEX Query Authorizations

Hello,

Go to role maintenance (PFCG) -> Authorization ->
Chanhe Authorization Data.

Open Basis - General Functions -> BC-SRV-KPR-BDS
and restrict the user activities set like
"Display, Print, Retrieve from Archive, Determine, Assign".

User with appropriate role could not be able to overwrite
WORKBOOKS (!!!).

As for QUERIES, address to
Business Information Warehouse -> BEx - Components
and restrict Activities retaled to Queries -
then users with appropriate role could not be able to
overwrite GLOBAL DEFINITION of QUERY (!!!).

So, you can see, you need to restrict access to queries and
workbooks separately.

Best Regards,

-----End of Message-----

Differences Among Query, Workbook and View

Many people are confused by the differences among: Query, Workbook, and View.

Here are my thoughts on the subject:

A query definition is saved on the server. Never anywhere else.

Although people say a workbook contains a query (or several queries); it does not. It contains a reference to a query. The workbook can be saved on the server; or anywhere else that you might save an Excel workbook.

What happens if someone changes the query definition on the server?

Answer: the next time you refresh the query in the Excel workbook, the new query definition replaces the old query definition in the workbook. Maybe. It depends on what change was made.

For example, if someone added a Condition to the query definition, the workbook will be virtually invisible to this. The Condition is available; but, is not implemented in the workbook. (Until the user of the workbook manually adds the view of the Condition and then activates it.)

For example, if someone changed the definition of a KF in the query definition, the revised KF will show up in place of the old KF in the workbook.

But ... if, for example, someone deleted the old KF and added a new KF, we get a different story. Now the old KF no longer appears (it does not exist); but, the new KF does not appear (it was not marked to be visible in the workbook).

About workbooks as views ... OK, a workbook may very well have a certain "view" of the query (drilldown, filters, et cetera). And, if the workbook is saved to the server in a Role where everyone can access it, this is good. But, if the workbook is saved to one's favorites, then this "view" is only accessible to that individual. Which may be good. Or may not.

A "saved view", on the other hand is stored on the server. So, it is available to all.

If you navigate in a workbook you can back up. You can back up, though, only as far as you navigated in the current session. You cannot back up to where you were in the middle of last week's session. Unless you saved that navigation state as a "saved view". Then, you can jump to that view at any time.

The downside of saved views is that they are easy for anyone to set up and difficult for most to delete.

Customer Exit Variable In Bex

The customer exit works at:

1. Extraction side

After enhancing datasource in RSA6 we need to populate those enhanced fields in that case we have to create a project in cmod transaction and select the Enhancement assignment RSAP0001 and select the appropriate FM and need to write the select statement in the appropriate include. EXIT_SAPLRSAP_001 - Transaction data EXIT_SAPLRSAP_002 - Master data EXIT_SAPLRSAP_003 - Text EXIT_SAPLRSAP_004 - Hierarchy The above things we need to do in Source System side Ex: R/3

2. Reporting side

We need to write the user-exit to populate Reporting related variables in the Enhancement assignment RSR00001 and select the FM EXIT_SAPLRRS0_001 and then in the include ZXRSRU01 we need to write the code. These are helpful especially we need to derive any varible.

Along with that:

BEx User Exit allows the creation and population of variables and calculations for key figures and variables on a runtime basis.

R/3 User Exit is found in R/3 under CMOD and contains additional programming that is needed to fill field additions to extract