BI Publisher fails with either "invalid template name" or undeclared varuables

Question

Summary BI Publisher fails with either "invalid template name" or undeclared varuables Content Hi, My second Oracle Report conversion via OR2BIPConvAssist has created issues but at least has created something in the publisher. I am just evaluating BI as a potential successor to Oracle Reports. It isn't going to well! In the publisher (12C) if I click on the report line in Catalog I have two boxes "Default" and "Untitled". If I click on "default" it fails with: invalid template name.:.xpt If I click on "Untitled" I get and sql error pls-0201 p_from_date' must be declared ora-06550 Though this is defined in the data model. Any ideas? Many thanks, Steve

timdexter · Answer

Hi Steve

Apols, but I think it might be time to get some Oracle support help. Without the rdf Im limited in what I can suggest. Something is not configured or something in the OReport is tripping up the converter.

O Support can take the rdf and run it through the converter and get some help from development if needed.

Cheers

Tim

Steve Hiscock · Answer

Hi Tim,

Thanks so far.

Yes this is what I have after running the OR2BIPConvAssist.  I haven't changed anything.

What screen shots would you like?

This is the second Oracle Report I have tried.  The first fell at the first hurdle with a java error :

WARNING: java.lang.ClassCastException: oracle.xdo.dataengine.queryparser.QueryBuilder$SetOperation cannot be cast to java.lang.String

The converter isn't doing a good job at all.  Perhaps there is some additional configuring I need to

do (?).

Thanks,

Steve

timdexter · Answer

Hey Steve

Couple of points on the conversion tool.

1. Its pretty good at handling the data extraction side of the OReport. If you have report triggers, those get converted to PLSQL pkgs and need to be deployed to the DB (as you have prolly read.)

2. Its not so good on the layout side of the house. Nested frames in an OReport are the equiv of nested tables in MSWord. And Word is not good at nested tables. More often than not, start again with the layout. Its faster than picking apart the nested tables.

To you issues:

a. Default and Untitled Im guessing are reports that have been created by the migration assistant? Or did you deploy them yourself?

b. For the default error - Im guessing that the layout template did not get deployed with the report

c. For the Untitled - Thats a pure PLSQL error and the variable needs to be declared in the pkg. Its not enough to declare it iin the report definition.

To be able to help further some screen grabs and the reports themselves would help.

Finally, BIP is different to Oracle Reports but its definitely better IMHO. Im a little biased having been involved from the start but Im a former OReports developer and made sure that BIP was better :0)

Tim