Title
Generation and Adjustment of Flow Definition during Downtime-MinimizedMigration from CRM 2.0x to CRM 3.0

Purpose
You can turn on the delta collection before making a system copy ofyour CRM 2.0x system. With a turned on delta collection you can extractchanged data from the CDB and transfer it to your CRM 3.0 system oncethe the system copy has been upgraded to CRM 3.0.
You can change the flow definition to migration mode. This turns offany non-migration and mobile application specific components. The flowdefinitions will consist exactly of migration service and datasynchronization services (CDB service, replication service, outboundadapter, ...) excluding R/3 Adapter services and CRM Serverapplication services.

Prerequisites
If you created your own BDoc structures, you must enter the name ofeach supported BDoc type in table MIG_BDOCTYPE.
BDoc types that are not registered in table MIG_BDOCTYPE will beignored. If you need to migrate unsupported BDoc types, you must createmapping services on a project basis.
This function does not support the R/3 transport mechanism. Thereforeyou must adjust flow definitions in test and productive systemsindividually.
When choosing CDB collection, you must have started with an existingstandard flow definition. The option CDB collection changes an existingflow definition.
When choosing Link to Productive CRM 3.0, the existing flowdefinition will be replaced.
If you encounter inconsistencies, you can return to the standard flowdefinition by executing transaction SMO8FDG for the relevant BDoctypes.

Features

Selection
You can reduce the selection by providing a BDoc type ID or a BDoc typename.

Output
You get a list of selected BDoc types with status of flow definitionchanges.