Last updated on AUGUST 21, 2017
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
This is an upgrade issue with all upgrade paths.
In the 'Create and Apply the "Required for Upgrade Change Package" to new release demo (upgrade source image)' step, upd17171200_upg.doc states that 17171200 is to be applied after importing the UPGOPT project in step 2-1 but before building the project in 2-1-2.
1. Login to FSCM 9.2 Image 5 (via the web), navigate to PeopleTools > LifeCycle Tools, and review the bug fix 17171200. There are 4 DataMover scripts and 1 Upgrade Query definition.
2. Navigate to the 8.53 PS_HOME\MAINT folder and find, deployed (as part of the Required for Upgrade Change Package) the four datamover scripts, and the same Word document outlining the instructions. Four scripts have been reviewed: two are export and two are import scripts. upd17171200_01_exp exports PROJECTDEFN WHERE PROJECTNAME = 'UPGOPT'. upd17171200_02_exp exports PROJECTITEM WHERE PROJECTNAME = 'UPGOPT' AND OBJECTVALUE1 = 'UPG_APY01'. The two import DMS scripts utility UPDATE_DUPS and import those two .DAT files.
Therefore, one would need to run the two export DMS scripts in a database that has UPG_APY01 in the UPGOPT project to create my DAT files. Then one can import them into the Target (ex. 8.9) environment after importing the UPGOPT project there.
3. Login to Copy of Production Target (ex. 8.9) database and import, from file, the UPGOPT project from the 9.2 PS_APP_HOME\projects\FSCM89 folder. They validate: (a) the project imported; and (b) UPG_APY01 doesn't exist in the Target (ex. 8.9) - yet.
4(a). When the two export scripts are run against 9.2 Upgrade Source Demo database since it was just patched with Required for Upgrade Updates. Each script exported 0 rows.
4(b). When the two export scripts are run against the FSCM 9.2 Image 5 database (PUM "source"). Each script exported 0 rows.
5. Log into both 9.2 Images via App Designer and found: (a) the UPG_APY01 query definition exists in both databases, but (b) the UPGOPT project doesn't exist in either.
17171200_01_exp.dms exports PROJECTDEFN WHERE PROJECTNAME = 'UPGOPT', and 17171200_02_exp.dms exports PROJECTITEM WHERE PROJECTNAME = 'UPGOPT' AND OBJECTVALUE1 = 'UPG_APY01'. If the UPGOPT project isn't in the database the scripts will export 0 rows.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms