“When is the next PeopleTools release going to be generally available?”


Oracle’s customer support team cannot comment on software that is not yet released, including release dates.

See E-INST: When Will the Next PeopleTools Be Released? (Doc ID 1362860.1). 


You may reference 1966243.2 - PeopleSoft Planned Features and Enhancements.  Or, check back, looking for Oracle's PeopleSoft PeopleTools 8.55 Release Notes.


“We have an older application (FSCM9.0) that is currently using PT 8.51. Can we upgrade this to PT 8.54?”


This application release level is now on Sustaining Support. 

If you review our document Lifetime Support Summary for PeopleSoft Releases (Doc ID 1348959.1), you’ll see the  statement:


New PeopleTools releases are not tested with application releases on Sustaining Support, however we expect PT releases to be largely backward compatible.  If an issue is found within the PT version itself and can be replicated with a current application release (one that is on Premier or Extended support), Peoplesoft will resolve the problem according to the PT support policy.  If the issue is exclusive to the older application release, a new fix will not be delivered since the application is on sustaining Support.


See the PeopleSoft PeopleTools 8.54 Upgrade Home Page (Doc ID 1915618.1), Certification Path section, you’ll see that the upgrade is written to accommodate  any 9.0x or higher PeopleSoft application or a PeopleTools-only application, upgrading to PT 8.54.02+;   or any 8.4x, 8.8x, or 8.9x PeopleSoft application on PeopleTools 8.4x or higher patch level upgrading to PT 8.54.14+. 


The really important thing to consider is that you will need to use a certified platform for the PT 8.54 level.  Verify each product by checking the MOS / Certifications / certification search where Product = PeopleSoft PeopleTools and Release = 8.54 (search).


Also, refer to E-UPG: PT8.4x, PT 8.5x: What Versions of PeopleTools Will Your Application run on? (Doc ID 1915747.1)


“We’d like to clarify the different PS Homes used in a PeopleTools Only Upgrade. And, what to do with them afterwards?”


In the PeopleTools only upgrade to 8.54.nn, the instructions have you install a separate PeopleTools PS_HOME for the purpose of the upgrade.  (See document Getting Started on your PeopleTools Upgrade posted to the PT8.54 Upgrade Home Page (Doc ID 1915618.1).


This is the upgrade ‘source’ environment.  The upgrade proceeds, and the new codeline from Source is applied to Target, resulting in your Target at the new PTools release level.    What happens next: 


If your site is using a de-coupled installation scenario, where the application code is in PS_APP_Home, and the PeopleTools code is in PS_Home, then adjust your pathings and configuration manager to the new release PS_Home.   


If your site is using a classic installation scenario, where the application code and the PeopleTools code are both in the PS_Home, then you can manually copy the new release PS_HOME (the Target of the PTools Upgrade, containing only tools) over the old release PS_HOME (containing tools + app). This will only replace the PeopleTools files.


“We’re using a PUM Upgrade Image in our upgrade.  What Ps_Home codeline should be used to locate the upgrade script files?”


Using an Upgrade Image as the Source environment can be a great time-saver, when preparing for an Application-and-PTools upgrade.

However, don’t forget to also install a new release codeline to use as the Source Ps_Home -- using the software media available on the Support Delivery Cloud website (previously called edelivery.oracle.com.)


“We want to take a backup of the New Release Demo and we are using an Upgrade Source image as the New Release Demo.  How does that work?”


The PUM Upgrade Source Image(s) could be backed up/restored one of two ways:

1. A snapshot of the entire Virtual Image could be taken.

2. The Image could be re-imported/recreated. The Image is a delivered virtual environment. Recreating it is no different than restoring it from a backup.

If a PUM Upgrade Source Image has had required-for-upgrade patches applied to it, then a backup/snapshot should be taken after these patches were applied.


Otherwise the Image could be recreated from scratch, and with the required-for-upgrade patches then being re-applied.