Using Boolen Operations in Query Designer

Hi All,
Below are the new formula which i have created in query designer
1.Number of years of service
2.Gratuity if years of service is greater than 20.
3.Gratuity if years of service is lessthan 20.
Now in report output i need to display Gratuity if years of service is greater than 20, or Gratuity if years of service is lessthan 20 based on Number of years of service.
In boolen function i have done as below
Number of years of service>=20==Gratuity if years of service is greater than 20
But in report output iam getting zero(0).
Is there any other way pls let me know
Regards
Albaik

HI Pravinder,
Number of years of service>=20=Gratuity
so how do we display this.
what does * indicate and where do we find this
(Number of years of service>=20) * Gratuity
Please let me know in detail
where do we find IF<Logic Expression IS IT IN BOOLEN OPERATION or MATHEMATICAL FUNCTION
In BEx you can follow this while writing a formula:
Follow this
IF<Logic Expression> THEN <Expression1> ELSE <Expression2>
this expression can be made using a formula in the form
<Logic Expression> * <Expression1> + NOT <Logic Expression> * <Expression2>
Please helpme
Regards
Albaik

Similar Messages

MDX - Filter members using AND operator in Query designer or otherwise

Hi,
I have the following table:
ID
Column A
1
ValA
1
ValA
1
Special
2
ValA
3
ValA
I need to return only IDs which has a Special value in Column A. So the output would be:
ID
Column A
1
ValA
1
ValA
1
Special
I thought that one way would be to use the MDX operator but there is very little documentation on it. I am a real beginner of MDX.
Thanks in Advance.

Hi RiddlerInPlay,
After testing the issue in my environment, we can add a group grouped on ID, then use an expression to control the row visibility to achieve your requirement. For more details, please see:
In the Row Groups pane, right-click the Details1 group to add a group grouped by ID field.
Delete the first column with “Delete columns only” option.
Right-click the details row to open the Row Visibility dialog box.
Use the expression below in the “Show or hide based on an expression” text box:
=iif(Fields!Column_A.Value="Special",false,true)
The following screenshot is for your reference:
If there are any other questions, please feel free to ask.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

What is the use of Condition is Query Designer ??

What is the use of Condition in Query Designer ??
How to use condition in Query Designer ??

Hi,
Conditions in a query can be defined for both characteristic combinations and key figures.
Characteristic combinations can be used using the ranking list functionality (e.g Top N or Last N customers with highest sales).
Key figures can be assigned the value limit conditions ( for e.g. display only rows in the query for which the key figure > 10 ).
For your specific requirements in which you need to display only a limited set based on the key figures, then you can go for conditions.
The conditions can be allowed to work on all the drill down characteristics independently, single characteristics or combination as well based on your requirement.
While execution the report, you can activate or deactivate the condition anytime by right clicking on the data cells.
Regards,
VA

Still using BW 3.5 query designer for BI 7.0 backend

Has anyone worked on an upgrade where only the backend has been upgraded to 7.0 but still using query designer 3.5?
Have there been any query performance issues?
Would you recommend upgrading the query designer to 7.0 soon?

We upgraded to 7.0 a long time ago and there are still some reports running as 3.x queries. It's no problem but there are so many benefits to working with the 7.0 query designer that I don't see the point in not upgrading.
Kind regards,
Alex

Using float amount in query designer

Hello,
I have an amount key figure of type fltp (float) with unit currency.
When I look at the data in cube or multiprovider the key figure has float precision.
When using the key figure in the query designer the value is rounded for two decimals.
This is independent of the display settings in bex or bex default settings in the infoobject (for example: when setting the value to 5 decimals, the kf will look like y.xx000 - rounded and filled with 0 - in the query).
Same problem when using the key figure in a formula.
Any ideas?
Regards,
Christoph

Hi Abhijeet,
the value is being calculated by a formula in transfer rules (like 5.50 u20AC / 30) and therefore has more than 2 decimals.
As I said using listcube will show the result I need.
When used in querydesigner the value is rounded to 2 decimals.
Christoph

Broadcasting to Enterprise Portal using Bex Broadcaster from Query Designer

I have already been able to broadcast from Query Designer using BEx Broadcaster to the portal based on a role or a user.
I select "Export into Enterprise Portal" as the Distribution Type.
I then select "Export Document to Personal Portfolio" and then enter a role.
Then I check "User-specific" because I want it to be user specific.
This all works fine.
Now I get to my question.
Can I go one step further and broadcast to a folder call... lets say "Sales" inside of their Personal Portfolio?

Hi Eric,
I have the same problem. Were you able to resolve it?

Using IN Operator in Query Parameter querying an Oracle dataset

I have created a main data set querying from Oracle in which I have two query parameters that are multi-valued lists. I created a data set for each of those multi-valued lists. These two parameters are configured to be multi-valued and selected
from the query. On the main data set, the parameters are set to an expression: = Join(Parameter.Field.Value, ","). If I sent just one value as a default in each of those parameters, works great. If I select "Select All"
in my drop down and rerun the report then I get "Query execution failed for dataset" and "rsErrorExecutingCommand". I am using Report Builder 3.0. I have seen some older posts saying you have to use a stored procedure to generate
a string from the selects to be passed to the parameter? I don't get this. Obviously I want to stick with using a query parameter for the performance gain. Is there an easy way to make this work?
Grateful for any help! Laurie

Laurie, you are right that the execution time is too long. Your instinct is correct to put the burden on the database to return the correct resultset, rather than filtering it in the report.
I think I wasn't clear about my explanation and you may have made this more complicated than it needs to be. The functionality that you want is already in ReportBuilder. Please check out this example from MS:
http://technet.microsoft.com/en-us/library/aa337396(v=sql.105).aspx
This is the correct syntax:
AND soh.SalesPersonID IN (@BusinessPersonID)
Is this how you have your query configured? If not, could you supply an example.
Hope that helps,
Mark

Using variables in the Query Designer

Hi,
I have 2 variables 'Z_COMP_CODE' and 'Z_BUS_AREA'. The type of 'Z_COMP_CODE' is single value ,customer exit and ready for input . The type of 'Z_BUS_AREA' is selection option,customer exit and not ready for input. I want the 2 variables to work like this: when 'Z_COMP_CODE' has the value '3000', 'Z_BUS_AREA' should have all the values excluding '2106'. Now in CMOD I have written the following codes for 'Z_BUS_AREA', But it does not work. 'Z_BUS_AREA' get no value while the query is running.Can somebody tell me how to correct it?thx.
WHEN 'Z_BUS_AREA'.
IF i_step = 2.
         READ TABLE i_t_var_range INTO l_s_range_v
            WITH KEY vnam = 'Z_COMP_CODE'.
         IF sy-subrc EQ 0.
           IF l_s_range_v-low = '3000'.
             l_s_range-low = '2106'.
             l_s_range-sign = 'E'.
             l_s_range-opt = 'EQ'.
             INSERT l_s_range INTO TABLE e_t_range.
           ENDIF.
         ENDIF.
       ENDIF.

It should be Customer Exit only.
Your code looks like ok to me. Have you tried to debug it? is l_s_range taking values?
Also i don't know much abt insert statement...may be same as append...but just try with append statement also.
Message was edited by:
        KJ (Kamaljeet)

Name of column using text variable in Query Designer

Hello!
I have 3 columns with amounts, 1 characteristic value variable and 1 text variable.
For example, names of this columns - 2005 year, 2006 year, 2005/2006.
I fill names using only one text variable and I can call first 2 column. I use set offset of variables for second column.
How can I call third column ''2005/2006"?

Hi,
u need a second Text varaible and u need to correct your existing text variable.
Prerequisite: u need for your key figures the same KF-variable
1. Edit your existing text variable lets say its called &Text1&
2. Select your Text variable and go to tab "replacement path"
3. Choose a) InfoObject b) Choose key
4. In section "use value range" choose from value
5. Create a new text variable lets call it &Text2&
6. make exact the same settings as for your first text variable butchoose for "value range" to value
Now u use this text variables for your KF:
KF 1 -> &Text1&
KF 2 -> &Text1&
KF 3 -> &Text1& / &Text2&
This should make it!!
Regards
Tobias

How to pass variable into lov sql query using like operator

hi.
i want to use a lov where i want to pass a variable using like operator.
my query is
select empno,name from table where empno like ':ed%';
my empno is A001 TO A199 AND B001 TO B199 so i want show either A% or B% empno
how can i do this ?
reagrds

kindly press Shift+F1 at a time you face this error to see the exact Oracle error message.
and provide us with that detail
and its better if you start new topic for that error... because that will be new error,,,
-- Aamir Arif
Edited by: Aamiz on Apr 7, 2010 12:27 PM

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

Blank space in Query Designer formula

Hello
I am using a formula in query designer to make some calculation but, once executed, this formula shows a blank space.
What does a blank space means?? The formula is not giving me an error.
Thank you,
Skull

Hi,
I think the blank appears in the report because it is encountering a Divide by Zero error.
First check what calculations your doing in the formula. If your doing a division and if there are chances that the Denominator is 0 and numerator has some value, then based on the setting in the spro, you might get a blank.
Try and put the function in BEx that handles divide by zero errors. The function is NDIV0
If that is not the case then please paste the formula that you have written.
Regards,
Forum

Use of structures in queries designer

hi experts,
using structures in Bex query designer increase the performance of query??

Nope, using structure has nothing to do with increasing the performance of query execution time. Actually if you use two structures and use those structures to create cell, that would have adverse effect on performance.
thanks.
Wond

Control display level for "display as hierarchy" in BI 7 Query Designer ?

Hi
I'm using BI 7.0 query designer and I can see there's an additional difference between BI 3.5 and BI 7.0 in rows/columns behavior, in the "display as hierarchy" functionality.
In BW 3.5 one could specify till what level the expand needed to be by default. So it could be 0 for totally collapsed. This is seems not possible anymore in BI 7.0 query designs anymore. Only on natural/technical hierarchies (cost center etc ...) this option is still there.
Is there a way (javascript or other) to have the hierarchies created by "display as hierarchy" also fully collapsed by default ?
Thanks.
Geert

HI, thanks for the reply.
But this is not about the standard InfoObject 'hierarchy" tab, with all it's options on default expand levels etc.
This is about a "pseudo structure" hierarchy which is defined at designtime (in Query Designer) and generated/shown at runtime (so bad for performance, I know). It's based on the real transaction data, not on a pre-created hierarchy as in normal hierarchies. It creates a tree view of otherwise unrelated InfoObjects, displays it in an collapsible/expandable tree shape.
it's a bit hidden in version 7 Query Designer, compared to version 3.5. In 3.5 one had a larger set of options, including the -now lacking- default expand-to level. But in Version 7, most options are dropped. Probably due to the move from the ABAP to the java backend, lots of other stuff got culled in that move as well.
For more info, look at the posts from Larry in this thread : [Display as Hierarchy|Display as Hierarchy]
I know it's an option not used a lot but can be handy in certain cases.
I really would like some help in getting a default query result with the "display as Hierarchy" collapsed.
Thanks,
Geert

Using Boolen Operations in Query Designer

Similar Messages

Maybe you are looking for