Multi Select Issue in Crystal Reports on top of Infosets

[Former Member]

In my crystal report going against SAP Infoset I have a crystal parameter called customer. This parameter is string and allows multi select and custom values. When user inputs values for customer say "1" and "2" it always fetches data for customer "1". Even if I change the order like "2" , "1" it still fetches the data for customer "1". I then tried for bunch of other customer values each time it displays data only for lowest customer number.

In the report selection formula I have this

VBRK.KUNAG in {?customer}

I then tried hard coded the values in the report selection formula like VBRK.KUNAG in ["1","2"] still it fetches data for customer "1".

I see that in this thread below it was reported as bug. I still have the same issue. I am not sure if this got resolved.

I using crystal reports 2008,SP3 Fixpack 3.4

SAP Integration kit is 3.1 , SP3 , Fixpack 3.4

Any input or help is highly appreciated.

Thanks,

Shivkumar

[former_member235179]

Hi Shivkumar,

I checked the ADAPT01459397 in the SAP R+D system, it is listed as "Will not be fixed" against FP3.4.

It might be an idea to reraise this with SAP, referencing the previous ADAPT01459397, for further investigation.

I hope this is a very helpful answer to you.

Kind regards,

John

[Former Member]

Thanks John.

Here is what SAP had to say

When reporting from a specific InfoSet in Crystal Reports, and

selecting multiple values, the report only returns one value.

I have reproduce the issue in support. The issue only occurs when

reporting from specific tables and database fields.

I researched on the issue and found out it had been escalated to

Product Group in the past, and the investigation determined it is an

issue with the SAP function:

RSAQ_REMOTE_QUERY_CALL

Which is a component of SAP Netweaver, and not Crystal Reports. At

this point, the workaround are to either:

- Uncheck the report option: Use Indexes Or Server For Speed

or

- Instead of using InfoSet, connect directly to the SAP Tables using

the SAP Open SQL driver

I will be escalating this issue to Product Group, and will update you

on the status of the escalation.

[stephen_brown3]

Hi All, I also am interested in this as it is a problem I am facing as well.

Has there been any update?

Regards,

Stephen