Show TOC

Managing Easy QueriesLocate this document in the navigation structure

Prerequisites

Note

The easy query concept was introduced in SAP NetWeaver 7.3 SPS05.

You are in the system where you want to expose the easy query and have performed the required configuration steps (see Configuring Easy Queries).

Query Definition

You have defined the required analytic query. Note that the analytic query can only be declared an easy query if it meets the following criteria:

  • Key figures cannot be mixed with characteristics.

  • Key figures can only be used on the X axis.

  • Characteristics can only be used on the Y axis.

  • Query variables are allowed. Single values or intervals can be used (depending on the variable definition). Multiple selection (of single values) is not possible.

  • The analytic query is static (standard view only).

  • The analytic queries can contain hierarchies and free characteristics. The easy query runtime only returns the standard view of the analytic query however. Hierarchy data is returned. Navigation and drilldown in the hierarchy or using free characterstics is not supported however.

  • The analytic query can contain formatting settings. The easy query runtime does not return this information however.

  • The easy query does not support any exceptions. The easy query can display the query result but ignores exceptions.

  • The easy query does not support any planning. The easy query runtime can display the query result but ignores planning functions and is read-only.

Context

Easy queries allow external access to queries (for more information, see the overview in Open Analysis Interfaces).

For an overview of the easy queries that you have generated, and to manage them, use Easy Query Manager (transaction EQMANAGER) in the BW system.

Procedure

  1. Release an existing query for external access The system generates this as an easy query.
    Note

    You can do this by selecting the By Easy Query option in the query properties on the Advanced tab page for a query in BEx Query Designer (see Query Properties).

    When you save, the system starts saving the easy query in the background. An RFC module is created with a Web service definition. The system creates the corresponding SOA configuration profile for the generated easy query based on the SOA standard settings. You can then use the easy query as a SOAP service.

    To delete easy queries created for a query, deselect the By Easy Query option in the query properties on the Advanced tab page in BEx Query Designer.

  2. Call the Easy Query Manager (transaction EQMANAGER). Easy Query Manager is started in a new browser window.

    The system shows a list of all queries that there is an easy query for in your system. If the list of queries with easy queries is very long, choose Filter On/Off and select filter criteria for the list. By pressing Refresh, you can update the information in the list.

    The system displays the following information regarding the status of the easy query:

    Column

    Description

    Usage Count

    This column shows how often the easy query has been used.

    Processing Status

    This column serves as a progress indicator for the generation of the easy query:

    • C (create) indicates that generation is currently under way.

    • U (update) indicates that regeneration is under way.

    • D (delete) indicates that deletion is under way.

    Once the process is complete, this column is empty.

    Note

    This column also shows you if a generation step has been terminated, due to missing authorizations for example.

    Obsolete

    This column shows queries whose easy query is obsolete. In other words, the query has changed since the last time the easy query was generated.

    Example

    This is normally only the case for terminated regeneration processes.

    Note

    To improve performance, this column is hidden when the transaction is started. To show the column, choose Obsolete On/Off. If you choose this option, the system reads the easy queries from the database again and checks whether they are obsolute. This is time consuming.

  3. To test the easy query, choose Test Easy Query. Here you see a preview of the potential query result based on the minimum requirements. If the query contains mandatory variables, a screen appears where you can enter variable values. Enter the required values in the form of technical IDs. No input help is provided here. Optional variables are not available for selection in the preview.
  4. To generate an easy query again, select the relevant row and choose Regenerate Easy Query.
    Note

    You can create an easy query for an older version of a query. To do this, copy the query, change it and and then a generate a new easy query for this modified copy of the query.

  5. The easy query background job is processed in the inbound queue. To check whether the job is running, how long it has been running for and whether it has been terminated, choose Monitor.

Results

The required easy query is now available for use.

For more information on the easy query result, see Easy Query API.

Transport Connection

The easy query is not a transportable object. As the query definition contains the Easy Query property however, the system generates the associated easy query after transporting to another system if the Easy Query property has been set.

Next Steps

You can find out more in the article Easy Queries in SAP NetWeaver BW in the SDN, at http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/27777Information published on SAP site.