BexGetData - Limitation or bug/problem ?

Question

Hello,
We are currently running BI 7 NW04s on Service Pack 9  (but with many notes applied to fix known issues).
I am attempting to determine the level of flexibility available with the BExGetData and "convert to fomula" functionality in the Bex Analyzer (Excel).
Am I correct in thinking that once you have "converted" your table to formulas you can only use the characteristic values that were displayed in the drill down prior to converting?
For example, I have a report listing <u><b>Amount</b></u> by <u><b>Cost Centre</b></u> and <u><b>Cost element</b></u>.
On running the query I have the Cost Centre and Cost Element values filtered to a single value for each - giving me one row of data.
I then convert the values to formulas and attempt the replace the Cost Centre and Cost element characteristic values with other values where I know there are posted amounts in the cube. The formula always displays #NV , even though I know amounts exist.
A number is only returned when I key in the original values I had in the drill down prior to converting. This behaviour seems at odds with the description of BexGetData and convert to formula in the Netweaver help.
Can somebody please tell me if I am totally misunderstanding the extent of this new functionality.
Thanks in advance,
JCM

Answer 1

Hello JCM2007,
I understand your problem and your question.
In my project the reporting-target is excel-analyzer and not the web.
We have several cubes concering to SAP-controlling.
Profit-Center-Accounting (and cc too) needs the following fields and values:
Proft-Center
Account
Year/Period
Version
Plan/Act-mark
Amount
The idea was, writing an Query to reduce the numer of fields and values, and
use it as a Dataprovider instead of the Cube (see SDN-show). (without variables)
My first step was:
Rows: 0accounts (with one presentationhierarchy) expanded to all nodes and values
cols: 0amount, Year, Period, Version, Plan/act/Mark
Normaly I would like to have the profit-center in rows, but there is a limit
in Excel (65k).  So i put the Profit-Center into  the filter.
In this example I got a simple result, navigation works fine, when converted in
formulars
But I want more flexibilty. I don't want use the filter-dialog and I don't want
use variables.
Using profit-center and 0account in rows can only work, if I use
hierarchynodes and expand only (f.e.) to level 3. (see limitation of Excel < 2007)
After the first result, I convert to formular. And then I have the effect:
I only can swap values (Profit-Center or accounts) wich have allways been
listed (or included) in the first queryresult. For example, I swap the nodevalue
of a field of level 4. Here I got the #NV, because the hierarchy was expanded to
level 3. But there are values concerning to the entered value.
Whats the reason (maybe I was wrong)
You are right, the flexibility has a limit. Only values of the basic-query (bevore converting to formular) are availible when your entering new values.
But what can I do? I my opinion there is a bug in this function.
My interim solution works as follow:
- You have your converted-to-formular Excel-result concerning to Dataprovider DP1.
- You got #NV when entering an new Object (cost-center/profit-center)
- Place a new design-item under your excel-layout (designmode)
- Use the same dataprovider DP1.
- exit the designmode.
- You have the same result before converting to formular.
- Now click right mouse button to querypropertys.
- You see cols, rows and filter fields.
- Change the selection of cols, rows or filter fields. (but do not delete the
selection-criteria) of the first excelresult (otherwise #NV is in the first result).
- Choose only those selections you realy need.
- go back to your queryresult.
- Now you have a bigger resultarea.
- So you can DELETE the designitem now, because You didn't need it.
- Now try the first resultarea.
Swap values, and it will work fine.
Be carefull:
If your query-resultarea is to large, you will become problems in excel.
The OLAP-resultarea (requested in the dataproviderquery) will be transported
to the local excel-cache. Your pc-cpu need 100% for a few minutes (50% dualcore)
and memory grows to 500 megabyte (in my example). In this environment, excel aborts and you have problems with the users.
Look for aggregates and combine nodes of object and accounts. (I have 40 aggregates because there are more then 2000 profit-center and costcenters)
The first result is much smaller when you use aggregates. But you must insert the designitem when you want enlarge your queryresult.
Regards
Roland