Using the Impact Analysis Tool to Determine the Impact of a Simplified Upgrade
Beginning with Release 9.2 you can choose to perform a Traditional Upgrade, which replaces all objects, or to perform a Simplified Upgrade, which only replaces a subset of objects on your existing Applications release. You can use the Impact Analysis Program (P96711) to create an Impact Analysis Report (R96711) to get a comprehensive analysis that details the impact of a Simplified Upgrade. For a description of the two upgrade processes, refer to the section of this guide entitled: Understanding Upgrade Types.
The impact analysis compares the objects in the manifest table (F96400) with Electronic Software Update (ESU) and Object Librarian (OL) tables to determine if the objects should be replaced or merged with or without custom modifications as defined by the spec merge rules.
This report is run against the source release environment. In addition to using the manifest, the report also accounts for objects that the user has specifically marked as modified (to be merged). The report then provides details for impacted objects in the supported target "from releases" to those that will reside in the "to release" (Release 9.2) as they will be delivered by the Simplified Upgrade.
The results of the Impact Analysis Tool provides a list of objects that will be impacted by the Simplified Upgrade process.
This section describes these tasks: