Vista Plus Interface For Oracle E-Business Suite User Guide PDF

Vista Plus Interface for Oracle EBusiness Suite
Users Guide
This book tells Vista Plus Administrators how to use the Vista
Plus Interface for Oracle E-Business Suite.
10081500.3
Copyright 20002005 by Open Text Corporation. The copyright to these materials and any accompanying
software is owned, without reservation, by Open Text. These materials and any accompanying software may not be copied
in whole or part without the express, written permission of Open Text.
Open Text Corporation is the owner of the trademarks Open Text, Great Minds Working Together, Livelink, and
MeetingZone among others. This list is not exhaustive. All other products or company names are used for identification
purposes only, and are trademarks of their respective owners. All rights reserved.
Open Text Corporation provides certain warranties and limitations in connection with the software that this document
describes. For information about these warranties and limitations, refer to the license agreement entered into between the
licensee and Open Text Corporation.
Written by Robert Shelton
Contacting Us
Corporate Headquarters
Open Text Corporation
185 Columbia Street West,
Waterloo, Ontario
N2L 5Z5
Canada
(519) 888-7111
If you subscribe to our Software Maintenance Program or would like more information about additional support
programs, visit Open Text Customer Support at http://www.opentext.com/services/support.html.
If you have suggestions for this publication, send an e-mail message to documentation@opentext.com to contact the Open
Text Publications Group.
Visit our home page at http://www.opentext.com for more information about Open Text products and services.
ii
Table of Contents
Chapter 1
Introduction................................................................................................................................... 1
Features.................................................................................................................................... 2
About This Book ....................................................................................................................... 3
Chapters in This Guide ..................................................................................................... 3
Conventions in This Guide ............................................................................................... 4
Vista Plus Products .................................................................................................................. 5
Chapter 2
Product Overview......................................................................................................................... 7
General Description................................................................................................................ 8
Two Methods: Full and Managed Synchronization............................................................. 9
Report Capture and Synchronization Method ........................................................... 10
How the Data is Transferred................................................................................................. 11
Relationship of Oracle Applications Data to Vista Plus Data .......................................... 12
Report Security ...................................................................................................................... 14
Responsibilities, Groups, and Folders............................................................................ 14
The Private Folder Option .............................................................................................. 14
Page Level Security ........................................................................................................ 15
Procedure Overview ............................................................................................................ 16
Full Synchronization Procedure ..................................................................................... 16
Managed Synchronization Procedure......................................................................... 17
Multiple Vista Plus Warehouses or Oracle Applications Databases ............................... 19
Chapter 3
Installation................................................................................................................................... 21
Compatibility ......................................................................................................................... 22
Requirements for Installation ............................................................................................... 23
Oracle Applications Requirements .............................................................................. 23
Vista Plus Requirements ................................................................................................. 23
Oracle Applications Server Configuration .................................................................. 23
Installation Overview ............................................................................................................ 24
The Installation Files ........................................................................................................ 24
Installation on the Oracle Applications Server .................................................................. 25
Extracting the Vista Plus Interface for Oracle Applications Files............................... 25
Installing the Vista Plus Interface for Oracle Applications ......................................... 26
Installing Forms....................................................................................................................... 30
iii
Starting the Vista Plus Interface for Oracle Applications ................................................. 33

Uninstalling Vista Plus Interface for Oracle Applications .................................................. 34
Removing Data from Vista Plus..................................................................................... 34
Deleting the Vista Plus Interface for Oracle Applications ......................................... 36
Chapter 4
System Profile Settings ............................................................................................................... 39
System Profile Introduction................................................................................................... 40
Required System Profile Settings ................................................................................... 40
Configurable System Profile Settings ............................................................................ 40
Viewing and Changing System Profile Settings................................................................. 43
Chapter 5
Defining the Vista Plus Server Host............................................................................................ 45
Determining a Synchronization Method ............................................................................ 46
Setting Interface Options ..................................................................................................... 47
Capture Method ............................................................................................................ 47
Capture On or Off for Full Synchronization.................................................................. 48
Capture On or Off for FSG Ad hoc Reports................................................................. 48
FSG Detail Capture On or Off ....................................................................................... 49
Passwords ........................................................................................................................ 50
Overriding Selective Synchronization........................................................................... 51
Synchronizing from Multiple Databases ............................................................................. 52
Synchronizing with Multiple Vista Plus Servers .................................................................... 53
Entering Vista Plus Server Information ................................................................................. 54
Deleting a Vista Plus Server ........................................................................................... 57
Chapter 6
Transferring Data Using Full Synchronization ........................................................................... 59
First-Time Data Transfer ......................................................................................................... 61
Initializing the Interfaces Oracle Applications Database......................................... 61
Selecting Users to Have Private Folders ....................................................................... 63
Selecting Reports to Link to Private Folders ................................................................. 64
Copying the Data into Vista Plus .................................................................................. 66
Scheduling Updates ............................................................................................................. 67
Capturing Reports................................................................................................................. 69
iv
Chapter 7
Transferring Data Using Managed Synchronization................................................................ 71
First-Time Data Transfer ......................................................................................................... 74
Initializing the Interfaces Oracle Applications Database......................................... 74
Selecting the Responsibilities to Transfer...................................................................... 76
Selecting the Users to Transfer....................................................................................... 78
Forcing Users Into a Vista Plus Group ........................................................................... 80
Adding Employees to a Vista Plus Group .................................................................... 82
Adding Sales Reps to a Vista Plus Group..................................................................... 84
Selecting the Reports to Transfer .................................................................................. 85
Selecting the Destination Report Warehouse ............................................................. 87
Copying the Data into Vista Plus .................................................................................. 89
Capturing Reports................................................................................................................. 90
Updating Vista Plus Information .......................................................................................... 91
Synchronizing Data in the Interfaces Database........................................................ 91
Selecting the Information to Update ........................................................................... 93
Sending the Updates to Vista Plus ................................................................................ 94
Chapter 8
Using Page-Level Security ......................................................................................................... 95
Page-Level Security Overview............................................................................................. 96
Page-Level Security by User................................................................................................. 97
Page-Level Security by Group........................................................................................... 101
Defining Page-Level Security for Other Groups ........................................................ 105
Creating the Page-Level Security in Vista Plus.......................................................... 109
Chapter 9
Capturing Reports .................................................................................................................... 111
Capture Overview .............................................................................................................. 112
Selecting Printers for Immediate Capture........................................................................ 114
Selecting the Reports to Capture ..................................................................................... 116
Printing Reports for Capture .............................................................................................. 118
Scheduling the Report Capture Request......................................................................... 119
Retrieving Missing Reports .................................................................................................. 121
Retrieving a Specific Missing Report........................................................................... 121
Retrieving All Reports for a Date Range .................................................................... 122
Reprinting Reports............................................................................................................... 124
Removing Reports from the Capture Table..................................................................... 125
Linking, Unlinking, and Deleting Reports .......................................................................... 126
The Link/Unlink/Delete Report Form ........................................................................... 126
Chapter 10
Monitoring Interface Activity................................................................................................... 129
Monitoring Report Capture ............................................................................................... 130
Listing Information Sent to Vista Plus ................................................................................. 135
The Process Log Form ......................................................................................................... 137
The Vista Plus Error Log........................................................................................................ 139
Appendix A
Files Installed............................................................................................................................. 141
Files Installed on the Oracle Applications Server ............................................................ 142
Files Installed on the Middle Tier or Oracle Client Manager .......................................... 145
Appendix B
Configuring the Interface to Work With Vista Plus Output Manager ................................... 147
General Information ........................................................................................................... 148
Install the qr Command ..................................................................................................... 149
Copy and Edit the qmOrapToVistaPlus file ....................................................................... 150
Create an Output Manager Queue ................................................................................ 151
Configure the Interface System Profile............................................................................. 152
Appendix C
Requests Included in the Interface ........................................................................................ 153
Index.......................................................................................................................................... 157
vi
Chapter 1
Introduction
The Vista Plus Interface for Oracle Applications creates connections between your Oracle
Applications database and your Vista Plus report warehouse. It saves you time and
effort by automatically performing two functions you would otherwise have to do
manually:
It updates the Vista Plus data structuresusers, groups, folders, and reportsbased
on changes to your Oracle Applications data.
It captures reports you print in Oracle Applications into the Vista Plus report
warehouse for electronic distribution.
Note
Oracle has changed the name of Oracle Applications to Oracle E-Business

Suite; we updated the name of this document to match. However, since the
large installed base of Oracle Applications users are familiar with the older
name, we refer to Oracle Applications rather than Oracle E-Business Suite
throughout this manual.
In This Chapter
Features ....................................................................................................... 2
About This Book ........................................................................................ 3
Vista Plus Products .................................................................................... 5
Introduction
Features
Features
These are some of the features in the Vista Plus Interface for Oracle Applications:
One-time setup of information to share between Oracle Applications and Vista Plus.
Supports both standard and ad hoc FSG (Financial Statement Generator) reports. You
can capture FSG reports to a special Vista Plus folder structure based on the report set,
period, and segment override or content set entry.
You decide how frequently information is synchronized; Vista Plus Interface for
Oracle Applications follows the schedule you set.
Oracle Applications responsibilities and users become Vista Plus groups, folders, and
users.
Oracle Applications reports become Vista Plus reports; individual report runs become
Vista Plus report generations.
All new users, responsibilities, and reports can be automatically added to Vista Plus,
or you can select only the ones you want to have transferred.
Limited individual user page-level security based on user, employee, or sales rep ID
or name, including support for sales rep hierarchies.
Limited group-based page-level security based on value sets and security rules.
You can monitor the Vista Plus capture table to see what reports are waiting to be
captured at any time.
Of course, once your Oracle Applications reports are in the Vista Plus report warehouse,
you have all the benefits of Vista Plus: electronic instead of printed distribution, page
security and bursting, full-text and indexed searches, and more. Please see your Vista Plus
documentation for complete information.
Vista Plus Interface for Oracle E-Business Suite Users Guide
About This Book
About This Book

This book describes how to use the Vista Plus Interface for Oracle Applications. While it
discusses Vista Plus and Oracle Applications concepts and product structure and how
they relate to each other, it is not a complete guide to either Vista Plus or Oracle
Applications. For more information on Oracle Applications, please refer to your Oracle
Applications documentation. For information on any part of Vista Plus, please see the
Vista Plus documentation or help files.
The Vista Plus Interface for Oracle Applications runs on an Oracle server using UNIX.
This manual assumes you are familiar with your operating system and know how to use
its basic commands and features, such as the vi editor. It also assumes you are familiar
with basic Oracle Applications procedures, such as logging on and selecting a
responsibility, and with common Windows functions.
All of the procedures and pictures of Oracle Applications forms in this book are for Oracle
Applications 11i. If you are using another version, the procedures and forms will be
slightly different.
Chapters in This Guide

Chapter 1
Introduces Vista Plus Interface for Oracle Applications
Chapter 2
How the Vista Plus Interface for Oracle Applications works: what it does
for you and how it does it
Chapter 3
Installing Vista Plus Interface for Oracle Applications
Chapter 4
Checking and, if needed, modifying the interfaces system profile

settings.
Chapter 5
Defining the Vista Plus report warehouse or warehouses to transfer

information to
Chapter 6
Keeping information synchronized between Oracle Applications and

Vista Plus using full synchronization
Chapter 7
Keeping information synchronized between Oracle Applications and

Vista Plus using managed synchronization
Chapter 8
Capturing report runs from Oracle Applications into the Vista Plus report
warehouse
Chapter 9
The monitoring and reporting features included in Vista Plus Interface for
Oracle Applications
Introduction
About This Book
Conventions in This Guide

To make our information and procedures easier to understand, all Vista Plus
documentation uses a standard set of typefaces and icons. These conventions are:
Dialog Box
Dialog box titles are in standard type with the first letter of each word
capitalized.
command
The names of commands are shown in bold.
Field name
The names of fields and buttons on dialog boxes are in bold type. We use
the same capitalization as on the dialog box.
username
UNIX and Oracle user names are given in italics.
file path
Directory and file names and paths are in italics; so are Vista Plus user,
group, report, folder, and other item names.
display
Text and prompts displayed on your screen are in this Courier typeface.
syntax
When were talking about the syntax of a command you type, the
command line is shown in this bold Courier typeface. It is generally, but
not always, also set off from other text. Parts of the line may also be in
italics and/or enclosed in brackets, as discussed below.
We also use this typeface for entries you type at the operating system
prompt or in a dialog box field.
variables
If part of a syntax statement is given in italics, you dont type the word
shown, but substitute a value for it instead. For example:
copy myfile
Myfile is in italics because you dont actually type myfile, you
substitute the proper file name.
[options]
Optional parts of a command syntax or program entry are in brackets.

When entering the command, do not include the brackets.
references
When we refer to part of a command syntaxfor example, to explain

possible entries for a parameterthe first reference is in this bold italic
typeface. Further references are in normal type unless that would be
confusing, in which case they are also in bold italic type.
emphasis
At times, particularly important text is in this bold italic typeface to

draw your attention.
Vista Plus Products
Vista Plus Products

Vista Plus Interface for Oracle Applications is part of a family of products available from
Open Text Corporation. For information on any of these products, contact your Open Text
representative.
Vista Plus Server
Home to the Vista Plus report warehouse. Users throughout

your enterprise use Vista Plus Web View or Vista Plus
Windows Client to connect to the server to view reports.
Designed for today's global networks, the Vista Plus server
runs on leading UNIX platforms and supported server
versions of Windows.
Vista Plus Web View
Installs on the Web server and can be used by anyone with a

supported Web browser. It allows both remote and local
users to view Vista Plus reports. It provides an intuitive user
interface for report viewing by users at all skill levels.
Vista Plus Windows

Client
Runs in supported versions of Windows. Like Web View, it

provides an intuitive user interface for report viewing by
users at all skill levels. It includes report capture tools for
capturing files from PCs.
Vista Plus Interface for

SAP R/3
Automatically matches user, group, and authorization

profiles, as well as SAP R/3 report tree structure
information, between the SAP R/3 application and Vista
Plus. It also provides automated, ongoing synchronization of
these elements without any code modifications to the SAP
R/3 system. This ensures error-free updates and report data
security. This tight integration with SAP R/3 assures Vista
Plus users timely and accurate access to SAP R/3
information from virtually anywhere.
Vista Plus Interface for

PeopleSoft
Automatically matches user, group, and authorization

profiles between the PeopleSoft application and Vista Plus. It
also provides automated, ongoing synchronization of these
elements without any code modifications to the PeopleSoft
system. This ensures easy updates and report data security.
This tight integration with PeopleSoft assures Vista Plus
users timely and accurate access to PeopleSoft information
from virtually anywhere. Reports generated by PeopleSoft
HR, Financials, and other modules or by users using nVision,
Crystal Reports, SQRs, or custom reports can all be captured
into Vista Plus. With TransVue Capture, nVision files can also
be captured in their native Microsoft Excel format.
Introduction
Vista Plus Products
Chapter 2
Product Overview
This chapter describes what Vista Plus Interface for Oracle Applications can do for you,
and how it does it. It does not include any instructions for using the product; those begin
in Chapter 4, after the installation procedure in Chapter 3. The information in this chapter
lets you know the capabilities of the product, how your Oracle Applications data becomes
Vista Plus data, how the various Vista Plus Interface for Oracle Applications features fit
into your work flow, and what the software is doing behind the scenes when you use a
feature.
In This Chapter
General Description .................................................................................. 8
Two Methods: Full and Managed Synchronization ............................. 9
How the Data is Transferred .................................................................. 11
Relationship of Oracle Applications Data to Vista Plus Data ........... 12
Report Security ........................................................................................ 14
Procedure Overview ............................................................................... 16
Multiple Vista Plus Warehouses or Oracle Applications Databases 19
Product Overview
General Description
General Description
Vista Plus Interface for Oracle Applications greatly reduces the time and effort needed to
administer your Vista Plus installation. It can automatically keep your Vista Plus report
warehouse in step with your Oracle Applications database, with very little interaction
from you required. It does this by copying, either on a schedule or when you request it,
information from your Oracle Applications database to Vista Plus. It can copy either all
responsibilities, users, and reports or only the ones you select.
Vista Plus Interface for Oracle Applications performs one-way synchronization:
information is copied from Oracle Applications to Vista Plus. Changes or additions you
make in Vista Plus are not copied back to the Oracle Applications database. In fact,
changes you make in Vista Plus to users, groups, or reports that exist in Oracle
Applications may be overwritten the next time synchronization takes place.
Besides copying user, responsibility, and report information to Vista Plus, the interface
also automates report capture. Each time you run an Oracle Applications report, the
interface checks to see if it is selected for capture to Vista Plus and, if so, captures it
automatically as a report generation. Capture can be performed immediately when the
report is run or later by a report capture request.
Two Methods: Full and Managed Synchronization

Vista Plus Interface for Oracle Applications offers two synchronization methods for you to
choose from, full synchronization and managed synchronization:
Full synchronization does just what the name suggests: once youve set up a schedule,
the interface transfers all the relevant Oracle Applications data to Vista Plus with no
further action from you. You can still use the private folders option, as described on
page 14.
Managed synchronization gives you more control over the data to be transferred:
using custom forms provided with Vista Plus Interface for Oracle Applications, you
select exactly which informationusers, responsibilities, and reportsto copy to
Vista Plus. You can also choose to assign additional Vista Plus groups to Oracle
Applications users, and create Vista Plus users from Oracle Applications employee
and/or sales representative records (see page 12 for more information). This enables
you to give people access to report data in Vista Plus without letting them manipulate
the data or run reports in Oracle Applications. You can also choose to implement Vista
Plus page-level security for one or more reports based on the Oracle Applications
user, employee, or sales representative ID or name for individual users, or on value
sets and security rules for groups.
Each method has its advantages and disadvantages. While full synchronization requires
almost no effort on your part, it also gives you little control over the information to be
synchronized. All users, responsibilities, and reports are transferred to the Vista Plus
report warehouse. This may mean that information you dont want, such as test users or
obsolete reports, are created in the warehouse. On the other hand, except for taking up
space, having the extra data does not generally do any harm.
Managed synchronization gives you complete control over the information synchronized:
each time the synchronization process runs, you choose the users, responsibilities, and
reports to include in the transfer. It also enables you to transfer employees and sales reps
to Vista Plus and use the page-level security features. While the custom Oracle
Applications forms make this process easy, you must take some time and make some
decisions each time you synchronize Vista Plus with Oracle Applications.
Note
Important! If you choose full synchronization, you can later switch to

managed. However, if you choose managed synchronization, you cannot later
switch to full.
If you are synchronizing data with more than one report warehouse, you
must use managed synchronization.
Product Overview
Report Capture and Synchronization Method

With managed synchronization, after selecting the reports to transfer to the Vista Plus
warehouse (creating the report structure), you choose which of those reports to capture
each time they are printed. This means you can create the report structure you want, but
not begin capturing reports until a time you choose.
With full synchronization, you have two choices for report capture. You can either have all
reports captured automatically each time they are run, making the entire synchronization
and capture process completely automatic, or you can choose to select just the reports you
want to have captured, as with managed synchronization.
With either synchronization method, you can also set a capture method option so report
runs are captured to Vista Plus only when you select a certain printer or number of copies.
See page 47 for more information.
10
How the Data is Transferred
How the Data is Transferred

Vista Plus Interface for Oracle Applications converts your Oracle Applications users,
responsibilities, and report definitions into Vista Plus report warehouse data in a series of
steps. Each step is performed by the programs run by a request included with Vista Plus
Interface for Oracle Applications:
The data to be transferred is placed into a database within Oracle Applications; this
database is created during Vista Plus Interface for Oracle Applications installation
and is used only by the interface. The first set of data is placed into the database by the
initialization request. During later synchronizations, this step is performed by the
synchronization request.
The information from the interfaces database is placed into text files formatted for
importing into Vista Plus. This is done by the migration request.
As information for each type of objectusers, reports, and so onis placed in the text
files, it is used to update the Vista Plus report warehouse. The process is then repeated
for the next type of object. This is also performed by the migration request.
If you are using managed synchronization, you select the users, responsibilities, and
reports to include in migration after initialization or synchronization, but before
migrationthis is after the first of these steps, but before the last two. You make your
selections using the custom forms which come with Vista Plus Interface for Oracle
Applications.
When you use full synchronization, you use the full synchronization/migration request.
This includes all the programs in both the synchronization and migration requests, and
performs all three steps in one process.
Capturing reports is handled by a different process. When a report request is run, the
interface checks to see if the report has been selected for capture. If so, the interface makes
an entry in one of the tables in its database. The report capture request reads the entries
from this table and captures the output for each listed report into Vista Plus. You can run
the capture request at any time, or schedule it to run periodically; if you schedule the
request, you do not need to take any action to create each new generation. You can also
capture reports immediately when they are run by sending the report output to one of the
printers defined for that purpose when the interface is installed.
Product Overview
11
Relationship of Oracle Applications Data to Vista Plus Data
Relationship of Oracle Applications Data to Vista

Plus Data
Since the types of data are not all the same in Oracle Applications and Vista Plus, you may
be wondering exactly how the Oracle Applications data is changed into Vista Plus data.
Obviously, an Oracle Applications user becomes a Vista Plus user, but what about an
Oracle Applications responsibility? What type of Vista Plus data does it become? This
table shows the types of Oracle Applications information kept synchronized by the Vista
Plus Interface for Oracle Applications, and how each one appears in the Vista Plus report
warehouse.
Oracle Data Type
Vista Plus Data Type
User
User. Each Oracle Applications user is added as a Vista Plus user. Some
user characteristics, such as responsibilities (groups in Vista Plus) and
expiration dates, are transferred. With managed synchronization, you
can also add users to the Vista Plus groups for responsibilities they do
not belong to in Oracle Applications.
If you choose the private folder option for an Oracle Applications user,
that user also becomes a Vista Plus folder and group. See page 14.
Employee or Sales Rep
User. With managed synchronization, you can create Vista Plus users
from Oracle Applications employee and/or sales rep records. You may
want to do this for employees who currently see paper copies of reports
(or who would benefit from seeing the reports), but who are not Oracle
Applications users. It allows you to give them access to the reports
online without entering them as Oracle Applications users.
Responsibility
Group and Folder. Each responsibility becomes a Vista Plus user group;
a folder with the same name is also created and used as the Home folder
for the group.
Employees and sales reps cannot have private folders.
12
Relationship of Oracle Applications Data to Vista Plus Data
Report
Report. For each responsibility, you select which Oracle Applications

reports to create in Vista Plus. (With full synchronization, all reports are
migrated to Vista Plus.) The report may belong to the responsibility
either through a request group or through menu security assigned to a
request group. Each report is linked to the folder for the responsibility.
If you choose to capture FSG ad hoc reports, the reports are assigned to
the General Ledger folder in Vista Plus. See page 48.
If you choose FSG Detail capture, separate reports and folders are
created based on the period and segment override or content set entry
used when running an FSG report. See page 49.
Except for FSG Detail reports, reports created in Vista Plus have a name
consisting of the SID assigned to the report warehouse (see page 55), the
concurrent program name, and the ID of the responsibility the report
was run under. The report description is the same as in Oracle
Applications, except that it may include the rcapture options used when
capturing the report. This is controlled by the PARAM System Profile
setting; see page 42 for more information.
Reports are created with the warehouse default report permission. Each
group with access to the reporteach group created from a
responsibility which can run the report in Oracle Applicationsis
explicitly assigned View permission for it.
Individual Report Run
Note
Report Generation. Each time a report is captured, it becomes a

generation of the report in the Vista Plus report warehouse. The
generation description includes the report name, the user running it,
and, for standard and FSG reports, the input parameters.
Vista Plus user names and passwords are case-sensitive. The user name can
be entered into Vista Plus in either all capitals or all lower case; this is
controlled by the CASE System Profile setting, as described in Chapter 4. You
must set this value before the first migration; you cannot change it once
youve transferred information to Vista Plus.
You can select from several different password formats for the Vista Plus
users created by the interface, and can choose to force each user to change his
or her password the first time he or she logs in to Vista Plus. See page 50 for
more about passwords.
Product Overview
13
Report Security
Report Security
Vista Plus Interface for Oracle Applications can replicate your Oracle Applications report
and data security in Vista Plus. It does this in three ways: creating groups and folders for
responsibilities, creating private folders for selected users, and implementing page-level
security by user or by group.
Responsibilities, Groups, and Folders

In Oracle Applications, access to reports is controlled by the responsibilities each user
belongs to. A user can run a report only if it is assigned to one of his or her responsibilities.
This security is maintained in Vista Plus: a group and folder are created in Vista Plus for
each Oracle Applications responsibility, and the folder is the Home folder for the group.
Each user becomes a member of the Vista Plus groups corresponding to the
responsibilities he or she belongs to in Oracle Applications. Each Vista Plus report is
linked only to the Vista Plus folders for the responsibilities with access to the report in
Oracle Applications. Since this folder is available only to members of the corresponding
group, and only users who belong to the Oracle Applications responsibility belong to the
Vista Plus group, only users who could run the report in Oracle Applications can see it in
Vista Plus. (You can also use the Force users option to allow selected users to view
reports in Vista Plus folders other than those for their Oracle Applications responsibilities.
See page 80 for more about this option.)
The Private Folder Option

If you choose, you can create folders and groups from selected Oracle Applications users,
which allows you to capture selected reports into Vista Plus for use only by the user who
ran the report. This is the private folder option.
When you use private folders, you select both the users to create folders for and the
reports to capture to the private folders. When a report marked private is run, Vista Plus
Interface for Oracle Applications checks to see who is running it. If the user has a private
folder, the report run is captured to the appropriate report in that folder; if the user
doesnt have a private folder, the report is not captured into Vista Plus. Once you mark a
report as private, it is not captured into the folder for its responsibility. You can, however,
change a report from private back to public at any time. If you do this, the report is then
captured to the report in the folder for its responsibility. A report is never captured to both
a private user folder and a responsibility folder.
Each user with a private folder belongs to a Vista Plus group for each Oracle Applications
responsibility he or she is a member of, like all users. He or she also belongs to a group
named Users Private Folder, where User is his or her user name. Each Users Private Folder
group has only one member; the user logs in to Vista Plus under this group to see the
reports that have been captured to his or her private folder, which is not accessible from
any other group. The reports created in the private folders include the users ID as part of
the report name; they are not linked to any other folder.
14
Report Security
Page Level Security

Vista Plus page-level security controls which pages of a report generation a user can see.
When page-level security is used, different users viewing the same report generation may
see different pages. The interface includes two page-level security features:
Page-level security by user creates and assigns page-level security in Vista Plus based on
the Oracle Applications user ID or name, employee number or name, or salesperson
number or name. When you base security on users or employees, the Vista Plus user
can see only pages which contain his or her own name or number. When you base it
on salespersons, you can create security based on the salesperson hierarchy, so Vista
Plus users can see pages containing their number or name, or the number or name of
anyone below them in the hierarchy.
Page-level security by group creates and assigns page-level security in Vista Plus based
on the values allowed by security rules in Oracle Applications. Users in a Vista Plus
group can see only pages which contain values allowed by the security rule for the
corresponding Oracle Applications responsibility. For each report, you define one or
more value sets and security rules to use for each group. If you dont define page-level
security for a group, users in that group cannot see any pages of the report, even if the
report is in one of their folders.
You can use either page-level security method for any report you are migrating to Vista
Plus. You can use security by user for some reports and security by group for others. The
data field (for security by user) or value sets/security rules (for security by group) to base
the page security on can be different for each report. Both types of page-level security use
report indexes you create in Vista Plus. See Chapter 8 for more information.
Product Overview
15
Procedure Overview
Procedure Overview
The basic procedure for using Vista Plus Interface for Oracle Applications is different
depending on whether you are using full synchronization or managed synchronization.
The next two sections give an overview of each procedure.
Full Synchronization Procedure

1.
After installation, check and, if necessary, modify the system profile settings for the
interface. Be sure to check all system profile values; some of them cannot be changed
after you have run the initialization request. See Chapter 4 for more information.
2.
Define the Vista Plus server or servers to copy data to. This is when you choose
managed or full synchronization and set report capture options, including selecting
any printers to use for immediate capture.
3.
Submit the initialization request. This copies your Oracle Applications data to the
interfaces database.
4.
If you are going to use any private folders, select the users to create private folders for
and the reports to capture to the private folders.
5.
Submit the migration request. This copies all information from the interfaces
database into the Vista Plus report warehouse.
6.
If you have chosen the option to select the reports to capture, either before or after the
initial migration, use the interface to select the reports you want captured. Each time a
selected report is runand meets the criteria specified in the capture method setting
(see page 47)it is placed into the Vista Plus capture table, or captured immediately if
sent to a designated printer.
If you chose to capture all reports, skip this step. Every report run which matches the
capture method setting will be placed in the Vista Plus capture table.
16
7.
Schedule the report capture request. This request takes report runs waiting in the
Vista Plus capture table and captures them as generations in the Vista Plus report
warehouse. How often to run this request depends on the number of reports you have
and how quickly you want access to them in Vista Plus; every 15 minutes is a good
starting point. You can also run the request manually at any time.
8.
If you want to use page-level security, create the needed report indexes in Vista Plus.
In the interface, select the reports to use page-level security for and whether to create
the security by user or by group. Run the page-level security by user and/or security
by group request to create the page securities in Vista Plus.
9.
Every so often, submit the full synchronization/migration request. This copies new
and changed Oracle Applications information to Vista Plus. Since you dont need to
select the information to copy, youll probably want to schedule this request to run at
regular intervals. If you do schedule it, you can also run it manually if you want to
synchronize information before the next scheduled execution.
Procedure Overview
10. As needed, update page-level security information. The full synchronization/

migration request does not do this. You must update page-level security using the
separate requests for that purpose.
Managed Synchronization Procedure

1.
After installation, check and, if necessary, modify the system profile settings for the
interface. Be sure to check all system profile values; some of them cannot be changed
after you have run the initialization request. See Chapter 4 for more information.
2.
Define the Vista Plus server or servers to copy data to. This is when you choose
managed or full synchronization and set report capture options, including selecting
any printers to use for immediate capture.
3.
Submit the initialization request. This copies your Oracle Applications data to the
4.
Define the information to copy from Oracle Applications to Vista Plus and which
Vista Plus report warehouse to copy it to. You can transfer some or all of your Oracle
responsibilities, users, and reports to Vista Plus. The interface includes custom Oracle
Applications forms you use to select the information to copy.
As part of this step, you can also assign additional Vista Plus groups to users, create
Vista Plus users for Oracle Applications employees and sales reps, select any users
you want to create private folders for, and select the reports to capture to the private
folders.
5.
Submit the migration request. This transfers the selected information from the
interfaces database to Vista Plus.
6.
If you want to use page-level security, create the needed report indexes in Vista Plus.
In the interface, select the reports to use page-level security for and whether to create
the security by user or by group. Run the page-level security by user and/or security
by group request to create the page securities in Vista Plus.
7.
Either before or after the initial migration, use the interface to select the reports you
want captured to Vista Plus; you can also do this when selecting the reports to migrate
(step 3). Each time the report is runand meets the criteria specified in the capture
method setting (see page 47)it is placed into the Vista Plus capture table, or
captured immediately if sent to a designated printer.
8.
Schedule the report capture request. This request takes report runs waiting in the
Vista Plus capture table and captures them as generations in the Vista Plus report
warehouse. How often to run this request depends on the number of reports you have
and how quickly you want access to them in Vista Plus; every 15 minutes is a good
starting point. You can also run the request manually at any time.
Product Overview
17
Procedure Overview
9.
Every so often, submit the synchronization request. This prepares new and changed
Oracle Applications information to be copied to Vista Plus; you can select the
responsibilities to include in the Synchronization. You can schedule this request at
regular intervals.
10. Select the new and changed information to transfer. As when first transferring data,
you use custom Oracle Applications forms included with the interface.
11. Submit the migration request to transfer the data youve selected. Since you need to
select the information to transfer before running this request, you probably wont
want to schedule it to run automatically.
12. Repeat steps 9 through 11 whenever you want to synchronize Vista Plus with your
Oracle Applications data.
13. As needed, update page-level security information. The synchronization and
migration requests do not do this. You must update page-level security using the
separate requests for that purpose.
18
Multiple Vista Plus Warehouses or Oracle Applications Databases
Multiple Vista Plus Warehouses or Oracle

Applications Databases
All of the discussions so far have assumed the simplest, and most common, case:
synchronizing data between one Oracle Applications database and one Vista Plus report
warehouse. However, Vista Plus Interface for Oracle Applications allows you to set up
more complex configurations, involving multiple Oracle Applications databases, multiple
report warehouses, or both.
Transferring information from an Oracle Applications database into more than one Vista
Plus report warehouse is straightforward: just define each report warehouse on the Server
form (see Chapter 5). Then, for each warehouse, select which responsibilities to transfer to
it. Information (users and reports) from each responsibility can go to one or more
warehouses. Because you need to select the destination warehouse for information before
it is copied to Vista Plus, you must use managed synchronization; you cannot use full
synchronization with more than one report warehouse.
You can also copy information from more than one Oracle Applications database into the
same report warehouse. When you do this, you need to be careful not to have data from
one database overwrite data from another. To ensure this, you must enter a unique one-tofour-character ID for each database when you define the report warehouse on the Server
form (see Chapter 5). Vista Plus Interface for Oracle Applications will insert this ID at the
beginning of all group, folder, and report names it creates with information from this
database. Thus, even if there are responsibilities with the same name in two databases, the
groups and folders created from them in the report warehouse will have unique names. If
there is any possibility of duplicate user names in the two databases, you must also set the
option to add the database ID to the Vista Plus user names. Your users will then see
information from different databases depending on the user names they use when logging
into Vista Plus.
For example, if you are copying data from two databases to the same report warehouse,
you could give one database the ID of ABCD and the other WXYZ. All Vista Plus report,
folder, and group names would start with one of these codes, letting you know where the
information originated. If you set the option, user names would have the ID added to
them; a user named Chris would log in to Vista Plus as Chris ABCD or Chris WXYZ to
see information from one database or the other.
More complex situations, with multiple Oracle Applications databases sending
information to more than one Vista Plus report warehouse, are just combinations of these
two scenarios. The two key points are to make sure all data going into a report warehouse
is uniquely named based on its Oracle Applications database, and, if you have more than
one report warehouse, make sure the correct data is going into each.
Product Overview
19
Multiple Vista Plus Warehouses or Oracle Applications Databases
20
Chapter 3
Installation
This chapter tells you how to install the Vista Plus Interface for Oracle Applications. It
describes how to perform the necessary installation on the Oracle Applications
applications server and how to install the forms for the interface on the forms server
where all the standard forms are located.
After installation, you must check system profile settings as described in Chapter 4. You
can then define the Vista Plus server host(s) to copy information to, as described in
Chapter 5.
In This Chapter
Compatibility ........................................................................................... 22
Requirements for Installation ................................................................ 23
Installation Overview ............................................................................. 24
Installation on the Oracle Applications Server ................................... 25
Installing Forms ....................................................................................... 30
Starting the Vista Plus Interface for Oracle Applications .................. 33
Uninstalling Vista Plus Interface for Oracle Applications ................ 34
Installation
21
Compatibility
Compatibility
Vista Plus Interface for Oracle Applications is compatible with Oracle Applications
versions 11.0.x, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, and 11.5.10.
The UNIX operating system on the Oracle Applications applications server must support
the vadmin command and remote capture tools for the version of Vista Plus used by the
server host(s) you are migrating data to. See the Vista Plus Server Administration Guide for
supported operating systems and versions.
22
Requirements for Installation
Requirements for Installation

Oracle Applications Requirements
Before installing the Vista Plus Interface for Oracle Applications, make sure you have all
of the Oracle Applications information and permissions you need:
Access to Oracle Applications with system administrator (SYSADMIN)

responsibilities and password
Access to Oracle Applications database tables via the Oracle SQL Plus interface
The Oracle user name and password for the Oracle Applications owner (the default is
apps)
The Oracle database System Manager (SYSTEM) password
Access to SQL Forms tools f45gen or f60gen
Access to the Oracle Applications $APPL_TOP directories
Vista Plus Requirements

All Vista Plus server host installationsreport warehousesyou want to transfer
information to with the interface must use a supported version of Vista Plus; supported
versions are listed in the interface Release Notes. Also, the root folder on all hosts must be
called MAIN. This is the default name, but it is possible to change it in Vista Plus. If you do
change it, the interface will not be able to copy information to the warehouse.
The Oracle Applications applications server where the interface is installed must be set up
as a Vista Plus remote host with access to the Vista Plus server host or hosts. The remote
capture tools installed must be the same version as on the Vista Plus server(s) you are
transferring data to. If you are transferring data to servers with different versions of Vista
Plus, you must install the matching version of the remote capture tools for each one, in
separate locations on the applications server host.
On the applications server host, the user designated as the capture user in the client.cfg
file(s) must be a Vista Plus Administrator in all report warehouses you will capture
reports to. The easiest way to ensure this is to enter Admin as the capture user.
Oracle Applications Server Configuration

The Oracle Applications database server and applications server may be on the same
physical machine or different machines. If they are on the same physical machine follow
the installation instructions in this chapter. If the database server and applications server
are on different machines, contact Vista Plus customer support before installing the
interface software. There are many possible configurations of the Oracle Applications
database server, applications server, and concurrent manager, and the steps necessary to
install and configure the interface depend on the exact server configuration at your
installation.
Installation
23
Installation Overview
Installation Overview
Installing Vista Plus Interface for Oracle Applications consists of these major procedures:
1.
Downloading the Vista Plus Interface for Oracle Applications files to the Oracle
Applications applications server. and extract the installation files.
2.
Creating the Oracle Applications QVISTA user.
3.
Running the installation script on the applications server.
4.
Installing the interface forms on the Oracle middle-tier (forms) server.
The Installation Files

The Vista Plus Interface for Oracle Applications files are available on CD or via FTP. The
table below lists the files found in each of the product folders:
Folder
Files
Description
Doc
*.pdf
An Adobe Acrobat PDF file of the

Users Manual.
New Install
qv_main.tar.Z
Contains the files installed on the

UNIX Oracle Applications
applications server for a new
installation.
qv_mid11.tar.Z
qv_mid11i.tar.Z
These tar files contain the files

installed on a UNIX middle-tier
server for releases 11.0.x and 11.5.5
through 11.5.10, respectively.
mmddyyyyvera.tar.Z
Contains the files installed on the

UNIX Oracle Applications
applications server for an upgrade.
mmddyyyyverb11.tar.Z
mmddyyyyverbr11i.tar.Z
These tar files contain the files

installed on a UNIX middle-tier
server for releases 11.0.x and 11.5.5
through 11.5.10, respectively.
Upgrade*
*: For all files in the Upgrade directory, mmddyyyy is the date the files were created and ver
is the version number of the software.
Appendix A lists the files installed on the Oracle Applications server and the middle-tier
server.
Tip
24
If you download the install file via FTP, extract all the files from it to a location
where you can copy them to the Oracle Applications applications server. This
will create the directory structure shown above.
Installation on the Oracle Applications Server

You must install the main software for Vista Plus Interface for Oracle Applications on the
Oracle Applications applications server. Installation consists of extracting the files from
the supplied .tar.Z files to the proper location on the server, then running the installation
script.
Note
These instructions are for a first time installation of the Vista Plus Interface for
Oracle Applications. If you are upgrading from an earlier version of the
interface, please refer to the upgrade instructions in the Release Notes for the
new version.
Extracting the Vista Plus Interface for Oracle Applications

Files
The Vista Plus Interface for Oracle Applications files must be extracted under
$APPL_TOP, a subdirectory of the Oracle Applications home directory. The extraction
creates a qv subdirectory under $APPL_TOP. Under qv, it follows Oracle Flexible
Architecture (OFA) structure, creating a 1.1.1 directory and several subdirectories: admin,
bin, dat, forms, install, log, mesg, out, patchsc, and sql. These directories contain files and
executables used to configure Oracle Applications to work with Vista Plus. This is similar
to the Oracle Financials directory structure.
To extract the Vista Plus Interface for Oracle Applications files

1.
If you are installing from CD, insert the installation CD in the CD-ROM drive of the
Oracle Applications applications server and, if necessary, mount it.
If you received the files via FTP rather than on CD, make sure they are in a location
where you can copy them to the applications server.
2.
Log on to the applications server as the Oracle application manager (usually applmgr).
3.
Change to the $APPL_TOP directory.
4.
Copy the qv_main.tar.Z installation file to $APPL_TOP. If you are copying from the
CD, use this command:
cp /cdrom/New Install/Unix/qv_main.tar.Z .
Cdrom is the device name for the CD-ROM drive.

If you are copying the file using FTP, be sure to use a binary copy.
Installation
25
5.
Uncompress the files and extract them by typing either these two commands:
$ uncompress qv_main.tar.Z
tar xvf qv_main.tar
Or this one, which combines and shortens the previous two:

zcat qv_main.tar.Z | tar xvf -
This creates the qv directory and the subdirectories listed earlier, containing all the
custom forms, PL/SQL and SQL scripts, and other files for Vista Plus Interface for
Oracle Applications.
Make sure the extracted files belong to applmgr. If they do not, use the chown and
chgrp commands as necessary.
6.
Within qv, the dat, log, bin, and forms subdirectories should be accessible to all users.
Use the command chmod 777 to change the security on these directories.
7.
Assign the QV_TOP environment variable:
Use vi or another editor to edit the file APPLSYS.env under the $APPL_TOP
directory and add the following commands:
QV_TOP="$APPL_TOP/qv/1.1.1"
export QV_TOP
If you use the C shell, source the APPLSYS.env file. For the Korn or Bourne
shell, execute the file by typing:
. ./APPLSYS.env
Type this command to make sure the variable has been assigned correctly:
echo $QV_TOP
This should return the path to the newly-defined $QV_TOP directory. This is
the path to $APPL_TOP followed by /qv/1.1.1.
Installing the Vista Plus Interface for Oracle Applications

The installation script uses the Oracle Applications user name QVISTA to perform some of
its actions. Before running the script, you need to create the QVISTA login name; youll
need the Oracle Applications SYSADMIN login to do so.
When you run the script, youll also need the password for the SQL Plus SYSTEM user,
the user name and password for the SQL Plus applications owner (by default, this is apps),
and the directory path to the Oracle Applications data files ($APPL_TOP).
The installation script compiles the Vista Plus Interface for Oracle Applications PL/SQL
scripts, Oracle Application menus, and forms.
To create the QVISTA user name

1.
26
Log in to Oracle Applications as SYSADMIN
2.
From the Navigator, select Security, User, Define.
3.
On the Users form, type QVISTA as the User Name.
4.
Enter a password of 12345 and any description you want. (Youll need to type the
password again to confirm it.) The first time you log on using this name, youll be
required to pick a new password.
5.
Save the user name by clicking the Save button in the Oracle Applications
toolbar.
Installation
27
To run the installation script

1.
Log on to the applications server as applmgr or using the UNIX login ID with access to
2.
Change to the $QV_TOP/install directory. This directory contains the files extracted
from the Vista Plus Interface for Oracle Applications installation file in the previous
section.
3.
Run the setup script.

$./setup
4.
This displays the following menu:

Install Vista Plus for Oracle E-Business Suite
===============================================
1. Oracle E-Business Suite Release 11.0.X
2. Oracle E-Business Suite Release 11.5.5, 11.5.6, 11.5.7, 11.5.8
3. Oracle E-Business Suite Release 11.5.9, 11.5.10
0. Exit
Enter your choice (0-3) :
Select the correct version of Oracle Applications by typing 1, 2, or 3.

5.
Setup then prompts you with the menu below. Enter the SYSTEM user password
carefully. The password will not appear on the screen when you type it.
Enter password for the 'SYSTEM' ORACLE userid
(For security reasons, your input will not be echoed.):
Please enter the password again to confirm:
6.
Now enter the Oracle Applications owners user name (for example, apps) and
password carefully. The password will not appear on the screen when you type it.
Enter the username for the Oracle Applications owner [default:
APPS]: apps
Enter password for user 'apps'
7.
Next, type the tablespace name to use for data files. This tablespace name must not
exist; the installation script will create it:
Enter Vista Plus Custom Tablespace Name for Data
[e.g. qvd] :
28
8.
Type the full path to the custom datafile, including the file name; the directory must
already exist, but the file must not exist. The installation script will create it:
Enter Vista Plus Custom Datafile Name and Location to Create the
File for DATA [e.g. /u02/oradata/vdem161/qvd_01.dbf]
9.
Type the tablespace name to use for the index. This tablespace name must not exist;
the installation script will create it:
Enter Vista Plus Custom Tablespace Name for Index
[e.g. qvd] :
10. Type the full path to the custom index file, including the file name; the directory must
already exist, but the file must not exist. The installation script will create it:
Enter Vista Plus Custom Datafile Name and Location to Create the
File for INDEX [e.g. /u02/oradata/vdem161/qvx_01.dbf]
11. Type the name to use for the temporary tablespace or just press Enter to accept the
default name of temp:
Enter the temporary Tablespace Name:[default: temp]
The installation now creates the requested tablespaces.

12. Type the password to give the Oracle QV user:
Enter the desired password for the Oracle qv user [default: qv]
13. Installation should be completed quickly. The following message appears after
installation; use vi or another editor to check the install.log file for errors:
Installation complete!
Check the install.log under $QV_TOP\log directory for errors!
14. To make sure the new custom objects are properly registered, stop and restart the
concurrent manager.
Installation
Tip
By default, the total tablespace is 50 MB: 25 MB each for the data and the
index. Depending on the size of your database, you may need to increase this.
You may also need to adjust the next extent size for the tablespace.
Note
The install.log file will include errors indicating the installation tried to drop
tables that do not exist. This is normal; you can ignore these messages.
29
Installing Forms
Installing Forms
This section describes how to install the forms needed for the Oracle Applications
interface. Only middle-tier computers using UNIX are supported; you must install the
forms on each middle-tier (forms) server.
To install the form files

1.
If you are installing from CD, insert the installation CD in the CD-ROM drive of the
Oracle Applications applications server and, if necessary, mount it.
If you received the files via FTP rather than on CD, make sure they are in a location
where you can copy them to the applications server.
2.
Log on to the middle tier as the Oracle application manager (usually applmgr).
3.
Change to the $APPL_TOP directory.
4.
Copy the forms file to $APPL_TOP. The file name is qv_mid11.tar.Z for release 11.0.x or
qv_mid11i.tar.Z for release 11.5.5 through 11.5.10. To copy the file from CD, use this
command:
cp /cdrom/New Install/Unix/name.tar.Z .
Cdrom is the device name of the CD-ROM drive; name is either qv_mid11 or qv_mid11i,
depending on your version of Oracle Applications.
If you copy the file using FTP, be sure to use a binary copy.
5.
Uncompress and extract the files by typing the commands below. For release 11.0.x,
type:
$ uncompress qv_mid11.tar.Z
tar xvf qv_mid11.tar
For releases 11.5.5 through 11.5.10, type:

$ uncompress qv_mid11i.tar.Z
tar xvf qv_mid11i.tar
This creates the qv directory and its subdirectories, containing all the custom forms for
Vista Plus Interface for Oracle Applications. The directory structure is the same as on
the Oracle Applications server; see Extracting the Vista Plus Interface for Oracle
Applications Files on page 25.
6.
30
Make sure the extracted files belong to applmgr. If they do not, use the chown and
chgrp commands as necessary.
Installing Forms
7.
Within qv/1.1.1, the bin, log, and forms subdirectories should be accessible to all users.
Use the command chmod 777 to change the security on these directories.
8.
Assign the QV_TOP environment variable:
Use vi or another editor to edit the file APPLSYS.env under $APPL_TOP

directory and add the following commands. They must come after the
command defining APPL_TOP:
QV_TOP="$APPL_TOP/qv/1.1.1"
export QV_TOP
If you use the C shell, source the APPLSYS.env file. For the Korn or Bourne
shell, execute the file by typing:
. ./APPLSYS.env
Type this command to make sure the variable has been assigned correctly:
echo $QV_TOP
9.
This should return the path to the newly-defined $QV_TOP directory. This is
the path to $APPL_TOP followed by /qv/1.1.1.
Make sure the ORACLE_SID variable points to the correct database name.
echo $TWO_TASK
10. Start the setup shell script to recompile all the forms and create an executable:
cd $QV_TOP/bin
./setup
11. This displays the following menu:

Install Vista Plus Interface for Oracle E-Business Suite
==============================================
1. Compile Vista Plus Custom Oracle Forms
0. Exit
Type 1 to install the forms.

12. Next, enter the Oracle Applications owners user name (for example, apps) and
APPS]: apps
Installation
31
Installing Forms
13. Type the password for the Oracle QV user:

Enter password for the 'QV' sqlplus userid
14. When prompted, press Enter to page through the readme.txt file. After you finish
readme.txt, the installation completes. When it is done, a message reminds you to
check the log files for errors.
15. To see if any errors occurred during compilation of the forms, change to the QV_TOP/
log directory. There is a log file in this directory for each compiled form. Check each
file for errors.
16. To make sure the new forms are properly registered, stop and restart the forms server.
32
Starting the Vista Plus Interface for Oracle Applications
Starting the Vista Plus Interface for Oracle

Applications
Note
All of the procedures and pictures of Oracle Applications forms in this book
are for Oracle Applications 11.5. If you are using another version, the
procedures and forms will be slightly different.
The Vista Plus Interface for Oracle Applications is written entirely within Oracle
Applications. To use the interface, you simply log in as an Oracle Applications user who
has access to the responsibility for the interface:
1.
Start Oracle Applications.
2.
On the Oracle Applications login form, enter QVISTA

and its password. Click Connect.
3.
This displays the Navigator for the Vista Plus Interface

for Oracle Applications. You select all interface features and programs from
here. If you double-click the Expand All button, the Navigator looks like the
picture below (you may need to enlarge the Navigator or the Oracle Applications
window to see the entire expanded list of functions).
You start all features of the interface from the Navigator. The
step-by-step procedures throughout the rest of the manual
assume you have started Oracle Applications and displayed the
Navigator for the interface.
Installation
33
Uninstalling Vista Plus Interface for Oracle Applications
Uninstalling Vista Plus Interface for Oracle

Applications
If you want to remove the Vista Plus Interface for Oracle Applications from your host
computer, there are two procedures involved:
The first removes all informationusers, groups, reports, and foldersadded to the
Vista Plus report warehouse by the interface. You can do this only if the DEINSTALL
option in the System Profile is set to Y, as described on page 41.
The second removes the software and all changes made to the Oracle Applications
database: it unregisters all forms, menus, and concurrent processes and deletes the
QVISTA Oracle Applications user and the qv Oracle database user.
You can run either or both of these processes. If you run both, you must delete the
information from Vista Plus first, as the process that performs that function is removed
from Oracle Applications by the second procedure.
Tip
After running both processes, you can remove the files and directories the
interface added to the Oracle Applications server: delete the $APPL_TOP/qv
directory and all of its contents. You can also remove this directory and its
contents from the middle-tier server.
Removing Data from Vista Plus

This procedure removes all the datausers, groups, folders, reports and report
generationsadded to the Vista Plus report warehouse by the Vista Plus Interface for
Oracle Applications. If you have been updating multiple Vista Plus warehouses, this
removes all data from all warehouses. Any data in any warehouse which was not added
through Vista Plus Interface for Oracle Applications is not affected.
This feature will remove objects from Vista Plus only if the System Profile DEINSTALL
value has been set to Y since before the first transfer of data to Vista Plus. If it has not, the
interface will not know which data to remove from the report warehouse. See page 41 for
more information on DEINSTALL.
To remove Oracle Applications data from Vista Plus
34
1.
In the Navigator, select Other, Requests, Run.
2.
On the Submit a New Request form, select Single Request and click OK.
3.
4.
On the Submit Request form, select the Vista Plus Indiv Del VP Whse request in the
Name field in one of these ways:
Type it.
Type the first few characters and press Tab. If only one request matches your
entry, it is entered. If there is more than one match, select Vista Plus Indiv Del
VP Whse from the list that displays and click OK.
Click in the field, then click the List of Values button next to it. Select Vista
Plus Indiv Del VP Whse from the list and click OK.
If you dont want to start the request immediately, click the Schedule button. On the
Schedule form:
Select Once.
Type the start time you want or click the List of Values button and select the
day and time.
Click OK.
5.
You can also click the Options button to use any of the standard Oracle Applications
options, such as sending notification messages.
6.
If you are sure you want to remove all data that was added to the Vista Plus
warehouse by the interface, click Submit to start the request.
7.
To check the status of the request, from the View menu, select Requests.
Installation
35
Deleting the Vista Plus Interface for Oracle Applications

This procedure removes the Vista Plus Interface for Oracle Applications from the server
host. It unregisters all forms, menus, and processes, removes the interfaces database, and
deletes the QVISTA Oracle Applications user and the qv Oracle SQL Plus user.
Warning
If you want to remove the data added to the Vista Plus report warehouse by
Vista Plus Interface for Oracle Applications, you must do so before deleting
the Vista Plus Interface for Oracle Applications software. Use the procedure
in the previous section.
Make sure no one is logged in as the SQL Plus user qv before you start the
uninstall program.
To delete the Vista Plus Interface for Oracle Applications

1.
Log on to the UNIX server host as applmgr.
2.
Change to the /$QV_TOP/install subdirectory:

cd $APPL_TOP/$QV_TOP/install
3.
Execute the uninstall program:

./uninstall
4.
Uninstall displays this menu:

Caution! Proceed will uninstall ORAP 5.0.
Uninstall Vista Plus for Oracle E-Business Suite
=========================================================
1. Uninstall Vista Plus for Oracle E-Business Suite
0. Exit
Type 1 to uninstall the correct version of Vista Plus Interface for Oracle Applications,
or 0 to stop the uninstall process.
5.
You next see the prompts below. Enter the SYSTEM user password carefully. The
password will not appear on the screen when you type it.
Enter password for the 'SYSTEM' ORACLE userid
36
6.
Now enter the Oracle Applications owners user name (for example, apps) and
APPS]: apps
After you confirm the password, the uninstall program begins deleting information.
When it finishes, Vista Plus Interface for Oracle Applications has been completely
removed from the server host.
Tip
Installation
After finishing this procedure, you can remove the interface files and
directories: delete the $APPL_TOP/qv directory and all of its contents. You can
also remove this directory and its contents from the middle-tier server.
37
38
Chapter 4
System Profile Settings

This chapter describes using the System Profile form to check and modify the interfaces
profile settings.
In This Chapter
System Profile Introduction ................................................................... 40
Viewing and Changing System Profile Settings ................................. 43
39
System Profile Introduction

After installation and before beginning to use the interface, you should check the
interfaces system profile settings and make any needed changes. These settings control
many aspects of the interfaces operation.
The System Profile form shows two types of settings:
Required settings: These settings are necessary for the interface to function properly.
You must not change the values for these settings.
Configurable settings: These settings determine how the interface behaves in certain
situations. You can set these values to match how you want the interface to function.
The following sections describe the required settings and each configurable setting.
Required System Profile Settings

Two required settings are shown on the System Profile form so you can check them if
requested by Open Text customer support. These settings are necessary for the interface to
function correctly. If you change either of them, the interfaces page-level security feature
will not work properly.
The two required settings are the first two on the System Profile form, the two with the
Lookup Type of PAGEGRP. Do not change either of these values unless you are explicitly
told to do so by customer support.
Configurable System Profile Settings

All of the other settings on the System Profile form control aspects of the interfaces
operation which you can change if desired for your installation. However, some of these
settings should be set once, before you transfer information the first time, and should not
be changed again afterward. Each settings description says whether there are limits on
when you should change its value. The configurable profile settings are (these are the
Lookup Codes on the System Profile form):
40
UNIX: (This is listed first because it has a Lookup Code of CLIENT rather than
SERVER.) This is the URL to open when you click the Launch Vista Plus button on
the Server form. It is normally the URL to Vista Plus Web View. This setting is also
available on the Server form.
APA: This value determines what format the interface uses for the page securities it
creates in Vista Plus when you use page-level security by group, as described starting
on page 101. For all supported versions of Vista Plus 5.x, set the Value to 5X.
APAO: Versions of the interface prior to 4.4.8.1 used a different name format for the
page securities it created in Vista Plus. If APAO is set to Y, the page-level security by
group request will delete any page securities which use the old name format and
replace them with ones using the new format. If you used page-level security by
group in an interface version earlier than 4.4.8.1, you should set this to Y before
running any of the page-level security by group requests with this version. If you
never used the earlier version, set this to N.
Note
Securities using the old name format are replaced only if the interface needs
to update them for some other reason, such as a changed security rule or
value set in Oracle Applications. This means it may take many many updates
of page-level security before all of the names have been changed to the new
format.
BACKUP: If this is set to Y, all the generated scripts, data, and log files created by the
interface during migration and capture are stored in the $QV_TOP/save directory. This
allows you or Open Text customer support to refer to them if necessary when
investigating any problems or questions. However, it also requires additional storage
on the file system where $QV_TOP resides. The default for this setting is N, which
means no files are written to $QV_TOP/save. If you set this to Y, be sure you have
enough storage for the additional files.
BYPASS: If this is set to N (the default), before migration or capture sends any
information to Vista Plus, the interface checks to make sure the destination report
warehouse is up and running. If you set this to Y, the interface does not perform this
check. You may want to do this if the interface captures reports through Vista Plus
Output Manager, so you can send reports to Output Manager whether the destination
report warehouse is up and running or not.
CASE: This setting controls whether user names are created in Visa Plus using all
upper case letter or all lower case letters (Vista Plus user names are case-sensitive).
You can set this to either upper (the default) or lower. You must set this value before
running the initialization request; if you change it after that request has been run the
Vista Plus user update will fail.
DEINSTALL: If this is set to Y, the interface keeps a record of every itemuser, group,
report, and so onit creates in Vista Plus, so it can remove all the data if you request
it, as described on page page 34. If this is set to N, the interface does not keep this
information, and so cannot delete the information it has added to Vista Plus. If you
want to be able to delete information from Vista Plus, you must set this value to Y
before first sending information to Vista Plus, and not change it.
41
42
LINKRESP: The page-level security by group feature (see page 101) lets you create a
page security for a Vista Plus group even if the corresponding responsibility cannot
run the report in Oracle Applications. However, users in the group will not be able to
open the report unless it is linked to the groups folder. If LINKRESP is set to Y, the
page-level security by group request (see page 109) will link each report to the folder
for any group you have created page security for, if the report is not already linked to
that folder. If it is set to N, you must use a Vista Plus client to link each report to the
folders for the groups you have created page securities for.
PARAM: If this is set to Y, the descriptions of reports created in Vista Plus by the
interface include the rcapture parameters entered for that report in the interface. If
this is set to N, the parameters are not made part of the report description.
PASS: This is the password for the Oracle qv user, as entered when you installed the
interface. This must always match the actual password for the user, as set in Oracle. If
you change the qv users password in Oracle, you must enter the new password here.
The password is shown in plain text; do not let others see this password if it would be
a security risk.
VPOMCMD1: This field is used only if you send reports through the interface to
Vista Plus Output Manager. The only part of it you should modify is the port number
following the equals sign. Set this to the port number used by Output Manager.
VPOMCMD2: This field is used only if you send reports through the interface to
Vista Plus Output Manager. If so, this must be the path to the Output Manager qr
command; qr must be installed on the Oracle Applications server where the interface
is installed. The -q and -x parameters in the command must be the proper queue name
and host name, respectively, for your Output Manager installation.
VPOMYN: Set this to Y if you want to send reports from the interface to Output
Manager.
WORKERS: To reduce the time it takes to transfer information to Vista Plus, the
interface can spawn extra workers so it can perform multiple operations at once. (It
does this during the page-level security by group request and when adding reports
during migration.) You set the number of workers here. A higher number of workers
decreases the time it takes for these requests, but increases the amount of system
resources they use. The maximum value for this setting is 5.
Viewing and Changing System Profile Settings

As mentioned earlier, you should view the system profile settings to make sure they are
correct for your needs before you begin working with the interface. Once you are using
the interface regularly, you will probably not need to check or change these settings often.
To view or change system profile settings

1.
In the Navigator, select Profile, System.
2.
To see additional settings, use the scroll bar at the left of the form.
If a Value or Description is too long to display completely, you can click in the field
and scroll through it.
3.
To change a Value, click in the field and type the new value.
4.
When you are done looking and with any changes, close the form. To save any
changes, click Yes when asked.
43
44
Chapter 5
Defining the Vista Plus Server Host

The first thing you need to do after installation is define the report warehouses you want
to transfer your Oracle Applications data to. During this process, you also select a
synchronization method and set several interface options.
In This Chapter
Determining a Synchronization Method ............................................. 46
Setting Interface Options ........................................................................ 47
Synchronizing from Multiple Databases ............................................. 52
Synchronizing with Multiple Vista Plus Servers ................................ 53
Entering Vista Plus Server Information ............................................... 54
45
Determining a Synchronization Method
Determining a Synchronization Method

As discussed on page 9, you can select either full synchronization or managed
synchronization for each Oracle Applications database. Full synchronization
automatically transfers all applicable Oracle Applications records to Vista Plus, while
managed synchronization lets you choose exactly which responsibilities, users, and
reports to transfer. There is no right or wrong synchronization method. Decide based on
how your use of Vista Plus fits into your work practices. Which is more important to you:
the ability to select exactly what is copied to the report warehouse, or completely
automatic synchronization of your Oracle Applications data and Vista Plus data?
If you are transferring data to more than one report warehouse, you must select managed
synchronization. Since you must select the destination for information from each
responsibility, full synchronization is not possible. You must also select managed
synchronization if you want to create Vista Plus users for Oracle Applications employees
or sales reps, or force Oracle Applications users in other Vista Plus groups.
Note
46
Important! When choosing a method, remember that if you select full

synchronization, and later decide you want more control, you can switch to
managed synchronization at any time. However, once you select managed
synchronization, you cannot later change to full.
Setting Interface Options

In addition to choosing the synchronization method, you can set several options while
you are defining the Vista Plus report warehouse. Some of these options are discussed in
the following sections.
Capture Method
The Capture Method option determines when a report is captured to Vista Plus by the
capture request. You can choose to capture all reports or only some, based on whether or
not the number of copies is zero, or on which printer the report is sent to. These are the
choices:
Number of Copies = 0: Capture a report only if it is run with the number of copies set
to zero (for viewing on the screen rather than printing). If the number of copies is one
or higher, do not capture it.
Number of Copies >0: The opposite of the previous choice: capture the report only if
the number of copies is at least one; do not capture it if the number of copies is zero.
Vista Plus Printer Name: Capture the report only if it is being printed to a particular
printer. You must enter the printer name in the field to the right. This printer must be
set up as a virtual or null printer in Oracle Applications.
Capture All Reports: Capture all reports whenever they are printed, regardless of the
number of copies or destination printer.
If you frequently test or repeat report runs with copies set to zero, you may want to
capture only when the report is actually printed: capturing the preliminary or repeated
runs will result in multiple generations in Vista Plus containing essentially the same
report information.
Note
This setting does not have any effect on reports sent to a printer defined for
immediate capture; those reports are captured immediately whether or not
they meet the condition set in this field. See page 114 for information on
immediate capture.
47
Capture On or Off for Full Synchronization

When you select full synchronization, all of your users, responsibilities, and reports are
automatically migrated to the Vista Plus report warehouse. However, while all reports are
created in Vista Plus, you can choose to have runs of all reports captured as report
generations, or to select the reports to capture.
If you set the Capture On or Off for Full Synchronization option to On, output from
all Oracle Applications report requests is captured into Vista Plus as generations.
If you set this option to Off, you must then select the reports you want to have
captured to Vista Plus, as described in Chapter 9. This is the same as selecting reports
for capture when using managed synchronization.
This option has no effect when you are using managed synchronization. With managed
synchronization, you must select the reports to create in Vista Plus, then select which of
those reports to capture.
Capture On or Off for FSG Ad hoc Reports

To have FSG ad hoc reports captured into Vista Plus, select Capture FSG Adhoc here. If
you are using managed synchronization, you must include the General Ledger
responsibilityand any other responsibility which may run FSG ad hoc reports for
capture into Vista Plusin synchronization, since the ad hoc reports belong to that
responsibility. Each captured report will be linked to the General Ledger folder in Vista
Plus; the report name will be FSG-Ad hoc followed by the request ID of the report, the
name of the user running the report, and the input parameters used.
48
FSG Detail Capture On or Off

All FSG reports are captured to reports linked to the General Ledger folder in Vista Plus (or
the folder for the responsibility that runs FSG reports, if that is not General Ledger). If you
turn on FSG Details capture, FSG reports run with a Segment Override or Content Set
entry are also captured to a special folder structure.
If you choose this option, the folder tree for detail FSG reports is created beneath the
General Ledger folder. The folder each report is captured to is based on the report setif
there is onethe period it is run for, and the Segment Override or Content Set entry:
If the report is run as part of a report set, a subfolder is created for the report set; a
folder for the period, as described below, is created in this folder.
A folder is created for the period: for example, Period Nm:Apr-00. This is a subfolder of
the report set folder, if one exists, or of the General Ledger folder. The folders for the
Segment Override and Content Sets are created in this folder
If there is a Segment Override entry, the report is captured to a folder named Segment
Override. This is true even if there is also a Content Set entry.
If there is a Content Set entry, but no Segment Override, the report is captured to a
folder named after the Content Set entry: for example, Expand by Sales Department.
For example, as shown in the picture, an FSG report run as part of a report set called End of
Month Reports for April 2000 with a Segment Override entry is saved to the Vista Plus
folder /General Ledger/FSG Detail/Report Set: End of Month Reports/ Period Nm:Apr-00/
Segment Override. (Note that these are all folder descriptions, not the actual folder names.
The folder name includes the SID for the instance and other information.)
For all reports captured to the Segment Override folder, the generation description includes
the currency used and the Segment Override setting, as shown. For reports captured to
Content Set, the description includes the currency used.
Detail FSG capture is in addition to regular report capture. All reports which are captured
to the detail FSG folder tree are also captured to the General Ledger folder.
Detail FSG capture affects only FSG reports with a Segment Override or Content Set entry.
If these two fields are blank, the report is captured only to the General Ledger folder.
49
Passwords
Vista Plus users may or may not have passwords assigned to them; if a user does have a
password, he or she must enter it to start a Vista Plus client. You can have the
synchronization assign passwords to the users it creates in Vista Plus. The interface can
use one of four formats for the passwords:
Default: Sets the password for all created users to ORACLE (all upper case; Vista Plus
passwords are case-sensitive).
User Name: Sets the password for all users to match their Oracle Applications user
names, in all upper case.
Null: Creates the users in Vista Plus without passwords.
Random: Sets the password to the user name plus a five-digit random numbersuch
as 12345 or 79830. Obviously, each user will not be able to log in to Vista Plus until an
administrator tells him or her the correct password. You can print a list of the
passwords assigned; see page page 135 for instructions.
Especially if you do not use the Random optionthe other options do not give much
security, since any user can easily guess other users passwordsyou may want to require
each user to select a different password when he or she first uses a Vista Plus client. To do
this, select the Force Password Change box.
Tip
50
Whatever password option you select, you can enter individual custom
passwords for any or all users. You do this by changing the password on the
Users form before migration. See page 63 for instructions on doing this with
full synchronization or page 78 for managed synchronization.
Overriding Selective Synchronization

If you are using managed synchronization, you can select which responsibilities the
interface includes both when it synchronizes data from Oracle Applications to its database
and when it migrates data from its database to Vista Plus. By default, the synchronization
request copies datareports, users, and so onfrom all Oracle Applications
responsibilities into the interfaces database. However, you can choose to have it copy this
data only for the responsibilities you have selected for migration, or even for just some of
those responsibilities. This speeds up synchronization, as it doesnt process information
from responsibilities you do not want. You make these choices on the Responsibility form,
as described starting on page 76.
Checking the Override Selective Sync box on the Server form overrides any
synchronization selections you have made on the Responsibility form: data from all
responsibilities is included in synchronization, including responsibilities that are not
included in migration. This lets you easily update all information in the interfaces
database. When you want to go back to synchronizing only the responsibilities youve
chosen, you can clear the check box.
There is no need to check Override Selective Sync when first defining Vista Plus servers,
as the initialization request always copies data from all responsibilities into the interfaces
database. Also, this setting has no effect if you use full synchronization (see page 9), as it
also always copies information from all responsibilities.
Note
Regardless of the setting for Override Selective Sync, or any selections you
make on the Responsibility form, synchronization always copies the complete
list of responsibilities to the interfaces database. These settings apply only to
the users, reports, and other data found within the responsibility.
51
Synchronizing from Multiple Databases
Synchronizing from Multiple Databases

You can synchronize more than one Oracle Applications database with the same Vista
Plus report warehouse. If you do, you need to be aware of possible conflicts if the
databases have any of the same user, responsibility, or report names. If this information is
copied to Vista Plus from both databases, it can cause several serious problems, including
deleting reports and generations, making reports and generation inaccessible by any user,
and making it impossible for users to log in.
To avoid these problems, you must enter an ID code of one to four characters when you
define the Vista Plus report warehouse to the Oracle Applications database. This code is
inserted at the beginning of each group, folder, and report name created in the report
warehouse by this database. This means each database will create its own data in Vista
Plus, without conflicting with information from another database. For example, if you
have separate databases containing information from your East coast and West coast
operations, you can enter East and West as the ID codes for the two databases. Then, if
there is a responsibility called Payroll in each database, the Vista Plus report warehouse
will have groups and folders called WestPayroll and EastPayroll.
You have the option to use this code at the end of user names. If there is any possibility of
identical user names in the two Oracle Applications databases, you must select this option
when defining the Vista Plus report warehouse. If you dont, importing the users from
both databases will create duplicate user records in Vista Plus, and make it impossible to
sign on with that user name. When you do use the prefix with user names, users log in
with the user name from the appropriate database (in the example above, User - West or
User - East) to select the data to work with.
52
Synchronizing with Multiple Vista Plus Servers
Synchronizing with Multiple Vista Plus Servers

You can transfer information from an Oracle Applications database into more than one
Vista Plus report warehouse. In this case, you must use managed synchronization so you
can select which responsibilities are transferred to which warehouse: any responsibility,
and the users and reports it contains, can be transferred to one or more warehouses.
To send your Oracle Applications data to more than one warehouse, you define each
warehouse using the Maintain Vista Plus Server form, as described in Entering Vista Plus
Server Information, below. You must enter a different four-character SID for each
warehouse.
53
Entering Vista Plus Server Information

Follow the procedure below to define the Vista Plus report warehouse to use and select
synchronization and report capture options. Refer to the preceding sections and to
Chapter 2 for information on how your choices affect Vista Plus Interface for Oracle
Applications.
To enter Vista Plus server information

1.
In the Navigator, select Administration, Server.
2.
On the Server form, select a synchronization method. If you are using multiple report
warehouses, you must select managed synchronization. See Determining a
Synchronization Method on page 46.
Note
54
Important! If you select managed synchronization, you cannot later change

to full. You can switch from full to managed synchronization at any time.
3.
Make your choices for Capture Method, Turn Capture ON or OFF for Full Sync,
Turn On/Off Capture FSG Adhoc, FSG Details, Password Value, and Override
Selective Sync. See Setting Interface Options on page 47.
4.
If you want to be able to launch the Vista Plus Web View client from the interface, type
the URL to use for it in the Vista Plus URL field. Youll be able to launch Web View by
clicking the Launch Vista Plus button on this form. You can also change this URL on
the System Profile form.
5.
Set the Primary Language to the language you want used for the names of the
responsibilities and reports migrated to Vista Plus. To select the language, either
type it or click in the field, click the List of Values button next to the field, and select it
from the list.
This selection affects only the names used for responsibilities and reports transferred
to Vista Plus. It does not change the forms of the Vista Plus Interface for Oracle
Applications.
6.
Type the path to the directory specified by the QV_TOP environment variable
specified during installation (see page 25), followed by a slash (/). For example, if
QV_TOPs value is /d01/apps/qv/1.1.1, enter /d01/apps/qv/1.1.1/. This entry must
be correct or the interface will not be able to migrate information to Vista Plus.
7.
Type the information for the Vista Plus report warehouse in the first row of data fields:
Server Name: The name defined for the destination Vista Plus server host on
your network.
TCP/IP Address: The address for the destination Vista Plus server host.
Port Number: The port number used by this Vista Plus report warehouse on the
server host.
Vista Plus Remote: The path on the Oracle Applications server host where the
Vista Plus remote capture tools software is installed. If the server host has more
than one version of the remote capture tools installed, this must be the path to
the version that matches the Vista Plus version on the server being defined.
Description: This is for your reference only. It doesnt appear anywhere but on
this form.
4 SID: A one- to four-character code used to identify this database/report

warehouse connection. The code is inserted at the beginning of group, folder,
and report names from this database in the report warehouse, and added to
user names if you choose that option. It is also used to select the report
warehouse on the Define Warehouse form.
Admin: If the Vista Plus warehouse uses vadmin password security, type the
Vista Plus user name of the Administrator user the interface should use when
sending vadmin commands to Vista Plus during migration. This user must
already exist, must be used only by this installation of the interface, and the
password for it must be the same as the user name. For security reasons, the
interface will change the password during each migration. Do not use the same
user name for more than one report warehouse.
If the report warehouse does not use password security for vadmin, leave this
field blank.
8.
To add the four-character SID for this database to all Vista Plus user names, check the
Append User with 4-Char SID box. You must check this box if you are importing
data to this server from more than one Oracle Applications database.
55
9.
To have all information copied to the report warehouse during each migration, even
information which has not changed since the previous migration, click the Recreate
box. For better performance, you will generally want to leave this box blank so only
new and changed information is copied. You may want to check it if you feel the
information was not correctly written to the report warehouse during migration.
10. After completing the row for one report warehouse, click the Save button or,
from the File menu, select Save. You must save each row before going on to the
next.
11. If you want to transfer information to another Vista Plus report warehouse, enter the
information for it in the next row. The 4 Char SID for each report warehouse must be
unique. If you enter more than one warehouse, you must use managed
synchronization. If you have multiple report warehouses, be sure to save after
entering the information for each one.
12. The Printer Definition fields at the bottom of the form are used to define printers for
immediate capture of reports. How to set up these printers, including how to use
these fields, is described starting on page 114.
13. When youve entered information for all report warehouses, make sure to save your
entries, then close the form.
Tip
56
To modify a server definition, simply change the information and save your
changes. Be sure to save the changes before doing anything else. However,
you cannot change the 4 Char SID for a warehouse once it has been saved.
Deleting a Vista Plus Server

At times, you may want to delete the definition of a Vista Plus server from the interface.
For example, you may have been using a test server you no longer need. You can delete a
server by following the procedure below. When deleting a server, you can also remove
from the Vista Plus report warehouse the users, groups, folders, and reports from that
server. Or you can leave the existing data in Vista Plus and merely remove the server
definition so no more information is transferred. (You can delete the data only if the
DEINSTALL flag has been set to Y since before the first migration. See page 41 for more
information.)
You can delete only one server definition at a time. If you want to delete multiple servers,
you must delete one, save your changes, then delete the next.
To delete a Vista Plus server definition

1.
From the Navigator, select Administration, Server.
2.
On the Server form, select the server definition you want to delete by clicking in any
field on its line.
3.
Click the Delete button on the toolbar.
4.
Do one of the following:
5.
To delete the server definition, all the records for the server definition from the
interfaces database, and all objects created by the interface in this Vista Plus
warehouse, click OK. The objects in the Vista Plus warehouse will be deleted
only if the System Profile DEINSTALL field has been set to Y since before the
first migration. See page 41 for more information.
To delete just the server definition, leaving all the objects in the Vista Plus
warehouse and all records for this server in the interfaces database, click Other.
If you decide not to delete the server definition, click Cancel.
Click the Save button or, from the File menu, select Save.
57
58
Chapter 6
Transferring Data Using Full Synchronization

This chapter describes the procedures to follow to initially populate a Vista Plus report
warehouse with Oracle Applications data using full synchronization, and to keep the
report warehouse synchronized with the latest Oracle Applications data.
If you are using the managed synchronization method, please use the procedures
described in Chapter 7.
In This Chapter
First-Time Data Transfer ......................................................................... 61
Scheduling Updates ................................................................................ 67
Capturing Reports ................................................................................... 69
59
Procedure Overview
Procedure Overview
With full synchronization, all transfer of data from Oracle Applications to Vista Plus is
performed by the Vista Plus Interface for Oracle Applications requests. All you need to do
is run the appropriate request, or schedule it to run automatically at an interval you
choose. Depending on the option you chose when defining the Vista Plus server, you may
also need to select the reports to capture as Vista Plus generations.
Here are the steps:
1.
Submit the initialization request to place the data to be transferred into the interfaces
database.
2.
If you want to create private folders for any users, as discussed on page 63, select
those users.
3.
Select any reports for private capture. If you are not capturing all reports
automatically, you can also select the reports to capture now.
4.
Submit the migration request to move the data from the interfaces database into the
Vista Plus report warehouse.
5.
If you are selecting the reports to capture, as described on page 48, and did not do so
in step 3, select the reports. Choosing reports for capture is described in Chapter 9.
6.
Either schedule the full synchronization/migration request to run at regular intervals,

or start it manually whenever desired.
Thats it. Since all users, responsibilities, and reports are transferred to Vista Plus, all you
need to do is set the synchronization schedule, and, if you want, set up private report
capture. The rest of this chapter describes these steps in more detail.
Tip
60
You also need to set a schedule for report capture. Capturing reports is
described in Chapter 9.
First-Time Data Transfer

Using full synchronization, moving data from Oracle Applications to create the Vista Plus
user, group, folder, and report structure is merely a matter of running two requests and
optionally selecting the users you want private folders created for (these are steps 1
through 3 in the list in the previous section). Follow the instructions in the sections below.
Initializing the Interfaces Oracle Applications Database

As described in Chapter 2, data is moved from the Oracle Applications database to the
Vista Plus report warehouse in a series of steps. The first of these steps is to place all users,
responsibilities, and reports into a custom Oracle Applications database created by Vista
Plus Interface for Oracle Applications. You do this using the initialization request.
Warning
You should run the initialization request only once. If you run it again after
transferring data to Vista Plus, it removes the synchronization between Oracle
Applications and Vista Plus; you will have to remove your Vista Plus data
and redo the entire data transfer process.
Warning
Before running initialization, make sure all system profile values are set
correctly. Some profile values cannot be changed once you have run
initialization. See Chapter 4 for more information.
Note
Only responsibilities with at least one associated report are placed in the
interfaces database; responsibilities without any associated reports are not.
To run the initialization request

1.
2.
61
3.
4.
62
On the Submit Request form, select the Vista Plus Indiv Initialization request in the
Type it.
entry, it is entered. If there is more than one match, select Vista Plus Indiv
Initialization from the list that displays and click OK.
Plus Indiv Initialization from the list and click OK.
Schedule form:
Select Once.
day and time.
Click OK.
5.
Click Submit to start the request.
6.
Selecting Users to Have Private Folders

As described on page 14, you can choose to have some reports captured to a private folder
viewable only by the user who ran the report. If you use this feature, you must select the
users who should have private folders created to hold these reports. You can do this using
the procedure below. You can also set a custom password for any user; see the Tip at the
end of the procedure. If you are not going to use private report capture or set any custom
passwords, skip this step.
To select the users who should have private folders

1.
In the Navigator, select Define, User, User Responsibility.
2.
On the User Responsibility form, select a responsibility in one of these ways:
Type it in the Name field.
Type the first few characters of the responsibility and press Tab. If only one
responsibility matches your entry, it is entered. If there is more than one match,
they display in a list. Select the one you want and click OK.
Click in the Name field, then click the List of Values button next to it. Select
a responsibility from the list and click OK.
3.
To display the users in this responsibility, from the View menu, select Query by
Example, Run.
4.
Since you are using full synchronization, the Proc box is checked for all users. For
each user who should have a private folder, check the Priv box. To give all users
private folders, click the Priv button.
5.
When youve selected users for this responsibility, click the Save button on the
Oracle Applications toolbar.
63
6.
Repeat steps 2 through 5 for each responsibility with users you want to create private
folders for.
7.
When done, save your changes and close the form.

Tip
To see additional information about the users, change the selection in the field
above the user list. You can select Responsibility Effective Dates to see the
beginning and ending dates for the user in this responsibility, or Password to
see the password that will be assigned to the user in Vista Plus and the
number of days until the password expires, if that value is set in Oracle
Applications. You can change the Vista Plus password for any user; the other
fields are not changeable.
Tip
If a user is in more than one responsibility, you need to select private only
once. The private folder in Vista Plus is for the user; it is not tied to any
responsibility. However, the Priv box will show as checked only in the
responsibility where you checked it. You can check the Priv box for the user in
all his or her responsibilities if you want; only one private folder is created in
Vista Plus.
Selecting Reports to Link to Private Folders

With full synchronization, all Oracle Applications reports are created as Vista Plus reports
linked to the folders for their responsibilities. You can also choose to create Vista Plus
reports in any user private folders. When these reports are captured, they will be captured
only into the report in the private folder of the user running the report (the report name in
the private folder includes the user name), not into the report in the responsibility folder.
Selecting reports for private folders does not cause the reports to be captured into Vista
Plus when they are printed. If you have Capture for full synchronization on, all reports
are captured; if this option is off, you can select the reports to capture either during this
procedure or later, as described in Chapter 9.
You can perform this procedure at any time to change reports to private or back to public.
To select reports
64
1.
In the Navigator, select Define, Reports.
2.
On the Reports form, select a responsibility in one of these ways:
Type the responsibility in the Name field.
3.
To display the reports in this responsibility, from the View menu, select Query by
Example, Run.
4.
Select the reports to create in private folders:
To link all reports to users private folders, click the Priv button. You can then
clear the check box for any reports you do not want linked to a private folder.
To link an individual report to users private folders, check its Priv box.
5.
To add any options to the rcapture command the interface uses to capture the report,
type them in the Rcapture command field. See the note below.
6.
When youve selected reports for this responsibility, click the Save button on the
7.
Repeat steps 2 through 5 for each responsibility you want to select private reports for.
8.

Note
The rcapture commands created by the interface include the d, f, m, and

t options. Do not enter a d or t option (or a, g, or n, which conflict with
the options used by the interface) on this form. For a complete list of rcapture
options, please see the Vista Plus Server Administration Guide.
Tip
To select which reports to capture, check their Cap boxes or click the Cap
button. Do this only if Capture for full synchronization is off. You can also
select reports for capture later; see page 116.
65
Copying the Data into Vista Plus

Once the information is in the interfaces database, the next step is to move it to the Vista
Plus report warehouse. Since all of the data is transferred when you use full
synchronization, all you need to do is submit the migration request. This copies the data
to text files, then creates and runs a script using the Vista Plus vadmin command to write
the data into the report warehouse.
Note
Important! With full synchronization, you submit the migration request only
for the initial transfer of data to Vista Plus. For future synchronizations, youll
use the full sync/migrate request as described on page 67.
To run the migration request

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Migration request in the Name
field in one of these ways:
4.
66
Type it.
Migration from the list that displays and click OK.
Plus Indiv Migration from the list and click OK.
Schedule form:
Select Once.
Type the start time you

want or click the List of
Values button and select
the day and time.
Click OK.
5.
You can also click the Options

button to use any of the
standard Oracle Applications
options, such as sending
notification messages.
6.
Click Submit to start the

request.
7.
Scheduling Updates
Scheduling Updates
As time goes by, your Oracle Applications data changes: youll add new reports and users,
change responsibility effective dates, and so on. So, after youve initially transferred data
from Oracle Applications to Vista Plus, youll need to resynchronize the information from
time to time to keep up. Using full synchronization, all you need to do is schedule the full
synchronization/migration request. This performs the entire process of moving data from
Oracle Applications to Vista Plus: copies it to the interfaces database, from there to a text
file, and finally into the report warehouse.
The full synchronization/migration request keeps your users, responsibilities, and report
structure up to date in Vista Plus. It does not perform any report capture. You also need to
follow the report capture procedures in Chapter 9.
Note
Unless the Recreate box is checked for a report warehouse on the Server form
(see page 54), migration copies only new and changed information to the
Vista Plus report warehouse. If you want to rewrite all data into Vista Plus
(for example, if a network or other error kept Vista Plus from being updated
correctly), check the Recreate box before running migration. In normal use,
youll want to have Recreate unchecked for better migration performance.
To schedule the full synchronization/migration request

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Full Sync/Migrt request in the
Type it.
entry, it is entered. If there is more than one match, select Vista Plus Indiv Full
Sync/Migrt from the list that displays and click OK.
Plus Indiv Full Sync/Migrt from the list and click OK.
67
Scheduling Updates
4.
68
If you dont want to start the request immediately, or if you want to schedule it to run
automatically at intervals, click the Schedule button. On the Schedule form:
Select Once,
Periodically, or On
Specific Days.

the day and time.
If you are scheduling for

repeated execution,
select the interval and
other options.
Click OK.
5.

button to use any of the standard Oracle Applications options, such as sending
6.
7.
Tip
You do not have to set a schedule. You can run the request individually
whenever you want to synchronize data in Vista Plus.
Tip
If you want to give a new Oracle Applications user a private folder in Vista
Plus, after running the Vista Plus Indiv Full Sync/Migrt request, bring up the
Users form, as described on page, and check the Priv box for the user. The
private folder will be created the next time the Vista Plus Indiv Full Sync/Migrt
request runs.
Note
Once a user has been migrated to Vista Plus you cannot change his or her
password through the interface.
Capturing Reports
Capturing Reports
All of the procedures in this chapter have dealt with keeping Oracle Applications data
specifically, users, responsibilities, and report definitionssynchronized in Vista Plus. All
of this is really just background information for the main function of Vista Plus Interface
for Oracle Applications: automatically capturing your Oracle Applications report runs as
report generations in the Vista Plus report warehouse.
To capture report generations, you need to run or schedule the capture report request, or
select a printer set up for immediate report capture. If full capture synchronization is off,
you also need to select the reports to capture if you have not already done so. Please see
Chapter 9 for instructions on these procedures.
69
Capturing Reports
70
Chapter 7
Transferring Data Using Managed Synchronization

This chapter describes the procedures to follow to initially populate a Vista Plus report
warehouse with Oracle Applications data using managed synchronization, and to keep
the report warehouse synchronized with the latest Oracle Applications data.
If you are using the full synchronization method, please use the procedures described in
Chapter 6.
In This Chapter
Procedure Overview ............................................................................... 72
First-Time Data Transfer ......................................................................... 74
Capturing Reports ................................................................................... 90
Updating Vista Plus Information .......................................................... 91
71
Procedure Overview
Procedure Overview
When you use managed synchronization, you select exactly what informationwhich
users, responsibilities, and reportsare transferred to the Vista Plus report warehouse.
You do this using custom Oracle Applications forms supplied with Vista Plus Interface for
Oracle Applications. You also run the requests provided to move the data into the
interfaces custom Oracle Applications database, then into Vista Plus, as described in
Chapter 2.
Here are the steps involved in managed synchronization:
72
1.
Submit the initialization request to place the Oracle Applications data into the
2.
Select the responsibilities to transfer to Vista Plus. During this step, you can also:
Choose whether to include all users and/or reports from the responsibility.
Choose whether to allow forcing users into the Vista Plus group for this
responsibility. Forcing users lets you select specific users who dont belong to
the responsibility in Oracle Applications and add them to the corresponding
group in Vista Plus.
Choose whether to allow Oracle Applications employees and sales reps to be

added to the Vista Plus group for the responsibility.
Select the responsibilities to include in future synchronizations.
3.
Select the users to transfer to Vista Plus and which, if any, should have private folders.
4.
For responsibilities you allowed it for in step 2, select the Oracle Applications users,
employees, and/or sales reps to add to the Vista Plus group for the responsibility.
5.
Select the reports to transfer to Vista Plus. This determines the Vista Plus report
structure. You also select which reports, if any, should be created in users private
folders. You can also select the reports to capture during this step.
6.
Set the destination Vista Plus report warehouse for each responsibility. You must do
this even if you are copying all information to the same warehouse.
7.
Submit the migration request to move the selected data into the report warehouse.
8.
Select the reports to be captured into the report warehouse if you didnt do so in step
5.
Procedure Overview
9.
Whenever you want to update the data in Vista Plus:
Submit the synchronization request. You may want to schedule this at regular
intervals.
Select the responsibilities, users, and reports to update in Vista Plus.
Submit the migration request to update the data in Vista Plus.
If youve added new reports to the report warehouse, select the ones to capture.
If you want to use page-level security by user or group, select the reports and
data fields to use and submit the page-level security requests.
Note
Important! Since only users and reports in the

responsibilities you select can be copied to Vista
Plus, you must perform the selections in the order
given here: responsibilities, users, reports. This is
the same order they are listed in in the Navigator.
Tip
You also need to set a schedule for report capture.

Capturing reports is described in Chapter 9.
73

As outlined in steps 1 to 5 in the previous section, moving data from Oracle Applications
to Vista Plus involves first moving data to the custom Oracle Applications database
created by Vista Plus Interface for Oracle Applications, selecting which data to include in
the transfer, then copying the data to Vista Plus. Follow the instructions in the sections
below.
Initializing the Interfaces Oracle Applications Database

As described in Chapter 2, data is moved from the Oracle Applications database to the
Vista Plus report warehouse in a series of steps. The first of these steps is to place all users,
responsibilities, and reports into a custom Oracle Applications database created by Vista
Plus Interface for Oracle Applications. You do this using the initialization request.
Warning
You should submit the initialization request only once. If you run it again
after transferring data to Vista Plus, it removes the synchronization between
Oracle Applications and Vista Plus; you will have to remove your Vista Plus
data and redo the entire data transfer process.
Warning
Before running initialization, make sure all system profile values are set
correctly. Some profile values cannot be changed once you have run
initialization. See Chapter 4 for more information.
To run the initialization request
74
1.
2.
3.
4.
On the Submit Request form, select the Vista Plus Indiv Initialization request in the
Type it.
Initialization from the list that displays and click OK.
Plus Indiv Initialization from the list and click OK.
Schedule form:
Select Once.
day and time.
Click OK.
5.
6.
75
Selecting the Responsibilities to Transfer

Oracle Applications responsibilities are transferred into Vista Plus as groups and folders;
the folder is the Home folder for the group. You can include any or all responsibilities in
the migration. Youll perform this procedure after the initialization request finishes and
again each time you synchronize and migrate data.
When you select responsibilities, you also choose whether to transfer all users and reports
for the responsibility, whether to allow users who arent in this responsibility to be placed
in its Vista Plus group (this is called forcing users), and whether to allow people who are
entered in Oracle Applications as employees and sales repsbut who are not Oracle
Applications usersto be added to the Vista Plus group.
In addition to selecting the responsibilities to migrate to Vista Plus, you can specify which
responsibilities will be written to the interfaces database during following
synchronizations. By default, all responsibilities, including those you are not migrating to
Vista Plus, are written to the interfaces database during synchronization. By selecting just
the responsibilities you may want to transfer to Vista Plus, you can decrease the time
needed for synchronization. You can override any selections you make for
synchronization by checking the Override Selective Sync option on the Server form; see
page 51.
Note
Only responsibilities with at least one associated report are placed in the
interfaces database; responsibilities without any associated reports are not.
To select responsibilities
1.
76
In the Navigator, select Define, Responsibility.
2.
On the Responsibility form, select the responsibilities to include in migration:
To select all responsibilities, click the Proc button. This checks the Proc box for
all responsibilities. You can then clear the Proc box for any responsibilities you
dont want to include.
To select individual responsibilities, check the Proc box for each one to include.
Warning Once youve selected a responsibility for processing and migrated it to Vista
Plus, it is included in all future migrations. You will not be able to go back
and clear the Proc box after you have run migration. Be sure to select only
the responsibilities you want to include in migration.
3.
For each responsibility with Proc checked, you have these options:
Check All to include all users and all reports for this responsibility in the
migration. You then do not need to select users and reports, as described below,
for this responsibility.
Check Usr to include all users, but not necessarily all reports, for this
responsibility in the migration. You then do not need to select users, as
described below, for this responsibility.
Check Rpt to include all reports, but not necessarily all users, for this
responsibility in the migration. You then do not need to select reports, as
described below, for this responsibility.
Check Forc to allow Oracle Applications users who dont belong to this
responsibility to become members of the Vista Plus group for the responsibility.
See page 80 for how to assign users to the Vista Plus group.
Check Emp to allow people who are entered in Oracle Applications as

employees, but who are not Oracle Applications users, to be included in
migration and become members of the Vista Plus group for the responsibility.
See page 81 for how to assign employees to the Vista Plus group.
Check Sale to allow people who are entered in Oracle Applications as sales
reps, but who are not Oracle Applications users, to be included in migration
and become members of the Vista Plus group for the responsibility. See page 84
for how to assign sales reps to the Vista Plus group.
Check Sync to include the responsibility in upcoming synchronizations.

(Synchronization is the copying of information from Oracle Applications to the
interfaces database.) If you dont select this box for any responsibilities, all
responsibilities are synchronized, including those that do not have the Proc box
checked. If you select Sync for any responsibility, only those with Sync selected
are synchronized.
To select any of these options for all responsibilities that youre processing, click the
corresponding button at the bottom of the form.
77
4.

Tip
You can create a new folder and group in Vista Plus by adding a
responsibility to the list on the Responsibility form. Click the Add
toolbar button and type the name you want. You can then add users,
employees, and/or sales reps to the group, as described in the following
sections.
Since there is no Oracle Applications responsibility corresponding to the new
group and folder, there are no reports linked to the folder when its created in
Vista Plus. You can add reports to the folder in Vista Plus.
Selecting the Users to Transfer

After youve selected responsibilities, you can select the users to transfer into Vista Plus.
You select users one responsibility at a time. This gives you complete control over the
user/group structure in Vista Plus; users are made members of a group in Vista Plus only
if you select them for transfer in that responsibility. (You can also make users members of
a Vista Plus group even if they arent members of the corresponding Oracle Applications
responsibility. See page 80.)
While selecting users, you can select which users should have private folders created in
Vista Plus. Private folders can allow these users to see reports which are not available to
other users; please see page 14 for more information. You can also change the password
which will be assigned to a user in Vista Plus; this lets you set custom passwords for any
or all users.
Youll perform this procedure after initialization and again each time you synchronize the
data.
Tip
If you checked the All or Usr box when defining a responsibility, all users
from the responsibility will be processed. You can skip this procedure for that
responsibility.
To select users
78
1.
In the Navigator, select Define, User, Responsibility.
2.
On the User Responsibility form, select a responsibility in one of these ways:
Type it in the Name field.
3.
To display the users in this responsibility, from the View menu, select Query by
Example, Run.
4.
Select the users to include in the synchronization:
To select all users, click Proc. You can then clear the Proc box for any users you
dont want to migrate.
To select an individual user name, check the Proc box next to it.
To select and create private folders for all users, click Priv.
To select and create a private folder for a single user name, check its Priv box.
Warning Once youve selected a user for processing and migrated it to Vista Plus, it is
included in all future migrations. You will not be able to go back and clear
the Proc box after you have run migration. Be sure to select only the users
you want to include in migration.
5.
To see additional information about the users listed, change the selection in the field
above the user list. You can select Responsibility Effective Dates to see the beginning
and ending dates for the user in this responsibility, or Password to see the password
that will be assigned to the user in Vista Plus and the number of days until the
password expires, if that value is set in Oracle Applications. You can change the Vista
Plus password for any user; the other fields are not changeable.
6.
When youve selected all users for this responsibility, click the Save button on the
7.
Repeat steps 2 through 6 for each responsibility you want to transfer users for.
79
8.

Tip
If a user name belongs to multiple responsibilities, you must select it for

migration in each responsibility it belongs to. If you do not select the user
name in a particular responsibility, it will not be a member of that group in
Vista Plus.
However, you need to select Priv only once for each user; since the private
folder is separate from the responsibility/group structure in Vista Plus, you
do not need to select Priv for each responsibility the user is in.
Forcing Users Into a Vista Plus Group

At times, you may want to have users belong to a Vista Plus group other than the ones
corresponding to their Oracle Applications responsibilities. A person may not need to be
able to add data or print a given report, but may need to see the report data. Without Vista
Plus, he or she probably got a paper copy of the report. With Vista Plus, you can add him
or her to the proper Vista Plus group so he or she can see the report using a Vista Plus
client. We call this forcing a user into a group. You could do it using one of the Vista Plus
administration clients, but it may be easier to use the Vista Plus Interface for Oracle
Applications to include the user in the group during migration.
You can force users to a Vista Plus group only if you checked the force box for the
responsibility when selecting the responsibilities to include in synchronization. See page
76.
To force users into a group

1.
In the Navigator, select Define, User, Force.
2.
On the User Force form, select the responsibility you want to force users into:
3.
80
From the View menu, select Query by Example, Run. This lists all Oracle
Applications users.
4.
For each user to add to this group in Vista Plus, select the Proc box. If you want to add
most or all Oracle Applications users to this Vista Plus group, click the Proc button.
You can then clear the Proc box for any users you dont want to process.
5.
You also have these options for each user:
To set an end date in Vista Plus for the users membership in this group, type
the date in the Force Date field.
To see the Oracle Applications responsibilities the user belongs to, click the Inq
box.
To see the password assigned the user in Vista Plus, select Password in the field
above the user list. You can change the password by typing a new one. This also
displays the number of days until the password will expire, if that value is set in
6.
When youve selected all users for this responsibility, click the Save button on the
7.
Repeat steps 2 through 6 for each responsibility you want to force users to.
8.
81
Adding Employees to a Vista Plus Group

Employees who do not need to use Oracle Applications may benefit from being able to
view reports online using Vista Plus. Therefore, the interface lets you take records from
the Oracle Applications employee tables and create Vista Plus users from them. You select
a responsibility, then choose the employees for it. Vista Plus users are created for each
employee and made members of the appropriate Vista Plus groups.
You can select employees to assign to a Vista Plus group only if you checked the employee
box for the responsibility when selecting the responsibilities to include in synchronization.
See page 76.
Note
While this feature is intended to let you add Oracle Applications employees
to Vista Plus groups, you can actually select any person type from the
Oracle Applications HR tables: employee, doctor, retiree, and so on. See step 4
of the procedure below.
To create Vista Plus users from employees
82
1.
In the Navigator, select Define, User, Employee.
2.
On the User Employees form, select the responsibility you want to add employees to.
Use one of these methods:
3.
Click in the Type field, then click the List of Values button next to it.
4.
From the list, select the person type and click OK.
5.
Applications records of the type you selected: employee, applicant, etc.
6.
For each person you want to add to the Vista Plus group for this responsibility, check
the Proc box. To select everyone on the list, click the Proc button. You can then clear
the Proc box for anyone you dont want to process.
Warning Once youve selected an employee name for processing and migrated it to
Vista Plus, it is included in all future migrations. You will not be able to go
back and clear the Proc box after you have run migration. Be sure to select
only the employees you want to include in migration.
7.
You also have these options for each employee listed:
To set an end date in Vista Plus for the persons membership in this group, type
To see the passwords the users will have in Vista Plus, select Password in the
field above the user list. You can change any password by typing a new one.
To see the persons employee and applicant number, select Applicant/

Employee Number in the field above the user list.
8.
When youve selected all employees for this responsibility, click the Save button
on the Oracle Applications toolbar.
9.
Repeat steps 2 through 8 for each responsibility you want to add employees to.
10. When done, save your changes and close the form.
83
Adding Sales Reps to a Vista Plus Group

As with people entered as employees (see the previous section), people entered as Sales
Reps in Oracle Applications may benefit from being able to view reports in Vista Plus.
Therefore, the interface lets you take Oracle Applications sales rep records and create
Vista Plus users from them. You select a responsibility, then choose the sales reps for it.
Vista Plus users are created for each sales rep and made members of the appropriate Vista
Plus groups.
You can select sales reps to assign to a Vista Plus group only if you checked the sales rep
box for the responsibility when selecting the responsibilities to include in synchronization.
See page 76.
To create Vista Plus users from sales reps

1.
In the Navigator, select Define, User, Salesrep.
2.
On the User Salesrep form, select the responsibility you want to add sales reps to. Use
one of these methods:
3.
84
Applications sales rep records.
4.
For each person you want to add to the Vista Plus group for this responsibility, check
the Proc box. To select everyone on the list, click the Proc button. You can then clear
the Proc box for people you dont want to process.
Warning Once youve selected a sales rep name for processing and migrated it to
Vista Plus, it is included in all future migrations. You will not be able to go
back and clear the Proc box after you have run migration. Be sure to select
only the sales reps you want to include in migration.
5.
You also have these options for each sales rep:
To set an end date in Vista Plus for the persons membership in this group, type
To see the passwords the users will have in Vista Plus, select Password in the
field above the user list. You can change any password by typing a new one.
6.
When youve selected all sales reps for this responsibility, click the Save button
on the Oracle Applications toolbar.
7.
Repeat steps 2 through 6 for each responsibility you want to add sales reps to.
8.
Selecting the Reports to Transfer

After choosing responsibilities and users, you select the reports to transfer to Vista Plus.
This process creates the reports in Vista Plus and links them to the folders matching their
Oracle Applications responsibilities. During this process, you also select which reports to
create in users private folders; the reports in the private folders include the users name
in the report name so reports can be captured to them without being captured into the
report in the folder for the responsibility.
You can also select the reports to capture during this procedure. Or, you can wait and do
that after the initial migration of information, as described in Chapter 9.
Youll perform this procedure after initialization and again each time you synchronize the
data.
To select reports
1.
2.
85
3.
Example, Run.
4.
Select the reports to process into Vista Plus:
To select all reports in this responsibility, click the Proc button.
To select an individual report, check its Proc box.
To link all reports to users private folders, click the Priv button.
To link an individual report to users private folders, check its Priv box.
Warning Once youve selected a report for processing and migrated it to Vista Plus, it
is included in all future migrations. You will not be able to go back and clear
the Proc box after you have run migration. Be sure to select only the reports
you want to include in migration.
5.
If you want to select the reports to capture:
To select a single report, check its Cap box.
To capture all reports being processed into Vista Plus, click the Cap button.
6.
You can select reports for capture only if they are selected to be processed. You can
also select reports for capture later; see page 116.
7.
8.
When youve selected all reports for this responsibility, click the Save button on
the Oracle Applications toolbar.
9.
Repeat steps 2 through 7 for each responsibility you want to transfer reports for.
10. When done, save your changes and close the form.
86
Note
The rcapture commands created by the interface include the d, f, h, o and

t options. Do not enter any rcapture option on this form which would
conflict with the options used by the interface. You can find a complete list of
rcapture options in the Vista Plus Server Administration Guide.
Tip
If a report is in multiple responsibilities, you must select it separately for each.

If you do not select a report for a particular responsibility, it will not be linked
to that folder in Vista Plus.
Selecting the Destination Report Warehouse

Vista Plus Interface for Oracle Applications can copy information from a single Oracle
Applications instance into one or more Vista Plus report warehouses. You select the
responsibilities to copy to each report warehouse. All information for each selected
responsibility is copied to the warehouse. You cannot copy only some reports or users
from a responsibility to a warehouse.
You can select the same responsibility for more than one warehouse. Data for each
responsibility can be copied to one, some, or all of the defined report warehouses.
Note
Important! You must perform this procedure even if you are copying Oracle
Applications data into only one warehouse! If you do not, no information will
be transferred to Vista Plus.
To select the destination warehouse

1.
In the Navigator, select Define, Warehouse.
2.
On the Warehouse form, click in the Warehouse SID field then click the List of
Values button next to it. Select a warehouse from the list and click OK.
87
3.
From the View menu, select Query by Example, Run from the menu. This displays all
responsibilities being synchronized from this database.
4.
Select the responsibilities to copy to this report warehouse:
To select all responsibilities, click the Proc button. You can then clear the Proc
box for any responsibilities you do not want to copy to this warehouse.
To select an individual responsibility, check its Proc box.
Warning Once youve selected a responsibility and migrated it to a particular report

warehouse, it is included in all future migrations for that warehouse. You
will not be able to go back and clear the Proc box after you have run
migration. Be sure to select only the responsibilities you want to include in
this report warehouse.
88
5.
When youve selected all responsibilities for this warehouse, click the Save
button on the Oracle Applications toolbar.
6.
Repeat steps 2 though 5 for each warehouse you are synchronizing data with.
7.
Copying the Data into Vista Plus

Once youve selected the information to copy and the report warehouse(s) to copy it to,
the next step is to move it to Vista Plus. You do this by running the migration request. This
copies the data to text files, then creates and runs a script using the Vista Plus vadmin
command to write the data into the report warehouse.
To run the Migration request

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Migration request in the Name
field in one of these ways:
4.
Type it.
Migration from the list that displays and click OK.
Plus Indiv Migration from the list and click OK.
If you dont want to start the

request immediately, click the
Schedule button. On the
Schedule form:
Select Once.

the day and time.
Click OK.
5.

options, such as sending notification messages.
6.
7.
89
Capturing Reports
Capturing Reports
If you didnt do so when you selected the reports to process, you now need to select the
reports you want to have Vista Plus Interface for Oracle Applications capture
automatically each time they are printed. This procedure is covered is Chapter 9.
Until you select reports for capture, the interface will not capture any report generations
into Vista Plus.
90
Updating Vista Plus Information

As time goes by, your Oracle Applications data changes: youll add new reports and users,
change responsibility effective dates, and so on. So, after youve initially transferred data
from Oracle Applications to Vista Plus, youll need to resynchronize the information from
time to time to keep up. To do so, you follow the procedure given in step 9 in the
Procedure Overview section on page 72: submit the synchronization request, select the
information to update in Vista Plus, then submit the migration request. The next few
sections describe these steps.
Note
Unless the Recreate box is checked for a report warehouse on the Server form
(see page 54), migration copies only new and changed information to the
Vista Plus report warehouse. If you want to rewrite all data into Vista Plus
(for example, if a network or other error kept Vista Plus from being updated
correctly), check the Recreate box before running migration. In normal use,
youll want to have Recreate unchecked for better migration performance.
Synchronizing Data in the Interfaces Database

As when first copying data to Vista Plus, the first step in updating Vista Plus with new
Oracle Applications information is copying the data from Oracle Applications to the
interfaces custom Oracle Applications database. You do this using the synchronization
request.
Depending on how frequently your Oracle Applications data changes, you may want to
synchronize daily, weekly, or just when you feel its necessary. If you do plan regular
updates, you can schedule the synchronization request to run at regular intervals.
However, remember that with managed synchronization, after the request runs, you need
to manually select the responsibilities, users, and reports to update in Vista Plus.
Tip
If you are going to begin migrating information for a responsibility you have
previously excluded from synchronization, be sure to select the responsibility
for processing and for synchronization (see page 76) before you run
synchronization, not between synchronization and migration. Otherwise, the
migrated data will not be up to date.
To copy the latest data to the interfaces database

1.
2.
91
3.
4.
92
On the Submit Request form, select the Vista Plus Indiv Synchronization request in the
Type it.
Synchronization from the list that displays and click OK.
Plus Indiv Synchronization from the list and click OK.
Select Once,
Periodically, or On
Specific Days.

the day and time.

repeated execution,
other options.
Click OK.
5.

button to use any of the standard Oracle Applications options, such as sending
6.
7.
Tip
If you choose to schedule synchronization to run automatically at preset

intervals, be sure to schedule it so you have enough time to select the
information to migrate to Vista Plus and run the migration request before the
next synchronization.
Selecting the Information to Update

After synchronization, you need to select the information to update in Vista Plus. You do
this using basically the same procedure as when first transferring data from Oracle
Applications to Vista Plus. You must select responsibilities, users (including forcing users,
employees, and sales reps), and reports, in that order.
When you display the responsibilities (or users or reports), the ones you selected and
migrated to Vista Plus are checked; any updates to these records will be transferred to
Vista Plus. You cannot clear any of these check boxesonce youve transferred a record to
Vista Plus, changes to it are included in all future synchronizations.
If there are any new records, check the ones to include in the synchronization. Information
for these responsibilities, users, or reports will be included in the next migration. If a
responsibility had the Usr, Rpt, or All box checked during synchronization (see page 76),
all new users and/or reports are included by default, and you must clear the Proc box for
any that should not be migrated. If these boxes are not checked for a responsibility, a new
user or report is not migrated unless you check its Proc box.
You can also change reports from private to public, and vice-versa, at any time.
You cannot change the password for any user who has already been processed into the
report warehouse. Once a user has been created in Vista Plus, you can change the
password only using one the Vista Plus clients.
If there are any new responsibilities, you must select the report warehouse to transfer
them to, even if all of your information is going to one warehouse.
Step-by-step instructions on selecting responsibilities, users, reports, and destination
warehouses start on page 76.
Note
If there are records you didnt include in the initial migration, you can select
them during a later synchronization to add them to the Vista Plus report
warehouse.
93
Sending the Updates to Vista Plus

Once youve selected the information to update, you run the migration request to copy the
selected information from the interfaces database to Vista Plus. Follow the procedure on
page 89.
You can schedule the migration request to run at regular intervals, as you can the
synchronization request. However, since you must manually select the data to be updated
between the requests, you may not want to do this. If for some reason you are unable to
select information before the migration request runs, existing records will be updated
with any changes, but no new records will be copied to Vista Plus.
94
Chapter 8
Using Page-Level Security

This chapter describes the interfaces two features which allow you to crate page security
for reports in Vista Plus: page-level security by user and page-level security by group.
In This Chapter
Page-Level Security Overview .............................................................. 96
Page-Level Security by User .................................................................. 97
Page-Level Security by Group ............................................................. 101
95
Page-Level Security Overview
Page-Level Security Overview

Vista Plus page-level security uses the value of a report indexa specific field or area on
the report pageto control which pages of the report a user (or all the users in a group)
can view: each user can see a report page only if the index for that page contains a value
he or she (or his or her group) has been given access to.
The interface offers two ways for you to create Vista Plus page-level security:
Page-level security by user creates and assigns page securities to users in Vista Plus
based on Oracle Applications user, employee, or sales rep names or IDs.
Page-level security by group creates and assigns page securities to groups in Vista Plus
based on the value sets and security rules that exist in Oracle Applications. You can
define page security both for the responsibility the report belongs to and for other
Vista Plus groups that you want to be able to see the report in Vista Plus.
The following sections describe each kind of page-level security. You can use whichever
method best fits your situation; you can use security by user for some reports and security
by group for others.
96
Page-Level Security by User

The interfaces page-level security by user feature lets you control access to individual
pages within reports, based on user, employee, or sales rep name or ID. When you use this
feature for a report, each Vista Plus user will see only those report pages which contain his
or her name or ID. For sales reps, you can also base the security on a sales rep hierarchy, so
each user will be able to see a page if it contains his or her name or number, or one for
someone below him or her in the hierarchy.
For each report you want to use page-level security by user for, you choose whether to
base access on user name or ID, employee full name or number, or salesperson name or
number. The report must contain the field you choose, and you must be able to index that
field: it must either be in the same location on each page or it must be preceded by the
same text each time it appears. If the report meets these requirements, use this procedure
to implement page-level security for it:
1.
Migrate the report to Vista Plus. All users you want to control access to the report for
must also be migrated.
2.
Capture at least one generation to the report. In Vista Plus, create a report index
containing the data field to base security on: user name, employee full name, or one of
the others listed above.
3.
In the interface, use the Page Level Security by Users form to identify the Oracle
Applications data field and Vista Plus report index to use for page-level security for
the report.
4.
Run the page-level security by user request. This creates the page securities in Vista
Plus and assigns them to the appropriate users.
The sections below describe how to perform steps 3 and 4 of this procedure. See the Vista
Plus Web View online help or the Vista Plus Windows Client Users Guide for more
information about indexes and instructions on creating them. See the Vista Plus Server
Administration Guide for more information about page-level security.
Note
Important! In Vista Plus, page-level securities are defined for individual

reports. Users can then be assigned one of the page securities defined for the
report. The Vista Plus Indiv Page Level User request performs both these
operations. It also sets an option for each report it creates page security for, so
any user who is not assigned a page security cannot open the report at all,
even if it is linked to a folder the user can access.
Setting page-level security for one report has no effect on any other report.
Tip
Because each Vista Plus user can be assigned only one page security for a
given report, you can use only one of the data fields to control access to any
report. Once you have selected a data field to use for a report, the report will
not display in the report list for any other fields.
97
Tip
The information needed for page-level security by user is placed in the

interfaces database by the Vista Plus Indiv Initialization request and updated
as part of the Vista Plus Indiv Full Sync/Migrt request (for full synchronization)
or the Vista Plus Indiv Synchronization request (for managed synchronization).
If you want to update just the information for page-level security by user, you
can run the Vista Plus Indiv Page Level User Sync request.
To set up page-level security by user
98
1.
Make sure that the reports you want to use page-level security for have been migrated
to Vista Plus and have had the necessary indexes created.
2.
In the Navigator, select Define, Page Level Security, Users.
3.
Under Field Type, select the field you want to use for security.
4.
If necessary, scroll the Process Report list to display the report you want to create
page-level security for.
5.
Type the name of the index to use for security in the Index field for the proper report.
This must exactly match the index name in Vista Plus; index names, like other Vista
Plus data, are case-sensitive.
6.
If you select either Salesperson Number or Salesperson Name, you can select a
Hierarchy Name if you want to base the security on a salesperson hierarchy. To do so:
Click in the Hierarchy Name field, then click the List of Values button that
appears next to the field.
In the Hierarchy Name form, select the name from the list. You can type part of
the name and click Find to narrow down the list.
Click OK to close the Hierarchy Name form.
7.
Check the Proc box for the report.
8.
Repeat steps 3 7 for any other reports you want to create page-level security for.
9.
When youre done, click the Save button to save your settings, then close the
Page Level Security by Users form.
To create the page security in Vista Plus

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Page Level User request in the
Type it.
entry, it is entered. If there is more than one match, select Vista Plus Indiv Page
Level User from the list that displays and click OK.
Plus Indiv Page Level User from the list and click OK.
99
4.
100
Schedule form:
Select Once.

the day and time.
Click OK.
5.

6.

request.
7.
Page-Level Security by Group

Unlike page-level security by user, which is always based on user, employee, or
salesperson information, page-level security by group can be based on any Oracle
Applications field there are value sets and security rules for. For example, if a report
contains a company number on each page, and there are security rules defined for the
company number field in Oracle Applications; you can define Vista Plus page security for
that report based on company number.
To use page-level security by group for a report, the report must contain a value there are
security rules for in Oracle Applications. The value must appear on each page of the
report, and you must be able to index that field in Vista Plus: it must either be in the same
location on each page or it must be preceded by the same text each time it appears. If the
report meets these requirements, use this procedure to implement page-level security by
group for it:
1.
Migrate the report to Vista Plus. All responsibilities you want to control access to the
report for must also be migrated.
2.
Capture at least one generation to the report. In Vista Plus, create a report index
containing the data value to base security on.
3.
In the interface, use the Page Level Security by Group form to identify the Oracle
Applications value set and security rules and the Vista Plus report index (or indexes)
to use for page-level security for the report for the group that the report belongs to.
Use the value set which contains only the values users in the group should be allowed
to see. If you enter multiple conditions, using multiple indexes in Vista Plus, users in
the group will be allowed to see only pages which meet all of the conditions.
4.
If desired, define page securities for groups which cannot run the report in Oracle
Applications.You can use the Page Level Security by Group form or a separate request
to do this.
5.
Run the page-level security by group request. This creates the page securities in Vista
Plus and assigns them to the appropriate group. It also updates existing group page
securities based on any changes that have occurred in Oracle Applications. For
example, if the values allowed by a given security rule have changed, the page
securities based on that rule are updated (actually, deleted and recreated) in Vista
Plus.
6.
If you have assigned page security to any responsibility which cannot run the report
in Oracle Applications (step 4 above), you may need to give the corresponding group
access to the report in Vista Plus. If LINKRESP is set to Y on the System Profile form
(see page 42), this was done automatically in step 5. If LINKRESP is set to N, you
must use a Vista Plus client to create the links.
101
The sections below describe how to perform steps 3, 4, and 5 of this procedure. See the
Vista Plus Web View online help or Vista Plus Windows Client Users Guide for more
information about indexes and instructions on creating them. See the Vista Plus Server
Administration Guide for more information about page-level security and about linking
reports to folders.
Note
Important! In Vista Plus, page-level securities are defined for individual

reports. Groups can then be assigned one of the page securities defined for
the report. The Vista Plus Indiv Page Level Group All request performs both
these operations. It also sets an option for each report it creates page security
for, so users in any group that is not assigned a page security cannot open the
report at all, even if it is linked to a folder the group can access.
Setting page-level security for one report has no effect on any other report.
Tip
You may be able to define page-level security for multiple groups with one
operation; see page 105.
Tip
Before running page-level security by group for the first time, make sure the
APA and APAO values on the System Profile form are correct for your
installation. See page 40 for more about these settings.
To define page-level security for the group that owns a report

This procedure updates the interfaces database with the page securities you define. You
must then migrate this information to Vista Plus, as described on page 109, to have the
page security take effect.
102
1.
Make sure the reports you want to use page-level security for have been migrated to
Vista Plus and have had the necessary indexes created.
2.
In the Navigator, select Define, Page Level Security, Groups.
3.
In the Name field, enter the responsibility to list reports for. You can do this in three
ways:
Type it.
Type the first few characters and press Tab. If only one responsibility matches
your entry, it is entered. If there is more than one match, select the one you want
from the list that displays and click OK.
Click in the field, then click the List of Values button next to it. Select the
responsibility you want from the list and click OK.
4.
From the View menu, select Query by Example, Run. This lists the reports for the
responsibility (only reports which have been migrated, and have at least one
generation in Vista Plus, are listed).
5.
To define Vista Plus page-level security for a report for the listed responsibility (which
is a group in Vista Plus), do one of the following:
To use only one index:
Click the Value Sets field for the report. Click the List of Values button and
select the value set to use when defining the page security.
Click the Rule Name field. Click the List of Values button and select the
security rule to use when defining the page security. Only rules associated with
the selected value set are listed.
In the Index field, type the name of the Vista Plus report index to use when
defining the page security. This must be the index which contains the values
corresponding to the selected value set and security rule. Be sure to type the
name correctlyindex names, like other Vista Plus data, are case-sensitive.
103
To use more than one index:
Click Distribution.
In the Responsibility/Group field in the first line, type the name of the
responsibility you selected in step 3, or click the List of Values button and select
it from the list.
Click the Value Set field. Click the List of Values button and select the value set
to use for the page security.
Click the Rule Name field. Click the List of Values button and select the
security rule to use when defining the page security. Only rules associated with
the selected value set are listed.
In the Index field, type the name of the Vista Plus report index to use when
defining the page security. This must be the index which contains the values
corresponding to the selected value set and security rule. Be sure to type the
name correctlyindex names, like other Vista Plus data, are case-sensitive.
Repeat the previous 4 steps on the next line of the table, using a different index
in the Vista Plus report; the value set and rule name can be either the same or
different. Continue for as many indexes as you want to use.
When youre done, click the Save button to save your settings, then close
the Distribution form.
6.
Repeat step 5 for all reports for this responsibility you want to assign group page
security for.
7.
When youre done, click the Save button to save your settings.
8.
To list reports for a different responsibility, return to step 3. When youre done
with all reports, close the Page Level Security by Groups form.
Tip
104
If you want to define page-level security for responsibilities other than the
one that owns the report, after step 5, click the Distribution button and
continue from step 6 of the procedure in the next section.
Defining Page-Level Security for Other Groups

There are two ways to define page-level security for groups other than the one that the
report belongs to in Oracle Applications. One method is best when you have only one or a
few combinations of group, value set, and rule name to define; the other allows you to
define security for large numbers of groups, value sets, and rule names more quickly.
Before using either of the procedures below, make sure the report you want to use pagelevel security for has been migrated to Vista Plus and has had the necessary indexes
created. You do not have to define page-level security for the group that owns the report
before defining page-level security for other groups.
Both of these procedures update the interfaces custom database with the page securities
you define. You must then migrate this information to Vista Plus, as described on
page 109, to have the page security take effect.
To define page-level security for a report for different groups

This method is best when defining a small number of page security combinations. It is
very similar to the method described on page 102 for defining page-level security for the
group that owns the report.
If you have a large number of page-level security definitions to create, you may want to
use the second method below instead of this one.
1.
In the Navigator, select Define, Page Level Security, Groups.
2.
In the Name field, enter the responsibility to list reports for. This must be the
responsibility that owns the report, not the one you want to define page-level security
for. You can do this in three ways:
Type it.
3.
From the View menu, select Query by Example, Run. This lists the reports for the
responsibility (only reports which have been migrated, and have at least one
generation in Vista Plus, are listed).
4.
Click the report name to select it.
105
5.
Click Distribution.
6.
In the Responsibility/Group field in the first line, type the name of the responsibility
to assign page security for, or click the List of Values button and select it from the list.
7.
Click the Value Set field. Click the List of Values button and select the value set to use
for the page security.
8.
Click the Rule Name field. Click the List of Values button and select the security rule
to use when defining the page security. Only rules associated with the selected value
set are listed.
9.
In the Index field, type the name of the Vista Plus report index to use when defining
the page security. This must be the index which contains the values corresponding to
the selected value set and security rule. Be sure to type the name correctlyindex
names, like other Vista Plus data, are case-sensitive.
10. To assign page security for this report for another responsibility or using another
index for this responsibility, repeat the previous 4 steps on the next line of the table.
11. When youre done, click the Save button to save your settings, then close the
Distribution form.
106
To define multiple page-level securities for a report

If you want to define page-level security for a lot of responsibilities (Vista Plus groups) or
value set-rule name combinations, the previous method can be time-consuming. Instead,
you can use the method below, which lets you use wildcards to specify multiple
responsibilities and/or rule names at once.
1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Page Level Group Ins request in
the Name field in one of these ways:
Type it.
Type the first few characters and press Tab. If only one request matches
your entry, it is entered. If there is more than one match, select Vista Plus
Indiv Page Level Group Ins from the list that displays and click OK.
Click in the field, then click the List of Values button next to it. Select Vista Plus
Indiv Page Level Group Ins from the list and click OK.
This displays the Parameters form for the request.
4.
In the Method field, enter Insert.
5.
In the Responsibility that Owns Report field, enter the responsibility to list reports
for. You can do this in three ways:
Type it.
107
6.
Enter the Report to define page-level securities for. You can use the same three
methods as in the previous step. If you list reports, only reports which belong to the
responsibility, have been migrated to Vista Plus, and have at least one generation in
Vista Plus are listed.
7.
In Responsibility/Group, type the name of the Vista Plus group you want to define
page-level securities for. You can use the % wildcard to define securities for more than
one group at a time. For example, Gen% defines securities for all groups that start with
Gen.
8.
In Value Set, type the name of the value set to use for the page-level securities you are
defining.
9.
In Rule Name, type the name of the security rule to use to define the page-level
securities. You can use the % wildcard to define page securities for more than one rule
at a time. For example, West% defines securities for all rules that start with West.
10. In Index, type the name of the Vista Plus report index to use for the page-level
securities. Remember that index names are case-sensitive.
11. Click OK. This closes the Parameters form.
12. If you dont want to start the request immediately, click the Schedule button. On the
Schedule form:
Select Once.

the day and time.
Click OK.
13. You can also click the Options

14. Click Submit to start the
request.
15. To check the status of the request, from the View menu, select Requests.
108
Tip
To delete page securities you no longer want, follow the above procedure, but
enter DELETE instead of INSERT in step 4. If the page-level securities have
already been migrated to Vista Plus, they will be deleted the next time you
run the page-level security migration or synch/migration request.
Note
You may submit this request multiple times to define page-level security for
various reports, groups, and so on. If so, the requests will run consecutively,
not concurrently; each one will start only when the previous one finishes.
Creating the Page-Level Security in Vista Plus

The procedures described in the previous section create definitions for the page-level
security you want in Vista Plus, and store those definitions in the interfaces custom
database. To make the page-level security take effect, you must copy this information to
Vista Plus; it is not copied by the standard migration request. You must run the page-level
security by group request to do so.
The page-level security by group request (Vista Plus Indiv Page Level Group All) performs
two functions. First, it finds any value sets, rule names, or other pertinent data that has
changed in Oracle Applications and updates the interfaces database. It then takes this
information and any page-level security definitions youve entered in the interface and
updates page securities in Vista Plus.
If the Vista Plus Indiv Page Level Group All request takes a long time to run, or if you want
to perform only one of its two functions, you can run these requests instead:
Vista Plus Indiv Page Level Group Sync This request updates the interfaces database
with changed value set and rule name data from Oracle Applications. It does not
transfer any information to Vista Plus.
Vista Plus Indiv Page Level Group Migrate This request updates Vista Plus page
security with the current group page-level security information from the interfaces
database. It does not check the Oracle Applications database for updated information.
You can run either of these requests by following the procedure below, but substituting
the request you want for Vista Plus Indiv Page Level Group All in step 3.
To create page security in Vista Plus

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Page Level Group All request in
Type it.
Type the first few characters and press Tab. If only one request matches
your entry, it is entered. If there is more than one match, select Vista Plus
Indiv Page Level Group All from the list that displays and click OK.
Click in the field, then click the List of Values button next to it. Select Vista Plus
Indiv Page Level Group All from the list and click OK.
109
4.
110
Schedule form:
Select Once.

the day and time.
Click OK.
5.

6.

request.
7.
Tip
If you assigned page-level security for a report to a responsibility which does

not have access to the report in Oracle Applications, users in that group will
not be able to see the report unless you link it to the folder for the group. If
LINKRESP is set to Y on the System Profile form (see page 40), this is done
automatically by the Vista Plus Indiv Page Level Group All request. If
LINKRESP is set to N, you must link the report to the folder using a Vista Plus
client.
Tip
If the request takes too long to complete, you may be able to speed it up by
modifying the WORKERS setting on the System Profile form. See page 40 for
more information.
Chapter 9
Capturing Reports
Previous chapters discussed the initial transfer of the Oracle Applications user/
responsibility/report structure to Vista Plus, and how to keep the Vista Plus information
synchronized with changes to the Oracle Applications data. This chapter describes using
Vista Plus Interface for Oracle Applications to automate the heart of the Vista Plus system:
capturing reports from Oracle Applications and placing them in the Vista Plus report
warehouse.
In This Chapter
Capture Overview ................................................................................. 112
Selecting the Reports to Capture ......................................................... 116
Scheduling the Report Capture Request ............................................ 119
Retrieving Missing Reports .................................................................. 121
Reprinting Reports ................................................................................ 124
Removing Reports from the Capture Table ....................................... 125
Linking, Unlinking, and Deleting Reports ........................................ 126
Capturing Reports
111
Capture Overview
Capture Overview
Capturing reports is the heart of the Vista Plus product. Because reports go into the report
warehouse instead of, or in addition to, being printed, they are instantly available to the
people who need to use them, throughout your organization. Vista Plus Interface for
Oracle Applications simplifies report capture from Oracle Applications reports: you
simply select the reports to capture. Then, when one of those reports is run, it is captured
in one of two ways:
If it is sent to a printer defined for immediate capture, a command to capture the

report is sent to Vista Plus as soon as the report request is finished.
If it is not sent to an immediate capture printer, and if it meets the criteria you have
selected for capture (see page 47), information about the report run is placed in the
report capture table in the interfaces database. The report is then captured to Vista
Plus the next time the report capture request is run. You can set this request to repeat
automatically, so each generation is captured on the schedule you set.
To prepare for capture, you need to:
Select the capture method, as described on page 47. This determines when running a
selected report places it in the report capture table and when it does not.
Select the reports to have captured into Vista Plus. With managed synchronization,
you can do this either when you select the reports to migrate, as described starting on
page 85, or afterward, as described on page 116. With full synchronization, you must
select the reports after migration. If you use full synchronization and have capture for
full synchronization on (see page 48), you do not select reports: all Oracle
Applications reports are captured.
If you will be using immediate capture, define the printer or printers to use. You
define these printers first in Oracle Applications, then in the interface. The procedure
is described starting on page 114.
If you will be sending reports from the interface to Vista Plus Output Manager,
configure the interface to work with Output Manager, as described in Appendix B.
Once youve set your options, selected the reports, and defined printers for immediate
capture, this is what happens when you run a report that has been selected for capture:
112
1.
If it is sent to a designated immediate capture printer, the interface captures it

immediately.
2.
If it is not sent to an immediate capture printer, but does meet the capture method
criteria, the interface places it into the Vista Plus capture table. This table lists reports
waiting to be captured into the report warehouse.
Capture Overview
3.
The next time the report capture request runs, it creates a script containing Vista Plus
rcapture commands for all report requests found in the Vista Plus capture table. It
then executes the script to capture the output from these reports into the report
warehouse as new report generations.
In most cases, youll want to schedule the report capture request to run on a regular
schedule, so reports are captured with no intervention necessary. How often to run it
depends on how many reports you run, how big they are, and how quickly you want
your users to have access to them from Vista Plus. In most situations, scheduling the
request every 15 to 30 minutes works well.
The rest of this chapter describes how to define printers for immediate capture, select
reports for capture and run or schedule the report capture request. It also describes how
you can recapture reports if an error keeps the report from successfully being captured
into the report warehouse.
Note
Capturing Reports
Reports set to private are captured into Vista Plus only if they are run by a
user with a private folder in Vista Plus. See page 14.
113
Selecting Printers for Immediate Capture

When a report selected for capture is printed to a printer defined for immediate capture,
the interface immediately creates and executes an rcapture command to capture the report
run as a Vista Plus generation. The capture does not wait until the next time the report
capture request runs.
Defining a printer to use for immediate capture is a two-step process. First, the printer
must be defined in Oracle Applications: this includes defining a printer driver, printer
style, printer type, and printer. The printer driver must have specific characteristics. The
interfaces installation script takes care of this step, defining four different printers you
can use for immediate capture, each for a different page size. These are:
Vista Plus A4
Vista Plus Landscape
Vista Plus Landwide
Vista Plus Portrait
Once the printers have been created, you use the Server form in the interface to select the
one(s) you want to use for immediate capture, following the procedure is shown below.
When you print a report to an immediate capture printer, it is only captured; it cannot also
be printed. Print only reports which have been selected for capture in the interface (see
page 116) to an immediate capture printer.
Note
114
Immediate capture through the interface does not use a Vista Plus Print
Queue. Instead, the interface builds and executes a Vista Plus rcapture
command. This enables the interface to capture the report to the correct report
and folder.
To select printers for immediate capture in the interface

1.
In the Navigator, select Administration, Server.
2.
On the Server form, click in the first field of the first row of the Printer Definition
section at the bottom of the form.
3.
Type the name of the immediate capture printer, or click the List of Values button and
select the printer from the list. When you select the printer, the rest of the fields on the
line are also filled in.
4.
To select this printer for immediate capture, check the box at the end of the row. If you
do not check this box, reports printed to this printer will not be captured immediately.
5.
After selecting a printer and checking the box, click the Save button or, from the
File menu, select Save. You must save each printer before going on to the next.
6.
Repeat steps 3 through 5 for each immediate capture printer. if there is no blank line,
click in the last line and press the Down Arrow key to create a blank line.
7.
When done, save the last printer and close the form.
Tip
Capturing Reports
You can use the check box for each printer to temporarily turn off immediate
capture without removing the printer from the list. Just clear the check box if
you dont want reports sent to the printer to be captured, then check it again
when you want to resume capturing. Be sure to save any change you make.
115
Selecting the Reports to Capture

If you use managed synchronization, or full synchronization with capture for full
synchronization off (see page 48), you select each report you want Vista Plus to capture.
This gives you complete control over exactly which report runs are captured into the
report warehouse. Once you select a report for capture, it is captured each time it is run
as long as it meets the capture method criteria, as described on page 47until you
choose to stop capture. Each captured report becomes a new generation of the Vista Plus
report.
You select reports for capture either at the same time you select the reports to process into
the Vista Plus report structure, as described in Chapters 6 and 7, or after the initial transfer
of information from Oracle Applications to Vista Plus. You can select additional reports at
any time; youll need to do so after adding new reports to Vista Plus during
synchronization. You can also change reports from private to public, or vice-versa.
The procedure for selecting reports to capture is very similar to the one for selecting
reports to process to Vista Plus, as shown on page 85.
Note
If you use full synchronization with capture for full synchronization on, all
reports are captured. Skip this section unless you want to set some reports to
private.
If a report has not yet been migrated into the report warehouse, you can
choose not to do so by clearing its Proc box during this procedure. Once a
report has been migrated to Vista Plus, it is included in all future migrations;
you cannot clear its Proc box.
To select reports for capture
116
1.
2.
3.
Example, Run.
4.
Select the reports to capture into Vista Plus:
To select all reports in this responsibility, click the Cap button.
To select an individual report, check its Cap box.
To stop capturing a report, clear its Cap box.
5.
If you want to change the private status of a report, check or clear its Priv box.
6.
7.
When youve selected all reports for this responsibility, click the Save button on
the Oracle Applications toolbar.
8.
Repeat steps 2 through 7 for each responsibility you want to capture reports for.
9.

Note
Capturing Reports
The rcapture commands created by the interface include the d, f, h, o,

and t options. Do not enter any rcapture option on this form which would
conflict with the options used by the interface. You can find a complete list of
rcapture options in the Vista Plus Server Administration Guide.
117
Printing Reports for Capture
Printing Reports for Capture

Once youve selected the reports to capture and defined printers for immediate capture,
reports you run in Oracle Applications with the proper options will get captured into
Vista Plus. The options you need to set are different based on how you want the reports to
be captured:
If you want a report to be captured immediately, you must set the number of copies to
one (or greater, though setting a higher number of copies will have no effect), and
send it to a printer defined for immediate capture (see page 114).
To capture a report with the report capture request, run it and make sure your
selections match the capture method youve set (see page 47). For example, you may
have to set the number of copies to 0, or pick a specific printer. Running the report
capture request to actually capture the reports into Vista Plus is described in the next
section.
Note
118
Both immediate capture and the report capture request will capture only
reports that have been selected for capture in the interface. Reports that have
not been migrated and selected for capture will not be captured by the
interface, no matter what settings you use when printing them.
Scheduling the Report Capture Request

As soon as you select the reports to capture, Vista Plus Interface for Oracle Applications
begins monitoring your report activity. Whenever a report which should be captured is
printed, it is placed into the Vista Plus capture table (one of the tables in the Oracle
Applications database created and used by the interface). However, reportsexcept for
those printed to an immediate capture printerare not actually captured into the Vista
Plus report warehouse until you run the report capture request. This request uses the Vista
Plus rcapture command to capture each report from the capture table into the report
warehouse.
In most cases, you will want to schedule the request to repeat at intervals, so reports are
automatically captured without any intervention necessary. However, you do not have to
do this; you can start the request manually whenever you want to capture reports. You
may want to use the manual method until you are sure the reports youve selected are
really the ones you want.
When you do schedule the request, the timing will depend on a number of factors: how
often you print reports, how many you print, how big they are, and how quickly you want
your users to have access to them. You should also consider the overall load on your
server. In most situations, we recommend you start by running the request every 15
minutes and adjust it as needed.
To schedule the report capture request

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Capture Generation request in
Type it.
Capture Generation from the list that displays and click OK.
Plus Indiv Capture Generation from the list and click OK.
Capturing Reports
119
4.
Select Once, Periodically, or On Specific Days.

the day and time.

repeated execution,
other options.
Click OK.
5.

6.
7.
Tip
120
Even if you set a schedule for the request, you can return to this form and run
it at any time. You can also adjust the schedule; you may want to do so as you
get a better idea of the number and size of the reports being captured. You can
check the reports waiting in the Vista Plus capture table using one of the List
Reports features, as described starting on page 130.
Retrieving Missing Reports

While it should be rare, it is possible for a report not to be properly placed into the
interfaces capture table. The most common reason for this would be a network error. If
this does happen, the report wont be captured into Vista Plus unless you specifically have
the report information copied from the Oracle Applications Concurrent Request Jobs table
into the capture table. This is called retrieving the report.
You can find out if a report was properly placed in the interfaces database using the List
Reports All feature. See page 131.
The interface includes two concurrent request jobs: one lets you retrieve a specific report;
the other retrieves all reports from a specified date/time range.
Note
If you retrieve a report which was intended for immediate capture, it is

captured by the report capture request the next time the request runs.
Retrieving a Specific Missing Report

If for any reason an Oracle Applications report is not placed into the report capture table
in the interfaces database, you can retrieve the report using the procedure below.
Tip
Before following this procedure, view the Oracle Applications Concurrent

Request Jobs list to find the request ID of the report you want to retrieve into
the interfaces database.
To retrieve a missing report

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Recover Request ID request in
Type it.
Recover Request ID from the list that displays and click OK.
Plus Indiv Recover Request ID from the list and click OK.
Capturing Reports
121
4.
On the Parameters form, type the request ID for the report you want to retrieve into
the report capture table. Click OK.
5.
Click Submit to submit the job now, or click Schedule to schedule the job for a later
time. You can also click the Options button to use any of the standard Oracle
Applications options, such as sending notification messages.
6.
Retrieving All Reports for a Date Range

If more than one report was not placed in the interfaces report capture table, you can run
a request to retrieve all reports for a date/time range. The request compares the Oracle
Applications Concurrent Request Jobs table to the report capture table in the interfaces
database and inserts any missing reports into the table. You may need to do this if, for
example, a network problem prevented anything from being written to the table for a
period of time.
When entering the date/time range, remember that the report completion timenot the
time it was requested or the time it begandetermines whether the report is retrieved.
Note
122
Retrieving a report is possible only if the report information has not been
purged from Oracle Applications. Once the report is purged, you must rerun
it in Oracle Applications if you wish to capture it into Vista Plus.
To retrieve all reports for a date range

1.
2.
On the Submit Request form, select the Vista Plus Indiv Recover Date request in the
Type it.
Recover Date from the list that displays and click OK.
Plus Indiv Recover Date from the list and click OK.
3.
On the Parameters form, enter the starting and ending date and time. All reports
which completed between these times and are not already in the report capture table
will be retrieved. Click OK.
4.
Click Submit to submit the job now, or click Schedule to schedule the job for a later
time. You can also click the Options button to use any of the standard Oracle
5.
Capturing Reports
123
Reprinting Reports
Reprinting Reports
It is also possible for a report to be included in the report capture table but not be captured
into Vista Plus. Network problems or an error on the Vista Plus server could keep the
report from reaching the Vista Plus report warehouse, though it appears in the interface
that the report has been captured. If this occurs, you can reprint the report.
Note
Reprinting a report is possible only if the report information has not been
purged from Oracle Applications. Once the report is purged, you must rerun
it in Oracle Applications if you wish to capture it into Vista Plus.
Note
If you reprint a report which was intended for immediate capture, it is

captured by the report capture request the next time the request runs.
To reprint a report
1.
From the Navigator, select Administration, Reports, Reports. If you want to reprint
an FSG ad hoc or FSG detail report, select FSG Adhoc or FSG Detail instead of
Reports.
2.
Click in either of the Date Range fields. This sets the default date range to today. To
change the range, type the Start and/or End date.
3.
Click Refresh to list the reports run for capture during the date range.
4.
Reports with a Status of Completed should exist in the Vista Plus report warehouse. If
capture failed for a report and you want to retry the capture, check its Reprint box. To
mark all Completed reports for recapture, click the Reprint button.
5.
When youve marked all the reports you want to recapture, close the form.
Reports marked for reprinting will be captured into Vista Plus the next time the report
capture request runs.
124
Removing Reports from the Capture Table
Removing Reports from the Capture Table

If a report ends up in the Vista Plus capture table but you do not want to capture it into the
report warehouse, you can remove it from the table while its status is still Pending. This
removes the entry for this report request from the table; it does not remove the report from
Vista Plus or affect any existing or future generations of it.
You can also delete a report from the table after it has been captured, but there is generally
no reason to do this. If the table gets too large you can delete all completed reports; see
page 132.
To remove a report from the table

1.
From the Navigator, select Administration, Reports, Reports. This displays the List
Reports All form with a list of all reports captured into Vista Plus, currently being
captured, or waiting to be captured. If you want to delete an FSG ad hoc report or FSG
detail report, select FSG Adhoc or FSG Detail instead of Reports.
2.
Click in any field of the line for the report you want to delete.
3.
On the toolbar, click the Delete button.
4.
When youve deleted all the reports you want to, save your changes by clicking
the Save button or selecting Save from the File menu.
5.
Close the form.
Capturing Reports
125
Linking, Unlinking, and Deleting Reports

By default, if you remove an Oracle Applications report from its responsibilities, the
report is unlinked from its folders in Vista Plus during the next migration. The existing
generations remain stored in Vista Plus, but they are not available to users. If you want to
delete the report entirelyincluding all existing generationsrather than just unlinking
it, you can do so using the Link/Unlink/Delete Report function. You can also use this
function to relink a report to a Vista Plus folder, even if it has not been reassigned to the
responsibility in Oracle Applications.
Its important to understand the difference between unlinking a report and deleting it:
When you unlink a report, Vista Plus Interface for Oracle Applications removes the
report from the folder for this responsibility. The report still exists in Vista Plus, and
any existing generations remain in the report warehouse, though they are not
available from any Vista Plus viewer client. If you reactivate and run the report in
Oracle Applications, a new generation will be captured in Vista Plus, and the report
will be relinked in Vista Plus during the next migration.
Deleting a report removes it completely from Vista Plus. All generations are removed,
and the report itself is unlinked from all folders it belongs to and deleted from the
warehouse. If you reactivate the report in Oracle Applications, you will need to
remigrate it to Vista Plus before you can resume capturing generations; the previous
generations cannot be restored (unless you had backed them up before deleting).
If you want to unlink all reports in Vista Plus if they are removed from a responsibility in
Oracle Applications, you do not need to use this function. If you do not make any
changes, each report is unlinked during the migration after it is removed in Oracle
Applications.
The Link/Unlink/Delete Report Form

The report list on the Link/Unlink/Delete Report form shows only those reports which
have been copied to Vista Plus, then removed from a responsibility in Oracle
Applications. Reports which were never migrated to Vista Plus and reports which are still
active in Oracle Applications are not listed.
Reports are added to this list by the first synchronization after they have been removed
from an Oracle Applications responsibility. For each report, there are three check boxes:
Proc: This box indicates the report has been copied to Vista Plus through the
migration process. It should always be checked; you cannot change it on this form.
Link: When a report first appears in the list after synchronization, this box is checked,
since the report is still linked to its Vista Plus folders. When you run migration, the
report is unlinked from its folders, and this box is cleared.
If a report has already been unlinked, you can check this box to relink it to the folder
for this responsibility in Vista Plus, even if it has not been re-added to the
corresponding responsibility in Oracle Applications. Since it is inactive in Oracle
126
Applications, no more generations will be captured, but existing generations will

again be viewable in Vista Plus.
Del: If you check this box, the report and all its generations will be deleted from the
Vista Plus report warehouse. Once the report is deleted, it will no longer display on
this form.
Any actions you take on this form (unlinking, relinking, or deleting a report) take effect in
Vista Plus the next time the Migration request is run.
To link, unlink, or delete a report

1.
In the Navigator, select Administration, Link/Unlink/Delete Report.
2.
By default, each newly listed report will be unlinked from its Vista Plus folder. To
delete a report and all its generations from Vista Plus, rather than just unlinking it,
check its Del box.
3.
If you want to relink a report which has already been unlinked from its Vista Plus
folder, check its Link box.
4.
When youre done, save your changes and close the form. Any actions you requested
will occur during the next migration.
Capturing Reports
127
128
Chapter 10
Monitoring Interface Activity

Vista Plus Interface for Oracle Applications includes utilities for monitoring the activity of
the interface. Of these, youll probably use only the report capture monitor regularly, and,
if you use the random password option, the password list. The other lists and the log file
utilities can be useful in certain situations but are generally needed only if youre trying to
find the cause of a problem.
In This Chapter
Monitoring Report Capture ................................................................. 130
Listing Information Sent to Vista Plus ................................................ 135
The Process Log Form ........................................................................... 137
The Vista Plus Error Log ....................................................................... 139
129
Monitoring Report Capture

To make sure the correct reports are being sent to Vista Plus, and to determine the best
schedule for the report capture request, it can be very helpful to look at the status of the
report files being captured into the report warehouse. For example, if many reports have
already been run, but are still waiting to be captured into Vista Plus, you may want to
increase the frequency of the report capture request (see page 119). There are four report
capture features which display different lists of reports:
List Reports by Responsibility shows all the reports for the responsibility you select.
It does not include FSG Ad hoc reports.
List Reports All shows reports for all responsibilities in a single list. It also does not
include FSG Ad hoc reports.
List Reports FSG Adhoc lists all FSG ad hoc reports.
List Reports FSG Detail lists all reports captured to the FSG detail folder structure.
List Reports All, List Reports FSG Adhoc, and List Reports FSG Detail let you reprint a
report if a network error or some other problem kept it from being properly captured into
Vista Plus. See page 124 for more information on reprinting reports. You can also remove a
report from the capture table; see page 125. You do not have the option to reprint or delete
a report when you use List Reports by Responsibility.
On all report lists, each report has one of three statuses: reports which have been run but
have not yet started capture are Pending, reports which are in the process of being
captured are Running, and reports which have been captured are Completed.
You can clear the standard report list, the FSG ad hoc list, and the FSG detail list using
requests included with the interface. Instructions are included following the instructions
for listing each type of report.
In addition to these interface features, there is also a log file, viewable from the Process
Log form, as described on page 137, which lists the report files captured by the current or
most recent capture request.
130
To look at the reports for a single responsibility

1.
In the Navigator, select Administration, Reports, Responsibility.
2.
Select a responsibility in one of these ways:
3.
To display the reports which have been run for this responsibility, from the View
menu, select Query by Example, Run.
4.
You can repeat steps 2 and 3 to see reports which belong to another responsibility.
To look at reports for all responsibilities

1.
From the Navigator, select Administration, Reports, Reports. This displays the List
Reports All form.
2.
131
3.
Click Refresh to list the reports run for capture during the date range.
4.
5.
To clear the report list

1.
From the Navigator, select Other, Requests, Run.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Del Reports All request in the
4.
Type it.
Reports All from the list that displays and click OK.
Plus Indiv Del Reports All from the list and click OK.
Click Submit to run the request immediately or click Schedule to schedule it to run
later. You can also click the Options button to use any of the standard Oracle
Note
132
This removes all reports with a Completed status from the report list.
Pending and Running reports are not affected.
To look at FSG ad hoc reports

1.
From the Navigator, select Administration, Reports, FSG Adhoc.
2.
3.
Click Refresh to list the reports run during the date range. This lists all FSG Ad hoc
reports run for capture during the date range.
4.
5.
To clear the FSG ad hoc report list

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Del FSG AD HOC request in
4.
Type it.
FSG AD HOC from the list that displays and click OK.
Plus Indiv Del FSG AD HOC from the list and click OK.
Note
To look at FSG detail reports

1.
From the Navigator, select Administration, Reports, FSG Detail.
2.
3.
Click Refresh to list the FSG detail reports run for capture during the date range.
4.
5.
133
To clear the FSG detail report list

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Del FSG Detail request in the
4.
Type it.
FSG Detail from the list that displays and click OK.
Plus Indiv Del FSG Detail from the list and click OK.
Note
To view the capture request log file

To view the capture request log file, select the report capture process on the Process Log
form and click the Log button. See page 137 for more information.
This log file contains only information from the most recent execution of the report
capture request. If the request is currently running, it contains only information for the
current execution. You do not need to clear information from this file.
134
Listing Information Sent to Vista Plus

The interface includes several reports you can print to show the individual users, reports,
and so on that are being processed and migrated to Vista Plus. You can list:
Responsibilities
Reports
Users
Users being forced into other Vista Plus groups (see page 80)
Employees
Sales reps
Passwords assigned to all users created in Vista Plus. This can be especially useful if
you are using the random password option, as it lets you tell users what their Vista
Plus passwords are. However, if a user has changed his or her password in Vista Plus,
this list will be incorrect; it lists only the passwords assigned by the interface.
The procedure for printing each of the lists is the same, as described below.
135
To print a list of items being migrated

1.
2.
3.
On the Submit Request form, in the Name field, select the list request you want: Vista
Plus Indiv User List, Vista Plus Indiv Report List, Vista Plus Indiv Resp List, Vista Plus
Indiv User Emp List, Vista Plus Indiv User Force List, or Vista Plus Indiv User Sales List.
You can select it in one of these ways:
4.
136
Type it.
Type the first few characters and press Tab. This displays a list of requests
starting with your entry. Select the one you want and click OK.
request from the list and click OK.
The Process Log Form

The Process Log form enables you to view two types of information which could be useful
if you suspect there are problems with any of the requests which send information from
Oracle Applications to Vista Plus. In most cases, you will need to use this form only if you
are asked to by customer support.
The top part of the form shows the Vista Plus process log. This log records the number of
itemsusers, responsibilities, and so onprocessed by each portion of the
synchronization and migration requests. Since it updates as the requests are running, you
can use it to see how they are progressing. You can also look at the process log after
synchronization or migration finishes to see how much information has been transferred
from Oracle Applications and into Vista Plus.
The bottom part of the form shows the shell, data, and log files created by the various
processes that write data to Vista Plus: migration, page security, and report capture. You
can view the contents of any of the files by clicking the appropriate button, as described
below.
137
To use the process log form

1.
In the Navigator, select Administration, Logs, Process.
2.
To view the process log contents, simply scroll the display on the top half of the form.
To search for specific information, from the View menu select Query by Example,
Enter and create an Oracle Applications query.
3.
To view the contents of a shell, data, or log file:
138
Click in any of the fields in the row for the process whose file you want to open.
Click the button for the file type: Shell, Dat, or Log.
Use the features of the viewer to look through the file.
The Vista Plus Error Log

The Vista Plus error log contains any errors encountered by previous synchronization,
migration, or report capture requests. You should not often need to look at the error log; it
is useful only if some Oracle Applications error prevents a request from completing.
Tip
You can see the status of any request while its running by selecting Requests
from the View menu.
To view the Vista Plus error log

1.
In the Navigator, select Administration, Logs, Error. This displays the Error Log form.
2.
If you are searching for specific information, from the View menu, select Query by
Example, Enter and create an Oracle Applications query.
139
To clear the error log

1.
2.
3.
On the Submit Request form, select the Vista Plus Indiv Del Error Log request in the
4.
140
Type it.
Error Log from the list that displays and click OK.
Plus Indiv Del Error Log from the list and click OK.
Appendix A
Files Installed
During installation, various files are installed on the Oracle Applications server and on
the middle-tier server. These are described in the tables below.
In This Appendix
Files Installed on the Oracle Applications Server ............................. 142
Files Installed on the Middle Tier or Oracle Client Manager .......... 145
Files Installed
141
Files Installed on the Oracle Applications Server

All of these PL/SQL files are placed in the $QV_TOP/sql directory:
File
Description
qsdel11p.pls
qsdel11b.pls
For Oracle Applications 11.0.x, deletes Vista Plus objects from the
interfaces database
qsdel1ip.pls
qsdel1ib.pls
For Oracle Applications 11.5.5 through 11.5.10, deletes Vista Plus objects
from the interfaces database
qsubrlip.pls
For Oracle Applications 11.5.5 through 11.5.10, a stand-alone function

that submits a concurrent job within a calling PL/SQL program owned
by apps.
qsvcglop.pls
qsvcglob.pls
Common-use procedure called by other PL/SQL procedures
qsvcimdp.pls
qsvcimdb.pls
Handles all immediate capture via printer definition
qsvcsfgp.pls
qsvcfsgb.pls
Handles all batch and ad hoc FSG reports
qsvcst2bp.pls
qsvcst2b.pls
Migrates all objects into Vista Plus report warehouse (with qsvcst3bp.pls,
qsvcst3b.pls, qsvcstrp.pls and qsvcstrb.pls)
qsvcst3bp.pls
qsvcst3b.pls
qsvcst3b.pls, qsvcstrp.pls and qsvcstrb.pls)
qsvcstrp.pls
qsvcstrb.pls
qsvcst2b.pls, qsvcst3bp.pls, and qsvcst3b.pls)
qsvcsyip.pls
qsvcsyib.pls
Used during synchronization on Oracle Applications 11.5.5 through

11.5.10
qsvcsynp.pls
qsvcsynb.pls
Used during synchronization on Oracle Applications 11.0.x
qsvctrgp.pls
qsvctrgb.pls
Controls which Oracle Applications reports should be captured into

Vista Plus
qsvir11p.pls
qsvir11b.pls
Installation procedure for Oracle Applications 11.0.x
qsvir1ip.pls
qsvir1ib.pls
Installation procedure for Oracle Applications 11.5.5 through 11.5.10
qsvpatcp.pls
qsvpatcb.pls
Used during upgrades and patch installation
qsvpgsep.pls
All page-level security functions
qsvpgseb.pls
qsvutilp.pls
qsvutilb.pls
142
Utilities program
These SQL Plus files are also placed in $QV_TOP/sql:
File
Description
qscpgbpr.sql
Executes package procedure used for page-level security
qscrole.sql
Creates Oracle role for QV schema.
qscsyn11.sql
Custom synonym for Oracle Applications 11.0.x
qscsyn1i.sql
Custom synonym for Oracle Applications 11.5.5 through 11.5.10
qscviw11.sql
Custom views for Oracle Applications 11.0.x
qscviw1i.sql
Custom views for Oracle Application 11.5.5 through 11.5.10,
qsrevoke.sql
Revoke QV schema current privileges
qsvadm10.sql
Calls a shell script (qsvaadm02.sh) which calls sql files to create the data
file and execute the vadmin commands
qsvadm30.sql
Creates the data files that contain the vadmin commands
qsvadm40.sql
Create the vadmin command to execute the vadmin commands
qsvadm50.sql
Resets the sequence the number use by qsvp_stage_0. This needs to be

executed manually by qv.
qsvadm60.sql
Creates a vadmin session command.
qsvcdelp.sql
Creates a dynamic shell script to delete all objects previously copied to

Vista Plus
qsvcdelt.sql
Used during uninstallation: drops all custom packages, synonyms and

sequences from the database
qsvcgrta.sql
Grants packages owned by apps to qv
qsvcgrtq.sql
Grants packages owned by qv to apps
qsvcinit.sql
Initializes all custom attribute fields used during installation and

upgrade
qsvckusr.sql
Checks if the Oracle Applications user QVISTA has been created
qsvcrtab.sql
Creates all the tables in the interfaces database and their indexes
qsvcrusr.sql
Creates the qv user and all its privileges
qsvcseqs.sql
Creates all custom sequences
qsvcsup1.sql
Script used by support to find table size and show environment

variables
qsvcsynm.sql
Creates custom synonym under apps schema
qsvcsyst.sql
Creates the public synonym per_all_people_f for per_people_f
qsvctbls.sql
Creates the custom tablespace
qsvctrig.sql
Creates the triggers for aps.fnd_concurrent_requests
qsvcupdt.sql
Updates all custom attributes and creates custom tablesused for

upgrade
qsvcview.sql
Creates views for page-level security
qsvcwhse.sql
Updates the qsvp_whse table for new Vista Plus warehousesa

concurrent program usage
Files Installed
143
144
qsvdesel.sql
Dynamically deletes a selected Vista Plus report warehousea

concurrent program usage
qsvindex.sql
Creates all the missing indexes
qsvinstl.sql
Installs the Vista Plus Interface
qsvipass.sql
Creates custom password called by a concurrent program
qsvitall.sql
Used during the selection of the process method on the Responsibility

form
qsvpatcb.sql
Updates patches during an upgradecurrently used for prime number

update
qsvrcptr.sql
Creates dynamic shell scripts to execute all recapture commands
qvcpgbpr.sql
Executes package procedure used for page-level security
Files Installed on the Middle Tier or Oracle Client Manager
Files Installed on the Middle Tier or Oracle Client

Manager
These Oracle form files are placed in $QV_TOP/forms/US during installation:
File
Description
qsextrac.fmb
Extraction screennot currently used
qsvdellk.fmb
Creates the define report link/unlink/delete form
qsverrvw.fmb
Creates the Error Log form
qsvfldgp.fmb
Creates the Reports form
qsvmtwhs.fmb
Creates multiple report warehouse support
qsvpafsg.fmb
Shows a list of detail FSG reports
qsvpahoc.fmb
Shows a list of FSG Ad hoc reports
qsvpclog.fmb
Shows the Process Log form
qsvpgfld.fmb
Shows page-level security
qsvpgusr.fmb
Creates the User Page Level Security form
qsvppgrp.fmb
Creates the Group Page Level Security form
qsvprlis.fmb
Shows all pending reports and previous reports
qsvrespb.fmb
Creates the Responsibility form
qsvrpque.fmb
Creates the Vista Plus report capture table
qsvstenv.fmb
Creates the Server form
qsvurshr.fmb
Creates the User Force form
qsvusemp.fmb
Creates the User Employee form
qsvusers.fmb
Creates the User Responsibility form
qsvusles.fmb
Creates the User Salesrep form
qszomsec.fmb
Set up ZOOM functionality; not currently used
Files Installed
145
Files Installed on the Middle Tier or Oracle Client Manager
146
Appendix B
Configuring the Interface to Work With Vista Plus

Output Manager
This appendix describes how to configure the interface to work properly with Vista Plus
Output Manager.
In This Appendix
General Information .............................................................................. 148
Install the qr Command ........................................................................ 149
Copy and Edit the qmOrapToVistaPlus file ...................................... 150
Create an Output Manager Queue ..................................................... 151
Configure the Interface System Profile .............................................. 152
Configuring the Interface to Work With Vista Plus Output Manager
147
General Information
General Information
If you are using Vista Plus Output Manager, you can set up the interface so that any report
you send for capture through the interface is sent to Output Manager, which then routes it
to the correct Vista Plus report warehouse and ensures that the capture completes. To do
this, you must perform some special configuration in both the interface and Output
Manager. The general steps are:
1.
If necessary, install the Output Manager qr command on the Oracle Applications

server where the interface is installed.
2.
Copy the qmOrapToVistaPlus.sh or qmOrapToVistaPlus.bat file to the proper location on

the Output Manager server.
3.
Modify the qmOrapToVistaPlus.sh or qmOrapToVistaPlus.bat file as necessary for your

installation.
4.
In Output Manager, create a new queue to handle reports from the interface.
5.
In the interface, modify the System Profile settings so the interface will send capture
requests to Output Manager.
The rest of this appendix gives detailed instructions for each of these steps.
148
Install the qr Command
Install the qr Command

If Output Manager is installed on the same host as the interface, the qr command is
already present and you do not need to perform this procedure. If Output Manager is
installed on a different host, you need to copy qr to the host where the interface is
installed.
1.
From the Vista Plus section of the Knowledge Center, download the Output Manger
installation file that matches your version of Output Manager and the operating
system of the host where the interface (not Output Manager) is installed.
2.
On the host where the interface is installed, log on as applmgr.
3.
Copy the Output Manager installation file to the $QV_TOP/tmp directory. If you are
using FTP, be sure to use a binary copy.
4.
Extract the qr command from the Output Manager installation file:

zcat installfile.tar.Z | tar xvf - bin/qr
Installfile is the name of the Output Manager installation file.

5.
Move the extracted qr command file to a directory thats accessible to applmgr:

mv bin/qr /path
Path is the path where the qr command should reside.

6.
Make sure permissions are set so qr is owned by applmgr and is readable and
executable by anyone.
7.
If you want, delete the Output Manager installation file and the subdirectory created
when you extracted the qr command:
rm installfile.tar.Z
rmdir bin
Whenever you upgrade Output Manager, you will need to repeat this process to install the
proper version of qr.
149
Copy and Edit the qmOrapToVistaPlus file
Copy and Edit the qmOrapToVistaPlus file

The qmOrapToVistaPlus.sh and qmOrapToVistaPlus.bat files are provided as part of the Vista
Plus Interface for Oracle Applications. You need to copy the correct file for your
installation to the Output Manager server host. The procedure for doing this is different
based on whether the Output Manager host is a UNIX or Windows computer.
If Output Manager is running on UNIX:
1.
Copy qmOrapToVistaPlus.sh from $QV_TOP/bin to the lib subdirectory of the Output

Manager home directory. If you use FTP, be sure to perform an ASCII copy.
2.
Make sure the file is owned by the root user and that all users can read and execute it.
If Output Manager is running on Windows:
Copy either qmOrapToVistaPlus.sh or qmOrapToVistaPlus.bat, whichever one is correct

for your installation, from $QV_TOP/bin to the lib subdirectory of the Output
Manager home directory. If you use FTP, be sure to perform an ASCII copy.
Once the file is in the proper location, open it using a text editor, such as vi on UNIX or
Notepad on Windows. Follow the instructions within the file to modify it as necessary for
your installation.
Note
150
The Vista Plus rcapture command must be installed on the Output Manager
host. If it is not, please refer to the Vista Plus Server Installation Guide for
instructions on installing it on remote hosts.
Create an Output Manager Queue
Create an Output Manager Queue

Next, you need to create an Output Manger queue to process the capture requests from
the interface. Using OUtput Managers WinCQ administrative client, add a queue with
these characteristics:
Field
Value
Queue Name
OrApptoVistaPlus (this is the suggested name; you can call it anything)
Queue Type
Print
Retention Queue
Retention (this is suggested; can be any Retention type queue)
Reject Queue
Retention (this is suggested; can be any Retention type queue)
Delay Time
0:0
Queue Process
On UNIX:
/OMHome/lib/qmOrapToVistaPlus.sh $JOB $ENTRYII
OMHome is the path to the Output Manager home directory.
On Windows, if you are using the .bat file:
OMHome\lib\qmOrapToVistaPlus.bat "$JOB" $ENTRYID
On Windows, if you are using the .sh file:
UnixShellHome\sh /OMHome/lib/qmOrapToVistaPlus.sh
"$JOB" $ENTRYID
UnixShellHome is the path to a UNIX shell emulation program.
Queue Description
Oracle Apps to Vista Plus
Output Options
Queue
Output Queue
Logs (this is suggested; can be any Retention type queue)
Be sure to upload your changes to the configuration before you quit WinCQ.
You must also define a host for the new queue.
For more information on using WinCQ and defining new queues, please see the WinCQ
help file.
151
Configure the Interface System Profile
Configure the Interface System Profile

Three settings on the interfaces System Profile form control how the interface interacts
with Output Manager. You must set the VPOMCMD1, VPOMCMD2, and VPOMYN
fields to the correct values for your installation. Follow this procedure:
1.
Log into Oracle Applications and start the interface.
2.
From the Navigator, select Profile, System.
3.
Click in the Value field for VPOMCMD1. Change the port number to the port being
used by the Output Manager host.
4.
Click in the Value field for VPOMCMD2. You need to make three changes to this
value:
Change the path to the qr command to match its location on the interfaces host.
Change the queue name following the -q parameter to match the Output
Manager queue you just created.
Change the host name in the -x parameter to match the Output Manager host
name.
Also, you can add parameters to the qr command as desired. For example, if you want
to suppress sending zero length files and keep any failed jobs in the OrApptoVistaPlus
queue in a Manual Restart Required state, add the -Fs and -E parameters
5.
Click in the Value field for VPOMYN. Set this field to Y.
6.
Save your changes and close the form.
You have now finished the Output Manager configuration. The interface will now route
capture requests to the queue youve created in Output Manager.
152
Appendix C
Requests Included in the Interface

This appendix gives brief descriptions of each Oracle Applications request provided with
the interface. For those requests you may use during normal interface operation, the
description includes a reference to the procedure where the request is described.
Request Name
Function
Vista Plus Indiv Capture

Generation
Captures all report output for which there is an entry in the

interface capture table. This includes reports which have not yet
been captured and any you have requested reprinting for. See
page 119
Vista Plus Indiv Del All
Deletes all data from all tables in the interface database. Contact
Vista Plus customer support before using this request.
Vista Plus Indiv Del Error Log
Deletes entries from the Error Log form. You can specify a date
range to delete only entries for those dates. See page 140.
Vista Plus Indiv Del FSG AD

HOC
Deletes entries from the List Reports FSG AD HOC form. You can
specify a date range to delete only entries for those dates. See
page 133.
Vista Plus Indiv Del FSG Detail Deletes entries from the List Reports FSG Detail form. You can
specify a date range to delete only entries for those dates. See
page 134.
Vista Plus Indiv Del Process
Log
Deletes entries from the Process Log form.
Vista Plus Indiv Del Reports All Deletes entries from the List Reports All form.See page 132.
Vista Plus Indiv Del VP Whse
Deletes from a Vista Plus warehouse all information that was

added by the interfaceall reports, folders, users, groups, and so
on. See page 34.
Vista Plus Indiv Full Sync/

Migrt
Performs the synchronization and migration tasks in a single

request; use this only with full synchronization. See page 67.
Vista Plus Indiv Initialization
Initializes the interfaces database and populates it with data

responsibilities, users, reports, and so onfrom Oracle
Applications. This request should only be run once. See page 61 or
page 74.
Vista Plus Indiv Migration
Copies new and changed data from the interfaces database into
Vista Plus. It does not migrate page-level security data. See page 66
or page 89.
153
Request Name
Function
Vista Plus Indiv Page Level

Group All
For page-level security by group, finds value sets, rule names, and
other pertinent data that has changed in Oracle Applications and
updates the interfaces database. It then takes this information and
any page-level security definitions youve entered in the interface
and updates page securities in Vista Plus. See page 109.

Group Ins
Allows you to enter parameters so you can define page-level

security by group for multiple groups and rule name/value set
combinations at once. See page 107.

Group Migrate
Updates Vista Plus page security with the current group page-level
security information from the interfaces database. It does not
check the Oracle Applications database for updated information.
See page 109.

Group Sync
Updates the interfaces database with changed value set and rule
name data from Oracle Applications. It does not transfer any
information to Vista Plus. See page 109.

User
For page-level security by user, updates page securities in Vista

Plus. See page 99.

User Sync
Synchronizes page-level by user security data from Oracle

Applications into the interfaces database.
Vista Plus Indiv Recover Date
Retrieves information on all reports run in the entered date range

and populates the lists on the List Reports All, List Reports FSG AD
HOC, and List Reports FSG Detail forms. See page 123.
Vista Plus Indiv Recover

Request ID
Retrieves information on a specific report request ID and adds it to

the list on the List Reports All, List Reports FSG AD HOC, or List
Reports FSG Detail forms. See page 121
Vista Plus Indiv Report List
Generates a report listing the Oracle Applications reports

contained in the interfaces database. See page 136.
Vista Plus Indiv Resp List
Generates a report listing the Oracle Applications responsibilities

Vista Plus Indiv

Synchronization
Copies new and changed data from Oracle Applications into the
interfaces database. It does not include page-level security
information. See page 91.
Vista Plus Indiv User Emp List
Generates a report listing the Oracle Applications employees

Vista Plus Indiv User Force List Generates a report listing the Oracle Applications users contained
in the interfaces database who have been forced into other
groups in Vista Plus. See page 80 for information about forcing
users into groups.
Vista Plus Indiv User List
Generates a report listing the Oracle Applications users contained

in the interfaces database. See page 136.
Vista Plus Indiv User Sales List Generates a report listing the Oracle Applications sales reps
154
Request Name
Function
Vista Plus Int ...
All requests which begin Vista Plus Int are used internally by the
interface. You should never submit these requests manually.
155
156
Index
A
About this manual
3
Ad hoc reports
See FSG ad hoc reports
Adding
77, 82
employees to a group
sales reps to a group
77, 84
users to other groups
77, 80
APA system profile setting
40
APAO system profile setting
41
APPL_TOP directories
23
applmgr user
28
applsys user
23
Assumptions
3
Audience
3
B
Backing up log and data files
41
BACKUP system profile setting
41
Basic page level security See Page level security
BYPASS system profile setting
41
C
Capture method
47
selecting
54
Capture on or off for full synchronization
48
Capture options
47
selecting
117
with managed synchronization
65, 87
Capture report request
119
Capture table
11, 119
clearing
132
removing reports
125
viewing
130
Capturing reports
111
FSG ad hoc
48, 54
FSG detail
49, 54
immediately
118
into private folders
14
Index
mechanism
11
monitoring
130
procedure overview
112
running the reports
118
scheduling
119
selecting reports to capture
116
with full synchronization
69
90
Case for user names
41
CASE system profile setting
41
chmod command for Interface directories
26
Choosing
See Selecting
Clearing
FSG ad hoc capture list
133
FSG detail capture list
134
report capture table
132
Compatibility
22
Concepts
8
Conventions used in the manual
4
Converting data
See Transferring
Copyin
See Transferring
Custom Oracle Applications database
11
used during transfer
Custom passwords
78
D
Data transfer
11
mechanism
61
74
Data types
12
Oracle Applications and Vista Plus
Databases
See Oracle Applications databases
Defining
114
printers for immediate report capture
Vista Plus server
45, 54
DEINSTALL system profile setting
41
Deleting
133
134
Oracle Applications data from Vista Plus 34,
41
page-level security for group
108
157
Deleting, continued
132
report warehouse
57
reports from Vista Plus
126
Vista Plus Interface for Oracle Applications 34,
36
Detail FSG reports
Directory structure
on middle tier
on server
setting permissions
See FSG detail reports
30
25
26
E
Employees
into Vista Plus users
printing list
Emptying
Environment variables
APPL_TOP
QV_TOP
Error Log form
Error log, viewing
Extracting files during installation
12, 77, 82
135
133
134
132
23, 25
26, 31
139
139
25
F
Feature list
2
Files installed
141
First-time data transfer
61
74
Folders
48
for FSG ad hoc reports
for FSG detail capture
49
from responsibilities
12, 76
from user names
14
private
See Private folders
14
security
unlinking and relinking reports
126
Forcing users into different groups
77, 80
Forms
26
compiling during installation
Error Log
139
Link/Unlink/Delete Report
126
158
List Reports All

125, 131
List Reports by Responsibility
131
NCA installation on UNIX
30
Page Level Security by Groups
103
Page Level Security by Users
98
Parameters
122, 123
Process Log
138
Reports
65, 86, 117
Responsibility
76
Schedule 66, 68, 89, 92, 100, 108, 110, 120
Server
54
immediate printers
115
Submit Request
35, 62, 75, 92, 99
System Profile
43
User Employee
83
User Force
81
User Responsibility
63, 79
User Salesrep
84
Warehouse
88
FSG ad hoc reports
48
capturing
48, 54
clearing the capture list
133
monitoring capture
133
removing from capture table
125
FSG detail reports
49
capturing
49, 54
clearing the capture list
134
monitoring capture
133
125
Full synchronization
9, 46, 54
advantages and disadvantages
9
copying the data to Vista Plus
66
initial data transfer
61
procedure overview
16, 60
report capture
69
report capture options
48
scheduling data updates
67
selecting reports for private capture
64
116
selecting users for private folders
63
using
59
Full synchronization/migration request
11, 67
G
General description
Generations
from Oracle Applications report runs
when created
8
13
113
Groups
adding employees to
adding sales reps to
forcing users into
from responsibilities
from user names
page level security
security
77,
77,
77,
12,
82
84
80
76
14
15, 101
14
H
Home folders for groups
Host
76
See Vista Plus server
L
Language, selecting
Launch Vista Plus, enabling button
Launching the interface
Link/Unlink/Delete Report form
LINKRESP system profile setting
List Reports All form
List Reports by Responsibility form
Listing
FSG ad hoc capture
FSG detail capture
report capture
55
40, 54
33
126
42
125, 131
131
133
133
130
Immediate report capture

defining printers
114
running the reports
118
Indexes needed
for page-level security
96
for page-level security by group
101
for page-level security by user
97
Initial data transfer
61
74
Initialization request
11
function
61
74
install.log file
29
Installation
compiling forms and scripts
26, 28
directory structure
25, 30
extracting files
25
file list
141
install.log file
29
middle tier
30
Oracle Applications access requirements
23
passwords needed
23
procedure overview
24
requirements
23
server
25
server install script
26, 28
setup menu
28
user QVISTA
26
Vista Plus access requirements
23
Vista Plus requirements
23
Managed synchronization
9, 11, 46, 54
advantages and disadvantages
9
and data transfer mechanism
11
copying the data to Vista Plus
89
initial data transfer
74
procedure overview
17, 72
report capture
90
scheduling data updates
91
selecting reports
85
selecting reports for private capture
85
116
selecting responsibilities
76
selecting users
78
selecting users for private folders
78
using
71, 95
with multiple warehouses
19, 53
Manual
3
assumptions
audience
3
chapter list
3
conventions used
4
Middle tier installation
30
Migration request
function
11
speeding up
42
66
89, 94
Monitoring
133
FSG ad hoc capture
FSG detail capture
133
report capture
130
Moving data
See Transferring
19, 52
Multiple Oracle Applications databases
Index
159
Multiple Vista Plus report warehouses

synchronization method
19, 53
19, 53
N
Navigator
33
NCA middle tier
See Middle tier
47
Number of copies, effect on report capture
O
On-going data updates
67
91
Operating system versions supported
22
Options for interface
40, 47
Oracle Applications database
entering prefix for
54
multiple
19, 52
types of data copied
12
Oracle Applications versions supported
22
Oracle user ID needed for installation
23
Other Vista Plus products
5
Output Manager
147, 153
configuration overview
148
creating a queue
151
defining commands for
42
system profile settings
152
turning on for interface
42
Overview
8
of procedures
16
P
Page level security
by group
deleting
by user
linking reports to folders
security format
security name format
speeding up request
Page Level Security by Groups form
Page Level Security by Users form
Page-level security
PARAM system profile setting
Parameters form
160
15, 101
108
15, 97
42
40
41
42
103
98
15, 96
42
122, 123
PASS system profile setting

42
Password for qv user
42
changing
setting
29
Passwords
50
custom
78
for vadmin
55
for Vista Plus users
50
forcing change
50
in Vista Plus
13
needed for installation
23
printing list
135
random
50
selecting format
50
PeopleSoft interface
5
Permissions on interface directories
26
middle tier
31
PL/SQL, compiling during installation
26
Prefix
entering for database
54
using with multiple databases
19, 52
Print queue
See Capture table
Printer names effect on report capture
47
Printers, defining for immediate report capture
114
Printing
employee list
report list
responsibility list
sales rep list
user list
Private folders
and full synchronization
and managed synchronization
capturing reports to
selecting reports for
selecting users for
users in multiple responsibilities
Procedure overview
Process Log form
Product overview
Profile settings
Purging
135
135
135
135
135
14
63
78
113
64, 85
63, 78
64
16
138
8
39
133
134
132
Q
qmOrapToVistaPlus.bat file
150
qmOrapToVistaPlus.sh file
150
qr command
copying to interface host
149
path in system profile settings
152
Queue for Vista Plus capture
See Capture table
Queue in Output Manager
151
qv directory
25, 30
qv user
changing password
42
setting password
29
QV_TOP directory
26, 55
QV_TOP environment variable
26, 31, 55
QVISTA user name, adding
26
R
Random passwords
50
printing
135
rcapture command
65, 87, 117
on Output Manager host
150
rcapture parameters in report descriptions
42
Relationship of Oracle Applications data to Vista
Plus data
12
Relinking reports to folders
126
Removing reports from the capture table
125
Removing Vista Plus Interface for Oracle Applica34, 36
tions
Report capture
111
and synchronization method
10
by printer name
47
clearing the capture table
132
defining immediate capture printers
114
effect of number of copies
47
FSG ad hoc
48
FSG detail
49
immediate
114, 118
into private folders
14
log file
134
mechanism
11
method
47
monitoring
130
options
47
procedure overview
112
request
11
running the reports
118
scheduling
119
Index
selecting capture options

117
65, 87
selecting method
54
116
table
See Capture table
69
90
Report capture request
11
Report description and rcapture parameters
42
Report generations
See Generations
Report run and Vista Plus generation
13
Report warehouse
11
checking status
41
defining
54
defining destination
87
deleting
57
deleting all data from
34
multiple
19, 53
Reports
capturing to private folders
113
deleting from Vista Plus
126
FSG ad hoc
48
FSG detail
49
in multiple responsibilities
87, 93
13
printing list
135
relinking to folders
126
125
reprinting
124
retrieving
121
by date range
122
single report
121
selecting for on-going updates
93
selecting for private capture
64, 85
selecting with managed synchronization
85
unlinking from folders
126
Reports form
65, 86, 117
Reprinting a report
124
Requests
Also see individual request names
capture report
11, 119
full synchronization/migration
11, 67
function
11
initialization
11, 61, 74
list of all by name
153
migration
11, 66, 89, 94
synchronization
11, 91
used with full synchronization
16, 60
used with managed synchronization
17, 72
161
Requests, continued
viewing errors during
139
Requirements for installation
See Installation
Responsibilities
into groups and folders
12
maintaining security
14
page level security
15, 101
printing list
135
selecting destination report warehouse
87
93
selecting for synchronization
76
76
Responsibility form
76
Retrieving missing reports
121
S
Sales reps
into Vista Plus users
12, 77, 84
printing list
135
SAP R/3 interface
5
Schedule form66, 68, 89, 92, 100, 108, 110, 120
Scheduling report capture
119
Scheduling updates
67
91
Security
14
assigning Vista Plus passwords
50
page-level
15, 96
by group
101
by user
97
password for vadmin
55
through groups and folders
14
Security rules and page-level security
101
Selecting
93
data for on-going updates
destination report warehouse
87
language
55
report capture method
54
synchronization method
54
Selecting reports
for capture
116
for private capture
64, 85
from multiple responsibilities
87, 93
85
Selecting responsibilities
76
Selecting users
80
from multiple responsibilities
162

78
Server form
54
immediate printers
115
Server
See Vista Plus server
Setup menu
28
SID
and multiple databases
52
and multiple report warehouses
53
entering
55
in user names
55
SQL Forms
23
SQL Plus
23
Starting the interface
33
Submit Request form
35, 62, 75, 92, 99
Synchronization
9, 13, 46
changing method
full
9, 60
managed
9, 72
method and multiple warehouses
19, 53
method and report capture
10
methods
9, 46, 54
overriding selective
51
selecting method
46, 54
selecting responsibilities
76
selecting responsibilities for
77
Synchronization request
91
function
11
System manager password
23
System Profile form
43
System profile settings
39, 40
changing
43
for Output Manager
152
required
40
viewing
43
T
Tablespace size
29
Text files used during transfer
11
Trace log, turning on
54
Transferring data
from multiple databases
19, 52
mechanism
11
to multiple report warehouses
19, 53
Turning on the trace log
54
Types of Oracle Applications and Vista Plus data
12
Typographical conventions
U
Uninstalling Vista Plus Interface for Oracle Appli34, 36
cations
UNIX system profile setting
40
Unlinking reports from folders
126
Updating data
67
91
URL for Vista Plus client
40, 54
User Employee form
83
User Force form
81
User names
in Vista Plus
13
QVISTA
26
selecting upper or lower case
41
with multiple Oracle Applications databases
19, 52, 55
User Responsibility form

63, 79
User Salesrep form
84
Users
14
becoming folders and groups
forcing into different groups
77, 80
from employees
12, 77, 82
from sales reps
12, 77, 84
in multiple responsibilities
80
information transferred
12
12
page level security
15, 97
printing list
135
printing password list
135
93
selecting for private folders
63, 78
78
V
vadmin password security
Value sets and page-level security
Versions supported
operating system
Oracle Applications
Vista Plus
Viewing
error log
Vista Plus capture table
Vista Plus
other products
Index
55
101
22
22
22
139
130
versions supported
22
Vista Plus capture queue
See Capture table
54
Vista Plus client, enabling button
Vista Plus Indiv Capture Generation
119, 153
Vista Plus Indiv Del All
153
Vista Plus Indiv Del Error Log
140, 153
Vista Plus Indiv Del FSG AD HOC
133, 153
Vista Plus Indiv Del FSG Detail
134, 153
Vista Plus Indiv Del Process Log
153
Vista Plus Indiv Del Reports All
132, 153
Vista Plus Indiv Del VP Whse
35, 153
Vista Plus Indiv Full Sync/Migrt
67, 68, 153
Vista Plus Indiv Initialization
62, 75, 153
Vista Plus Indiv Migration
66, 89, 153
Vista Plus Indiv Page Level Group All 102, 109,
154
Vista Plus Indiv Page Level Group Ins 107, 154

Vista Plus Indiv Page Level Group Migrate 109,
154
Vista Plus Indiv Page Level Group Sync 109, 154

Vista Plus Indiv Page Level User
97, 99, 154
Vista Plus Indiv Page Level User Sync
154
Vista Plus Indiv Recover Date
123, 154
Vista Plus Indiv Recover Request ID
121, 154
Vista Plus Indiv Report List
136, 154
Vista Plus Indiv Resp List
136, 154
Vista Plus Indiv Synchronization
92, 154
Vista Plus Indiv User Emp List
136, 154
Vista Plus Indiv User Force List
136, 154
Vista Plus Indiv User List
136, 154
Vista Plus Indiv User Sales List
136, 154
Vista Plus Int ...
155
Vista Plus Output Manager See Output Manager
Vista Plus print queue
See Capture table
Vista Plus server
45, 54
defining
deleting
57
description
54
directory
54
port number
54
prefix
54
server name
54
TCP/IP address
54
Vista Plus URL
54
VPOMCMD1 system profile setting
42, 152
VPOMCMD2 system profile setting
42, 152
VPOMYN system profile setting
42, 152
163
W
Warehouse form
Warehouse ID
and multiple databases
and multiple report warehouses
entering
164
88
52
53
55
in user names
55
Warehouse
See Report warehouse
5
Web View
Web View URL
40
Windows Client
5
WORKERS system profile setting
42

Vista Plus Interface For Oracle E-Business Suite User Guide PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Vista Plus Interface For Oracle E-Business Suite User Guide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Vista Plus Interface for Oracle EBusiness Suite

Starting the Vista Plus Interface for Oracle Applications ................................................. 33

Oracle has changed the name of Oracle Applications to Oracle E-Business

Vista Plus Interface for Oracle E-Business Suite Users Guide

About This Book

About This Book

Chapters in This Guide

Introduces Vista Plus Interface for Oracle Applications

Installing Vista Plus Interface for Oracle Applications

Checking and, if needed, modifying the interfaces system profile

Defining the Vista Plus report warehouse or warehouses to transfer

Keeping information synchronized between Oracle Applications and

Keeping information synchronized between Oracle Applications and

About This Book

Conventions in This Guide

The names of commands are shown in bold.

UNIX and Oracle user names are given in italics.

Optional parts of a command syntax or program entry are in brackets.

When we refer to part of a command syntaxfor example, to explain

At times, particularly important text is in this bold italic typeface to

Vista Plus Interface for Oracle E-Business Suite Users Guide

Vista Plus Products

Vista Plus Products

Home to the Vista Plus report warehouse. Users throughout

Vista Plus Web View

Installs on the Web server and can be used by anyone with a

Vista Plus Windows

Runs in supported versions of Windows. Like Web View, it