Compare Process

The Application designer upgrade tools are designed to streamline the process of merging system objects, such as records, pages and PeopleCode from one PeopleSoft Database to another. Once you install PeopleSoft for the first time, you customize it for your business requirements by changing the Pages, Records, Menus etc. Since PeopleSoft also delivers new applications with changes, these changes may be distinct from the changes you have made or they could overlap in some area. For this, when you perform an upgrade, you have to decide whether to keep the modification you have made or accept the modification made by PeopleSoft. This is done by Compare Process, where you compare the application between 2 databases, the Source and the Target.

• The Source Database is the source of new changes (usually New Release)
  
  
• The Target is the database to which you are moving these changes (Copy of Production or Production Database)
  

There are 3 steps during the compare process which would need to decide which components you want from the source and then merge them into your target database. The 3 core steps of the compare process that utilize the Application Designer Upgrade tools consist of the following procedures:

Compare Compares the objects between the Source and the Target databases and produces a PeopleSoft Project that identifies objects with differences the 2 databases.

Report Produces reports that detail the differences between the objects in the project Copy Merge the source database and target database using the entries identified during the compare process that have been marked for updates.

The PeopleSoft system uses several system tables PSRELEASE and the various definition tables, to record modified data time and which operator modified the object. This PSRELEASE table contains rows of data for every release level at which the database has ever existed. It has 2 columns, RELEASEDTTM and RELEASELABEL. The first column RELEASEDTTM contains a date time stamp identifying when each release level was stamped. RELEASELABEL identifies the release level. When comparing 2 databases, you can compare on date or on release level. Both methods use data and time to determine the object status. Each PeopleTools Object type record for example, for object type of Records, there is a PeopleTool table called PSRECDEFN, this would include 2 columns like LASTUPDORPID and LASTUPDDTTM which would tell us who the last updated Oprid is and Last updated date time.

There are various Object Status like:

• Unknown The default status of all non-comparable objects
  
• Absent Found in other DB and not in this one.
  
• Changed The LASTUPDOPRID value is “PPLSOFT” and its LASTUPDDTTM value is greater than datetime stamp of the Comparison Release database, which indicate the new release has the modified objects
  
• Unchanged The LASTUPDOPRID value is “PPLSOFT” and its LASTUPDDTTM value is less than or equal to the datetime stamp of the Comparison Release database, which indicate the PeopleSoft last modified the object prior to the
  Comparison release.
  
• Changed* The LASTUPDOPRID value is not “PPLSOFT” and its LASTUPDDTTM value is greater than datetime stamp of the Comparison Release database, which indicate the you modified the object since the Comparison release.
  
• Unchanged* The LASTUPDOPRID value is not “PPLSOFT” and its LASTUPDDTTM value is less than or equal to the datetime stamp of the Comparison Release database, which indicate that you modified the object prior to the Comparison release.
  
• Same The object has been compared and is defined the same in both the databases.

Once the compare process is done, it assigns default actions for each object depending on what needs to be done to make the Target database consistent with source. The action types include:

• Copy - the Object will be copied to the target database
  
• Delete - the Object will be deleted from the target database
  
• CopyProp - For Record Definitions Properties, choose to copy the
  record properties without copying Record Fields.
  
• None - Appears if the objects are identical in the source and target database.
  
  
  

Review Hardware and Software Environment

Check the PeopleSoft Customer Connection website to get the Hardware and Software guide. This guide outlines the hardware and software requirements for the new release. These are the minimum levels require to operate your PeopleSoft system for new release.
For Example, before you begin a upgrade, make sure that you are on supported release for the upgrade to PeopleSoft 9.0. Ensure that you have reviewed this guide thorougly and begin the acquisition process for any hardware and software upgrades that are not delievered by PeopleSoft. You can find this document by navigating :

• Implement, Optimize, and Upgrade
  
  
• Upgrade Guide
  
  
• Upgrade Documentation and Scripts
  
  
• Hardware and Software Requirements

Also, check the PeopleSoft New Release notes that would provide the information on platforms that are certified.

• Implement, Optimize, and Upgrade
  
  
• Upgrade Guide
  
  
• Upgrade Documentation and Scripts
  
  
• Release Notes
  
  
• Enterprise
  
  
• PeopleTools

Release notes should help you to determine what has changed in the system, and to familiarize with new features. They also provide you with detailed information regarding application changes.

Planning the Upgrade Process

The Planning & Initiation phase establishes the overall project environment. If this is your first upgrade, it could be a challenging task at the beginning.As you go along the process, you would learn quite a bit and it would be very good learning experience. I believe this blog should help prepare those inital stages and help you get going. In this phase, most of the planning is completed, the team identified and supporting project processes documented. Usually a “road map” is defined for completing the work with deliverables like Project Plan, Project Budget or an Estimation, Resource Requirement, and Technical Assessment of the PeopleSoft Environment.

When you develop a Project Charter, you would have to present to the Management as to show the Benefits of this process, summary and background of the upgrade project, its objectives and the scoping and its risks.

Also, a detailed project plan should be developed that has the entire roadmap that defines each and every tasks, deliverables, milestones, work hours, resource allocations and timing. The plan should include all appropriate tasks and resources accountable for on-time completion. Please check the attached Sample Project Plan that can be used for your project. Also, please leave comments on what other things that can be included in the plan. The Sample project plan is for PeopleSoft HRMS Upgrade from 8.3 to 8.9 that includes initial pass and test move to production



The most important task during the Planning Phase is to do an assessment on your hardware and software environment. This would address the technical infrastructure required for the new PeopleSoft Release. This is critical for a smooth and successful upgrade process. Check the hardware and software requirement from the PS CC website and also platforms supported. Also, you would look into the customization level of your production environment to categorize them as easy, medium or complex level.

The length of the PeopleSoft Upgrade project depends on many factors. Some of the most common factors are: The level of cutomizations (easy , medium , complex), the number of resources available, your environment, the number of modules implemented, if you are considering the implement new functionality, your budget etc.

PeopleSoft provides an upgrade home page for each release (each major releases, product updates and service pack releases). Each home page contains the certified upgrade path for that release, the upgrade instructions, and the paths to fixes that are required for upgrade.

The navigation for this home page in PeopleSoft Customer Connection is:

• Implement, Optimize, and Upgrade
  
• Upgrade Guide
  
• Upgrade Documentation and Scripts
  
• Release
  
• Enterprise
  
• HRMS
  
• PeopleSoft 9.0
  

Make sure that you are on the supported PeopleSoft release for the upgrade to PeopleSoft new version as listed on the Upgrade Documentation Page.

Identifying Project Team Members:

An important part of your upgrade process involves having key resource personnel. They can be either dedicated or partially dedicated. The following are the important upgrade roles that should be considered during the project:

Upgrade Project Manager: This member must be familiar with the upgrade process.This individual must be able to make management decisions and resolve issues that impact the progress of the upgrade project.

Upgrade Specialist or Technical Upgrade Resource: This individual must be familiar with PeopleSoft upgrades, RDBMS, SQL, PeopleTools, Change Assistant Tool, Data Management Tool, Application Engine and PeopleSoft Configuration and Administration. This member will execute and manage all technical upgrade tasks and will log all upgrade steps. Resolves issues with DBA or System Admin. Oversees all necessary checklists to ensure completion of the upgrade.

Database Administrator:The DBA must be a dedicated upgrade resource and will help in reviewing the scripts and to modify them if necessary. Monitor closely the database and provide support, perform back-ups and recoveries. Also help in troubleshooting and tuning the database.

Network/System Administrator: A part time member, will help in managing the network security and connectivity, troubleshoot network issues, Manage logins, passwords and system security etc

Developers: PeopleSoft Developers must be familiar with the customizations, they would need to have good amount of experience in SQR, COBOL, PeopleTools, Application Engine, PeopleCode, Crystal etc. They would help in Retrofit Customizations, Unit, System and Interface Test the change and document all the changes.

Functional Resource: These key members must be familiar with your business process and customizations. This member must be familiar with new release functionality as well. This key individual must review Release notes, identify customizations, create and execute test plans, document all issues etc

Understanding the Upgrade Process

Once you know the definition of PeopleSoft Upgrade as defined in the previous post, you need to review the PeopleSoft Upgrade components which are

catergorized into 3 main system components:

Most of the times you would have to upgrade your environment like RDBMS, Operating System, Third party tools etc.

After reviewing the H&S , you

Steps involved in PeopleSoft Upgrade Process

Following are the Steps or Parts that are involved in PeopleSoft Major Application Upgrade Process:

- Planning the Upgrade Process
- Understand the Upgrade Process
- Review Hardware and Software Environment
- Install Demo Software
- Apply Updates required for Upgrade
- Installing and Configuring Change Assistant
- Process Initial Pass
- Compare Process
- Data Conversion
- Applying Customizations
- Testing the Initial Pass process
- Test Move to Production
- Final Move to Production or Cut-Over

What is PeopleSoft Upgrade?

The term upgrade or upgrade process could mean:

• Moving from one (current) release level to a higher (newer) release level

• Upgrade to a new release of your own by copying a subsystem from development to production.

• The PeopleSoft upgrade process begins when PeopleSoft issues a new release and ends when you have successfully upgraded to the new release.

For Example, if you are currently on PeopleSoft 8.9 Version, and since PeopleSoft 9.0 is already released, you can upgrade your HRMS system to 9.0 vesion. You have basically follow the Upgrade Methodolgy that is available.Most often this move comes with benefits -- technical and functional -- that are improvements to the way the current release functions.

PeopleSoft uses the term “Upgrade” in a special sense – an upgrade is the migration of any object or objects from one PeopleSoft Database to another, and the subsequent adjustment of the PeopleSoft system to accommodate the new objects.

When you upgrade to new PeopleSoft Release you are provided with a new database, as well as the information you need to adjust your system components – COBOL statement, SQR’s, the system messages and so on, to work with objects in the new database.

An Upgrade can consists of Upgrading one or more of the following PeopleSoft components:

· Internal tables which are used by PeopleSoft Programs called PeopleTools Tables.

· Calculation programs for Payroll, Benefits, Time and Labor etc like COBOLS, SQR’s.
· Application Tables and other definitions like Records, Pages, Menus, so forth.

· PeopleTools Programs which are used to run online system under windows.

PeopleTools Tables contain the PS no underscore tables and their companion tables contain the data dictionary for PeopleSoft Applications.

Application Tables contain the PS_ tables that contain the online Application

A PeopleSoft upgrade requires a lot of planning, time, resources, testing, and development.When upgrading to a new release of PeopleSoft it may be required to upgrade the hardware and software environment; You may have to install new RDMS software, new server machines, upgrade third party tools that make up the complete environment and all of this software should be supported by PeopleSoft. For this you need to consult the Hardware and Software Guide or the Platforms Supported from PeopleSoft Connections.

The PeopleSoft Upgrade process streamlines copying system objects such as records, pages and PeopleCode from one PeopleSoft database to another and finally into your current production database.

When you do upgrade to a new PeopleSoft release, several upgrade passes are required to ensure that whenyou perform the final pass your upgraded production database performs as you expect. You must complete allof these passes to complete your upgrade. The first pass is called the initial pass. In this pass, you create a copyof your production database referred to as Copy of Production. You then take the delivered database (the onewith the new PeopleSoft release delivered with your product) called the Demo database, and incorporate themodified objects into the Copy of Production to create your first upgraded Copy of Production. In this passyour Demo database is your Source and the Copy of Production is the Target.

After you complete the initial pass, you begin the first test Move to Production pass. In this pass you createanother copy of your production database called the New Copy of Production. You take the upgraded Copy ofProduction (the one created in the initial pass) and incorporate the modified objects into the New Copy ofProduction to create your second upgraded Copy of Production. In this pass, the upgraded Copy of Production(from the initial pass) becomes your Source and the New Copy of Production becomes your Target.The test Move to Production is repeated until it runs smoothly. A New Copy of Production is created for everytest Move to Production pass and is the new Target for each pass.

When you are ready for the final Move to Production pass, you freeze your production database andincorporate the modified objects from your most recent upgraded Copy of Production into the productiondatabase itself. Once again the upgraded Copy of Production (from the test move to productions) is yourSource and your production database is the Target.