I'm thinking this must be a known issue, but I can't seem to locate any information relating to it. Hence the question 
I'm using Crystal Reports 2008 designer (it was at service pack 2 but i've taken it up to sp 7 now and still get the same behaviour) and trying to connect a new report to a data-source (an Oracle stored procedure) via a native Oracle connection.
It finds and requests the parameters well enough, but upon pressing ok on the parameters screen I get:
Enabling the crystal tracing shows me that the SYS.ALL_OBJECTS view is being queried to determine the type of the data-source.
Looking at the returned results of the query again ALL_OBJECTS for both 11G and 12C database instances shows that the results are returned in a different order (two rows come back for a package-based data source, one containing a type of PACKAGE BODY and one a type of PACKAGE.
It looks like Crystal is looking for one of these types in the (probably) first row returned and now doesn't get what it expects, thereafter assuming the data source is a table.
I can sort out the problem if I compile a order by clause into our test database sys.all_objects view that makes it return the data in the same order as the 11G database.
Can any tell me if this is a known bug? As mentioned - i can't find anything to say it is. If it is known then is there a patch available or in the pipeline.
Any help you could give would be much appreciated.
Thanks,
Stephen