Migrate legacy units of measure to the unified measurement system

As of version 2406, Teamcenter has an updated units of measure capability. Following upgrade of a Teamcenter installation from a version prior to 2406, an administrator can migrate legacy BMIDE units of measure to the new unit management system (UMS) using the ums_mapping utility. The utility links legacy units to unit definitions in the UMS. If necessary, the linking and mapping can later be reverted. Configure units of measure relationships Use the following steps to create a mapping configuration file that identifies the relationship between legacy units of measure and unit definitions in the unified measurement system. Procedure In a Teamcenter command window, run the ums_mapping utility with the -analyze -report_file option. For example, Copy ums_mapping -u=username -p=password -analyze -report_file=c:\temp\mapping_config.csv The utility examines the Teamcenter database for existing UMS unit definitions. The utility then creates mappings between the legacy units of measure to existing unit of measure definitions in the UMS. These mappings are created based on unit names and symbols. The utility generates the mapping_config.csv file showing these mappings along with units for which it could not create mappings between the systems. The file contains the following information for each unit. Column Definition Is Approved Remove the # character in this column to process this unit when using -map, -unMap, or -createMap. UOM Name The name of the unit in the legacy system. UOM Symbol The symbol of the unit in the legacy system. In Use A value of Yes indicates that this unit is used by an object in the legacy system. Action The utility action performed to create the file. Status The unit's mapping state at the time the file was created. Details A description of the unit's state and any recommended actions. Unit Definition ID The ID of the unit in the UMS. Unit Definition Name The name of the unit in the UMS. Unit Definition Symbol The symbol of the unit in the UMS. In the command window, the utility also summarizes the unit mappings between units in the legacy and unified measurement systems. Using an ASCII editor or Microsoft Excel, review the mappings in mapping_config.csv. Approve proposed matches by removing the "#" symbol from the first column of that line of the file. Units have the following mapping states. Existing-mapped Units with this state already exist in the UMS. No further action is needed for these. Candidate-match The utility proposes a mapping for the unit of measure. Legacy units with this status completely or partially match unit definitions in the UMS. Multiple-match The legacy unit of measure is a candidate to match more than one unit definition in the UMS. Determine which definition is the correct mapping for the unit and update the .csv file accordingly. A legacy unit of measure can map to only one unit definition in the UMS. Multiple legacy units of measure can map to a single unit definition in the UMS. Non-matching The utility could not determine a candidate mapping for the unit of measure or the UMS unit definition. If there is no matching UMS unit for a unit of measure, manually review the UMS unit definitions in the .csv file for an appropriate definition. Update the column information to map the unit of measure to this unit definition. If you cannot find a match, use the ums_import_unit_definitions utility to create an appropriate unit definition in the UMS and re-run this process to approve the mapping of the unit of measure to this new unit definition in the UMS. If there is no matching unit for a UMS unit definition, follow the steps in Create units of measure later in this topic. NA This unit of measure is specific to Classification and is not mapped. No further action is needed for these. Once you have reviewed, revised, and approved the units of measure mappings, perform a dry run of linking the approved units of measure to unit definitions in the UMS. Use a command of the following form Copy ums_mapping -u=username -p=password -analyze -input_file=c:\temp\mapping_config.csv -report_file=c:\temp\analyze_mapping_config.csv The utility generates a .csv report file that shows the results that would have occurred in and actual linking of the units approved in the mapping configuration file. Review these results to ensure the linking will occur as you expect. Address any failures or other issues by updating the configuration file and performing additional dry runs. Add the unit of measure relationships to the Teamcenter database Once you have confirmed the units of measure are mapped properly in the mapping configuration file, you are ready to add the relationships to the Teamcenter database. Do so using a command of the following form. (You must be a Teamcenter administrator who is a member of a group with DBA privileges to run this command.) Copy ums_mapping -map -input_file=c:\temp\mapping_config.csv -report_file=c:\temp\mapping_report.csv This example updates the Teamcenter database with the relationships defined in mapping_config.csv. Approved unit relationships in the file (lines with no "#" symbol in the first column) are added to the Teamcenter database. The utility generates the report mapping_report.csv listing the updates and their completion status. Remove unit of measure relationships from the Teamcenter database If you want to remove one or more relationships from the Teamcenter database, you can do so using the ums_mapping utility. You must be a Teamcenter administrator who is a member of a group with DBA privileges to remove these relationships. Procedure To remove a limited number of mapping relationships, update the mapping configuration file (mapping_config.csv in the earlier example) by removing the "#" symbol from the first column of each unit for which you want to remove the mapping relationship. In a Teamcenter command window, run the ums_mapping utility with the -unmap option. For example, Copy ums_mapping -u=admin-username -p=admin-password -g=dba -unmap -input_file=c:\temp\mapping_config.csv -report_file=c:\temp\mapping_report.csv The utility generates the report mapping_report.csv listing the removed unit relationships. Results In cases where you want to remove several existing units of measure relationships from the Teamcenter database, consider using the ums_mapping utility with the -all option. Doing so removes all existing units of measure relationships from the Teamcenter database. After removing all relationships, restart migrating legacy units of measure as described earlier. To remove all existing units of measure relationships from the Teamcenter database, use a command of the following form. Copy ums_mapping -u=admin-username -p=admin-password -g=dba -unmap -all -report_file=c:\temp\mapping_report.csv The utility generates the report mapping_report.csv listing the removed unit relationships. Create units of measure If the UMS contains definitions with no related unit of measure, create units of measure for the definitions using the ums_mapping utility with the -create_uom option. Doing so creates new units of measure with relationships to the unit definitions previously with no related definitions. These relationships are automatically added to the Teamcenter database. In a Teamcenter command window, enter a command of the following form: Copy ums_mapping -u=admin-username -p=admin-password -g=dba -create_uom -report_file=c:\temp\unit_report.csv The utility analyzes the UMS, creates new units for definitions without related units, and generates the report unit_report.csv listing the created units.