cancel
Showing results for 
Search instead for 
Did you mean: 

Problem when setting data source location for a SQL Command in CR Report

Former Member
0 Kudos

Hi all

I need to change a CR 2011 Report which is stored in our DEV environment (the report is up and running in our PROD environment). We have started using SAP CR for Enterprise (version 14.1.6.1702), Build: 2013 Support Pack 6, so when I open the report from the DEV environment, and try so save it locally, I get the following message

After that, I refresh the report and get the following error:

After that, I choose the Edit Data Source option and got the following message

And after that, I get the next message

This report is based on 2 Oracle SPs and a series simple SQL Commands (Oracle DB version is 11g)

I choose the Click here to verify the datasource to fix this error link and it took me to the following message:

Then I go ahead and replicate one of the SQL Commands used in this report, so that I can remap the original SQL Command. I created a new connection which has the following Properties:

Which is pretty much the same as the original connection:

However, when I try to click on the OK button , while creating the new SQL Command, it doesn't get saved. I got no error, though. But, since the new SQL Command is not saved, I cannot proceed and set the datasource location for this Command.

I was wondering if this behavior has something to do with the use of Parameters within the SQL Command. Since these Parameters are already in the report, I suppose I should not create them (by using the Create button)

I was able to set the datasource location for the 2 SPs the report uses, it was pretty straight forward but I'm stuck with the SQL Commands

Any advise will be greatly appreciated

Accepted Solutions (0)

Answers (2)

Answers (2)

DellSC
Active Contributor
0 Kudos

Parameters that are created in the report don't have the same internal properties as the ones created in the Command editor. In order to use a parameter in a command, the parameters MUST be created in the Command Editor and NOT in the report. If the two Commands use the same parameters, give them the exact same name(s) for each Command. They'll then be available in the Field Explorer in the report so that you can modify them to set additional properties, but they must have been created in each command first.

-Dell

0 Kudos

Hi Gabriel,

You will need to create the parameters being used in the Commands.

You can create those commands under the "Parameter list" pane on the right side in the "Add Command Table option" window.

Note: The names of those parameters should be the same as that used in the parameter.

Regards,
Pranav Deshmukh