BIP Deskotop 11.1.1.6 (32-bit) with Office 2010 (32-bit) on Win 7 64-bit

10-11  Source: Network gathering  Views:2 

Advertisement
BIP Deskotop 11.1.1.6 (32-bit)
Office 2010 (32-bit)
Win 7 (64-bit)
The current certification matrix seems to say this is supported, however I am having the following problem:
1. I have an existing RTF template, with data template that works. I have run it to be sure, and can view output and verify.
2. If Iopen that RTF template in BIP Desktop, then remove a field, and then using the field browser ( or insert > field ) add that same field back, or a new one the report will not generate output.
Upload the RTF, and the process will finish with status warning, and it fails during post processing. I look at the Output Post Processor error. edit the RTF template with a text editor and see that instead of putting in a <?YOUR_FIELDNAME?> BIP Desktop has instead inserting something similar to the following: <?ref:xdo0001?>. The only solution I currently have is to manually change these tags, however for large BIP reports this is cumbersome, and unacceptable for a long term solution.
Is there a workaround? or reported bug? I couldn't find anything on MOS for this.
Here's the OPP log, you can see the error points to the "REF" element that was added by BIP:Desktop.
[5/29/12 1:26:38 PM] [8629358:RT6176186] Executing post-processing actions for request 6176186.
[5/29/12 1:26:38 PM] [8629358:RT6176186] Starting XML Publisher post-processing action.
[5/29/12 1:26:38 PM] [8629358:RT6176186]
Template code: XX123XML
Template app: MUTL
Language: en
Territory: US
Output type: RTF
[5/29/12 1:26:39 PM] [8629358:RT6176186] Output file was found but is zero sized - Deleted
[5/29/12 1:26:39 PM] [UNEXPECTED] [8629358:RT6176186] java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at oracle.apps.xdo.common.xml.XSLT10gR1.invokeNewXSLStylesheet(XSLT10gR1.java:611)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:239)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:182)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1044)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:997)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
     at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1665)
     at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:975)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5936)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3459)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
     at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:302)
     at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:176)
Caused by: oracle.xdo.parser.v2.XPathException: Namespace prefix 'ref' used but not declared.
     at oracle.xdo.parser.v2.XSLProcessor.reportException(XSLProcessor.java:806)
     at oracle.xdo.parser.v2.XSLProcessor.newXSLStylesheet(XSLProcessor.java:571)
     ... 17 more
Solution was to follow: Report Generation Fails Due to oracle.xdo.parser.v2.XPathException: Namespace prefix 'ref' used but not declared [ID 1337111.1]
Related articles