nVision

Developing Financial Reports Using PeopleSoft nVision - Introduction

What is nVision?

1. nVision is a reporting tool

2. Used mainly for financial reporting of ledger data in PeopleSoft's General Ledger module

3. Integration with MS Excel makes it popular with developers and end users

4. Requires minimal coding/programming

5. Easy and quick to develop reports

End users access PeopleSoft, including running nVision reports, through a web interface. PeopleSoft’s web interface is called the PIA (PeopleSoft Internet Architecture). But most of the development tools (PeopleTools), including nVision report development, require MS Windows thick client install.

There are two types of reports, also called layouts, in nVision:

• Matrix
• Tabular

Matrix layouts are the most commonly used and are discussed first. Both Matrix and Tabular nVision layouts have .XNV file extensions.

Both Matrix and Tabular layouts leverage existing General Ledger (GL) configuration. It is assumed that the readers have working knowledge of the GL module, therefore not all GL Configuration is discussed in detail in the book.

nVision reports are developed only on the thick client installation of PeopleSoft, but they can be run on both the thick client install and on the PIA (web). To run an nVision report from the web it must reside on the reporting server specified in the PeopleSoft configuration. But reports run from the thick client can reside in any location, including the local drive of a developer’s PC.  

You create a Report Request to run an nVision report. The Report Requests reside in your financial database. A typical Report Request creates one .XLS report output. But you can specify a Scope value on a Report Request to create multiple .XLSoutputs, one for each value in the Scope definition. For example, you can create Departmental Expense reports from one .XNV layout and one Report Request that uses a Scope of DEPTID values.

You can group multiple Report Requests into a Report Book. When you run a Report Book it executes the Report Requests by the sequence in the Report Book definition. Report Books can only be run on the web (PIA).

To restrict certain users from accessing particular reports or data, configure PeopleSoft Security and attach to the Report Requests.

Developing Financial Reports Using PeopleSoft nVision - PeopleTool Objects

PeopleTools Objects related to nVision are tabulated below:

Screen	Navigation	Menu	Component	Page	Records
Define Report Book	Reporting Tools > PS/nVision > Define Report Book	REPORT_BOOKS	IC_NVSBOOK	IC_NVSBOOK	PSNVSBOOK PSNVSBOOKREQUST
Register DrillDown Layout	Reporting Tools > PS/nVision > Register DrillDown Layout	REPORT_BOOKS	NVS_DRILL_LAYOUTS	IC_DRILL_LAYOUTS	NVSSERVER_SRCH NVSDRILL_LAYOUT
Define Report Request	Reporting Tools > PS/nVision > Define Report Request	REPORT_BOOKS	NVS_REPORT_REQUEST	NVS_REPORT_RQST NVS_REPORT_RQST3 NVS_REPORT_EMAIL_SBP NVS_REPORT_FILE_ SBP NVS_REPORT_BUCPY_SBP NVS_REPORT_WEB_SBP NVS_REPORT_TEMPL_SBP	NVS_REPORT NVS_REPORT_AUTH
Define Scope	Reporting Tools > PS/nVision > Define Scope	REPORT_BOOKS	NVS_SCOPE	NVS_SCOPE_DEFN	NVS_SCOPE NVS_SCOPE_FIELD NVS_SCOPE_VALUE

Developing Financial Reports Using PeopleSoft nVision - Using Virtual Ledgers

Using Virtual Ledgers

Virtual Ledgers provide an alternative view of ledger data that can be used for PS/nVision reporting purposes.  Virtual Ledgers are not setup and configured as part of the PeopleSoft General Ledger system, thus they cannot accept transactions and are used exclusively for PS/nVision reporting.

Example:  A company wants to restrict ledger reporting data by project to its Operations Management and Support. Other ledger users will have ledger reporting data secured by Business Unit. 

Solution:  You will develop a Virtual Ledger that is a view of the LOCAL ledger secured by PROJECT_ID.

#	Step	Step Description
1	Analyze data at project level	run SQL to list project-level data in the LEDGER table
2	Run baseline report	run P&L report off LOCALS ledger with OPER_ID VP1
3	Create project authorization table	create table  PROJECT_AUTH with  OPER_ID and PROJECT fields
4	Populate the project authorization table	Populate the PROJECT_AUTH table with valid projects for user VP1
5	Create the project reporting Virtual Ledger	save LEDGER record as LED_PROJACT_VW and modify with OPRID.  Create SQL to populate the view
6	Create Ledger Template	specify LED_PROJACT_VW as the reporting view record name
7	Create Detail Ledger	create Detail Ledger called NVSPROJECT
8	Create Ledger Group	create Ledger Group called PROJLOCAL
9	Update Ledgers For a Unit	add Detail Ledger PROJLOCAL and Calendar 01 to Business Unit US001
10	Open periods for the new Ledger Group	open periods from 1/1/2000 to 12/31/2010 for all Business Units with Ledger Group PROJLCOAL
11	Modify nVision layout	modify EXAMPLE3.XNV to pull from the PROJLOCAL ledger
12	Run nVision report	run Report Request EXAMPLE3.XNV under BU US001

Follow the steps below to build a Virtual Ledger and run an nVision report:

1. Analyze Data at Project Level

Run the following SQL in your PS Demo env to see what projects have data in the LEDGER table. For this example, we will secure the Virtual Ledger so only project 0000000151 is visible on nVision reports for OPERID VP1

SELECT A.BUSINESS_UNIT, A.ACCOUNT, A.LEDGER, A.DEPTID, A.OPERATING_UNIT, A.PROJECT_ID, A.CURRENCY_C, A.FISCAL_YEAR, A.ACCOUNTING_PERIOD, A.POSTED_TOTAL_AMT

  FROM PS_LEDGER A

  WHERE A.PROJECT_ID NOT LIKE ' '