Register BI Publisher Report Template to EBS
After you have completed converting the Oracle Reports RDF file to BI Publisher Data Template and RTF Template with the conversion tool, the next step is to register such template files. You can do so by logging into the EBS web UI with BI Publisher Administrator responsibility and register them. After the registration you need to update the existing concurrent program to use the new Data Template file.
First, you need to register your Data Template.
- Login to EBS
- Choose XML Publisher Administrator responsibility
- Click Data Definition in the left box
- Click ‘Create Data Definition’ button to create a new Data Definition
- Input Data Definition Name
- Input Code
- Choose Application. (e.g. Receivables)
- Input Start Date
- Specify the XML data file as Preview Data. (Optional)
- Specify your Data Template file as Data Template
- Click Apply to save
Once your Data Template has been registered now you can register your RTF Template.
- Click Templates tab
- Click ‘Create Template’ button to create a new Template
- Input Template Name
- Input Template Code name
- Choose Application (e.g. Receivables)
- Choose Data Definition
You need to choose the Data Definition that you have created at the previous process step.
- Choose Template Type, in this case it’s ‘RTF’
- Specify Start Date
- Specify RTF Template file that you have developed
- Choose English as Language
- Check ‘Translatable’ checkbox
- Click ‘Apply’ button to save
Once you have completed the registration of both Data Template and RTF Template then you want to create a new concurrent program based on the original concurrent program, which is associated with the Oracle Reports base report, and associate it with the templates.
- Choose System Administrator responsibility
- Go to Concurrent/Program/Define
- Select the original Reports Concurrent program
- Click ‘Copy to’ to copy the original concurrent program
In a popup window,
- Type Program name
- Type Short Name (This must be identical to the Data Definition Code that you have registered in Template Manager.)
- Choose Application, e.g. Receivable (AR)
- Check both ‘include Incompatible Program’ and ‘include Parameters’
- Choose ‘XDODTEXE’ as Executable
This is XML Publisher Data Engine Java Concurrent program that takes Data Template and extract data based on the template information and generate XML file
- Choose XML as Output Format
Assign the new Concurrent Program to a Request Group
Now you need to assign the newly created concurrent program to a request group that your users have access to, otherwise the users can not find the new concurrent program to run.
- Go to Security/Responsibility/Request
- Select a Request Group which is assigned to your responsibility that you want to run the request with. (e.g. Receivables All for Receivables Manager)
- Add the new Concurrent Request program and Save
- Make sure the users’ responsibility has the Request Group
Now you want to test this report to see all the registration and configuration at the previous steps have been done appropriately.
- Go to Submit Request Window or select View/Request from the tool bar menu
- Choose the new Concurrent Request program
- Select parameter values if any.
- You should see the RTF Template you have registered in the Template Manager.
- Click Submit
Once the request is run with complete status successfully now you should be able to open the PDF report by clicking ‘View Output’. If the request has completed with an error click ‘View Log’ to find the detail problem.
After the ‘Oracle Reports Migration to BI Publisher in EBS Part 1, 2, and 3’, now you have 1) converted the original Oracle Reports base report to BI Publisher base report which consists of Data Template and RTF Template, 2) registered the converted template files with EBS, 3) created a new concurrent program by copying the original and associate it with the templates 4) validated the converted report.
This is a normal process of the reports conversion from Oracle Reports to BI Publisher for EBS. Of course, as discussed at the beginning, you can convert only the layout part of the report and keep using Oracle Reports as a data generation engine. In this case you need to register only the RTF Template and associate it with the original concurrent program through Data Definition.
Again, the most critical thing is not just the technical side of the conversion process, it’s more the business side. While administration and maintenance cost in IT departments will be reduced by converting to BI Publisher reporting architecture it’s important to note that there can be a huge value at the business side who will be the users and could see a lot of potential values with this new reporting architecture and this reports conversion initiative itself.
For example, by moving to BI Publisher reporting architecture now the users can use MS-Word to design the reports by themselves. With RTF Template the users can have images, charts, table of contents, URL hyper link, etc in their reports easily. Separation of the layout design piece from the data definition enables the users to make changes on the layout easier with less risk. BI Publisher’s reporting engine has better performance and scalability than Oracle Reports.
So not only delivering the x number of the reports being converted on time, but also it’s important to discuss how to meet the business requirements in today’s business condition and how the new reporting architecture can improve their business and set clear objectives to be shared through the conversion project phases. And such objectives should drive on what conversion option to be chosen and how to set the conversion plan and execute.
So that’s it for the reports migration (conversion) for EBS. I will start another reports conversion topic, ‘Actuate to BI Publisher conversion for Siebel’ from tomorrow, so stay tuned!