• Word Properties <?ref:xdo000X?>


    BIP Deskotop 11.119.00.0 (32-bit)
    Office 2013 (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

    =============================================================

    have you checked backward comparability option without touching anything in the template and don't open the form fields without loadng the xml file.

    =============================================================

     

    Hi,
    Thanks for all the responses on this one. We are using Word 2010 which I think accounts for a lot of the problems we've been having in getting the plugin to work. We have it working now albeit by using a number of workarounds.
    The main step we've needed to take is that all of the fields in the report need to be edited via the word properties - Add help text option so that the default fields in the form field help text window beginning with 'ref' are replaced with the actual field names. So for example:
    <?ref:xdo0002?>
    Replaced with
    <?EMPLID?>
    Importantly the F and E fields which are at the start and end of all fields listed in a template that has repeating values need to be replaced as follows:
    F field at the beginning:
    <?ref:xdo0001?> replaced with <?for-each:row?>
    And
    E field at the end:
    <?ref:xdo000??> Replaced with <?end for-each?>
    This allows all of the values to be listed in a report table.
    By carrying out these steps we are able to use the word templates when running the BI publsher reports in Peoplesoft.
    Kind Regards,
    Neil

    =============================================================

    In options for BI Publisher - choose tab "Build" and radio button "Backward compatible" - then BIP will create your field names "10g style" as required by you...:-)
    BR Martin Z.

    =============================================================

     image

  • 相关阅读:
    Calling Convention的总结
    形参传递关键点
    linux input输入子系统分析《四》:input子系统整体流程全面分析
    22.Linux-块设备驱动之框架详细分析(详解)
    spring: 使用profiles选择数据源(结合嵌入式数据源EmbeddedDatabaseBuilder)
    spring: 使用嵌入式数据源 EmbeddedDatabaseBuilder
    jsp:jstl标签之控制流程
    jsp: jstl标签库
    jsp:tld标签
    spring boot: 组合注解与元注解
  • 原文地址:https://www.cnblogs.com/quanweiru/p/4932010.html
Copyright © 2020-2023  润新知