Top Banner

Click here to load reader

Xml Publisher And Reporting To Excel

Nov 03, 2014

ReportDownload

Technology

An Overview of XML Publisher, followed by a look at how we delivered an improved Excel reporting solution for a client.

  • 1. XML Publisherand Reporting to Excel Duncan Davies, Jay Jorgensen and Adam Clark Allinity

2. Who are we? Duncan Davies - Technical Consultant (Allinity) Email: [email protected] Adam Clark - Technical Consultant (Allinity) Email: [email protected] Jay Jorgensen - External Consultant Email: [email protected] 3. What are we covering today?

  • XML Publisher- Duncan
  • Reporting to Excel Overview- Adam
  • Reporting to Excel Deep-Dive- Jay
  • Questions

4. What is XML Publisher?

  • Publisher is the only Reporting Platform for Fusion Apps

5. How does it work? XMLData Source Technical Task Template Layout Business Task Report Output XML Publisher Engine 6. Step 1

  • Create an App Engine to supply:
  • XML Sample Data File
  • XSD Schema File

7. Step 1 Code Populate Rowset 8. Step 1 Code Output Files 9. Step 2 Create an RTF template in Word using the XML Sample data file. 10. Step 3

  • Within PeopleSoft, create:
  • Data Source Defn
  • Report Defn
  • Process Defn

11. Step 3 Data Source Definition 12. Step 3 Report Definition 13. Step 4 Update your App Engine to output full data, then run it. 14. Step 4 Code Code Changes 15. Advanced Use

  • Bursting
  • Content Library
  • Translations

16. Whats good?

  • Single Toolset
  • Business users dont need a techie to layout a report
  • Highly Flexible
  • Easier upgrade to Fusion
  • Quick and easy

17. Whats not good?

  • XML/XSL knowledge needed for complex reports
  • Excel output very basic
  • No update until 2008 (Tools 8.50)
  • Need to use Report Mgr

18. What other tips can we give?

  • Make sure all rowset levels are filled in sample data.
  • RTFs not shown in Process Monitor, so set up Report Manager.
  • Limit the size of therowset for sample data.
  • Sort data in Code

19. AEXLS Overview 20. Why?

  • Client required a reporting solution
    • Output to Microsoft Excel
    • Must be a PeopleTools solution

21.

  • Output onto Multiple Sheets
  • Complete control of individual cells
    • Formatting of individual rows/columns/cells
    • Formulas
  • Client specific Branding/Formatting

22. Options

  • XMLP
  • SQRXLS
  • nVision
  • XSLT for XMLP

23. The Solution

  • Application Package
    • Kept within PeopleSoft
    • Standard PeopleSoft APIs
    • Classes and Methods

24. Benefits

  • Rapid development
    • Standard PeopleCode
    • Object oriented API
    • Simply pass a RowSet to the constructor

25. Example 26. Summary

  • Client Requirements
  • Flexibility
  • Rapid Development

27. AEXLS

  • The Internals

28. What Have We Done

  • Formatting text, celland sheet
  • Print and Page Settings
  • Formulas and Functions
  • Multiple sheets
  • Named Ranges

29. What Can be Done

  • Short answer everything but Macros and Passwords
  • For Example
    • Pivot Tables
    • Charts
    • Hyperlinks (drill-down like nVision)
    • Data Functions filters, sorting etc
    • Smart Tags and Comments

30. Components

  • Excel/XML
  • XMLDOC Object
  • Application Packages

31. Excel/XML

  • Need to learn XML
  • Simple Cascade - Worksheet/Column/ Row/Cell
  • Styles used like CSS
  • Namespaces and Schemas
  • MS Schemas of some use

32. XMLDoc

  • PeopleSofts XML Parser
  • Provides random access to the xml document Like a Database
  • Based on W3C standards Uses XPath
  • XPath is like a directory structure
  • Examples
  • Get a Sheet
    • Findnode(WorkbookWorksheet
    • [@Name=Sheet1] )
  • Get a Cell
    • Findnode(WorkbookWorksheet
    • [@Name=Sheet1]RowCell
    • [@Index=4]DataText()

33. App Packages

  • Object Oriented Approach Classes
  • Makes things more complex but so much faster/easier to maintain.
  • Model your classes on the excel objects sheets, cells etc
  • Quicker debugging

34. Problems

  • Namespaces and XMLDoc
  • Other XMLDoc Issues
  • Performance

35. Tips

  • Plan your object model first
  • Remove namespaces and add them in by string manipulation after XMLDoc is finished
  • Consider generating large chunks of data by other methods (e.g. SQL)
  • Leverage PeopleSoft Metadata (e.g. Field labels, translate and prompts)
  • Apply a template (like the report class)

36. Finish

  • Time estimates
    • 2 man months for the Excel generator
    • 1 man month for the template overlay
    • Much of this is learning curve
  • Time is easily recouped in developing reports etc that use it.

37. Thanks for listening.

  • Does anyone have a Question?