Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

PeopleTools and Lifecycle Management - PSFT (MOSC)

Change Assistant warning: Status of Change Package: Not Updated

Nov 25, 2019 4:07PM edited Feb 13, 2020 1:02PM in PeopleTools and Lifecycle Management - PSFT (MOSC) 7 comments

I see that my Dev pass updated the change package per UpdateChangePackage_CA.log:

Updating Change Package with new Project.Renaming PeopleSoft Change Package.Renaming file from \ca_work\dwn\updZ_PUM015.zip to \ca_work\dwn\updZ_PUM015.zip_2019_11_21_12_13Creating Modified Change Package Information file.Setting UpdatedChangePackage to true in ChangePackageProperties.xml.Creating Modified Change Package file.

...and now that I am running my QA pass, I see that the new and previous packages exist in my download directory:

Directory of \ca_work\dwn11/25/2019  02:39 PM    <DIR>          updZ_PUM01511/25/2019  02:39 PM         5,939,218 updZ_PUM015.zip11/21/2019  11:39 AM         5,939,212 updZ_PUM015.zip_2019_11_21_12_13

...so does that mean that it is OK for me to ignore this warning and continue on?

Tagged:

Maintenance & PUM

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month