Content Migration Manager > User's Guide (CMM 1899 Series, Jan 2020) > Part I: New features, Release notes, and Configuration > 1. New features
CMM general new features
Support for Teamcenter 12 CMM now supports Teamcenter 12.1, 12.2, and 12.3. CMM menu layout The CMM menus have been reorganized to better indicate when certain activities should be performed during the migration process and to support new menu options. CMM Solo progress tracking CMM Solo now supports tracking of the source CAD files and their migration. New menu selections are:
- Audit source CAD files Locates all source CAD files and identifies duplicate files.
- Determine migrated files and Determine unmigrated files Determines what has been migrated and what remains to be migrated. These menu selections only work when you have turned on the Reuse Lookup Table in the options file. CMM Solo import to Teamcenter CMM Solo now helps you import migrated NX files into Teamcenter and tracks what has been imported. The new menu selections for this are:
- Prepare data for import
- Run Teamcenter import
- Update item import status
New features CMM Solo skip item selection after loading The new CMM Solo option Allow item selection after load is added to let you immediately begin migration of all items once they have been loaded. When running CMM Solo with the graphical user interface, you can currently select or deselect individual items for migration after all of the items have been loaded into CMM Solo. After you select and deselect items as desired, you are then required to choose the migration command to start the migration. The select and deselect step can now be skipped so that after all items have been loaded, migration of all of the items immediately begins without any interaction. The new option is not selected, by default, which keeps the previous behavior and lets you select and deselect items before migration. When the option is selected, the select and deselect step is skipped and migration begins immediately after load. Check in of items During migration, CMM checks items out from Teamcenter. If the migration is aborted by the user or crashes, items may be left checked out. The menu selection Administration→Check in items is added to let CMM check in items that have been left checked out. Reporting The reporting functionality is enhanced to provide additional reports and commands. Under the CMM→Reporting command, you can now select the following to create additional reports:
- Create Post Report Summary — Creates an Excel compatible file that contains statistics on success and failure rates based on item types and individual items.
- Search for specific errors — Lets you search for all error messages or specifi error messages based on a set of strings.
- Sum feature success/failure counts — Creates a report that counts all features in the selected data. The count can be for total features or specific features, such as imported, failed, locked, and so on. In CMM Solo, the Reporting command is added. The following selections are available for that command:
- View Report — View a report for the selected item and its children.
- Create Post Report Summary — Creates an Excel compatible file that contains statistics on success and failure rates based on item types and individual items.
- Search for specific errors — Lets you search for all error messages or specifi error messages based on a set of strings.
- Sum feature success/failure counts — Creates a report that counts all features in the selected data. The count can be for total features or specific features, such as imported, failed, locked, and so on. New features
New features Reuse Lookup Table For CMM Solo, the Reuse Lookup Table menu selection is added. New functionality is added in CMMSolo to aid in the migration of large amounts of data. It is now easier to migrate data from several source folders without migrating shared data multiple times. Using a Reuse Lookup Table, CMMSolo detects previously migrated data even when it is migrated from and to separate folders. The Reuse Lookup Table is designed to support a single migration user to leverage previously migrated source CAD files without the need to collocate (by copying) additional files into existing processing folders. A typical environment for Resource Lookup Table deployment would be where you have complete, separate products and want to export complete products into their own folders. Common source CAD files of each product would then be found in multiple folders. For example, you have a large collection of data that you want to migrate using CMMSolo, but you need to migrate it in smaller groups. For organizational purposes you have source data in many folders based on the top-level assemblies, but each folder contains some of the same source CAD parts. You choose to migrate your first top-level assembly contained in folder SourceCAD1 using a scratch folder called CMMScratch1. Then you migrate your next top-level assembly contained in SourceCAD2 into the scratch folder CMMScratch2. New features
New features CMMSolo is now able to detect that some of the same parts migrated from Source A are also used in the top-level assembly contained in Source B. By setting the CMMSolo Reuse Lookup Table option, you can reuse the parts migrated from Source A. It is recommended that a single migration user sequentially processes the set of folders. It is not recommended that multiple CMM processes are launched against a shared system file location. This could result in access violations as multiple processes may access the same source CAD file or result in inconsistent reuse of NX data files, since the Reuse Lookup Table is unique to each user account. Although the Reuse Lookup Table advances the management of processed files, it is not a replacement for the capabilities provided by utilization of Teamcenter. Additionally, it is recommended that you ensure your source CAD files are up-to-date as it is possible that matches may cause update conflicts during loading. This functionality is provided for Pro/E, SolidWorkds, and CATIA V5 migrations. It is not effective for CATIA V4 or I-deas due to the structure of the source CAD data. In addition the following selections are then available for that command:
- Write NX item and children to a file — You can select a top-level NX item and generate a listing of the names and locations of all of its children. This includes all levels of the product structure.
- Copy NX item and children — You can select a top-level NX item and copy it and all of its children to a directory. This includes all levels of the product structure.
- Scan for duplicate source CAD files — You can now search your source CAD files to locate duplicate items. From a list file of directories to search, CMM locates all files with the same name, size, and checksum, and creates a spreadsheet compatible report. Reporting migration result attributes Specific migration report attributes have been added to the NX file. Since these values are now stored in the NX part, assembly, and drawing files, you can modify the values during migration repair. Then you can create a report of the current value of these attributes using either:
- The new menu selection Report migration attributes in both CMM and CMM Solo.
- The CMMBatch -reportNXAttr option To save these attributes, select the NX Part option Save Migration Report in NX File before migrating.
Source: CMM 1921 download (Support Center PL20201112075217794, CMM1921.7z), NXMigration/Documentation/cmm_1921.pdf, page 17 · retrieved 2026-10-02