Query visible in RSZELTDIR not in Query designer

Hi experts ,
I do a transport for Query from dev to  qas, the name of query is visible in Table of query : RSZELTDIR in my BW Qas, but when I open my Query designer in BW Qas I donu2019t see my query.
In suggestion please.
Tanks & best regards
ILYAEBI

Hi ILYAEBI,
I dont think you have problem with the transports, if the query is visible in RSZELTDIR means, query is imported successfully.
Pl. check the below:
If u have any folders, under which query is assigned to it means and folder is not imported to QA system query will not be visible in query designer.
Further chjeck up:Go to query designer and search the query with the SERCH tab availbe in the query designer. i think u should be able to get the query.
let me know if any details required...hope this helps you!
Best Reagrds,
Maruthi

Similar Messages

  • Attribute not visible in the Query Designer

    Hi,
    I am not able to see 0BPPartner as attribute of object 0Customer in the Query designer .It is marked as display attribute.For some user its visible & for Some not.
    Please help me its very urgent.
    Thanks & regards,
    Anita

    Hi Anita,
    As you stated earlier that some users are able to see it and some are not then it surely is a Authorization/Profile issue. Speak to the BASIS/person who manages this to resolve the issue.
    Bye
    Dinesh

  • Attribute not visible in Query Designer

    hi BI Gurus,
    I could not see some InfoObjects(Attributes) which are marked Authorization Relevant, in the query designer. And the strange thing is, they are not visible even for the user with SAP_ALL and 0BI_ALL assigned. The authorizations for the  cube in which the main char is used looks fine.
    I have checked all the options in RSECADMIN, everything looks good.
    pls help me in finding the solution..
    thanks
    Cnu..

    check out with the info object screen in attribute tab, navigational attribute on/0f switch box, if u r using FF source system.
    check out with the infocube whether u r checked the check boxes in navigational attribute tab.
    regards
    harikrishna.N

  • Variable not visible in query designer

    Hello,
    I have 4 variables created for an InfoObject. But for one of my query written on Infoset, under that InfoObject in query designer it only shows me 2 variables.
    Any ideas what is causing the other 2 variables not to be visible?
    Thanks in advance,
    vamsi.

    which type of variables have you created?
    Regards,
    Chandra.

  • New key figures in multiprovider not visible in query designer

    Dear Experts,
    I added a cube and  keyfigures to the multiprovider definition.
    The multiprovider is activated successfully.
    The added keyfigures come only from this new cube.
    I  identified these new keyfigures to this new cube only.
    There is an existing query based on old version of the multiprovider without the new cube.
    When i relaunch query designer and re-open this query, i could not see the new keyfigures.
    When i create a new query, also its not showing the new keyfigures.
    Is there something not refreshed that I do not see these new key figures?
    Kindly advise. Thank you!
    Best regards
    Bass

    Hi,
    Some time it happens that newly added key figures and characteristics are not visible immediately in Bex query designer. Just check for warnings if any encountered while activating else try editing and re activating your Multiprovider and also proper field assignment.
    Newly added Key Figures should be visible in both New and Old queries without any differentiation. Just log off and log in back after some time, there is a good possibility that this inconsistency would be resolved.
    Regards
    Raj Rai

  • Hierarchy not visible in Query designer

    Hello Experts.
    I am trying to create a query in BW 3.5 but I ran into one issue. I created a hierarchy for an Infoobject. But I am not able see this Hierarchy for the Infoobject in BW 3.5 Query designer although I can see it in BI 7.0 Query designer.
    Any help in this regards will be appreciated and points will be assigned.
    Than

    Check if you have made the "hierarchy" Active in your BW 3.5 query and also chosen the hierarchy correctly.
    Right click on the characteristic----
    > properties.
    Hope this helps.

  • In Bex Query designer - Flat is not supported

    Hi all,
    In Bex query designer,
    While execution of the query, the following error is coming .
    Failed to process request; contact your system administrator
    Error Summary
    Exception occured while processing the current request; this exception cannot be handled by the application or framework
    If the information on this page does not help you locate and correct the cause of the problem, contact your system administrator
    To facilitate analysis of the problem, keep a copy of this error page Hint: Most Web browsers allow you to select all content, and copy and paste it into an empty document (such as in an email or simple text file)
    Root Cause
    The initial exception that caused the request to fail was:
    Flat mode is not supported!
    java.lang.UnsupportedOperationException: Flat mode is not supported!
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Characteristic.setHierarchy(Characteristic.java:330)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Characteristic.readStateFromDomNode(Characteristic.java:542)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QvCharacteristic.readStateFromDomNode(QvCharacteristic.java:379)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QvStructure.readStateFromDomNode(QvStructure.java:106)
    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.AttributeContainer.readStateFromDom(AttributeContainer.java:297)
    Details: Full Exception Chain
    Most important error.
    regards
    Selvan

    Hello,
    I have the same problem with Flat mode is not supported! at ... Characteristic.setHierarchy(Characteristic.java:335):
    Open, close, reload of the query does not help.
    Other SDN-thread "500 Internal Sever - Flat Mode is not Supported!" related to transaction RSRT.
    Execution of query via RSRT works, but the problem still persists in the BEx Web Analyzer.
    Could be related to a BEx Web Analyzer "bookmark" ("Personalize Web Application").
    I have not deleted any item. We use SAP BW 7.0 with a patch level approx. 09.2009.
    The "flat-mode" seems to be the  "BEx table mode".
    SAP hints do not seem to fit here:
    - 715820 BW 3.x Front-End Patch 14 (we use BW 7.0)
    - 874825 SAPBWNews for BW 3.x Front-End Support Package 19
    - 874827 SAPBWNews for BW 3.5 Front-End Patch 08 (we use BW 7.0)
    - 905229 update to SAPTableTree
    - 909824 Termination in flat mode when an object is deleted (old?)
    - 909827 Incorrect InfoProvider-dependent characteristic values
    - 910602 Condition includes too many characteristics (usage of deleted elements)
    - 915215 Termination when a query definition is changed (old? visibility of elements?)
    - 968273 Cache with flat files: Exception is not caught (does not apply to given error)
    Any new solutions?
    Best regards
    Thomas

  • Mapped characteristics in Multiprovider not available in Query Designer

    Hi,
    we have a multiprovider with approx 10 cubes and lot of characteristics, Navigational attributes mapped to it. I have added around 3 more characteristics and mapped to underlying cubes. But these added characteristics are not visible in Query designer.  Is there maximum limit for the number of characteristics.
    Thanks,

    Disconnecting the BEx made it work. But i dont understand i added this yesterday in the multiprovider. But i also removed some navigational attributes from the mapping. I will re-map and check. Thanks for the tip.

  • Text value is not getting displayed in Query designer !!

    Dear experts..,
    i have created a new query in query designer using my info provider and then selected one field in default value and then trying to restrict that particular field while selecting the restriction in query designer am getting the exact text value but after generating the report instead of text value , key value is getting displayed....so how can i get text instead of key value??
    please help me friends....
    i have posted in OSS mesage also...i got a reply like...even i didnt understand his reply too...what he is trying to say?
    whether can i get text display or not???
    can any one help me in this regard???
    SAP Reply----
    Hello kumar,
    After another analysis I have to inform you about general concept of
    "compounded characteristics".
    A compounded characteristic bounds two characteristics. The technical
    name is generated by both technical names of the two characteristics
    combined by two underlines "__".
    An individual text is only available for one single combination of both
    characteristics.
    Example:
    =======
    Compounded characteristic "Famous family name" is a combination of
    characteristic "COUNTRY" & "ETHNIC". Technical name: COUNTRY__ETHNIC
    Values for Country: USA, Australia
    Values for Ethnic: Asian, Latino
    Possible value combinations with individual text:
    USA & Asian; text: "Ling"
    USA & Latino; text: "Sanchez"
    Australia & Asian; text: "Chu"
    Australia & Latino; text: "Garcia"
    (Keep in mind the individual text only valid for the specific
    combination.)
    In analogy to the issue that you reported, you want to restrict this
    compounded characteristic. In the window where you select the restrictedvalue (called Selector) you'll see on the left hand side all available
    combinations of the characters with an individual text.
    You select family name "Chu" and drag'n'drop it to the right side.
    Actually you can only restrict the right compounded characteristic. In
    our example you would restrict on characteristic "ETHNIC" with value
    "Asian". (When you switch on technical names this comes more clear). Thetext "Chu" is displayed in the context of Selector because you selected
    value combination Australia & Asian. But in the end it's just a
    placeholder(!) for any combination of characteristic "ETHNIC" and value
    #Asian#; in our example it could be USA & Asian "Ling" or Australia &
    Asian "Chu").
    By leaving the Selector the individual text is gone because now the
    context is lost between the two characteristics. You have just a
    restriction on characteristic "ETHNIC" with value "Asian". An individualtext can't be displayed because the compounded characteristic is not
    specified for this restriction.
    You're right, it is confusing when "loosing" the text of a restriction.
    But accoring to the concepts of the compounded characteristics it
    is a correct behavior.

    Hi anandkumar,
    I belive this issue can be resolved by changing the  Query proprties for the perticular field.
    Kindly check the Field proerties in query designer and ensure that Text is enabled ather than Key.
    __Field property check up:__Go to query designer->click onn the field-> Right hand side in properties click on display tab-> select Text in drop down menu of Display as tab.
    FURTHER CHECK UP: check the master data avaiulability for the perticular info object, if masterdata is not available, do the text data for txt data availability in report level.
    Hope this helps you!!
    Best Regards,
    Maruthi

  • Master data is not getting displayed in the Query Designer

    Hi,
    I have a DSO in which I have an InfoObject called Emp No. in the Data Field.
    The Emp.No is being maintained as master with (Emp Name, Address, Telephone No, DOB) as attributes.
    I have loaded the data in the Emp. No. master. Then tried loading the transaction data in DSO.
    The Emp.No is there in the DSO active data, but in the query designer its not getting displayed.
    Hope its clear.
    Please help.
    Thanks

    Hi,
    I have brought the Emp. No. in the Key Field and also have activate the master data again.
    Yet my Query Designer doesn't have the Emp. No.
    I have done a full load for both Master and Transaction.
    Please advice me what the other alternative.
    Thanks

  • Not able to enter data in query designer

    hi
    can any one help, i created a input ready query on multi provider contain both standered and real time cube, here real time cube not contain any data.
    when i created layout by taking 2 chracteristics and 2 key figures from real time cube it give me like " no data available".
    what i have to do here to enter data to realtime cube key figure

    First check if you have created aggregate level.
    Second check the loading behavior setting on the Realtime infocube- it must be set to "Real- Time Data Target can be planned, data loading not allowed’'.
    Third, query must be also input ready- in other words set the Selections (key figures) to input ready in Query designer.
    Finaly, when you open context menu over the query, Bex Analyzer' Analysis grid, you can check the input ready settings for every cell if you want. If you did all steps, mentioned in the text above, input ready check box will be automatically checked for every cell of input enabled keyfigures...
    Alex.

  • 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

  • Nav Attributes not seen during creation of RKF in Query Designer

    Hi
    SCENARIO
    I have a Char InfoObject POSTFI[POSTFI is Navigational Attr] with 3 Navigational Attributes included in the InfoCubes.
    1. ZINREPIND Reporting Indicator
    2. ZFITMCD01 Statement 01 Financial Item
    3. ZPCNR1 Profit Center Indicator
    NOTE: All the above mentioned Nav Attr are properly set as Nav Attr and Active, Check and Rechecked.
    We have 2-InfoCubes Current and Historical[both have same Structure].
    A MultiProvider is build using the above 2-InfoCubes and the Char InfoObject PostFi is included in the MultiProvider.
    Now I am trying to Create a Report using Query Designer and in that I have to Create a RKF[GrossSales1] and
    the Condition for which is KeyFigure=FINAMT, where POSTFI_ZFITMCD01 = 5010, POSTFI_ZPCNR1= Y
    PROBLEM
    I can see the Nav Attr ZINREPIND, ZFITMCD01, ZPCNR1 in the main Screen of the Query Designer's LeftHandSide Pane containing KeyFigures and Dimenions under Dimension Financial=> PostFi=> Nav Attr ZINREPIND, ZFITMCD01, ZPCNR1.
    While creating the RKF on KeyFigure FINAMT I am just able to see the InfoObject POSTFI[in its resp Dimension] in the
    Display RKF GrossSales1 Screen in the Left Hand Side Pane where we see the KeyFigures and Dimensions.
    But I am NOT able to see the Nav Attr's ZINREPIND, ZFITMCD01, ZPCNR1 anywhere in the LHS Pane of the Display RKF GrossSales1 Screen.
    Now I cant Create the RKF bcoz I cant see the 3NavAttr's of Char InfoObject PostFi it the LHS Pane and the 2-Nav Attr required for creating the RKF.
    Can anyone PLEASE let me know How can I see/bring these Nav Attr ZINREPIND, ZFITMCD01, ZPCNR1 in the LHS Pane of the RKF Creation Screen to add them to make my RKF ?
    Thanx in Advance

    Hi
    As per your explanation, below are the details
    POSTFIPOSTFI --- This is navigational attribute which has below 3 objects as navigation attrs.
    1. ZINREPIND Reporting Indicator
    2. ZFITMCD01 Statement 01 Financial Item
    3. ZPCNR1 Profit Center Indicator
    first one, could you please confirm whether POSTFIPOSTFI is main info object or it is attribute of another info object.
    If it is attribute of another info object, then the last attibutes(3) are called Transitive attribute(attributes attribute).
    Reporting on Transitive attributes is only possible with the creation Info Sets.
    If my guess is correct, then create Info Set based two info cube now create the query.
    Hope it will work
    Regards,
    Venkatesh.

  • Infoarea not appearing in Query designer

    Hi - I have some cubes created under cross application components infoarea but the infoarea is not appearing in the query designer. I have to create reports on these. how can I see them in query designer?
    Thanks,
    Raj.

    Hello,
    Please check your role. You do not have the authorization for that infoarea.
    Hope it helps,
    Regards,
    Meric

  • Infoobject in infoset but not displaying in query designer

    Hi,
    I have created a query on infoset(ods1 & ods2).
    a custum defined infoobject (fiscyr) is not displaying in query designer while it is present in infoset.
    pls give your inputs,for why this infoobject is not available in query designer.
    Thanks
    Radika

    Hi Radika,
    I cannot think of anything other than the solutions already mentioned in this thread (checking the IOBJ in infoset, running RSISET and activating it). I just had a foolish idea that you might not be looking for the right IOBJ. All the IOBJs from an infoset are not displayed with their original technical names in the query designer. They are disdplayed in the format: <infoset_technical_name>_FXXXXX where XXXXX is a number.
    Also try one more thing. Go to transaction RSISET and type in the technical name of the infoset there.
    Right below the box where you type the Infoset name is a check button. Check your Infoset there and then activate it from within the RSISET transaction (the activate button is right after the check button). With Infosets, sometimes just activating it from within RSA1 does not work but RSISET always seems to work.
    Do this and see if it helps.
    Thanks & regards,
    Nikhil

Maybe you are looking for