Multivalue Error ? one user affect another user not affect !!!

[Former Member]

Hi all,

My user raised one issue. Details below:

He is getting multivalve error when he execute the report (Webi) using his credentials .but other user can execute the same report without error

As per my understanding itu2019s not possible because its data issue not authorization issue

Am I correct? If I wrong kindly advise me

Note:

*This report developed based on SAP universe

*Previously the same issue fixed at the time we created one dimension object (WBS Element Key) instead of detail object (L01 WBS Element Key)

Regards,

Tamil

[MariannevL · Accepted solution]

Hi Tamil,

The multivalue with SAP typically pops up when the master data of an infoobject is not unique for each key.

So the description or caption of the infoobject has homonyms (two different keys can have the same description).

If you have the keyfigures/measures defined as database delegated you will get this multivalue because SAP cannot calculate it on the combined level.

So authorisation might have impact if one user can see the two (or more) keys and the other user does not.

Two ways to solve this.

1) set the aggregation method of the object to sum (on the advanced tab).

This allows WebI to sum the values pulled back on the two different key values.

2) use the key as the master/dimension object and the caption/description as the detail.

Hope this helps,

Marianne

And on your note, any of the infoobjects can cause this behavior.

So solving it for one does not mean it doesn't happen anymore.

[Former Member · Accepted solution]

Hi Marianne,

Thank you for quick response ,

kindly advise ,below 2 points where we have to set (Uni/ WEBi / BW )?

1) set the aggregation method of the object to sum (on the advanced tab).

This allows WebI to sum the values pulled back on the two different key values.

2) use the key as the master/dimension object and the caption/description as the detail

Environment : BOXI3.0

Note: in this report "L01 WBS Element Key" column only having this problems

Regards,

Tamil

Edited by: Rajesh Kumar Thoppe on Oct 14, 2010 7:19 AM

[MariannevL · Accepted solution]

Even if the object is called key, the master data for it still can be non-unique.

Look in the xml of the object itself.

If it ends with [LEVEL01] then its non specific and will pull back master data if there.

To point specifically to the key, you could use [LEVEL01].[NAME]

or if the key is there as an attribute (generated as green object normally), you can use that.

Hope this helps,

Marianne