Compare Reports

PeopleSoft Compare Reports:

• The compare reports are critical tools for the Fit/Gap analysis and determining the effort to re-apply/re-develop customizations.
• The PeopleSoft Compare Reports provide a comparison of PeopleSoft delivered functionality (vanilla) at the new release level to a client’s copy of production.
• The compare process is executed to identify the object and system data differences between current production and new release levels.
• The purpose of the compare report is to identify which customizations, objects and system data to upgrade to the new release level.
  
• The technical team will run the compare process and involve the client/functional team in the analysis to make the appropriate business decisions.
  
• When you review the compare reports always look at the following combinations and take the appropriate action.

Source	Target	Action
Unchanged	Changed*	Keep Target
Changed	Changed*	Copy and re-apply customization
Absent	Changed*	Keep Target
All other		Copy

Generating and reviewing the compare reports valuable insight to the level of customization.

Approach to Compare Report Analysis and Customization:

In a typical upgrade, the following approaches are taken to re-applying customizations:

• Customizations are carried forward where no PeopleSoft conflict exists. These customizations will require careful testing to ensure proper results.
• Customizations where PeopleSoft conflicts exist will be replaced by delivered PeopleSoft objects. If it is determined that these customizations are required in the new release they will need to be reapplied and tested to ensure proper results.
• Most client PeopleCode modifications are typically replaced where PeopleSoft conflicts exist. This is done to ensure the integrity of the new release and requires that any client modification will need to be reapplied manually.
• Currently there is no delivered PeopleSoft process for comparing Message Definitions, SQR, SQC, and Crystal Reports. Modifications to these delivered PeopleSoft components will need to be manually identified and included in the upgrade process.
• Customizations to components of Process Scheduler (Process Types, Process Definitions) will be identified through the compare process and included in the upgrade process.
• Custom indexes for performance reasons will be evaluated during the upgrade process to determine appropriateness of the index in light of key structure and data distribution changes. All effort will be focused on ensuring no performance degradation.
• Modifications required for external interfaces will be identified through the analysis and design process included in the upgrade project.

Compare Report Error

Error while running the compare report:
Records Application Upgrade Compare started: 2007-11-22-10.50.37 (62,6)
System Error : SQL error. Stmt #: 6962 Error Position: 0 Return: 1 - End of fetch (SQLSTATE PS001) (62,16)
System Error : RUN RECSTATS FOR TABLE (PSPROJECTWORK,LOW) (62,16)
Records Compare Report Created : c:\temp\HC9_MP1_ML\Upg00Records.prt (75,9)
Internal Error: invalid transaction handle instance passed from SamDestroy 0: 70 vs 0

Resolutions:
1. In compare report window UNCHECK the Update Project Item/Child Status option .
2. In configuration manager - CHECK the Disable DB Stats box