cancel
Showing results for 
Search instead for 
Did you mean: 

Inconsistent query behavior

Former Member
0 Kudos

Dear All,

A good day to all.

I would like to know your ideas/comments regarding a particular scenario I am currently facing.

The scenario is that query results behaves in such a way that a keyfigure sometimes shows its values and sometimes not, with value or blank.. We are currently running on SAP BW3.5 and SAPGui 6.2. An example would be VOLUME (GR quantity). By the way, these queries are ran using a multiprovider.

I am using an ID which has almost full authorizations (good enough to execute these queries).

The weird thing about this is that this behavior is inconsistent...

I have tried to search for some OSS notes about this but have not found any match for this case..

Maybe someone could give me some thoughts regarding this situation on things I should further check or should have done to avoid this.

Thanks a lot..

- Arnold -

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Arnold,

Are you executing it based on same selections each time?

Is it a restricted key figure? Are there any variables used?

Whenver there is a blank record seen, you can actually check the selections, the parameters, and try to find out if there are records satisfying these in the infoprovider.

Remember, multiprovider will give u a union output and not a join.

Thanks,

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Arnold,

You should be able to run listcube on the multiprovider, this way you can apply the restriction and determine whether the issue is in the query or the multiprovider.

Hope this helps,

Carolyn

Former Member
0 Kudos

Try listcube transaction and check same scenario as your query and compare results. If you get data in listcube you should get data in your query.

Regards,

Former Member
0 Kudos

Dear Aby,

Yes, we are dealing with restricted keyfigures.

Thanks..

Dear BJP,

Thanks for the input, but there is 1 selection criteria that is mandatory in our query but is not contained in the affected InfoCube. The affected InfoCube data is linked via a different set of characteristics from other InfoProviders..

Thanks again to all..

- Arnold -