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

Standard Database for Intergraph Smart Reference Data Merge Tool Help
Language
English
Product
Intergraph Smart Reference Data Standard Database
Search by Category
Installation & Upgrade
Standard Database for Smart Reference Data Version
12.1

Administration

This module covers merge workflows for the following administration related objects and 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

  • Parameters

  • Interface settings

  • Project/Project Discipline Defaults

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

Document management

This module covers merge workflows for below Document Management related objects and respective child nodes.

  • Documents

  • Tool Version Management

  • Symbol Library Management

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

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

  • When a data is merged at commodity code level without applicable documents, then documents and only dependent parent data like PDB documents, symbol library and symbols will get merged. User 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 Smart Reference Database transfer jobs screen.

Attribute management

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

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

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

Table management

This module allows user to merge the following table management related objects and respective child nodes.

  • Table Types (For Details)

    This node is used to merge the tables and respective details. There are three types of table types in this module (commodity code tables, interface tables and specification tables).

  • Table Types (All) -Table Attributes

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

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

  • Under 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 Magenta color.

  • If user faces error message, Unique Constrain (M_SYS.TD_ID_U01) Violated, while merging table details, user should run TR_53527_update_sequence_val.sql script (Delivered at the location <SDB Installation Location>\db_server\scripts) on the target database.

Geometric Management

This module allows user merge for below Geometric management related objects and 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 user selects Source Only and Save direct children for source only data, geometric rules will merge the respective rule definitions automatically.

  • For target-only records, user must verify that the data does not create any duplicates in the target database and takes appropriate actions to prevent the same.

As there is a huge data in this module, user can use Excel Report functionality to review the data.

Commodity/Ident management

This module allows user to merge below 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 sequential order.

    Under Commodity Group/Part/Commodity Code node, a quick merge node, Commodity Code Descriptions (Differences Only), and Commodity Code layouts (Differences Only) are 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 ‘Magenta’ color.

    • For Commodity code, 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 the user selects a single record for merge, all the data under that node will get merged to the customer database automatically.

    • It is recommended to build the required commodity idents & geometric relations from Smart Reference Data, instead of merging through the 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.

As data is huge in this module, use Excel Report functionality to review the data.

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

  • Commodity codes are updated with latest commodity rules in DB. User must merge commodity rules and update the commodity codes first in Smart Reference Database and then use Standard Database. Otherwise duplicate commodity codes will get created in the target database.

Geometric rules

This module allows user to merge Geometric rules and respective child details.

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

  • For different records and only target database records, users need to validate the data and then take appropriate actions on it.

It is recommended to validate and rebuild the commodity rules as per requirement after migration is completed.

Specification

This module allows user 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 user merges Source Only specifications at header level, all the child records such as Spec Headers, Spec Items, and so on will also get merged automatically to the target database.

The following nodes present under specifications, delete and replace functionality is implemented.

  • Specification Header Notes

  • Specification Header Geometrics

  • Specification Details

  • Specification Items

Delete and Replace functionality is implemented such that even if user selects a single record in the grid and clicks Delete and Replace, all the data under that node on the target side is deleted and is replaced by the data on the source side. Also, Delete and Replace option is enabled only if there are any Source Only or Difference records under that node.

Smart 3D/CADWorx Integration

This module allows user to merge the following Smart 3D/CADWorx integration related objects and respective child nodes.

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

    Under 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 Magenta color.

    Delete and Replace functionality is implemented for Templates data.

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

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

  • User cannot merge Data Table Configuration Attributes, if physical attribute already exists in the target and is different from the source database. User need to remove these physical attributes in the target database to perform merge operation.

As data is huge in this module, use Excel Report functionality if Differences not shown in hierarchy mode is used for migration.

SmartPlant Isometrics Integration

This module allows user to merge the following SmartPlant Isometrics integration related objects and respective child nodes.

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

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

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

CMS (Component Management System)

This module allows user 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 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 Magenta color.

As data is huge in this module, use Excel Report functionality if Differences not shown in hierarchy mode is used for migration.

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