Managing Easy Queries 
Easy queries allow external access to queries (for more information, see the overview in Open Analysis Interfaces).
To get an overview of the easy queries that you have generated, and to manage them, use Easy Query Manager (transaction EQMANAGER) in the BW system.
Prerequisites
You are in the system where you want to expose the easy query and you have the necessary authorizations for this system:
Authorizations
You have the required authorizations:
Role S_RS_RDEMO contains all authorization objects for BW.
Role SAP_BC_SIW_DEV contains all authorizations required for Service Integration Workbench (SIW). (SIW is needed for generation of the ABAP components in the easy query).
You still need an SOA role for service configuration with SOA Manager (such as SAP_BC_WEBSERVICE_ADMIN_TEC or SAP_BC_WEBSERVICE_ADMIN_BIZ). For more information, see the documentation for SOA Manager under Roles and Authorizations.
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 conditions or exceptions. The easy query runtime can display the query result but ignores conditions and 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.
SOA Settings
A standard profile must be configured before the easy query can create the SOA configuration profile. For more information, see the Web services documentation under Working with SOA Manager.
Procedure
Release an existing query for external access The system generates this as an easy query.
NoteYou 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.
End of the note.Call the Easy Query Manager (transaction EQMANAGER). Easy Query Management 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. Choose 
Refresh to 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 columns is 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.
NoteThis column also shows you if a generation step has been terminated, due to missing authorizations for example.
End of the note.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.
ExampleThis is normally only the case for terminated regeneration processes.
End of the example. NoteTo 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.End of the note.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.To generate an easy query again, select the relevant row and choose
Regenerate Easy Query. NoteYou 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.
End of the note.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.
Result
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 property Easy Query however, the system generates the associated easy query after transporting to another system if the Easy Query property has been set.
More Information
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/27777.