Xml Publisher And Reporting To Excel

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

2 comments

Comments 1 - 2 of 2 previous next Post a comment

Post a comment
Embed Video
Edit your comment Cancel

7 Favorites

Xml Publisher And Reporting To Excel - Presentation Transcript

  1. XML Publisher and Reporting to Excel Duncan Davies, Jay Jorgensen and Adam Clark Allinity
  2. Who are we? Duncan Davies - Technical Consultant (Allinity) Email: Duncan@Allinity.com Adam Clark - Technical Consultant (Allinity) Email: Adam@Allinity.com Jay Jorgensen - External Consultant Email: Jay@GlobalWalkabout.com
  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? XML Data 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. What’s good?
    • Single Toolset
    • Business users don’t need a techie to layout a report
    • Highly Flexible
    • Easier upgrade to Fusion
    • Quick and easy
  17. What’s 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 the rowset 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
    • Output onto Multiple Sheets
    • Complete control of individual cells
      • Formatting of individual rows/columns/cells
      • Formulas
    • Client specific Branding/Formatting
  21. Options
    • XMLP
    • SQRXLS
    • nVision
    • XSLT for XMLP
  22. The Solution
    • Application Package
      • Kept within PeopleSoft
      • Standard PeopleSoft APIs
      • Classes and Methods
  23. Benefits
    • Rapid development
      • Standard PeopleCode
      • Object oriented API
      • Simply pass a RowSet to the constructor
  24. Example
  25. Summary
    • Client Requirements
    • Flexibility
    • Rapid Development
  26. AEXLS
    • The Internals
  27. What Have We Done
    • Formatting – text, cell and sheet
    • Print and Page Settings
    • Formulas and Functions
    • Multiple sheets
    • Named Ranges
  28. What Can be Done
    • Short answer – everything but Macro’s and Passwords
    • For Example
      • Pivot Tables
      • Charts
      • Hyperlinks (drill-down like nVision)
      • Data Functions – filters, sorting etc
      • Smart Tags and Comments
  29. Components
    • Excel/XML
    • XMLDOC Object
    • Application Packages
  30. Excel/XML
    • Need to learn XML
    • Simple Cascade - Worksheet/Column/ Row/Cell
    • Styles used like CSS
    • Namespaces and Schemas
    • MS Schema’s of some use
  31. XMLDoc
    • PeopleSoft’s 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()
  32. 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
  33. Problems
    • Namespaces and XMLDoc
    • Other XMLDoc Issues
    • Performance
  34. 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)
  35. 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.
  36. Thanks for listening.
    • Does anyone have a Question?

+ DuncanDaviesDuncanDavies, 3 years ago

custom

12630 views, 7 favs, 3 embeds more stats

An Overview of XML Publisher, followed by a look at more

More info about this presentation

© All Rights Reserved

  • Total Views 12630
    • 12616 on SlideShare
    • 14 from embeds
  • Comments 2
  • Favorites 7
  • Downloads 579
Most viewed embeds
  • 11 views on http://www.allinity.com
  • 2 views on http://learningpeoplesoft-abode.blogspot.com
  • 1 views on http://idontwanttowrite.blogspot.com

more

All embeds
  • 11 views on http://www.allinity.com
  • 2 views on http://learningpeoplesoft-abode.blogspot.com
  • 1 views on http://idontwanttowrite.blogspot.com

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories