How to create an Infoset

Dear Experts,
I have to create an infoset based on 3 DSO's. I have to make sure this is exactly same as another infoset(zati01), which is available on our development system.(the only difference shold be source system). But how can i chek what join conditions they have used in the infoset.
I created infoset from context menu of infoarea and supplied description, and selected ODS1. And then from left hand screen include infoprovider icon selected other 2 DSO's and now the 3 dso's are in right hand screen. After that when i clicked on check icon, it says no on condition is available. I want to create join conditions exactly as they are in another infoset. But how can i check the conditions they used. After that how can i apply same join conditions. Can someone guide me? If anyone can send how to docs or screenshot, that would be really helpful.
my e-mail address is [email protected]
Thanks,
Riya

Hi,
http://help.sap.com/saphelp_nw04/helpdata/en/68/253239bd1fa74ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/68/253239bd1fa74ee10000000a114084/frameset.htm
The above URL's contain all the necessary things you need...
Hope this helps u lot...
Regards,
Koundinya Karanam.

Similar Messages

  • How to access a infoset query

    Hi
    I am assigned to a user group P1   but how to use the tcode SQ02 AND SQ03
    Whether to use TCODE SQ02 in first place or the other as i was unable to get in there To get into the infosetquery .
    Regards
    P

    You can create an infoset from SQ02.  If you need details on how to create an infoset, there are many postings in SDN, and you can check the sap help also.   You have to assign this infoset to your usergroup, by selecting the query and clicking on the Role/User Group assignment or from SQ03.  Make sure you are in the correct query area.  Once the infoset is assigned to the user-group, you can run the query from SQ01.
    Albert

  • What is Infoset and How to create

    HI Experts
    Can any one please explain me what is the purpose of INFOSET in BW
    and how to create a info Set between A Info Object and Cube
    Thanks

    Dear bw user,
    Check the below link
    http://help.sap.com/saphelp_nw04s/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
    Purpose is,
    1.To join required data from basic InfoProviders
    2.This allows building a relational BI data model with unified views for reporting (seeveral InfoProviders,but only one view). Therefore, we recommend keeping data in smaller, basic InfoProviders that can be flexibly joined for reporting purposes.
    3. To allow BEx Reporting on a DataStore object without turning the BEx Reporting indicator on
    4. To evaluate time dependencies (for example, join time dependent master data InfoObjects)
    5. To be able to create self joins and left outer joins
    Creatind in simple steps
    Infoset is a Virtual Infoprovider.
    Click on InfoProvider under modeling in RSA1 > Select InfoArea > right click Create Infoset > give name and description.
    Select the ODS / Master Data Object or more than one ODS and maintain the link.
    Infoset works on Join operation.
    you can include Infocube if it is BI 7.
    chk this link...
    http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
    Aslo see this link contents
    Creating InfoSets
    Prerequisites
    Make sure that the objects for which you want to define the InfoSet are active. Create any required InfoObjects that do not
    exist already and activate them.
    Instead of creating a new InfoSet, you can transfer one of the InfoSets that are delivered with SAP Business Content.
    Procedure
    1. You are in the InfoProvider tree of the Modeling function area in the Administrator Workbench.
    Choose the Create InfoSet function from the context menu (right mouse-click) of the InfoArea in which you want to create an
    InfoSet. You get to the Create InfoSet dialog box.
    2. Type in the following information for your new InfoSet:
    ¡ technical name
    ¡ long description
    ¡ short description
    3. In the Start with InfoProvider section, you determine which InfoProvider you want to use to start defining the InfoSet.
    ¡ Select one of the object types that the system offers you:
    ODS Object
    InfoObject
    Choose an object.
    If you want to choose an InfoObject, it must be a characteristic with master data. The system provides you with the
    corresponding input help.
    4. Choose Continue. You get to the Change InfoSet screen. For more information on editing InfoSets see Editing InfoSets.
    When you create an InfoSet, the system generates a corresponding entry for this InfoSet in the subtree of the InfoArea. The
    following functions are available from the context menu (right mouse-click) of this entry:
    • Change
    • Delete
    • Object overview
    Editing InfoSets
    Prerequisites
    Before you can get to the screen where you edit InfoSets, the following prerequisites have to be met:
    • You have created a new InfoSet.
    • You have selected the Change function from the context menu of an InfoSet entry in the InfoProvider tree of the Modeling
    function area in the Administrator Workbench.
    • You have called the InfoSet Builder transaction, and selected the Change function. You can find additional information
    under Additional Functions in the InfoSet Builder .
    Procedure
    1. You are in the Change InfoSet screen.
    Choose a layout for the InfoProvider tree:
    InfoArea
    InfoProviders Used
    All ODS Objects
    All InfoObjects
    For more information on the screen layout, particularly the layout of the InfoProvider tree, see Screen Layout: Changing
    InfoSets.
    2. Use the function Where-Used List via AWB to determine which BW objects use the InfoSet that you have selected. You get to
    the Administrator Workbench: Where-Used List screen. You are able to work out what would happen in the system if you made
    changes to the InfoSet. This helps you to decide whether or not it is sensible to make these changes at this particular point
    in time.
    3. You define the InfoSet by inserting one or more InfoProviders into the join.
    There are several ways of inserting an InfoProvider into the join control:
    ¡ From the InfoProvider tree:
    § In the InfoProvider tree, double-click on the entry that corresponds to the InfoProvider that you want to add to the join
    control.
    § Use the drag-and-drop function to move the InfoProvider into position.
    ¡ Choose the Add InfoProvider function, to add a particular ODS object or a particular InfoObject independently of the
    current layout of the InfoProvider tree. You get to the dialog box of the same name. Enter the data that the system asks you
    for.
    If you know the technical name of the InfoProvider that you want to add, this method is quicker than switching the layout of
    the InfoProvider tree.
    When this function is complete, the InfoProvider that you selected is displayed in the join control. For more information on
    the structure of the join control, see Join Control.
    4. Define the join conditions. For more information see Defining Join Conditions.
    5. You can get general information such as object version, date created and date changed via Goto ® Global Settings. You can
    also set the indicator Most recent Reporting for InfoObjects from here. You can find additional information under Most recent
    Reporting for InfoObjects.
    6. Via the button Documents, which appears on the pushbutton bar, you can access document editing for this InfoSet.
    7. You can use Check to check the correctness of the InfoSet definition. The log display is shown in the screen area under
    the join control.
    8. Save the InfoSet. The log display is shown in the screen area under the join control.
    9. Activate the InfoSet. After activation, the system executes the checks. The result of the activation is displayed in the
    log in the screen area under the join control.
    Additional Functions in the InfoSet Builder
    You can also use transaction RSISET to call up the InfoSet Builder when you want to edit an InfoSet. Select the InfoSet that
    you want to edit. Value help is available for this. Additional functions are also available to help you edit and manage your
    InfoSet.
    Compare
    You use this function from the main menu to check if the InfoProviders used in the InfoSet have been changed and the InfoSet
    needs to be adjusted as a result. For more information, see Matching InfoSets.
    Jump to object maintenance
    You use the InfoObjects and ODS Objects functions to jump to the maintenance screen for the InfoProviders included in the
    InfoSet definition.
    Info functions
    There are various info functions on the status of the InfoSets:
    • The Object Catalog Entry
    • The log display for the save, activate, and delete runs of the InfoSet.
    Display in tree
    You use this function to display in a tree structure all the properties of the A version (active) of the selected InfoSet.
    • Header data
    • InfoProvider and its fields
    • On condition
    • Wherecondition
    The display is empty, if no active version is available.
    Version comparison
    You use this function to compare the following InfoSet versions:
    • The active (A version) and modified (M version) versions of an InfoSet
    • The active (A version) and content (D version) versions of an InfoSet
    • The modified (M version) and content (D version) versions of an InfoSet
    The Display InfoSet screen appears. Depending on which option you choose, the system displays either all of the differences
    between the two versions of the selected InfoSet or all of the properties of both versions in a tree structure.
    Transport connection using AWB
    You use this function to transport an InfoSet into another system.
    The Administrator Workbench: Transport Connection screen appears.
    The system has already collected all the BW objects that are needed to guarantee the consistency of the target system.
    InfoSet data display
    You use this function to access the data target browser. If you have already loaded data into the InfoProviders included in
    the InfoSet, you can display this data.
    Delete
    You use this function to delete an existing InfoSet.
    Copy
    You use this function to copy an existing InfoSet and, if necessary, edit it further.
    Show/hide technical names
    You can use this function to show alias names for fields. These alias names are necessary in InfoSets, for example to be able
    to map self joins. Field alias names start with F, followed by a five-digit number.
    Defining Join Conditions
    Use
    A join condition determines the combination of records from the individual objects that are included in the resulting set.
    Before an InfoSet can be activated, the join conditions have to be defined in such a way (as equal join condition) that all
    the available objects are connected to one another either directly or indirectly.
    Usually, however, only rows containing a common InfoObject or rows containing InfoObjects that share the same basic
    characteristic are connected to one another.
    Connect tables T1 and T2 using a join and set as a join condition that the F1 field from T1 must have the same value as F2
    from T2. For a record from table T1, the system determines all records from T2 for which F2(T2) = F1(T1) is true. In
    principle, as many records from T2 can be found as required. If one or more records are found, the corresponding number of
    records is included in the result set, whereby the fields from T1 contain the values from the record from T1 under
    consideration, and the fields from T2 contain the values of the records found from T2.
    Procedure
    There are various ways of defining join conditions:
    Using a mouse-click
    Position the cursor over a row in an InfoObject. Press the left mouse-button and, keeping the left mouse-button pressed down,
    trace a line between this row and a row in another object. Providing that the join condition between the two rows that you
    have indicated is a valid join condition, the system confirms the join condition by displaying a connecting line between the
    two rows.
    Using the Link Maintenance pushbutton
    You get to the Link Maintenance dialog box.
    In a tree structure on the left-hand side of the screen, all of the InfoProviders that are already included in the join are
    displayed along with their fields or attributes. If you double-click on one of these fields or attributes, the system
    displays on the right-hand side of the screen all of the fields or attributes with which you are able to create a join
    condition.
    In the Selection column, set one or more of the indicators for the fields or attributes for which you want to create a join
    condition. The system generates valid join conditions between the fields or attributes that you specify.
    You use the Delete Links pushbutton to undo all of the join conditions.
    You use the All Characteristics or the Basic Characteristics Only pushbutton to choose between the corresponding display
    variants.
    We recommend that you use the Basic Characteristics Only option. The All Characteristics setting displays all of the
    technical options involved in a join. If you are not able to find a join condition on the basic characteristic level, then
    the All Characteristics setting is useful, but this is an exceptional case.
    When you have finished making your settings, click on the Continue icon.
    We recommend this method, because the system searches for all the possible join conditions for any field or attribute that
    the user specifies, ensuring that the join conditions are defined without errors.
    Using the Context Menu Left Outer Join – Inner Join
    Usually inner-join operators connect all the objects in a join to one another. You can also connect each object with any of
    the many other objects by using a left outer join operator.
    You can find additional information about usage and special features under Left Outer Join.
    If you want to use a left-outer join operator to connect an object, select the object and choose the corresponding function
    from the context menu.
    The system displays all of the valid join conditions that originate from this object. The connecting lines that represent
    these join conditions are labeled as Left Outer Join . InfoProviders, on which a left outer join condition is affixed, are
    differentiated by color from the InfoProviders that are connected using an inner join operator.
    If you used a left outer join operator to connect two objects, you have to make sure that all on conditions are linked except
    for these two objects with the formulation of join conditions.
    Note that you cannot add an object, which you have already connected by using the left outer join operator, to another
    object.
    If you want to use an inner-join operator instead of the left-outer join operator, select the object that you want to
    connect, and choose the Inner Join option from the context menu. Again the system displays all the valid join conditions that
    originate from this object, and labels the connecting lines accordingly.
    Result
    Once the join conditions have been defined in such a way as to connect all the available objects to one another, either
    directly or indirectly, the InfoSet is ready to be activated.
    You click on the Check pushbutton in the pushbutton toolbar to find out if these preconditions for the activation have been
    met.
    For objects that are joined by a left-outer join operator, there is one extra condition that has to be met, namely that all
    the other objects have to be connected to one another either directly or indirectly.
    http://help.sap.com/saphelp_erp2004/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
    Hope itr helps
    Regards
    Bala
    Also

  • How to create Infotype in Infoset?

    Hi,
       How to create new infotype in already created Infoset and existing infoset is created using logical database?
    Please suggest me what can be done.
    Thanks,
    S P Joshi.

    Hi,
    When you create an InfoSet, you select a logical database on which the InfoSet is based, and determine which infotypes are included in the InfoSet. They are displayed in the InfoSet as field groups. After you have selected the infotypes, you can determine which fields are included in the field groups for each infotype.
    Regards,

  • How to create Infoset&user group query--(query report)

    Hi Guys,
      how to create Infoset&user group query--(query report),
      Pls send me the exact procedure with Example....
                                                                              Regards:
                                                                              Kumar .G

    goto SQ03 and create an User Group If U want to create Ur Own.
    Goto SQ02 to create Ur Infoset by Giving Logical database name or Simple Database table
    Then Choose What ever data U need to be included in The Qurey in field Groups.
    Then Generate the Infoset
    Now Assign the infoset to user group
    Now goto SQ01 and Click on Other user group Button and choose Ur user Group.
    Then in the USer group select Ur Infoset and then create Ur own Query and save this.
    Now select the infoset query and goto More functions under Query menu and Generate report name.
    Now Create a transaction code for the report name generated.
    Now use the Tcode.
    Hope U have got the basic idea of creating Queries.
    ~BiSu

  • Interactive list musing abap query and how to create infoset records

    hi,
    Can any one suggest how to create interactive list using ABAP Query .And also infosets and ranked list ..thanks in advance
    Regards,
    Raghu.

    Hi,
    Check this
    Re: How to make output of ABAp query interactive(drill down)..?
    some info on the ABAP query
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40bec8da-4cd8-2910-27a9-81f5ce10676c
    hope it helps.
    Regards!

  • How to create infoset (pls urgent)

    Hi.. frdz
    For reports like employee MD, Applicant MD I have to create infoset, hence I request fridz let me know  how to create infoset and generation of reports thorough the infoset.
    Awaiting for ur favorable reply.
    Points would be awarded for answers.
    $Lakshmi

    Dear Naveen,
                Continuation this point...... i would like to know can we change the layout
    which we obtain through abap query.. Actually i have a requirement where
    i have to do the report in the abap query........now the client say he dont want
    the output which i have got through abap query.......first ihave shown him
    the ALV report , next i have shown him through ABAP list......but they wants the  report in their  own format.which they are using in lotus notes till now.......... Please let me know can i change the report which has been generated through Infoset.......and give him in their own LAYOUT........do we have any
    option .......or we have to change the STANDARD code generated by the abap query.
    tell me is it possible to change the layout and give in their format.....if you any body know please let me know......
    Please let me know.
    regards
    vamsi ravi

  • How to create querys based on infosets?

    Hi all,
    How to create queries on infosets ? can anyone let me know the procedures?
    Thanxs
    haritha

    Hi Haritha,
    TC SQ02 - Enter name of the Infoset – Create – enter name of Infoset - Data source -- > Table join by basis table – give name of table e.g pa0000 - Enter - Click on insert table if we want to include more tables – give name of table one by one and after finishing, place cursor on the joining lines and right click to delete unwanted relationships - check - and go back - field groups - include all table fields - click on generate button - go out
    Also refer this thread
    SAP Query-for  Reporting   how to create and use it
    Regards
    Karthik

  • How to create infoset query

    Hi,experts
    Can anybody give me documents on infoset query and step by step showing how to create infosetquery. I will really greatful to you all.
    Thanks
    Preeti

    Hi Preeti,
    1. You can query the data using 'Listcube' transaction.
    2. Instead of builing on tables, it sits on ODS (no need to worry about underlying tables).
    3. Visible on the Bex 'info area' as like other infoproviders.
    4. It generates additional key figure called 'Number of records' in the Bex. This will be useful for query.
    5. No additional ABAP can be used. But in RSQ02, you can use piece of ABAP.
    6. Queries created on data provider infoset can work like other queries including transport functionality.
    Hope helps.
    For more info check Re: Query on Infoset
    Bye
    Dinesh

  • How I create query from infoset ???

    Case 1 : I cannot create query from infoset
    Case 2 : I cannot create query from multiprovider that is created from infoset
    When I create multiprovider from infoset , I open query designer from this multiprovider... I received error message from query designer as below...
    File name : bextrace_qd_25510925_0556.txt
    Application error:
    17:56:02.171: Info: Query Designer Start. Revision: 601
    QueryDesigner.UserSettings.LoadSettings: Could not find file 'BExQueryDesigner.xml'.
    17:56:11.15: DEBUG ASSERT ### False - QDbCommandManager::.ctor - Method not called from CommandManager
    -CALLING-FROM- 17:56:11.15: DEBUG ASSERT ### False - QDbCommandManager::.ctor - Method not called from CommandManager ---
       at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
       at com.sap.bi.et.common.appl.Log.Debug.Assert(Boolean iExpectedCondition, String iAdditionalInformation, String iDetailedMessage)
       at com.sap.bi.et.QueryDesigner.QDfForm.InitFromCommandManager(QDbCommandManager iCommandManager)
       at com.sap.bi.et.QueryDesigner.QDbCommandManager..ctor(QDbApplicationData iApplicationData, QDfForm iWindow)
       at com.sap.bi.et.QueryDesigner.QDbApplicationData.Init()
       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()
    QDbApplicationData::ApplyUserSettings  - Standard View
    QDbCommandManager::DoViewCommand  - Table View
    QDbCommandManager::DoViewCommand  - Rows/Columns
    QDbCommandManager::DoViewCommand  - Cells
    QDbCommandManager::DoViewCommand  - Conditions
    QDbCommandManager::DoViewCommand  - Exceptions
    QDbCommandManager::DoViewCommand  - InfoProvider
    QDbCommandManager::DoViewCommand  - Filter
    QDbCommandManager::DoViewCommand  - Documents
    QDbCommandManager::DoViewCommand  - Where-Used List
    QDbCommandManager::CommandExecute  - Properties
    QDbCommandManager::DoViewCommand  - Properties
    QDbCommandManager::DoViewCommand  - Messages
    QDdEventDispatcher::MenuItemClickedHandler - Bar clicked: NewQuery
    QDbCommandManager::CommandExecute  - New...
    QDdEventDispatcher::MenuItemClickedHandler - Bar clicked: OpenQuery
    QDbCommandManager::CommandExecute  - Open...
    -EXCEPTION-START- 18:03:12.671: TRACE EXCEPTION  ---
    Exception Name: NullReferenceException
    Exception Message: Object reference not set to an instance of an object.
    Exception    at com.sap.bi.et.QueryDesigner.QDmCharacteristic.LoadValues()
       at com.sap.bi.et.QueryDesigner.QDbCharacteristic.GetValues(Boolean iReload)
       at com.sap.bi.et.QueryDesigner.QDmMetaBase.GetValues(Boolean iReload)
       at com.sap.bi.et.QueryDesigner.QDmCharacteristic.get_ValuesNonTechnical(QDeInfoObjectFilter iFilter)
       at com.sap.bi.et.QueryDesigner.QDpCharacteristicReference.ValueInitial()
       at com.sap.bi.et.QueryDesigner.QDpCharacteristicReference.set_pValue(Object value)
       at com.sap.bi.et.QueryDesigner.QDpString.set_Value(String Value)
       at com.sap.bi.et.QueryDesigner.QDbVariable.FromTable(RSZ_X_VAR isVar, QDcElement iElements)
       at com.sap.bi.et.QueryDesigner.QDbElement.FromTables(Hashtable iTables, QDcElement iElements)
       at com.sap.bi.et.QueryDesigner.QDbElement.CreateElements(Hashtable iTables, QDcElement iElements)
       at com.sap.bi.et.QueryDesigner.QDbElement.Load(QDeElementType iElementType, String iName, String iCompUid, String iGenUniId)
       at com.sap.bi.et.QueryDesigner.QDbQuery.Load(String iName, String iCompUid, String iGenUniId)
       at com.sap.bi.et.QueryDesigner.QDbApplicationData.LoadQuery()
       at com.sap.bi.et.QueryDesigner.QDbApplicationData.LoadFromServer()
       at com.sap.bi.et.QueryDesigner.QDbCommandOpenQuery.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 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- 18:03:12.671: 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()
    Please kindly help me !!

    Hi,
    check the links to create  Infosets
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d6419190-0201-0010-0cb0-d7e4503c1231
    http://help.sap.com/saphelp_nw04s/helpdata/EN/ab/7a877cba29144b85d07f26f1f50cd8/content.htm
    Thanks.

  • How to create a report to bring all data from two different Info providers

    Hi All,
    I have a peculier problem while creating a report. I have two custom info providers one DSO and another Cube. There are only two common fields between these two Info providers . I need to create a report such that the report displays all the values from DSO but user can have the selection option on one of the fields in the Cube.
    Here is an example
    DSO Contents:
    DocNum-     DocItem-     DocText-     Amount-      Quantity
    10000----     10----            ABC----          100----           10
    10001----     20----     DSN----     200----     10
    10005----     20----     DSN----     200----     10
    Z1003----     10----     CAN----     500----     1
    Cube Contents
    DocNum-     DocItem-     Date-----          InvoiceAmt
    10000----     10----     1/10/2009----         50
    10001----     20----      2/20/2009----        100
    10005----     20----      2/25/2009----        100
    The report needs to be displayed as shown below when the user selects value for date from 1/10/2009 to 2/20/2009
    DocNum-     DocItem-     DocText-     Amount-      Quantity
    10000----     10----     ABC----     100----     10
    10001----     20----     DSN----     200----     10
    I hope this was clear for you to understand. I would really appricate if any one can answers about how to resolve this problem. I cannot add the date filed to DSO and I also have Doc Num and Item as the user selection fields in the report.
    Thank you all in advance and i would really appreciate for your suggestions.
    Regards
    Chinna
    Edited by: chinna2479 on Mar 3, 2009 7:38 PM
    Edited by: chinna2479 on Mar 3, 2009 7:39 PM

    Hi chinna,
    Two possible options, I can think of now, but both of them may be a compromise with performance.
    1. create an infoset and then a query on top of it, provided we have a one to one relation in both the targets. That is, the combination of doc and item number is not duplicate in either cube or ODS.
    2. Create a master data object of doc and item number and have date as an attribute. Load that from cube data and make date as navigational attr.
    Use this navgntal attr for selection in your report.
    Let us know, if you require any further info.
    Naveen.A

  • How to Create a Functiona Query

    Dear all,
    Could any body detail me how to create a functional query. Please give me step by step procedure to create a query.
    I would appreciate if you can give me a material with screen shots. Your help will be highly appreciated.
    Thank you
    Raghu Ram

    Hi Raghu,
               Go through this document it may help you,
    SAP Query
    Step 1: Create User Group – SQ03
    Follow the menu path – SAP Menu > Tools > ABAP Workbench > Utilities > SAP Query > User Groups
    a) In the User Group: Initial Screen -
    Enter User Group Code (self named)
    Click on “Create”
    b) In the User Group (Code): Create or Change pop-up window -
    Enter the User Group Description
    Click on “Save”
    c) In the Create Object Directory Entry pop-up window -
    Ö Click on “Local Object” button
    Ö The User Group Created is saved
    Step 2: Create User Group – SQ02
    Follow the menu path – SAP Menu > Tools > ABAP Workbench > Utilities > SAP Query > Infosets
    a) In the Infoset: Initial screen -
    Ö Enter Infoset Code (self named)
    Ö Click on “Create” button
    b) In the Infoset: Title & Database Screen -
    Ö Enter Description of Infoset in the “Name” field
    Ö In the Data Source selection: Select appropriate Data Source by clicking
    the radio button
    · Source the data can either be multiple tables OR single table. There are 4
    options for the user to select from
    Ö Click on “Continue” (Enter)
    Ö Selected Table gets displayed in the Infoset : Initial Screen
    c) In the Infoset: Initial Screen -
    Ö Click on “Insert Table” button
    d) In the Add Table Screen -
    Ö Enter the Table Name that is to be inserted
    Ö Click “Continue” (Enter)
    e) In the Infoset: Initial Screen -
    Ö Click on “Back” button
    f) In the Field Group Defaults pop-up Screen -
    Ö Select Appropriate Field Group Option by clicking on the radio button
    · there are 3 options to select from. User can select Empty Field Group
    option and then select the data fields in the steps explained further.
    Alternatively, User can select an option which clubs all the data fields
    From all the tables selected
    Ö Click “Continue” (Enter)
    g) In the Change Infoset Screen -
    · the left side lists the Tables that the user has selected in step b, c & d
    · In the right side, system creates field groups, one for each table listed in the
    left part. Initially, the Field Groups are empty
    Ö In the Left Side, Click on the arror next to the table name and expand and
    display all the data fields in the table
    Ö Select a Data Field from the expanded Table view, which is to be added to
    the Field Group on the right.
    Ö Select a Field Group on the right side, in which Data Field selected above
    has to be added
    Ö Right click on the Data Field selected and click on “Add Field to Field Group”
    Ö The selected Data Field gets added to the selected Field Group, which is
    indicated by an arrow next to the Field Group.
    Ö Carry out the steps above to add the required Data Fields to the respective
    Field Groups
    Ö After transferring Data Fields to Field Groups click on “Generate” button
    h) In the Create Object Directory Entry Screen -
    Ö Click on “Logical Object” button to generate the infoset
    i) In the Change Infoset Screen -
    Ö Click on the “Back” button
    j) User is taken back to the “Infoset: Initial Screen” which displays the
    created Infoset record.
    Step 3: Assigning User Group to Infoset – SQ03
    Follow the menu path – SAP Menu > Tools > ABAP Workbench > Utilities > SAP Query > User Groups
    a) In the User Groups: Initial screen -
    Ö Enter the User Group for which Infoset is to be assigned
    Ö Click on “Assign Users & Infosets” button
    b) In the User Group: Assign Users Screen -
    Ö Click on “Assign Infosets” button
    c) In the next screen, select the Infoset, which needs to be attached to the
    User Group selected
    d) Click on the “Back” button
    Step 4: Creating Query – SQ00 & SQ01
    Follow the menu path – SAP Menu > Tools > ABAP Workbench > Utilities > SAP Query > Queries
    a) In the “Query from User Group: Initial Screen -
    Ö Click on “Other User Groups” button
    Ö In the pop-up screen, User Groups, select the User Group for which the
    Query has to created. The pop-up screen closes.
    Ö Enter the Query Code in the “Query” field
    Ö Click on “Create” button
    b) A pop-up screen “Restrict Value Range” shows the list of Infosets assigned to
    the User Group
    Ö Select the Infoset for which Query has to be created
    c) In the new screen Create Query: Title, Format -
    Ö Enter the Description of the Query in the “Title” field
    Ö Click on the “Next Screen” button
    d) In the Select Field Group” screen
    Ö Select the Field Groups from which Data Fields have to be selected for the
    Output
    Ö Click on the “Next Screen” button
    e) In the “Select Field” screen -
    Ö Select the Data Fields, which should appear in the output
    Ö Click on the “Next Screen” button
    f) In the Screen “Selection” -
    Ö Select the Data Fields for the selection criteria
    Ö Enter the sequence in which the selected fields would appear in the input
    screen of the query.
    Ö Define if the selection criteria should be Single Value or Multiple Value Range
    by clicking in the appropriate check boxes
    Ö Click on the “Basic List’ button
    g) In the screen “Query Layout Design” -
    Ö Select the Output Fields from the Data Fields section by clicking the
    appropriate check box
    Ö Change the sequence of Data Field columns if required
    Ö Click on the “Test” button to test the query created
    h) On the “Test Query” screen click “Continue”
    i) In the “Query” screen -
    Ö Enter the selection criteria
    Ö Click on “Execute” button
    j) Save the Query created
    Step 5: Running the Query – SQ00
    a) In the Query From User Group: Initial screen –
    b) Click on “Other User Groups” button to select the User Group
    c) In the pop-up screen “User Groups” select the User Group
    d) System lists all the queries created for the User Group
    e) Select the appropriate Query
    f) Click on “Execute” button
    g) User is taken to the Selection screen
    h) Enter the selection criteria and click on “Execute” button
    i) System runs the query and gives the output
    Regards,
    Murali.

  • SAP Query-for  Reporting   how to create and use it

    Hi SAP Gurus,
    i need your help. in my project, client is asking to create queries to generate reports, i am not familiar with queries, so would appreciate it if any one can guide me and tell me the procedure for writing and creating queries soon.
    also if you have any study material on steps on How to write and create queries for PP module
    thank you very much

    Hi
    Please refer below document
    http://www.thespot4sap.com/Articles/SAP_ABAP_Queries_Introduction.asp
    Also refer below
    How to Create Infoset Query (SAP Query)
    Steps on how to proceed to create a Query:
    ADHOC QUERY
    A query can be created to extract information from master records  i.e  Infotypes.  For example, by creating a query , the data relating to an employee contained in various Infotypes can be extracted.
    Proceedure :  
    Decide on  the various Infotypes we  want to make the query.  Decide on the area where we  want to query  i.e  Global area or Standard area.  Standard area is client specific and globel area will include all clients.
    Menu : HR – PM – Admn -  Information System -  Adhoc Query
    Select area standard and select the  user group already created
    Creation of new query  :  
    TC SQ03  -  Select Environment – Select Standard Area -  Enter  --  If new user group is to be created, enter name of the user group, click on create and enter necessary information and  exit after saving
    TC SQ02  -  Enter name of the Infoset – Create – enter name of Infoset -  Data source -- >  Table join by basis table – give name of table e.g  pa0000 -  Enter -  Click on insert table if we  want to include more tables – give name of table one by one and after finishing,  place cursor on the joining lines and right click to delete unwanted relationships  - check  - and go back  - field groups  -  include all table fields  - click on generate button   -  go out
    TC SQ03  -  Select user group  -   eg.  Payroll
    Infoset  - Enter name of newly created Infoset 
    Assign users and Infosets  -  Assign infosets  -  put tick on payroll  - save and go back
    TC  PAAH  -  Expand the nodes and put tick on relevant fields depending upon necessity
    Save the query  by giving the same name as infoset for easyness..
    For executing a query which is already created
    1. Go to SQ01 transaction
    2. Go to Environment menu->query areas->std areas
    3. Then choose the user group where the query is created
    4. It will display all the queries created for the group.choose the query you want to executeand click execute.
    5. will take to the initial screen
    6. Enter the required parameters and execute
    Regards
    Ranga
    Message was edited by:
            Ranganathan Srinivasamurthy

  • Dates are not mapped as the Date data type in Universe created on Infoset

    Hi,
    When i try to create the universe on top of Infoset query, the date fields present as the variables in SAP BI Query are not mapped as date data type in Universe, instead they are considered as Characters, hence the prompts related to those variables are coming s List of values instead of Calendar in WebI.
    Can any one pls help me to find the solution on how to map date variables as calendar in Webi Prompts.(For SAP BI Queries created on Infoset)
    Edited by: Nisha Makhija on Jul 20, 2009 5:59 PM

    Hi Ingo,
    Thanks for your response!!
    The I Query is built on Top of BW MultiProvider and the InfoObject is of Type DATS.
    Actually our Modeling on the BI is as follows :
    DSOs> Infoset>Multiprovider->BI query>Universe.
    Since we were not able to get the prompts as Calander so We tried Debugging on different Data targets to find the root cause. Please find our observations as follows:
    When I tested the same date infoobject(of Type DATS) by creating a BI Query on top of DSO, Infocube & Multiprovider ,the Prompts are working fine as a calander in WEBI Report.
    But when the BI Query is built on Infoset data target, In WEBI Report I am getting list of values rather a Calender prompt .
    I tested in the Universe that field is appearing as Character instead of Date.
    Please guide to resolve this issue.
    Thanks,
    Nisha.

  • How to create a target group with all prospects?

    Hi guys,
    I am wondering how do I have to set up my data source when I would like to build a target group in my segment builder which includes all persons/contacts/organizations with the bp role prospect?
    Which infoset do I need to choose in my data source? What do I need to fill under details?
    Thanks a lot for your help.
    Best regards,
    Janine

    Hi Janine,
    What I could understand is that you require to create target group of all BPs having BP role as prospects.
    To do so, you can create an infoset joning tables BUT000 and BUT100. The table BUT100 , has a field "BP Role"->select it, so that it is available when you are creating the attribute list using this infoset.
    Create a data soucre for this infoset. Then when creating a attribute list, include this datasource and under this select the attribute "BP Role". Add filter to this attribute for prospects.
    This filter can be used in segmentation builder in UI to create TG containing BPs having BP role as prospect.
    Hopes this helps you.
    Thanks,
    Apoorv

Maybe you are looking for

  • Help understanding workflow for best quality.

    Greetings. I've read countless hours on this forum in the effort to understand this extremely complicated subject of getting my video out of my camera and onto a DVD in the best quality possible, and I'm still a little confused. I'm not recording any

  • Project Conventions for J2EE Apps Early Access...

    Hi I am trying to set up a standardized directory structure for J2EE apps that is flexible enough from a simple webapp to a complex J2EE App with multiple EJB components, WARs...etc..etc... For this, I turned to Java Blueprints Guidelines, Project Co

  • What is the best way to display list of software titles for sale?

    I am a small retailer that would like to display a list of approximately 15-30 software titles in the most professional way (with prices). Can anyone recommend a layout that would serve this purpose, the ones in the template just don't seem to cut it

  • Select all check box in interactve report

    Hi,   I am writing an interactive report. The second screen will display the check box for thye user to select the items. Now the requrement is to create an option like select all means it should select all the check boxes. How can I create this opti

  • Opening merged WebHelp projects

    I currently have a project that I just converted to WebHelp (stand-alone, not merged). In addition, I have another projected that I converted; this is used as a "merged" project and is merged into one mentioned previously. When I am in the stand-alon