370 likes | 745 Views
nVision Deep Dive. IntroductionTom Achor, CPA.CITPFinance software consultant in PortlandCPA since 1991Began consulting practice in 1994PeopleSoft Financials specialist since 1998Wrote and taught custom PeopleSoft reporting classes for Clackamas County, San Mateo Transit, Countrywide, Benton
E N D
1. nVision Deep Dive Oracle PeopleSoft
NWRUG Meeting
Fall 2008
2. nVision Deep Dive Introduction
Tom Achor, CPA.CITP
Finance software consultant in Portland
CPA since 1991
Began consulting practice in 1994
PeopleSoft Financials specialist since 1998
Wrote and taught custom PeopleSoft reporting classes for Clackamas County, San Mateo Transit, Countrywide, Benton PUD
Other PeopleSoft clients have included Great Western Malting, Kmart, Western Wireless, Portland Public Schools
3. nVision Deep Dive How deep is deep?
Different user experience levels
Different environments
Different tools versions
Different reporting needs
About 80 minutes...
4. nVision Deep Dive With apologies to Andy Warhol:
5. nVision Deep Dive Assume basic knowledge of nVision app, Trees, & TimeSpans
Our Agenda
Best Practices for Development
Tips & Tricks
Lots of Sharing
6. nVision Best Practices Use Tree Manager Consistently
Create Layout Templates
Build Proof Reports
External documentation
7. nVision Best Practices Using Tree Manager
Trees can provide controlled structure
Use trees that require All Detail Values
Do not Allow Duplicate Detail Values Two things nVision handles very well: PeopleSoft Trees and TimeSpans
Good because these are also the basis for allocations and/or combo editsTwo things nVision handles very well: PeopleSoft Trees and TimeSpans
Good because these are also the basis for allocations and/or combo edits
8. nVision Best Practices Using Tree Manager, continued
Use only Tree nodes and no detail values in nVision layouts
Use only one Tree for each ChartField in any given layout Two things nVision handles very well: PeopleSoft Trees and TimeSpans
Good because these are also the basis for allocations and/or combo editsTwo things nVision handles very well: PeopleSoft Trees and TimeSpans
Good because these are also the basis for allocations and/or combo edits
9. nVision Best Practices Make a Layout Template
A table of all Variables you might use
Named ranges in the Variables
Standard headers
Print formatting
10. Row Sets and Column Sets Often multiple reports use the same columns with different row requirements
Many reports may use the same rows, but with different columns
Save and recombine proven row and column layouts to speed development
Avoid using cell-based criteria Go from here to Layout Template fileGo from here to Layout Template file
11. Template Layout Create in out-of-view area
Put in all the nVision Variables you might want and label them
Name the cell for each Variable using
Insert> Names> Create
12. nVision Best Practices Build one or more Proof Reports
Like a Trial Balance but built on Trees
Include every Tree Node, nPloded to all levels
Rows built on Account
Columns by Department or Business Unit, TimeSpans
13. nVision Proof Report One for each Tree combination used
Rows based on Account Tree
Columns based on Deptid, Business Unit, Fund, etc.
Use Top-level nodes
All-level nPlosion Will incorporate some other tricks in building the proof reportWill incorporate some other tricks in building the proof report
14. Proof Report - Select Account Nodes
15. Proof Report - Add nPlosion
16. Proof Report: adding rows
17. Proof Report -Account rows
18. Selecting a Tree
19. Selecting a Tree
20. Selecting a Tree
21. Selecting a Tree
22. Selecting a Tree
23. Effective Dating and nVision Layout Effective Date
24. Back to the Proof Report Cut from here to report layoutCut from here to report layout
25. Troubleshooting Tricks Copy troublesome row and column to a separate layout file
Set nPlosion on the criteria
Try different scopes on report
26. Troubleshooting Tricks Use Show Report SQL
Copy SQL statements into Word to view all at once
27. nVision Tips & Tricks TimeSpans
Dates v. Periods
Quarterly Reporting
Relative and Absolute Timespans
28. Dates v. Accounting Periods
29. Dates v. Accounting Periods Report Request As of Date (ASD) of Aug 15:
Period End Date (PED) of August 31
Real As of Date is PED because Ledgers cant distinguish days in the month.
30. TimeSpans and nVision: YTD YTD has only a fixed start period
Other parameters are relative to AS OF DATE
31. TimeSpans and nVision:QTR3 QTR3 TimeSpan has Absolute beginning and ending periods
32. Comparing Timespans
33. Quarter to Date TimeSpan QTD has Absolute Start Period
Relative End Period
34. Comparing Timespans
35. Working with QTD In out of view area, set up 4 QTD columns
Use OFFSET formula in visible part of report to pick up correct Quarter
Example: =OFFSET(U10,0,QTR,1)
36. Why nVision? Makes the best use of PeopleSoft trees
Employs Effective Dating and TimeSpans
Integrated tightly with PeopleSoft Ledgers
Can integrate PS/Query
Drillable spreadsheets make accountants happy
37. nVision Discussion
www.achorconsulting.com
tom@achorconsulting.com
(503) 504-0507