Definition of IS Search Connectors
IS search connectors are based on InfoSet Queries. You define the input and output fields in the InfoSet Query. The system transfers the input and output fields to the search connector and provides them as the maximum scope when defining a BCV query (see Search Connector). As a result, when defining a BCV query, you can select individual fields from the maximum scope of the InfoSet Query fields according to your requirements.
You can define InfoSet search connectors if the following applies:
You have defined InfoSet Queries.
You have identified the input fields of the InfoSet Query as value fields (Value Only) or as value and text fields (Text and Value). This ensures that during query execution it is visible exactly which fields need entries.
SAP offers InfoSet Queries of the following types:
Link
Table
Logical Database (LDB)
Report
Business Context Viewer cannot process InfoSet Queries that are based on InfoSets of the type 'logical database' (LDB). See further restrictions described in SAP Note 723577 
.
Processing InfoSet Queries that are Based on InfoSets of Type 'LDB'
You can use InfoSet Queries based on InfoSets of type LDB in the following way:
You release the InfoSet in its source system, using transaction SQBWPROP.
In the BEx Query Designer, you can use the InfoSet as an InfoProvider.
You create a BI query for this InfoSet in the BEx Query Designer and check the consistency.
You release the BI query for external use and save it. For more information, see Definition of BI Search Connectors.
You define a BI search connector using the InfoProvider and the BI query that you just created.
You reset the input and output fields.
The system copies over all features of the BI query to the search connector as the input fields and output fields. The system also creates additional output fields for all input and output fields. All key figures of the BI query are copied over to the search connector as the output fields.
You can use the new search connector in BCV queries.
Processing InfoSet Queries that are Based on InfoSets of Type 'Report'
When the system generates an InfoSet Query, it generates pieces of code and structure. For an InfoSet Query of the type 'report', this means that the system separates the logic of the report into different parts of code. For example, it places data definition into an include, whereas it places the processing logic into a function module. This has some unintended consequences for BCV.
When you use the parts of code that the system generates when creating an InfoSet Query, take into account that when you refresh a query view in the side panel, the system does not reset local variables automatically. This means that when you refresh a query view, the system extrapolates their value (for example, it doubles, triples, and so on, the value of a local variable upon repeated execution of the refresh function). This can lead to an incorrect result being displayed in the query view.
To avoid this problem, you must define the report the InfoSet Query is based on in a way that it refreshes every local variable directly after the data definition part of the report, even though this seems unnecessary when considering the report itself, outside of the context of BCV.
REPORT WHATEVER.
DATA:
ls_capacity type s_abc,
lt_result type t_def,
lt_capacity type t_abc.
CLEAR:
ls_capacity,
lt_result[],
lt_capacity[].
:
:
For more information about InfoSets, see SAP Library at http://help.sap.com, under 
SAP NetWeaver 
SAP NetWeaver 7.0 including Enhancement Package 1 SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology ABAP Workbench (BC-DWB) SAP Query InfoSets 
.
For more information about InfoSet queries, see SAP Library at http://help.sap.com, under SAP NetWeaver SAP NetWeaver 7.0 including Enhancement Package 1 SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology ABAP Workbench (BC-DWB) SAP Query InfoSet Query .