This chapter contains the following topics:
In JD Edwards EnterpriseOne Report Design Aid (RDA), you create reports and define specific printing properties to affect the report output. The report developer creates reports from the Microsoft Windows client. The batch engine can process reports on various servers or on the workstation.
After development is complete, the reports and associated batch versions are checked in and advanced through the development cycle. The system administrator then builds a package and deploys the reports and batch versions to the enterprise server. The reports and batch versions are generated to HTML so that they can be run from the web client.
Report output from the Microsoft Windows client can be in these formats:
View the report in Adobe Reader.
Comma separated values (CSV)
Export the report to a CSV spreadsheet application.
Output stream access (OSA)
Export the report to a third-party product using OSA interfaces.
Printed copy
Send the report to a printer.
BI Publisher Report
The BI Publisher report can be a PDF, RTF, XLS, Power Point, etext, XML, and so on.
After report processing is complete, output management handles the generation and output of the report.
From the web client, the batch engine processes reports on various servers. Report output from the web client can be in these formats:
CSV
OSA
Printed copy
BI Publisher Report
The BI Publisher report can be a PDF, RTF, XLS, Power Point, etext, XML, and so on.
Viewing the report on screen is not an option at runtime from the web client. However, once the report has been processed, you can view the report online using options on the Row menu.
Output management refers to managing the different output options available for viewing a report. You can view reports in different file types, send them to different printers, and create output in different forms or paper types. JD Edwards EnterpriseOne accommodates simple output processes such as viewing the PDF of a report online or sending it to a network printer. You can also use more complex processes such as defining versions to print to different printers across the country.
Some output options are defined in initialization files. For the Microsoft Windows client, the jde.ini is read at runtime by the Microsoft Windows client. For the web client, the jas.ini is read at runtime by the HTML (JAS) server.