1

I have an existing report in AP non-withholding tax, now the report layout was created in report builder in paper layout, the report output was in PDF.

Now the user wants the output to be in Excel format, the report doesn't have template and data definition in XML publisher administrator,

So what I did is I generated a report from XML and made my own layout in BI publisher desktop, after which I made a template and data definition, uploaded my RTF file.

When I try to generate a report it is still the same output that I get. layout from report builder, even I uploaded my RTF file.

Could you please clarify on the behaviour

Sudipta Mondal
  • 2,550
  • 1
  • 19
  • 20
michael
  • 21
  • 6

3 Answers3

1

I am are using a BI Publisher Desktop with Large Form Fields enabled. For EBS this has to be disabled (backward compatible).

In Word, go to BI Publisher->Options->Build->Form Field Size->Backward Compatible.

To fix the layout: 1. Open the Field Browser. 2. Start at the top, select each form field (line). 3. In the Edit window add a character, delete it. Click Update. 4. Repeat for each form field. 5. Save and upload the layout.

TY all for the reply.

michael
  • 21
  • 6
0

You will need to change a few things to make this work.

  1. In concurrent program form, you will need to setup output type as XML

  2. To validate Pt # 1. you can run the concurrent program and check the XML from view diagnostics from the Concurrent request form. If the button is highlighted, click on it and check if XML opens correctly in the browser, if NO XML is generated the button will be disabled.

If you are not able to check Pt #2, then your RDF is not producing XML Output and for RTF reports, you require an XML output, so your problem is with RDF/Concurrent program setup.

  1. If in case, your setup in Concurrent Program form has output type as XML and you are still getting PDF output, you need to check the output type in your Template.
Sudipta Mondal
  • 2,550
  • 1
  • 19
  • 20
  • i already did the part#1, but the output shows the script of xml, and the output type in my template is excel. – michael Jun 25 '18 at 07:09
  • @michael Did you validate Pt # 2 ? Do you get an XML output or a PDF output ? – Sudipta Mondal Jun 25 '18 at 07:19
  • can u explain it to me briefly, how to validate pt#2? i didnt get the instruction in pt # 2 – michael Jun 25 '18 at 07:23
  • this is the output, - - - - 2017-01 2017-02 1007 AIR POWER INTERNATIONAL EXPRESS (PHILS.) INC. 000-104-562-0000
    Veronica De Leon St Paranaque
    73594.5571 73594.56 1     – michael Jun 25 '18 at 07:28
  • @michael - If you are getting the above XML output when you run the concurrent program, You have something incorrect with the Data Definition Setup. Make sure the `SHORT CODE` field for the DATA Definition is same as your concurrent program short code. – Sudipta Mondal Jun 25 '18 at 07:33
  • @michael - When you run the concurrent program via the Concurrent Requests form, after the request is complete, there is a button for *Diagnostics* adjacent to the *View Log* button. If you click on the Diagnostics button, you will see a new popup form with a button to View 'XML' – Sudipta Mondal Jun 25 '18 at 07:35
  • there the same, and im still getting the XML output. – michael Jun 25 '18 at 07:48
  • @michael - If you are getting the same, then your Data definition is not getting linked with your Concurrent Program. The short code for them needs to be the same. One easy way to verify it is, when you submit a concurrent request, you can check what is appearing in the `LAYOUT` form field towards the bottom part of the form. Your Template name/short code should be coming in that field – Sudipta Mondal Jun 25 '18 at 07:52
  • view xml is disabled – michael Jun 25 '18 at 07:52
  • now i have this kind of error,The XML page cannot be displayed Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later. – michael Jun 26 '18 at 02:18
  • @michael - I am guessing, the XML which is coming out of your RDF report is not a valid XML, only that is the reason, why the browser will not display the XML and give you an error message. – Sudipta Mondal Jun 26 '18 at 06:09
0

I see from your screenshots in the Oracle forum post, that the datasource code is mixed case whereas the conc short name is all uppercase, so maybe try with the datasource in all uppercase instead.

Then, also check the setup with the SQL here: https://www.enginatics.com/reports/xdo-publisher-datasources/ (take the SQL-text from the second tab of the excel example file, remove " from start and end and replace "" with ")

Or alternatively, use Blitz Report to generate Excel.

Andy Haack
  • 429
  • 3
  • 6