Bex Query Variable error in Webi and Crystal for Enterprise

Question

Hi,
We just upgrade to BOBJ 4.1 SP2 and BW7.4 SP5
I am creating a webi report based on a BEx query. There is Variable on Period/Fiscal Year from BEX side(Mandatory prompt) when I try to create a Webi or Cyrstal for Enterprise report the below error pops up. Other Bex queries work correctly. Can it be the values in the variable the following values exist when execute from Bex i.e. 001.2012; Period 2013
Is the SAP Note : 1611185 relevant for 4.1 SP2
Error:
com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: Termination message sent
ABEND DBMAN (257): SQL Error: INTERNAL_ERROR
  MSGV1: INTERNAL_ERROR
Is this True for BOBj4.1 SP2?
http://scn.sap.com/thread/3362312
Selection range variables are not fully supported in Crystal Reports for Enterprise.
Message was edited by: Tienie Nothnagel

Answer 1

Henry Banks wrote:
> I know what you mean.  In BEx, it's automatic: the default values are pre-selected at runtime, based on user authorizations
>
> In WebI, user needs to do a 3-click workflow to select the authorized values from the prompt dialog. This can be broken down into 3 phases:
>
> (a) initialize prompt u2013 empty pane.
>  (b) refresh list of values,
>  (c) select response values.
Thanks Henry! I was looking for this confirmation that it is a limitation of Webi and I'm not missing something.
Henry Banks wrote:
> ---> make this BEx variable u2018mandatoryu2019 u2013 this will trigger an automatic refresh mechanism on the list of values, and show it to the user.  This will eliminate steps (a) & (b).
>
It is not possible to set Authorization variables as mandatory. They are set to "optional" and cannot be changed (BEx limitation).
Henry Banks wrote:
> Unfortunately, BEx and WebI are not like-for-like replacement tools. Not all u2018normalu2019 BW features integrate natively into BObj.
> So this will also have to be an excercise in positioning a new product to your onboarding users.  (i.e.  just click the button)
> Regards,
> H
I understand that. Thanks for your suggestion.