Aggregation level & Reference characteristics

hi
Could reference char be incorporated as part of the aggregation level?
thanks

Sure. But you cant post or repost or copy or distribute to that char.
Ravi Thothadri

Similar Messages

More than one reference characteristics Exception Aggregation

Hi All,
Is it possible to use more than one reference characteristics in reports for Exception Aggregation?
Thanks In Advance

Hi PPMM,
Did you resolve this issue?
Thanks,
Pam

Aggregation level

Dear Experts
I have 2 restricted key figures both set with aggregation level Total with reference to a characteristic. both are with reference to different characteristics. KF 1 is a formula containing KF 2 .
So, the referred characteristics are Char 1 for KF 1 and Char 2 for KF 2.
In the rows, if I drill down further by chars other than char 1 and char 2, how will the KF 1 and KF 2 values be affected?
Am i right to say drill down will not affect the aggregation behavior?
What determines which chars to be referred to when setting aggregation level in the KF?
Thanks in advance.
regards
Pascal

Hi Pascal,
Can i ask you to paste your report requirement so that we can visualize in a better way and guide you on the same.
Regards,
AL

How data update when there is two planning cubes in one aggregation level

If we have two planning cubes and a multi-cube includes these two planning cubes.
then we have the aggregation level defined based on this multi-cube.
if the characteristics and key figures defined in aggregation level all are included in these two planning cubes. When we plan the data with plan query based on this aggregation level, which plan cube will be updated with plan data, or both of them?

HI Wang,
yes as Bindu said you need to restrict the layout based on the infoprovider.
Lets assume that we have a multi provider M1 and it has two planning cubes cube1 and cube1.
in case u develop a layout for updating cube 1 give the restriction in the filter section as infoprovider = cube1.
or the vice versa.
Else ur layout must input values for both the cubes simultaneously, then in that case create two restricted KF with each having a restriction for cube1 and cube 2.
so wen the user enters value for the first restricted KF it will get saved in cube1 and wen he enters value for the second restricted KF it will gets saved in cube2.
This is how it works. Guess this was useful to u.
Regards.
Shafi.

Aggregation level on single level basis or multiprovider

Hello,
we use IP 7.0 and have a planning cube for CO-PA data, as well as a multiprovider combining the actual cube and the planning cube for COPA data. We need to implement a planning tool in which planning simple planning functions are needed on the single basis (copy, revaluation, multiply,manual planning ...) as well as on the multi-provider (top-down with reference data).
-> on which level(s) should we define the aggregation level? Do we need to define it on the multiprovider (in order to do the top-down) or can we split it up (single level and multi-provider) and define a workbook with a manual planning function on the single level AND including the top-down based on the multiprovider?
thanks
Dries

I agree with Gregor,
I think it is more logical to configure your Aggregation Level on top of your Multi-Provider, especially since you already have a need to view ref data from Actuals to perform calculations on your Planned. You can always restrict your 'simple' functions to the appropriate InfoProvider.
As for the FOx question, you can always restrict to each InfoProvider when writing your FOx (either inside the FOx code or using the FOx conditions).
Regards,
Zane

Aggregation level query "value help" = Only Values in InfoProv doesn't work

Hi,
I have a problem with Selection Variable for a BEx Query :
- I'm working with SAP BI 7.0 support package 15
- My query is an input ready query built for an "aggregation level" based on "real time infocube" (Planning);
- Characteristic, I want to filter with variable, has query property Advanced->Query Execution for Filter Value Selection = Only Values in InfoProvider
- Characteristic (info-object) has set the property: Business Explorer tab--> Query Def. Filter Value Selection as Only Values in the info-provider...
My problem is:
when I execute a query,
the Select Values for Variables screen appears
I push on the Select from List button
and Select Values For MyCharacteristic appears...
but it shows me all values in master data table of my characteristic instead of only values in the infoprovider!!!
If I build a query for the Real Time Cube it works correctly, but if the query is built for the aggregation level it doesn't work!
Could someone explain me why it doesn't work correctly?
Thanks in advanced
Fede

Thanks to Mariana Lazar
30.03.2009 - 12:30:36 CET - Risposta by SAP
Dear Fede,
Regarding the query built on aggregation level please note the following
the aggregation level is always a Virtual Provider built other
InfoProvider and hence it does not have the dimension table and hence
the F4 mode D is not supported.
Therefore when aggregation level is used in a query, F4 does not supportD-mode: 'Only Values in InfoProvider' and all master data values are
displayed in the value list.
Reference from the note
984229 F4 modes for input help as of SAP NetWeaver 2004s BI
4. Since other InfoProviders do not have a dimension table, the system
displays only posted values if you select "Only Posted Values for
Navigation". Otherwise, it displays the values from the master data
table.
Hope this should clarify your doubts. Please let me know if you have
questions else please confirm the message at your earliest convenience.
Thank you for your cooperation and kind regards,
@KR@ Mariana Lazar
Senior Support Consultant
SAP Active Global Support
Netweaver Business Warehouse

Aggregation level in only bps ?

hi friends,
can we need aggregation level in reporting for only bps module or for normal cubes also. so what is the if we use for normal cube alos.,
Tu
suneel.

Lets say you have fiscal period, fiscla year, GL account, amount, qty, product in the cube. But you wish to plan for GL account, fiscal period, fiscal year. Then you create an aggregation level for this and plan on GL account.
Similarly, you wish to plan for product, fiscal period, fiscal year and amout, then you create another aggregation level and plan for product.
Under this level, you further have filters, in which you restrict the values for the characteristics that you wish to plan.
Ravi Thothadri

Cross-Aggregation-Level Selection Evaluation indicator

Hi,
Can any one explain me the meaning of the below statements in the two paragraphs. This is for "Cross-Aggregation-Level Selection Evaluation indicator" in alert monitor.
If the Cross-Aggregation-Level Selection Evaluation indicator has not been set in the SDP alert profile, only planning objects that exactly correspond to the aggregation level defined in the selection are taken into account. This means that the planning objects contain exactly the characteristics of the aggregation level. Planning objects that have additional characteristics are not taken into account.
If however, the Cross-Aggregation-Level Selection Evaluation indicator is not set in the SDP alert profile, the system takes into account not only planning objects that exactly correspond to the aggregation level of the selection but also those containing additional characteristics.
Example
If you use a selection with the aggregation level 'Product' in the SDP alert profile and set the Cross-Aggregation-Level Selection Evaluation indicator, alerts will be issued not only for this product but for the relevant location products.
Thank you.

Hi Datta,
Let me go further with my data model first.
Selection criteria:
Sales organisation = CZ01
Sales statut = active
Standard / promo = standard
Product size = A, B, C, D, E
Aggregation level:
Sales organisation
Distribution chanel
Division
Product size
What I understand of the 546079 OSS notes:
Distribution chanel and division are to be out of the aggregation level. Moreover in my case, there is only one value possible.
What I understand of the 374681 OSS notes:
The system searches for all the characteristics of the sales organisation * product size (of the aggregation level) that match the selection. At that step, APO should select only active and standard skus for CZ01 sales organisation and A, B, C, D, E product size. Afterwards the system searches for all the characteristics combinations that fit the chosen aggregation level and aggregates its values.
My question is: does APO disaggregate on the ID selection?
The characteristic combination I see in the job log are those defined on the aggregated level taking into account the sales organisation and product size restriction defined in the selection ID.
Thank you for your return.

Forecast, selection and aggregation level

Hi gourous,
I'm working on APO 4.1.
Forecast runs in background as following:
- Aggregation level: Sales organization / distribution channel / division / product size.
All these four characteristics are part of the characteristic combination.
- Selection ID is defined on: sales organisation / sales statut / standard - promo indicator / product size
Sales statut and standard - promo indicator are attributes of the characteristic material (sales view).
However there is forecasts on promo SKUs even if they aren't in the selection ID (standard - promo indicator as value egal to standard in the selection ID)
My question is: how is it possible? is there a conflict between the selection ID and the aggregation level?
I check the assignment of forecast profiles and there is no profil assigned on the ID selection.
Thank you for your return.
Sophie

Hi Datta,
Let me go further with my data model first.
Selection criteria:
Sales organisation = CZ01
Sales statut = active
Standard / promo = standard
Product size = A, B, C, D, E
Aggregation level:
Sales organisation
Distribution chanel
Division
Product size
What I understand of the 546079 OSS notes:
Distribution chanel and division are to be out of the aggregation level. Moreover in my case, there is only one value possible.
What I understand of the 374681 OSS notes:
The system searches for all the characteristics of the sales organisation * product size (of the aggregation level) that match the selection. At that step, APO should select only active and standard skus for CZ01 sales organisation and A, B, C, D, E product size. Afterwards the system searches for all the characteristics combinations that fit the chosen aggregation level and aggregates its values.
My question is: does APO disaggregate on the ID selection?
The characteristic combination I see in the job log are those defined on the aggregated level taking into account the sales organisation and product size restriction defined in the selection ID.
Thank you for your return.

Running Macros on 9AMALORE aggregation level

Hi,
I'm trying to run simple macro in SNP (5.0)
I use DP Activities and Background jobs for this.
When I create a Background job, with selection "Select All" from Aggregation level I can choose what I want - "9AMALORE".
When I create a selection in the shuffler ( I have to restrict the selection to one plant only) and use it as Background job selection, I cannot manage to run the macro on 9AMALORE level.
In this case only one selection is available based on the shuffler selection grouping criteria, and unfortunately I can do it only by 9ARE (Resource only) or 9AMALO (Material Location).
Do you know what trick I can use to achieve this?
Regards!

Hi,
I am trying to understand your requirement. Not sure if I have understood this correctly,
When I create a Background job, with selection "Select All" from Aggregation level I can choose what I want - "9AMALORE".
Question - You mean in the /sapapo/mc8d txn you are able to select 9AMALORE as your agg level? What is ur selection id in this case?
When I create a selection in the shuffler ( I have to restrict the selection to one plant only) and use it as Background job selection, I cannot manage to run the macro on 9AMALORE level.
In this case only one selection is available based on the shuffler selection grouping criteria, and unfortunately I can do it only by 9ARE (Resource only) or 9AMALO (Material Location).
Question - Again in the interactive planning, you use shuffler to create a selection id. So here, What is your "Selection characteristics" and what is your "Show Characteristics" (the one at the top). Are you using this selection id in the background job and not able to aggregate by 9AMALORE or are you trying to running the macro in interactive.
Either ways, we shud be able to achieve what you are looking for.
Sorry I am a little confused with your requirement, but I am confident that I can help you, if you can clarify what you are looking for.
Thanks
Mani

Aggregation for reference characteristic

can i use aggregation (in infocube) for a reference characteristic?
Regards

Hi...
The regular standard aggregation process consists of totaling or
determining the MIN/MAX values; however, more complex
aggregation processes may be required. The exception aggregation
is an example of such a process. This aggregation process
comprises different types of aggregation such as SUM, MAX, MIN,
AVG, COUNT, FIRST, LAST, VARIANCE. Typical examples of exception
aggregation include the calculation of the number of deliveries
per month and the average revenue per customer.
These types of key figures require the specification of an
InfoObject as a reference value. The InfoObjects can be both
time-related and non-time-related characteristics.
The following illustrates the calculation of an exception
aggregation based on a sample average value calculation for the
number of purchase orders per day:
STANDARD AGGREGATION SUM (Database)
CALENDAR DAY CUSTOMER MATERIAL ORDERS
01/17/05 0815 AAA 14 u03A3 30
01/17/05 0815 BBB 16
01/17/05 0816 AAA 50
01/18/05 0815 CCC 22
01/18/05 0816 DDD 18 u03A3 36
01/18/05 0816 AAA 18
BECOMES -->
CALENDAR DAY CUSTOMER ORDERS
01/17/05 0815 30 Ø 40
01/17/05 0816 50
01/18/05 0815 22 Ø 29
01/18/05 0816 36
The calculation of the Orders key figure is based on the standard
aggregation process, Summation (SUM). This step is carried out
in the database. Moreover, the key figure also contains the
exception aggregation, Average (AVG). The calculation of the key
figure Average number of orders per day is handled by the OLAP
Processor.
Versusu2026EXCEPTION AGGREGATION AVG (OLAP) -->
CALENDAR DAY Ø ORDERS
01/17/05 40
01/18/05 29
When you use key figures with exception aggregation in the
InfoCube, the reference characteristics of the key figure are
automatically included in the aggregate. In the example shown
above, the aggregate must contain the time characteristic
0CALDAY because 0CALDAY represents the reference characteristic
for the exception aggregation.
The automatic inclusion of reference characteristics in exception
aggregation can affect the size and therefore the performance of
the aggregate. You can remove the reference characteristics via
the Expert mode (menu path: ExtrasSwitch Expert Mode On).
But, in that case, the OLAP processor can use the aggregate only
if the query does not contain the corresponding key figure.
Hope this helps you..
Regards,
Debjani..

Unable to create Aggregation level on Multiprovider

Hello Experts,
I am getting the following error when activating a newly created aggregation level on a certain Multiprovider.
Error : Aggregation level B2MP01L02: InfoProvider 0COMP_CODE cannot be used for definition.
0comp_code is a characteristic that I have included in a dimension of the Multiprovider. In the same dimension, i have another characteristic opcomp_code whose reference characteristic is also 0comp_code.
Could this be the source of the error? There are already many queries built on the Multiprovider, I am reluctant in deleting opcomp_code and check the impact while activating the Agg level.
Has anyone encountered this issue?
Any help will be greatly appreciated.
Thanks,
Nitish.

Hi Nitisch,
it seems that you get message RSPLS192, cf. long text of the message.
Not all multiproviders can be used as a basis for an aggregation level. The multiprovider has to contain at least one real-time InfoCube and not aggregation levels (aggregation levels cannot be nested).
Regards,
Gregor

Fields in Input Ready Query and Aggregation Level

Hi All - New to IP. What if we dont include all the fields of Aggregation level in Input Ready Query.
Supose there are 4 fields in Aggregation level and we are including only two in Input Ready Query.

Hi Harry,
For a Keyfigure to be input ready, all the characteristics of the Aggregation should be filled with some values at the time of input.
The characteristics should be either in Static Filter, Dynamic Filter, Row, Column. New Selection.
If a characteristic is not there in any of the above area then it is considered to be null and query will not be input ready.
Regards,
Gopi R

Error : Reading from Aggregation Level not permitted

Hello Gurus,
Could somebody please give some help or advice regarding this?
I have a multiprovider on a regular cube and an aggregation level, for some reason the multicube gives me the following error message when I try to display data using listcube.
Reading from Aggregation Level is not permitted
Message no. RSPLS801
Also the Query on the multicube does not display data for any of the KF's in the Agg Level but when I create a query on the Agg level itself it is fine.
Any suggestions?
Thanks.
Swaroop.
Edited by: Swaroop Chandra on Dec 10, 2009 7:29 PM

Hi,
transaction LISTCUBE does not support all InfoProviders, e.g. aggregation level are not supported. LISTCUBE is a 'low level' to read data from the BW persistence layer, e.g. InfoCubes. Since aggregation level always read transaction data via the so called planning buffer and the planning buffer technically is a special OLAP query LISTCUBE does not support aggregation level.
Regards,
Gregor

Query Designer not working with Aggregation Levels on BW 7.30

Hi,
Every time I try to create a query on top of an Aggregation Level that I created with the new ABAP based RSPLAN transaction.
If somebody can help me out I'd appreciate it.
By the way, we don't have the Java stack, but we are currently using BO4's JVM as we're on ramp up.
This is the error that I get when trying to create the query:
QD Revision 667
ERROR ID: E-ONGUIUNHANDLEDEXCEPTION
And this is the error log:
1:42:13 p.m..319: Info: Query Designer Start. Revision: 667
QDbCommandBase::Execute - Standard View
QDbCommandBase::Execute - Table View
QDbCommandBase::Execute - Rows/Columns
QDbCommandBase::Execute - Cells
QDbCommandBase::Execute - Conditions
QDbCommandBase::Execute - Exceptions
QDbCommandBase::Execute - InfoProvider
QDbCommandBase::Execute - Filter
QDbCommandBase::Execute - Documents
QDbCommandBase::Execute - Where-Used List
QDbCommandBase::Execute - Properties
QDbCommandBase::Execute - Properties
QDbCommandBase::Execute - Messages
QDbCommandManager::ItemClickedHandler - Bar clicked: NewQuery
QDbCommandBase::Execute - New...
QDbCommandBase::Execute - Table View
QDbCommandBase::Execute - Rows/Columns
QDbCommandBase::Execute - Cells
QDbCommandBase::Execute - Conditions
QDbCommandBase::Execute - Exceptions
QDbCommandBase::Execute - InfoProvider
QDbCommandBase::Execute - Filter
QDbCommandBase::Execute - Documents
QDbCommandBase::Execute - Where-Used List
QDbCommandBase::Execute - Messages
QDbCommandBase::Execute - Table View
QDbCommandBase::Execute - Cells
QDbCommandBase::Execute - Conditions
QDbCommandBase::Execute - Exceptions
QDbCommandBase::Execute - Rows/Columns
QDbCommandBase::Execute - Filter
QDbCommandBase::Execute - InfoProvider
QDbCommandBase::Execute - Properties
-EXCEPTION-START- 1:42:52 p.m..416: TRACE EXCEPTION ---
Exception Name: TargetInvocationException
Exception Message: Exception has been thrown by the target of an invocation.
Exception    at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.PropertyGet(Object iPropertySource, String iPropertyName)
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.ValueGetDefault(Object iPropertySource)
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.pValueDefault()
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.ValueDefault()
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.ValueResolved()
   at com.sap.bi.et.QueryDesigner.QDpPropertyMulti.SetFirstProperty(QDpPropertyBase iProperty)
   at com.sap.bi.et.QueryDesigner.QDpPropertyMulti.Add(QDpPropertyBase iProperty)
   at com.sap.bi.et.QueryDesigner.QDuPropPageQuery.ToDialog()
   at com.sap.bi.et.QueryDesigner.QDuPropPageBase.ToDialogCore()
   at com.sap.bi.et.QueryDesigner.QDuPropPageBase.set_CommandContext(QDbCommandContext Value)
   at com.sap.bi.et.QueryDesigner.QDuPropPages.EnablePage()
   at com.sap.bi.et.QueryDesigner.QDuPropPages.ContextChangedHandler(Object iSender, QDbCommandContext iCommandContext)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.ContextChangedEventHandler.Invoke(Object iSender, QDbCommandContext iCommandContext)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.OnContextChanged(QDbCommandContext iCommandContext)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CalculateContext(QDcView iViews, QDeAreaType iAreaType)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CalculateContext(QDbElement iElement)
   at com.sap.bi.et.QueryDesigner.QDbCommandPropertiesQuery.ExecuteCommand()
   at com.sap.bi.et.QueryDesigner.QDbCommandBase.Execute()
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CommandExecute(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.InitialCommandExecute(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.DoExecuteCommandInternal()
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.DoExecuteCommand(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.ItemClickedHandler(Object sender, BarItemClickedEventArgs args)
   at com.sap.bi.et.QueryDesigner.QDdEventDispatcher.MenuItemClickedHandler(Object iSender, BarItemClickedEventArgs iE)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarManager.OnItemClicked(BarItemClickedEventArgs args)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarItem.OnItemClicked(EventArgs args)
   at com.sap.bi.et.QueryDesigner.QDiBarItem.OnItemClicked(EventArgs args)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarItem.PerformClick()
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarRenderer.OnMouseUp(MouseEventArgs e)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarControlInternal.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarControlInternal.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Full Stack:   at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
   at com.sap.bi.et.common.appl.Log.Trace.Exception(Exception ex, String iAdditionalInformation)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.OnGuiUnhandledException(Object iSender, ThreadExceptionEventArgs iEventArgs)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDbQueryDesigner.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDStarter.QDStartup.Main()
-EXCEPTION-END----
-CALLING-FROM- 1:42:52 p.m..416: TRACE EXCEPTION ---
   at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
   at com.sap.bi.et.common.appl.Log.Trace.Exception(Exception ex, String iAdditionalInformation)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.OnGuiUnhandledException(Object iSender, ThreadExceptionEventArgs iEventArgs)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDbQueryDesigner.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDStarter.QDStartup.Main()

Hi,
it seems that you are already using the most recent query designer version. Is your SAPGUI also the most recent version? If yes, open a OSS ticket. If not reinstall the SAPGUI and the BEx tools. I am also working with this query desinger version and I don't have this kind of problem.
Regards,
Gregor

Aggregation level & Reference characteristics

Similar Messages

Maybe you are looking for