Query Designer with SAPNW7.01ABAPTrial

Hello
I am beginner on SAP BI and I want to know how to get or where to download query designer that can work with SAPNW7.01ABAPTrial. Thanks to reply sooner
Regards

Hi,
Pls go to Service Market Place. www.service.sap.com--> Downloads -> SAP support Packages -> My Companys application component -> BI Addons for SaP GUI -> BI 7.0 Addon for SAP GUI 710/BW 3.5 Addon for SAP GUI 7.10.
Regards
CSM Reddy

Similar Messages

Unable to access Query Designer with RRMX.

I have intalled Sap GUI 7.0. I am able to run all applications vai Link : START -> ALL PROGRAMES -> BUSINESS EXPLORER -> QUERY DESIGNER.
But when i try opening query designer from my logon pad with transaction RRMX, the query designer does not work.Kindly guide on the issue.

You can start the BEx Query Designer using one of the following options:
●      Standalone, by choosing Start ® Programs ® Business Explorer ® Query Designer.
●      BEx Web Application Designer:
In the menu bar of the Web Application Designer, you have chosen Extras ® BEx Query Designer.
●      BEx Analyzer:
You are in an empty cell and have chosen Extras ® Define New Query in the analysis toolbar.
●      BEx Report Designer:
In the menu bar of the Report Designer, you have chosen Extras ® BEx Query Designer.

Restricting infoobject in query designer with authorization object

Hi,
We have to restrict CUSTOMER infoobject with a authorization object in query designer.
How to do this task ? Request kindly suggest.

thr RSSECADMIN tcode. Search with this key word you will get good docs & Wikis in SDN
bhaskar

SELECT Query design with JOINS

Dear Users,
In one of our requirements, we have a SELECT query which joins a few tables together and selects a few fields from each table.
Example: Fields 1,2 and 3 from Table 1
Fields 4 and 5 from Table 2.
These fields are later displayed in the form of an ALV. However, the end user wants more fields on the output, let's say field 6 from Table 2. Due to this requirement, I have to amend the SELECT query to add field 6 of Table 2.
The above example is simple since it only involves 2 tables. However, in reality, we have a SELECT query with INNER JOINS on more than 6 tables and we don't want to change the code when someone asks for an additional field from one of these tables. Is there any way by which I can design my SELECT query (Using field symbols or dynamic selections etc) such that I don't have to amend the SELECT query and instead I should be able to maintain the field required by the user and it's source table name in a Z-Table and the SELECT automatically picks it up ? Thanks!
Vijay

better you can create a view on your 6 or more tables and select the fields .
Use Select * from <view name> every time in a select statement.
If you need a additional column then just change the view , there is no need to change of your select query.
with regards
Edited by: Avenai on Jun 28, 2010 2:09 PM

Corrupted Query Designer with strange External Restriction

Dear Experts,
I have a dilemma with query, when I run the query in RSRT and debug it with OLAP, in the restriction side it appears to restrict the query with two Attributes which are not even used in my query not also their master-data.
I have created the same query again but still it gave the same behavior.
Please help me to remove this dilemma.
Regards,
Mohammed

close all applications re-use RSRT
hope it works

Authorizations to restrict Query Designer with Only Display option

Hello,
I have looked all most all possible ways in internet to find out a suggestion/solution for the below. But Invain.
I would like to know the Transactions, authorization objects and profiles that are responsible to restrict users not to change and copy queries from QD.
I need only display option for queries.
Also,please confirm shall we restrict the same from Transaction SCC4.
Thanks In Advance.

Hi there,
Since you're talking about a QD system, you should lock it in transaction SCC4.
In case you need to change things in QD without opening the system in SCC4, you can go to transaction rsa1->transport connection and click on Object Changeability. In there you can define what paricular options are "opened for changes" even with SCC4 in close mode.
Also, for roles having that objects, you should use the authorization object S_RS_COMP and S_RS_COMP1 with Activity with value 02 - Display
Diogo.

Sap bi authorizations issue with query designer..

i am using bw 3.x and bi 7 query designer with different kind of probs?...
i am able to see the info provider in query desinger 3.x. but i can see only cubes .i am not able to find dso or infosets or multiprovider.. can anyone suggest is there any authorizations issues..please suggest.
and with BI 7 query designer i am not able to see info providers in info areas folder to design a query..
please suggest if any authorizations should be added or not

hi suman chakravar,
thanks for replying,
can u be little bit clear about the steps.
i went to tcode su01 and entered profile 0bi_all..it doesnt work.
and executed tcode su56.there i can find list of BI related authorization profiles
i added s_rs_all profile to my user. even then i face the same problem.
i can see only queries in query designer of bi 7 format and i can not view info providers.
i can view only cube and infosets and i can not view dso and multiproviders in bw 3.x type query designer
Edited by: satishchow on Dec 14, 2011 3:23 PM

All Dates displayed for "Characteristic Values" in Query Designer

Hello Experts,
We are on BI 7.0, level 13. I am having an issue within the Query Designer with regards to dates. I have a write-optimized DSO that contains 3 date fields (for example, ZDATE1, ZDATE2, and ZDATE3). Each date InfoObject is of type DATS so the system automatically creates it with reference to 0DATE.
When I create a query in the Query Designer, on the left hand side, I expand the "Characteristic Values" node under each date field. The Query Designer shows the same list of values for each of the 3 dates even though they are not valid values posted in the DSO for those fields.
For example, ZDATE1 only has 1 value posted in the DSO (01/01/2005).
ZDATE2 only has 1 value posted in the DSO (01/01/2006).
ZDATE3 only has 1 value posted in the DSO (01/01/2007).
Bute when I expand the "Characteristic Values" node in the Query Designer, I see ALL THREE values under each date field. I would expect to only see the 1 value posted for the InfoObject in the DSO. Also note that each InfoObject is defined to show "Only posted values in InfoProvider".
It appears that Query Designer will show all values for the reference InfoObject 0DATE instead of the ones posted to the actual InfoObject in the DSO. If I delete the data in the DSO, the Characteristic Values list still remains because they exist in 0DATE. Anyone encounter this before? How can I get the Characteristic Values list to only show posted values for that InfObject?
Thanks for your help!
J

Thanks for the response. I went into the DSO and right clicked on each of the Date fields. I looked at the Provider-specific properties and there is the option for "Query Exec.FilterVal" which only restricts what values appear when restricting during execution, not during query creation.
Is there someplace else I should look or someplace else I can make change to only display posted dates when creating a query? Thanks!

Bex Query designer withour Enterprise Portal?

Dear BW experts,
After launching the Bex Query designer with BI7 system. After designing query, If I click on execute (Ctrl+R). It is launching internet explorer with error "Invalid Syntax error - Page cannot be displayed"
It is launching the following URL
http:///irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.pct!2fplatform_add_ons!2fcom.sap.ip.bi!2fiViews!2fcom.sap.ip.bi.bex?QUERY=ZCCQ20071048070001&VARIABLE_SCREEN=X&DUMMY=1
I think it is looking for Enteprise Portal server. I dont have an EP server.
What is the alternate way to execute this?
Thanks in Advance...

Hello to all of you,
just to make sure that I do not missunderstand:
As far as I know in BW3.5 (without EP installed) you were able to execute a query directly out of the query designer and it was shown as a web-query.
Now I tried to do the same with a BI7-System the first time and I get the same symptom as Abdullah. We also do not have an EP installed on that system.
As solution, you all describe that I have to open the query in analyzer to see it in excel - OK - BUT if I do not want to see it in excel but as a webquery (like in my good old BW3.5) instead ? Isn't that possible anymore ???
Uwe

Formula Evaluation in Query Designer

Hi
In query designer I have Complex formula which is having lot of variables.
My users are saying some values are incorrect in report output
Can any one help how can we find the value is calculated in report output for this formula.
Thanks
Sudhakar.

Hi Sudhakar,
One more way which you can try to find out how the particular Key Figure is been calculated in query designer is as given below:
1) Go to RSRT
2) execute your query with option for Query Display As "List"
3) You will get the query output
4) In this screen, you will get the button "Key Figure Definition" on the top
5) Click on this button and there will be a pop up screen to select "Structure Element 1" and "Structure Element 2"
6) Here for "Structure Element 1" please select the KeyFigure name for which you want to see the calcuation
7) and click on the "Continue" (Here its blue colored icon)
8) After this you will get a screen showing KF value that is calculated by query
9) Drill down the key figure to see "Fixed Fliter" which will show the data selection used to calculate this value. These are nothing but the global filters defined in query
10) Drill down the KF to see the dynamic filter values i.e. selections with which this KF is restricted in query designer
With above analysis you can easily trace out how the particular KF is calculated in query designer.
Regards,
Geetanjali

Difference Beetween Query Designer and Adhoc Query Designer

Hello!
can any one explain me what exactly is Adhoc query designer and how is it different from Bex Query designer. can you please provide me links for Adhoc query designer (not to Bex query designer)
with regards
ashwin

Hi Ashwin,
See this link:
http://help.sap.com/saphelp_nw04/helpdata/en/1f/03223c5f00612be10000000a11402f/content.htm
Basically the Adhoc query designer is a web item that you can include in a web template to allow the user to create or change queries in the web environment. It has some limitations like you cannot use variables, and can only use one structure.
Hope this helps...

BW 3.5, BEx Query designer issue with text of the characteristics

Hi All,
We are currently using BEx 3.5 Query Designer to design the queries. We have one of the ODS on which we are querying for.
We have 3 different types of Customer in this ODS. 0Customer, 0BBP_CUSTOMER and 0GN_CUSTOMER. The problem is when we open this ODS in Query designer we see their text name on the left hand side column where it shows data fields as the same text name Customer.
Now the our Power users have raised the issue that it is very confusing even when there are 3 different technical names for these characteristics.
2 Questions I have.
1) Why is something like this happening? is it some issue with the Patch or something. We will be migrating to new BI soon but in the mean time if I could resolve it that will be the best. Or does it even get resolved with new BI???
2) what is the way in which we can resolve it?
Thanks in advance and points will be given generously.

HI BI Consul!
Things like this happen, when it is called customer it could be different customers, 0customer is the standard R/3 customer and 0BBP_customer is objects from CRM and most likely 0GN_Customer might be customer from different system.
Sure, power users should be told which customer is customer and you could also change the discription of the object, to match the definition on the other system. You could also just create z object and replace the existing confusing object with something meaningful to users.
thanks.
Wond

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

Combine two reports in query designer using key figure with sap exit

Hi experts,
i want to combine two reports in query designer using key figure with sap exit
in the report 1 key figure calculation based on the open on key date(0P_DATE_OPEN)
to calculate due and not due in two columns
in report 2 key figure calculate in the time zones using given in variable Grid Width (0DPM_BV0) like due in 1 to 30 days, 31 to 60 days...the due amount based on the open on key date(0P_DATE_OPEN)
to calculate in 1-30, 31-60, 61-90, 91-120, 121-150 and >150 days in 6 columns
now i have requirement like this
not due, 1-30, 31-60, >60, due,1-30, 31-60, >60 in 8 columns
or
not due, due, 1-30, 31-60, 61-90, 91-120, 121-150 and >150 in 8 col
thank you

Hi Dirk,
you perhaps know my requirement,
for the management to make used in one report,
we have in reporting finacials Ehp3.
Vendor Due Date Analysis - which show due, not due
Vendor Overdue Analysis - show only due and analysis in time grid frame
i want to combine in one report that show NOT DUE, DUE, DUE time frames in grid.
krish...

Problem with Variable in Query Designer.

hi all,
we have a variable ZAMREG on characteristic AM Region, where AM region is attribute for two different master data objects mastobj1 and mastobj2, we have different infosets build on these two master data objects along with some other ODS.
now this variable ZAMREG is visible in one of the infosets only in query designer, whereas it is not visible in the other infoset.
what could be the problem??
thanks,
Rk

Hi,
Please check if that variable is created locally or globally. If it is a local variable in any query, it will not appear in any other query.
In anyways, you can always create one more variable if the older one is not available. This will not make much of difference. I would suggest go ahead with creating a new variable.
Regards,
Yogesh

Query Designer with SAPNW7.01ABAPTrial

Similar Messages

Maybe you are looking for