Specific Phases for ZDO

In addition to the phases of a standard update procedure, the following phases are specific to ZDO:

Phase	Purpose	Comment
PREP_CONFIGURATION/SUMASK_ZDO_CONFIGURATION	Configuration of ZDO	The administrator is asked if a system backup needs to be performed during the system restart. For more information, see Backup Strategy for ZDO .
RUN_RSPTBFIL_ZDM_CHECK_BW	SAP BW Check	Checks for an active SAP BW system. As a result, the following log messages are possible: NO_BW_SCOPE: `System scope is NO_BW_SCOPE, ZDO is supported` ANALYTICS_ONLY: `System scope is ANALYTICS_ONLY, ZDO is supported` DATA_WAREHOUSE: `System scope is DATA_WAREHOUSE, ZDO is not supported, see SAP note 2707731` For more information, see Error in Phase RUN_RSPTBFIL_ZDM_CHECK_BW.
PREP_GENCHECKS/PARRUN_ZDO_CONSISTENCY_*	ZDO consistency check for ABAP dictionary objects, database objects, SLT logging tables, and SLT triggers	The purpose of the check is to detect inconsistencies already in the original system at an early stage as part of the General Checks module. For example, ZDO can only handle database indexes that are defined in the data dictionary. Undefined indexes disappear in the target release when the table is to be cloned. Such indices must be removed directly or defined in the data dictionary using the transactions SE11 or SE14. See also in chapter Known Issues the section Error in Phase PARRUN_ZDO_CONSISTENCY_CHECK or RUN_ZDO_CONSISTENCY_CHECK_POST With Regard To The SLT Setup.
MAIN_SHDIMP/SUBMOD_SHD2_RUN/GENKEYTRACE	Test import for ZDO	Preparation step required for ZDO table classification.
MAIN_SHDIMP/SUBMOD_SHD2_RUN/CHECK4NOTES_TOOL_SHD2	Implementation of SAP Notes in the shadow system	Checks for SAP Note corrections required by SUM in the shadow system. These SAP Notes belong to the target release.
MAIN_SHDIMP/SUBMOD_SHD2_RUN/SUBMOD_LC4BRI_PREP/RUN_RSPTBFIL_ZDM_CLASSIFY	Table classification to calculate the handling of tables during the ZDO procedure	In phase RUN_RSPTBFIL_ZDM_CLASSIFY, tables are classified as follows on how they are handled during the upgrade. Share: Tables are not affected by the upgrade Clone: Tables are populated with new or additional content Read Only: Tables to which complex structural changes are made A possible business impact can be estimated with the Impact Analysis.
MAIN_SHDIMP/SUBMOD_SHD2_RUN/SUBMOD_LC4BRI_PREP/RUN_IMPACT_ANALYSIS_ZDO	Impact analysis by SUM in batch mode	Analysis of the table classification impact on productive usage statistics regarding tables that are modified by after-import methods. From this phase on, the dialog version of the impact analysis can also be used. For more information, see Impact Analysis Usage.
Start phase: MAIN_BRISETUP/REQ_USER_ROLLOVER_PREP Completed with phase: MAIN_BRITRANS/REQ_USER_ROLLOVER_FINAL	Rollover to bridge subsystem	From this point in time, tables classified as Read Only become read-only for the bridge subsystem.
MAIN_SWITCH/EU_SWITCH_ZDM	Smart switch	SUM renames the original tables classified as Clone tables.
MAIN_SWITCH/SUBMOD_LC4BRI_EXEC/SQLRUNTASK_FDCT_TRANSFER	Fast data copy transfer	Creation of live clone tables.
MAIN_NEWBAS/SUBMOD_ZDO_REPLAY/RUN_ZDOREPLAY_REPLAY_LKPM	Replay phases	Replay of the changes created during the runtime of phase SQLRUNTASK_FDCT_TRANSFER.
MAIN_POSTPROC/SUBMOD_BRIDGE_POSTPROC/RUN_PREP_CHECK_ILLACCESS	Illegal access check	Checks for illegal table access from the upgrade subsystem.
Start phase: MAIN_POSTPROC/SUBMOD_BRIDGE_POSTPROC/REQ_USER_ROLLBACK_PREP If you have chosen in phase SUMASK_ZDO_CONFIGURATION that a backup has to be requested, you are prompted in phase MAIN_POSTPROC/SUBMOD_BRIDGE_POSTPROC/REQ_ZDO_SYSTEM_BACKUP to perform the complete system backup Completed with phase: MAIN_POSTPROC/SUBMOD_BRIDGE_POSTPROC/REQ_USER_ROLLBACK_FINAL	End of bridge subsystem	Roll back to the productive system and system restart. The target release becomes active after the system restart.