DMT Solutions, Inc.

www.PeopleSoftCareer.com

Page 1 The Upgrade Planning Guide for PeopleSoft 9.2 © Copyright 2013

Copyright © 2013 Printed in the United States of America. Page 2 The Upgrade Planning Guide for PeopleSoft 9. neither DMT SOLUTIONS. and its authors are supplying information but are not attempting to render engineering or other professional services. PeopleSoft. INC. or stored in a database or retrieval system. This work is published with the understanding that DMT Solutions. It is illegal to distribute or copy this book in any part. or damage arising from the use of this publication. If such services are required. The views expressed in this book are solely those of the author and do not represent the views of any other party or parties. omissions. Except as permitted under the United States Copyright Act of 1976. Inc. PeopleCode. the assistance of an appropriate professional should be sought. PeopleTools. However. authorization or participation of ORACLE. Information contained in this work had been obtained from sources believed to be reliable.2 © Copyright 2013 . This book is an independent creation of the author and has been published without license. nor the author guarantee the accuracy or completeness of any information published herein and shall not be responsible for any errors. PeopleBooks and nVision are registered trademarks of Oracle / PeopleSoft Inc. without the prior written permission of the publisher. no part of this publication may be reproduced or distributed in any form or by any means. You are permitted to print one copy of this eBook for yourself. All rights reserved.

................................................................................. 11 Technical Planning .............................................................................................................................................................................................................................................................................................................................Contents Introduction ............................................... 15 Regression Testing ................................................................................................................................................................................................................................................................. 15 Performance Testing ......................................... 12 Create Your Project Plan .................................................................................................................... 15 Parallel Testing .................................................................................................................................................................................................................................................................................................................................................................................2 © Copyright 2013 ............................ 16 Conclusion .......................... 14 Unit Testing .............................................................................................................................................................................................................................................................................. 13 Testing Requirements ......................................... 13 Put Together a Testing Strategy.............................. 14 System Testing ............................................ 15 User Acceptance Testing ................................................................................................................................................................................................... 10 Thou Shalt Know Thy Customizations ............................... 11 Planning Your Project Team Requirements ........................................................................................................................................................................................................................... 4 Acquire all Pertinent Upgrade Information ............................................................................................. 10 Define Your Upgrade Plan ........................................................................................................................................................................................................................................................................................................................... 13 Why Test? .......................................................................... 7 Determining Business Requirements & Critical Success Factors ................................................................................................................................................................................................................................................................... 12 Defining Your Test Strategy .............................................. 13 Define Your Testing Strategy ................................................................................................................................... 16 Page 3 The Upgrade Planning Guide for PeopleSoft 9........................................................................... 8 Retire those Customizations............................................................... 14 Integration Testing .............................................................................................................................................................................. 5 Training for your team .......................................................................................................................................................................................................

Make sure you fully understand the process Page 4 The Upgrade Planning Guide for PeopleSoft 9. Determining Business Requirements 4. Be sure you have an adequate plan and task outline completed before you start your upgrade project. technical requirements.2 © Copyright 2013 . From a high level. Producing a Fit Gap Analysis 5. there are many other factors to consider like what people will be involved? What testing strategy will be used? What kind of training is needed and how many people need to go? The bottom line is that planning is the essential Key to a successful upgrade. Acquire all pertinent upgrade information and materials 2. There are several planning tasks that are necessary for a successful upgrade. The purpose of this guide is to provide you with information that will assist you in getting started planning for your upgrade and installing the new release. implementation/upgrade team requirements. this document will benefit any project team member in a technical or functional role. Training for your team 3. here are the major planning activities that need to be performed. however. There is a lot of planning and decision making that must go into the upgrade process. Layout your technical requirements 6. A PeopleSoft upgrade is no minor feat. Define and layout your testing Strategy 8. and in defining other project considerations.INTRODUCTION This Planning guide was written primarily for upgrade managers. Define the upgrade plan 7. Does my current hardware meet the minimum requirements? Do I need to upgrade my O/S? How about my Database Software? Also. These plans and task outlines will help you in assessing your business requirements. 1.

you may find that you need to make your upgrade a multi-version upgrade. This document will contain all of the necessary steps for performing your upgrade. This application is template driven containing the pertinent steps for your upgrade process and ensuring that you run them in the specific order as instructed by PeopleSoft. This is also where you will find the certified upgrade path for your release. These templates execute set scripts and application engine programs that will be used to convert your data.2 © Copyright 2013 . With this out of the way you are ready to obtain the necessary information.Once your organization had made the decision to upgrade to PeopleSoft 9. PeopleSoft upgrade’s uses the Change Assistant application to organize and automate the upgrade tasks. You will need to review this document to find specific instructions for planning your upgrade. Download the latest release of the Change Assistant and the associated scripts and programs. This can easily be done by comparing your current version of the application with the certified upgrade paths defined by PeopleSoft. Be sure to also download the UPGCONVERT project that will be later loaded into your PeopleSoft Page 5 The Upgrade Planning Guide for PeopleSoft 9. or "Required for Upgrade. This section will supply all of the necessary information and notices for each release. Pay particular attention to any upgrades and fixes that are labeled as "Required for Install". you will need to choose your upgrade path.   Release Value Proposition Prerelease Notes Next you will download the upgrade documentation for your upgrade path. ACQUIRE ALL PERTINENT UPGRADE INFORMATION The very first step to successful information gathering is a visit to Oracle Support's PeopleSoft Upgrade Section.2. You will need an Oracle Support account to access these documents. Updates & Fixes seem to be another crucial step. Depending on how old your release is." Skipping one of these required updates or fixes could result in an upgrade disaster.

52 PeopleSoft has introduced the Update Manager to make this easier for you. and then review them. and technical team leads must know the upgrade process before starting it.Application Designer. be sure to review them. and then review them again. Note: In version 8.  You can “get current” on fixes by having the system generate a custom change package that suits the current state of your environment. for a very good reason. and cost of application maintenance. The PeopleSoft Update Manager provides is supposed to help you reduce time. Other Resources and Links to stay informed are:        Applications Strategy Blog Legislative Updates Blog PeopleTools and Technology Blog Twitter Facebook LinkedIn YouTube Page 6 The Upgrade Planning Guide for PeopleSoft 9. The benefits of this are:   Your environment does not have to be current on maintenance. If you think I just repeated myself I did. Then the PeopleSoft Update Manager will use tools like the Change Assistant and Change Packager and give you an easy way to select what you want to patch to your environment.2 © Copyright 2013 . effort. Now that you have downloaded and reviewed the pertinent information and materials for your upgrade. it is an excellent idea to download and study all PeopleSoft whitepapers on the new features of the version you are upgrading to. The way it works is that PeopleSoft will deliver the most current PeopleSoft applications code and objects in the form of a PeopleSoft Update Image on a Virtual Machine on a regular basis. You can select a single fix and have the system automatically find the needed prerequisites to go with that fix. Project managers. In addition to this information.

if you want to upgrade to the latest release of PeopleSoft 9.com/us/products/applications/054275. The next step will be to ensure the proper education and training of your Upgrade team.2 successfully. Your team members will need the more training than anyone else and it is crucial that they get it early in the project planning and deployment process and not during the upgrade. http://www. So where do you start to find the right training for you or your team? You can start with the Oracle Support website or you can visit Oracle University to schedule formal training. This step has to deal with Training Your Team.Now that you understand that the first step in this upgrade process is to make sure that you are well educated.http://www. Your PeopleSoft upgrade project team members will require training at one level or another. Furthermore. Failure for your team to understand what they are doing will result in a loss in time.2 features on Oracle's You Tube channel. Remember.oracle.com/user/PSFTOracle?feature=mhee and the PeopleSoft Information Portal . so you want to make sure they get the proper knowledge and skills necessary to upgrade successfully.youtube. In addition you can find a great series of overview videos on the latest 9.2 © Copyright 2013 . you want to make sure that your Upgrade team is adequately trained to ensure a smooth upgrade. TRAINING FOR YOUR TEAM Next. They have several guides to training courses that are designed to easily let you see what training is needed for a specific role. I would like to make mention of another crucial step in the upgrade process. This will include the education of the Upgrade process and the required training to help your team be successful in upgrading. these team members are the key to a fast and smooth upgrade. These guides contain a list of the most common roles in your upgrade project team and the training courses that would best develop the skills required for that role. All Page 7 The Upgrade Planning Guide for PeopleSoft 9. production and money.html Oracle / PeopleSoft has designed a road map for the specific training your team members will need.

Oracle has extended the 9. All of these are necessary steps in determining your Business Requirements. Are you getting the idea of what a scope is? Next. and partners.0 support through June of 2015. or implement new Talent Management functionality or Self Service features. establishing the scope of your project is also crucial in ensuring you are successful. listing any new customizations that you will add during the upgrade. For example. suppliers. knowing how much testing and what level will be done. how many databases you will use and the name & function of each. Next is to make a timeline for your implementation listing your CSF's and your milestones. take how long you Page 8 The Upgrade Planning Guide for PeopleSoft 9. be sure to list the number of team members. Defining the scope of your upgrade project is important so that your team and members outside of your team understand what you are doing and stay within the confines of that scope. By doing so. how much technical and functional analysis is involved. Or. it is crucial that you know your CSF and the associated risk factors. documenting the new features and modules that you will be taking advantage of in the new release. Finally.things you can't afford on an upgrade project. knowing the scope of training your end users and managers.2 © Copyright 2013 . you will be able to manage your entire upgrade project like a Pro! One of the first ways that you can define your business requirements is to establish your upgrade budget and know it before you start. Perhaps you want to extend you application to your customers. Other factors to consider in your scope are. Perhaps you want to reduce costs. DETERMINING BUSINESS REQUIREMENTS & CRITICAL SUCCESS FACTORS Do you know what the Critical Success Factors (CSF) are for your upgrade? Why are you upgrading in the first place? I know many of you will say "because we have to or we will lose support." but I'm sure that some of you are upgrading for other business reasons. In addition to this. let’s talk money and budget! Face it! You can't just do what you want. maybe you want to implement employee and manager self-service and save big on HR and Payroll administrative costs. Whatever the business reason.

2 © Copyright 2013 . outside resources. the bean counters in your company have limited the amount of money you can spend by approving a budget. this task will be very important. And even more importantly.000 consultants to do the job! If you've been involved in the PeopleSoft world long enough then you know that it used to be that way in the 90's. end date. Here is where we start to roll up our sleeves and do some analysis against our current version of the application and the new release of the application. Lastly. training etc. This is called a Business Fit Gap Analysis. It is essential to identify these items and create a budget for your project. if you have a lot of customizations. we have discussed the various requirements and information gathering stages. For most companies. software. All of these guidelines and tasks are extremely important in identifying your Business Requirements to ensure a successful upgrade. After all. Some upgrade projects that include the addition of new modules take as long as a year. you can add a few more months. Got Customizations? Well if you have a lot of customizations and you are embarking upon an upgrade from an earlier release. However. Be sure to treat your upgrade the same way you would treat any corporate initiative or project.2. the average time to upgrade to HCM 9. and you are planning on adding new functionality.want. However. You will start by looking at the release note and comparing Page 9 The Upgrade Planning Guide for PeopleSoft 9. especially in this economy! What? You haven't created a budget yet? You better start now and get going. those days are long gone and you need to ensure that you stay within a budget and get a return on your investment of upgrading to PeopleSoft 9. because you may have to acquire new hardware. and major milestones. will help you to better plan and manage your project so you won't have to stop in the middle of the project to get approval to by another server or piece of software. and bring in 1. you will be successful! Producing a Fit Gap Analysis So far. Make sure that you list target dates and milestones and associate your CSF's where applicable.2 will take approximately 3 to 4 months and 3 to 6 months for Financials. make sure you create a project timeline that shows your start date. Doing so.

look at pages. this is what you either love or hate to do. So. to retire those high-maintenance customizations and accept the new delivered functionality that replaces them. for years to come. and batch programs that you customized for your business needs. RETIRE THOSE CUSTOMIZATIONS Now. if you find that your customization has been replaced with a delivered functionality or component. fields. This can save you a countless Page 10 The Upgrade Planning Guide for PeopleSoft 9. then you will already have the documentation for all of your customizations. both now and in the future. interfaces. you will want to keep the delivered and dump your customization to save you countless hours in maintenance and upgrades. try to obtain the same project team members for your upgrade that you used in your implementation and throughout the lifecycle of your installation. Oracle provides a release comparison HCM Cumulative Feature Overview Tool which will compare your current release with the new one and give you all of the new features. you will find the various fits and gaps between your customizations and the new features and changes you found in the release notes. In doing so. If not. records. well then get busy! You need to know your customizations to perform a successful fit gap analysis. look at your reports.2 © Copyright 2013 . To Re-Customize or Not to Re-Customize?? You should identify as many opportunities as you can. While doing this.them to your current customizations. THOU SHALT KNOW THY CUSTOMIZATIONS Most importantly. For online components. be certain that you know your customizations like the back of your hand. If you have done it right. Why would you want to dump them? Because. PeopleCode. make sure that you examine both the online and batch components that you have customized. Take your time to carefully identify all of your customizations and compare the current release functionality with the new functionality in the new version. if you do it right. menus. During this step is where you get to make all kinds of decisions on whether to dump or keep your customizations. but it will work to your advantage. For Batch reporting. to determine the differences in your customizations and your new release. Know Thy Customizations! Finally. etc. if you can.

and Planning. TECHNICAL PLANNING In order to efficiently perform your upgrade as smoothly as possible. Now we will discuss Planning. be sure to plan for at least three times the size of your current production database with room for several backups of these databases. we have discussed the various requirements and information gathering stages. When you perform an upgrade you will need a vast amount of file and database disk space for holding multiple copies of your database. Planning. We have even included a sample project plan for you to use. And. DEFINE YOUR UPGRADE PLAN So far. Second. it is most important that your upgrade Page 11 The Upgrade Planning Guide for PeopleSoft 9. we have also discussed the Business Fit Gap Analysis of our current version of the application and the new release of the application. Therefore. identifying key personnel and resources.number of hours during your upgrade. There are really 3 steps of planning that we need to highlight. In our next article we will discuss the planning of your technical requirements. This is the information you downloaded in an earlier step. Did I mention Planning? Now that you have gathered this enormous amount of information and performed your business fit gap analysis. you need to plan your project team requirements. here is some important information for capacity planning. Once you perform this comparison you will be able to see the Gaps in your technical environment and discover what needs to be aqcuired to meet the new requirements. you need to perform a review and analysis of your current hardware and software components that make up your current PeopleSoft application. you need to perform Technical planning. you should be knowledgeable and prepared enough to start planning and putting together your Project plans. you will create your detailed project plan. Furthermore you will require about twice the amount of File Server space that you utilize in production today. This will include planning for your technical requirements and performing a Technical Fit Gap analysis. First. Now. You should document this information in a spreadsheet or other format and then compare this information with new release Hardware and Software requirements. Finally.2 © Copyright 2013 .

you can start to establish your working upgrade environment for your team. If you have the members of your implementation still on hand. You will also need to include testing and end user training in this process. CREATE YOUR PROJECT PLAN Now that you have identified and documented your gap fit analysis. Developer. any external assistance you need. and Functional Resources. make sure you target these individuals as the key members of your project team. System Admin. So you will need to identify these Key resources and create a resource plan accordingly. and change control procedures. roles. Finally. key team members. Once you identify each of these key role players. and anything that is needed for the team to be successful. These standards will ensure that your team works with documentation. The best way to do this is to utilize your documentation of the business fit gap analysis. DBA. and the Upgrade instructions. Their knowledge is extremely valuable. phones. Your project will need a Project Manager. dedicated shared file directories. their skills.server have the appropriate processing power. documentation of issues. issue management. and standards you are ready to create a detailed project plan that is specific to your environment. Installer. create a resource plan that documents their roles. This will include workstations. PLANNING YOUR PROJECT TEAM REQUIREMENTS If you have ever performed a PeopleSoft upgrade or implementation. supplies. Page 12 The Upgrade Planning Guide for PeopleSoft 9. This will allow you to create an outline of the detailed tasks that are required to execute the upgrade. resources. technical requirements. and any additional training that is required for these team members. Make sure that you clearly define their roles and determine the amount of time they will be able to commit to the upgrade project. Technical Upgrade Specialist. the technical fit gap analysis. memory. make sure you identify and establish standards for your upgrade project. After the resource plan is completed.2 © Copyright 2013 . email groups. Network Admin. and that it is properly configured for a large amount of batch processing. then you know that it requires key personnel and resources to make necessary business decisions and to be able to identify customizations and other business requirements. communication.

you will need to define the testing strategy before the project begins or soon after. Your testing strategy will provide the basis for understanding how you will test your newly upgraded applications. but the majority of testing will occur after your application has been upgraded. Therefore. After you are comfortable that the system is working properly. The project manager and upgrade specialist should identify these stages. Some of the stages will include testing the integrity of the data and meta-data structures within the PeopleSoft applications. specifically after upgrading PeopleTools and also when copying upgrade projects from your demo database to your copy of production. and when the testing should be performed. you can perform the Test Move to Production. There are several points within the technical upgrade process where your developers will unit test programs. you will not be performing the testing until a later time in your upgrade project.DEFINING YOUR TEST STRATEGY Although. let’s talk strategy! PUT TOGETHER A TESTING STRATEGY An effective testing strategy will require that you have a pretty solid understanding of the different stages of a PeopleSoft Upgrade. It is extremely important to know where these stages are. for the testing strategies that you will perform. it is crucial to develop a plan. Therefore. You will verify that the system is working properly by reviewing the system online. early in the project. TESTING REQUIREMENTS There is more than one approach and method you can take for testing your upgrade and you should Page 13 The Upgrade Planning Guide for PeopleSoft 9.2 © Copyright 2013 . your testing strategy should be based on these day-to-day processes and you should involve the users and functional leads that perform these processes. There are certain key stop-points or stages where certain testing should be performed. These steps are outlined in the upgrade instructions and usually include running and reviewing your DDDAUDIT and SYSAUDIT reports from your copy of production. But first. WHY TEST? Testing your database after you have completed the upgrade ensures that you can still operate your day-to-day processes on your newly upgraded release of your application.

SYSTEM TESTING This stage of testing ensures that all your functionality works together. However. There is no need for testing scripts in this phase. The testing types below do not necessarily run systematically. one after another. you will be testing customizations.2 © Copyright 2013 . certain organizations may not require all testing stages listed. you have completed your upgrade tasks. UNIT TESTING In this stage of testing. Your database is now at the new release level. Here are some basic questions to ask:    How many products and modules do you currently have in your production database? How many customizations you have in your production database? What you need to test? DEFINE YOUR TESTING STRATEGY Once you have evaluated your testing requirements. to determine the levels of testing required for your applications in your organization. you will test to ensure that you can access existing data and enter new data successfully. Different test conditions can sometimes run in parallel. as each organization is unique. Use the testing type definitions below. Review the following testing types. you will want to unit test before you use the new system. Every organization will develop their testing strategy slightly differently from others. During this phase you will test individual transactions and processes of your application. In addition. you will determine the type of testing you need. In addition.evaluate your requirements by gathering key information about your applications and environment. You will test your logon process. Define what you will need for each testing type. defined from the PeopleSoft upgrade instructions. Sometimes. and verifying access to data and pages. In addition. the test Page 14 The Upgrade Planning Guide for PeopleSoft 9.

you validate your data. and external applications.eliminates conflicts with old and new customizations. reports. You will also define the acceptance criteria for your upgrade. During the upgrade. This phase should require testing scripts and an issue resolution process to resolve any open issues. In addition. This stage is optional but is very useful in that you can perform a test move to production that creates a new environment. USER ACCEPTANCE TESTING In this stage of testing. interfaces. PERFORMANCE TESTING This stage of testing measures your current system performance against the new release level performance. In this phase. business rules. paying.2 © Copyright 2013 . Page 15 The Upgrade Planning Guide for PeopleSoft 9. and customizations. INTEGRATION TESTING In this stage. you will test to ensure that your business processes work as designed. This is where your end users and business process owners will run through all of the test scripts and execute key business processes such as hiring. and business processes requirements. PARALLEL TESTING This stage of testing is optional and is mostly used for those customers with extensive Payroll customizations and setup. terminating. etc. batch programs. you can test all of the integration points between modules. security. Then. if necessary. You should not move on to the next phase unless this is successful. you will use a full functioning and separate testing environment to test all business processes. you will ensure that any design flaws are resolved before User Acceptance Testing. This phase will require testing scripts to follow and record the results. You’ll want to monitor the performance during this phase and even perform load testing. you would be performing parallel tests throughout all testing stages to ensure that your upgrade was successful.

1. Define and layout your testing Strategy 8. Define the upgrade plan 7. and testing plan for a successful upgrade. please send me your feedback at http://dmtsolutions. Producing a Fit Gap Analysis 5.zendesk.com Page 16 The Upgrade Planning Guide for PeopleSoft 9. training and putting together a solid project plan. If you would like to provide me with your feedback and/or provide me with a suggestion of other topics you would like me to create. We covered the following topics. Determining Business Requirements 4. because you will use it later in the upgrade process when you complete the upgrade of your copy of production. Training for your team 3. Layout your technical requirements 6.REGRESSION TESTING This stage of testing validates the test move to production and move to production parts of the upgrade. testing strategy. You have now finished developing your testing strategy and you should document this information thoroughly. Make sure you fully understand the process I hope this guide was useful to you. CONCLUSION This upgrade planning guide should give you enough information to start planning.2 © Copyright 2013 . Acquire all pertinent upgrade information and materials 2.

Sign up to vote on this title
UsefulNot useful