Error using CR 11.5 with dynamic cascading prompts and SAP Integr.Kit XI R2

[former_member142702]

Hi,

we are using the SAP Integration Kit XI R2 (patched up to FP4.3) in order to report SAP BW data (BW 3.5) in Crystal Reports 11.5 (SP 4). In order to access the stored BEx Queries we use either the SAP BW Query or the SAP BW MDX Query Driver (_we DO NOT use any universes_). Everything seems to work fine ex cept when we want to use dynamic cascading LOVs within CR. For example when a user runs a report she/he should select first a customer group (0CUST_GROUP prompt) and then the customer (0DEBITOR). Defining the cascading prompts with dynamic LOVs is no problem in CR and when the report runs (either in CR Designer or in InfoView) both prompts appear. Still when we do a selection for the first prompt (0CUST_GROUP) we get a 0x8004380D error with the text message stating that the system is not able to retrieve the LOV data (I guess for the 0DEBITOR prompt). Please note that we do not get a corba error and no firewalls are activated. We checked the trace files of the page server and found out that there was an error calling the createRowsetCursor function within enginekernel.cpp.

Any hints on our case will be mostly appreciated. We have the feeling that we are hitting a bug here but maybe we are overseeing something.

Cheers

Stratos

PS: Please note that if we access directly the ODS Object (SAP ODS driver) the dynamic cascading prompts on exactly the same InfoObject (or better their keys in the ODS) work without a problem.

[roland_hoeller2 · Accepted solution]

Dear Stratos

Dynamic prompts in Crystal Reports are not supported with SAP datasources.

Roland

[former_member142702 · Accepted solution]

Hi Roland,

thank you very much for your answer. How about defining cascading LOVs in Universes having an SAP source. Is this supported in XI R2 SAP Int.Kit and CR 11.5?

Regards,

Stratos

[roland_hoeller2 · Accepted solution]

Hi Stratos

You can define LOV's in universes but unfortunately you can not use universes based on SAP in Crystal Reports.

You can define parameters in the Bex query which are passed on to Crystal Reports, so you don't need to define them in the Business Objects tools. Please have a look at the SAP Integration Kit user's guide

Roland