RP Nvision Guide

PS/nVision
Configuration
&
Troubleshooting Tips
11/12/2009 PS/nVision Reporting Tool
T I TLE OF P AP E R PS/nVision and Troubleshooting Tips

11/12/2009
Reference Number: PTOOLS001

Reporting Tool’s Product(s): PS/nVision
PeopleTools Release(s): 7.x, 8.1x, 8.4x, 8.5x
Revision Number: Rev1
Contains:
√
√
√
√
√
√
2
11/12/2009
Table of Contents
Table of Contents........................................................................................................................................................3
Introduction .................................................................................................................................................................5
Structure of this Red Paper 5
Related Materials 5
Chapter 1 - Executive Overview ...............................................................................................................................6
Chapter 2: PS/nVision ................................................................................................................................................8
Chapter 3: Main Components of PS/nVision report ..............................................................................................10

Report Layout 10
Report Request 12
Chapter 4 - PS/nVision Configuration for 2-tier client environment..................................................................14

Configuration Manager Settings 14
Chapter 5 - How to run PS/nVision in 2-tier client environment .........................................................................16

Appearance of PS/nVision 2 tier client 17
Steps to create an PS/nVision report 18
Chapter 6: PS/nVision setup in Web Environment (n tier) ...................................................................................20

Report Server Requirements 20
MS Excel 21
PSPRCS.cfg settings 21
DrilltoPIA.xla 22
Chapter 7: How to run PS/nVision in Web environment.......................................................................................23

Report Request 23
Scope and Report output Types 24
Drilldown 25
Chapter 8: PS/nVision Advanced Features ............................................................................................................27

Scope 27
Drilldown 29
nPlosion 30
ReportBook 30
PS/nVision Variables 31
NvsInstanceHook 31
Copyright © 2006 Oracle, Inc. All rights reserved. 3

Chapter 9: New Features in PS/nVision in PeopleTools 8.4x..............................................................................33

SaveTempFile 33
TimeOut settings 33
EnablePoll Dialogs 34
PS/nVision Trace 34
Secured Reports 34
EnableDrillDownforFile 35
Chapter 10 : New Features in PS/nVision in PeopleTools 8.5x ...........................................................................36
Public and Private Report Requests in nVision Windows client 36

Improved Drilldown on PIA using Web Services 36
Tree Effective Date Criteria 37
Not In Tree Criteria 38
Support for Query Prompts via PIA 38
Decoupled PS_HOME vis-à-vis nVision 39
Chapter 11 : PS/nVision with Excel 2007/PeopleTools 8.4x/8.5x ........................................................................40
Known Issues with Excel 2007 Compatibility Mode 40

Features that need to be verified with Excel 2007 normal mode 41
Chapter 12: Troubleshooting Tips ..........................................................................................................................42

In 2-tier client 42
With Certain workstations 42
With all workstations 42
In Web Environment 43
On Intermittent Basis 43
On Regular Basis 43
With all Reports 43
With some certain Reports 43
Tips for DRILLDOWN 46
With Certain Drilldowns 46
With All Drilldowns 47
Drilldowns in 2-tier 47
Drilldowns in Web Environment 47
Drilldown issues with some specific Users 48
Perforamnce issues with PS/nVision 48
Important Logs 48
Important Resolutions 49
Appendix A ................................................................................................................................................................50
References.................................................................................................................................................................51

Introduction
This Red Paper is an introductory and practical guide for technical PS/nVision users, beginners, PS/nVision reports
Developers and Oracle Global Customer Services analysts. This Red Paper discusses the PS/nVision reporting
tool, it’s configuration within PeopleSoft Application and troubleshooting tips for PS/nVision related problems.
Much of the information contained in this document originated from and within Customer’s production environments
and PeopleSoft Development and is therefore based on "real-life" problems encountered in the field. The issues
that are discussed here are the problems that prove to be the most common or troublesome.
STRUCTURE OF THIS RED PAPER
This Red Paper provides guidance on basic understanding of PS/nVision reporting tool.
Keep in mind that PeopleSoft updates this document as needed so that it reflects the most current feedback one
receive from the field. Therefore, the structure, headings, contents, and length of this document is likely to vary with
each posted version. To see if the document has been updated since users last downloaded it, compare the date of
usersr version to the date of the version posted on Customer Connection.
RELATED MATERIALS
It is assumed that our readers are Oracle GCS Reporting Tools analysts, PeopleSoft DBAs and PS/nVision reports
developers. To take full advantage of the information covered in this document, it is recommended that users
should have a basic understanding of system administration, basic Internet architecture, relational database
concepts/SQL, and how to use PeopleSoft applications.
This document is not intended to replace the documentation delivered with the PeopleTools PS/nVision section. It
is recommended that before any user reads this document, user should read the PIA related information in the
PeopleTools People Books 8.49 to ensure that user have a well-rounded understanding of our PIA technology.
Note: Much of the information in this document eventually gets incorporated into subsequent versions of the People
Books.

Chapter 1 - Executive Overview
PS/nVision is a PeopleSoft owned product, which is used for reporting purpose. It is one of the main reporting tools
one uses to generate reports within PeopleSoft Application. It is an Excel based reporting and analysis tool.
PS/nVision selects data from PeopleSoft database against the Ledgers, Trees and Queries. Depending upon the
criteria defined at the report level, it retrieves the information from database and places it into Excel spreadsheet.
Users use familiar enhanced Excel commands to format and analyze the data. This transfer of information from the
database to spreadsheet enables users to use familiar excel commands for formatting and analyzing data.
Overview of PS/nVision Tool:
1- Major Capabilities:
a- Enables users to summarize transactional data.
b- Enable users to nPlode (explode) and Drilldown to the appropriate level of detail.
c- Allow users to define scope for report. Users can define scopes on multiple fields also.
d- Facilitates the use of trees in reports.
e- Handles report bursting and distribution (to individual or role) through Scope Definition.
2- Major Strengths:
a- It’s a PeopleSoft developed Reporting Tools.
b- Builds upon users’ Excel expertise.
c- Enables functional users to create reports to fit their needs

3- Disadvantages:
a- PS/nVision tools runs only in Windows environment as it uses Microsoft Excel for the reporting
purpose. So, it cannot be run on Unix or any other O/S.
b- In Web environment (4-tier), users can run PS/nVision reports to only two output formats (.HTM
and .XLS). In comparison to other Reporting Tools, PS/nVision has very few output format options.
In 2-tier also, users may run PS/nVision report to both .HTM and .XLS format but not in any other
output formats like .PDF or .DOC etc..

Chapter 2 - PS/nVision
PS/nVision not only works with spreadsheets, it works within them. Users access PS/nVision features from a
special PS/nVision menu within Microsoft Excel. User organizations can also create a custom “front-end” macro
sheet to give users point-and-click access to reports and reporting functions.
Because PS/nVision works from within user spreadsheet, users may use the familiar commands, Excel offers for
inserting formulas, formatting and graphics. Users may check more detailed information for these Excel commands
in Microsoft’s Excel User guide or the Excel on-line help.
The first question arises in mind why PS/nVision tool in comparison to other Reporting Tools? Some of the
advantages and strengths of PS/nVision tools have already been discussed in Chapter 1. Below are some
scenarios where users will better understand the need of PS/nVision tool. See the picture below:
Consider the scenario: At the end of every month, company generates reports from the accounting systems to help
determine its financial health and position, typically, this task is performed by accountants and analysts, who are
responsible for evaluating the company’s position and reporting the results to Senior Executives. The complete
process includes tasks such as reporting, analysis, data entry and delivery.

To reduce the time and efforts required in reporting, analysis, data entry, and delivery users are assigned the task
of retrieving the data directly into an Excel spreadsheet. Users only need to combine the power of PS/nVision with
the known functionalities of the Microsoft Excel spreadsheet to format and deliver the report. PS/nVision makes all
reporting and analysis of data very easy.
This is one of the scenarios, which describes the usage of PS/nVision tool in terms of commercial purposes.

Chapter 3 - Main Components of PS/nVision report
Before proceeding further, users must understand more about the Report Layout and Report Request and their
roles in generation of any PS/nVision report.
Report Layout
Report layout is an Excel spreadsheet that users can use as a template to define the format in which the report is
displayed and the type of information that goes into the report. Report layout specifies the type of data that can be
retrieved within the columns and rows. The Report Layout also consists of formulae to calculate and retrieve data.
Creation of report layouts is the first step towards developing the Report layouts. It specifies the Query or Ledger,
whichever is used for the report generation. Report layout is just an Excel spreadsheet. However it does not
include any actual PeopleSoft data. It is just the structure of the report-query/ledger information, criteria, test,
formulae, graphics, formatting or other information users want to include.
PS/nVision offers two types of Report layouts.
1- Tabular Layout
2- Matrix Layout
The main difference between both these types of layouts is the way in which users specify the data to be retrieved
from the database. Tabular layouts are used for detailed transaction reporting, while matrix layouts are more
appropriate for summarized reporting and analysis.
PS/nVision > Layout Options
Tabular layouts are the simpler of the two layout types. These layouts use a Query defined in PeopleSoft Query
to retrieve data. The columns in the report correspond to the fields returned by the query and the rows in the report
correspond to the rows in the query result set.
Matrix layouts are more complex in nature. Matrix layouts have data selection criteria based on the intersection of
columns and rows in the spreadsheet, thus creating a criteria matrix. Users can specify data selection criteria at
the level of the entire spreadsheet i.e. a row, a column or an individual cell.
The data retrieved for an individual cell is determined by a combination of the criteria for its’ column and its’ row.
Unless users are specifying a query in the matrix layout, all matrix layouts must have at least one timespan, one
ledger and one chartfield as criteria.

The table below shows some of the key differences between tabular and matrix layouts.
Feature/Function Matrix Layout Tabular Layout

Data Sources Multiple Queries and/or Ledgers. Single Query
Data Numbers in matrix, text in labels and variables Text and numbers
Data Delivery Row/Column intersections (amounts); row and Selected Query results columns, one
column labels (text) data row per spreadsheet row
Layout sheets One per workbook Multiple per workbook
Selection Criteria Scope, Query, including prompts, criteria at Scope, Query including Prompts
Sheet, column, row and cell level
PS/nVision variables Yes No
Scope Multiple instances of layout workbook Multiple instances of layout
workbook
nPlosion Rows and Columns None
Drilldown from Instance Yes No
Time Spans Yes, with data keyed by year, period No
Before creating layout, users must be very clear about the format and type of data users like to show to the end
users as a Report output. It makes users’ work very easy while putting format related columns and fields in layout
or putting formulae to calculate the data in end results.
PS/nVision > Layout Definition
For more details about the “tabs” in “Layout Definition” window and their usage, please review “PS/nVision” section
in PeopleBooks.

Report Request
Second step is creating Report Request for this PS/nVision report. Users must create a corresponding Report
Request for running a PS/nVision report.
Each Report Request is a collection of report-specific information such as Request name, report title, associated
Report Layout, Scope and so on. Users must use the Report Request dialog box to open, create, modify or delete
Report Requests.
When defining a Report Request, users can use the Scope feature to create multiple instances of a report from a
single request as shown in the screenshot below:
Excel PS/nVision tab Select New Report Request this window appears

Below are the descriptions of Fields under Report Request.
Request Name: This name identifies Report Request

Report Title: This tile appears on prompt lists and can be used in reports and can be used in report
Requesting: Report request are owned by Business Units. The Layout may retrieve data for this
Business Unit business unit.
Layout: One can choose the applicable .XNV report layout, one likes to execute
Scope: This is optional. Leave blank if users do not need scope. A scope is used to create
multiple Instances of one .XNV file, such as instances for each Business Units or
departments
Directory Template: Specifies which directory to place the report after users have run the request. If users
leave the Template field blank the finished report will be in default directory. Users may
use PS/nVision variables also to get any specific nomenclature for users directory names.
File Template: It specifies the name of Report Instance (output) that is created when running this Report
request. Users can include PS/nVision variables in the template to dynamically creates file
names at the run time
For Ex: %RTT% or %LYN%
Enable nPlosion: In 2-tier, for performing nPlosion, this checkbox should be checked. Otherwise one will not
be able to perform nPlosion successfully
Data from requesting: When this checkbox is turned on the report, data will reflect only from the requesting
business unit only. If this box is not checked, it will extract data for all Business units,
meeting the criteria in Layout. This is how users can run a consolidated report.
Business Unit only
As of Date: It allows users to select the effective date of the trees to be used when trees are
referenced in layout and scopes. This is usually left at the default.
Use Main as of Date: It means it will use the tree closest to the As of Date.
** For more details, please check the “PS/nVision” section in PeopleBooks.

Chapter 4 - PS/nVision Configuration for 2-tier client environment
PS/nVision requires specific DLL’s and ODBC driver that are specific to that Peopletools version. PS/nVision relies
on the PeopleSoft PTools ODBC Driver to be the exact same version of PTools that is currently being run. If a user
has multiple Peopletools versions on his machine a “Workstation install” might be required to go back and forth with
PS/nVision according to the usage of one environment. So, please check if users are having multiple PeopleTools
versions on box and in Web environment also. However, PeopleSoft does not recommend multiple PeopleTools
version on single machine for avoiding issues with PS/nVision and Crystal Reports.
In 2-tier client environment:
1- Open Configuration Manager

2- Click the “Profile” tab
3- Click the “Edit” button
4- Click the “PS/nVision” tab
This is the only place where one can configure the PS/nVision related directories within Configuration Manager.
Now let’s discuss the various settings under “PS/nVision” tab in Configuration Manager.
Space between Query Columns: This is the setting that is defined to have spaces in between the columns in the
report output or Query to Excel output.
Under Directory Paths:

1- Customization Macros: PS/nVision is basically a macro driven tool. Macros are used to run some
features of PS/nVision report. For ex: DrilltoPIA.xla, NVSUSER.xla, GLLog etc. Here the path for “excel”
folder, available under %PS_HOME% needs to me mentioned.
For ex: D:\FMS89\excel where “D:\FMS89” is usersr PS_HOME or “D” drive is where usersr File server is
mapped.
2- Report Layouts: This is the field to specify the location of PeopleSoft delivered Report Layouts as well as
Customized Report layouts. There is a folder by name “layout” under “PS/nVision” folder for this.
Ex: D:\FMS89\PS/nVision\layout
3- Drilldown Layouts: This is the location of the folder where all users Drilldown layouts reside, both
PeopleSoft delivered and Customized ones. Ex: D:\FMS89\PS/nVision\layout\drilldn
4- Report Instance: This is the location where all PS/nVision Report Instances will get saved when running
to 2-tier client. Ex: C:\USER\PS/nVision\INSTANCE
5- Query Templates: This is the setting where Query Templates are available. These templates are
available under the Excel folder only in PS_HOME. Ex: D:\FMS89\excel
6- Style Sheets: This is the location where various Excel style sheets get stores. These are mainly used
during nPlosion. Ex: D:\FMS89\excel\stylesheets
Note: If users access PS_HOME from the network, please give the UNC path instead of mapped drive path as
there are many issues involves with mapped drive path. There are some resolutions # 201008980 (Doc ID
647145.1), 200999015 (Doc ID 645019.1), 200975617(Doc ID 640030.1), which talk about the issues
related to mapped drive paths.
Prerequisites for PS/nVision in 2-tier client for successful running
1- Certified Excel version with present PeopleTools version should be installed on users machine.
2- Workstation Installation should be done in proper manner in “Configuration Manager” with correct settings
in below locations:
a- Check the PS_Home directory setting under Process Scheduler tab. It must be correct.
b- Check the DBBIN setting under Process Scheduler tab. It must point to the correct location.
c- Please check all the locations are correctly filled under “PS/nVision” tab
d- Under Client Setup tab --> under ODBC setup --> Check the Install PeopleSoft ODBC Driver and
Workstation Installation --> click Apply.
After performing the above, users should be ready to work within PS/nVision Reporting Tool.

Chapter 5 - How to run PS/nVision in 2-tier client environment
There are two ways by which users may run PS/nVision client on users machine.
First: Log in Application Designer Go PS/nVision (click)
Second: If while performing “Workstation Installation” users select “PS/nVision” also, PS/nVision would be
available to users under the “start” Programs - PeopleSoft > PS/nVision

Appearance of PS/nVision client:

When users run PS/nVision, PS/nVision instance opens a file named NVSUSER.xls (PS/nVision Menu).
With this it also opens an Excel sheet and an instance of PS/nVision.
NVSUSER.xlm (or .xls) is “Startup” homepage for PS/nVision. There are two new menu choices in Excel
tool bar i.e. “PS/nVision” and “Drill”
Please make sure that all the three NVSUSER.xlm, Excel Instance and PS/nVision windows must remain
open. If users close any one of them, PS/nVision instance would be closed.

Users have many options under “PS/nVision” and “Drill” tab in layout, with which users can design layouts, define
Report Requests and run PS/nVision reports.
Steps to Create a PS/nVision Report:
Every PS/nVision report, users create, is based upon “Report layout”. When users run a PS/nVision report through
Report Request, PS/nVision uses the specified Report Layout to determine what data to retrieve for the report and
how to display it. Therefore creating a PS/nVision report is a 2-step process.
There are two main components about creating PS/nVision reports. These components are:
1- Report layout
2- Report Request
1- Report Layouts are the formats of PS/nVision reports in which one would like to show data to the end users.
One creates Report layouts in Excel only. Report layouts have extensions .XNV.
This step is required only for the first time users create the report. Once the layout is saved, users can use the
same Report layout repeatedly.
2- After creating Report layout, users should create a Report Request. In Report Request, users specify the
layout and the other run options for PS/nVision report.

After defining a Report Layout and Report Request, users run the Report Request either by using the
PS/nVision menu in MS-Excel or clicking the “RUN” button on the Report request dialogue box. This creates
“Report Instance” at the location which users define in Configuration Manager > PS/nVision > “Report
Instance”.
A Report instance contains data that PS/nVision has retrieved from users PeopleSoft database. It is the output
of PS/nVision report.
Users can produce multiple instances of a single PS/nVision report with the help of the feature scope. For
example, users might want to generate an income statement report for each department in users organization.
Each instance is an individual report with up-to-the-minute data from users database, selected and formatted
according to the instructions in the Report Layout.
User can send Report outputs to “File”/”Printer” output type and only “XLS” output format is available in 2-tier
environment.

Chapter 6 - PS/nVision setup in Web Environment (n tier)

With PeopleSoft 8 users with Internet access can run, view, drilldown and distribute PS/nVision reports through a
browser, without a PeopleSoft installation on client machines. Users can also send reports as email attachments
rather than requiring recipients to navigate to a location on file server.
Main advantages in Web:
1- Internet versions of Report Requests, ReportBooks and Scope Definitions

2- PS/nVision report output in .XLS and .HTM formats
3- Drilldown for report outputs in HTML (PeopleTools 8.10 and higher) or XLS format (8.14 and higher)
4- Email options to send PS/nVision reports to individual user or users in specified roles
Users may run multiple parallel PS/nVision sessions in web environment, depending upon the MAX Concurrent
settings for PS/nVision processes in Server Definition. Users can create Report Request, register Drilldown
layouts, run Drilldown to “Web” or “Window” output types and also can define scopes in web environment.
But remember, users cannot create Report Layouts in Web environment. For creating Report layouts users
still require workstation client. So for PS/nVision developers, client installation is required. However for the end
users who only run PS/nVision reports in web environment or view them, there is no need of client installation on
their machines.
PS/nVision windows client is used only to generate Report layouts. Once these Report Layouts are developed, they
are uploaded to the configurable layout directory, which is accessible to Report Server. Users access the Report
Server and the database via browsers though PIA. Scopes and Report Requests can be directly created in Web
environment itself and reports can be run through the Web as well.
When Report Request is run from Web interface, Process Scheduler initiates a PS/nVision instance on the Report
Server, which in turn initiates an instance of Excel. PS/nVision analyzes the Report Layout and retrieves data from
database and saves the report to a specified output format (XLS or HTM) under a configurable instance directory to
the Report Repository.
Users can view the report in browser via a link in Report Manager.
PS/nVision configuration for Web Environment:
For running PS/nVision in Web environment, Report Server must be setup correctly. Report Server is the place
where PS/nVision reports are run when requested by end users. As it is known PS/nVision uses EXCEL to
generate reports, the Report Server must be running on Windows platform. Report Server must also have the
following components:
1- Microsoft Excel
2- Process Scheduler Server
3- PeopleTools client installation (this installs PSNVS.EXE, which is what runs PS/nVision reports)
4- Database connectivity software
So, please make sure the above components are installed properly on Scheduler box to run PS/nVision
successfully in the web environment.
** For verifying that the Excel registry settings, ODBC driver and basic settings for PS/nVisions are correct on the
Process Scheduler box, please run any PS/nVision report through Application Designer (2- tier) on the Report
Server. If report is generated successfully it indicates that the settings are correct.

BEAPROCMgr Tuxedo Service:
1. Please check if Process Scheduler is started with a service or thru psadmin. If as a service then it is
recommended to log on as 'this account'. Please make sure that it is a Domain Account.
If the Process Scheduler is started thru PSADMIN then please find out the user id that logs onto the network to
access PSADMIN to startup the process scheduler - Ensure that this user is a Domain Account.
2. BEAProc Manager Service - Please find out if this service is logged on as 'Local system account' or 'this
account'? Recommended way would be 'This Account' and ensure that it is a Domain Account.
3. Ensure that the user ID that starts up both the Process Scheduler and BEA Proc Manager are the same and that
Users have Domain rights.
Excel version:
It is recommended to use Excel 2000 and above Excel version on Report Server. PS/nVision supports both XLS
and HTML in release 8.x onwards. When an HTML format is requested, PS/nVision uses Excel’s “Save as Web
Page” function to generate the HTML format output. This function is only available from Excel 2000 and upper
versions. Therefore if Excel 97 is used on the Report Server, users will not be able to generate PS/nVision reports
in HTML format output.
Process Scheduler Configuration:
It is important to know that when running PS/nVision in the web environment, Process Scheduler on the Report
Server kicks it off. For this configuration of PS/nVision related directories in Process Scheduler configuration file
(PSPRCS.cfg) is required. The PSPRCS.cfg file is located at below location
%PS_HOME%\appserv\prcs\Domain name \PSPRCS.cfg
Configuring similar directories using PeopleTools Configuration Manager only enables users to run PS/nVision as a
Windows client on the Report Server.
Below are settings for PS/nVision in PSPRCS.cfg file.
[PS/nVision]
;=======================================================================
; General settings for PS/nVision
;=======================================================================
DrillDownDir=%PS_HOME%\PS/nVision\LAYOUT\DRILLDN
InstanceDir=%PS_HOME%\PS/nVision\INSTANCE
LayoutDir=%PS_HOME%\PS/nVision\LAYOUT
MacroDir=%PS_HOME%\EXCEL
StyleDir=%PS_HOME%\EXCEL\STYLESHEETS
TemplateDir=%PS_HOME%\EXCEL
EnableDrillDownForFile=0
EnablePollDialogs=0
PollDialogSeconds=30
TraceLevel=0
SaveTempFile=0
In above configuration, most of the directory locations are similar to the Configuration Manager, which is discussed
in previous chapter. However there are certain flags, which are introduced only with PeopleTools 8.4x and
onwards. These flags are introduced by development to enhance the capabilities of PS/nVision as a Reporting
Tool and make it more competitive against the other available Reporting Tools. These flags are discussed in detail
in following chapters. (Chapter 9)

Excel Add-in (DrilltoPIA.xla):
DrilltoPIA.xla is an optional Excel VBA add-in that is provided for end users convenience in PS/nVision for
PeopleTools 8.14 and above. End users need to install this add-in only when Users want to Drilldown directly from
Report instances in Excel on a browser client. Users do not need this add-in if then only view reports in Excel XLS
format through the web.
DrilltoPIA.xla is delivered with PeopleTools CD. This add-in requires only a one-time load in the load in the end
user’s environment. To load the add-in DrillToPIA.xla file into usersr Excel environment:
1. Go to usersr %PS_HOME%\Excel directory
2. Copy the file DrillToPIA.xla to usersr Excel add-in directory
If usersr Microsoft Office is installed in %MS_OFFICE%, then Excel add-ins directory is

%MS_OFFICE%\Office\Library.
3 - Launch Excel, and select DrillToPIA in the Add-ins dialog box. Select the menu option Tools, Add-ins
In Web Environment, users can access PS/nVision with the below navigation:
Menu > Reporting Tools > PS/nVision

Chapter 7 - How to run PS/nVision in Web environment

PS/nVision report can be run in Web environment (n-tier) by navigating as suggested below.
Menu > Reporting Tools > PS/nVision
User can define Report Request in Web environment also. It is similar to the 2-tier environment.
Reporting Tools > PS/nVision > Define Report Request

Users can define Scope and other entries by clicking Scope and Delivery Templates link.
Reporting Tools > PS/nVision > Define Report Request > Scope and Delivery Templates
After putting the desired entries in report request, user can run the report by clicking “Run Report” button.
Report Output types:
Users have the option to run PS/nVision reports to multiple output types “Web”, “Email”, ”Printer”, “Window” and
“File” in web environment. When users run the report to “Web” output type, report output goes to the “Report
Repository” and one can access the output from the Report Manager. If user runs the report to “File”, one can send
the report output to the desired location. In “Window”, report output appears in a new Window. Similarly one can
send the report output directly to “Email” and “specified network “Printer”.
Note: For “Window” output type, “Ren Server” setup should be correct. And for “Printer”, printer should be setup
correctly in that environment.
Viewing Report output:
User can check the status of the report through “Process Monitor” page. Like in below screenshot, it is showing
status “Success/Posted”
By clicking on “Details” link, user can move to “Process Details” page. Where by clicking on “View Log/Trace” link,
user can see the Report output.

The other way to look the Report Output is directly from “Report manager”. Please see the screenshot below.
Reporting Tools > Report Manager
Drilldown:
If Drill down criteria is defined on the parent instance, user can start Drilldown on clicking that cell. The page will
appear as.
Note: If users are not getting custom Drilldowns in Web environment, please make sure that users have registered
that Drilldown for that specific environment.
For running Drilldown, select the “Run Drilldown” button for the desired drilldown. On this, Drilldown instance will
run. On Success, users can view the output either from the “Process Monitor” page

or from the “Report Manager” directly.
By clicking the link under “Description” field or the “Details” link, user can view the Drilldown report output.

Chapter 8 - PS/nVision Advanced Features
There are some advanced features of PS/nVision, which enhance the capabilities of PS/nVision as a Reporting
Tool and provides some edge on the other reporting tools. The main features are
1- Scope
2- Drilldown
3- nPlosion
4- ReportBook
5- PS/nVision Variables
6- NVSInstanceHook
Let’s discuss in more detail about these. For more details about these features, please go through People Books,
as there is detailed information about the same.
Scope
A Report Scope enables users to create multiple instances of an PS/nVision report by using a single Report layout
and running Report Request only once.
* Users can use PS/nVision Scope feature while creating a Report request to retrieve instances of a report from the
PeopleSoft database
* Users process the Report Request once and PS/nVision automatically produces a multiple Report instances for
specific Field values

* Using a scope, each Report Instance will contain data specific to an individual field value, such as a Business Unit
or Department, or a group of values, such as a tree node summarizing all sales departments. In this way, each
report instance can share the same layout, while contains data unique to these field values.
In 2-tier:
Users can define Scopes on combination of Fields.
In Web:

Drilldown
Drilldown is a PS/nVision feature that enables users to select a cell on the Report Instance worksheet and expand it
according to the new criteria in a special Drilldown layout. Users can perform Drilldown in both the environments
i.e. 2-tier environment and Web environment.
Drilldown is useful when PS/nVision Reports are based on summary Ledgers, because it provides underlying
details whenever and wherever users need them. The key to Drilldown is passing the selection criteria from a
parent cell to its’ child cell by using the Drilldown layout.
The Drilldown feature is available only for Matrix layouts. However the layout that displays the results of the
Drilldown, can be with either matrix or tabular. Please note that users can Drilldown further only from a Matrix
Layout. After displaying the results of a Drilldown in a tabular layout, users cannot Drilldown further.
Matrix Matrix
D Layout Layout
R D
I R
L I
L L
D L
O D
W O
N Matrix W
N
Tabular
Layout Layout
D
R
I
L
L
D
O Tabular
W
N Layout
POSSIBLE DRILLDOWN SCENARIOS
In summary, Drilldown feature offers fast and convenient access to supporting details in summary reports.
In Web environment, user may Drilldown to two output types “Web” and “Window”. Drilldown output type is default
to "Window", in Web environment. If "Window" is used to run any process, Ren Server must be setup. So please
confirm if users setup Ren Server in users environment so that users could run drilldown to "Window".
If Ren Server is setup correctly, Please check the below points for that specific user.

1- Please add permission list PTPT1200 to the user's profile.
2- Update the Web Libraries tab on the primary permission list to include WEBLIB_RPT "FULL ACCESS".
WEBLIB_RPT is the script that produces the "processing page".
nPlosion
nPlosion is used to expand row or columns containing Field criteria. When enabled, nPlosion automatically creates
individual rows or columns for each detail value defined in the criteria, whether those values are defined specifically
or implicitly.
nPlosion is set at layout level. NPlosion provides the ability to specify a tree node in a layout and have rows or
columns at run time for each underlying detail value, which makes up the criteria. Likewise users may expand
multi-period timespans, such as YTD, to show amounts for each accounting period. Detail values rows are inserted
above the row where the nPloded criteria are specified. Detail value columns are inserted to the left of the column
where the nPloded criteria are specified.
There are two types of nPlosions.
1- Row nPlosion
2- Column nPlosion
In Report Instance, nPlosion looks like the below picture. It is showing the Row nPlosion. Similarly for Column
nPlosion, brackets come at the top of columns on which one defines nPlosion.
ReportBook
A ReportBook is a PS/nVision component that enables users to group multiple Report Requests and run the
ReportBook once to process all the combined Report Requests. Use of a Report Book saves users the time that
would be required to manually run a large number of Report Requests. Users can schedule it in Process
Scheduler.
In Web Environment:

PS/nVision Variables
There are certain variables available which one may use to enhance the Report Instances nomenclature options
and enhance the reporting capabilities. One can use PS/nVision variables into the layout to display heading
information that might change from report to report, or between report runs.
Besides using PS/nVision variables in users layouts, users can use some of these variables in the Instance
Controls section of the Report Request dialog box.
Users can define variable criteria at the cell level only—one variable per cell—and the variable must be the only
element in that cell.
When users choose a variable, users select its three-letter code. However, when a variable is used in a layout or
report request, its code must be enclosed within percent signs (for example, %RID%).
There are mainly three types of PS/nVision variables.
1- Report Request Variables, which are defined on the Report Request, dialog box.
Ex: %ICT%, %IFN%, %RTT%, %RID%
2- Date and Time Period Variables, which help to insert specific time or period in layouts where different
accounting periods are reported in each instance.
Ex: %APN%, %ASD%, %PER%
3- Scope-Related Variables helps in labeling layouts for which one are using any report scope. A scope is
used to define multiple instances of a report based on different field values.
Ex: %SFN%, %SFD%, %SFV%
** For more details about PS/nVision variables, please review information available in People Books.
NVSInstanceHook
“NvsInstanceHook” is the name assigned to an Excel macro in an PS/nVision layout when users want PS/nVision
to process the macro as the last procedure in the creation of an PS/nVision report instance. NvsInstanceHook
indicates the name or reference of the macro to be run on completion of the instance.
With the NVSINSTANCEHOOK one can make custom macros in Visual basic and can use them for customizing
the PS/nVision reports according to our requirements.

Please review the screenshots.
However from GSC perspective, please be informed that custom macros which are used in any PS/nVision report,
are considered as customizations and do not come under GSC support domain. However some information about
this is available in People Books so that customer can take help of this in customizing their macros.
For more details about this, please check the People Books, which will give users some idea about how to use that.
Users can get this information in People Books at below given navigation:
Home > People Books > Enterprise PeopleTools 8.46 PeopleBook: PS/nVision > Using the PS⁄PS/nVision
Visual Basic Interface
However, below are some scenarios where one can take help or suggest customers to use NVSINSTANCEHOOK.
1- If users like to apply an nPlosion style to one specific column.

2- If users like to have time and date stamp in PS/nVision reports output file names.
3- If users would like to combine multiple PS/nVision reports into one Excel Workbook during the PS/nVision
report generation.

Chapter 9 - New Features in PS/nVision in PeopleTools 8.4x

This chapter will give users some idea about the new features, which are introduced in PeopleTools 8.4x for
PS/nVision, to enhance the reporting capabilities of PS/nVision as a Reporting Tool.
1- SaveTempFile:
This flag is introduced in PeopleTools 8.45.16. This flag is setup in the PS/nVision section of the PSPRCS.cfg file.
If one sets SaveTempFile=1 files will not be deleted when reports ran to Web, Email or Printer output type.
File output specified in Directory Name Template of Report Request, if left blank, report saves to PS/nVision
Instance Directory
Users may check the Resolution # 200976598 (Doc ID 640188.1) for more details about this new flag.
2- Time-out settings:
This feature is introduced in PeopleTools 8.44 release. Users can define Time-out setting for any specific
PS/nVision report at the “Report Request Definition” level.
Users may also define “Time-out” for PS/nVision/Drilldown in “Process Definition-NVSRUN/DRILLDWN”
** Users may check Resolution # 200770135 (Doc ID 622973.1) for more details about this issue.

3- EnablePollDialogs:
This flag is introduced in PeopleTools 8.44 release. This flag is setup in the PS/nVision section of the Process
Scheduler configuration file. (PSPRCS.cfg)
•1= turned on
•0 = turned off
When this setting is set = 1, and if any PS/nVision dialog messages come up while running PS/nVision report,
PS/nVision will detect and dismiss them. It is not for Excel Pop ups or O/S Pop up boxes as such.
EnablePollSeconds=30
It configures how often to check for unattended PS/nVision dialog boxes. There is a known issue with this, which
was addressed in Incident # 1294236000 resolved in PeopleTools 8.45.18 and 8.46.06.
4- PS/nVision trace option:
Users may turn on trace for PS/nVision reports in the PS/nVision section of the Process Scheduler configuration file
(PSPRCS.cfg).
The Output of that trace would be available at
Client: c:\temp\psnvs_<process_id>.nvt
Web: View Log/Trace link under Process Details
TraceLevel=0 (0-4)
0: No tracing (default setting)

1: Basic high level process flow and status
2: Entries from Level 1 plus additional info
3: Tracing up to level 2 and SQL statements
4: Tracing up to level 3 plus additional function calls, output values, and other detail information.
5- Secured Reports:
With PeopleTools 8.44 onwards user can secure PS/nVision reports with the help of this option. This includes the
below features.
a: Private by Default
b: Share by users or roles
c: Secured -Only users in list can update
d: Public –All users can update

6- “EnableDrilldownforFile” flag:
a: Started in PeopleTools 8.42.08 and 8.43

b: Ability to run parent PS/nVision report to “File” output type and still run Drilldown
c: PSPRCS.CFG “EnableDrilldownforFile = 1”
d: Report still goes to Report Repository
Please check Resolution # 200756612 (Doc ID 620653.1), for more details.
** These are the features, which are introduced with PeopleTools 8.44 onwards. For details of these features users
may go through People Books.

Chapter 10 - New Features in PS/nVision in PeopleTools 8.5

This chapter will give users some idea about the new features, which are introduced in PeopleTools 8.5x for
PS/nVision, to enhance the reporting capabilities of PS/nVision as a Reporting Tool.
1- Public and Private Report Requests in nVision Windows client :
In PeopleTools 8.4x:
Report Requests can be secured, shared or transferred via PIA only.
In PeopleTools 8.50:
a- Windows client can be used for securing and sharing Report Requests.
b- New “nVision Share Report Request” dialog box added.
c- New “nVision Report Request Admin” dialog box added.
d- All new report requests will be secured by default.
e- User can change security settings for individual Report Requests.
2- Improved Drilldown on PIA using Web Services
Drilldown from Excel takes the user to PIA for layout selection.
a- Excel invokes REST-based web services to eliminate the PIA trip.

b- User opens a report and goes to nVision Drill menu.
c- Web service operation retrieves the list of drilldown layouts.
d- User chooses a drilldown layout from the list in Excel.
e- Web service operation submits report request to Process Scheduler.
f- Web service operation opens the report in a new Excel window.
g- User could disable the web services mode and operate the 8.4x way.

Setup Checklist to achieve the “Drilldown” from “Web Services”
•MS Excel 2007

•MS Visual Studio Tools for Office Plug-in
•MS Office 2007 Primary Interop Assemblies
•MS .NET 2.0 Framework
•nVisionDrill add-in in Excel
•App Server Configuration
•IB Configuration
•SSL Configuration
•Report Node Configuration
3- Tree Effective Date Criteria
Effective dates for trees, only in Report Request
a- Effective dates for trees in Criteria Definition and Report Request.

b- New “As Of Date” field added in “PeopleSoft nVision Filter Criteria” dialog.
c- New “Override Layout“check-box added in “PeopleSoft nVision Report Request” dialog.
d- New “Override Tree As Of Date If Specified in Layout” in PIA Report Request page.
e- User can override criteria effective date in Report Request.
f- No impact on Tabular Layouts.

4- Not In Tree Criteria
Layout Definition does not allow exclusion of nodes.
a- User can exclude tree nodes in Layout Definition.

b- New check box added in “PeopleSoft nVision Filter Criteria” dialog.
c- Excluded nodes appear grayed out in “PeopleSoft nVision Layout Definition” dialog.
d- Excluded nodes become part of “Not In” criteria string inserted into the selected cell.
5- Support for Query Prompts via PIA
Windows client accepts query prompt values at runtime.
a- User can input query prompt values via PIA.

b- New sub-page named “Query Prompts” added.
c- User can view the prompt parameters of queries associated with the layout.
d- User can view/edit the prompt values.
Constraints:
Report must be executed once to ave the prompts in database.

Important Points to check with the “Query Prompts via Web” feature:
a- Report execution will fail for the first time. Subsequent Report executions should work successfully.
b- If prompts are modified through Query Manager, then the new list of prompts have to be loaded in nVision
Report Request also. This can be done by clicking the Update Parameters link.
6- Decoupled PS_HOME vis-à-vis nVision
PS_HOME is read-write.
PS_HOME is read-only.
Changes in nVision
a- nVision/INSTANCE directory is moved out of PS_HOME. The new default location is under PS_SERVDIR.
b- nVision/LAYOUT directory has to be moved out of PS_HOME if Layout files are required to be editable.

Chapter 11 - PS/nVision with Excel 2007/PeopleTools 8.4x/8.5x
Excel 2007 is the certified Excel version with PeopleTools 8.46 onwards. However, presently there are certain
issues involve in using PS/nVision with Excel 2007.
Following are the limitations, which would not allow PS/nVision to run normally like any other Excel 2007 based
applications:
Whenever Excel 2007 opens a file in Excel 2003 file format, i.e. a .xls file, it opens in “compatibility” mode and not
in “normal” mode.
Known Issues with Excel 2007 “Compatibility” Mode:
One of the ways that we enable people to create documents in Excel 2007, which are compatible with previous
versions is by disabling new features of Excel 2007 by changing the characteristics of runtime container of Excel
2007 to match characteristics of runtime container of Excel 2003.
In this “compatibility” mode of Excel 2007, PS/nVision functions as it did in Excel 2003 and does not take
advantage of the enhanced capabilities of Excel 2007:
a- The total number of available columns in Excel - Currently restricted to 256 (New Limit: 16k)
b- The total number of available rows in Excel - Currently restricted to 64k (New Limit: 1M)
c- Max number of arguments per function - Currently restricted to 30 (New Limit: 255)
d- Number of levels of nesting in formulas - Currently restricted to 7 (New Limit: 64)
e- Formula Length - Currently restricted to 1k characters (New Limit: 8k characters)
f- Structured Referencing of Tables in Formulas - Structured references to tables are not created automatically
when formulas are created.
Structured references are saved as cell references in previous version (Excel97-2003) file formats ie. ".xls".
g- Save/Save As: Every time Excel 2007 opens a .xnv file, a message box pops up informing that the file is
corrupted. This pop-up message cannot be disabled. The user needs to click OK and then continue working on the
layout. So, saving does not work, we need to use Save As feature of Excel 2007.
h- Print Preview -
Whenever spreadsheet has label and it is saved in excel 2003 format using Excel 2007 there is some difference in
the color of the label and when user prints the spreadsheet there is chances of label printed in the right color
format.
IE7 doesn't print preview Excel 2007 for which MS has provided a hotfix.
i- Macro layout or something that is posted on the blog - Excel 2007 has a specific format to save spreadsheet with
macro i.e. ".xlsm", so if we try to save the spreadsheet in any other format the macro information is lost and hence
resulting spreadsheet (layout) is not a valid.
Features that need to be verified with Excel 2007 “normal” mode:
a- Redrill may fail as it creates a new xls file from xls file which is macro free spreadsheet.
b- Using nplosion which would expand to more than 255 columns or 64000 rows.
c- Using PS/nVision-Defined Names.

d- EnablePollDialogs feature.

e- Using PS/nVision API Functions.
f- Using PS/nVision VBA Interface.
g- Using PS/nVision in Remote Desktop where network is slow.
h- Using PS/nVision for Win2003 SP2 for COM Initialize and COM Uninitialize statements.
i- Creating new toolbar buttons in PS/nVision toolbar.
j- Macro Security for making macros run.
k- Cells containing embedded URL to calculate values from remote data source.
l- User opening an Excel workbook in Excel 2007 by using a hyperlink that contains a query string as part of the
URL.
m- Using PS/nVision StyleSheet might not show the proper required format when the report result is generated.
So one needs to take care that PS/nVision runs within the limits of “Compatibility” mode and need to apply proper
workarounds whenever PS/nVision crosses these limits. Any Report Request of PS/nVision, which doesn’t fall
within these boundaries, is bound to fail.
** There is an enhancement request opened with Development for optionally taking advantage of new capabilities
of Excel 2007. These enhancements are addressed under Incident # 1629231000.
Please also review the Solution # 201066688 (Doc ID 661373.1).

Chapter 11 - Troubleshooting Tips

Here are some guidelines to troubleshoot/pinpoint the exact root causes of any specific problems for PS/nVision in
different scenarios.
Before start working on any PS/nVision issue, it is necessary that one should know about the exact issue
and exact configuration of PeopleSoft environment. For pin pointing the exact reason behind any issue,
there are certain points/guidelines, which one should always check. This will help in understanding the
main cause behind the issue and trouble-shooting it.
One can run PS/nVision in 2-tier client as well in Web environment, so the first question should be:
1- Please check if the issue is appearing in 2-tier client environment or in Web environment?
Troubleshooting steps (for 2-tier):
1- Please check if users are running on certified PeopleTools/Excel/Workstation O/S combination. One can verify
with Customer Connection whether Users are on certified combination or not. If not, please BE on certified
combination. In many of the cases, one finds that this is the main reason behind the issue.
2- Please check if this issue is happening in 2-tier environment only or in Web environment or in both the
environments.
A- If this issue is happening only in 2-tier, verify whether this issue is happening with all the workstations or with
certain workstations.
a- If this issue is with certain workstations:
1- Please check all the Directory locations under PS/nVision tab in Configuration manager are put
correctly.
2- One can try with “Workstation Installation”. Please refer Resolution # 687760 (Doc ID 609003.1) that
gives users correct idea how to perform Workstation Installation correctly.
3- If the problem persists, please try un-installing Excel on this workstation and then re-install it, as the
issue could be that the Excel is not registered properly.
4- If the problem persists the issue could be that PSNVS.exe is not registered properly on this
workstation. In this case, please ask customer to register PSNVS.exe manually on this workstation.
5- Also, please check if there is any orphaned PSNVS.exe or Excel.exe in Task Manager> Processes. If
there is any, please kill them.
6- If the problem persists, the issue could be with the registry of this workstation. Please refer
Resolution # 200978054 (Doc ID 640433.1) that is available in customer connection. It suggests to
Use Regmon (www.sysinternals.com) to fix registry issues.
b- If this issue is happening with all workstations (2-tier):
It happens rarely as there is very simple configuration for PS/nVision for running in 2-tier client and one may
always check the above points. Besides that one can check the below points.
1- Please check Users are purring correct PS-HOME and DBBIN path under Process Scheduler tabs in
Configuration manager.
2- Check if Users are on certified combinations.
3- There could be a network issue.

Troubleshooting steps (for Web):

If this issue is happening in Web Environment only, please check the below points:
1- If issue is happening on intermittent basis or on regular basis.
On Intermittent basis:
If the issue is happening on intermittent basis, this indicates that basic setup for running PS/nVision is perfectly
fine otherwise user would not be able to run PS/nVision reports even for a single time.
a- Most of the intermittent issues related to PS/nVision reports happen due to cache at Application Server and
Process Scheduler level. So, please try deleting Application Server cache and reboot the Application server
domain. Also, it is recommended as well to delete Process Scheduler cache and reboot the Process Scheduler
domain. Now test.
b- There is a known issue for PS/nVision in present PeopleTools releases (PeopleTools 8.47 onwards) that
users intermittently encounter error like “SQL error 416 Error Position 28 return 0 Invalid Cursor Number“,
when running in web environment. As a workaround, please add one DBFLAGS key in “PSTOOLS” section in
PSPRCS.cfg file (Process Scheduler configuration file).
Please check Resolution # 201009382 (Doc ID 647253.1).
c- Please check the “MAX Concurrent settings” for PS/nVision in “Server “ Definition. If it is low, please
increase it to some higher number. This defines how many number of simultaneous PS/nVision processes one
can run in any specific environment. So, if the usage is high for PS/nVision, it is always suggested to have
some higher values for PS/nVision.
d- Check if there is any orphaned PSNVS.exe or Excel.exe in Task Manager >Processes on Process
Scheduler box. If there is any kill them and now test. There was a known issue with Development for
PeopleTools 8.42.
e- Try uninstalling Excel on the Process Scheduler box and then reinstall it with the user having Administrator
rights.
On Regular Basis:
If the issue is happening on regular basis, this indicates that issue could be with the PS/nVision Configuration for
Web environment.
a- Please check the directory locations for the PS/nVision, under PS/nVision section in PSPRCS.cfg file.
Correct them and then reboot the Scheduler domain to get these changes into affect.
b- Please check the Process Definition for PS/nVision is setup correctly in this environment. Users may
navigate the correct page by this navigation
PeopleTools > Process Scheduler > Process Definition
c- Try uninstalling Excel on the Process Scheduler box and then reinstall it with the user having Administrator
rights.
d- BeaProcMgr service should be logged in as “This Account”.
e- Check the Process Scheduler logs for errors when running PS/nVision reports.
f- Please check ICE for any known issues with PS/nVision reports.

2- Check if this issue is happening with all the PS/nVision reports or certain PS/nVision reports?
If with all reports:
a- If the issue is happening with all the PS/nVision reports, it means that issue coule be because of wrong
configuration and one can always check the above points for PS/nVision configuration.
If with some specific reports:
b- If the issue is happening with only one PS/nVision report or some specific PS/nVision reports, one should
check the below points.
1- In these type of issues one should look into the SQL, which is running behind that specific problem
PS/nVision report. To capture the SQL one have to check the "Show Report SQL" option. This option would be
available on Options dialog box by selecting PS/nVision, Options from the toolbar of Excel sheet.
Open Layout --> PS/nVision --> Options --> "Show report SQL" checkbox
This option helps us in troubleshooting issues with single PS/nVision report or issues with some specific
PS/nVision reports. Please turn on "Show Report SQL" option and run this report.
Copy the SQL statements and then run that SQL directly in Query Analyzer (2-tier) and check if users are
getting the correct results. If users are not getting the correct results there, then the issue is at the SQL
level and one has to correct it.
2- If users like to see what exactly the criteria is passed in any specific PS/nVision report, users can select
“Show Row and Column Criteria” in the above image. By this user will get to know about the fields, Trees
etc used in that specific PS/nVision report.
In this way users will see criteria in the column “A” of the excel sheet. Please review the screenshot, below.

It has some entry in Column “A”, like this:
%,FACCOUNT,TGASB_ACCOUNTS,NCASH
One can read these criteria as “F” is indicating that Field is “Account”. “T” is indicating that “Tree” Used is
“GASB_ACCOUNTS” and “N” indicates “Node” is “Cash”
3- One can turn on the PS/nVision Trace in PSPRCS.cfg file. One can set Trace for some higher values “4”
and can capture the deeper execution details of that specific PS/nVision report. The output of that trace
would be available at
•Client: c:\temp\psnvs_<process_id>.nvt
•Web: View Log/Trace link under Process Details
4- One can run PS/nVision report by “Foreground” method on the Scheduler box. In this way one can capture
all the execution for that PS/nVision report, which usually happens at the backend, would be appear on the
screen. In this way if there is an error at the execution level, it would be appear on the screen. One can
capture that and start troubleshooting on that basis.
For running PS/nVision in “Foreground” method, start BeaProcMgr service as a "Local Account" with Check
on the box for "Allow service to interact with desktop".
Go to Windows Start >> Settings >> Control Panel >> Administrative Tools >> Services Double click on
BeaProcMgr service. Go to Log on as tab
Select Local System account Radio button and Check on the box which says Allow service to interact with
desktop.

5- Please check if user is able to run the same PS/nVision report in any other web environment. If yes, please
compare the Process Definitions of that PS/nVision report in both the environments. If there is any
difference, please correct that. It may help in fixing the issue.
6- Users may also check the command line parameters that are being passed for that PS/nVision report. Ask
users’ if they are able to run report directly from command line. For parameters, one can navigate to
Process Monitor > Details (against the report) > Process Detail page > Parameters link
Troubleshooting steps for Drilldown
There are certain tips to pinpoint the exact reasons behind any issues with performing Drilldown.
1- Check if the issue is happening with certain Drilldown or with all the Drilldowns.
If with certain Drilldown:
1- Please check the SQL running behind that PS/nVision Drilldown and see if it is getting the correct results in
Query Manager.
2- Please check if users are not using any invalid character in parent PS/nVision report name. It should not
contain spaces, wild character such as !,@,%,&,*,( or periods.
3- Check in ICE for any specific issues reported for these Drilldowns
4- If the issue is happening with that Drilldown only in Web environment, please check whether the same
Drilldown correctly in 2-tier client.
5- If the issue is in Web environment or users are getting that specific Drilldown in Web, please make sure that
users have registered this Drilldown properly for each server.

6- Please check if the issue is happening with only larger set of data, as there is certain limitation with
MSEXCEl of 256 columns.
Please check Resolution # 201042761 (Doc ID 654934.1) for the same.
If with All Drilldowns:
In 2-tier:
1- Please check if the Drilldown folder location is correct in Configuration Manager > PS/nVision
2- Please make sure that DrilltoPIA.xla file is installed properly on that workstation. Users can call GSC for
latest version of DrilltoPIA.xla according to usersr PeopleTools version.
3- Please check “Browse in Same Window” option checked for Excel.
Go to Tools >> Folder Options >> File Types Select .xls Click on Advanced push button and Check on browse
in the same window check box.
In Web Environment:
1- Please check if Drilldowns are running successfully on newly PS/nVision reports. If yes and the issue is
happening only for the parent PS/nVision reports which were run in past and Drilldown is performed on them,
the issue could be that the instance of parent PS/nVision report is not available in Report Repository.
The reason for this is that when doing the PS/nVision drilldown, the process attempts to copy the PS/nVision
report from the report repository to the PS/nVision instance directory on the process scheduler server, where
it can then perform the drilldown. So, it is must be that instance of parent PS/nVision report is there in “Report
Repository”.
The PS/nVision reports must exist in the PS_CMD_LIST table and the report repository in order to do the
drilldown.
2- If the issue is happening on the Drilldowns for which the parent PS/nVision reports ran to “File” output type,
please make sure that “EnableDrillDownDownForFile” parameter is et to “1”.
“EnableDrillDownDownForFile” parameter is introduced by PeopleTools 8.43 and supports DrillDown on File

output type reports in the web-based PS/nVision environment. The setting only takes effect when the report
request is defined to run in File output type on the web.
Indicate whether users want to enable drilldown on a report with the output type of file.
1 = Enable drilldown.
0 = Disable drilldown. (Default).
3- Please also check the settings under DrillDown dir in PSPRCS.cfg file.
[PS/nVision] ;
========================================================================= ;
General settings for PS/nVision
DrillDownDir=%PS_HOME%\PS/nVision\LAYOUT\DRILLDN
InstanceDir=%PS_HOME%\PS/nVision\INSTANCE
After making any changes, please reboot the Process Scheduler

4- If the issue is Drilldowns are going to “Posted” status on the Process Monitor page, please check users
Report Node definition.
The “operating system” field on “Report Node Configuration” page, must be set to O/S of the WebServer i.e. To
the O/S of the box where report node URL is pointing. After that reboot the scheduler. So please check if
users specify the values in the report node configuration correctly to guarantee that the drilldown will work
successfully. One may navigate to “Report node Definition” page in web environment:
PeopleTools > Process Scheduler > Report Nodes
5- Please try rebooting the Web Server if all above points are correct.
6- Please check PSPRCS.cfg file for any Error messages related to Drilldown. Users may check ICE for any
known issues for Drilldowns.
With some specific users:
If only some of the users are not able to perform Drilldowns in Web environment, please check below points:
1- Please add permission list PTPT1200 to the user's profile.
2- Update the Web Libraries tab on the primary permission list to include WEBLIB_RPT "FULL ACCESS".
WEBLIB_RPT is the script that produces the "processing page".
3- Please check if “PS/nVision” and “REPORT_BOOKS” pages are attached with the Permission List of user.
Performance related issues with PS/nVision reports
Please refer a document that is available on customer connection for understanding how exactly the Trees and
different performance options work for PS/nVision reports.
This document is available in Customer Connection at below given URL:
URL:
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=843107.1
Important Logs: (for troubleshooting purpose)
Below are the logs, which users can always refer for checking the errors.
1- Log/Output Directory:
This log is located at: %PS_HOME%\appserv\prcs\Domain Name\log_output
2- Process Scheduler logs and Distribution Agent Log:
These logs are located at:
%PS_HOME%\appserv\prcs\Domain Name \LOGS
It contain Log files DSTAGNT_Date & SCHDLR_Date
3- PS/nVision Traces:
When users will set the Trace options in PSPRCS.cfg file for “PS/nVision”. Trace files will be located at:
a- Client: c:\temp\psnvs_<process_id>.nvt
b- Web: View Log/Trace link under Process Details

Some Important Resolutions
200756612 (Doc ID 620653.1): How to setup drilldown to run outside of the web?
200776624 (Doc ID 624174.1): "Users are not authorized to access this page" error when attempting drilldown
200768153 (Doc ID 622627.1): ISSUE: Problem with memory errors when running PS/nVision on the Process
Scheduler
200951257 (Doc ID 635847.1): E-NV: PS/nVision reports run on win XP/Win2003 machine error when machine is
locked
200953642 (Doc ID 636310.1): E-NV: PS/nVision drilldown menu does not display the drilldown option using
XL2003
200956718 (Doc ID 636864.1): E-NV: "Access Denied, unable to post files to repository" doing web drilldown
201009382 (Doc ID 647253.1): E-NV PT 8.47 PS/nVision Report Requests, Report Books Intermittently error out
200778054 (Doc ID 624427.1): "PS/nVision: Getting error when trying to access Report Request in 8.44"
200770135 (Doc ID 622973.1): E-NV: PS/nVision reports timeout when running over 15 minutes after upgrade to
8.44
200949219 (Doc ID 635485.1): E-NV: Getting error that DrillDown is not allooned for this file from Web
200976598 (Doc ID 640188.1): E-NV: Ability to save a copy of PS/nVision to file when run to email, printer, web
201066688 (Doc ID 661373.1): E-NV/QR: Excel 2007 does not recognize the format message
200765265 (Doc ID 622158.1): E-CR/NV: Crystal and PS/nVision output reflecting that wrong language has been
selected
201048723 (Doc ID 656499.1): E-NV/DR: PS/nVision/Drilldown run to Success after 15min status Error/Win
2003SP2
201070039 (Doc ID 662397.1): E-NV: PS/nVision hangs on Windows 2003 SP2 on PeopleTools 8.49.07 onwards
Doc ID 815983.1: E-NV: “Excel Interface Exception, E:\pt84918b-retail\peopletools\src\psnxl\gridapp.cpp:2048” on

Windows 2008

Appendix A – Validation and Feedback

This section documents that real-world validation that this Red Paper has received.
CUSTOMER VALIDATION
PeopleSoft is working with PeopleSoft customers to get feedback and validation on this document. Lessons
learned from these customer experiences will be posted here.

References
1- People Books
All version of People Books available in MetaLink at below given URL:
URL:
http://my.oracle.com/portal/page/myo/global/PeopleSoft%20Portal/Train_Doc:PeopleBooks%20Library
2- Performance Document by Lakshmi Maddila, which is available in MetaLink at below given URL:
URL:
3- PS/nVision Red Paper (2004)
This Red Paper is available in MetaLink at below URL:

PS/nVision Configuration & Troubleshooting Tips

By Sandeep Verma
[August] 2007
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
Copyright © 2006, Oracle. All rights reserved.
This document is provided for information purposes only and the
contents hereof are subject to change without notice.
This document is not warranted to be error-free, nor subject to any
other warranties or conditions, whether expressed orally or implied
in law, including implied warranties and conditions of merchantability
or fitness for a particular purpose. One specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document. This document
may not be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without our prior written permission.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle
Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.

RP Nvision Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RP Nvision Guide

Uploaded by

Copyright:

Available Formats

PS/nVision

T I TLE OF P AP E R PS/nVision and Troubleshooting Tips

Reference Number: PTOOLS001

Chapter 1 - Executive Overview ...............................................................................................................................6

Chapter 2: PS/nVision ................................................................................................................................................8

Chapter 3: Main Components of PS/nVision report ..............................................................................................10

Chapter 4 - PS/nVision Configuration for 2-tier client environment..................................................................14

Chapter 5 - How to run PS/nVision in 2-tier client environment .........................................................................16

Chapter 6: PS/nVision setup in Web Environment (n tier) ...................................................................................20

Chapter 7: How to run PS/nVision in Web environment.......................................................................................23

Chapter 8: PS/nVision Advanced Features ............................................................................................................27

Copyright © 2006 Oracle, Inc. All rights reserved. 3

Chapter 9: New Features in PS/nVision in PeopleTools 8.4x..............................................................................33

Chapter 10 : New Features in PS/nVision in PeopleTools 8.5x ...........................................................................36

Public and Private Report Requests in nVision Windows client 36

Chapter 11 : PS/nVision with Excel 2007/PeopleTools 8.4x/8.5x ........................................................................40

Known Issues with Excel 2007 Compatibility Mode 40

Chapter 12: Troubleshooting Tips ..........................................................................................................................42

Copyright © 2007 Oracle, Inc. All rights reserved. 4

STRUCTURE OF THIS RED PAPER

Copyright © 2007 Oracle, Inc. All rights reserved. 5

Chapter 1 - Executive Overview

Overview of PS/nVision Tool:

Copyright © 2007 Oracle, Inc. All rights reserved. 6

Copyright © 2007 Oracle, Inc. All rights reserved. 7

Copyright © 2007 Oracle, Inc. All rights reserved. 8

Copyright © 2007 Oracle, Inc. All rights reserved. 9

Chapter 3 - Main Components of PS/nVision report

PS/nVision offers two types of Report layouts.

PS/nVision > Layout Options

Copyright © 2007 Oracle, Inc. All rights reserved. 10

Feature/Function Matrix Layout Tabular Layout

PS/nVision > Layout Definition

Copyright © 2007 Oracle, Inc. All rights reserved. 11

Copyright © 2007 Oracle, Inc. All rights reserved. 12

Below are the descriptions of Fields under Report Request.

Request Name: This name identifies Report Request

** For more details, please check the “PS/nVision” section in PeopleBooks.

Copyright © 2007 Oracle, Inc. All rights reserved. 13

Chapter 4 - PS/nVision Configuration for 2-tier client environment

In 2-tier client environment:

1- Open Configuration Manager

Under Directory Paths:

Copyright © 2007 Oracle, Inc. All rights reserved. 14

Prerequisites for PS/nVision in 2-tier client for successful running

Copyright © 2007 Oracle, Inc. All rights reserved. 15

Chapter 5 - How to run PS/nVision in 2-tier client environment

Copyright © 2007 Oracle, Inc. All rights reserved. 16

Appearance of PS/nVision client:

Copyright © 2007 Oracle, Inc. All rights reserved. 17

Steps to Create a PS/nVision Report:

Copyright © 2007 Oracle, Inc. All rights reserved. 18

Copyright © 2007 Oracle, Inc. All rights reserved. 19

Chapter 6 - PS/nVision setup in Web Environment (n tier)

Main advantages in Web:

1- Internet versions of Report Requests, ReportBooks and Scope Definitions

PS/nVision configuration for Web Environment:

Copyright © 2007 Oracle, Inc. All rights reserved. 20

BEAPROCMgr Tuxedo Service:

Process Scheduler Configuration:

%PS_HOME%\appserv\prcs\Domain name \PSPRCS.cfg

Below are settings for PS/nVision in PSPRCS.cfg file.

Copyright © 2007 Oracle, Inc. All rights reserved. 21