Oracle XML Publisher / BI Publisher
ā¢Download as PPS, PDFā¢
61 likesā¢53,152 views
This document outlines a course on reporting systems using Oracle BI Publisher. The course objectives are to explain BI Publisher concepts and uses, advantages of reporting with BI Publisher, and how to create, deploy, and maintain BI Publisher reports. The agenda covers an overview of BI Publisher, installing the desktop, creating reports using templates, formatting, and administering BI Publisher within Oracle E-Business Suite.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Oracle XML Publisher / BI Publisher
Similar to Oracle XML Publisher / BI Publisher (20)
More from Edi Yanto
More from Edi Yanto (14)
Recently uploaded
Recently uploaded (20)
Oracle XML Publisher / BI Publisher
- 1. Reporting System with BI Publisher Edi Yanto edi.y4nto@gmail.com Oracle Applications Technical Consultant
- 2. 2 Course Objectives After completing this course, you should be able to do the following: ā¢ Explain the basic concepts and uses of BI Publisher ā¢ Explain the advantages of reporting system with Oracle BI Publisher tool ā¢ Create and use an Rich Text Format (RTF) template ā¢ Deploy and maintain BI Publisher Reports in an E-Business Suite instance
- 3. 3 Course Agenda ā¢ Oracle BI Publisher Overview ā¢ Install Oracle BI Publisher Desktop ā¢ Creating Reports in Oracle E-Business Suite Using BIP ā Generate XML file using Concurrent Manager ā Creating RTF Report Templates ā Using the Design Helper Plug-in ā Creating Data Definition for the report ā Using Template Manager to upload the report ā Running BI Publisher Reports ā¢ Translation and Localization ā¢ Grouping and Subtotals ā¢ Adding Header and Footer Information ā¢ Date and Number Formatting
- 4. 4 Course Agenda (Con.) ā¢ Repeating Header With Resetting The Page Numbering For Each New Header ā¢ Adding Chart and Image ā¢ Using Conditional Formatting ā¢ Using Cross Tab Functionality ā¢ Adding Updateable Variables To The Template ā¢ BIP Security ā¢ Creating Report from Data Template ā¢ Administering BI Publisher in an Oracle E-Business Suite
- 5. 5 Oracle BI Publisher Overview ā¢ What is Oracle BI Publisher (BIP) ? ā¢ Why Oracle BI Publisher ? ā¢ Classic Report Issues ā¢ Oracle BI Publisher Usage ā¢ Designing using Oracle BI Publisher Desktop ā¢ Register and Submitting BI Publisher ā¢ Demo & Practice
- 6. 6 Oracle BI Publisher Oracle BI Publisher is a new Java-based product available with the technology stacks of EBS, PeopleSoft, Siebels, JD Edwards and BI Enterprise Edition (OBIEE). It provides users with: ā¢ A template-based, easy-to-use publishing solution ā¢ A tool to rapidly develop and maintain report formats
- 7. 7 Oracle BI Publisher Concept ā¢ Separate data / layout / translation Report output Data Logic Layout Translation BI Publisher XML EFT ļ¾Rapid Development ļ¾Greater Flexibility ļ¾Reduce Maintenance Cost
- 8. 8 ā¦ from Data to Destination ā¦
- 9. 9 Extract Once, Publish Many Times
- 10. 10 Oracle BI Publisher Architecture Delivery PDF Word Excel Moreā¦ XSL Data Server SQL XML Oracle Report Web Services Template XLIFF Translation XML Translation Catalogs Data Handler Template Manager Translation Handler XML EFT Email Printer Fax Repository e-Commerce
- 11. 11 Oracle BI Publisher Technology Open Standard Technologies ā¢ Pure Java ā¢ Pluggable data in XML ā¢ Output format in PDF, RTF, HTML and EXCEL ā¢ W3C XSL-FO implementation Added Value: ā Performance ā Security ā MLS and Extensions to FO ā¢ Support for Internet Printing Protocol, WebDAV, Internet Fax Protocol, and SMTP
- 12. 12 Performance and Scalability Stream-based Implementation: ā¢ Reduces memory footprint ā¢ Handles large XML input files ā¢ Is the fastest XSL-FO Implementation
- 14. 14 Financial Reports What Do You Want To Publish Today ?
- 16. 16 Invoices
- 18. 18 Sales Orders
- 20. 20 Tax Forms
- 21. 21 Electronic Payments EFT / EDI
- 22. 22 Or Maybeā¦. All Of Them One Solutions for All Your Business Documents
- 23. 23 Why Oracle BI Publisher ?
- 24. Why Oracle BI Publisher? ā¢ Reduce complexity ā¢ Reduces time to develop, test and deploy ā¢ Reduces total cost, including maintenance ā¢ Increase developer productivity ā¢ Enable flexible customizations ā¢ Follow Oracleās development standard ā¢ Enable ease of use
- 25. 25 Complex Reporting Environments ā¢ Highly skilled engineers required to maintain the 3rd party software EFT/EDI ā¢ Strong business requirements in reporting area ā¢ Have to rely on multiple reporting solutions ā¢ 3rd party software and many servers required to satisfy business requirements. servers ļ¾Costly ļ¾Complex Systems ļ¾Expensive Maintenance ļ¾Time Consuming ļ¾Labor Intensive
- 26. 26 Single Solution Environment ā¢ Utilizing Oracle BI Publisher ā¢ Apps Integrated Publishing Solutions ļ¾Meet Business Requirements ļ¾Remove Complexity ļ¾Reduce Maintenance Cost ļ¾Reduce Total Cost Checks Reports XML / EFT / EDI Labels Invoices Destinations
- 27. 27 Benefits to Stakeholders Business Consultant ā¢ Focus on business requirements ā¢ Uses familiar tools to prototype report (Excel*, Word or Acrobat) ā¢ Higher Productivity Development ā¢ Focus on data provisioning IT Consultant ā¢ Faster deployment ā¢ Report matches prototype ā¢ Reduced maintenance End User ā¢ Consistent user interface ā¢ Report in multiple formats ā¢ Language and locale options ā¢ Multiple delivery channels
- 28. 28 Classic Report Customization ā¢ 1 data set : 10 layouts : 30 languages >> 300 reports ā¢ Requires high skilled engineers for customization ļ¾High Maintenance Cost ļ¾High Customization Cost ļ¾Difficult Upgrade ļ¾Less Flexibility
- 29. 29 Classic Report Customization (Con.) Data logic Layout Translation Report file
- 30. 30 BI Publisher Customization ā¢ 1 data set : 10 layout templates : 30 translation files automatically generated using XLIFF ā¢ Business consultants use familiar desktop tools for layout customization Report Templates XML Data Report Output XSL XML EFT
- 31. 31 Benefits of BI Publisher ā¢ Meet Business Requirements ā¢ Flexibility ā¢ Reduce Complexity ā¢ Reduce Maintenance ā¢ Reduce Costs
- 32. 32 Oracle BI Publisher Usage Itās everywhereā¦
- 33. 38 Designing Using Oracle BI Publisher The report layout can be designed by familiar desktop application (familiar design tools) ā¢ Microsoft Word Oracle BI Publisher Desktop ā¢ Adobe Acrobat ā¢ XSL Editors ā¢ Microsoft Excel Oracle BI Publisher Analyzer for Excel P D F R T F Excel X S L
- 34. 39 Template Styles Available
- 35. 40 Designing the Layout The RTF layout can be designed using the Standard features in Word. ā¢ Select the size, font, and alignment of text ā¢ Insert bullets and numbering ā¢ Draw borders around paragraphs ā¢ Include a watermark ā¢ Include images (jpg, gif,) ā¢ Use table auto formatting features ā¢ Insert a header and footer
- 36. 41 Multiple Language and Font Support Multiple Language Support ā¢ 185 languages and 244 territories (ISO Standards) are supported ā¢ Easy to translate each template into 185 languages ā¢ Utilize RTF or XLIFF for translation Multiple Font Support ā¢ BI Publisher ships with full set of Unicode Fonts ā¢ Support for font mapping and font linking (MICR and Barcode fonts can be embedded and linked to the output.)
- 37. 42 Security BI Publisher allows the user to produce secure PDF output, with security levels covering the following ā¢ Read only / Editable ā¢ Copy Text ā¢ Printable ā¢ Password Protection
- 38. 43 Associating the XML Data Data Element: To create the data element we need to add the Forms toolbar.
- 39. 44 Text Form Field ā¢ Text Form Field is used to reference the XML Data.
- 40. 45 Grouping Data Note: Use the for-each@section to repeat the header information across pages of the output document. The field will be repeated if the line information runs across more than one page, the page numbering will also be reset. Re-grouping: <?for-each-group:BASE Group;Grouping Element?>
- 41. 46 Headers and Footers There are 2 ways to define headers and footers: ā¢ Native word headers ā¢ Header Template
- 42. 47 Conditional Formatting Conditional Format Statements: ā¢ if ā¢ if-then-else ā¢ choose-when-otherwise
- 43. 48 Variables Declaration and Assigning Value <?xdoxslt:set_variable($_XDOCTX,āvariable name', 0)?> Sets the value of variable_name to the current value plus the element amount xdoxslt:set_variable($_XDOCTX,āvariable name', xdoxslt:get_variable($_XDOCTX,āvariable name')+element name) Get Value <?xdoxslt:get_variable($_XDOCTX, āvariable name')?>
- 44. 49 Others Formatting Row/Column High Lighting <?if@row:position() mod 2=0?> <xsl:attribute name="background-colorā xdofo:ctx="incontext">green</xsl:attribute> <?end if?> Creation of Page Total Element <?add-page-total:TotalFieldName;'element'?> <?add-page-total:dt;āDEBIT'?> Displaying Page Total <?show-page-total:TotalFieldName;'number-format'?> <?show-page-total:dt;$#,##0.00; ($#,##0.00)ā?> Sorting <?sort:element name?> Page Breaks <?split-by-page-break:?> Last Page Only <?start@last-page:body?> <?end body?>
- 45. 50 Others Formatting (Con.) Conditional High Lighting with Text Decoration <xsl:attribute xdofo:ctx="block" name="font-weight">bold</xsl:attribute> Oracle Number Format Mask <?format-number:fieldname;ā999G999D99ā?> Oracle Date Format Mask <?format-date:fieldname;āMASKā?> Mask Output for US Locale ā SHORT 2/31/99 ā MEDIUM Dec 31, 1999 ā LONG Friday, December 31, 1999 ā SHORT_TIME 12/31/99 6:15 PM ā MEDIUM_TIME Dec 31, 1999 6:15 PM ā LONG_TIME Friday, December 31, 1999 6:15 PM ā SHORT_TIME_TZ 12/31/99 6:15 PM GMT ā MEDIUM_TIME_TZ Dec 31, 1999 6:15 PM GMT ā LONG_TIME_TZ Friday, December 31, 1999 6:15 PM GMT
- 46. 51 XPATH Notations Notation Meaning . Current Node .. Parent // All elements in the XML document / Descendants @ Attribute [ ] To Specify Conditions
- 47. 52 Extended SQL and XSL Functions Syntax: <?xdofx:expression?> Examples: <?xdofx:rpad(FIRST_NAME||LAST_NAME),30,'x')?> <?xdofx:decode('xxx','bbb','ccc','xxx','ddd')?> <?xdofx:Instr('abcabcabc','a',2)?> <?xdofx:upper(char)?>
- 48. 53 Register and Submitting Oracle BI Publisher Process Overview: ā Set up the XML Publisher Administrator responsibility. ā Set the E-Business Suite report to generate XML output. ā Register the E-Business Suite report as a Data Definition with XML Publisher. ā Design the template and Register the template in the Template Manager. ā Run the Standard program to obtain the XML data file. ā Run the XML Report Publisher request to merge the data with the template.
- 49. 54 XML Publisher Responsibility
- 50. 55 Define Data Logic
- 51. 56 Register Data Logic Set the output type for any Oracle Seeded Report program to XML Physical Report File Name Concurrent Program name Output Format : XML
- 53. 58 Register Data Logic as a Data Definition in XML Publisher Concurrent Program Short name (N): XML Publisher Administrator-> Data Definition-> Create Data Definition
- 54. 59 Data Definition Template File Register Layout as a Template in XML Publisher (N): XML Publisher Administrator-> Template-> Create Template
- 55. 60 Submitting the Concurrent Request ā¢ Run the concurrent program via SRS (Standard Request Submission) ā¢ Click Option Button ā¢ On the Option dialog box, choose desired template, language and output type that you want.
- 56. 61 Submit Registered Data Logic Program Concurrent Program Name Template Name
- 57. 62 Concurrent Program XML Output XML Tags
- 58. 63 Next Actions ā¢ Demo of Oracle BI Publisher features ā¢ Practice Oracle BI Publisher reporting tool
- 59. 64 Demo ā¢ Overview Template Builder / BI Publisher Desktop ā¢ Invoice ā¢ Localization and Translation ā¢ Chart and Cross Tab
- 60. 65 Summary ā¢ Oracle BI Publisher is a new, innovative reporting and output management solution that is designed to lower the total cost of ownership of reporting and document output management.
- 61. 66 References ā¢ http://www.oralce.com/technology/products/xml-publisher/index.html ā¢ http://www.oracle.com/technology/products/xml-publisher/ xmlpsamples.html ā¢ http://blogs.oracle.com/xmlpublisher/ ā¢ http://ediyanto83.wordpress.com ā¢ http://www.slideshare.net/ediyanto83 ā¢ http://w3schools.com/ ā¢ http://metalink.oracle.com
- 62. 67
Editor's Notes
- BI Publisher Concept BI Publisher breaks the three components apart and treats them separately at design time At runtime the three are brought back together by BI Publisher to generate the final formatted, translated output Results: More flexibility than the current model A single data definition can support multiple layouts Multiple translations can be applied at runtime to generate translated output Leads to a reduction in maintenance costs for all concerned
- BI Publisher is made up of the four modules: Data: Data engines are registered with the data handler Can be any XML source or any engine that generates XML such as Oracle Reports Template: Layout templates to be used for the final output are stored and managed in the Template Manager Templates are created using familiar desktop tools such as MS Word, MS Excel or Adobe Acrobat Translation: Manages the translation that is required at runtime Delivery Server: Takes the output document and delivers it to the printer, email, and etc
- Oracle BI Publisher has been built on open standard technologies. Pure Java ā the product is a pure java solution Pluggable data in XML ā the data source is XML Output formats in PDF, RTF, HTML, EXCEL ā standard output formats BI Publisher technology is based on an implementation of the W3C XSL-FO standard to transform XML data into an FO object; this contains both data and formatting information that can then be further transformed to an output format such as PDF. Added to the implementation are features to improve performance, increase security, support MLS and extensions to the FO standard to support more complex reporting objects. WebDAV ļ Web Distribution, Authoring, and Versioning
- Performance and Scalability The XSL-FO engine that has been developed is not only robust but also fast, this is vital. XML data by its nature generates large objects or files and these can cause serious memory issues during processing. BI Publisher has a stream based implementation that reduces this memory footprint allowing large XML input files to be processed.
- No single system can currently do all this, you need to invest in 3rd party software and often a dedicated server to achieve this. This leads to an increase in costs and very complex systems. Of course if you have all these extra servers and software on your system you will need skilled engineers to maintain them. Further cost to you and extremely labor intensive.
- To summarize, all parties win from report developers to the end user when using Oracle BI Publisher. End User ā The end user is presented with a richer report offering from the e-Business Suite. Reports in multiple formats with multiple delivery options are now available directly from the applications suite; the language and locale options have been improved and this all comes through a consistent user interface. Business Consultant ā traditionally the business consultant would gather the business requirements and then describe the report that was required in a document and pass this to the IT consultant for implementation. The business consultant now has a set of familiar desktop applications that can be used to design the report format itself, this will ensure the report will meet all the business requirements that are in scope and it will look exactly as the consultant has designed it. IT Consultant ā the IT consultant will now receive a document that is the actual report format as designed by the business consultant. The time to develop, deploy and test will be greatly reduced; the cost of on going maintenance will also be reduced. Development ā are now able to focus on generating XML data from the e-Business Suite schema to satisfy multiple requirements, now development is free from ā1 data definition : 1 report layoutā there is a move toward generating larger data engines that can satisfy a larger requirement set. This will provide end users with far greater choice and control over the content of the reports they want to see from the suite.
- Classic reporting approaches combine the data definition, the layout format and translation in a single source. This leads to large numbers of report files; a single data definition (query) could support several layouts but due to the nature of the report definition file the user has to create and maintain a separate report for each combination. Now add the required translation and the number of report definitions has become huge. Typically the tools used to create these reports are powerful but complex and require a high level of technical training to be used effectively. If a company takes a development delivered report and has to customize it the only option they have is to take a copy of that report definition, make the changes they require and then use it. If development upgrade the base report then any changes will need to be propagated through to the customized report. These three factors lead to an increase in maintenance and customization costs and an extremely difficult and complex upgrade.
- The classic approach to reporting is to combine all of the elements of a report into a single entity: Data definition Layout Translation Results: Report file is very unwieldy and causes problems due to its inflexibility If a report is required that has even a minor layout change a new report file must be created to support the new requirement even thou the data definition is exactly the same If another version of a report is required at runtime in a different language then a new report file must be created to support the new language This model leads to more time and expense in maintaining report files
- Oracle BI Publisher simplifies the whole customization process and combines this with reducing costs. The traditional approach of combining the data definition, format and translation in a single entity is thrown out in favor of breaking the three components apart. With the three pieces now separated the whole model is simplified. Data Definition - The data definition exists as a single entity, an Oracle Report, PL/SQL package, Service Bean, etc but it now just becomes an āXML Data Engineā that can service not only a reporting need but can fulfill other requirements e.g. B2B communication along with other reports. Report Templates ā The technology behind BI Publisher is a W3C standard, XSL-FO. There are many XSL editors currently in the market that can be used to create report formats. BI Publisher also allows the user to create layouts using Microsoft Word, Microsoft Excel and Adobe Acrobat, these familiar desktop tools make report template design and much simpler proposition for users and can be designed comfortably by business analysts rather than an IT specialist. Translation ā BI Publisher is able to extract the report boilerplate to an XLIFF format. These files can then be translated by 3rd party translation companies. At runtime the three components are brought together by BI Publisher to generate the required output.