XML Publisher supports two basic Templates types: Rich text format (RTF) and Portable document file format (PDF). At runtime, XML Publisher converts RTF template to XSL-FO, Therefore XSL-FO is also supported as a template type.
XML Publisher’s Template Builder for Word
RTF templates can be created in Microsoft Word. Using a combination of native Microsoft Word features and XML Publisher command syntax you can create a report template that is ready to accept XML data from your system.
RTF templates can generate the following output types:
RTF Design Tool
XML Publisher provides a plug-in for Microsoft Word to facilitate the design of RTF templates. It automates many tasks and provides preview capabilities. The desktop installation also includes samples and tutorials to get you started. The following figure shows the Template Builder for Word.
eText Templates
An eText template is a specialized type of RTF template used expressly for the generation of text output for Electronic Funds Transfer (EFT) and Electronic Data Interchange (EDI) transactions. To achieve the specialized layout, XML Publisher uses tables to define the position, length, and value of fields, as well as data manipulation commands. At runtime XML Publisher constructs the output file according to the setup commands and layout specifications in the tables of the RTF template file.
PDF Templates
PDF templates are designed using Adobe Acrobat. You can use a PDF file from any source, including downloaded predefined forms (such as government forms). Using Acrobat’s form fields, map your data source element names to the PDF fields where you want the data to appear. PDF templates are less flexible than RTF templates, but are more appropriate for creating form-like reports, such as invoices or purchase orders.
Translation Support
For RTF templates that you want available in different languages, XML Publisher provides the capability to extract the translatable strings from the template and export them to an industry-standard XLIFF file. The XLIFF file can then be translated in-house or shipped to a localization provider. You create one XLIFF file for each language and territory combination (locale) desired. The translated XLIFF files can then be loaded back to your system and associated with the original template file. At runtime, XML Publisher applies the template and translation appropriate for the user’s selected locale.
XML Essentials :
XML stands for eXtensible Markup Language. XML was designed to transport and store data, with focus on what data is.
- XML files are composed of “elements”. An element is used to describe or contain a piece of information.
- Elements consist of two tags: an “opening tag” and a “closing tag”. Opening tags appear as text contained between the two angle brackets (). Closing tags also appear within angle brackets, but they have a forward slash (/) just before the tag name.
- The data between the tags (text and/or numeric) is the “value” of the element.
<AddressNumber_ID4> 903066 <AddressNumber_ID4>
(Opening tag) (Element value) (Closing tag)
Knowledge of XML is not a prerequisite for being able to successfully create reports in BI Publisher; however, familiarity with XML will help with the more intricate reports that you create. If you interested in knowing more about XML,then can refer to a site which gives detailed info.
Link : http://www.w3schools.com/xml/ Understanding the XML Output/Source Code :
Some of the components that should consider when review XML outputs are:
- Section tags.
- Item tags.
- Special characters.
- Formatted numbers.
- Page headers and page footers.
- Level break sections.
- Conditional sections.
- Child sections.
- Report properties.
Section Tags
Section tags are determined by the name that is specified in Oracle’s JD Edwards EnterpriseOne Report Design Aid (RDA). The name that you see in the XML file is the same as the name found in the Description field of the Section Properties form.
Because multiple sections in an RDA report template can be named the same, the section tag in the XML file is appended with a section ID. The section ID is assigned by RDA to ensure that each report section is unique. The section ID is retrieved from the report specifications and cannot be modified.
This is an example of the sections that are included in the XML output for the address book report task covered in this guide:
<Page_Header_S1>
<Address_Book-One_Line_Report_S2>
S1, the page header, is the first report section from the RDA report template. S2, the detail section, is the second report section included in the RDA report template. Address Book – One Line Report is the name of the detail section as defined in RDA. Ten records are included in this report as indicated by the ten S2 lines.
Item Tags
Item tags that you see in the XML file are determined by the data dictionary name of the fields used in the RDA report template. An exception to this rule is that if the data dictionary name has been overridden in RDA, then the override is used as the item tag.
Because multiple data items in an RDA report template can be named the same, the item tag in the XML file is appended with an object ID. The object ID is assigned by RDA to ensure that each report object is unique. The object ID is retrieved from the report specifications and cannot be modified.
This is an example of an individual section included in the XML output.
<A_P_Detail_Reports_S1> {This is the Business View Name used in the report}
<AddressNumber_ID4>903066</AddressNumber_ID4>
<AmountGross_ID6>0.00</AmountGross_ID6>
</A_P_Detail_Reports_S1>
- <A_P_Detail_Reports_S1>
<AddressNumber_ID4>903066</AddressNumber_ID4>
<AmountGross_ID6>42800.00</AmountGross_ID6>
</A_P_Detail_Reports_S1>
- <A_P_Detail_Reports_S1>
<AddressNumber_ID4>903066</AddressNumber_ID4>
<AmountGross_ID6>-1080.00</AmountGross_ID6>
</A_P_Detail_Reports_S1>
When the node of an S1 section is expanded, you can view the item tags of the individual record. Each piece of data is enclosed within descriptive item tags that include the object ID.
Special Characters
Many special characters that are used in RDA and included in EnterpriseOne data are replaced in the XMLPOSA interface output. For example:
“>” is replaced with “>”.
’&’ is replaced with “&”.
Apostrophes are replaced with “&apos”.
Quotes are replaced with “"”.
Other special characters that are prohibited, as defined in the XML 1.0 specifications, are replaced with an underscore.
Formatted Numbers
Numbers are formatted in the Oracle XML Publisher output using JAVA BigDecimal String format. This formatting consists of an optional sign (“–”) followed by a sequence of decimal digits. These digits can be followed by a fraction and additionally by an exponent, for example, –123456.3455e-3.
Page Headers and Page Footers
Information that is contained in page headers and page footers of RDA reports is grouped together at the top of the XML file. This ensures that the headers and footers do not break up the report data. Design your reports in RDA without including page headers and page footers. You should design the page headers and page footers in the XML template.
This is an example of the page header that is included in the XML output for the address book report task covered in this guide:
<PageHeaders>
- <Page_Header_S1>
<Company_Name_ID10>JD Edwards, Inc.</Company_Name_ID10>
<Report_Name_ID11>One Line Per Address</Report_Name_ID11>
</Page_Header_S1>
</PageHeaders>
Level Break Sections
Level break sections are used in RDA to group large amounts of data into manageable groups. Level break headers typically display a descriptive heading for the group while the level break footer typically displays an aggregate. These level break sections appear in the XML file as parents of the section on which they were created.
Conditional Sections
Conditional sections appear in the XML file at the root level. They do not appear as children of the section from which they are called.
Child Sections
Child sections appear in the XML file as children of the section from which they are called.
Report Properties
The following report properties are included in the XML file for auditing and informational purposes:
• Machine key
• Environment
• Role
• User
• Hostname
• OneWorld release //This is the JD Edwards EnterpriseOne application release.
• Report time
• Reportdate
• Company name
• Language
This is an example of the report properties that are included in the XML output for the address book report .
<Properties>
<Title>One Line Per Address</Title>
<Machine>DENSNBX01</Machine>
<Host>DENSNBX01</Host>
<Environment>STGAIMGS1</Environment>
<User>JDE</User>
<Role>*ALL</Role>
<Language>EN<Language />
<Company>JD Edwards, Inc.</Company>
<OneWorldRelease>E90</OneWorldRelease>
<Date>2006/4/27</Date>
<Time>8:41:43</Time>
</Properties>
