Skip navigation
1 2 3 Previous Next

PeopleSoft Enterprise Support Blog

38 Posts authored by: CarlaG-Oracle

Creating a PeopleSoft Non-Technical Service Request

 

 

What is the difference between a Technical and a Non-Technical Service Request?

 

Technical Service Requests

examples:

--You are installing the PeopleSoft product and run into an error.

--You wish to apply a Tax Update but cannot find the Update on MyOracle Support (MOS).

--You are looking for non-current upgrade materials on MOS.

--A Cobol program does not compile, but instead, gives off errors.

--The process scheduler (or application server or web server) does not boot up.

 

For all of the above, you need to work with a support analyst to debug these issues.

You may need to provide logs, screenshots, or trace files.

 

Non-Technical Service Requests

example:

--When you want to request software that you cannot locate in your application's Update Home Page or on the PeopleTools and Patches home page, or in e-delivery (Oracle's Support Delivery Cloud).

 

How to create a non-technical service request? 

In MyOracle Support, select the Service Requests tab.

See section labeled Contact Us Service Requests.

 

HowTo3.bmp

 

Click on Create "Contact Us" SR.

Fill in the Problem Summary with appropriate information.

 

For Problem Type, select from the drop down:

   Software and OS Media Requests

Then choose what is appropriate:

   electronic download Software and OS Media Request

   exception physical Software and OS Media Request

 

You will also need to enter your Support Identifier.

Click "next" and review materials presented to you, and "next" again to create the service request. 

The service request will be routed to a specialist who can advise you in obtaining the materials requested. 

The PeopleSoft PeopleTools 8.56 Upgrade Home Page (Doc ID 2270700.1) contains a link to directions on how to do this.

This documentation will walk you through the steps needed to perform a PeopleTools-only upgrade to PeopleSoft PeopleTools 8.56 using the PeopleSoft PeopleTools DPKs. Be sure to read this before you start your upgrade, because the process flow is different from the traditional method. This documentation is needed in addition to the regular upgrade documentation, found in Doc 2270700.1, section Upgrade Documentation.

 

  Performing a PeopleTools–Only Upgrade Using PeopleSoft PeopleTools DPKs

 

Upgrade Flow.bmp

 

 

More instructions follow this diagram.

 

If you need to patch PeopleTools to a higher release than what is delivered in the image,

See PeopleSoft PeopleTools Patches Home Page (Doc ID 2062712.2) / Best Practices tab.

The HCM 9.1 to 9.2 PI 24 upgrade is now available.

This upgrade was written for upgrading the HCM application to 9.2 PI24 on the PeopleTools release PT 8.56.03+.   

 

Top of Doc 1959519.2.bmp

 

In the PeopleSoft Human Capital Management Upgrade Home Page (Doc ID 1959519.2), see the tab at the top for this new upgrade.

Located there are the materials for this upgrade: 

   

    upgrade path certification chart

    demo-to-demo compare reports

    upgrade documentation in pdf and html formats

    and more.

 

Also on this page is the link to a renamed Getting Started on Your PeopleSoft Application Upgrade document, dated October 2017.

 

 

Where are the Upgrade Source Images?

Yes, a new Upgrade Source Image for the upgrade 9.1 to 9.2 PI 24 is available, posted to the HCM Upgrade Home Page tab HCM Upgrade Source Images.

This Source Image is HCM 9.2.003.

 

Second Top of Doc 1959519.2.bmp

 

The Upgrade Source Images for all PeopleSoft product pillars were previously posted to the

PeopleSoft Upgrade Source Images Home Page (Doc ID 1552580.1) but in the future will be available on their specific product's Upgrade Home Page. 

 

We suggest a thorough review of all sections of the Upgrade Source Images tab.  Topics covered there include Languages, Unicode, the certified Upgrade Path and details, Hardware/Software requirements, and a variety of useful links to needed documentation.   For an overview of the steps needed to use the Upgrade Source Images, see (the document linked there) titled Using Upgrade Source Images for PeopleSoft Application Upgrades.

 

VCDs

Will the VCDs for HCM 9.2 PI 24 be available soon on the Oracle Support Delivery Home Page (previously e-delivery)?

No.  To learn more, read the new Tech Update - PeopleSoft Application DPKs Replace VCD Installation with PeopleTools 8.56 (Doc ID 2291199.1).

 

Just to review

The latest PUM "PI" Image 24 will be needed in order to create the Upgrade Change Package, which contains the upgrade job template. The PI is also needed to generate the required-for-upgrade patches project.  

 

Really important

When using the HCM Update Image 24, and until the future Update Image 25 is generally available, you will have to first apply the PRP 26969666 to the PI 24, to be able to generate the upgrade template.  The PRP is to be applied to the PI 24, not the to Upgrade Source Image.  Refer to the note on the PeopleSoft Human Capital Management Upgrade Home Page (Doc ID 1959519.2), section Upgrade Packages (Change Assistant templates).

 

The Upgrade Source Image is used to setup the Upgrade Source environment.  The RFU project is applied to the Upgrade Source environment.

Even if your upgrade is using the Upgrade Source image 003, which is HCM 9.2 PI 24, you will still need the PI Image 24 in order to obtain the most recent RFUs and the Upgrade Change Package, which contains the upgrade template and html documentation.  A PRP, 26969666 , should first be applied to the PI Image 24 to obtain the upgrade template.

Three passes in the Upgrade process.jpg

 

     Three passes in the Upgrade process. Test Move to Production is in the middle.  For more information, see Getting Ready for your PeopleSoft Upgrade

     on the PeopleSoft PeopleTools 8.56 Upgrade Home Page (Doc ID 2270700.1).

 

The Test Move to Production Pass

 

Application upgrades consist of 3 different passes:  the Initial Pass, and the Test Move to Production Pass (MTP), and the Final Move to Production pass.  A good big-picture explanation of the Test Move to Production Pass 

is located in the upgrade documentation in section "Understanding the Test Move to Production Passes":

 

The Test Move to Production pass is a different series of steps (from the initial upgrade pass).  It

includes a subset of the previous tasks, and takes advantage of the tasks performed during the first upgrade pass.

 

You should perform as many Test Move to Production passes as necessary to work out any issues and to be

comfortable with the process. During each Test Move to Production pass you will be able to refine the process so

that you can save time and avoid manual processes. These test passes will also let you know how long the process

takes so that you can plan your production downtime for your Move to Production weekend.

 

The steps executed in the MTP pass vary (from the initial upgrade pass) in several ways. Many of the tasks and steps

in the initial test pass will be replaced in the MTP pass with PeopleSoft Data Mover export and import scripts.

 

In the initial pass, some steps required you to make functional decisions and take time to manually set up data. That

data can be copied from the first database to the next, saving you setup time and eliminating the chance for manual

error or typos.

 

The MTP pass does not repeat the database compare/copy steps. You made the decisions once; there is no

need to repeat these steps. Instead, a PeopleSoft Data Mover script, MVPRDEXP, will export all of the tables that

contain the PeopleSoft PeopleTools objects like records and PeopleCode from the first database. Another

PeopleSoft Data Mover script, MVPRDIMP, will import those tables into the second database.

 

Anything you have done to PeopleSoft PeopleTools objects while executing or testing the first pass

   -copied objects from the Demo database

   -reapplied customizations

   -applied updates from the My Oracle Support website

 

will be moved to the second Copy of Production with these scripts.

 

Another important difference in the MTP pass is the handling of SQL scripts that create and alter tables. In the

initial pass, you generate and sometimes edit, then execute the SQL scripts. In the MTP pass, you may be able to

skip the generation steps and use the SQL that you previously generated. This is another way to save time in your

critical go-live window.

 

What are commonly asked questions regarding the Move to Production Pass?

 

Why do the MTP pass anyway?

 

Q: If the Source database requires an initial environment that is up to date,  then what is the advantage of doing a

move-to-production run?  This can only add to the amount of time to perform the upgrade.  Plus, the initial pass

does not seem as efficient to do, as a move-to-production pass.  One issue is that it seems that the Users are taken from the Source

rather that the Target.     

 

A: The Initial Pass includes tasks for the Upgrade compare and copy (you make decisions here); and a task to set aside customizations to be preserved.  The MTP does not include these tasks.  Regarding the users from Source...see next...

  

Production Changes to Psoprdefn are lost

 

Q: In the different MTPs in an upgrade, the PSOPRDEFN table is copied from Source to Target through data mover export

and import scripts (Mvprdexp.dms and Mvprdimp.dms). This procedure does not take into consideration any new values that might be in the Target environment -- because it data-replaces the table. This means that new users (i.e. new rows in PSOPRDEFN table) in the live production environment will be lost from the final move to production. Is this the expected behavior?

 

A:  Yes. The upgrade requests that you "freeze changes to production" during the course of the MTP upgrade pass.

To workaround this design see  E-UPG PT8.2x, PT8.4x, PT8.5x: How to Preserve Security through Upgrade Passes (Doc ID 642944.1).  

 

Why do the PeopleTools Upgrade in MTP?

 

Q: We are currently in the process of upgrading PeopleSoft to version 9.2. When we create a 'move to production' pass

in the Change Assistant,  a PeopleTools upgrade job is created as well. Since the application upgrade contains a step

to export and import all PeopleTools tables (Task 4-1-3: Exporting PeopleTools System Tables and Task 4-1-4:

Importing PeopleTools System Tables) can this PeopleTools upgrade be skipped?

 

A:  Go back and review the tasks in the PTools Upgrade.  You will see that they are more than just an export-import.  

 

Upgrade passes and Preserving customizations

  

Q: When applying updates, you need to select a Pass type.  What is the correct pass type to select?

 

A: Please review E-PUM How to Create a Change Package Incorporating Customizations with PeopleSoft Update Manager (PUM) (Doc ID 1566344.1).

 

Additional patches, upgrading PeopleTools, applying a Tools patch

 

Q:  When are the required-for-upgrade patches to be applied?  Is it one-and-done?

A: These are most usually applied to the Source environment as the upgrade begins.  But that’s just one time to apply them;  it is

important to frequently search for and apply the Required at Upgrade fixes for your particular application.  For more information,

See the PUM Home Page (Doc id 1641843.2) > tab Install and Upgrade > Required at Upgrade patches.  This section has instructions for applying the required at upgrade patches during the different stages of the upgrade:  beginning of the upgrade; before data conversion;  and between upgrade passes.

 

Q:  Can we upgrade PeopleTools between upgrade passes? Or, what about tools patches?

A: Oracle does not support Tools upgrades between upgrade passes.  The Upgrade Templates are written for a specific application release and PeopleTools target release.  This is found in each Upgrade Home Page’s section Upgrade Certification Path.  You are free to apply a PeopleTools patch between upgrade passes, but it is rarely required to do so. 

 

Change Assistant should point to the correct database

 

Q: We are upgrading from PeopleSoft 9.1 to 9.2, PeopleTools 8.52 to 8.55.

For the Move to Production pass, 2 jobs were created “softwareupdate.PeopleTools_Only_Upgrade.{HCM92DEV-HCM92QA}MTP”

and “UPG.HCM91TO92UPG.{HCM92DEV-HCM92QA}MTP”. The PeopleTools only upgrade ran successfully but the second job, (the HCM application upgrade) kept failing at the non-manual steps.

Step “Running the Application Filter” failed because “Change Assistant Failure: Filter Query steps are not supported

for 8.52 and lower databases.”  and  Step “Applying the UPGOPT Project” failed because “System Error : The database is at release 8.55.  The PeopleTools being run require databases at release 8.52.”

How should this be resolved?

 

A: When creating the new Change Assistant Upgrade job for the Test Move to Production pass, take care to specify the correct databases for Source and Target.

You will need to create a new PeopleSoft Change Assistant job for each test Move to Production pass.

 

 

KM references

 

E-UPG PT8.2x, PT8.4x, PT8.5x: How to Preserve Security through Upgrade Passes (Doc ID 642944.1).

E-PUM How to Create a Change Package Incorporating Customizations with PeopleSoft Update Manager (PUM) (Doc ID

  1. 1566344.1).

E-UPG: Applying Additional Maintenance in the Upgrade Passes (Not Required For Upgrade) (Doc ID 1280840.1)

HCM Upgrade: How to Preserve Queries and Tree Objects (Doc ID 2153527.1)

PUM Home Page (Doc ID 1641843.2)

E-UPG Understanding the Upgrade Certification Path section of an Upgrade Home Page (Doc ID 1970917.1)

New in PT 8.56 and the PT 8.56 Tools Upgrade

 

No PTools patching:  the full codeline is delivered containing the PeopleTools patch

Here’s an example – PT 8.56.01 the full codeline contains the 01 patch. Each subsequent PTools patch

will be delivered with a full codeline.

Where is the patch change package?  See PS_HOME\PTP.

 

Elasticsearch is the supported search tool with PT 8.56.   SES/Verity is not supported with this release.

A pre-upgrade manual task will remove the SES indexed data from the SES server.

 

Upgrade efficiencies:

A two-stage copy will help streamline the upgrade.  The records, fields, and indexes will be copied first,

then the records are built, and then the remaining object types are copied.

Data mover scripts will be ‘optimized’.  For similar scripts run with the same id, they will be auto-consolidated into a single nested script.

 

There will be a delivered Linux CA client, but not supported for use with the PT 8.56.01 upgrade.

 

There is no delivered PeopleTools System database with PT 8.56, and no upgrade for the PeopleTools System database to PT 8.56.

 

Translations for the upgrade will be delivered in PTxx.dms scripts, instead of through a PTTLSML project.

 

New features overview See the PeopleTools 8.56 New Features Overview (Doc id 2267247.1)

               New Features were previously called Release Notes

 

Application upgrade template changes? Can you take the current upgrade templates and use them for an application and Ptools upgrade to PT 8.56?

This is not a supported method.  Instead, use the current upgrade templates and upgrade to PT 8.55, then do the PTools upgrade to 8.56. 

Future upgrades to higher Image versions may utilize the new PTools release.

 

Will there be certification changes?  Check MOS / Certifications.  Many existing ‘planned’ certifications may be reposted with PT 8.56.01 GA.  

 

Finding upgrade materials:

The Upgrade documentation is posted on the PeopleSoft PeopleTools 8.56 Upgrade Home Page, (Doc id 2270700.1).

A revised version of the Getting Started on your PeopleTools Upgrade doc, plus the Upgrade Change Package, is also on 2270700.1.

 

Finding the codeline:

The VCDs for PT 8.56.01 are posted to the Software Delivery Cloud site, previously called e-delivery.  

               The DPKs are posted to the PeopleSoft PeopleTools Patches Home Page (Doc ID 2062712.2)

Repository Subscriptions Small.bmp

 

Cloud Manager and Subscriptions

 

What is it

A respository subscription: think of this as a "Pum inbox"

 

In Cloud Manager, a repository subscription can enable you to have your own dedicated File Server in the Oracle Cloud.  This is where your PeopleSoft Pum Images (PIs), standalone patches (PRPs), and PeopleTools patches,  will be downloaded.  

 

Who does the downloading? 

Not you.  Cloud Manager will do this automatically when a new image is released or when a new PRP is made available for your products that you have 

created a Subscription Channel for, and then subscribed to that Subscription Channel.

 

Subscriptions page.bmp

                  Cloud Manager page showing subscribed channels

 

Examples of a Subscription Channel:   PeopleTools channel or HCM channel.

Cloud Manager can download previous  PeopleTools patch releases  for the Tools channel.

For Application channels, only the latest patches are downloaded.

 

 

How does that work, exactly

Cloud Manager has a process scheduler recurring job, that invokes download manager for all the subscribed release channels.  This runs once per week. It will make sure that latest updates for all the subscribed release channels are downloaded regularly  without any user interaction.

 

Repository Subscriptions.bmp

                 The Repository tile is delivered as part of the Cloud Manager home page

 

How to subscribe

To subscribe to a channel, click the Related Actions button corresponding to channel name.

If you select Subscribe option, Cloud Manager starts monitoring for any new PIs

or PRPs and downloads them from MOS.

 

How to un-subscribe

If you select the Unsubscribe option, Cloud Manager will no longer monitor/download latest PIs or PRPs. No downloads are performed.

 

Minimum release

Is there a requirement in order to use Cloud Manager?

The minimum application release is 9.2, used with a minimum of PeopleTools 8.55.11 

 

To learn more

  For more information, see Chapter 3 of Cloud PeopleBooks.

The Oracle Cloud and Trial (or Paid) Subscriptions

 

Cloud Pic.bmp

 

You can obtain a Trial subscription to use the Oracle Cloud, for 30 days. 

A requirement is that your site is a PeopleSoft licensee.

If you are licensing PeopleSoft, you can choose to have a Trial subscription, or a Paid subscription, in addition to the licensing of PeopleSoft.

 

If you choose to have a Trial subscription, you can deploy and maintain any PeopleSoft application you have licensed, in the Oracle Cloud. 

These environments can be used for development, testing, or training.  Play around with it, install and use Cloud Manager, for a 30-day period.

These applications will remain available in the Cloud until you no longer subscribe to the Oracle Cloud.

The Cloud Services subscription (purchased or trial) would provide you with a Customer Support Identifier (CSI). This is separate from a license to use PeopleSoft. 

If you do not have a Cloud CSI, and want to temporarily obtain a Cloud account, you can get a 30-day Trial subscription.

 

The license for PeopleSoft applications is not the same as a license for Oracle Cloud services.  You would need to get Cloud subscription to create an environment

in the Cloud.  Once you have obtained a subscription to Oracle Cloud, no additional PeopleSoft application license or usage license is required.

 

For more information, see the  PeopleSoft Cloud FAQ

Also, review the following documentation:
PeopleSoft on Oracle Cloud: http://docs.oracle.com/cd/E52319_01/infoportal/opc.html

Where do I get the Cloud Subscription, trial or otherwise?

Please visit - http://docs.oracle.com/en/cloud/get-started/index.html

On the right hand side you will see a link to "Get a Trial or Subscription".  

Materialized Views

 

What are they

 

When building SQL views or query views on an Oracle database, you have the option of implementing a materialized view.

 

A traditional view has what is called a logical existence, but a materialized view has a physical existence.

A materialized view takes the results of SELECT statements and saves the result data to disk. This information is then available without the

need to run the SQL each time.

 

Using materialized views can provide significant improvements in performance, especially when complex SELECT statements are involved to gather the view data. 

 

 

Application Designer

 

Like other PeopleSoft record definitions, materialized views are defined using Application Designer. The data is refreshed on a schedule set

up in the materialized view record definition.  Those users with the Materialized View Administrator role have permission to access the

online page where maintenance of the view (and the refresh schedule) is setup.

 

MaterializedView Definition.bmp

Example of a materialized view definition in the Application Designer. 

 

A refresh schedule is set in the online page Materialized View Maintenance run control page.

 

PeopleSoft developers began utilizing materialized views as of PeopleTools 8.54.  

 

 

Positive aspects

 

Improved performance of queries that summarize job and payable time data, in PeopleSoft's Time and Labor Functionality to Support the

Affordable Care ActPeopleSoft's ACA processing, is one benefit.

Materialized views provide significant improvements in performance when used in Pivot Grids that use infrequently updated data.

 

 

Audit report sections

 

The audit report DDDAUDIT includes sections specific to materialized views on the Oracle platform: MVIEWS-1, MVIEWS-2, and MVIEWS-3.

These queries check for materialized views defined in the Application Designer but not in the database, or if defined in the database but not

in the Application Designer, or if a materialized view is missing a related language record.

 

As of PT 8.55, sections were added to DDDAUDIT for the

MicroSoft Sql Server Indexed View Queries:  IVIEWS-1 through IVIEWS-4.  Sections were also added to the audit report for the Db2 Zos

Materialized Query Tables:  MQT-1 through MQT-4.

 

DDDAUDIT solutions are posted to the PeopleSoft PeopleBooks / Data Management book.

 

 

Other platforms

 

Support for Materialized Views was first provided on the Oracle database platform in PeopleTools 8.54.

In PeopleTools 8.55, this was expanded to include materialized views on the MicroSoft SQL Server database platform, and materialized query

tables on the IBM DB2 z/OS database platform.

 

Additionally, PeopleTools 8.55 will provide the ability to create indexes on materialized views for Oracle, SQL Server, and DB2 z/OS.

 

To learn more

PeopleBooks > PeopleTools 8.55 > Administration Tools > Data Management > Administering Psft databases on Oracle > Using Materialized Views

 

PeopleSoft HCM - Time and Labor Functionality to Support the Affordable Care Act (Doc ID 1987962.1).  Attachments to this document are

specific to the Oracle and Db2 platforms.

Talking about Upgrades IV:  Upgrade Source Images

 

What is it:  A PUM Image, delivered in DPK format, that will install a complete environment* to be used in an upgrade.

The *indicates that the PsHome codeline is not included.  The codeline can be obtained from the virtual CDs posted to the Oracle Support Delivery Cloud (previously called e-delivery). 

 

Used for:   To quickly install an upgrade source environment to be used in an upgrade.

Not used to search for and obtain required-for-upgrade fixes.

 

Where to find:   Links to the DPKs and installation instructions are posted to the PeopleSoft Upgrade Source Images Home Page (Doc ID 1552580.1).

 

Need to install the Source in the classic manner

However, there are some instances where you need to install the upgrade source environment in the 'classic' manner.  This is where you download the virtual CDs from the Oracle Support Delivery Cloud (previously called e-delivery).  This would include situations where:

 

--Can't find the upgrade source for my product

At the time of this writing, there is no upgrade source created for the Interaction Hub 9.1 product (previously called Enterprise Portal). If there is not an upgrade source available, you will need to install the new source environment in the classic manner, from the VCDs found on the Oracle Support Cloud (previously called e-delivery).  Install instructions are attached to the PeopleTools Installation Home Page for your release, and the Applications' Installation or Documentation Home Page. 

 

--Unicode vs. non-unicode

The upgrade source images are delivered in unicode format.  If your environments are in non-unicode format, then use of the upgrade source images is not for you.  Instead, install your new source environment in the classic manner, from the VCDs found on the Oracle Support Cloud (previously called e-delivery).

 

--Multi Language considerations

At this time, the delivered upgrade source images are English-only.

 

On the PeopleSoft Upgrade Source Images Home Page (Doc ID 1552580.1), in the Comments box in the chart, there is text that says:

... This upgrade source image is for ENGLISH-ONLY customers.If you use or require multi-lingual functionality,

then you must install the Demo Database using the classic installation method. See the installation home page for your application for more information.

 

However, there are other upgrades, where the comment box text says:

You can use this upgrade source image for ALL platforms and languages currently certified for the <specific upgrade>.  If you use or require multi-lingual functionality, review Getting Started on Your PeopleSoft Upgrade (Doc ID: 739129.1) for additional instructions that need to be performed on the upgrade source image.

 

...which are...

 

If your Upgrade Source Image is listed as being supported for multilingual upgrades and you are a multilanguage customer, you will need to perform the following instructions to complete your source image for use in the upgrade:

 

1. Install a complete codeline from the CDs, including all of your licensed languages, after installing the delivered upgrade source image.

 

2. Load your non-English licensed languages into the Upgrade Source Image. The delivered upgrade source image is English-only.

The delivered translations are on the same PeopleTools patch and application maintenance level as the source

image, so you will want to load the translations into your database prior to applying any PeopleTools maintenance.

 

--Not using the Oracle database platform 

You can use the upgrade source image, but will also need to download the virtual CD from Oracle Software Delivery Cloud and then install the full codeline for use with your upgrade.

 

Alternatives to Using an Upgrade Source

Can the regular Pum Image (PI) also called PeopleSoft Image, be used for the Upgrade Source?

  1. See E-PUM: Can the PUM Image be Used as SOURCE Database During Upgrade? (Doc ID 1581790.1).

 

Platforms

For the latest upgrades, the images are delivered in formats:

--VirtualBox

--NativeOS - for Windows or Linux

    The  NativeOS downloads are for Linux and Windows sites. 

[The text in doc 1552580.1 says "Advanced Windows" but this was to have been edited to be "Windows".]  This download allows you to apply your PeopleSoft Update Image directly to your OS or a virtualization platform without having to use VirtualBox.

 

Required for Upgrade Patches

Why do the upgrade source images not contain all the required-for-upgrade patches?

Most likely there is a PUM Image (PI) or two released after the upgrade source image's GA date.

The PIA will contain the very latest required-for-upgrade patches created after the upgrade source image was released. 

 

The upgrade source images do not contain the upgrade template; these are delivered in the PI.

 

As of PeopleSoft PeopleTools 8.55, the application upgrade template is delivered within the most current Update Image. You will need to generate the template out of the most current update image since the upgrade template can only be downloaded via the upgrade package. You will need to define the required-for--upgrade packages and create the upgrade template before performing your application upgrade in Change Assistant.

 

Don't see the exact upgrade source image for the upgrade you want to do...?

 

Application differences

--Upgrade source is delivered on (example) PI 9, and you want to go to PI 10.  You can use the Upgrade source, perform the upgrade to PI 9, and then apply patches from PI 10.

 

A poor choice would be to apply PI 10 to the Upgrade Source, and then do the upgrade. The upgrade

was written to go to PI 9, not 10, and scripts or conversion programs might not be successful if you modify the upgrade path.

 

See Upgrade Certification Path on each upgrade home page:    E-UPG Understanding the Upgrade Certification Path section of an Upgrade Home Page (Doc ID 1970917.1).

  

PeopleTools release differences

 

--The minor Tools patches can be applied to an upgrade source.  Use the upgrade source just like

it had been installed in the classic manner.  The instructions are the Tools patch readme.

 

--Full Tools release   

**If your upgrade is certified** on a later PeopleTools release level than the Upgrade Source Image and you want to use the later PeopleTools release to upgrade, then you must upgrade the Upgrade Source Image to that certified PeopleTools release before beginning your upgrade.

 

To find if you upgrade is certified on the later PeopleTools release, locate the Upgrade Home Page for the upgrade desired, then the sub-section Upgrade Certification Path.

 

Can't find anything on MyOracle Support

 

A good place to start is the document Upgrading PeopleSoft? Start Here. (Doc ID 1587686.2), a tabbed document that contains links to all things Upgrade.  To locate the upgrade source images page from this document, navigate to tab PeopleSoft Upgrade >  General PeopleSoft Upgrade Resources,  section PeopleSoft Update Manager.   

 

To find your upgrade's Upgrade Home Page, start from Doc ID 1587686.2, then navigate to your application or PeopleTools > Upgrade Resources, section Upgrade Home Pages.

 

Have a question, want to be sure

 

Visit the Lifecycle Management PSFT Community.   We are glad to field your upgrade questions.

The PeopleTools Delta Change Package

 

What is it?

 

The Define Tools Delta Package component is a wizard used after a PeopleTools upgrade to create a Tools Delta Change Package that contains attributes or objects that were stripped away when the updates were applied to a previous release.

 

Who needs to create and apply it?

 

PeopleTools Upgrading sites who have applied Pum maintenance in the past, to their environment at its previous PeopleTools release.

This would apply to 9.2 applications.

 

How is the Delta Change Package created?

 

During a Change Package create, select Define Tools Delta Package, select From <full PeopleTools release> and To <full PeopleTools release>.

The change package will then be created -- note that it may contain additional bugs not yet applied to the target database.

 

For details, see PeopleBooks > PeopleTools > Change Assistant and Update Manager > Creating and Applying Object Delta Change Package.

 

What about application objects?

 

In the PeopleTools 8.55 upgrade documentation (posted to PeopleSoft PeopleTools 8.55 Upgrade Home Page (Doc ID 2070772.1)),

see task 4-10 Updating Application Objects. This chapter consists of wrap-up tasks, and applying the Tools Delta Package may be one of them as well as adding application objects.

 

The task instructions start out:  (asterisks are added for emphasis)

 

If a site has recently completed an application and PeopleTools upgrade, there **may be** additional fixes to be applied to your database to ensure compatibility of your application with the latest PeopleTools release.

 

This can mean application objects -- see document PeopleTools 8.55 Upgrade Impacts for PeopleSoft 9.2 Applications (Doc ID 2067985.1).

The PeopleTools Upgrade documentation also points to Creating and Applying Object Delta Change Package for PeopleTools, a section in the

Product documentation  for PeopleTools 8.55 > Change Assistant and Update Manager.  .  

 

FAQ

 

Q:  We have just upgraded People Tools from 8.53.10 to 8.55.04.

 

       As part of the upgrade process, we are generating the Tools delta change package against our upgraded database.

      Why is there no object delta change package generated?

 

A:  From your situation description, because the images used in previous maintenance were based on PeopleTools 8.53,

      they would not contain 8.55 objects. So there would not have been any 8.55 objects removed when updates

      were applied to the target database. Since there were no objects removed, there would be no objects to add back after

      the target was upgraded to PeopleTools 8.55.

 

Q:  If the target environment is on PT 8.53, and updates have been applied from a PUM image created with PT 8.55, is that different?

 

A:  Yes. When using an image based on PT 8.55 to apply updates to a target based on 8.53, the PT 8.55 specific objects would have

      been stripped out when applying maintenance to 8.53.

      If then you upgraded the 8.53 environment to 8.55, then the "Generate Object delta package" would bring back those

      previously removed objects.

 

Q:  Would like to know why we need to create and apply a Tools Delta Change Package if we are upgrading from PT8.53.26 to PT8.55.07.

      Does this preserve the old Ptools objects? Does this have anything to do with our customization of Tools objects?

 

A:  If you have applied maintenance that was created using PT 8.54 or 8.55 then any objects or fixes that had 8.54 or 8.55

     as pre-requisites would not have been applied to your environment.

 

        1. For those bug fixes that have a hard requirement of a higher PeopleTools release the bug fix would not be applied at all,

             so if you did a “All Updates Not Applied” change package those would now be included.

        2. However, those that had a soft requirement (meaning they would be still applied but any 8.54 or 8.55 objects would be stripped out of

             the fix) would have been applied so if you did    a “All Updates Not Applied” change package those would not show up

             since they have already been applied. The Tools Delta Change Package brings back those 8.54 and 8.55 objects that were previously stripped out.

 

Example scenarios

 

Example 1

If your environment was on PT 8.54, and you have applied application patches from a PUM image created on PT 8.55. 

There may have been attributes of objects stripped away, meaning, removed from the package to be applied to the target.

This is because those objects are unique to PT 8.55 and would not have a table for storage in PT 8.54.

 

Later you upgrade to PT 8.55.

Part of the upgrade tasks is to go back and create the PTools Delta Change Package to see if there were items not applied at that time.

If there are objects in that package, then it can be applied.  Your environment would then no longer be missing those objects.

 

If there are additional instructions solely for <your application> at the new Tools release, those should be followed as well.

 

Example 2

Say you were on PT 8.53 and upgraded the PeopleTools to PT 8.55. 

During this upgrade, there are no objects removed and not applied.  The PTools upgrade is completed, it is a PTools Only Upgrade.

Later you go to apply maintenance from a PUM Image created on PT 8.55, applying this to the newly upgraded PT 8.55 environment.

There is no need to create the PTools Delta Upgrade Change Package at this point. 

 

Example 3

We are at tools 8.53, HCM 9.2 PUM 006 and want to upgrade to 8.55 PUM 018.

Do we have to upgrade to tools 8.55 first then update to Pum image 018?

 

No, but if you plan to do both, it would make more sense to do the PT 8.55 upgrade first.

 

Why:  If you don’t, then objects and bug fixes that have a PT 8.55 requirement would not be applied.

You would then have to create and apply a PTools Delta Change Package, in order to have all the PT 8.55 objects on your environment.

 

Clarification of terms

 

"Tools delta package" is a step that need to be accomplished  after the PeopleTools upgrade is completed.

This redelivers bugs you have already applied, in order to get the bits of objects that were stripped out on the initial apply,

due to a PeopleTools limitation.

 

"All updates not yet applied"  is maintenance that can be applied at any time. This can include tax updates or a wide variety of application updates, fixes, or new features. 

 

"PeopleTools Upgrade Change Package"  is different than the Delta Change Package discussed here.  The Upgrade Change Package contains the upgrade template

and upgrade documentation.

 

Note that applying the PeopleTools Upgrade Change Package is not needed if a site is using DPK-deployed PeopleTools on Windows or Linux. 

 

For further information

 

Refer to PeopleBooks Product documentation for PeopleTools 8.55: Change Assistant and Update Manager, Upgrading PeopleTools, Creating and Applying Tools Delta Packages.

A link to this PeopleBooks section can also be found on the MOS PUM Home Page (Doc ID 1641843.2) section Learning about PeopleSoft Update Manager / What

is PeopleSoft Update Manager / PUM Overview.

A search in MyOracle Support may not provide the most useful results, if the input libraries searched are incomplete.

 

Are you searching on an error or problem that might have been previously reported?  A problem that might be a known issue?

For best search results,  include the Bug database.

 

SearchBug.bmp

 

 

In the search above, the Knowledge Base, the MyOracle Support Communities, and the BUG database are selected as input libraries.  

 

Other useful optional input libraries are:

 

--The archive knowledge base

--Documentation (=PeopleBooks)

 

SearchBug2.bmp

    searching in 3 libraries:  it is a known issue?

 

The search can be made more selective by entering Product, Release, and a date range of last update.

 

You can also do this by using the product line breadcrumbs that appear with each result. Just click on any one of the

breadcrumbs to filter the result set to show documents only for what you selected:

 

Snap11.jpg

 

The more specific your search, the more likely that the search results would include the most useful items.

Or that the best results would appear near the top of the result list.  

 

In the example above, a  PowerView is utilized.  PowerViews can be used to narrow down a search to the Product Line.

They can be set for use as the default search setting.

PowerView in Use.bmp

image002.png


Is my Application supported with the newest PeopleTools release?

 

Many times a customer site will want to stay on their current application release, but upgrade the PeopleTools to the most current release available.

An example would be staying on FSCM 9.1 but upgrading to PeopleTools 8.55. 

 

Will the current application release be supported on the newest PeopleTools release?

 

An easy way to find this information is to follow the steps and screenshots in document  E-UPG: PT8.4x, PT 8.5x: What Versions of PeopleTools Will Your Application run on? (Doc ID 1915747.1).  MOS Certifications may not specifically say:  Yes, FSCM 9.1 is supported on PTools 8.55. But the certification notes will show: 

 

PeopleSoft Financials and Supply Chain Management 9.1 can be run on PeopleTools 8.50 or higher.

 

Other considerations: Platform releases

 

If you upgrade to PeopleTools 8.55, then you may need to modify the releases of other products in your environment. Perhaps this is what is triggering the upgrade to begin with.

 

The database release may need to be modified - for example,  upgrading to Oracle 12.1.0.2.0.  This is one of 2 Oracle database releases currently supported for PT 8.55.   Would this release of Oracle work successfully with FSCM 9.1?   Note that it is the PeopleTools release that is tested and certified for use with the Rdbms release.  Yes, Oracle 12.1.0.2.0 is certified with PeopleTools 8.55.

 

You would want to verify that all software components in your environment (Operating Systems, Databases, Desktop Applications, etc.).

would be certified with PT 8.55.   A good place to start would be the Tech Update - Main Page (Doc ID 764222.1), found on MyOracle Support. 

Here you can determine if a third party product has reached end-of-life in general, or is no longer supported as of a specific PeopleTools release, or is newly supported.   Examples would include Tech Update – Oracle Retires Support for Crystal Reports (Doc ID 1927865.1) or Oracle Certifies Microsoft Windows 10 for PeopleSoft (Doc ID 2161227.1).

 

Sustaining Support

 

The certification notes continue:

 

For application releases that are on Sustaining Support, see My Oracle Support (Doc ID 1348959.1) for important upgrade considerations.

This document is titled Lifetime Support Summary for PeopleSoft Releases.  See section PeopleTools Considerations for PeopleSoft Applications on Sustaining Support, which says:

 

PeopleSoft Application releases can be run on the PeopleTools version that the application initially shipped with, up through and including

the latest available PeopleTools release

 

What about the NEXT upgrade?

 

Running an application release on Sustaining Support, if upgraded to a newer PeopleTools release, will impact the next Application Upgrade that is attempted. The application upgrades are written for a specific Peopletools release.  This information is found on each Upgrade's Home Page, shown in the Upgrade Path Certification chart.

 

  If you upgrade past the PeopleTools release that such an upgrade was written for, and in the future,  attempt to upgrade with that combination of products, there will be additional tasks to be completed in order for the upgrade to run.  These are generally modifications to the upgrade templates.  Required changes are listed in Upgrade Editing Instructions in the Lifetime Support Summary for PeopleSoft Releases (Doc ID 1348959.1).  

Talking about Upgrades III

Latest installment - Upgrade top topics


1) Upgrading either of the Application or PeopleTools, without upgrading the other.

      Is this certified?  and How to go about finding this information?    

    

        Example Upgrade question A.   Can I upgrade HCM 9.0 to 9.2, but stay on PTools 8.54?

            So, the questions are really, is HCM 9.2 supported on PTools 8.54?  And is the App-Only Upgrade a supported upgrade?

            On MyOracle Support > Certifications > Certification Search, enter

            Product = PeopleSoft Human Capital Management, Release = 9.2, Search

            In results, see Certification Notes, which say PeopleSoft Human Capital Management 9.2 can be run on PeopleTools 8.53 or higher.

          

            Next, see PeopleSoft Human Capital Management Upgrade Home Page (Doc ID 1959519.2) tab HCM 9.0 to 9.2 PI 9.

            Find section Change Assistant Template, which contains the template for app-only upgrade 9.0 to 9.2.  

 

            Can an Upgrade Source image be used for the HCM 9.0 to 9.2 upgrade?

            See PeopleSoft Upgrade Source Images Home Page (Doc ID 1552580.1), HCM section, there is an upgrade source for the upgrade from

            HCM 9.0 to 9.2 PI9, written on PTools 8.54.03.  The comments there say it is supported for all database platforms, for English-only sites.

            Additional steps are required for a multi-language environment.

 

       Example Upgrade question  B.    Can I upgrade PTools to PT8.55, but stay on Application FSCM 9.0?

 

        On MyOracle Support > Certifications > Certification Search, enter

            Product = PeopleSoft Financials and Supply Chain Management,  Release = 9.0,  Search

            In results, see Certification Notes, which say PeopleSoft Financials and Supply Chain Management 9.0 can be run on PeopleTools 8.48 or higher.

            The Lifetime Support document (Doc ID 1348959.1) is also referenced.  A read of the Lifetime Support document shows that FSCM 9.0 is now on Sustaining 

            Support.     There is also text there:

                     PeopleSoft Application releases can be run on the PeopleTools version that the application initially shipped with, up through and including

           the latest available PeopleTools release.  Oracle recommends using the latest available PeopleTools release. 

 

           The Lifetime Support document contains additonal information, that should be reviewed, in section

           PeopleTools Considerations for PeopleSoft Applications on Sustaining Support.

 

 

2) Installing the new Upgrade source environment, which is delivered in DPK (deployment package) format

 

           The best approach here is to start with reading the DPK documentation beforehand.

           The variety of documentation includes 

              --extensive installation documents:

                  PeopleSoft Deployment Packages for Update Images Installation (PeopleSoft PeopleTools 8.55)

                       (link is on the PUM Home Page Doc ID 1641843.2)

                  Understanding PeopleSoft Deployment Packages for Update Images (PeopleSoft PeopleTools 8.55)

                       (link is on the PUM Home Page Doc ID 1641843.2

              --Quick Start Reference for PeopleSoft Update Images on PeopleTools 8.55 (Doc ID 2101192.1)

              --E-DPK PT8.55: Frequently Asked Questions about Deployment Packages (DPKs) (Doc ID 2127715.2)

              --and the  Lifecycle Management PSFT community:  what have others run into?

                

                   

3)  Just finding upgrade materials

  

      Examples:  Where are the release notes for the new release?

                            Where is the upgrade template, the upgrade documentation? 

 

       The best way to find things is to start from document Upgrading Psft? Start Here (Doc id 1587686.2).   This doc can be bookmarked, then

       you can alway locate the upgrade materials.

 

 

4) Certification of third-party products.

 

     To find this information easily, find and bookmark the Tech updates index:

                Tech Update - Main Page (Doc ID 764222.1)

     As a new product release is certified with the PeopleSoft products, an entry to a separate document is made here.

 

    or review E-CERT PT8.55: Certification Hot Topics(Doc ID 2093951.1)

                       E-CERT PT8.54: Certification Hot Topics(Doc ID 1916684.1)

 

    Other reference documents:

    Updated monthly, see the Top Solutions - PeopleTools Installs and Upgrades: Certification, Change Assistant, Database Specific, DPK, Install, Maintenance, PUM, Setup Manager, Testing Framework, Upgrade (Doc ID 1481826.1)

   E-UPG Master Note: Upgrade Issues with PeopleTools 8.55 (Doc ID 2131756.1)

   E-UPG Master Note: Upgrade Issues with PeopleTools 8.54 (Doc ID 1928294.1)

Learning about the Oracle Cloud

 

Oracle has announced that customers using PeopleSoft, e-Business Suite, and JD Edwards EnterpriseOne can run non-production workloads on the Oracle Compute Cloud Service. You have the ability to move existing Development, Test, Training, Demo and Conference Room Pilot environments to the Oracle Compute Cloud or use the Oracle Compute Cloud for an upcoming Oracle Applications Project.

 

Oracle customers who already own a license to PeopleSoft applications may use the Oracle Cloud to host instances of their licensed applications.

 

There are many scenarios where you might benefit from using Oracle’s Compute Cloud with your PeopleSoft applications:

 

Demo instances of the latest PeopleSoft application images (PUM Images) in order to explore the latest features and capabilities.

 

Test instances of YOUR PeopleSoft database.

 

Development and Testing environments,  accessed by your developers using Windows Remote Desktop.

 

 

 

Start here:  PeopleSoft Information Portal

 

(Choice 1)

Navigate to Concepts > PeopleSoft on Oracle Cloud

 

What's there?

 

--An extensive FAQ

 

--Video:  PeopleSoft Talk with Marc Weintraub:  PeopleSoft on Oracle Cloud feature Jeff Robbins

 

--Sections on How You Can Use PeopleSoft on the Oracle Cloud:

  Demo, Development, and All Cloud

 

--Get Started section:  red papers

 

--Tutorial: Deploying PeopleSoft Applications on Oracle Compute Cloud Service Instances

 

--Step-by-step guides:  Migrate a PeopleSoft Installation to Oracle Compute Cloud Service

 

                        Performing a PeopleTools Patch Update on a PeopleSoft Environment Running in Oracle Cloud

 

                        Performing PeopleTools-Only Upgrade on PeopleSoft Environments Running in Oracle Cloud

 

                        and more.

 

 

Or, for (Choice 2)

Navigate to Concepts > PeopleSoft Cloud Architecture

 

for an overview and then Read the Full Story.

 

Cloud.bmp

Setting up an Upgrade Job:  Application 9.2 and PeopleTools 8.55+

 

 

Separation of PeopleTools and Application Upgrades

In the past, Application-Only upgrades were available for those sites wishing to change the release of their Application but not the PeopleTools.  Another option available was a combined Application and PeopleTools upgrade.

 

Application Only Upgrades - the new normal

Starting with PeopleTools 8.55, Oracle will not be delivering templates combining an application plus PeopleTools upgrade.  We will deliver the Application-only upgrade template.

The PeopleTools upgrade will be delivered separately from the Application upgrade.

 

Change Assistant can generate jobs

PT 8.55 Change Assistant can generate a series of upgrade jobs:

--the first is the PeopleTools Upgrade

   and

--the second part is the Application Upgrade.

 

Actually, three jobs can be generated.  The first would be the PeopleTools upgrade, the second the Required-for-upgrade patches (if selected), and third, the Application Only upgrade.

 

In order for this to happen, the PeopleTools Upgrade change package needs to be downloaded from MyOracle Support into the same directory where the application upgrade package is located.

 

The template jobs can be run sequentially so that it is virtually the same as an Application and PeopleTools Upgrade combined.  A huge benefit is the required-for-upgrade job that, if selected to be generated, will run after the PeopleTools upgrade and before the Application upgrade.

 

HCM, ELM, CRM, and Campus upgrades

These applications now have their upgrade templates delivered in PUM Update Images.

Upgrading customer sites will generate the Application Only Upgrade change packages from the  Update Images.   (Update Images shouldn't be confused with Upgrade Source Images.)

 

As of PeopleTools 8.55, the application upgrade template is delivered within the most current Update Image. You generate the template out of the most current Update Image since the upgrade template can only be downloaded as an upgrade package. You will define your upgrade packages in PUM, and create your upgrade template in Change Assistant, before starting the application upgrade.

 

While you need to generate your upgrade template from the most current update image, you can ONLY upgrade to the certified update image.

 

 

How to find the "certified update image"?  This is the defined upgrade to a specific update image:

 

UpgradeTemplates2.bmp

   The highlighted tab shows the ELM application's latest certified update image, which is 9.2 PI12 for the 9.1 to 9.2 upgrade.

 

 

For more details on the steps to generate the upgrade package and template, see the video tutorial - PeopleSoft 9.2: Creating the PeopleSoft Change Package and Template.

This is posted to any of the Upgrade Home Pages below,  in section Upgrade Packages (Change Assistant templates):

     PeopleSoft HCM Upgrade Home Page,  (Doc ID 1959519.2)

     PeopleSoft Campus Solutions Upgrade Home Page (Doc ID 2078564.2)

     PeopleSoft CRM Upgrade Home Page (Doc ID 1961844.2)

     or

     PeopleSoft ELM Upgrade Home Page (Doc ID 1962959.2)

 

 

Including PeopleTools

If you wish to generate an Application and PeopleTools upgrade job, Change Assistant PT 8.55 can do this for you if the PeopleTools Upgrade change package has been downloaded from the PTools Upgrade Home Page on MyOracle Support, and placed into the same directory where the application upgrade template is placed.

 

PToolsPkg.bmp

    Example showing the PTools Change Package for upgrades to PT8.55 from PeopleTools 8.55 Upgrade Home Page (Doc ID 2070772.1)

 

 

FSCM upgrades, the exception for now

As of now, the FSCM Upgrade Template has not yet been delivered in an Update Image.

 

In the FSCM 9.1 to 9.2 Image 11 upgrade,  upgrading sites will need to download the Application Only Upgrade template from the upgrade home page, PeopleSoft Financials and Supply Chain Management Upgrade Home Page (Doc ID 1963697.2).

 

UpgradeTemplates.bmp

   Only template available on the FSCM Upgrade Home Page 1963697.2 for upgrading to FSCM 9.2 / PT 8.55

 

 

We expect the FSCM upgrade template to be delivered in the Update Image as of FSCM 9.2 Image 19.

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see https://community.oracle.com/docs/DOC-1022508 for instructions.