Module Level Workflows to Merge Data from the Source to the Target - Intergraph Smart Reference Data Standard Database - Version 12.5 - Installation & Upgrade - Hexagon

Standard Database for Intergraph Smart Reference Data Installation and Migration
Language
English
Product
Intergraph Smart Reference Data Standard Database
Search by Category
Installation & Upgrade
Standard Database for Smart Reference Data Version
12.5

Administration

This module covers merge workflows for the following Administration related objects and their respective child nodes:

  • Languages

  • Standards

  • Disciplines

  • Units related objects (Unit Systems, Unit Sets, Unit Groups, Unit Types, and Unit to Unit)

  • Interfaces

  • Interface Dependent Units

  • Privileges

  • User

  • User Security

  • Approval Templates

  • Menus

  • Roles/Menus

  • Configurations

  • Guided Tours

  • Attribute Security

  • Sections

  • License Modules/Menus

  • DBA Settings

  • Parameters

  • Interface Settings

  • Project/Project Discipline Defaults

  • Custom Views

You need to traverse all the data nodes under each object, validate them, and then select the required rows for the merge process.

Document Management

This module covers merge workflows for the following Document Management related objects and their respective child nodes:

  • Documents

  • Tool Version Management

  • Symbol Library Management

  • When you merge documents present only in the source, then the document files (Symbol DLL) get merged automatically as an additional dependency.

  • To merge the child data for records present in Source only, in the Save window, select Save child dependencies for source only.

  • When data is merged at the commodity code level without applicable documents, only dependent parent data like PDB documents, symbol libraries, and symbols will get merged. You must merge additional dependencies like document files and PDB document views manually to get symbol DLLs and gif files at the time of commodity code export using the Smart Reference Database Transfer Jobs screen.

Attribute Management

This module allows you to merge Attribute groups and their respective child nodes.

  • You must verify and merge attribute groups, attributes, and attribute values at each level.

  • The merging of additional child dependencies is not applicable for these data nodes.

Table Management

This module allows you to merge the following Table Management related objects and their respective child nodes:

  • Table Types (For Details)

    This node is used to merge the tables and their respective details. There are three types of tables in this module, which are:

    • Commodity Code Tables

    • Interface Tables

    • Specification Tables

  • Table Types (All) -Table Attributes

    This node is used to merge the tables and their respective attributes, which are used for creating geometrics.

  • As the data is huge in this module, it is recommended to use the Excel Report functionality to identify the required data that needs to be merged if the Differences not shown in hierarchy mode is used for migration.

  • Under the Commodity Code Tables node, a quick merge node, Commodity Code Table Details (Differences Only), is provided to facilitate quick merging of all the table detail differences under a single node instead of navigating across multiple nodes in the hierarchy. For easy identification, this node is color coded with the Magenta color.

  • If you face an error message, Unique Constraint (M_SYS.TD_ID_U01) Violated, while merging table details, you must run the TR_53527_update_sequence_val.sql script (Available at: <SDB Installation Location>\db_server\scripts) on the target database.

Geometric Management

This module allows you to merge the following Geometric Management related objects and their respective child nodes:

  • All types of Geometric Tables - This node is used to merge all the geometric related data (Commodity geometrics, Filter geometrics, Other geometrics, Other special geometrics, Rating geometrics, Standard geometrics, and Wall thickness geometrics).

  • Nominal Sizes - This node is used to merge the nominal size tables used in the specifications.

  • Outer Diameters - This node is used to merge the outer diameter tables.

  • Branches - This node is used to merge the branch tables used in the specifications.

  • Schedules - This node is used to merge the outer diameter tables.

  • Nominal Reducers - This node is used to merge the nominal reducer tables.

  • Metric/English Equivalence - This node is used to merge English to metric Equivalence tables.

  • When you select Source Only and Save direct children for source only data, geometric rules will merge the respective rule definitions automatically.

  • For Target Only records, you must verify that the data does not create any duplicates in the target database and take appropriate actions to prevent the same.

SHARED Tip As there is a lot of data in this module, you can use the Excel Report functionality to review the data.

Commodity/Ident Management

This module allows you to merge the following Commodity/Ident Management related objects and respective child nodes:

  • Commodity Rules - This node is used to merge the commodity rules and their child details.

  • Commodity Group/Part/Commodity Codes - This node is used to merge commodity groups, parts, commodity codes, and respective child details in a sequential order.

    Under the Commodity Group/Part/Commodity Code node, a quick merge node, Commodity Code Descriptions (Differences Only) and Commodity Code layouts (Differences Only), is provided to facilitate quick merging of all the Commodity Code Description differences and Commodity Code layout differences, respectively under a single node instead of navigating across multiple nodes in the hierarchy. For easy identification, this node is color coded with the Magenta color.

    • For Commodity code, the Delete and Replace functionality is implemented as commodity code, which is completely dependent on commodity code details. And partial merging of commodity code details will lead to incorrect data in the customer database. With this, even if you select a single record for merge, all the data under that node will get merged to the target database automatically.

    • It is recommended to build the required commodity idents and geometric relations from SRD instead of merging through the SDB Merge Tool.

  • Object Parameters - This node is used to merge object parameters and their child details.

  • Part Object Parameters - This node is used to merge object parameters linked with the parts.

  • Parts with Table Groups and Parts with Table Details - These nodes are used to merge table groups and table details linked with the parts.

  • Parts with SP3D Short Codes - This node is used to merge Smart 3D short codes assigned at the part level.

SHARED Tip As there is a lot of data in this module, you can use the Excel Report functionality to review the data.

  • In the SDB Merge Tool, the Code list number associated with a PDB document is displayed instead of the PDB document sequence.

  • The Commodity codes are updated with the latest commodity rules in the database. You must merge commodity rules and update the commodity codes first in SRD, and then use SDB. Otherwise, duplicate commodity codes will be created in the target database.

Fluids

This module allows you to merge the following specification-related objects and their respective child nodes:

  • Fluid Color Codes - This node is used to merge the Smart Reference Database fluid color codes.

  • Danger Classes - This node is used to merge the Smart Reference Database Danger Classes.

  • Fluid Class Unique Keys - This node is used to merge the Smart Reference Database fluid class unique keys.

  • Fluid Class Unique Keys - This node is used to merge the Smart Reference Database fluid class unique keys.

  • Fluid Groups and Classes - This node is used to merge the Smart Reference Database fluid groups and classes and their respective child details.

Assembly Management

This module allows you to merge the objects related to assemblies and their respective child nodes.

Geometric Rules

This module allows you to merge Geometric Rules and respective child details:

  • When you select Source Only and Save direct children for source only data, geometric rules will merge the respective rule definitions automatically.

  • For different records and Target Only database records, you need to validate the data and then take appropriate actions on it.

It is recommended to validate and rebuild the commodity rules according to your requirements after the migration is complete.

Specification

This module allows you to merge the following Specification related objects and respective child nodes:

  • Short code management - This node is used to merge the Smart Reference Database short codes and respective child details.

  • Notes - This node is used to merge the specification notes.

  • Specification Rules - This node is used to merge the specification rules and respective child details.

  • Specification Types - This node is used to merge the specification types and respective child details.

  • Functional Specification Setup - This node is used to merge the functional specification setup and respective child details.

  • Specifications - This node is used to merge all the specifications related data and respective child details.

When you merge the Source Only specifications at the header level, all the child records such as, Spec Headers, Spec Items, and so on, will also get merged automatically to the target database.

Smart 3D/CADWorx/PDMS Integration

This module allows you to merge the following Smart 3D/CADWorx/PDMS Integration related objects and respective child nodes:

  • Configuration - This node is used to merge all the Smart3D/CADWorx/PDMS configuration related data (Data Tables, Smart 3D Attributes, Transfer Types, Retrieval Sources, Procedures, Data Table Configurations, Templates, Data table mappings, and Attribute mappings) and their respective child details.

    Under the Data Table Configurations node, a quick merge node, Data Table Configuration Attributes (Differences Only), is provided to facilitate quick merging of all the Smart 3D Data Table Configuration Sheet Attribute differences under a single node instead of navigating across multiple nodes in the hierarchy. For easy identification, this node is color coded with the Magenta color.

  • Transfer Jobs - This node is used to merge all the Smart3D/CADWorx/PDMS transfer job related data (General Configurations, Destinations, Catalog Structures, and Transfer Jobs) and their respective child details.

  • If you want to merge any Smart 3D related data that is already available in the CADWorx interface of target database or vice versa, it is recommended to rename the values accordingly in the target database and then merge the respective record from the source to the target.

  • You are not allowed to merge Data Table Configuration Attributes if a physical attribute already exists in the target database and is different from the source database. You need to remove these physical attributes from the target database to perform a merge operation.

SHARED Tip As there is a lot of data in this module, use the Excel Report functionality if the Differences not shown in hierarchy mode is used for migration.

Smart Isometrics Integration

This module allows you to merge the following Smart Isometrics Integration related objects and respective child nodes:

  • Master Data - This node is used to merge all the Smart Isometrics master data required for configuring Smart Isometrics integration and respective child details.

  • Smart Isometrics SKEY Mappings - This node is used to merge the SKEY mappings required for configuring Smart Isometrics integration and respective child records.

  • Export - This node is used to merge the Smart Isometrics export related data and respective child records.

CMS (Component Management System)

This module allows you to merge the following CMS related objects and respective child nodes:

  • Manage Class Systems - This node is used to merge CMS Class related data and respective child details.

  • Component Manager - This node is used to merge CMS Components related data and respective child details.

    Under the Class System node, a quick merge node, CMS Objects (Differences Only), is provided to facilitate quick merging of all the CMS Class Property and CMS Class Layout differences under a single node instead of navigating across multiple nodes in the hierarchy. For easy identification, this node is color coded with the Magenta color.

SHARED Tip As there is a lot of data in this module, use the Excel Report functionality if the Differences not shown in hierarchy mode is used for migration.

Unique key details must be set on the source database for existing class properties prior to the merge of CMS component data.