Removing leading 0 in query designer

Hi guys,
I have a characteristic with values like '0000000123'. How can I remove the leading zeros in query designer?
Thanks.

u can do this in a routine.The code is as follows
data a(9) value '000012345'.
SHIFT a LEFT DELETING LEADING '0'.
write:/ a.
Output will be : 12345
Or use this method also
data a(9) value '000012345'.
Call function 'CONVERSION_EXIT_ALPHA_OUTPUT'
Exporting
input = a
Importing
output = a.
write a.
output:
12345.
assign points if helpful

Similar Messages

  • Removing Leading zeros from query output.

    Hello Experts,
    Is it possible to remove leading zeros from the query output for a particular column?
    I have a characteristics 'Reference Document' which has values like '000001386'. The users just need '1386' to be displayed and have asked us to remove the leading zeros.
    Is there something that can be done for this at a query level? I can't modify the underlying InfoProvider because this requirement is just for one set of users, the other users need the document nmber in the original format.
    Thanks
    Arvind

    Hi,
    you can use ALPHA conversion option in the definition of that particular characteristic.
    Try this code  in a routine.,in query designer;
    data a(9) value '000001386'.
    SHIFT a LEFT DELETING LEADING '0'.
    write:/ a.
    Output will be : 1386
    Or use this method also
    data a(9) value '000001386'.
    Call function 'CONVERSION_EXIT_ALPHA_OUTPUT'
    Exporting
    input = a
    Importing
    output = a.
    write a.
    output:
    1386
    Regards
    CSM Reddy

  • Remove leading zeros in query

    Hi Gurus,
    I have a alpha routine in update rule which will add leading zeros in omaterial,but now I want to display 0material in the report without leading zeros. How to do this ?
    Thanks
    Liza

    Easiest thing is remove the conversion routine in 0material, if you dont want leading zeros.
    Or
    In update rules, use truncate statement to remove leading zeros.
    Ravi Thothadri

  • Query designer removing parts of where clause in VS 2012

    I'm new to reporting services and I'm finding the query designer very frustrating.  First off,  I have read here and
    am having a problem where the tool automatically wipes out parameters I have changed/added in the query designer.  I read this 5 years ago, yet it seems that this problem still exists.  I've tried changing the XML as suggested by some with mixed
    results.  Now I am having a problem when I changed the WHERE clause it keeps disappearing if I try and make any other change.  Does anyone have advice on working with this tool?  Should one keep a running copy of the query and keep pasting it
    back in whenever a change is needed?  Is this behavior not expected?  Is anything different with SSRS 2014?
    Thanks

    Hi billywinter,
    According to your description, parameters are wiping out automatically when you change something in query designer.
    In Reporting Service, if we use where clause to add parameters in query designer, Define Query Parameters will pop-up when running the query. Please refer to screenshot below:
    Regarding the issue, we couldn’t understand it clearly, and we would like to confirm something from you below:
    1. Does parameters disappear in your query? Or when you preview the report, the selected box of parameters doesn’t display?
    2. How about the query in query designer when parameters disappear?
    3. What’s the modification have you performed for where clause? And what’s the result after this modification?
    4. What the query type you are using, MDX query, stored procedure or another query type?
    Please provide more information about the issue then we can understand the issue clearly. If possible, please provide some screenshots about the query in query designer, and the results of parameters before and after changing where clause.
    In addition, we have found a feedback which descripts an issue about overwriting parameter in MDX query designer, and this issue is resolved by design. Is this issue same as yours? Please refer to this feedback:
    MDX Query Designer Overwrites Parameter Queries.
    Best regards,
    Qiuyun Yu

  • Group by in BEx query designer

    Hello experts,
    I'm new in BEx query designer and I'm currently working on displaying the maximum of a list of values and group them by calendar day like the exemple below:
    CalendarDay
    Client
    Amount
    02.09.2014
    A
    3000
    02.09.2014
    B
    2000
    03.09.2014
    A
    1500
    03.09.2014
    B
    1600
    The result I need to display is as below:
    CalendarDay
    Amount
    02.09.2014
    3000
    02.09.2014
    2000
    OverAll result
    3000
    03.09.2014
    1500
    03.09.2014
    1600
    OverAll result
    1600
    What's the best solution for this ?! is it to work with calculated Key Figure or Exceptions ?! Would any one help me to get such result.
    Thanks a lot

    If you need to show the data as you mentioned then i think you are suppose to keep client in rows and also you have to switch on the result row display for that characteristic.
    Because if you remove it then data will get aggregated based on calday and it will become 2 records only.
    To get the maximum value you have to use Exception aggregation.Create a new formula and put the amount kf inside it.Hit the aggregation tab--Exception aggregation as maximum--Reference characteristic as client.
    If this does not work then we can also apply nested aggregation based on calday.
    Regards,
    AL

  • Problem loading Query Designer Add-in

    Hi All,
    Can anyone please help me on my below issue.
    Whenever user is trying to start a new query in Essbase , he is getting below error message. It will not allow user to build a fresh Essbase pull
    Problem loading Query Designer Add-in. Workbook Activate,open & close operations may not be fully propogated
    Thanks in advance.
    Regards
    Vishal

    Hi Vishal,
    1) Try to remove the addin and then add again.(Before doing this close all the excel process from the task Manager)
    2) Check weather essexcln.xll and essxleqd.xla are corrupted.

  • Error while executing query in query designer and RSRT.

    Hello All,
    At none of the places (BI--> RSRT  or via query designer GUI) my query is executing properly .
    At RSRT the error message ---
    At Bex Query designer the error msg--
    Checked the data at the sales-infocube level , the data is absolutely ok.
    Regards
    Deblina

    Hi,
    Have checked both the places, backend cube as well as the filter conditions of the query ,everything is in sync.
    to make the query more simple i have removed the charateristics restrictions then ran the query , but still getting the same error.
    Am just attaching the screenshot of the query layout, for your reference.
    Regarding connectivity to access the portal,  how it can be established.
    Many Thanks
    Regards
    Deblina.

  • Grouping Free Characteristics in Query Designer?

    Hello,
    I have a couple reports that per busniess have many free characteristics. So many that that they do not fit on one page and you must continue scrolling the page down to view all. This makes the report look sloppy but the business owner wants all of these free characteristics. I'm looking for a way to clean up the list of free characteristics without removing any selections. Can they be grouped up or consolidated through Query Designer or WAD?
    Thank You,
    Alex

    Hi Alex,
    Actually use of free characteristic will not slow down the report performance rather free characteristics are used to enable the user for dynamic drilldown and to improve the query performance for initial output display.
    What you can suggest your users is to keep only required free characteristics and then remove the rest of the characteristics and from grouping perspective all the free characteristics in query designer output are shown alphabetically so you can not manipulate the group in designer.
    Regards,
    Durgesh.

  • Query designer problem

    Dear All,
    I am facing the problem in the query designer that when i edit any of the formula in the query it allows me but when i edit it second time , it wont allow me and throws a following exception...
    "An unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will be shut down immediately.
    Object reference not set to an instance of an object."
    and in details of the exception the following comes...
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
                                        Exception Text
    System.NullReferenceException: Object reference not set to an instance of an object.
       at com.sap.bi.et.QueryDesigner.QDbPoolEditSelection.Get()
       at com.sap.bi.et.QueryDesigner.QDbCommandEditElement.EditFormula(IQDView iSelectedView)
       at com.sap.bi.et.QueryDesigner.QDbCommandEditElement.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.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 com.sap.bi.et.QueryDesigner.QDbCommandManager.ExecuteDoubleclickCommand(ParentBarItem iContextMenu)
       at com.sap.bi.et.QueryDesigner.QDbCommandManager.NodeDoubleClickHandler(Object sender, EventArgs e)
       at com.sap.bi.et.QueryDesigner.QDdEventDispatcher.ItemDoubleClickHandler(Object sender, EventArgs e)
       at com.sap.bi.et.QueryDesigner.QDdEventDispatcher.ItemDoubleClickHandler(Object sender, EventArgs e)
       at com.sap.bi.et.QueryDesigner.QDuHeaderTree.OnItemDoubleClick(EventArgs iE)
       at com.sap.bi.et.QueryDesigner.QDuHeaderTree.NodeDoubleClickHandler(Object sender, EventArgs e)
       at System.Windows.Forms.Control.OnDoubleClick(EventArgs e)
       at Syncfusion.Windows.Forms.Tools.TreeViewAdv.OnDoubleClick(EventArgs e)
       at com.sap.bi.et.QueryDesigner.QDiTree.OnDoubleClick(EventArgs 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.ScrollControl.WmMouseUp(Message& msg)
       at Syncfusion.Windows.Forms.ScrollControl.WndProc(Message& msg)
       at Syncfusion.Windows.Forms.Tools.TreeViewAdv.WndProc(Message& m)
       at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
                                                     Loaded Assemblies
    mscorlib
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
    BExQueryDesignerStarter
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.486
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExQueryDesignerStarter.exe
    System
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    BExQueryDesigner
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.486
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExQueryDesigner.DLL
    BExCommon
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.122
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExCommon.DLL
    BExControls
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.122
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExControls.DLL
    BExCAControls
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.122
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExCAControls.DLL
    System.Windows.Forms
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2032
        CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
    BExCommunication
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.122
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExCommunication.DLL
    Microsoft.VisualBasic
        Assembly Version: 7.0.5000.0
        Win32 Version: 7.10.6001.4
        CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
    System.Xml
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2032
        CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
    8mfr2iet
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    SAP.Connector
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.0.23
        CodeBase: file:///c:/windows/assembly/gac/sap.connector/2.0.0.0__50436dca5c7f7d23/sap.connector.dll
    Interop.SAPLogonCtrl
        Assembly Version: 1.1.0.0
        Win32 Version: 1.1.0.0
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/Interop.SAPLogonCtrl.DLL
    SAP.Connector.Rfc
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.0.23
        CodeBase: file:///c:/windows/assembly/gac/sap.connector.rfc/2.0.0.0__50436dca5c7f7d23/sap.connector.rfc.dll
    BExGeneratedAll
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.123
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExGeneratedAll.DLL
    System.Web.Services
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2032
        CodeBase: file:///c:/windows/assembly/gac/system.web.services/1.0.5000.0__b03f5f7f11d50a3a/system.web.services.dll
    System.Drawing
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2032
        CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
    System.Web
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
    nwibr-hj
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    orv3kyon
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    3wroaodz
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    uzyztof1
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    bmpxtf3w
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    BExControls2
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.123
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExControls2.DLL
    BExSharedImageList
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.122
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExSharedImageList.DLL
    System.Runtime.Serialization.Formatters.Soap
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2032
        CodeBase: file:///c:/windows/assembly/gac/system.runtime.serialization.formatters.soap/1.0.5000.0__b03f5f7f11d50a3a/system.runtime.serialization.formatters.soap.dll
    BExSelectorAPI
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.202
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExSelectorAPI.DLL
    System.Data
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2032
        CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
    BExOpenSaveServices
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.108
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExOpenSaveServices.DLL
    Syncfusion.Tools.Windows
        Assembly Version: 4.401.0.51
        Win32 Version: 4.401.0.51
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/Syncfusion.Tools.Windows.DLL
    Syncfusion.Shared.Base
        Assembly Version: 4.401.0.51
        Win32 Version: 4.401.0.51
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/Syncfusion.Shared.Base.DLL
    Syncfusion.Grid.Windows
        Assembly Version: 4.401.0.51
        Win32 Version: 4.401.0.51
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/Syncfusion.Grid.Windows.DLL
    Syncfusion.Core
        Assembly Version: 4.401.0.51
        Win32 Version: 4.401.0.51
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/Syncfusion.Core.DLL
    Syncfusion.Grid.Base
        Assembly Version: 4.401.0.51
        Win32 Version: 4.401.0.51
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/Syncfusion.Grid.Base.DLL
    Syncfusion.Shared.Windows
        Assembly Version: 4.401.0.51
        Win32 Version: 4.401.0.51
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/Syncfusion.Shared.Windows.DLL
    Accessibility
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.573
        CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
    AxInterop.SHDocVw
        Assembly Version: 1.1.0.0
        Win32 Version: 1.1.0.0
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/AxInterop.SHDocVw.DLL
    Interop.SHDocVw
        Assembly Version: 1.1.0.0
        Win32 Version: 1.1.0.0
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/Interop.SHDocVw.DLL
    Syncfusion.Edit.Windows
        Assembly Version: 4.401.0.51
        Win32 Version: 4.401.0.51
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/Syncfusion.Edit.Windows.DLL
    ezadp-o7
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    czxpebds
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    ws48wlef
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    nbphnkyi
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    qmxat26w
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    BExFormulaParser
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.122
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExFormulaParser.DLL
    RegexAssembly140_0
        Assembly Version: 0.0.0.0
        Win32 Version: n/a
        CodeBase:
    System.Design
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2032
        CodeBase: file:///c:/windows/assembly/gac/system.design/1.0.5000.0__b03f5f7f11d50a3a/system.design.dll
    BExQueryDesignerFormulaParser
        Assembly Version: 7000.0.0.0
        Win32 Version: 7005.5.1401.2
        CodeBase: file:///C:/Program%20Files/SAP/FrontEnd/Bw/BExQueryDesignerFormulaParser.DLL
    JIT Debugging **************
    To enable just in time (JIT) debugging, the config file for this
    application or machine (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the machine
    rather than being handled by this dialog.
    Please anybody help me.
    Nitesh

    Hi,
    This is a typical front end issue where you have to look at your GUI patch and front end patch.I recommend you deinstalling your frontend installation as follows:
    - Remove your frontend via 'START' - 'PROGRAMS' - 'SAP FRONTEND' -
       'REMOVE SAP FRONTEND'
    - Install the newest frontend and GUI patch and check the installation with sapbexc.xla
    Please run the front-end checktool SAPBEXC.XLA as per Note 918394 and ensure there are no errors.
    Path for frontend patches
    Please goto
    -> service.sap.com/patches
    ->entry by application group
    ->SAP Frontend Components
    ->SAP GUI FOR WINDOWS
    ->SAP GUI FOR WINDOWS 6.40
    ->SAP GUI FOR WINDOWS 6.40
    ->Win32
    ->Apply latest frontend patch
    Once the installation is done run the installation check file as per note 918394 and ensure that there are no red flags.
    Rgds
    Manoj Kumar

  • Hide a row or column for characteristic value # in Query Designer

    Hi gurus,
    I would if we could hide a result row / column if one of the characteristic value is #. The requirement is actually to remove the meaningless row / column from the whole result set. For example, I have a char Material Group in the column. Since not every Material is assigned to a Material Group, I will get the following layout:
    Material_Group A
    Material_Group B
    Material_Group C
    Is it possible to define in query designer so that the column with # will automatically not be displayed?
    Thanks,
    Meng

    Hi Meng,
    I guess we have the same users..
    But there is one thing that is going to make a non sense on the report: if you do not display the "#" for material group, then the total of your query by material group will not be the summation of what is displayed on the screen...and if the user explort the information in Excel (pretty sure they will do so), you will have some calls that your query does not balance....
    Based on that assumption, tell the users to assign a material group to the materials, so that this unassigned column disappears. You could even give them a control report listing all the parts that do not have a material group
    If this is a standard business rule not to have a material group for all parts, then, what you could do is to change the text for empty rows for Material group, then the "#" will disappear and wil be under the text description you defined.
    But keep in mind that your data is made of materials which do not have a material group in their definition, noraml or not ?
    PY

  • BEx query design: defining complex filters?

    Is it possible to define complex filters in a query definition? By complex I mean using logical operators (AND, OR, NOT)
    Example: report giving sales results
    I want to have
    (Customers from Germany <b> AND </b> product type A)
    <b> OR </b>
    (Customers from Romania <b> AND </b> product type B)
    If I define a standard filter:
    Customer country IN (DE,RO)
    Product type IN (A,B)
    I will obtain all combinations while I only want to have the couples {(DE,A),(RO,B)}.
    Thxs.
    LauQ

    Hide is just to remove the "object" from the display. It is used as an intermediate filter for the object that includes the logical combinations that one would like to get in the results.
    In my example:
    In the Query Designer:
    1. Define a structure (rows)
    2. right-click on it and make new selections corresponding with
    a) Country=Germany (:='DE')
    b) Country=Romania (:='RO')
    c) Material=A
    d) Material=B
    3. Right-click on each of them and "hide" them
    4. New formula in the structure:
    TEST:=(( 'DE' AND 'A' ) OR ( 'RO' AND 'B' ) )
    5. You need to edit the Cell definition and make use of the Help Cells (select therein the KF you need to display; e.g. "QUANTITY SOLD").
    6. "Play" with Cell definition and define a final KF such as:
    FINAL:='QUANTITY SOLD' * 'HELP'
    You need to try by yourself...
    Regards
    LauQ

  • Query designer error

    hi all,
    while i am trying to do changes in BEX Query designer, following error occurs and not allowing me do the changes(like drag and droppinf of char and key fig in rows and colums)
    errors
    1 Bex transport request is not suitable or available
    2 choose an existing request
    please suggest asap.
    thanx

    hello,
    Firstly log off from the query designer.
    From RSA1->Transport connection ->select ur query->transfer only necessary objects.
    Then on the right side panel when scrolling to the right u can see the request to which the query is assigned to.
    If u see any query objects in any other request which u do not want to be,remove the objects from that transport.
    Then come back to query designer,check the query for syntax errors,make the changes u wnat to do and save now to your transport request.
    Reg,
    Dhanya

  • Query not showing detailed result when run through query Designer or Portal

    Hi,
    There is one query which not showing detailed result while running through Query Designer or run in Portal.
    But strange thing is that it is showing the detailed result when i run it through BeX Analyzer.
    While all the other queries don't have this problem in system. All showing the correct detailed result.
    If anyone have some idea on this issue plz let me know.
    Regards,
    Javed
    Edited by: Javed Akhtar on Jul 7, 2009 3:59 PM

    Hi,
    We can do this setting in WAD. Please check the web template and try to remove that setting. When you have hierarchy then we can display only till certain level in portal, this setting is done in web template APIs, but in bex analyzer you can see all the detailed information.
    Edited
    Go through this thread for some more detailed information
    http://help.sap.com/saphelp_nw2004s/helpdata/en/44/7b5f0a95ce12d0e10000000a422035/frameset.htm
    Regards,
    rik

  • Cell definition choice in Query Designer is inactive

    In the Query Designer the choice "Define cells" is inactive, or grayed out. Why is this? Is there a global setting or does it have something to do with the query itself?

    Hi TMV,
    if you want to see the "cell " option in active mode , first u must have two structures.
    one is charactersitc structure and on key figure.
    Just go throw the below description.
    Hi,
    just go throw the below description:
    In the Query Designer, choose View ® Cells from the menu bar to reach the functions of the cell definition. The Cells screen area is displayed.
    New selection
    1. Select a cell in the Cell screen area and choose New Selection with the secondary mouse button. The new selection that is not yet defined appears in the cell.
    2. Select the new selection and choose Edit from the context menu. The Change Selection Cells dialog box appears. Make the basic settings on the General tab page.
    3. Use Drag&Drop to define your required selection by dragging a key figure and the characteristic values by which you want to restrict the key figure to the right-hand area of the Details of the Selection dialog box. See Defining Selections.
    You can use characteristic value variables instead of fixed characteristic values.
    - If you want to change an existing variable, select the variable and choose Edit from the context menu. The variables editor appears and you can change the settings.
    - If you want to define a new variable, select the characteristic value and choose New Variable from the context menu. The new variable is displayed. Choose Edit from the context menu of the new variable. The variables editor appears and you can define the settings.
    For more information, see Defining Variables.
    4. Enter a description for the selection.
    You can use text variables in the description.
    5. Make any necessary settings for the properties of the selection on the other tab pages. See Selection/Formula Properties.
    6. Choose OK. The cell contains the description of the selection. The symbol shows you that a selection exists for this exception cell.
    New formula
    1. Select a cell in the Cell Definition dialog box and, using the secondary mouse button, choose New Formula from the context menu. The new formula that is not yet defined appears in the cell.
    2. Select the new formula and choose Edit from the context menu. The Change Formula Cell dialog box appears. Make the basic settings on the General tab page.
    3. Define your formula using the operands and functions available. See Defining Formulas.
    4. Enter a description of the formula.
    You can use text variables in the description.
    5. Make any necessary settings for the properties of the formula in the other tab pages. See Selection/Formula Properties.
    6. Choose OK. The cell contains the description of the formula. The symbol shows you that a formula exists for this exception cell.
    New cell reference
    You can use any cell that you define in a formula. If you want to reuse the value from the implicit, generic cell definition that is automatically created at the intersection of the two structural components of a query, select this cell in the Cell screen area and, using the secondary mouse button, choose New Cell Reference. A description taken from the two structural components now automatically appears in the cell. The symbol shows you that a cell reference exists for this exception cell. Now you can reference this cell. You can continue to use the implicit cell definition and do not have to manually generate this value using a new selection.
    Functions of explicitly defined cells:
    Select a defined cell and choose the required function from the context menu (secondary mouse button).
    &#9679; Edit
    &#9679; Cut
    &#9679; Copy
    &#9679; Paste
    &#9679; Remove
    &#9679; Where-Used List
    Before you delete a cell, you can check for the formulas in which the defined cell is used in the where-used list.
    You reach the properties of a defined cell by selecting the defined cell. In the Properties screen area you can also make changes such as:
    &#9679; Changing the description of the cell
    &#9679; Changing the highlighting of the cell
    &#9679; Hiding the cell ( if you do not want to see the values of the cell)
    Help cells
    In the Help Cells area you can define additional cells for help selections or help formulas. You can use the functions New Selection and New Formula in the context menu to define help cells that are not displayed in the query to serve only as objects for help selections and help formulas.
    For example, you can define an invoice in a help cell and use this in a “real” cell to calculate a duplicated invoice.
    a. Using the secondary mouse button, click on the empty cell next to Help Cells to reach the context menu. From here, choose New Selection.
    b. Use Drag&Drop to drag the Invoice key figure into the right-hand Details of the Selection area.
    c. Enter a description.
    d. Choose OK. The cell contains the description of the selection. The symbol shows you that a selection exists for this exception cell.
    e. Now choose New Formula from the context menu of the required cell of the query. The new formula that is not yet defined appears in the cell.
    f. Select the new formula and choose Edit from the context menu.
    g. Use Drag&Drop to drag the cell you have just defined, which you can find in the Available Operands window under Cells, into the Detail View window. Click on the button twice.
    h. Enter a description.
    i. Choose OK. The cell contains the description of the formula. The symbol shows you that a formula exists for this exception cell.
    Result
    You have defined one or more exception cells for a query.
    Regards,
    Shailaja

  • Adhoc query designer

    Hi All,
    Is adhoc query designer (Portal) supports 7.3 version? we have 3.x version
    Thanks in advance
    Regards,
    Ravi

    Hi,
    Ad-hoc query designer is removed (BOBJ WebI fulfills this need).
    The use of WebI can be through LiveOffice, BICS, OLAP & SQL Universes, QaaWs and Data Federator for accelerated (BWA) or non-accelerated ad-hoc querying (can also be used for any 7.x system)
    Thanks,
    Venkat

Maybe you are looking for