Oracle E-Business Suite Interface 6 0 Release Notes

8/10/2019 Oracle E-Business Suite Interface 6 0 Release Notes

http://slidepdf.com/reader/full/oracle-e-business-suite-interface-6-0-release-notes 1/20

Copyright Open Text Corporation. All rights reserved.

This software product and documentation is licensed subject to the terms of the license agreement shipped with the product.

Vista Plus Interface for Oracle E-Business Suite v6.0 Release Notes (October 3, 2012) VP4EBS060000-RN-EN-02

Page 1

Vista Plus ® Interface for Oracle E-Business Suite

Version 6.0

Release NotesOctober 3, 2012

IMPORTANT: This document describes new features and updates in version 6.0 of theVista Plus Interface for Oracle E-Business Suite. It includes descriptions of the changessince version 5.1 as well as upgrade instructions. OpenText recommends that you readthis document in conjunction with the Vista Plus Interface for Oracle E-Business Suitedocumentation included with the software. If any conflicts exist, the information in thisdocument supersedes that documentation.

Check the OpenText Knowledge Center at https://knowledge.opentext.com for any patches or

documentation updates that may have been posted after the initial release of this versionof Vista Plus Interface for Oracle E-Business Suite.

Note For space considerations, throughout the rest of this document we will referto Oracle E-Business Suite as Oracle EBS.

Table of Contents

General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

New Features and Changes in Version 6.0 . . . . . . . . . . . . . . . . . . . 3

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Upgrade Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

After the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

https://knowledge.opentext.com/

https://knowledge.opentext.com/



General Information




Page 2

General Information

The Vista Plus Interface for Oracle E-Business Suite version 6.0 is a major update. Thesoftware has been completely rewritten. There are major improvements in all of theseareas:

Performance

• Efficiency and space requirements

• Usability

For more information on the enhancements and changes in version 6.0, see “New Featuresand Changes in Version 6.0” on page 3.

The core functionality of the product remains the same. However, in order to bring theseimprovements to market as quickly as possible, version 6.0 does not include someperipheral features from version 5.1 that were seldom used. We plan to add most of these

features back into the product in future versions. See “Removed Features” on page 7 for alist of the features that have not yet been transitioned to the new generation of theinterface.

The Vista Plus Interface for Oracle E-Business Suite version 6.0 is available as a downloadfrom the OpenText Knowledge Center. The release directory contains all files needed foreither a new installation or an update from a previous version. If you are updating anexisting installation, please refer to “Upgrade Instructions” on page 10 of this document.If you are installing the software for the first time, please follow the procedures in Chapter3 of the Vista Plus Interface for Oracle E-Business Suite User’s Guide.

Compatibility

Vista Plus Interface for Oracle E-Business Suite 6.0 works with Oracle EBS versions 12.0.x

and 12.1.x.

You can migrate information to any Vista Plus server host running Vista Plus 5.5.0 withthe patch for issue VP-1875, or 5.5.1 or later.

The Oracle EBS applications server must run a version of UNIX or Linux which supportsthe remote capture tools for the Vista Plus® version(s) used by the server host(s) you will be migrating data to. See the Release Notes for your version of Vista Plus for supportedUNIX and Linux versions.

Installing the interface on a Windows Oracle EBS applications server is not supported.



New Features and Changes in Version 6.0




Page 3


The lists below briefly describe the new features and operational changes found in version6.0. As mentioned above, the software has been completely rewritten for this release. Thechanges described here include visible changes to the user interface and product behavior,improved performance and reliability, and internal modifications which should beinvisible to the user.

Simpler, More Efficient Software and Database

We have greatly simplified both the database structure the interface uses and the softwareitself. This results in better performance, decreased disk space usage, and a product that iseasier to maintain and update. Specifically:

• We have substantially reduced the number of programs comprising the interface andthe total lines of code. This makes the programs more efficient and more reliable, and

makes it easier to diagnose and fix any problems that may arise.

• We have normalized the database, reducing the number of tables from 45 to 17 andthe average number of columns per table from 24 to 11. Redundant data has beenremoved, dramatically reducing the size of the database and making data storage andretrieval much more efficient.

These changes have resulted in dramatic performance improvements. The gains arelargest in operations which take place entirely within the interface, such as initializationand synchronization. Improvements during migration and report capture, which copyinformation into Vista Plus, are less striking because the Vista Plus components areunchanged, but are still significant.

Testing with our in-house sample database, which contains over 2000 responsibilities,

1000 users, and 100,000 reports, showed these improvements:• Initialization of the entire database was over four times faster.

• Synchronization of the entire database was over 10 times faster.

• Migrating the entire database showed about a 40% improvement, reducing the timeneeded on our test system by more than five hours. With version 6.0, almost all of thistime was occupied by executing the vadmin commands on the Vista Plus server.Migrating fewer objects showed larger gains, as the more efficient interface played alarger part in the overall operation.

• Capturing 100 reports completed more than four times as fast. As with migration, ifthere are fewer reports in an individual capture request run, the performance gain iscorrespondingly greater—more than 30 times as fast when capturing a single report.

We include these test results solely to give you an idea of the types of gains we have seenin our environment, and that you may see in yours. Many factors will affect your results,including the amount of data in Oracle EBS, the hardware configuration of the computersinvolved—the Oracle EBS applications server, the Vista Plus server, and the Oracledatabase server—your network configuration and traffic, other programs being used on









Page 5

More Flexible Private Reports

The private report feature has been improved and made more flexible. You can nowdefine any report as private for one or more individual users, while keeping it public forothers. When you make a report private for a user, a new report is created in Vista Plusand linked directly to the personal folder for that user. When the user runs the report inOracle EBS, it is captured to the private report linked to the personal folder, so no one elsehas access in Vista Plus. When a user for whom the report is not private runs it in OracleEBS, it is captured to the public Vista Plus report, which is linked to the folder for thereport’s responsibility.

Removed System Profile Form

There is no longer a separate System Profile Settings form. These settings have been eithermoved to the Server form, so you can set them as desired for each Vista Plus server,

moved to the Report form so you can set them for each migrated report, or removedentirely, as some of them are no longer needed. Moving these options to the server orreport level greatly increases the flexibility of the interface: you are no longer forced tohave settings such as default access levels, user password formats, and so on, the same forall Vista Plus servers.

More Meaningful Object Names and Descriptions

We have changed the format of object names and descriptions in Vista Plus. We haveadded the application short name to the name of each group, folder, and report toguarantee that all names are unique. (Previously, responsibilities with the same name indifferent applications in Oracle EBS created identical Vista Plus objects). Descriptions arenow based on the Oracle EBS object description, if it has one. Specifically:

• Group names and the names of folders created from responsibilities now include theapplication short name. The group or folder description is the responsibilitydescription if it has one, or the responsibility name if the responsibility has nodescription.

• User names have not changed, except that, if the SID for the Vista Plus warehouse isincluded, it is at the beginning of the name, as it is for the other object types, instead ofat the end. The user full name is now the Oracle EBS user name, while the descriptionis the user description if it has one, or the user name if the user has no description.

• Vista Plus report names now include the full Oracle EBS report name followed by theapplication short name. The Vista Plus report description is the Oracle EBS reportdescription, or the report name if the Oracle EBS report has no description.

• FSG report names now include the FSG report name from Oracle EBS instead of thereport ID. The description is the report description if it has one, the title if it has nodescription, or the report name if it does not have a description or title.







Page 6

The new name formats for each type of object are:

In addition, private reports include the user’s name at the end.

If you choose to include the SID for the Vista Plus server in object names, it is added at thefront of each object, including user names. The option to include the SID now affects allobject types, not just users. It is possible to assign an SID to a Vista Plus server, but notinclude it in the names of objects created on that server.

See “After the Upgrade” on page 19 for a discussion of how these object name changesmay affect behavior after an upgrade.

Improved FSG Report Handling

FSG reports, both ad hoc and detail, are no longer treated differently than other reports.You select them for replication and capture just like any other Oracle EBS report. TheirVista Plus report names do use a different format than other reports, as described in theprevious section and in Chapter 2 of the Vista Plus Interface for Oracle E-Business SuiteUser’s Guide.

Synchronization and Migration Improvements

We’ve made multiple changes and improvements to the process of synchronizing andmigrating your data:

• The Synchronization request always copies information for all Oracle EBSresponsibilities into the interface’s schema. Previously, unless you chose to override it,Synchronization included only those responsibilities you selected. Synchronization’sgreatly improved performance—see “Simpler, More Efficient Software and Database”on page 3—makes it unnecessary to limit the responsibilities. This means you canalways include any responsibility, user, or report in the next migration.

• You no longer have to select “managed” or “full” migration. At any time, you canchoose to perform either the one-step Synchronization and Migration process foreasiest use and fastest completion, or separate Synchronization and Migrationrequests so you can choose the specific responsibilities, users, and reports to migrate.

• You no longer have to select which responsibilities, users, and reports to migrate, thengo to a separate page to select which ones to send to each Vista Plus server. After theSynchronization request and before Migration, you simply select which objects tomigrate to each Vista Plus server.

Group RESP_NAME-APPL_SHORT_NAME

Folder RESP_NAME-APPL_SHORT_NAME

User USR_NAME

Report RPT_NAME-APPL_SHORT_NAME-RESP_ID

FSG Report FSG-RPT_NAME-RESP_ID







Page 7

• For each Vista Plus server, you choose whether to migrate all responsibilities, users,and/or reports by default. When you perform Synchronization and Migration as one

process, these selections determine what’s included for each server. When youperform them separately, you can override the defaults and select exactly whichobjects to copy to Vista Plus.

More Efficient Report Capture

The internal process for capturing reports into Vista Plus after they are run in Oracle EBSis completely different. The interface no longer adds a trigger to the Oracle EBS concurrentrequest table. That method could cause problems if the concurrent request table wascustomized, and violated the design precept that the interface should not modify anystandard Oracle EBS tables.

Instead, the interface’s report capture process now uses a custom view to compare theconcurrent request table, the interface’s table containing reports to be captured, and theinterface capture queue. Any requests for reports which are selected for capture are addedto the interface capture queue, then immediately captured to Vista Plus with an rcapture command (unless the request has already been captured).

Any concurrent request which is sent to an immediate capture printer, and is for a reportselected for capture, immediately creates an entry in the interface’s report capture queue,which in turn creates and executes the rcapture command.

Note In both types of capture, if the interface is configured to use Vista Plus OutputManager, it configures and executes a qr command to send the report outputto Output Manager instead of using rcapture.

Removed Features

Version 6.0 does not contain some peripheral features which existed in the previousversion. None of these features are part of the core functionality of the product—copyingresponsibilities, users, and reports from Oracle EBS into Vista Plus. Each one has beenremoved from this release for one of two reasons: either the function it filled was morelogically provided elsewhere, or, while it was a useful feature, it was not widely used andthe time required to implement and test it would have delayed the release of 6.0. We feelthe performance and reliability improvements in this version are very important, and wedid not want to make customers wait for them while we finished these other features. Weplan to re-implement some of these features in future versions of the interface.

The features which are not included in version 6.0 are:

• You cannot “force” a user into a Vista Plus group that does not correspond to one oftheir Oracle EBS responsibilities. The purpose of the interface is to replicate the Oracle

EBS responsibility, user, and report structure in Vista Plus. We decided that includingthis feature was not consistent with that purpose, as it allowed users access to reportsthat they could not access in Oracle EBS. If desired, you can use Vista Plus features(the Server Admin client or vadmin) to add users to other Vista Plus groups after theyhave been replicated to Vista Plus. See “Assign Vista Plus Folders” on page 17.







Page 8

• The interface does not replicate page-level security from Oracle EBS to Vista Plus. Thisfeature did not function correctly in all situations and was not widely used. You can

create and assign page securities as desired in Vista Plus after replicating users andreports. We are planning on re-introducing an improved, more efficient, version ofthis feature in a future release of the interface.

• You cannot replicate Oracle EBS sales representatives or employees to Vista Plus asusers. This feature was not widely used. We plan to re-implement it in a futureversion.

Note If you replicated employees or sales reps to Vista Plus with an earlier versionof the interface, those users are converted to the new naming format duringthe upgrade procedure, and personal groups and folders are created for them.You will need to relink them to the folders for the desired responsibilities afterthe upgrade. See “Assign Vista Plus Folders” on page 17.

• Because of the changed implementation for report capture, you can no longer removea report from the interface’s report capture queue before it is captured into Vista Plus.In the new implementation, reports are not added to the capture queue until thereport capture request runs, and are then captured immediately. If, after running areport in Oracle EBS, you decide you do not want to capture it into Vista Plus, you canclear the Cap box for the report in the interface’s Select Report page before the reportcapture request runs.

• The interface does not contain a way to delete the information created on a Vista Plusserver by the interface—the delete warehouse request has been removed. If you wantto delete all the information from a Vista Plus server, you can do so using a Vista Plusadministration client. We are planning on re-introducing this ability in a futurerelease.

• You cannot “recreate” all data on a Vista Plus server. We are planning on re-

introducing this ability in a future release.



Known Issues




Page 9

Updates to the Documentation

The Vista Plus Interface for Oracle E-Business Suite User’s Guide has been extensively revisedto match the improved user interface. This new version of the User’s Guide is provided asan Adobe® Acrobat® PDF file in the Doc folder of the installation directory. It is notavailable in printed form.

Note Previous versions of the documentation used either “synchronization” or“migration” to refer to the entire process of copying information from OracleEBS into the interface’s schema, and from there to Vista Plus. Thedocumentation for version 6.0 uses “replication” to refer to this process. Thishas two advantages:

• Replication is more accurate, as a copy of the selected data is added toVista Plus, while the original data in Oracle EBS is unchanged.

• It eliminates the possible confusion caused by using either

“synchronization” or “migration” to refer to both a part of the process andthe entire process. Synchronization now always refers only to the actionsperformed by the Synchronization request, while migration refers only tothe actions performed by the Migration request.

Known IssuesIn addition to the features which have been removed (see “Removed Features” on page 7),version 6.0 of the interface contains this known limitation:

• Text Reports Only: You can capture reports through the interface only if they are runas text reports in Oracle EBS. The interface cannot capture reports generated as PDF

files or in other formats.



Upgrade Instructions




Page 10


Version 6.0 of the Vista Plus Interface for Oracle EBS has been completely rewritten. Ituses a newly-designed database structure. In fact, it does not re-use anything used byprevious versions of the interface: its folder structure, programs, and user schemas are allnew, with different names than those used by previous versions.

This means that “upgrading” to version 6.0 of the interface does not modify any existinginterface objects or data, or replace them with revised versions of the same objects.Instead, upgrading consists of these general procedures:

1. Installing version 6.0.

2. Using the provided programs and scripts to take data from the existing interfaceschema and Oracle EBS, populate the new tables in the new interface schema, andcreate Vista Plus users, groups, folders, and reports which use the new namingconventions.

3. Removing the old interface’s data and programs.

There is a more detailed overview below, followed by complete instructions for each step.

Note If you are installing the interface for the first time, do not follow theseprocedures. Instructions for a first-time installation are in Chapter 3 of theVista Plus Interface for Oracle E-Business Suite User’s Guide.

Before Upgrading

Warning Perform the upgrade in a test environment before updating your productioninstance of the interface. Parts of the procedure are complex; any error duringthem could keep the interface from working properly after the upgrade.

Before installing version 6.0 of the interface and starting the upgrade procedures below,you must do the following:

• If you are not already running version 5.1 of the interface, upgrade to version 5.1 byperforming the procedures in the Vista Plus Interface for Oracle Applications 5.1 ReleaseNotes. You cannot upgrade from any earlier version directly to 6.0; the data conversionwill not work.

• Perform a migration from the interface to Vista Plus. There should not be any data inthe interface’s schema, waiting to be migrated, when you copy the data to the newinterface schema.

• If any of the programs for version 5.1 of the interface (for example, report capture orsynchronization) are scheduled to run automatically, cancel the requests so theprograms will not run again.

• Back up all of the data in the old interface’s tables: everything in the QV schema. Onceyou have copied this data to the new interface schema and confirmed that the newinterface is working, you will delete the QV schema. It is a good idea to have a backupof the data in case you need to return to the old interface.







Page 11

• Back up your Vista Plus database. While upgrading to the new interface does notdelete any of the existing Vista Plus data, the names of many of the objects (reports,

folder, users and groups) that were created by the interface will be changed. It isalways recommended to perform a complete backup before any procedure that makeslarge database changes.

Note You do not need to back up the programs from version 5.1 of the interface.The programs for version 6.0 are installed in a different folder structure anddo not overwrite the existing programs.

Procedure Overview

As described above, the upgrade consists of installing version 6.0 of the interface,converting the data, then removing the old version (5.1) of the interface. These are theprocedures involved:

1. Installing the Vista Plus Interface for Oracle EBS, version 6.0. If your Vista Plus serveruses Vista Plus 5.5.0, you also need to install an updated version of vadmin.

2. Compile the upgrade programs which were installed with the 6.0 software.

3. Run the first upgrade program. This takes information from the old interface’sschema and the Oracle EBS schema and places it, in the new, more efficient format, inthe new interface schema.

4. Run the second upgrade program. This reads the data from the new interface schemaand creates a series of vadmin batch files. These files contain the commands toconvert the objects created by the interface in Vista Plus to the new naming format.

5. Run a shell script which executes a series of vadmin commands to update the VistaPlus database. If you use the interface with multiple Vista Plus servers, there is a

separate shell script for each server.After you have performed this step, the data used by version 5.1 of the interface nolonger exists in the Vista Plus database—all the objects have been renamed to followthe new conventions. After this step, if you want to return to using version 5.1 of theinterface, you must restore your Vista Plus data from a backup.

6. Set the internal server ID for each Vista Plus server in the interface database.

7. If desired, manually link the personal folders for Vista Plus users created during theconversion to additional Vista Plus folders create from responsibilities. You may needto do this if you used the “forcing users into groups” features or migrated employeesor sales reps. with the previous version of the interface.

8. Unregister the old version of the interface from Oracle EBS and drop all of its objects

from the database.9. Drop the upgrade programs from the database. This step is optional.

10. Remove the $QV_TOP environment variable and folder. This step is optional.







Page 12

Install Vista Plus Interface for Oracle EBS Version 6.0

Follow the instructions in Chapter 3 of the Vista Plus Interface for Oracle E-Business SuiteUser’s Guide to install the version 6.0 software. There is no separate procedure forupgrading the software. Because the software is installed into a different folder structurethan earlier versions, installing it has no effect on the existing interface.

If the version of the remote capture tools installed on your Oracle EBS server is from VistaPlus 5.5.0, you must install an updated version of the vadmin command. This is neededonly for Vista Plus 5.5.0. Versions 5.5.1 and later already have the necessary version ofvadmin. To update vadmin:

1. Download the updated vadmin file for your operating system. For your convenience,you can find it in the same Knowledge Center folder as the rest of the interfacesoftware.

2. Copy the file to the folder where the remote capture tools are installed, replacing the

existing copy of vadmin.

Compile the Upgrade Programs

Installing version 6.0 of the interface following the procedures in the User’s Guide installsthe programs needed to convert data from version 5.1 to the proper format for version 6.0.However, before you can run these programs, you must compile them. To do so:

1. Log on to the Oracle EBS server as applmgr.

2. Change directory to $VPI_TOP/upgrade/upg5160.

3. Enter these commands:

sqlplus vpi/vpi_pwd @vpdupg1.sql

sqlplus vpi/vpi_pwd @vpdupg2.sqlsqlplus apps/apps_pwd @vpdupg3.sql

Where vpi_pwd is the password for the vpi user and apps_pwd is the password for theapps user.

Run the First Upgrade Program

The first upgrade program populates the tables in the database schema for version 6.0. Todo so, it takes information from both the schema for version 5.1 of the interface anddirectly from the Oracle EBS database:

• It places the Vista Plus server definitions from the 5.1 database’s into the new serverdefinition table.

• It takes information for all Oracle EBS objects—responsibilities, users, and reports—from the Oracle EBS database. This is the same function that the initialization requestperforms after a new installation.

• It takes information about what has been migrated, which reports have been markedas private, and so on, from the 5.1 interface’s schema and stores it in the new schema.







Page 13

The upgrade program stores all of the data in the new structure and format used byversion 6.0. See “Simpler, More Efficient Software and Database” on page 3 for a general

description of how the database structure has been improved.To run the first upgrade program:

1. Log on to the Oracle EBS server.


3. Enter this command:

sqlplus vpi/vpi_pwd @vpxupg1.sql

Where vpi_pwd is the password for the vpi user.

Before proceeding to the next step, you should verify that the data has been properlycopied to the schema for the new interface. It is particularly important to make sure thatthe paths defined for each Vista Plus server are correct. To check the data:

1. Log into Oracle EBS and select the Vista Plus Interface responsibility.

2. From the Navigator, select Define Vista Plus Server, Define Vista Plus Server.

3. Make sure the entry in the VP Remote Capture Tools Path points to the directorywhere the Vista Plus remote capture tools are installed on the Oracle EBS host.

4. Make sure the VPI_TOP Path points to the VPI_TOP directory defined when youinstalled the software.

5. If the server captures through Vista Plus Output Manager, make sure the VPOMCommand Path field points to the directory where the VPOM commands are installedon the Oracle EBS host.

6. If any of the paths shown are not correct, type the correct path and save your changes.

7. If you have more than one Vista Plus server defined, select the next one in the VPServer Name field. Repeat steps 3 though 6 for each server.

8. Return to the Navigator and expand Inquiry Information.

9. Use the ... Already Migrated features to make sure that they list the correctresponsibilities, users, and reports as having already been migrated to Vista Plus. Theupgrade program reads the old interface’s schema to mark the items that already existin Vista Plus.

Once you have verified the data in the interface forms, you can proceed with the secondupgrade data conversion program.







Page 14

Run the Second Upgrade Program

The second upgrade program reads the data that was created in the new interface schema by the first program and uses it to create vadmin commands to update the Vista Plusdatabase. (Most of these commands modify the Vista Plus objects created by the earlierversion of the interface so that they use the new name and description formats, asdescribed in “More Meaningful Object Names and Descriptions” on page 5.) It placesthese commands in a series of .dat files—one file for each vadmin command type—andcreates a shell script to run the commands in each file.

To run the second upgrade program:



3. Enter this command:

sqlplus vpi/vpi_pwd @vpxupg2.sql

Where vpi_pwd is the password for the vpi user.

This command creates two types of files in the $VPI_TOP/dat directory:

• Data files, each containing a series of vadmin commands. The files names are in theformat SID_CommandAbbreviation.dat.

SID is the SID for the Vista Plus server the commands are for and ShortCommand isthe short form of the type of vadmin commands the file contains. For example,test_mu.dat contains ModifyUser commands for the server with the SID test.

• Shell scripts, each of which executes all of the data files for a particular Vista Plusserver. The script file names are in the format SID_vpadm.sh. SID is the SID for theVista Plus server the file is for.

Execute the vadmin Commands

Warning This procedure changes the names and descriptions of the Vista Plus reports,folders, users, and groups created by the previous version of the interface. Besure you have a good backup of your Vista Plus database before performingthese steps. After you have performed this procedure, if you want to return tousing version 5.1 of the interface, you must restore your Vista Plus data froma backup.

The vpxupg2.sql command creates data files containing vadmin commands and the scriptfiles to execute them in the $VPI_TOP/dat directory. However, the commands should not be executed from that directory. They need to be moved to the upgrade directory,$VPI_TOP/dat/upg5160. To move and execute the files:

1. Log in as applmgr.

2. Change directory to $VPI_TOP/dat.

cd $VPI_TOP/dat







Page 15

3. Move all the data files to the upg5160 subdirectory with this command:

mv *.dat upg5160

4. Copy all the shell script files into the upg5160 subdirectory, then remove them from$VPI_TOP/dat:

cp *.sh upg5160rm -f *.sh

Note You need to copy and remove the shell script files, instead of moving them, because they are owned by the Oracle database user, not by applmgr. Whenyou copy them, the copies are owned by applmgr, so you can make themexecutable and run them in the following steps.

5. Change directory to $VPI_TOP/dat/upg5160:

cd upg5160

6. Make the shell script files executable:chmod 500 *.sh

7. You can now execute the vadmin commands by running the shell script file for eachVista Plus server. However, before you do, we recommend you open the data files andread the vadmin commands so you can see and understand the changes thecommands will be making.

8. Once you are satisfied that you know what changes will be made to your Vista Plusdata, execute the shell script for each Vista Plus server:

./ SID -vpadm.sh 2>> SID -vpadm.log

SID is the SID of the Vista Plus server the script file is for.

If you have more than one Vista Plus server, repeat this for each script file.

9. View the SID-vpadm.log file to make sure the script executed successfully.

10. Use the Vista Plus clients to check that the folders, reports, users, and groups werechanged successfully. It is probably easiest to do this with the Server Admin client.







Page 16

Update the Server ID

Each Vista Plus server defined in the interface has an internal ID assigned to it. Theinterface programs use this ID to identify the server and objects which belong to it in theinterface schema. For technical reasons, version 5.1 used prime numbers for these IDs;version 6.0 assigns them sequentially. The earlier conversion programs are not able tochange the ID assigned to a server. To complete the data conversion, you need todetermine the old server ID, then run a script to change the server ID in the proper placesin the new interface schema.

To find and change the internal server ID:


2. Call the SQL Plus tool and log in as the vpi user:

sqlplus vpi/vpi_password

3. In SQL Plus, enter this command:

Select QV_HOST_NAME, ATTRIBUTE3 from QV.QSVP_ENV;

This lists the name and ID of each Vista Plus server defined in the 5.1 interface.

4. Now, enter this command:

Select SVR_NAME, SVR_ID from VPI.VPI_SVR;

This lists the name and ID of each Vista Plus server defined in the 6.0 interface. Itshould match the results of the previous command.

If there is only one server defined, you will change its ID to 1. If there is more than oneserver, you will change the lowest ID to 1, the next to 2, and so on.


6. Again, call the SQL Plus tool and log in as the vpi user.

7. In SQL Plus, enter this command:

@vpxsvrid.sql;

8. When prompted for the current server ID, enter the server ID from version 5.1 of theinterface—the one you found in step 3 of this procedure. If there is more than oneserver, enter the lowest server ID.

9. When prompted for the new server ID, enter 1.

The command changes the server ID from the old value to the new value, based onthe values you entered, everywhere it appears in the interface’s schema.

10. If you have another Vista Plus server defined, repeat steps 5 through 9 for the next

one. In step 9, enter 2 for the second server ID, 3 for the third, and so on.vpxsvrid.sql logs all of its actions in the file $VPI_TOP/log/vpxsvrid.log.







Page 17

Assign Vista Plus Folders

Tip If you did not migrate employees or sales reps, and did not use the “forceusers” feature, you can skip this section.

Version 6.0 of the interface does not include two peripheral features which allowed you touse the interface to give users access to reports they did not have access to in Oracle EBS—the ability to migrate employees and sales reps and the ability to force users into VistaPlus groups even if they do not belong to that responsibility in Oracle EBS. (See“Removed Features” on page 7.) If you used either of these features, you need to performactions in Vista Plus if you want to maintain these users’ access to Vista Plus reports. Hereis why:

• The upgrade process creates personal folders for all Vista Plus users created by theprevious version of the interface, including any users created from employees andsales reps. (See “Improved Vista Plus Folder Structure” on page 4 for information

about these personal folders.) However, because the new interface schema does notlink employees or sales reps to any responsibilities or groups, their personal foldersare not linked to any responsibility folders in Vista Plus. To see the reports for aresponsibility, they will have to switch groups to the corresponding Vista Plus group.

• Similarly, the Vista Plus personal folder for each migrated Oracle EBS user is linkedonly to the folders for the responsibilities the user was selected for migration from.The new interface does not maintain the links to “forced” responsibilities. To see thereports for a forced responsibility, the user will have to switch groups to thecorresponding Vista Plus group.

In either of these cases, to make it easier for the Vista Plus users to have access to reportsoutside their Oracle EBS responsibilities, you can use the Vista Plus Server Admin clientor the vadmin LinkFolder command to link each personal folder to the desired

responsibility folders (the personal folder needs to be the parent folder). Links you createin this way will not be affected by the interface.

Unregister the Old Interface

After the interface data has been copied to the version 6.0 schema and you are comfortableusing the new interface, you can unregister version 5.1 of the interface and drop all itsobjects from the database. To do so, follow the procedure below.

Warning Do not use the uninstall program from the 5.1 version of the interface to dothis! You must use the program provided with 6.0 and described here. If youuse the version 5.1 uninstall program, it will also unregister some objectsneeded by 6.0.

1. Make sure no one is logged into Oracle EBS using the Vista Plus Responsibility responsibility. Also, make sure that the interface's database is not being accessed viaSQL Plus or any other method.

2. Log in as applmgr.





After the Upgrade




Page 19

After the Upgrade

After completing the upgrade process, there is one area where you may need to takeaction before you start using version 6.0 of the interface, and another area where you maywant to make some changes to take advantage of one of the improvements in the newversion. The sections below discuss these areas.

Effects of Changed Object Names

As described in “New Features and Changes in Version 6.0” on page 3, we have changedthe name format for the objects—users, groups, folders, and reports—that the interfacecreates in Vista Plus. Because Vista Plus identifies all objects by their unique object IDs,not by their names, this does not cause any problems in Vista Plus. All page securities,permissions, SmartAlarms, and migration rules that were associated with a user, group,report, or folder before you upgraded will still be associated with it afterward, even

though the name of the object will be different.One change that your users will need to be aware of immediately is that, if you use an SIDfor the Vista Plus server and include it in object names, their user names will be differentafter the upgrade than they were before, because the SID will be at the beginning of eachuser name, not the end. Be sure that everyone knows about this change or they will not beable to log in to Vista Plus after the upgrade.

The only other difference in behavior you can expect in Vista Plus viewer clients is that thesort order of objects, especially report and generation lists, will change because of the newnames. There may be an adjustment period while your users become familiar with thenew order.

However, if you have any scripts, either vadmin command scripts or external scripts, thatidentify Vista Plus objects, especially reports, by their names, you will need to modify

them to use the new naming conventions. We recommend you test all scripts carefullyafter making the changes.

More Flexible Private Reports

In previous versions of the interface, any report that you designated as private becameprivate for all users who had private folders. For example, if users A, B, C, D, and E hadprivate folders, and reports 1, 2, 3, 4, and 5 were marked as private, then all five reportswere treated as private for all five users. If user A only needed reports 1 and 2 to beprivate, and user B only needed reports 3 and 5, there was no way to configure that behavior.

Version 6.0 is much more flexible. You select specific combinations of private users andprivate reports. In the above example, you can select reports 1 and 2 for user A, 3 and 5 for

user B, 2 and 4 for user C, and so on, or any other combination you want.During the upgrade process, all private reports and private users defined in the previousversion of the interface are preserved. In our example, that means that each of the fivereports becomes private for each of the five users. If not all of your users who had private



After the Upgrade




Page 20

folders need access to all the reports marked as private, after the upgrade you can use theinterface’s Select Private Report feature to remove the combinations that you do not need.

To do so, just clear the Priv checkbox for each report/user combination to remove, andselect either Unlink or Delete as the delete option. Your changes will take effect the nexttime the Migration request is run. See the sections “Defining Private Reports” and“Selecting the Information to Update” in Chapter 5 of the User’s Guide for moreinformation.

Note All users created in Vista Plus, not just those selected for private reports, nowhave personal folders. Selecting a private report for a creates a private versionof the report and links that report to the user’s personal folder. It does notcreate a new folder. See “More Flexible Private Reports” on page 5.

Documents

Oracle E-Business Suite Interface 6 0 Release Notes