Skip to Content
Technical Articles

Error: Info-Object ‘XXX’ must be uniquely selected in Query

Brief description about the application, system, and device: Error: Infoobject ‘XXX’ must be uniquely selected in Query in Bex Query Designer when SAP BW is on HDB and Eclipsed Neon has been used for any object modifications, Product: SAP Net Weaver 7.4; SAP Net Weaver 7.5.

Issue: There is an error while adding an infoobject (X) to free characteristic panel in query designer. This object (X) is a Nav Attribute of other infoobject (Y). This Nav attribute has been added in Y master infoobject and thereafter Bex Query has been built on infoobject (Y). After adding this object in free characteristic, while checking the Bex Query, this error appears.

Even, if you create a new Bex query on this master data (info object Y) and if you do not drag that object in query panel, still it will show same error while checking the query in query designer.

 

RSRV testing on Queries which are built on this infoobject (Y) and get below error. After repairing this error in RSRV, it fails in next run.

RSRV testing for infoobject (Y) and infoobject (X) has passed successfully but query error persists.

Solution:

There are few steps to correct this error:

Before working on solution, please check if this object has correct settings in Bex Explorer selection, it has to be set as always ‘No Selection Restriction’, don’t set it as ‘Unique for Query’.

  1. Generate the Bex query in RSRT, if still getting same error occurs, then follow the next step.

 

2. Open the mast data object (Y) on which query has been built, in Eclipse and activate the object as per below screenshot, thereafter error will disappear in query designer.

 

Additional comments/information: This activity will directly affect the all queries, which have been built on this info object (Y). None of the queries has been executable in Bex Analyzer until this error gets resolved.

Why the problem occurs:

        1. Sometimes, due to changes in infoobject, backend queries were impacted and it showed an error.
        2. After making changes from Key to ‘Key and Text’, it might have set selection settings as Unique for query unfortunately.
        3. When back end infoobjects are inactive and throw this error.

Out of Scope:

  1. If you set a single filter value for that objet in Query, then error will disappear. However, this is not the solution as we cannot apply filter with single value, as it is a Key and we need multiple values.

 

2. You do not need to apply any SAP Note to correct this error.

 

Conclusion:

Whenever this error occurs, please check in backend if all master data objects are active and Bex query selection has not been set as ‘Unique for Query’ in infoobject level.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.