PRE-UPGRADE Adjust Start Profile Before you start the upgrade, add the SAPSYSTEM parameter to the start

profile o f you system. Apply SAP Note to Avoid Error During Reset We recommend to apply SAP Note 1518145 before starting the upgrade yet in your system as part of the corresponding Support Package). vents an error that can occur when you reset the upgrade procedure eprocessing roadmap step. Without this note, some tables that need during the reset cannot be deleted. (if it is not This note pre during the Pr to be deleted

Phase PARCONV_UPG During the upgrade, the phase PARCONV_UPG can fail with an error during the crea tion of secondary indexes. In the conversion log files of the form NCONV..<SID> the following erroris reported: Index " " could not be created completely in the database To solve this problem, repeat the phase. To avoid the error in advance include t he support packages mentioned in SAP Note 1468467 in the upgrade procedure. POST-UPGRADE Missing authorization in upgrade wizard When using the wizard for automated processing of selected follow-up activities, you get the following error message: Error: BAPIRET2 SWF_XI_ADAPTER 203 Error in BPM - Autocustomizing. Role SAP_XI_BPE_SERV_USER is missing an authorization. To fix this, refer to SAP note 1580460. This is no longer valid with support pac kage stack 4. Reconfiguration of User Reauthentication If you have performed the upgrade from a source release lower than SAP NetWeaver 7.0 EHP1, you have to reconfigure the user reauthentication after the ugprade. As of SAP NetWeaver 7.0 EHP1, there is a new implementation of the user reauthen tication and it is not active until you have configured it.For more information, see SAP Note 1532874. GPAL WebDynpro application are not loaded correctly after Upgrade to EP730. Therefore, you must apply Note 1531137 after the upgrade has finished. BW Only: DataSource Issues after Upgrades from NW 7.0 A number of issues may occur after the upgrade from SAP NW BW 7.0 in the context of DataSources. To view the list of these issues and the procedure how to solve these, see SAP Note 1489064.